Key Guidelines for
Implementation
General Guidelines
TCMP uses three trunk port states to control port activation and
deactivation:
notInUse — A trunk port in this state has not been selected to
participate in the trunk.
selected — TCMP has selected the trunk port to participate in the
trunk, but the port has not yet become active.
inUse — A trunk port is fully active on the trunk.
Consider the following important factors when you implement and
configure trunks:
Create trunks before you define VLANs.
The system supports four point-to-point trunks, each built from up to
eight ports. All channels in a trunk must be parallel and must connect:
Correctly configured ports
Identical types of ports (with no two ports on a trunk connected to
the same network)
Identical types of network nodes (switches or servers)
You cannot mix FDDI, Fast Ethernet, and Gigabit Ethernet links in a
trunk. All links to be trunked must be homogeneous.
When multiple links are trunked, it can be difficult to manage and
troubleshoot individual port-to-port connections if a connectivity
problem occurs. This issue may not be of concern in a server farm
room. But if you use trunking extensively between wiring closets and
data centers, the large number of connections involved and their
distributed nature may make their management and troubleshooting
difficult. 3Com recommends that you apply trunking only within data
center and campus interconnect areas.
Key Guidelines for Implementation
147
Need help?
Do you have a question about the corebuilder 3500 and is the answer not in the manual?
Questions and answers