Implementing GMPLS UNI The Generalized Multiprotocol Label Switching (GMPLS) User Network Interface (UNI) creates a circuit connection between two clients (UNI-C) of an optical network. This connection is achieved by signaling exchanges between UNI Client (UNI-C) and UNI Network (UNI-N) nodes, where UNI-C nodes are router nodes and UNI-N nodes are optical nodes. A GMPLS overlay model is required to connect packet routers with the optical network in these scenarios: • Different groups within a service provider are responsible for managing packet and optical networks. • The optical and packet network are managed by different service providers. • There is a weak trust model between the entities operating the optical and packet networks. Feature History for Implementing GMPLS UNI Modification Release This feature was introduced. Release 4.3.0 nLight enhancements were introduced. Release 6.0 • Prerequisites for Implementing GMPLS UNI, page 1 • Restrictions for Implementing GMPLS UNI, page 2 • Information About Implementing GMPLS UNI, page 2 • How to Implement GMPLS UNI, page 4 • Configuration Examples for GMPLS UNI, page 16 • Additional References, page 18 Prerequisites for Implementing GMPLS UNI The following prerequisites are required to implement GMPLS UNI: Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x 1
20
Embed
Implementing GMPLS UNI - cisco.com · •improvedIPavailabilitythroughpro-activeprotection. How to Implement GMPLS UNI AnewsubmodeisintroducedunderthemainTEsubmodetoenableGMPLSUNIandtocontainGMPLS
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Implementing GMPLS UNI
The Generalized Multiprotocol Label Switching (GMPLS) User Network Interface (UNI) creates a circuitconnection between two clients (UNI-C) of an optical network. This connection is achieved by signalingexchanges between UNI Client (UNI-C) and UNI Network (UNI-N) nodes, where UNI-C nodes are routernodes and UNI-N nodes are optical nodes.
A GMPLS overlay model is required to connect packet routers with the optical network in these scenarios:
• Different groups within a service provider are responsible for managing packet and optical networks.
• The optical and packet network are managed by different service providers.
• There is a weak trust model between the entities operating the optical and packet networks.
Feature History for Implementing GMPLS UNI
ModificationRelease
This feature was introduced.Release 4.3.0
nLight enhancements were introduced.Release 6.0
• Prerequisites for Implementing GMPLS UNI, page 1
• Restrictions for Implementing GMPLS UNI, page 2
• Information About Implementing GMPLS UNI, page 2
• How to Implement GMPLS UNI, page 4
• Configuration Examples for GMPLS UNI, page 16
• Additional References, page 18
Prerequisites for Implementing GMPLS UNIThe following prerequisites are required to implement GMPLS UNI:
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x 1
• Youmust be in a user group associated with a task group that includes the proper task IDs. The commandreference guides include the task IDs required for each command. If you suspect user group assignmentis preventing you from using a command, contact your AAA administrator for assistance.
• 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.
Restrictions for Implementing GMPLS UNI• The total number of configured GMPLS UNI controllers should not exceed the platform scale limit of500 GMPLS interfaces.
• Each UNI-N (ingress or egress) should be routable from its adjacent UNI-C. The UNI-C nodes need tobe routable from the UNI-N nodes too.
• GMPLSUNI is supported only over DWDMcontrollers and so, over POS andGigabitEthernet interfaces.
• GMPLS UNI is supported only with these Cisco ASR 9000 Enhanced Ethernet Line Cards:
◦A9K-MOD80-SE : 80G Modular Line Card, Service Edge Optimized
◦A9K-MOD80-TR : 80G Modular Line Card, Packet Transport Optimized
Information About Implementing GMPLS UNITo implement GMPLS UNI, you should understand these concepts:
GMPLS UNI vs GMPLS NNIIn case of GMPLS NNI, the optical network topology is known and path calculations are performed at theNNI head. In case of GMPLS UNI, the optical network topology is unknown to the UNI-C nodes and pathcalculations are performed by the UNI-N nodes.
GMPLS LSP SignalingThe GMPLS overlay model architecture is used for LSP signaling for GMPLS connections. In GMPLS UNI,UNI-C nodes send a request for a connection to UNI-N node. The connection request does not contain anend-to-end path. This is because, as mentioned previously, UNI-C nodes do not have knowledge of the topologyof the optical network and therefore cannot determine the end-to-end path. TheUNI-C node signals a connectionrequest without an ERO.
The LSP diversity is signalled on a GMPLS UNI tunnel with a path-option. A path-option is permitted on aGMPLS UNI tunnel with a "no ERO" and an optional "XRO" attribute sets to specify LSP diversityrequirements. If multiple LSP exclusions are configured in the attribute-set, they can be added to the pathmessage along with an appropriate LSP connection diversity sub-object.
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x2
Implementing GMPLS UNIRestrictions for Implementing GMPLS UNI
Path Message without an EROIn GMPLS UNI, UNI-C nodes send a request for a connection to UNI-N node. The connection request doesnot contain an end-to-end path, because, UNI-C nodes do not have knowledge of the topology of the opticalnetwork and therefore cannot determine the end-to-end path. The UNI-C node signals a connection requestwithout an ERO.
When no ERO is present in a received path message, the UNI-N node calculates a route to the destination andincludes that route in an ERO, before forwarding the path message. If no route is found, the UNI-N returns apath error message with an error code and subcode of 24,5 - "No route available toward destination".
The destination address of a GMPLS LSP can be either the optical router-id of the tail UNI-C node, or theoptical address of the ingress interface to the tail UNI-C node. Supplying the router-id allows the UNI-N toroute the tunnel to the tail UNI-C node via any attached UNI-N node; supplying the UNI-C's ingress interfaceaddress forces the tunnel's path to traverse the UNI-N node attached to that interface.
The optical router-ids and interface addresses may or may not be the same as the packet ones.Note
XRO Attribute-setAn optional XRO attribute-set can be specified as part of the path-option to specify LSP diversity requirements.An empty XRO attribute set results in the GMPLS tunnel being signaled with no exclusions, and thereforeno XRO.
A non-existent XRO attribute-set can be configured in the GMPLS UNI tunnel path-option; in this caseno attempt will be made to bring up the GMPLS tunnel until the configuration is complete.
Note
Connection DiversityConnection diversity is required to ensure that GMPLS tunnels can be established without sharing resources,thus, greatly reducing the probability of simultaneous connection failures. For example, an edge-node wishesto establish multiple LSPs towards the same destination edge-node, and these LSPs need to have few or noresources in common.
Connection diversity supports the establishment of a GMPLS LSP which is diverse from the path taken byan existing LSP. An XRO is added to the tunnel's path message with appropriate LSP diversity sub-objectsor exclusions. A maximum of 20 connection diversity exclusions per XRO is supported.
DWDM Transponder IntegrationAGMPLS UNI based solution preserves all the advantages of the integration of the DWDM transponder intothe router blade. These advantages include:
• improved CAPEX and OPEX models
• component, space and power savings
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x 3
• improved IP availability through pro-active protection.
How to Implement GMPLS UNIA new submode is introduced under the main TE submode to enable GMPLS UNI and to contain GMPLSUNI configuration.
To implement GMPLS UNI, follow these procedures:
Configuring TE for GMPLS UNITE configuration specific to packet tunnels does not affect GMPLS UNI tunnels.
To implement TE configuration for GMPLS UNI, follow these procedures:
Enabling GMPLS UNI SubmodePerform this task to enable GMPLS UNI configuration submode and to configure GMPLS UNI tunnels.
Removal of the GMPLS UNI submode results in the removal of all configuration within it, including anyother parser submode, and the immediate destruction of all GMPLS UNI tunnels.
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x4
Implementing GMPLS UNIHow to Implement GMPLS UNI
PurposeCommand or Action
RP/0/RSP0/CPU0:router(config-te-gmpls)#
commitStep 4
Configuring GMPLS UNI ControllerPerform this task to setup a GMPLS tail inMPLS-TE configuration. This task enables GMPLSUNI controllersubmode to configure controllers for establishing GMPLS UNI tunnels. This is the minimal configurationrequired at the tunnel tail.
Removal of the GMPLS UNI controller submode results in the immediate destruction of any GMPLStunnel established over the controller referenced.
Configuring GMPLS UNI Controller as a Tunnel HeadPerform this task to configure the tunnel properties for a GMPLS UNI controller.
This configuration designates the controller as a tunnel-head, rather than a tunnel tail. After the tunnel propertiesare configured, the incoming path messages are rejected and any existing tail-end tunnel is torn down.
An XRO attribute-set can be specified as partof the path-option, if required.
Note
commitStep 9
Configuring Other Tunnel Properties for a GMPLS UNI TunnelPerform this task to configure the optional tunnel properties for a GMPLS UNI tunnel. This configuration isoptional, and if omitted, the GMPLS tunnel is established with the default property values.
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x 7
Implementing GMPLS UNIConfiguring TE for GMPLS UNI
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x8
Implementing GMPLS UNIConfiguring TE for GMPLS UNI
PurposeCommand or Action
The setup-priority and hold-priority values arenumbers ranging from 0 to 7, where 0 represents thehighest priority. The hold-priority must be equal orhigher (numerically less) than the setup-priority.
Note
Enables record-route functionality for a GMPLS tunnel.record-route
If no signalled name is configured, TE will generatea default name in the form ofrouter-name_tunnel-id_destination-address, forexample, te-ma1_123_10.10.10.10.
Note
Configure events to generate system log messages when statechanges occur on the GMPLS tunnel. If omitted, no eventswill result in the generation of system log messages.
logging events lsp-status state
Example:
RP/0/RSP0/CPU0:router(config-te-gmpls-tun)#logging events lsp-status state
Step 9
commitStep 10
Configuring LSP DiversityTo configure an XRO attribute-set as part of the path-option for MPLS-TE, and to specify exclusions for anattribute set for LSP diversity, follow these procedures:
Configuring XRO Attribute-set
Perform this task to configure XRO attribute set in the GMPLS UNI tunnel path-option, under MPLS-TEsubmode.
Specifies a controller for GMPLS UNI.controller dwdm controller
Example:
RP/0/RSP0/CPU0:router(config-lmp-gmpls-uni)#
Step 4
controller dwdm 0/4/0/0
Specifies an LMP neighbor for GMPLS and entersLMPGMPLSUNI neighbor configuration submode.
neighbor name
Example:
RP/0/RSP0/CPU0:router(config-lmp-gmpls-uni-cntl)#
Step 5
neighbor nbr1
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x14
Implementing GMPLS UNIConfiguring LMP for GMPLS UNI
PurposeCommand or Action
Specifies the optical interface address for an LMPlink for a GMPLS UNI controller.
link-id ipv4 unicast address
Example:
RP/0/RSP0/CPU0:router(config-lmp-gmpls-uni-cntl)#
Step 6
link-id ipv4 unicast 10.2.2.4
Specifies the neighbor's optical address of an LMPlink for a GMPLS UNI controller.
neighbor link-id ipv4 unicast address
Example:
RP/0/RSP0/CPU0:router(config-lmp-gmpls-uni-cntl)#
Step 7
neighbor link-id ipv4 unicast 10.10.4.4
Specifies the neighbor's optical interface ID of anLMP link for a GMPLS UNI controller.
neighbor interface-id unnumbered interface-id
Example:
RP/0/RSP0/CPU0:router(config-lmp-gmpls-uni-cntl)#
Step 8
neighbor interface-id unnumbered 17
commitStep 9
Configuring RSVP Optical Refresh Interval and Missed CountPerform this task to configure optical refresh interval under the RSVP controller submode and to configurethe number of missed refresh messages allowed before optical tunnel states are deleted.
The interval argument is the interval (in seconds) at whichrefresh messages are sent and expected to be received. Therange is 180 to 86400 (a refresh-interval of 1 day).
signalling refresh out-of-band interval 200
Configures number of missed refresh messages allowed beforeoptical tunnel states are deleted.
signalling refresh out-of-band missed miss-count
Example:
RP/0/RSP0/CPU0:router(config-rsvp-cntl)#
Step 5
The miss-count argument is the number of refresh messages,expected at the configured refresh-interval, which can bemissedbefore optical tunnel states time out. The accepted range is 1to 48. The default value is 12.
signalling refresh out-of-band missed 30
commitStep 6
Configuration Examples for GMPLS UNIThese configuration examples are provided for GMPLS UNI:
Configuring Head UNI-C for a GMPLS Tunnel: ExampleThis example shows the minimal head UNI-C configuration require to establish a GMPLS tunnel:
Additional ReferencesFor additional information related to implementing GMPLS UNI, refer to the following references:
Related Documents
Document TitleRelated Topic
GMPLS UNI Commandsmodule in Cisco ASR 9000Series Aggregation Services RouterMPLS CommandReference
GMPLS UNI commands
MPLS Traffic Engineering commands module inCisco ASR 9000 Series Aggregation Services RouterMPLS Command Reference
MPLS Traffic Engineering commands
RSVP commands module in Cisco ASR 9000 SeriesAggregation Services Router MPLS CommandReference
RSVP commands
Cisco ASR 9000 Series Aggregation Services RouterGetting Started Guide
Getting started material
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x18
Implementing GMPLS UNIConfiguring LSP Diversity: Example
Document TitleRelated Topic
Configuring AAA Servicesmodule in Cisco ASR 9000Series Aggregation Services Router System SecurityConfiguration Guide
Information about user groups and task IDs
Standards
TitleStandard
—No new or modified standards are supported by thisfeature, and support for existing standards has notbeen modified by this feature.
MIBs
MIBs LinkMIBs
To locate and download MIBs using Cisco IOS XRsoftware, use the Cisco MIB Locator found at thefollowingURL and choose a platform under the CiscoAccess Products menu:
Exclude Routes - Extension to Resource ReserVationProtocol-Traffic Engineering (RSVP-TE)
RFC 4874
Generalized Labels for Lambda-Switch-Capable(LSC) Label Switching Routers
RFC 6205
Technical Assistance
LinkDescription
http://www.cisco.com/techsupportThe Cisco Technical Support website containsthousands of pages of searchable technical content,including links to products, technologies, solutions,technical tips, and tools. Registered Cisco.com userscan log in from this page to access evenmore content.
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x20