Activating A Port Monitor Policy - Cisco MDS 9000 Series Configuration Manual

Activating a Port Monitor Policy

• We recommend that you use the delta threshold type for all the counters except the tx-slowport-oper-delay
Note
counter which uses absolute threshold type.
• The rx-datarate and tx-datarate are calculated using the inoctets and outoctets on an interface.
• You must activate the err-pkt-from-port, err-pkt-from-xbar, and err-pkt-to-xbar counters using the
monitor counter name command, before specifying the counter parameters.
• Counters err-pkt-from-xbar, err-pkt-from-port, and err-pkt-to-xbar support delta threshold type only.
• Counter tx-slowport-oper-delay supports absolute threshold type only.
• Counter tx-slowport-oper-delay does not support portguard action.
• You must first enable ER_RDY flow-control mode using the system fc flow-control er_rdy command
and then enable congestion isolation using the feature congestion-isolation command before setting the
portguard action as congestion isolate (cong-isolate). For more information, see
Port-Monitor Portguard Action for Congestion Isolation, on page
• The cong-isolate port monitor portguard action is used only for configuring the credit-loss-reco,
tx-credit-not-available, tx-slowport-oper-delay, and txwait counters.
(Optional) Revert to the default values for a counter:
switch(config-port-monitor)# no counter {credit-loss-reco | err-pkt-from-port | err-pkt-from-xbar | err-pkt-to-xbar
| invalid-crc | invalid-words | link-loss | lr-rx | lr-tx | rx-datarate | signal-loss | state-change | sync-loss |
timeout-discards | tx-credit-not-available | tx-datarate | tx-discards | tx-slowport-oper-delay | txwait} poll-interval
seconds {absolute | delta} rising-threshold count1 event RMON-ID warning-threshold count2 falling-threshold
count3 event RMON-ID portguard {errordisable | flap | cong-isolate}
(Optional) Monitor a counter:
switch(config-port-monitor)# monitor counter {credit-loss-reco | err-pkt-from-port | err-pkt-from-xbar |
err-pkt-to-xbar | invalid-crc | invalid-words | link-loss | lr-rx | lr-tx | rx-datarate | signal-loss | state-change | sync-loss
| timeout-discards | tx-credit-not-available | tx-datarate | tx-discards | tx-slowport-oper-delay | txwait}
A port monitor currently recognizes two kinds of ports:
• Logical-type edge ports are normally F ports that are connected to end devices.
• Logical-type core ports are E ports (ISLs) or (T)F ports connected to Cisco NPV switches. Some of the edge port
counter thresholds and port-guard actions might not be appropriate on the TF ports in the port-monitor configurations.
Specifically, portguard disable, flap, and isolate actions can affect multiple end devices on the F ports. Therefore,
performing disable, flap, or isolate actions should be avoided on an N-Port Identifier Virtualization (NPIV) system.
Activating a Port Monitor Policy
To activate a port monitor policy, perform these steps:
Step 1
Enter configuration mode:
switch# configure terminal
Step 2 Activate the specified port monitor policy:
Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x
54
Configuring Interfaces
Configuring the
180.