- Using Ethernet Operations Administration and Maintenance
- Configuring IEEE Standard-Compliant Ethernet CFM in a Service Provider Network
- Configuring ITU-T Y.1731 Fault Management Functions in IEEE CFM
- CFM CCM Extensions to Support the NSN Microwave 1+1 Hot Standby Protocol
- IEEE-Compliant CFM MIB
- Configuring Ethernet Connectivity Fault Management in a Service Provider Network
- Ethernet Performance Monitoring on Untagged EFPs
- Syslog Support for Ethernet Connectivity Fault Management
- Dynamic Ethernet Service Activation
- Layer 2 Access Control Lists on EVCs
- Static MAC Address Support on Service Instances and Pseudowires
- IEEE 802.1s on Bridge Domains
- IEEE 802.1ah on Provider Backbone Bridges
- Enabling Ethernet Local Management Interface
- Configuring Remote Port Shutdown
- Configuring Ethernet Local Management Interface at a Provider Edge
- Configuring IEEE 802.3ad Link Bundling and Load Balancing
- Multichassis LACP
- ICCP Multichassis VLAN Redundancy
- ITU-T G.8032 Ethernet Ring Protection Switching
- Configuring IP SLAs Metro-Ethernet 3.0 (ITU-T Y.1731) Operations
- IPSLA Y1731 On-Demand and Concurrent Operations
Contents
- Configuring Remote Port Shutdown
- Finding Feature Information
- Prerequisites for Configuring Remote Port Shutdown
- Restrictions for Configuring Remote Port Shutdown
- Information About Configuring Remote Port Shutdown
- Ethernet Virtual Circuit
- Ethernet LMI
- OAM Manager
- Benefits of Remote Port Shutdown
- How to Configure Remote Port Shutdown
- Specifying LDP as an OAM Protocol
- Configuration Examples for Remote Port Shutdown
- Example Specifying LDP As the OAM Protocol and Associating a Service Instance to an EVC
- Example Configuring Xconnect Directly on an Interface
- Additional References
- Feature Information for Configuring Remote Port Shutdown
Configuring Remote Port Shutdown
The Remote Port Shutdown feature uses Ethernet Local Management Interface (LMI) in an Ethernet over Multiprotocol Label Switching (EoMPLS) network to propagate remote link status to a customer edge (CE) device.
- Finding Feature Information
- Prerequisites for Configuring Remote Port Shutdown
- Restrictions for Configuring Remote Port Shutdown
- Information About Configuring Remote Port Shutdown
- How to Configure Remote Port Shutdown
- Configuration Examples for Remote Port Shutdown
- Additional References
- Feature Information for Configuring Remote Port Shutdown
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Configuring Remote Port Shutdown
Ethernet LMI must be enabled for the Remote Port Shutdown feature to function.
Restrictions for Configuring Remote Port Shutdown
Connectivity Fault Management and Lightweight Directory Protocol (LDP) cannot be configured at the same time.
Information About Configuring Remote Port Shutdown
Ethernet Virtual Circuit
An Ethernet virtual circuit (EVC) as defined by the Metro Ethernet Forum is a port level point-to-point or multipoint-to-multipoint Layer 2 circuit. EVC status can be used by a CE device to find an alternative path into the service provider network or in some cases, fall back to a backup path over Ethernet or over another alternative service such as Frame Relay or ATM.
Ethernet LMI
Ethernet LMI is an Ethernet Operations, Administration, and Maintenance (OAM) protocol between a CE device and a Provider Edge (PE) device. Ethernet LMI provides information that enables autoconfiguration of CE devices and provides the status of EVCs for large Ethernet metropolitan area networks (MANs) and WANs. Specifically, Ethernet LMI runs only on the PE-CE user network interface (UNI) link and notifies a CE device of both the operating state of an EVC and the time when an EVC is added or deleted. Ethernet LMI also communicates the attributes of an EVC.
Ethernet LMI interoperates with Ethernet Connectivity Fault Management (CFM) and LDP. In this case Ethernet LMI relies on the OAM manager to interwork with LDP to report remote link status to the local CE.
OAM Manager
The OAM manager is an infrastructure element that streamlines interaction between OAM protocols. The OAM manager requires two interworking OAM protocols, in this case Ethernet LMI and MPLS LDP.
No interactions are required between Ethernet LMI and the OAM manager on the CE side. On the user-facing provider edge (UPE) side, the OAM manager defines an abstraction layer that relays data collected from Ethernet CFM to the Ethernet LMI device.
Ethernet LMI and OAM manager interaction is unidirectional, from the OAM manager to Ethernet LMI on the UPE side of the device. An information exchange results from an Ethernet LMI request or is triggered by the OAM manager when the OAM manager receives notification from the OAM protocol that the EVC status has changed. In this case, the change is called a remote link status change.
Benefits of Remote Port Shutdown
The Remote Port Shutdown feature provides direct interaction of Ethernet LMI with MPLS, LDP, and OAM. When CFM/802.1ag is not running in a network, Remote Port Shutdown enables communication of link status to a CE, and traffic from the CE can be stopped if MPLS or the pseudowire is down. The figure below shows an EoMPLS network with the remote link down.
How to Configure Remote Port Shutdown
Specifying LDP as an OAM Protocol
Perform this task to specify LDP as an OAM protocol.
1.
enable
2.
configure
terminal
3.
ethernet
evc
evc-id
4.
oam
protocol
{cfm svlan svlan-id domain domain-name| ldp}
5.
end
DETAILED STEPS
Configuration Examples for Remote Port Shutdown
- Example Specifying LDP As the OAM Protocol and Associating a Service Instance to an EVC
- Example Configuring Xconnect Directly on an Interface
Example Specifying LDP As the OAM Protocol and Associating a Service Instance to an EVC
In this example, the OAM protocol for EVC pw_evc is specified as LDP, and service instance 1 is associated with the EVC.
Router(config)# ethernet evc pw_evc Router(config-evc)# oam protocol ldp Router(config-evc)# uni count 2 Router(config-evc)# exit Router(config)# pseudowire-class vlan-xconnect Router(config-pw-class)# encapsulation mpls Router(config-pw-class)# interworking Router(config-pw-class)# exit Router(config)# interface ethernet 0/0 Router(config-if)# ethernet lmi interface Router(config-if)# ethernet uni id ce1 Router(config-if)# service instance 1 ethernet pw_evc Router(config-if-srv)# encapsulation dot1q 2 Router(config-if-srv)# xconnect10.2.2.2 123 pw-class vlan-xconnect Router(config_if-srv)# exit
Example Configuring Xconnect Directly on an Interface
In this example, Xconnect is configured directly on an interface.
Router(config)# interface ethernet 0/0 Router(config-if)# xconnect 2.2.2.2 123 pw-class vlan-xconnect Router(config-if)# ethernet lmi interface Router(config-if)# ethernet uni id ce1 Router(config-if)# service instance 1 ethernet pw_evc Router(config-if-srv)# encapsulation dot1q 2 Router(config_if-srv)# exit
Additional References
Related Documents
|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands: master list of commands with complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
|
|
Cisco IOS Carrier Ethernet commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
Cisco IOS Carrier Ethernet Command Reference |
Standards
|
Standard |
Title |
|---|---|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
|
MIB |
MIBs Link |
|---|---|
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
|
RFC |
Title |
|---|---|
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
-- |
Technical Assistance
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Configuring Remote Port Shutdown
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Remote Port Shutdown |
12.2(33)SRB |
The Remote Port Shutdown feature uses Ethernet LMI in an EoMPLS network to propagate remote link status to a CE device. In Release 12.2(33)SRB, this feature was implemented on the Cisco 7600 router. The following commands were introduced or modified: oam protocol. |