Table Of Contents
Implementing MPLS Optical User Network Interface Protocol on Cisco IOS XR Software
Prerequisites for Implementing MPLS O-UNI
Information About Implementing MPLS O-UNI
How to Implement MPLS O-UNI on Cisco IOS XR Software
Setting Up an MPLS O-UNI Connection
Tearing Down an MPLS O-UNI Connection
Verifying MPLS O-UNI Configuration
Configuration Examples for MPLS O-UNI
MPLS O-UNI Neighbor and Data Link Configuration: Examples
O-UNI-N Neighbor Configuration
O-UNI Connection Establishment: Example
O-UNI Connection Configuration at Active Side
O-UNI Connection Configuration at Passive Side
O-UNI Connection Tear-Down: Example
O-UNI Connection Deletion at Active Side
O-UNI Connection Deletion at Passive Side
Implementing MPLS Optical User Network Interface Protocol on Cisco IOS XR Software
The Optical User Network Interface (O-UNI) is specified by the Optical Internetworking Forum (OIF). The O-UNI standard specifies a means by which client devices, such as routers, Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Add Drop Multiplexers (ADMs), and other devices with SONET/SDH interfaces may request optical layer connectivity services of an optical transport network (OTN). Such services include the establishment of connections between two client devices, the deletion of connections, and the query of connection status.
![]()
Note
The term MPLS O-UNI is often used instead of O-UNI, as it emphasizes that the OIF's O-UNI is based upon many MPLS standards developed by the Internet Engineering Task Force (IETF).
Feature History for Implementing MPLS O-UNI on Cisco IOS XR Software
Contents
•
Prerequisites for Implementing MPLS O-UNI
•
Information About Implementing MPLS O-UNI
•
How to Implement MPLS O-UNI on Cisco IOS XR Software
•
Configuration Examples for MPLS O-UNI
Prerequisites for Implementing MPLS O-UNI
The following prerequisites are required to implement MPLS O-UNI:
•
You must be in a user group associated with a task group that includes the proper task IDs for MPLS O-UNI commands.
•
A router that runs Cisco IOS XR software.
•
Installation of the Cisco IOS XR software mini-image on the router.
•
Installation of the Cisco IOS XR MPLS software package on the router.
Information About Implementing MPLS O-UNI
O-UNI offers the ability to establish OIF standards-based connections through a SONET/SDH-based heterogeneous optical network. These connections can be made across optical transport networks (OTNs) composed of Cisco equipment or third-party vendor equipment.
An OTN provides transport services to interconnect the optical interfaces of O-UNI client devices, such as IP routers and SONET ADMs. In Figure 14, two routers running Cisco IOS XR software with O-UNI client (O-UNI-C) support are connected to SONET/SDH cross-connects, which provide O-UNI Network (O-UNI-N) services. These cross-connects sit at the edge of the OTN, and O-UNI client devices may request services from them. The client devices have no knowledge of the OTN structure, and all services are invoked at the edge of the OTN. These services include connection establishment, deletion, and query for a given data link, where a data link corresponds to a unique SONET/SDH interface on an O-UNI-C device.
To complete a connection request, an O-UNI-N node needs a database to determine its route within the OTN. The algorithms used to determine the connection path, although not standardized in the OIF's O-UNI 1.0 standard, must consider the connection characteristics requested by the O-UNI-C device, including connection bandwidth, framing type, cyclic redundancy check (CRC) type, and scrambling.
Routers request O-UNI services using the following RSVP messages:
•
path
•
reservation
•
reservation confirmation
•
path error
•
path tear
•
reservation tear
•
refresh
These RSVP messages are transported over IP Control Channels (IPCC) between the router and the O-UNI-N device. The IPCCs rely on IP connectivity between O-UNI-C and O-UNI-N devices, represented in dotted lines in Figure 14. When services from the OTN are requested, the following parameters are included in the RSVP messages transmitted:
•
A unique data link identifier
•
Bandwidth requested
•
Framing type requested (that is, SONET or SDH)
•
CRC 16 or 32
•
Scrambling type
•
IP address of the node to receive the request
A unique identifier exists for every interface participating in an O-UNI connection. This identifier consists of a TNA and an interface ID. The TNA addresses are unique within the OTN, and represent the address of one or more data links between an O-UNI-N device and an O-UNI-C device. Cisco IOS XR software supports the use of IPv4 TNA addresses.
The interface ID is used to uniquely identify a given data link interface connected between an O-UNI-N device and an O-UNI-C device. The interface ID is a 32-bit value with local significance, generated by the device on which an interface resides; for example, a POS interface on a router connected to an O-UNI-N device would have an interface ID generated by the router and is only unique on this router. To avoid reconfiguration of LMP information, it is important that the interface ID values are persistent across control plane restarts and router reloads.
To establish an O-UNI connection, the messaging exchanges must include data link information from other devices. This information is provisioned using a static version of the LMP. The LMP commands allow the provisioning of the following capabilities:
•
The TNA associated with the data link. This value is assigned by the operator of the OTN.
•
The interface ID of the neighboring device. In Figure 14, this is the interface ID on the SONET/SDH cross-connect referred to as the remote interface ID.
•
The node ID of the data link adjacent device. In Figure 14, this is the IPv4 address used to send RSVP messages to a directly attached SONET/SDH cross-connect.
Local information is configured to enable the establishment of O-UNI connections. This information includes:
•
The router ID used as the source IPv4 address for RSVP messaging. This value is also configured on neighbor devices. Note that the terms node ID and router ID are often used synonymously. Node ID represents the generic term, while router ID refers to the node ID of a router.
•
The TNA of the data link on which to terminate the connection.
•
The operational mode of the interface that participates in an O-UNI connection. This interface can be configured to only terminate a connection or to initiate a connection.
Figure 14 O-UNI Network
![]()
How to Implement MPLS O-UNI on Cisco IOS XR Software
O-UNI requires setting up data links with neighbor nodes and establishing Internet Protocol Control Channel (IPCC) channels to setup O-UNI connections.
If IP connectivity is established over the RP management port and a standby RP card is present, the following conditions ensure NSF in case of RP failover:
•
Standby management port is not shutdown and operational up.
•
Standby management port has an IP address assigned to it.
•
Proxy-ARP is not enabled (proxy-ARP is disabled by default).
•
Active and standby ports have the same IP subnet configured.
•
An IP virtual address with the same subnet as the active and standby ports is configured.
•
The virtual address above is used as next hop in any static routes configured on neighbor O-UNI-N nodes.
This section contains the following procedures:
•
Setting Up an MPLS O-UNI Connection (required)
•
Tearing Down an MPLS O-UNI Connection (required)
•
Verifying MPLS O-UNI Configuration (required)
•
Configuration Examples for MPLS O-UNI (optional)
Setting Up an MPLS O-UNI Connection
Perform this task to configure and set up an MPLS O-UNI connection.
Prerequisites
The following prerequisites are required to configure and set up an O-UNI connection:
•
To configure the data link parameters you must have a node ID for the neighboring node.
•
A stable node ID is required at both ends of the O-UNI data link to ensure the configuration is successful. If you do not assign a node ID (also known as a router ID), the system defaults to the configured global router ID.
SUMMARY STEPS
1.
configure
2.
snmp-server ifindex persist
3.
snmp-server interface type number ifindex persist
4.
mpls optical-uni
5.
router-id {ip-address | interface-id}
6.
lmp neighbor neighbor-name
7.
ipcc routed
8.
remote node-id ip-address
9.
exit
10.
interface type number
11.
lmp data-link adjacency
12.
neighbor neighbor-name
13.
remote interface-id interface-id
14.
tna ipv4 ip-address
15.
exit
16.
destination address ipv4 ip-address
or
passive17.
end
or
commit18.
show mpls optical-uni
DETAILED STEPS
Tearing Down an MPLS O-UNI Connection
Perform this task to tear down an existing MPLS O-UNI connection.
SUMMARY STEPS
1.
configure
2.
mpls optical-uni
3.
interface type number
4.
no destination address ipv4 ip-address
or
no passive5.
end
or
commit6.
show mpls optical-uni
DETAILED STEPS
Verifying MPLS O-UNI Configuration
Verify the configuration of the MPLS O-UNI connection by running the show commands in this section.
SUMMARY STEPS
1.
show mpls optical-uni lmp neighbor
2.
show mpls optical-uni lmp
3.
show mpls optical uni lmp ipcc
4.
show mpls lmp clients
5.
show mpls optical-uni lmp interface type number
6.
show mpls optical-uni
7.
show mpls optical-uni interface type number
8.
show mpls optical-uni diagnostics interface type number
DETAILED STEPS
1.
Use the show mpls optical-uni lmp neighbor command to display LMP neighbor information, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uni lmp neighborLMP NeighborName: oxc-uni-n-source, IP: 10.56.57.58, Owner: Optical UNIIPCC ID: 1, State UpKnown via : ConfigurationType : RoutedDestination IP : 10.56.57.58Source IP : NoneData LinkI/F |LclDataLink ID|Link TNA Addr|Data Link LMP state--------------------------------------------------------------POS0/2/0/2 2 10.0.0.5 Up Allocated2.
Use the show mpls optical-uni lmp command to display LMP information, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uni lmpLocal OUNI CLI LMP Node ID: 10.56.57.58(Source: OUNI LMP CLI configuration, I/F: Loopback0)LMP NeighborName: oxc-uni-n-dest, IP: 10.12.13.14, Owner: Optical UNIIPCC ID: 2, State UpKnown via : ConfigurationType : RoutedDestination IP : 10.12.13.14Source IP : NoneData LinkI/F |LclDataLink ID|Link TNA Addr|Data Link LMP state--------------------------------------------------------------POS0/2/0/2 2 10.0.0.5 Up Allocated3.
Use the show mpls optical uni lmp ipcc command to display LMP IPCC information, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uni lmp ipccIPCCID | Type | IP | Status | Neighbor Name-------------------------------------------------------------1 Routed 10.56.57.58 Up oxc-uni-n-source4.
Use the show mpls lmp clients command to display information about MPLS LMP clients, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls lmp clientsCurrent time: Tue Nov 4 13:20:50 2003Total Number of Clients = 2Client | Job ID | Node |Uptime| Since--------------------------------------------------------------ucp_ouni 304 node0_0_0 5m45s Tue Nov 4 13:15:05 2003rsvp 261 node0_0_0 5m44s Tue Nov 4 13:15:06 20035.
Use the show mpls optical-uni lmp interface command to display LMP information for a specified interface, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uni lmp interface pos 0/2/0/2Interface: POS0/2/0/2Owner: Optical UNILocal data link ID type: UnnumberedLocal data link ID: Hex = 0x2, Dec = 2TNA address type: IPv4TNA address: 10.0.0.5Local TE link switching capability: Packet-Switch CapableRemote neighbor name: oxc-uni-n-sourceRemote neighbor node ID: 10.56.57.58Remote data link ID type: UnnumberedRemote data link ID: Dec = 2, Hex = 0x2Remote TE link switching capability: TDM Capable (TDM)Data link I/F state: UpData link LMP state: Up/AllocatedTE link LMP state: UpData link allocation status: AllocatedIPCC ID: 1IPCC type: RoutedIPCC destination IP address: 10.56.57.586.
Use the show mpls optical-uni command to display the state of O-UNI network connections, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uniIndex of abbreviations:----------------------M=O-UNI configuration Mode.P=PassiveAR =active/receiverAS=active/senderU=UnknownInterface TunID M ig State CCT Up Since------------------------------------------------------------POS0/2/0/2 000004 AS Connected 04/11/2003 13:16:187.
Use the show mpls optical-uni interface command to display detailed O-UNI information for a specific interface, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uni interface pos 0/2/0/2Interface POS0/2/0/2Configuration: Active->UserSignaling State: Connected since 04/11/2003 13:16:18TNA: 10.0.0.5Sender NodeID/Tunnel ID: 10.12.13.14/4Local Data Link ID: 2Remote Data Link ID: 2Local Switching Capability: PSC 1Remote Switching Capability: TDMPrimary IPCC: Interface: RoutedLocal IP Address: 10.0.0.0Remote IP Address: 10.56.57.588.
Use the show mpls optical-uni diagnostics interface command to display diagnostics information for an O-UNI connection on a specific interface, as shown in the following sample output:
RP/0/RP0/CPU0:router# show mpls optical-uni diagnostics interface pos 0/2/0/2Interface [POS0/2/0/2]Configuration: Active->UserSignaling State: [Connected] since 04/11/2003 13:16:18Connection to OLM/LMP established? YesOUNI to OLM/LMP DB sync. status: SynchronizedConnection to RSVP established? YesRSVP to OLM/LMP DB sync. status: SynchronizedThe neighbor [oxc-uni-n-source] has been configured, and has the node id [10.56.57.58]Found a route to the neighbor [oxc-uni-n-source]Remote switching capability is TDM.TNA [10.0.0.5] configured.All required configs have been entered.Global Code: No Error/ Success @ unknown timeDatalink Code: No Error/ Success @ unknown timeConfiguration Examples for MPLS O-UNI
This section provides the following configuration examples:
•
MPLS O-UNI Neighbor and Data Link Configuration: Examples
•
O-UNI Connection Establishment: Example
•
O-UNI Connection Tear-Down: Example
MPLS O-UNI Neighbor and Data Link Configuration: Examples
The following configuration examples are provided in this section:
•
O-UNI Router ID Configuration
•
O-UNI-N Neighbor Configuration
•
O-UNI Data Link Configuration
O-UNI Router ID Configuration
configurempls optical-unirouter-id Loopback 0commitO-UNI-N Neighbor Configuration
configureoptical-unilmp neighbor oxc-uni-n-sourceipcc routedremote node-id 10.56.57.58commitO-UNI Data Link Configuration
configurempls optical-uniinterface pos 0/2/0/2lmp data-link adjacencyneighbor oxc-uni-n-sourceinterface-id 2tna ipv4 10.0.0.5commitO-UNI Connection Establishment: Example
The following configuration examples are provided in this section:
•
O-UNI Connection Configuration at Active Side
•
O-UNI Connection Configuration at Passive Side
O-UNI Connection Configuration at Active Side
configurempls optical-uniinterface pos 0/2/0/2destination address ipv4 10.0.0.7commitO-UNI Connection Configuration at Passive Side
configurempls optical-uniinterface pos 0/2/0/2passivecommitO-UNI Connection Tear-Down: Example
The following configuration examples are shown in this section:
•
O-UNI Connection Deletion at Active Side
•
O-UNI Connection Deletion at Passive Side
O-UNI Connection Deletion at Active Side
configurempls optical-uniinterface pos 0/2/0/2no destination address ipv4 10.0.0.7commitO-UNI Connection Deletion at Passive Side
configurempls optical-uniinterface pos 0/2/0/2no passivecommitAdditional References
For additional information related to O-UNI, refer to the following references:
Related Documents
Standards
Standards 1 TitleOIF UNI 1.0
User Network Interface (UNI) 1.0 Signaling Specification
1 Not all supported standards are listed.
MIBs
MIBs MIBs Link—
To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
RFCs 1 TitleRFC 3471
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
RFC 3473
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
draft-ietf-ccamp-gmpls-sonet-sdh-xx.txt
Generalized Multi-Protocol Label Switching Extensions for SONET and SDH Control
LMP IETF draft
Link Management Protocol (LMP)
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-lmp-10.txt
draft-ietf-ccamp-gmpls-architecture-xx.txt
Generalized Multi-Protocol Label Switching Architecture
draft-ietf-ccamp-lmp-xx.txt
Link Management Protocol (LMP)
1 Not all supported RFCs are listed.
Technical Assistance