Configuring SRv6
Segment Routing (SR) can be applied on both MPLS and IPv6 data planes. In a SR-MPLS enabled network, an MPLS label is used as the Segment Identifier (SID) and the source router chooses a path to the destination and encodes the path in the packet header as a stack of labels. In a Segment Routing over IPv6 (SRv6) network, the IPv6 address serves as the SID. The source router encodes the path to destination as an ordered list of segments (list of IPv6 addresses) in the IPv6 packet. To encode an ordered list of IPv6 addresses in an IPv6 packet, a new routing header which is an extension header is used. This new header for SRv6 is called Segment Routing Header (SRH). In an SRv6 enabled network, the active segment is indicated by the destination address of the packet, and the next segment is indicated by a pointer in the SRH. SRv6 works on IPv6 data forwarding and is suitable for all data center deployments. SRv6 with SRH facilitates traffic engineering and path protection capabilities. Minus the SRH, SRv6 also supports traffic forwarding for multi-tenants with only the IPv6 packet header. In this case, the IPv6 destination address (128-bit) represents the reachability (locator) and the VPN function.
The forwarding methodology is such that if the destination address is within the locator space and is not in the SID table, it checks the standard routing table for a match.
For more information, see the Cisco Nexus 9000 Series NX-OS SRv6 Configuration Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-installation-and-configuration-guides-list.html/
Configuring a Locator and Encapsulation Source
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
srv6
locators
locator main-locator
prefix cafe:0:a:100::/64
encapsulation
source-address 1::1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srv6Entity |
sys/segrt/srv6 |
srv6Encapsulation |
sys/segrt/srv6/encapsulation |
srv6Locators |
sys/segrt/srv6/locators |
srv6Locator |
sys/segrt/srv6/locators/locator-main-locator |
segrtInst |
sys/segrt/inst |
srv6Entity Properties
The following table contains information about the srv6Entity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srv6Encapsulation Properties
The following table contains information about the srv6Encapsulation properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srcAddress | address:Ip
| IPv6 address | Value must match the ipv6 known format |
srv6Locators Properties
The following table contains information about the srv6Locators properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srv6Locator Properties
The following table contains information about the srv6Locator properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | srv6:LocName (string:Basic) | Locator name | A sequence of characters |
prefix | address:Ip
| Locator address | Value must match the ipv6 known format |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Traffic Engineering
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Traffic Engineering
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
no traffic-engineering
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Policy
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
policy POL_1
color 1 endpoint 1:2::3:4
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srtePolicy |
sys/segrt/te/policy-POL_1 |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srtePolicy Properties
The following table contains information about the srtePolicy properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
color | srte:ColorVal (scalar:Uint64) | Segment Routing TE Policy Color | RANGE: [0 , 4294967295] DEFAULT: 0 |
endpoint | address:Ip
| Segment Routing TE Endpoint IPv4/v6 address | Value must match the ipv6 known format |
name | srte:Name (string:Basic) | Segment Routing TE Policy Name | Must be unique for each policy. The name must only contain letters, digits, and the hyphen and underscore characters A sequence of characters |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting a Policy
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
no policy POL_1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srtePolicy |
sys/segrt/te/policy-POL_1 |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srtePolicy Properties
The following table contains information about the srtePolicy properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | srte:Name (string:Basic) | Segment Routing TE Policy Name | Must be unique for each policy. The name must only contain letters, digits, and the hyphen and underscore characters A sequence of characters |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring SRv6 Under SRTE
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-routing
srv6
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srteSR |
sys/segrt/te/sr |
srteSRv6 |
sys/segrt/te/sr/srv6 |
segrtInst |
sys/segrt/inst |
srteTE, srteSR, srteSRv6, and segrtInst Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting SRv6 Under SRTE
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-routing
no srv6
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srteSR |
sys/segrt/te/sr |
srteSRv6 |
sys/segrt/te/sr/srv6 |
segrtInst |
sys/segrt/inst |
srteTE, srteSR, srteSRv6, and segrtInst Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the SRv6 SRTE Locators Item
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-routing
srv6
locators
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srteSR |
sys/segrt/te/sr |
srteSRv6 |
sys/segrt/te/sr/srv6 |
srteLocators |
sys/segrt/te/sr/srv6/locs |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSR Properties
The following table contains information about the srteSR properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSRv6 Properties
The following table contains information about the srteSRv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteLocators Properties
The following table contains information about the srteLocators properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the SRv6 SRTE Locators Item
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-routing
srv6
no locators
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srteSR |
sys/segrt/te/sr |
srteSRv6 |
sys/segrt/te/sr/srv6 |
srteLocators |
sys/segrt/te/sr/srv6/locs |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSR Properties
The following table contains information about the srteSR properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSRv6 Properties
The following table contains information about the srteSRv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteLocators Properties
The following table contains information about the srteLocators properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Default Locator Name
Note: This example was added in Release 9.3(5).
The locator name element specifies the name of the locator that will be used for allocating policies. This is a reference by name to the global locator definition, and as such, the global locator must be separately defined under the top level segment-routing subitem srv6.
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-routing
srv6
locators
locator SampleString_123
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srteSR |
sys/segrt/te/sr |
srteSRv6 |
sys/segrt/te/sr/srv6 |
srteLocators |
sys/segrt/te/sr/srv6/locs |
srteLocator |
sys/segrt/te/sr/srv6/locs/loc-SampleString_123 |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSR Properties
The following table contains information about the srteSR properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSRv6 Properties
The following table contains information about the srteSRv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteLocators Properties
The following table contains information about the srteLocators properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteLocator Properties
The following table contains information about the srteLocator properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | srte:Name (string:Basic) | Locator name for SRv6 Traffic Engineering | The name must only contain letters, digits, and the hyphen and underscore characters |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Default Locator Name
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-routing
srv6
locators
no locator SampleString_123
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srteSR |
sys/segrt/te/sr |
srteSRv6 |
sys/segrt/te/sr/srv6 |
srteLocators |
sys/segrt/te/sr/srv6/locs |
srteLocator |
sys/segrt/te/sr/srv6/locs/loc-SampleString_123 |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSR Properties
The following table contains information about the srteSR properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteSRv6 Properties
The following table contains information about the srteSRv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteLocators Properties
The following table contains information about the srteLocators properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srteLocator Properties
The following table contains information about the srteLocator properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | srte:Name (string:Basic) | Locator name for SRv6 Traffic Engineering | The name must only contain letters, digits, and the hyphen and underscore characters |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Route with Complete SRv6 Encap (Without Traffic Engineering Policy)
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
tunnel-profile test
encapsulation srv6
route vrf default 13.0.0.0/24 remote-locator 6000:0:6:: function 66
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
ofmInst |
sys/ofm |
ofmTunnelProfile |
sys/ofm/tunnelprofile-[test] |
ofmRouteSrv6 |
sys/ofm/tunnelprofile-[test]/routevrf-[default]-routeip-[13.0.0.0/24] |
ofmTunnelProfile Properties
The following table contains information about the ofmTunnelProfile properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
encaptype | ofm:encapType (scalar:Enum8) | Encapsulation type for tunnel profile. The encapsulation type must be set to srv6 to configure SRv6 routes. VXLAN is not supported. | SELECTION: 0 - none 1 - vxlan 2 - srv6 DEFAULT: none |
profName | ofm:profileName (string:Basic) | Name of Tunnel Profile | MAX SIZE: 50 |
ofmRouteSrv6 Properties
The following table contains information about the ofmRouteSrv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
function | scalar:Uint32
| Function in the remote sid | RANGE: [0 , 65534] |
remoteLocator | address:IPv6
| Ipv6 locator of remote srv6 peer | Value must match ipv6 format |
route | address:Ip
| IP address for Srv6 | Value must match ipv4 or ipv6 known format |
vrfName | l3:VrfName (string:Basic) | Vrf name for Srv6 | A sequence of characters DEFAULT: default |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Route with Complete SRv6 Encap with Traffic Engineering Policy
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
tunnel-profile test
encapsulation srv6
route vrf default 14.0.0.0/24 remote-locator 6000:0:6:: function 66 via policy name POLICY1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
ofmInst |
sys/ofm |
ofmTunnelProfile |
sys/ofm/tunnelprofile-[test] |
ofmRouteSrv6 |
sys/ofm/tunnelprofile-[test]/routevrf-[default]-routeip-[14.0.0.0/24] |
ofmTunnelProfile Properties
The following table contains information about the ofmTunnelProfile properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
encaptype | ofm:encapType (scalar:Enum8) | Encapsulation type for tunnel profile. The encapsulation type must be set to srv6 to configure SRv6 routes. VXLAN is not supported. | SELECTION: 0 - none 1 - vxlan 2 - srv6 DEFAULT: none |
profName | ofm:profileName (string:Basic) | Name of Tunnel Profile | MAX SIZE: 50 |
ofmRouteSrv6 Properties
The following table contains information about the ofmRouteSrv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
function | scalar:Uint32
| Function in the remote sid | RANGE: [0 , 65534] |
remoteLocator | address:IPv6
| Ipv6 locator of remote srv6 peer | Value must match ipv6 format |
route | address:Ip
| IP address for Srv6 | Value must match ipv4 or ipv6 known format |
tePolicyName | ofm:TePolicyName (string:Basic) | Name of the Te-policy | MAX SIZE: 64 |
vrfName | l3:VrfName (string:Basic) | Vrf name for Srv6 | A sequence of characters DEFAULT: default |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Route with Complete SRv6 Encap with Traffic Engineering Policy via Color and Endpoint
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
tunnel-profile test
encapsulation srv6
route vrf default 15.0.0.0/24 remote-locator 6000:0:6:: function 66 via policy color 1 endpoint 6000:0:6::
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
ofmInst |
sys/ofm |
ofmTunnelProfile |
sys/ofm/tunnelprofile-[test] |
ofmRouteSrv6 |
sys/ofm/tunnelprofile-[test]/routevrf-[default]-routeip-[15.0.0.0/24] |
ofmTunnelProfile Properties
The following table contains information about the ofmTunnelProfile properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
encaptype | ofm:encapType (scalar:Enum8) | Encapsulation type for tunnel profile. The encapsulation type must be set to srv6 to configure SRv6 routes. VXLAN is not supported. | SELECTION: 0 - none 1 - vxlan 2 - srv6 DEFAULT: none |
profName | ofm:profileName (string:Basic) | Name of Tunnel Profile | MAX SIZE: 50 |
ofmRouteSrv6 Properties
The following table contains information about the ofmRouteSrv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
color | scalar:Uint32
| Name of Te-policy color | RANGE: [0 , 4294967295] |
endpoint | address:IPv6
| Ipv6 address of SRv6 End-point | Value must match ipv6 format |
function | scalar:Uint32
| Function in the remote sid | RANGE: [0 , 65534] |
remoteLocator | address:IPv6
| Ipv6 locator of remote srv6 peer | Value must match ipv6 format |
route | address:Ip
| IP address for Srv6 | Value must match ipv4 or ipv6 known format |
vrfName | l3:VrfName (string:Basic) | Vrf name for Srv6 | A sequence of characters DEFAULT: default |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Route with Traffic Engineering via a Policy Name
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
tunnel-profile test
encapsulation srv6
route vrf default 16.0.0.0/24 via policy name POLICY1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
ofmInst |
sys/ofm |
ofmTunnelProfile |
sys/ofm/tunnelprofile-[test] |
ofmRouteSrv6 |
sys/ofm/tunnelprofile-[test]/routevrf-[default]-routeip-[16.0.0.0/24] |
ofmTunnelProfile Properties
The following table contains information about the ofmTunnelProfile properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
encaptype | ofm:encapType (scalar:Enum8) | Encapsulation type for tunnel profile. The encapsulation type must be set to srv6 to configure SRv6 routes. VXLAN is not supported. | SELECTION: 0 - none 1 - vxlan 2 - srv6 DEFAULT: none |
profName | ofm:profileName (string:Basic) | Name of Tunnel Profile | MAX SIZE: 50 |
ofmRouteSrv6 Properties
The following table contains information about the ofmRouteSrv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
route | address:Ip
| IP address for Srv6 | Value must match ipv4 or ipv6 known format |
tePolicyName | ofm:TePolicyName (string:Basic) | Name of the Te-policy | MAX SIZE: 64 |
vrfName | l3:VrfName (string:Basic) | Vrf name for Srv6 | A sequence of characters DEFAULT: default |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Route with Traffic Engineering via Color and Endpoint
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
tunnel-profile test
encapsulation srv6
route vrf default 16.0.0.0/24 via policy color 1 endpoint 6000:0:6::
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
ofmInst |
sys/ofm |
ofmTunnelProfile |
sys/ofm/tunnelprofile-[test] |
ofmRouteSrv6 |
sys/ofm/tunnelprofile-[test]/routevrf-[default]-routeip-[16.0.0.0/24] |
ofmTunnelProfile Properties
The following table contains information about the ofmTunnelProfile properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
encaptype | ofm:encapType (scalar:Enum8) | Encapsulation type for tunnel profile. The encapsulation type must be set to srv6 to configure SRv6 routes. VXLAN is not supported. | SELECTION: 0 - none 1 - vxlan 2 - srv6 DEFAULT: none |
profName | ofm:profileName (string:Basic) | Name of Tunnel Profile | MAX SIZE: 50 |
ofmRouteSrv6 Properties
The following table contains information about the ofmRouteSrv6 properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
color | scalar:Uint32
| Name of Te-policy color | RANGE: [0 , 4294967295] |
endpoint | address:IPv6
| Ipv6 address of SRv6 End-point | Value must match ipv6 format |
route | address:Ip
| IP address for Srv6 | Value must match ipv4 or ipv6 known format |
vrfName | l3:VrfName (string:Basic) | Vrf name for Srv6 | A sequence of characters DEFAULT: default |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Enabling OFM
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
feature ofm
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
fmEntity |
sys/fm |
fmOfm |
sys/fm/ofm |
fmOfm Properties
The following table contains information about the fmOfm properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | fm:AdminState (scalar:Enum8) | Admin status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Disabling OFM
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no feature ofm
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
fmEntity |
sys/fm |
fmOfm |
sys/fm/ofm |
fmOfm Properties
The following table contains information about the fmOfm properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | fm:AdminState (scalar:Enum8) | Admin status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Enabling an SRv6 Tunnel Profile
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
tunnel-profile PROFILE1
encapsulation srv6
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
ofmInst |
sys/ofm |
ofmTunnelProfile |
sys/ofm/tunnelprofile-[PROFILE1] |
ofmTunnelProfile Properties
The following table contains information about the ofmTunnelProfile properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
encaptype | ofm:encapType (scalar:Enum8) | Encapsulation type for tunnel profile. The encapsulation type must be set to srv6 to configure SRv6 routes. VXLAN is not supported. | SELECTION: 0 - none 1 - vxlan 2 - srv6 DEFAULT: none |
profName | ofm:profileName (string:Basic) | Name of Tunnel Profile | MAX SIZE: 50 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring a Segment List
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
segment-routing
traffic-engineering
segment-list name low-latency
index 1 segment-routing srv6 cafe:0:b:200:1::
index 2 segment-routing srv6 cafe:0:d:400:1::
index 3 segment-routing srv6 cafe:0:c:300:1::
index 4 segment-routing srv6 cafe:0:e:500:1::
segment-list name high-bandwidth
index 1 segment-routing srv6 cafe:0:c:300:1::
index 2 segment-routing srv6 cafe:0:d:400:1::
index 3 segment-routing srv6 cafe:0:f:600:1::
index 4 segment-routing srv6 cafe:0:e:500:1::
policy blue
color 1 endpoint 5::5
candidate-paths
preference 200
explicit segment-list low-latency
preference 100
explicit segment-list high-bandwidth
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
segrtEntity |
sys/segrt |
srteTE |
sys/segrt/te |
srtePolicy |
sys/segrt/te/policy-blue |
srteExpCndPaths |
sys/segrt/te/policy-blue/expcndpaths |
srtePolPref |
sys/segrt/te/policy-blue/expcndpaths/pref-100 |
srtePolExp |
sys/segrt/te/policy-blue/expcndpaths/pref-100/exp-high-bandwidth |
srtePolPref |
sys/segrt/te/policy-blue/expcndpaths/pref-200 |
srtePolExp |
sys/segrt/te/policy-blue/expcndpaths/pref-200/exp-low-latency |
srteSegList |
sys/segrt/te/seglist-high-bandwidth |
srteNxtSid |
sys/segrt/te/seglist-high-bandwidth/nxtsid-4 |
srteNxtSid |
sys/segrt/te/seglist-high-bandwidth/nxtsid-3 |
srteNxtSid |
sys/segrt/te/seglist-high-bandwidth/nxtsid-2 |
srteNxtSid |
sys/segrt/te/seglist-high-bandwidth/nxtsid-1 |
srteSegList |
sys/segrt/te/seglist-low-latency |
srteNxtSid |
sys/segrt/te/seglist-low-latency/nxtsid-4 |
srteNxtSid |
sys/segrt/te/seglist-low-latency/nxtsid-3 |
srteNxtSid |
sys/segrt/te/seglist-low-latency/nxtsid-2 |
srteNxtSid |
sys/segrt/te/seglist-low-latency/nxtsid-1 |
segrtInst |
sys/segrt/inst |
srteTE Properties
The following table contains information about the srteTE properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srtePolicy Properties
The following table contains information about the srtePolicy properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
color | srte:ColorVal (scalar:Uint64) | Segment Routing TE Policy Color | RANGE: [0 , 4294967295] DEFAULT: 0 |
endpoint | address:Ip
| Segment Routing TE Endpoint IPv4/v6 address | Value must match the ipv6 known format |
name | srte:Name (string:Basic) | Segment Routing TE Policy Name | Must be unique for each policy. The name must only contain letters, digits, and the hyphen and underscore characters A sequence of characters |
srteExpCndPaths Properties
The following table contains information about the srteExpCndPaths properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
srtePolPref Properties
The following table contains information about the srtePolPref properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
pref | srte:OptNum (scalar:Uint32) | The preference value for the group of explicit paths | RANGE: [1 , 65535] |
srtePolExp Properties
The following table contains information about the srtePolExp properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | srte:Name (string:Basic) | Explicit path name. Must be the name of an existing ExpPath MO | Must be the name of an existing ExpPath MO A sequence of characters |
srteSegList Properties
The following table contains information about the srteSegList properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | srte:Name (string:Basic) | SRTE Explicit Segment List Name | Must be unique for each explicit path. The name must only contain letters, digits, and the hyphen and underscore characters A sequence of characters |
srteNxtSid Properties
The following table contains information about the srteNxtSid properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
idx | srte:OptNum (scalar:Uint32) | SRTE Segment List Next Label Index | RANGE: [1 , 65535] |
sid | address:Ip
| SRTE Segment List Next SID Value | Value must match ipv6 known format |
segrtInst Properties
The following table contains information about the segrtInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | nw:AdminSt (scalar:Enum8) | The administrative state of the object or policy. | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Show IPv6 Route Detail
Note: This example was added in Release 9.3(5).
CLI Output |
---|
switch# show ipv6 route detail
IPv6 Routing Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
ff00::/8, ubest/mbest: 1/0
cand ubest/mbest: 1/0, ufdm in/update: 1/0
*via Null0, [220/0], 00:33:43, discard, discard
0::/127, ubest/mbest: 1/0
cand ubest/mbest: 1/0, ufdm in/update: 1/0
*via Null0, [220/0], 00:33:43, discard, discard
fe80::/10, ubest/mbest: 1/0
cand ubest/mbest: 1/0, ufdm in/update: 1/0
*via sup-eth1, [0/0], 00:33:04, local
1::1/128, ubest/mbest: 2/0, attached
cand ubest/mbest: 2/0, ufdm in/update: 1/0
*via 1::1, Lo0, [0/0], 00:10:59, direct,
*via 1::1, Lo0, [0/0], 00:10:59, local
2::2/128, ubest/mbest: 1/0
cand ubest/mbest: 1/0, ufdm in/update: 1/0
*via 2000::2/128, [1/0], 00:04:34, static
recursive next hop: 2000::2/128
2000::/64, ubest/mbest: 1/0, attached
cand ubest/mbest: 1/0, ufdm in/update: 1/0
*via 2000::1, Eth1/1, [0/0], 00:04:34, direct,
2000::1/128, ubest/mbest: 1/0, attached
cand ubest/mbest: 1/0, ufdm in/update: 1/0
*via 2000::1, Eth1/1, [0/0], 00:04:34, local
|
Show IP Route Detail
Note: This example was added in Release 9.3(5).
CLI Output |
---|
switch# show ip route detail
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%' in via output denotes VRF
0.0.0.0/32, ubest/mbest: 1/0
*via Null0, [220/0], 00:30:09, broadcast, discard
127.0.0.0/8, ubest/mbest: 1/0
*via Null0, [220/0], 00:30:09, broadcast, discard
255.255.255.255/32, ubest/mbest: 1/0
*via sup-eth1, [0/0], 00:29:30, broadcast
1.1.1.1/32, ubest/mbest: 2/0, attached
*via 1.1.1.1, Lo0, [0/0], 00:09:52, local
*via 1.1.1.1, Lo0, [0/0], 00:09:52, direct
2.2.2.2/32, ubest/mbest: 1/0
*via 10.0.0.2, [1/0], 00:00:55, static
recursive next hop: 10.0.0.2/32
10.0.0.0/24, ubest/mbest: 1/0, attached
*via 10.0.0.1, Eth1/1, [0/0], 00:01:02, direct
10.0.0.0/32, ubest/mbest: 1/0, attached
*via 10.0.0.0, Null0, [0/0], 00:01:02, broadcast
10.0.0.1/32, ubest/mbest: 1/0, attached
*via 10.0.0.1, Eth1/1, [0/0], 00:01:02, local
10.0.0.2/32, ubest/mbest: 1/0, attached
*via 10.0.0.2, Eth1/1, [250/0], 00:00:55, am
10.0.0.255/32, ubest/mbest: 1/0, attached
*via 10.0.0.255, Eth1/1, [0/0], 00:01:02, broadcast
|