Extreme 3802 Installation Guide
Summit 400 “e” Series Switches
Extreme Networks Consolidated "i" and "e" Series Hardware Installation Guide
85
Do not assign an in-band IP address to the management port VLAN. The management port VLAN is an
out-of-band VLAN, so if it is assigned an in-band IP address (an address where the source and
destination are in the same subnet), the switch treats it as a normal VLAN and attempts to route traffic
through it.
out-of-band VLAN, so if it is assigned an in-band IP address (an address where the source and
destination are in the same subnet), the switch treats it as a normal VLAN and attempts to route traffic
through it.
Extreme Networks does not recommend that you use the management port to route traffic to any front
panel port on the switch. The management port is designed only for switch management purposes.
panel port on the switch. The management port is designed only for switch management purposes.
There are two LEDs for the management port, located in the bottom corners of the port. The LED on the
bottom right turns solid green when a cable is inserted and the port detects a link. The LED on the
bottom left blinks green when there is transmission activity on the link.
bottom right turns solid green when a cable is inserted and the port detects a link. The LED on the
bottom left blinks green when there is transmission activity on the link.
Uplink Redundancy
The four fiber ports and the first four of the 10/100/1000BASE-T ports are designed as combination
ports for uplink redundancy. When sharing ports, only the fiber port or only the copper port can be
active at the same time. If copper port 1 goes down while transmitting packets, fiber port 1X activates
and becomes the primary link. See Figure 34 for a diagram of these combination ports.
ports for uplink redundancy. When sharing ports, only the fiber port or only the copper port can be
active at the same time. If copper port 1 goes down while transmitting packets, fiber port 1X activates
and becomes the primary link. See Figure 34 for a diagram of these combination ports.
The switch determines whether the port is the primary or redundant port based upon the order in
which the cables are inserted into the switch. When the switch senses that cables are in both the fiber
and corresponding copper port, the switch enables the uplink redundancy feature. For example, if you
insert mini-GBICs into ports 1X and 3X first, and then connect copper ports 1 and 3, the switch assigns
ports 1 and 3 as redundant ports.
which the cables are inserted into the switch. When the switch senses that cables are in both the fiber
and corresponding copper port, the switch enables the uplink redundancy feature. For example, if you
insert mini-GBICs into ports 1X and 3X first, and then connect copper ports 1 and 3, the switch assigns
ports 1 and 3 as redundant ports.
Figure 34: Redundancy cabling
You can override the configuration and behavior of these ports through the CLI. Using the CLI, you can
set a preference for either fiber or copper. You can also turn off port redundancy using the force option.
If a combination port fails to link, determine whether the force option is in effect. For more information
about using the CLI to set redundancy priority, see the ExtremeWare Software Users Guide.
set a preference for either fiber or copper. You can also turn off port redundancy using the force option.
If a combination port fails to link, determine whether the force option is in effect. For more information
about using the CLI to set redundancy priority, see the ExtremeWare Software Users Guide.
The Summit 400-48t switch Gigabit Ethernet port failover from the fiber link to the copper link takes 4-5
seconds. The Gigabit Ethernet port failover from the copper link to the fiber link takes 2-3 seconds.
seconds. The Gigabit Ethernet port failover from the copper link to the fiber link takes 2-3 seconds.
NOTE
To support automatic failover between the fiber and copper ports, you must use an Extreme mini-GBIC
connector.
connector.
1
2
3
4
1
2
3
4
ES4K019