In-Band Discovery of McDATA Switches.
|Article:TECH24954|||||Created: 2003-01-18|||||Updated: 2005-01-14|||||Article URL http://www.symantec.com/docs/TECH24954|
In-Band Discovery of McDATA Switches.
VERITAS SANPoint Control (tm) uses the GS-3 Management Server Common Transport (MS/CT) protocol in Management Server Explorer (MGEX) for in-band discovery of McDATA switches. McDATA switches can be discovered in-band by either the SANPoint Control primary server or a remote in-band host when the following requirements are met:
- A direct Fibre Channel (FC) connection to either the SANPoint Control primary server or to a SANPoint Control Remote Agent InBandHost exists. MGEX in-band discovery does not work without a direct FC connectivity to a host running MGEX explorer.
- Open Systems Management Server (OSMS) License is installed on each McDATA switch being discovered in-band by MGEX. The McDATA OSMS license is also required for SANPoint Control to perform zoning on McDATA switches. To purchase an OSMS license, contact McDATA.
- The exploring host has a SANPoint Control supported host bus adaptor (HBA) make, model, firmware and driver. Check the Hardware Compatibility List (HCL) for this.
- The HBA is set to point-to-point topology mode.
- The HBA explorer is enabled on the exploring host.
- Switch model and firmware are supported per HCL. Switch discovery and zoning is not possible without the supported firmware.
Switch has the supported version of Fabric Alliance MIB installed on it. Without the supported MIB, SANPoint Control will not be able to perform Simple Network Management Protocol (SNMP) led administration of the switch which is explored by MGEX.
- Switch should have an assigned switch name. By default, the McDATA switch name is Null. Without a legitimate name, the switch will not be discovered in-band.
- Each switch should have a name that is unique in the SAN. If more than one switch in the SAN has a particular name (such as default names), only the first switch with that name will have collectors associated with it.
- Each switch should be configured for Out-of-Band Addressing even when it is discovered in-band. If the switch is not configured for out-of-band addressing (IP address, subnet mask, and gateway), then SANPoint Control features such as policies, reports and in-context launch of the McDATA Enterprise Fabric Connectivity Manager (EFCM) will not be available. Out-of-band addressing information is discovered by the SANPoint Control configuration utility. To check this information manually, see your vendor documentation for details. This configuration is done on the switch itself, and is not the same as subnet mask and gateway configuration options within SANPoint Control. McDATA manuals may be consulted for procedures to add out-of-band addressing to the switch.
- Each switch must be configured to send SNMP traps to the SANPoint Control primary server. If this is not done, SNMP trap-based collectors will not be updated and combination collectors will take longer to update. To configure the SNMP trap recipient host for the switch, see McDATA switch manuals.
- To take advantage of all the SANPoint Control features, the EFCM proxy should be accessible through IP by SANPoint Control primary server. If the proxy is on a public subnet, all SANPoint Control features will work (provided other requirements are met).
- Zoning must be set to Soft (also called Advisory) on the switch. Hard zoning (switch-port zoning) is not currently supported for McDATA switches in SANPoint Control. To configure the switch for Soft zoning, see McDATA switch manuals.
- In-Band Common Transport (CT) commands must be enabled in the EFC Manager. SANPoint Control in-band discovery and zoning commands will not work unless in-band CT commands are enabled. To configure this in the McDATA switch, see switch manuals.
Article URL http://www.symantec.com/docs/TECH24954