SAN Switch
return to main contents page
return to "Management and monitoring target" contents page
Tuning Manager - Agent for SAN Switch
(1) Fabric configuration
- Fabric composed of only Brocade switches (B-Model)
- Fabric composed of only Cisco switches
When monitoring Cisco switches connecting to Cisco (Seed Switch), only Seed Switch is monitored in the fabric composed of only Cisco switches.
(2)Brocade switches (*1)(*6)
Product name
Brocade 300
Brocade 5100 or
Brocade 5300
Brocade 5460
Brocade 5410 or
Brocade 5424 or
Brocade 5430 or
Brocade 5431 or
Brocade 5432 or
Brocade 5450 or
Brocade 5470 or
Brocade 5480
Brocade 6505 or
Brocade 6510
Brocade M6505 or
Brocade 6520 or
Brocade 6546 or
Brocade 6547 or
Brocade 6548
Brocade 7500
(SilkWorm7500)
Brocade 7800
Brocade 7600 or
Brocade 7840
Brocade 8000
Brocade 48000
(SilkWorm 48000)
Brocade DCX or
Brocade DCX-4S
Brocade DCX8510-4 or
Brocade DCX8510-8
Brocade VA-40FC
Brocade Encryption Switch
Notes:
- Be careful when you monitor Brocade switches in a fabric for which the Fibre Channel routing function is enabled. If a virtual SAN has been created by using the Fibre Channel routing function, Agent for SAN Switch acquires information only for the physically connected ports and nodes.
- Agent for SAN Switch acquires configuration and performance information for standard FC ports, but does not acquire configuration or performance information from ports for which FCIP has been set as the networking method. 
Although the Brocade 7800 switch has an FCIP port, the switch does not collect FCIP port information. The information is discarded as on the Brocade 7500 switch.
Notes:
(*1) When Brocade B-Model switches and Brocade M-Model switches co-exist in same fabric, please contact your sales representaive for its support.
       We need to evaluate mixtured fabric environment.
(*6) HTM - Agent for SAN Switch 7.1.0-00 or later supports communication by HTTPS between HTM - Agent for SAN Switch and DCFM SMI Agent.
(3)Cisco switches(*5)(*8)
Product name
MDS 9216A or
MDS 9506 or
MDS 9509 or
MDS 9513
MDS 9124 or
MDS 9134 or
MDS 9222i
MDS 9148 or
MDS 9250i or
MDS 9706 or
MDS 9710
Cisco Nexus 5010 or
Cisco Nexus 5020 or
Cisco Nexus 5548UP or
Cisco Nexus 5548P or
Cisco Nexus 5596UP or
Cisco Nexus 5596T
Cisco Nexus 5624Q or
Cisco Nexus 5672UP or
Cisco Nexus 5696Q or
Cisco Nexus 56128P
Notes:
- Agent for SAN Switch acquires configuration and performance information for standard FC ports, but does not acquire configuration or performance information from ports for which FCIP has been set as the networking method.
- When you want to set up a new instance to monitor a Cisco switch, perform monitoring by connecting to Cisco (DCNM-SAN SMI-S Agent).
- HTnM - Agent for SAN Switch 7.1.0-00 or later supports communication by HTTPS between HTnM - Agent for SAN Switch and Cisco switches.
- When you want to set up a new instance to monitor a Cisco switch, perform monitoring by connecting to Cisco (DCNM-SAN SMI-S Agent). 
 Cisco no longer supports connecting to a Cisco (seed switch) and then directly collecting information from the FC Switch, so using this technique to investigate failures might no longer work.
- In this version, HTnM - Agent for SAN Switch is supported at the level of 7.6.0.
Notes:
(*5) HTM - Agent for SAN Switch 7.1.0-00 or later supports communication by HTTPS between HTM - Agent for SAN Switch and Cisco switches.
(*8) When you want to set up a new instance to monitor a Cisco switch, perform monitoring by connecting to Cisco (DCNM-SAN SMI-S Agent).
      Cisco no longer supports connecting to a Cisco (seed switch) and then directly collecting information from the FC Switch, so using this technique to investigate failures might no longer work.