Port Configuration
8-6
8
Creating Trunk Groups
You can create multiple links between devices that work as one virtual, aggregate
link. A port trunk offers a dramatic increase in bandwidth for network segments
where bottlenecks exist, as well as providing a fault-tolerant link between two
devices (i.e., single switch or a stack). You can create up to 32 trunks.
The switch supports both static trunking and dynamic Link Aggregation Control
Protocol (LACP). Static trunks have to be manually configured at both ends of the
link, and the switches must comply with the Cisco EtherChannel standard. On the
other hand, LACP configured ports can automatically negotiate a trunked link with
LACP-configured ports on another device. You can configure any number of ports
on the switch as LACP, as long as they are not already configured as part of a static
trunk. If ports on another device are also configured as LACP, the switch and the
other device will negotiate a trunk link between them. If an LACP trunk consists of
more than eight ports, all other ports will be placed in a standby mode. Should one
link in the trunk fail, one of the standby ports will automatically be activated to
replace it.
Command Usage
Besides balancing the load across each port in the trunk, the other ports provide
redundancy by taking over the load if a port in the trunk fails. However, before
making any physical connections between devices, use the web interface or CLI to
specify the trunk on the devices at both ends. When using a port trunk, take note of
the following points:
• Finish configuring port trunks before you connect the corresponding network
cables between switches to avoid creating a loop.
• You can create up to 32 trunks on a switch or stack, with up to eight Gigabit ports
per trunk or up to four 10Gbps ports per trunk. Note that because the stack
functions conceptually as a single system, you can include ports from different
units in the same trunk. For example, you could connect ports spread across
several units that belong VLAN 2 into a common trunk.
• The ports at both ends of a connection must be configured as trunk ports.
• When configuring static trunks on switches of different types, they must be
compatible with the Cisco EtherChannel standard.
• The ports at both ends of a trunk must be configured in an identical manner,
including communication mode (i.e., speed, duplex mode and flow control), VLAN
assignments, and CoS settings.
• Any of the Gigabit ports on the front panel can be trunked together, including ports
of different media types.
• All the ports in a trunk have to be treated as a whole when moved from/to, added
or deleted from a VLAN.
• STP, VLAN, and IGMP settings can only be made for the entire trunk.
Summary of Contents for 8926EM
Page 6: ...ii ...
Page 34: ...Getting Started ...
Page 44: ...Introduction 1 10 1 ...
Page 62: ...Initial Configuration 2 18 2 ...
Page 64: ...Switch Management ...
Page 76: ...Configuring the Switch 3 12 3 ...
Page 118: ...Basic Management Tasks 4 42 4 ...
Page 164: ...User Authentication 6 28 6 ...
Page 176: ...Access Control Lists 7 12 7 ...
Page 284: ...Quality of Service 14 8 14 ...
Page 294: ...Multicast Filtering 15 10 15 ...
Page 300: ...Domain Name Service 16 6 16 ...
Page 310: ...Dynamic Host Configuration Protocol 17 10 17 ...
Page 320: ...Configuring Router Redundancy 18 10 18 ...
Page 344: ...IP Routing 19 24 19 ...
Page 356: ...Unicast Routing 20 12 20 Web Click Routing Protocol RIP Statistics Figure 20 5 RIP Statistics ...
Page 386: ...Unicast Routing 20 42 20 ...
Page 388: ...Command Line Interface ...
Page 400: ...Overview of the Command Line Interface 21 12 21 ...
Page 466: ...SNMP Commands 24 16 24 ...
Page 520: ...Access Control List Commands 26 18 26 ...
Page 546: ...Rate Limit Commands 30 2 30 ...
Page 612: ...VLAN Commands 34 24 34 ...
Page 626: ...Class of Service Commands 35 14 35 ...
Page 670: ...DHCP Commands 39 16 39 ...
Page 716: ...IP Interface Commands 41 36 41 ...
Page 768: ...IP Routing Commands 42 52 42 ...
Page 770: ...Appendices ...
Page 791: ......