Loop Monitoring; About Loop Monitoring - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Loop Monitoring

S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
o rx_id
o els
o swils
o fcp_cmd
o fcp_data (FCP data frames only)
o fcp_rsp
o class_f
o bad_fc
o els_cmd
o swils_cmd
o fcp_lun
o fcp_task_mgmt
o fcp_scsi_cmd
o fcp_status
o gs_type
o gs_subtype
o gs_cmd
o gs_reason
o gs_reason_expl
o dns
o udns (unzoned name server)
o fcs
o zs
o fc
o els
o swils (use as swils[x:y] similar to fc)
o fcp
o fcct (use as fcct[x:y] similar to fc)
Loop Monitoring
This section includes the following topics:
•
•
•

About Loop Monitoring

By default, loop monitoring is disabled in all switches in the Cisco MDS 9000 Family. When a disk is
removed from a loop port, the loop stays active based on the bypass circuit. Thus the disk removal is not
known until you try to communicate with the disk. To detect such removals, the disks can be polled
periodically (every 20 seconds).
Caution Changes to the loop monitoring feature should be made by an administrator or individual who is
completely familiar with switch operations.
Cisco MDS 9000 Family CLI Configuration Guide
58-14
(FCP Command frames only)
(FCP response frames only)
(Generic Services type)
(Generic Services subtype)
(name server)
(fabric configuration server)
(zone server)
(use as fc[x:y] where x is offset and y is length to compare)
(use as els[x:y] similar to fc)
(use as fcp[x:y] similar to fc)
About Loop Monitoring, page 58-14
Enabling Loop Monitoring, page 58-15
Verifying Loop Monitoring Configuration, page 58-15
Chapter 58 Troubleshooting Your Fabric
OL-18084-01, Cisco MDS NX-OS Release 4.x