HP Cisco MDS 9020 Cisco MDS 9000 Family Fabric Manager Configuration Guide, Re - Page 1178

Monitoring Traffic Using Fibre Channel Analyzers Chapter 62 Monitoring Network Traffic Using SPAN Send documentation comments to [email protected] Session 2 (active) Destination is fc1/9 No session filters configured Ingress (rx) sources are vsans 12 fc1/6 (vsan 1-20), Egress (tx) sources are fc1/6 (vsan 1-20), Once upgraded to Cisco MDS SAN-OS Release 1.1(1): Session 2 (inactive as no active sources) Destination is fc1/9 No session filters configured No ingress (rx) sources No egress (tx) sources Note The deprecated configurations are removed from persistent memory once a switchover or a new startup configuration is implemented. Session 2 had a source VSAN 12 and a source interface fc1/6 with VSAN filters specified in Cisco MDS SAN-OS Release 1.0(4). When upgraded to Cisco MDS SAN-OS Release 1.1(1) the following changes are made: - The source VSAN (VSAN 12) is removed (rule 1). - The source interface fc1/6 had VSAN filters specified-it is also removed (rule 2). Monitoring Traffic Using Fibre Channel Analyzers You can use SPAN to monitor traffic on an interface without any traffic disruption. This feature is specially useful in troubleshooting scenarios where traffic disruption changes the problem environment and makes it difficult to reproduce the problem. Without SPAN You can monitor traffic using interface fc1/1 in a Cisco MDS 9000 Family switch that is connected to another switch or host. You need to physically connect a Fibre Channel analyzer between the switch and the storage device to analyze the traffic through interface fc1/1 as shown in Figure 62-8. 62-10 Cisco MDS 9000 Family CLI Configuration Guide OL-16184-01, Cisco MDS SAN-OS Release 3.x