Port Mirroring
80-Series Modules
The following problem has no workaround:
■Removing a port mirror causes an interface to stay in the “UP” state with no connections to the interface.
Problem: | If you mirror multiple ports, the switch monitors both transmit and |
| receive traffic regardless of the direction of traffic that you specify. |
| The switch continues to monitor both directions of traffic even if |
| you remove the port mirror with multiple source ports and set up a |
| new port mirror with a single source port. |
Workaround: | Reset the switch before setting up a port mirror with a single source |
| port. |
Problem: | Version 5.2.2 of the switch software does not support piggyback |
| ports on |
| earlier than 5.2.2 and you set up a port mirror with a piggyback port |
| on an |
| as the startup configuration, and reset the switch, the switch retains |
| the port mirroring information and will reset repeatedly as long as |
| the port mirror exists. |
Workaround: | Before downloading and running v5.2.2, remove port mirrors with |
| piggyback ports on |
The following problems have no workaround: | |
Modules |
|
| ■ When you try to mirror a blocked port, the Web Agent |
| displays the port as forwarding, but it is blocked. When you |
| remove the blocked port from being mirrored, you receive |
| panic messages on the console. The problem does not |
| interrupt traffic or cause any other problems in the network. |
| ■ If a standby supervisor module installed in slot 2 has become |
| the Active supervisor (CPU) due to a failover, the web agent |
| shows the supervisor module in slot 1 as available for |
| mirroring during a port mirroring operation. This is incorrect. |
| This problem does not affect traffic running in the network. |
| * Note: The Supervisor module should not be configured |
| for port mirroring even if it displays as available for |
| port mirroring. |
24 | June 14, 2001 |
