4.Connect the 9304M, 9308M, 6308M-SX, or 6208M-SX to the switch(es) that were disconnected in step 2 and bring up the network.

Operating Notes for Using the 9304M, 9308M, 6308M-SX, or 6208M-SX in a Tagged VLAN Environment.

If there is more than one of these devices in the network, the root (primary) device must have an STP Priority setting that is lower than the other such devices in the network. This ensures that the device will become the root if the primary device fails.

C a u ti o n

If there is more than one such device in a tagged VLAN environment with STP enabled, STP will fail if the link between the primary and secondary device fails while both devices continue to route packets. An STP failure will cause broadcast storms and will result in a catastrophic failure of the network. For this reason, using STP in a tagged VLAN environment with multiple devices is not recommended.

The following scenarios will cause STP to fail:

■The 9304M, 9308M, 6308M-SX, or 6208M-SX is not configured to be the root bridge, as described above. In this case, STP fails between any of these devices and an HP ProCurve switch.

■If there is more than one such device in the network and they are not directly connected, STP will fail between these devices. Multiples of these devices must be directly connected to each other in order to correctly interpret each other’s BPDU (bridge protocol data unit) packets.

Auto-Negotiation Between the HP 9300M Routing Switches and Extreme Summit™ Switches

Condition. Auto-Negotiation between the HP 9300M routing switches and Extreme Summit switches may sometimes fail.

Solution. Disable auto-gig on the routing switch port(s) attached to the Extreme Summit switch.

For example, use the following CLI commands to disable auto-gig on port 2 in slot 1 of the HP J9304M Routing Switch:

HP 9304M (config)# int e 1/2

HP 9304M (config-if-1/2)# no auto-gig

Web Management Interface Running Slow or Failing To Respond

Condition. The Web management interface on the routing switch times out or does not respond. This can occur when the routing switch CPU is processing an excessive amount of broadcast traffic.

Solution. The Web management interface recovers automatically when the CPU is sufficiently free of broadcast traffic. Because the Web management interface is a low priority for the CPU, you may want to take steps to reduce the broadcast traffic on your network. One method for doing this is to use TopTools for Hubs & Switches (version N.01.03 or later) to determine the "top talkers" on your network, then create VLANs to segment the network for optimum traffic control.

Web Management Interface "Not Available" or "In Use"

Condition. You are unable to access the Web managment interface.

6