Brocade Communications Systems 8/40 Service Manual Page 30

  • Download
  • Add to my manuals
  • Print
  • Page
    / 46
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 29
BCSM IN A NUTSHELL 2008
© 2008 Brocade Communications Systems, Incorporated.
Page 28 of 44
VERIFYING DEVICE CONNECTIVITY
Use the cfgshow command on the edge fabrics to verify device connectivity:
NDA-T01-48K:admin> cfgshow
<Truncated Output>
Defined configuration:
zone: fabAzone b48_w2k; b48_disk1
zone: lsan_fabBB_fabA b48_disk1; b75_w2k
<Truncated Output>
The zoneshow command will give the same information in slightly different format
You may also use Fabric Manager, as long as you use the MetaSAN View
VERIFYING PROXY DEVICES
Display proxy devices with the fcrproxydevshow command:
NDA-T01-7500:admin> fcrproxydevshow
Proxy WWN Proxy Device Physical State
Created PID Exists PID
in Fabric in Fabric
----------------------------------------------------------------------------
10 10:00:00:00:c9:2b:4e:bc 01f001 100 010c00 Imported
100 22:00:00:04:cf:bd:56:53 02f001 10 0a0fe2 Imported
Total devices displayed: 2
Note: Besides using CLI commands to verify devices, ports, zones, proxies, etc., verification can be
achieved using SAN Health and Fabric Manager
M-SERIES ROUTERS
Monitoring an M-Series routed fabric requires the use of EFCM Standard. Under the Configuration Archive
dialogue box, you may choose to archive some files that will help in the event of a problem. You would
want to save copies of the event log and take a backup of the configuration, in the event something
happens that requires the information from a point in time.
To manage routing within an M-Series fabric consider these zoning caveats:
Only the active zone set is distributed to the switches in the fabric
Depending on the platform, membership is restricted either by zone set size or member count
Page view 29
1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 45 46

Comments to this Manuals

No comments