The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Nokia Siemens Networks (NSN) Microwave 1+1 Hot Standby (HSBY) protocol is a link-protection protocol that extends connectivity fault management (CFM) continuity check messages (CCMs) to enable 1:1 link redundancy in microwave devices. NSN Microwave 1+1 HSBY provides link-protection support for both indoor units (IDUs) and outdoor units (ODUs).
This document describes the extensions to the IEEE 802.1ag CFM component in Cisco IOS software that enable the detection and handling of microwave outdoor unit hardware failures.
To enable link-protection on a maintenance endpoint (MEP), the connectivity fault management (CFM) domain and MEP must adhere to the Nokia Siemens Networks (NSN) configuration requirements.
CFM CCMs are heartbeat messages exchanged periodically between maintenance association endpoints (MEPs). CCMs allow MEPs to discover each other within a maintenance association, and allow maintenance association intermediate points (MIPs) to discover MEPs. CCMs provide a means for detecting connectivity failures in a maintenance domain. CCMs are transmitted frequently enough so that consecutive messages can be lost without causing the information to time out in any of the receiving MEPs.
For detailed information about CFM, MEPs, MIPs, and maintenance associations, see "Configuring IEEE Standard-Compliant Ethernet CFM in a Service Provider Network".
The NSN Microwave 1+1 HSBY Protocol has specified a proprietary time-to-live (TLV) field in CCMs for monitoring active and standby ODUs, and a flag to temporarily suspend CCM monitoring. Identified by an Organizational Unique Identifier (OUI) value of 0x000FBB, the TLV is attached to CCMs as an organization-specific TLV.
An IDU or an ODU may need to temporarily halt transmitting traffic, including CCMs, in circumstances such as a software upgrade or a reload. An IDU or ODUs can set the Suspend CC Monitor flag to signal a temporary pause in CFM traffic if a suspension is needed. Using this flag prevents the other two devices from triggering an unnecessary link-protection action. The Suspend CC Monitor time interval field, in conjunction with the flag, indicates the maximum amount of time the two devices must wait before expecting CCMs to resume from the suspended device.
The NSN Microwave 1+1 HSBY protocol monitors three maintenance associations. One maintenance association is at Ethernet CFM level 4 and is called the ODU-to-ODU CCM (P-CCM) session, and two maintenance associations are at Ethernet CFM level 0 and are called the IDU-to-ODU CCM (E-CCM) sessions. The IDU is associated with only the two E-CCM sessions and has an outward-facing MEP configured in each session. The IDU is required to pass CFM traffic between the ODUs only in the P-CCM session; no additional monitoring of this maintenance association is needed.
The HSBY configuration shown in the figure below supports four separate traffic flows:
CFM traffic between the IDU and ODU 1.
CFM traffic between the IDU and ODU 2.
CFM traffic between ODU 1 and ODU 2. This traffic passes through the IDU.
Data traffic between the WAN and ODU 1. This traffic passes through the IDU.
The NSN Microwave 1+1 HSBY link-protection function within the scope of CFM CCM extensions is provided through configuration of a single IDU connected to two ODUs for redundancy. The Cisco IOS device acts as the IDU. At a given time only one ODU is actively handling data traffic, but both the active and standby ODUs are processing and transmitting CFM traffic. The CFM traffic is composed of CCMs with NSN proprietary TLV fields that extend the CCMs’ detection of connectivity failures to IDUs and ODUs. Additionally, these extended CCMs passed between the IDU and ODUs are used to indicate which ODU is active and handling the data traffic. If a failure occurs, the standby ODU assumes the role of the active ODU. The figure below shows a sample physical topology.
The HSBY Protocol specifies that some IDU parameters are configurable and others are fixed values. The table below summarizes the permitted values for an IDU using the HSBY Protocol.
 Note |
The same maintenance association (MA) VLAN ID (MA VLAN-ID) can be used for all MAs configured on an IDU. |
|
Parameter |
Default Value |
Permitted Values |
|---|---|---|
|
CC Interval |
100 milliseconds (ms) |
10ms, 100ms, and 1000ms |
|
Domain Level |
0 |
Fixed |
|
Domain Name |
Null |
Fixed |
|
MA VLAN-ID (E-CCM) |
None |
1-15 |
|
MPID |
1 |
Fixed |
|
Short MA Name |
None |
0-65535 |
|
Suspend Interval |
160 seconds |
80s, 160s, 240s, and 320s |
The HSBY Protocol specifies that some ODU parameters are configurable and others are fixed values. The table below summarizes the permitted values for an ODU using the HSBY Protocol.
Note |
By default, an ODU learns the short MA name when it receives the first E-CCM from an IDU. |
|
Parameter |
Default Value |
Permitted Values |
|---|---|---|
|
MA VLAN-ID (E-CCM) |
None |
16-50 |
|
MPID |
2 |
Fixed |
|
Short MA Name |
Learned |
0-65535 |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ethernet cfm global Example: |
Enables Ethernet CFM globally. |
| Step 4 |
link-protection enable Example: |
Enables link protection globally on the router. |
| Step 5 |
link-protection group management vlan vlan-id Example: |
Defines the management VLAN used for link protection.
|
| Step 6 |
link-protection group group-number pccm vlan vlan-id Example: |
Specifies an ODU-to-ODU continuity check message (P-CCM) VLAN. |
| Step 7 |
ethernet cfm domain domain-name level level-id [direction outward ] Example: |
Configures the CFM domain for ODU 1 and enters Ethernet CFM configuration mode. |
| Step 8 |
id {mac-address domain-number | dns dns-name | null } Example: |
Configures a maintenance domain identifier (MDID). |
| Step 9 |
service {ma-name | ma-num | vlan-id vlan-id | vpn-id vpn-id } [port | vlan vlan-id [direction down ]] Example: |
Defines a maintenance association for ODU 1 and enters Ethernet CFM service instance configuration mode. |
| Step 10 |
continuity-check [interval time | loss-threshold threshold | static rmep ] Example: |
Enables transmission of continuity check messages (CCMs) within the ODU 1 maintenance association and defines a continuity-check interval. |
| Step 11 |
exit Example: |
Exits Ethernet CFM service instance configuration mode. |
| Step 12 |
exit Example: |
Exits Ethernet CFM configuration mode. |
| Step 13 |
ethernet cfm domain domain-name level level-id [direction outward ] Example: |
Configures the CFM domain for ODU 2 and enters CFM configuration mode. |
| Step 14 |
id {mac-address domain-number | dns dns-name | null } Example: |
Configures a maintenance domain identifier (MDID). |
| Step 15 |
service {ma-name | ma-num | vlan-id vlan-id | vpn-id vpn-id } [port | vlan vlan-id [direction down ]] Example: |
Defines a maintenance association for ODU 2 and enters Ethernet CFM service configuration mode. |
| Step 16 |
continuity-check [interval time | loss-threshold threshold | static rmep ] Example: |
Enables transmission of CCMs within the ODU 2 maintenance association and defines a continuity-check interval. |
| Step 17 |
exit Example: |
Exits Ethernet CFM service instance configuration mode. |
| Step 18 |
exit Example: |
Exits Ethernet CFM configuration mode. |
| Step 19 |
interface type slot / port Example: |
Configures the interface to be connected to ODU 1 and enters interface configuration mode. |
| Step 20 |
spanning-tree portfast {disable | trunk } Example: |
Enables PortFast on the interface when it is in trunk mode. |
| Step 21 |
cfm mep domain domain-name mpid mpid {port | vlan vlan-id } Example: |
Configures a CFM MEP domain for ODU 1. |
| Step 22 |
link-protection group group-number Example: |
Configures a link-protection group for ODU 2. |
| Step 23 |
exit Example: |
Exits interface configuration mode. |
| Step 24 |
interface type slot / port Example: |
Configures the interface to be connected to ODU 2 and enters interface configuration mode. |
| Step 25 |
spanning-tree portfast {disable | trunk } Example: |
Enables PortFast on the interface when it is in trunk mode. |
| Step 26 |
cfm mep domain domain-name mpid mpid {port | vlan vlan-id } Example: |
Configures a CFM MEP domain for ODU 2. |
| Step 27 |
link-protection group group-number Example: |
Configures a link-protection group for ODU 2. |
| Step 28 |
end Example: |
Returns the CLI to privileged EXEC mode. |
| Step 29 |
show ethernet cfm maintenance-points remote detail Example: |
(Optional) Displays remote maintenance endpoints in the continuity check database. |
This example is a sample CFM domain and MEP configuration that follows the NSN requirements for monitoring ODUs. The link-protection command for configuring NSN-specific parameters is included. CFM configuration parameters for an IDU are shown within angle brackets (<>):
link-protection suspend-interval <80s, 160s, 240s, 320s>
link-protection management vlan <51-4094>
link-protection pccm vlan <16-50>
!
ethernet cfm ieee
ethernet cfm global
!
ethernet cfm domain <Domain for ODU1> level 0
id null
service number <number> vlan <1-15> direction down
continuity-check
continuity-check interval <10, 100, 1000ms>
!
ethernet cfm domain <Domain for ODU2> level 0
id null
service number <number> vlan <1-15> direction down
continuity-check
continuity-check interval <10, 100, 1000ms>
!
interface GigabitEthernet 0/3
ethernet cfm mep domain <Domain for ODU1> mpid 1 vlan <1-15>
link-protection group <group #>
!
interface GigabitEthernet 0/4
ethernet cfm mep domain <Domain for ODU2> mpid 1 vlan <1-15>
link-protection group <group #>
!
The following example shows a 1+1 HSBY protocol configuration on the Cisco 7600 series router:
Router> enable
Router# configure terminal
Router(config)# ethernet cfm global
Router(config)# link-protection enable
Router(config)# link-protection group management vlan 51
Router(config)# link-protection group 2 pccm vlan 16
Router(config)# ethernet cfm domain eccm1 level 0
Router(config-ecfm)# id null
Router(config-ecfm)# service 1 vlan 14 direction down
Router(config-ecfm-srv)# mep mpid 1
Router(config-ecfm-srv)# mep mpid 2
Router(config-ecfm-srv)# continuity-check interval 100ms
Router(config-ecfm-srv)# exit
Router(config-ecfm)# exit
Router(config)# ethernet cfm domain eccm2 level 0
Router(config-ecfm)# id null
Router(config-ecfm)# service 2 vlan 15 direction down
Router(config-ecfm-srv)# mep mpid 1
Router(config-ecfm-srv)# mep mpid 2
Router(config-ecfm-srv)# continuity-check interval 100ms
Router(config-ecfm-srv)# exit
Router(config-ecfm)# exit
Router(config)# interface gigabitethernet 1/1
Router(config-if)# switchport mode trunk
Router(config-if)# spanning-tree portfast trunk
Router(config-if)# ethernet cfm mep domain eccm1 mpid 1 vlan 14
Router(config-if)# link-protection group 1
Router(config-if)# exit
Router(config)# interface GigabitEthernet 3/2
Router(config-if)# switchport mode trunk
Router(config-if)# spanning-tree portfast trunk
Router(config-if)# ethernet cfm mep domain eccm2 mpid 1 vlan 15
Router(config-if)# link-protection group 1
Router(config-if)# end
Router# show ethernet cfm maintenance-points remote detail
|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands: master list of commands with complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
|
|
Carrier Ethernet commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
Cisco IOS Carrier Ethernet Command Reference |
|
Configuring IEEE Standard-Compliant Ethernet CFM |
"Configuring IEEE Standard-Compliant Ethernet CFM in a Service Provider Network" |
|
Configurations for Carrier Ethernet networks |
Carrier Ethernet Configuration Guide, Cisco IOS Release 15.1S |
|
Understanding and configuring Microwave 1+1 HSBY on the Cisco MWR 2941 Mobile Wireless Edge Router |
“Configuring Ethernet Link Operations, Administration, and Maintenance” chapter of the Cisco MWR 2941 Mobile Wireless Edge Router Software Configuration Guide, Release 15.0(1)MR |
|
Standard |
Title |
|---|---|
|
IEEE 802.1ag |
Connectivity Fault Management |
|
MIB |
MIBs Link |
|---|---|
|
None |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
|
RFC |
Title |
|---|---|
|
None |
-- |
|
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 Name |
Releases |
Feature Information |
|---|---|---|
|
CFM Extension for 1+1 Hot-Standby Support |
Cisco IOS XE Release 3.9S |
The NSN Microwave 1+1 HSBY protocol is a link-protection protocol that extends CFM CCMs to enable 1:1 link redundancy in microwave devices. NSN Microwave 1+1 HSBY provides link-protection support for both IDUs and ODUs. In Cisco IOS XE Release 3.9S, support was added for the Cisco ASR 903 Router. The following command was introduced or modified: show ethernet cfm maintenance-points remote detail . |
Feedback