McData Sphereon 4500 Fabric Switch
 
McData Intrepid 6140 Director
 
McData Intrepid 10000 (i10K) Director
 
McData Intrepid 6064 Director
 
McData Sphereon 4300 Fabric Switch
 

PLA-Support>Sun Systems>DISK>Switch>SN-DK: McData Switch
 

• SAN diagram (EFCM SAN/Export)
• switch data (EFCM / DCFM "Data Collection")
• Host logs (explorer or equivalent)
• Storage target logs

Step 1: Obtain a Picture/Diagram of the SAN
[EFCM steps] SAN...Export...Physical Map (JPG created)

Step 2: Obtain a 'Data Collection' from each switch in SAN.
[EFCM steps] Product View...Maintenance...Data Collection

[DCFM steps] Product View...Maintenance...Data Collection

Obtaining a 'Data Collection' output from the ECFM/DCFM GUI will provide all the switch configuration settings, zone, port state and log information. For EFCM, this can be performed for each switch in the SAN or by using 'Group Manager' to define a group of switches on which Data Collection can be run in one action.

What is collected
'Data Collection' creates a zip file on the ECFM/DCFM client containing a number of directories:-

The most interesting is 'Service' containing:-
AuditLog...txt Audit of administration changes.
EventLog...txt Switch events.
HardwareLog...txt Hardware replacement log.
LinLog...txt Link events on ports.
ProductInfo...txt Switch information, configuration, port states, nameserver and zone info.

Recent switch FW and EFCM/DCFM versions additionaly contain:-
PortStatistics..txt Port error and statistics at time of collection
OpenTrunkingLog..txt Trunking events.
SwitchFabricLog..txt Frabric changes, RSCNs etc.
EmbeddedPortLog..txt Log of traffic to/from 'embedded' ports on switch (FFFFFn)

Alternatively, obtain and execute explorer version 4.2.1 or above to get a subset of the above information.
eg, explorer -w sanextended
see 'man -M <-explorer_install_dir->/man explorer' for more details.

What is collected
show_eventlog.out show_port_info.out
show_features.out show_port_status.out
show_frus.out show_port_technology.out
show_ip_ethernet.out show_security_portbinding.out
show_loginserver.out show_switch.out
show_nameServer.out show_system.out
show_port_config.out show_zoning.out

Step 3: Obtaining port error statistics
Obtaining multiple port error statistics may help eliminate marginal link components. It is valuable to collect port error counters before and after problem observation and checking the deltas on these values , that is have the error counters increased during the time that the problem was in existance.

Port error statistics are collected with a Data Collection.

Note: Unlike most other switch vendors, the port error stats tend not to 'spin' when an attached node is rebooted. In this respect a single reading is of some use.

Switch overview.

Name Max Port Count Management method
6064 64 DCFM/EFCM/EFCM Basic (was called Sanpilot,Browser)/telnet
6140 140 DCFM/EFCM/EFCM Basic/telnet
i10K 256 DCFM/EFCM/telnet
4700 32 DCFM/EFCM/EFCM Basic/telnet
4500 24 DCFM/EFCM/EFCM Basic/telnet
4400 16 DCFM/EFCM/EFCM Basic/telnet
4300 12 DCFM/EFCM Basic/telnet

DCFM and ECFM are Java aplications (GUIs). There is a server and client installation for Solaris
and Windows.

EFCM Basic (SANpilot) is http port 80 on the switch IP address.

Default user is 'Administrator' , default password is 'password'

EFCM Basic and telnet access can be turned off/on via ECFM where applicable.

Updated 25/5/2004 to include explorer module in SUNWexplo version 4.2.1

Updated 19/06/2006 to include recent additional log files , statis gathering and general format improvements.

This solution has no attachment