Portguard; Port Level Portguard - Cisco MDS 9000 Series Configuration Manual
Interface
Hide thumbs
Also See for MDS 9000 Series:
- Command reference manual (1464 pages) ,
- Configuration manual (344 pages) ,
- Troubleshooting manual (161 pages)
Table of Contents
Configuring Interfaces
CWDM-1550
CWDM-1570
CWDM-1590
CWDM-1610
Portguard
The Portguard feature is intended for use in environments where systems do not adapt quickly to a port going
down and up (single or multiple times). For example, if a large fabric takes 5 seconds to stabilize after a port
goes down, but the port actually goes up and down once per second, a severe failure might occur in the fabric,
including devices becoming permanently unsynchronized.
The Portguard feature provides the SAN administrator with the ability to prevent this issue from occurring.
A port can be configured to stay down after a specified number of failures in a specified time period. This
allows the SAN administrator to automate fabric stabilization, thereby avoiding problems caused by the
up-down cycle.
Using the Portguard feature, the SAN administrator can restrict the number of error events and bring a
malfunctioning port to down state dynamically once the error events exceed the event threshold. A port can
be configured such that it shuts down when specific failures occur.
There are two types of portguard, Port Level type and Port Monitor type. While the former is a basic type
where event thresholds are configurable on a per port basis, the latter allows the configuration of policies that
are applied to all the ports of the same type, for example, all E ports or all F ports.
Note
We recommend against the simultaneous use of both types of portguard for a given port.
Port Level Portguard
The following is the list of events that can be used to trigger port-level portguard actions:
• TrustSec violation—Link fails because of excessive TrsustSec violation events.
• Bit errors—Link fails because of excessive bit error events.
• Signal loss—Link fails because of excessive signal loss events.
• Signal synchronization loss—Link fails because of excessive signal synchronization events.
• Link reset—Link fails because of excessive link reset events.
• Link down—Link fails because of excessive link down events.
• Credit loss (Loop F ports only)—Link fails because of excessive credit loss events.
A link failure occurs when it receives two bad frames in an interval of 10 seconds and the respective interface
will be error disabled. A general link failure caused by link down is the superset of all other causes. The sum
of the number of all other causes equals the number of link down failures. This means that a port is brought
to down state when it reaches the maximum number of allowed link failures or the maximum number of
specified causes.
Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x
Portguard
c1550
c1570
c1590
c1610
27
- Quick Links:
- E Port
- Configuring Isl between Two Switches
Hide quick links:
Table of Contents
