MPLS-TE OpenConfig Translation
General Restrictions
The general restrictions are as follows:
• MPLS-TE configuration is always given in “default” network-instance.
• For IP addresses, only IPv4 address family is supported.
• Only PATH_SETUP_RSVP is supported for /network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/config/signaling-protocol attribute.
• OpenConfig is mostly contained in /network-instances/network-instance/mpls. OcNOS NETCONF (IPI datamodels) is more dispersed with global configuration in /ipi-rsvp:rsvp-te/rsvp-instance and it contains router rsvp CLI command configuration with no correspondence in OpenConfig.
For this reason, the following configuration is augmented to OpenConfig as shown below:
grouping rsvp-te-config {
leaf enabled {
type empty;
description "When this leaf is present, it signifies that the RSVP functionality is active; conversely, its absence explicitly deactivates the feature";
}
}
augment "/oc-netinst:network-instances/oc-netinst:network-instance/oc-netinst:mpls/oc-netinst:signaling-protocols/oc-netinst:rsvp-te" {
container config {
description "RSVP-TE configuration attributes";
uses rsvp-te-config;
}
container state {
description "RSVP-TE state attributes";
uses rsvp-te-config;
config false;
}
}
For MPLS-TE configuration to be accepted in OcNOS, the following configuration must be provided at least once:
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
</mpls>
</network-instance>
</network-instances>
Create a Label-Switched Path (LSP) without Constraints
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set an LSP at the ingress router.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set an LSP at the ingress router.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<tunnels>
<tunnel>
<name>TUNNEL1001</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>TUNNEL1001</name>
<source>172.16.100.1</source>
<description>TUNNEL_A_TO_B</description>
<metric-type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LSP_METRIC_ABSOLUTE</metric-type>
<metric>10</metric>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<protection-style-requested
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:UNPROTECTED</protection-style-requested>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
</p2p-tunnel-attributes>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set an LSP at the ingress router.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-trunk TUNNEL1001 ipv4
description TUNNEL_A_TO_B
from 172.16.100.1
lsp-metric absolute 10
to 172.16.200.1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set an LSP at the ingress router.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>TUNNEL1001</trunk-name>
<config>
<trunk-name>TUNNEL1001</trunk-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
<trunk-family>ipv4</trunk-family>
<absolute-metric>10</absolute-metric>
</config>
</ingress-trunk>
</ingress-trunks>
</trunks>
</rsvp-te>
Create a Label-Switched Path (LSP) with Constraints
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to configure an LSP with traffic engineering constraints (delay, bandwidth and hop count) at the ingress router.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to configure an LSP with traffic engineering constraints (delay, bandwidth and hop count) at the ingress router.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<tunnels>
<tunnel>
<name>TUNNEL1001</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>TUNNEL1001</name>
<description>TUNNEL_A_TO_B</description>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<protection-style-requested
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:UNPROTECTED</protection-style-requested>
<source>172.16.100.1</source>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
<p2p-primary-path>
<p2p-primary-path>
<name>LSP_BW_WITH_CONSTRAIN</name>
<config>
<name>LSP_BW_WITH_CONSTRAIN</name>
<use-cspf>false</use-cspf>
<retry-timer>60</retry-timer>
<path-computation-method
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LOCALLY_COMPUTED</path-computation-method>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
</config>
<path-metric-bound-constraints>
<path-metric-bound-constraint>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
<config>
<metric-upper-bound>4</metric-upper-bound>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
</config>
</path-metric-bound-constraint>
</path-metric-bound-constraints>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
<bandwidth>
<config>
<specification-type>SPECIFIED</specification-type>
<set-bandwidth>5000</set-bandwidth>
</config>
</bandwidth>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to configure an LSP with traffic engineering constraints (delay, bandwidth and hop count) at the ingress router.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-trunk TUNNEL1001 ipv4
description TUNNEL_A_TO_B
no primary cspf
primary setup-priority 7
primary hold-priority 0
primary hop-limit 4
primary bandwidth 5m
primary retry-timer 60
from 172.16.100.1
to 172.16.200.1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to configure an LSP with traffic engineering constraints (delay, bandwidth and hop count) at the ingress router.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>TUNNEL1001</trunk-name>
<config>
<trunk-name>TUNNEL1001</trunk-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
<trunk-family>ipv4</trunk-family>
</config>
<sessions>
<session>
<trunk-session-type>primary</trunk-session-type>
<config>
<trunk-session-type>primary</trunk-session-type>
<disable-cspf/>
<retry-interval>60</retry-interval>
</config>
<path-state-block>
<session-attributes>
<config>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
<hop-limit>4</hop-limit>
<bandwidth>5m</bandwidth>
</config>
</session-attributes>
</path-state-block>
</session>
</sessions>
</ingress-trunk>
</ingress-trunks>
</trunks>
</rsvp-te>
Create a Label-Switched Path (LSP) with Explicit Paths
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set an LSP with explicit path constraints.
Note: This configuration may have additional constraints by combining it with the configurations in other sections.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set an LSP with explicit path constraints.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<named-explicit-paths>
<named-explicit-path>
<name>EXPLICIT_PATH_1_2_3</name>
<config>
<name>EXPLICIT_PATH_1_2_3</name>
</config>
<explicit-route-objects>
<explicit-route-object>
<index>1</index>
<config>
<address>172.16.101.1</address>
<hop-type>STRICT</hop-type>
<index>1</index>
</config>
</explicit-route-object>
<explicit-route-object>
<index>2</index>
<config>
<address>172.16.102.2</address>
<hop-type>STRICT</hop-type>
<index>2</index>
</config>
</explicit-route-object>
<explicit-route-object>
<index>3</index>
<config>
<address>172.16.103.3</address>
<hop-type>STRICT</hop-type>
<index>3</index>
</config>
</explicit-route-object>
</explicit-route-objects>
</named-explicit-path>
</named-explicit-paths>
<tunnels>
<tunnel>
<name>TUNNEL1001</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>TUNNEL1001</name>
<source>172.16.100.1</source>
<description>TUNNEL_A_TO_B</description>
<metric-type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LSP_METRIC_ABSOLUTE</metric-type>
<metric>10</metric>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<protection-style-requested
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:UNPROTECTED</protection-style-requested>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
<p2p-primary-path>
<p2p-primary-path>
<name>LSP_EXPLICIT_PATH</name>
<config>
<name>LSP_EXPLICIT_PATH</name>
<use-cspf>false</use-cspf>
<path-computation-method
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LOCALLY_COMPUTED</path-computation-method>
<explicit-path-name>EXPLICIT_PATH_1_2_3</explicit-path-name>
</config>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
<bandwidth>
<config>
<specification-type>SPECIFIED</specification-type>
<set-bandwidth>5000</set-bandwidth>
</config>
</bandwidth>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set an LSP with explicit path constraints.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-path EXPLICIT_PATH_1_2_3 mpls
172.16.101.1 strict
172.16.102.2 strict
172.16.103.3 strict
!
!
rsvp-trunk TUNNEL1001 ipv4
description TUNNEL_A_TO_B
no primary cspf
primary path EXPLICIT_PATH_1_2_3
primary bandwidth 5m
from 172.16.100.1
lsp-metric absolute 10
to 172.16.200.1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set an LSP with explicit path constraints.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<rsvp-paths>
<rsvp-path>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<path-type>mpls</path-type>
</config>
<explicit-route-object>
<mpls-hops>
<mpls-hop>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
<mpls-hop>
<hop-address>172.16.102.2</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.102.2</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
<mpls-hop>
<hop-address>172.16.103.3</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.103.3</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
</mpls-hops>
</explicit-route-object>
</rsvp-path>
</rsvp-paths>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>TUNNEL1001</trunk-name>
<config>
<trunk-name>TUNNEL1001</trunk-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
<trunk-family>ipv4</trunk-family>
<absolute-metric>10</absolute-metric>
</config>
<sessions>
<session>
<trunk-session-type>primary</trunk-session-type>
<config>
<trunk-session-type>primary</trunk-session-type>
<disable-cspf/>
</config>
<path-state-block>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
</config>
<session-attributes>
<config>
<bandwidth>5m</bandwidth>
</config>
</session-attributes>
</path-state-block>
</session>
</sessions>
</ingress-trunk>
</ingress-trunks>
</trunks>
</rsvp-te>
Create a Label-Switched Path (LSP) with Protection Redundancy 1+1
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set an LSP with traffic in a redundant path. The redundant path, called secondary path, must be disjoint from the primary path.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set an LSP with traffic in a redundant path.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<named-explicit-paths>
<named-explicit-path>
<name>EXPLICIT_PATH_1_2_3</name>
<config>
<name>EXPLICIT_PATH_1_2_3</name>
</config>
<explicit-route-objects>
<explicit-route-object>
<index>1</index>
<config>
<address>172.16.101.1</address>
<hop-type>STRICT</hop-type>
<index>1</index>
</config>
</explicit-route-object>
</explicit-route-objects>
</named-explicit-path>
</named-explicit-paths>
<tunnels>
<tunnel>
<name>TUNNEL1001</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>TUNNEL1001</name>
<source>172.16.100.1</source>
<description>TUNNEL_A_TO_B</description>
<metric-type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LSP_METRIC_ABSOLUTE</metric-type>
<metric>10</metric>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<protection-style-requested
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:UNPROTECTED</protection-style-requested>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
<p2p-secondary-paths>
<p2p-secondary-path>
<name>LSP_SECONDARY</name>
<config>
<name>LSP_SECONDARY</name>
<use-cspf>false</use-cspf>
<retry-timer>60</retry-timer>
<path-computation-method
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LOCALLY_COMPUTED</path-computation-method>
<explicit-path-name>EXPLICIT_PATH_1_2_3</explicit-path-name>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
</config>
<path-metric-bound-constraints>
<path-metric-bound-constraint>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
<config>
<metric-upper-bound>4</metric-upper-bound>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
</config>
</path-metric-bound-constraint>
</path-metric-bound-constraints>
</p2p-secondary-path>
</p2p-secondary-paths>
<p2p-primary-path>
<p2p-primary-path>
<name>LSP_EXPLICIT_PATH</name>
<config>
<name>LSP_EXPLICIT_PATH</name>
<use-cspf>false</use-cspf>
<retry-timer>60</retry-timer>
<path-computation-method
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LOCALLY_COMPUTED</path-computation-method>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
</config>
<path-metric-bound-constraints>
<path-metric-bound-constraint>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
<config>
<metric-upper-bound>4</metric-upper-bound>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
</config>
</path-metric-bound-constraint>
</path-metric-bound-constraints>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
<bandwidth>
<config>
<specification-type>SPECIFIED</specification-type>
<set-bandwidth>5000</set-bandwidth>
</config>
</bandwidth>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set an LSP with traffic in a redundant path.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-path EXPLICIT_PATH_1_2_3 mpls
172.16.101.1 strict
!
rsvp-trunk TUNNEL1001 ipv4
description TUNNEL_A_TO_B
no primary cspf
primary setup-priority 7
primary hold-priority 0
primary hop-limit 4
primary bandwidth 5m
primary retry-timer 60
no secondary cspf
secondary path EXPLICIT_PATH_1_2_3
secondary setup-priority 7
secondary hold-priority 0
secondary hop-limit 4
secondary bandwidth 5m
secondary retry-timer 60
from 172.16.100.1
lsp-metric absolute 10
to 172.16.200.1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set an LSP with traffic in a redundant path.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<rsvp-paths>
<rsvp-path>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<path-type>mpls</path-type>
</config>
<explicit-route-object>
<mpls-hops>
<mpls-hop>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
</mpls-hops>
</explicit-route-object>
</rsvp-path>
</rsvp-paths>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>TUNNEL1001</trunk-name>
<config>
<trunk-name>TUNNEL1001</trunk-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
<trunk-family>ipv4</trunk-family>
<absolute-metric>10</absolute-metric>
</config>
<sessions>
<session>
<trunk-session-type>secondary</trunk-session-type>
<config>
<trunk-session-type>secondary</trunk-session-type>
<disable-cspf/>
<retry-interval>60</retry-interval>
</config>
<path-state-block>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
</config>
<session-attributes>
<config>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
<hop-limit>4</hop-limit>
<bandwidth>5m</bandwidth>
</config>
</session-attributes>
</path-state-block>
</session>
<session>
<trunk-session-type>primary</trunk-session-type>
<config>
<trunk-session-type>primary</trunk-session-type>
<disable-cspf/>
<retry-interval>60</retry-interval>
</config>
<path-state-block>
<session-attributes>
<config>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
<hop-limit>4</hop-limit>
<bandwidth>5m</bandwidth>
</config>
</session-attributes>
</path-state-block>
</session>
</sessions>
</ingress-trunk>
</ingress-trunks>
</trunks>
</rsvp-te>
Create a Label-Switched Path (LSP) with Protection Redundancy 1:1 (“FRR one-to-one”)
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set an LSP with backup paths (detour LSPs) at the ingress node. Each node along the LSP will establish a backup LSP circumventing the next node of the protected LSP.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set an LSP with backup paths (detour LSPs) at the ingress node.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<named-explicit-paths>
<named-explicit-path>
<name>EXPLICIT_PATH_1_2_3</name>
<config>
<name>EXPLICIT_PATH_1_2_3</name>
</config>
<explicit-route-objects>
<explicit-route-object>
<index>1</index>
<config>
<address>172.16.101.1</address>
<hop-type>STRICT</hop-type>
<index>1</index>
</config>
</explicit-route-object>
</explicit-route-objects>
</named-explicit-path>
</named-explicit-paths>
<tunnels>
<tunnel>
<name>TUNNEL1001</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>TUNNEL1001</name>
<source>172.16.100.1</source>
<description>TUNNEL_A_TO_B</description>
<metric-type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LSP_METRIC_ABSOLUTE</metric-type>
<metric>10</metric>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<protection-role xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments" xmlns:ipi-oc-ni-augments="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">ipi-oc-ni-augments:ONE_TO_ONE</protection-role>
<protection-style-requested
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LINK_NODE_PROTECTION_REQUESTED</protection-style-requested>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
<p2p-primary-path>
<p2p-primary-path>
<name>LSP_EXPLICIT_PATH</name>
<config>
<name>LSP_EXPLICIT_PATH</name>
<use-cspf>false</use-cspf>
<retry-timer>60</retry-timer>
<path-computation-method
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LOCALLY_COMPUTED</path-computation-method>
<explicit-path-name>EXPLICIT_PATH_1_2_3</explicit-path-name>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
</config>
<path-metric-bound-constraints>
<path-metric-bound-constraint>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
<config>
<metric-upper-bound>4</metric-upper-bound>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
</config>
</path-metric-bound-constraint>
</path-metric-bound-constraints>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
<bandwidth>
<config>
<specification-type>SPECIFIED</specification-type>
<set-bandwidth>5000</set-bandwidth>
</config>
</bandwidth>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set an LSP with backup paths (detour LSPs) at the ingress node.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-path EXPLICIT_PATH_1_2_3 mpls
172.16.101.1 strict
!
rsvp-trunk TUNNEL1001 ipv4
description TUNNEL_A_TO_B
no primary cspf
primary fast-reroute protection one-to-one
primary fast-reroute node-protection
primary path EXPLICIT_PATH_1_2_3
primary setup-priority 7
primary hold-priority 0
primary hop-limit 4
primary bandwidth 5m
primary retry-timer 60
from 172.16.100.1
lsp-metric absolute 10
to 172.16.200.1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set an LSP with backup paths (detour LSPs) at the ingress node.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<rsvp-paths>
<rsvp-path>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<path-type>mpls</path-type>
</config>
<explicit-route-object>
<mpls-hops>
<mpls-hop>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
</mpls-hops>
</explicit-route-object>
</rsvp-path>
</rsvp-paths>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>TUNNEL1001</trunk-name>
<config>
<trunk-name>TUNNEL1001</trunk-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
<trunk-family>ipv4</trunk-family>
<absolute-metric>10</absolute-metric>
</config>
<sessions>
<session>
<trunk-session-type>primary</trunk-session-type>
<config>
<trunk-session-type>primary</trunk-session-type>
<disable-cspf/>
<retry-interval>60</retry-interval>
</config>
<path-state-block>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
</config>
<session-attributes>
<config>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
<hop-limit>4</hop-limit>
<bandwidth>5m</bandwidth>
</config>
</session-attributes>
</path-state-block>
</session>
<fast-reroute>
<config>
<protection>one-to-one</protection>
<enable-node-protection/>
</config>
</fast-reroute>
</sessions>
</ingress-trunk>
</ingress-trunks>
</trunks>
</rsvp-te>
Create a Label-Switched Path (LSP) with Protection Redundancy 1:N
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set a shared backup LSP (bypass tunnel) for multiple LSPs.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set a shared backup LSP (bypass tunnel) for multiple LSPs.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<named-explicit-paths>
<named-explicit-path>
<name>EXPLICIT_PATH_1_2_3</name>
<config>
<name>EXPLICIT_PATH_1_2_3</name>
</config>
<explicit-route-objects>
<explicit-route-object>
<index>1</index>
<config>
<address>172.16.101.1</address>
<hop-type>STRICT</hop-type>
<index>1</index>
</config>
</explicit-route-object>
<explicit-route-object>
<index>2</index>
<config>
<address>172.16.102.2</address>
<hop-type>STRICT</hop-type>
<index>2</index>
</config>
</explicit-route-object>
<explicit-route-object>
<index>3</index>
<config>
<address>172.16.103.3</address>
<hop-type>STRICT</hop-type>
<index>3</index>
</config>
</explicit-route-object>
</explicit-route-objects>
</named-explicit-path>
</named-explicit-paths>
<tunnels>
<tunnel>
<name>BYPASS_TUNNEL10001</name>
<config>
<name>BYPASS_TUNNEL10001</name>
<source>172.16.100.1</source>
<description>TUNNEL_A_TO_B</description>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<protection-role xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments" xmlns:ipi-oc-ni-augments="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">ipi-oc-ni-augments:BYPASS</protection-role>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
<p2p-primary-path>
<p2p-primary-path>
<name>LSP_BW_WITH_CONSTRAIN</name>
<config>
<retry-timer>60</retry-timer>
<name>LSP_BW_WITH_CONSTRAIN</name>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
</config>
<path-metric-bound-constraints>
<path-metric-bound-constraint>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
<config>
<metric-upper-bound>4</metric-upper-bound>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
</config>
</path-metric-bound-constraint>
</path-metric-bound-constraints>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
</tunnel>
<tunnel>
<name>TUNNEL1001</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>TUNNEL1001</name>
<source>172.16.100.1</source>
<description>TUNNEL_A_TO_B</description>
<metric-type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LSP_METRIC_ABSOLUTE</metric-type>
<metric>10</metric>
<admin-status
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:ADMIN_UP</admin-status>
<protection-role xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments" xmlns:ipi-oc-ni-augments="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">ipi-oc-ni-augments:FACILITY</protection-role>
<protection-style-requested
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LINK_NODE_PROTECTION_REQUESTED</protection-style-requested>
</config>
<p2p-tunnel-attributes>
<config>
<destination>172.16.200.1</destination>
</config>
<p2p-primary-path>
<p2p-primary-path>
<name>LSP_EXPLICIT_PATH</name>
<config>
<name>LSP_EXPLICIT_PATH</name>
<use-cspf>false</use-cspf>
<retry-timer>60</retry-timer>
<path-computation-method
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:LOCALLY_COMPUTED</path-computation-method>
<explicit-path-name>EXPLICIT_PATH_1_2_3</explicit-path-name>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
</config>
<path-metric-bound-constraints>
<path-metric-bound-constraint>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
<config>
<metric-upper-bound>4</metric-upper-bound>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:HOP_COUNT</type>
</config>
</path-metric-bound-constraint>
</path-metric-bound-constraints>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
<bandwidth>
<config>
<specification-type>SPECIFIED</specification-type>
<set-bandwidth>5000</set-bandwidth>
</config>
</bandwidth>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set a shared backup LSP (bypass tunnel) for multiple LSPs.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-path EXPLICIT_PATH_1_2_3 mpls
172.16.101.1 strict
172.16.102.2 strict
172.16.103.3 strict
!
rsvp-trunk TUNNEL1001 ipv4
description TUNNEL_A_TO_B
no primary cspf
primary fast-reroute protection facility
primary fast-reroute node-protection
primary path EXPLICIT_PATH_1_2_3
primary setup-priority 7
primary hold-priority 0
primary hop-limit 4
primary bandwidth 5m
primary retry-timer 60
from 172.16.100.1
lsp-metric absolute 10
to 172.16.200.1
!
rsvp-bypass BYPASS_TUNNEL10001
description TUNNEL_A_TO_B
setup-priority 7
hold-priority 0
hop-limit 4
retry-timer 60
from 172.16.100.1
to 172.16.200.1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set a shared backup LSP (bypass tunnel) for multiple LSPs.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<rsvp-paths>
<rsvp-path>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
<path-type>mpls</path-type>
</config>
<explicit-route-object>
<mpls-hops>
<mpls-hop>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.101.1</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
<mpls-hop>
<hop-address>172.16.102.2</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.102.2</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
<mpls-hop>
<hop-address>172.16.103.3</hop-address>
<hop-type>strict</hop-type>
<config>
<hop-address>172.16.103.3</hop-address>
<hop-type>strict</hop-type>
</config>
</mpls-hop>
</mpls-hops>
</explicit-route-object>
</rsvp-path>
</rsvp-paths>
<trunks>
<bypass-trunks>
<bypass-trunk>
<bypass-name>BYPASS_TUNNEL10001</bypass-name>
<config>
<bypass-name>BYPASS_TUNNEL10001</bypass-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
</config>
<session>
<config>
<retry-interval>60</retry-interval>
</config>
<path-state-block>
<session-attributes>
<config>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
<hop-limit>4</hop-limit>
</config>
</session-attributes>
</path-state-block>
</session>
</bypass-trunk>
</bypass-trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>TUNNEL1001</trunk-name>
<config>
<trunk-name>TUNNEL1001</trunk-name>
<ingress>172.16.100.1</ingress>
<egress>172.16.200.1</egress>
<description>TUNNEL_A_TO_B</description>
<trunk-family>ipv4</trunk-family>
<absolute-metric>10</absolute-metric>
</config>
<sessions>
<session>
<trunk-session-type>primary</trunk-session-type>
<config>
<trunk-session-type>primary</trunk-session-type>
<disable-cspf/>
<retry-interval>60</retry-interval>
</config>
<path-state-block>
<config>
<path-name>EXPLICIT_PATH_1_2_3</path-name>
</config>
<session-attributes>
<config>
<hold-priority>0</hold-priority>
<setup-priority>7</setup-priority>
<hop-limit>4</hop-limit>
<bandwidth>5m</bandwidth>
</config>
</session-attributes>
</path-state-block>
</session>
<fast-reroute>
<config>
<protection>facility</protection>
<enable-node-protection/>
</config>
</fast-reroute>
</sessions>
</ingress-trunk>
</ingress-trunks>
</trunks>
</rsvp-te>
Create a Label-Switched Path (LSP) with Auto-Bandwidth
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set an LSP with Auto-Bandwidth feature.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set an LSP with Auto-Bandwidth feature.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<tunnels>
<tunnel>
<name>T1</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>T1</name>
</config>
<p2p-tunnel-attributes>
<config>
<destination>192.168.0.90</destination>
</config>
</p2p-tunnel-attributes>
<bandwidth>
<config>
<specification-type>AUTO</specification-type>
</config>
<auto-bandwidth>
<config>
<adjust-interval>300</adjust-interval>
</config>
<overflow>
<config>
<overflow-threshold>20</overflow-threshold>
<trigger-event-count>10</trigger-event-count>
</config>
</overflow>
<underflow>
<config>
<underflow-threshold>20</underflow-threshold>
<trigger-event-count>20</trigger-event-count>
</config>
</underflow>
</auto-bandwidth>
</bandwidth>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set an LSP with Auto-Bandwidth feature.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
rsvp-auto-bandwidth T1
adjust-interval 5
overflow-threshold percent 20
underflow-threshold percent 20
overflow-limit 10
underflow-limit 20
!
!
rsvp-trunk T1 ipv4
auto-bandwidth T1
to 192.168.0.90
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set an LSP with Auto-Bandwidth feature.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>T1</trunk-name>
<config>
<trunk-name>T1</trunk-name>
<egress>192.168.0.90</egress>
<trunk-family>ipv4</trunk-family>
<auto-bandwidth>T1</auto-bandwidth>
</config>
</ingress-trunk>
</ingress-trunks>
</trunks>
<rsvp-auto-bandwidths>
<rsvp-auto-bandwidth>
<profile-name>T1</profile-name>
<config>
<profile-name>T1</profile-name>
<adjust-interval>5</adjust-interval>
<overflow-threshold-percent>20</overflow-threshold-percent>
<underflow-threshold-percent>20</underflow-threshold-percent>
<overflow-limit>10</overflow-limit>
<underflow-limit>20</underflow-limit>
</config>
</rsvp-auto-bandwidth>
</rsvp-auto-bandwidths>
</rsvp-te>
Configure Shared Risk Link Group (SRLG)
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to set SRLG values to RSVP enabled interfaces.
RSVP attempts to prevent using links with the same SRLG value when establishing primary and secondary LSPs in order to effectively form disjoint paths.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to set SRLG values to RSVP enabled interfaces.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
<interface-attributes>
<interface>
<interface-id>eth1</interface-id>
<interface-ref>
<config>
<interface>eth1</interface>
</config>
</interface-ref>
<config>
<interface-id>eth1</interface-id>
<enabled xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">true</enabled>
</config>
</interface>
<interface>
<interface-id>eth2</interface-id>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
<config>
<interface-id>eth2</interface-id>
<enabled xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">true</enabled>
</config>
</interface>
<interface>
<interface-id>eth3</interface-id>
<interface-ref>
<config>
<interface>eth3</interface>
</config>
</interface-ref>
<config>
<interface-id>eth3</interface-id>
<enabled xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">true</enabled>
</config>
</interface>
</interface-attributes>
</rsvp-te>
</signaling-protocols>
<global>
<interface-attributes>
<interface>
<interface-id>eth1</interface-id>
<config>
<interface-id>eth1</interface-id>
<mpls-enabled>true</mpls-enabled>
</config>
<interface-ref>
<config>
<interface>eth1</interface>
</config>
</interface-ref>
</interface>
<interface>
<interface-id>eth2</interface-id>
<config>
<interface-id>eth2</interface-id>
<mpls-enabled>true</mpls-enabled>
</config>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
</interface>
<interface>
<interface-id>eth3</interface-id>
<config>
<interface-id>eth3</interface-id>
<mpls-enabled>true</mpls-enabled>
</config>
<interface-ref>
<config>
<interface>eth3</interface>
</config>
</interface-ref>
</interface>
</interface-attributes>
</global>
<te-interface-attributes>
<interface>
<interface-id>eth1</interface-id>
<config>
<interface-id>eth1</interface-id>
<srlg-membership>100</srlg-membership>
<srlg-membership>200</srlg-membership>
</config>
<interface-ref>
<config>
<interface>eth1</interface>
</config>
</interface-ref>
</interface>
<interface>
<interface-id>eth2</interface-id>
<config>
<interface-id>eth2</interface-id>
<srlg-membership>100</srlg-membership>
</config>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
</interface>
<interface>
<interface-id>eth3</interface-id>
<config>
<interface-id>eth3</interface-id>
<srlg-membership>200</srlg-membership>
</config>
<interface-ref>
<config>
<interface>eth3</interface>
</config>
</interface-ref>
</interface>
</te-interface-attributes>
<te-global-attributes>
<srlgs>
<srlg>
<name>100</name>
<config>
<name>100</name>
</config>
</srlg>
<srlg>
<name>200</name>
<config>
<name>200</name>
</config>
</srlg>
</srlgs>
</te-global-attributes>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to set SRLG values to RSVP enabled interfaces.
OcNOS#show running-config
!
router rsvp
!
...
!
interface eth1
label-switching
mpls traffic-eng srlg 100
mpls traffic-eng srlg 200
enable-rsvp
!
interface eth2
label-switching
mpls traffic-eng srlg 100
enable-rsvp
!
interface eth3
label-switching
mpls traffic-eng srlg 200
enable-rsvp
!
...
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to set SRLG values to RSVP enabled interfaces.
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
<enable-rsvp/>
</config>
</interface>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
<enable-rsvp/>
</config>
</interface>
<interface>
<name>eth3</name>
<config>
<name>eth3</name>
<enable-rsvp/>
</config>
</interface>
</interfaces>
</rsvp-te>
<mpls xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-mpls">
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
</config>
<label-switching>
<config>
<enable/>
</config>
</label-switching>
<mpls-interface-bandwidth>
<config>
<shared-risk-link-group>100</shared-risk-link-group>
<shared-risk-link-group>200</shared-risk-link-group>
</config>
</mpls-interface-bandwidth>
</interface>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<label-switching>
<config>
<enable/>
</config>
</label-switching>
<mpls-interface-bandwidth>
<config>
<shared-risk-link-group>100</shared-risk-link-group>
</config>
</mpls-interface-bandwidth>
</interface>
<interface>
<name>eth3</name>
<config>
<name>eth3</name>
</config>
<label-switching>
<config>
<enable/>
</config>
</label-switching>
<mpls-interface-bandwidth>
<config>
<shared-risk-link-group>200</shared-risk-link-group>
</config>
</mpls-interface-bandwidth>
</interface>
</interfaces>
</mpls>
Add Administrative Group Constraints to a Label-Switched Path (LSP)
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to add administrative group constraints (also known as color constraints) to an LSP.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to add administrative group constraints to an LSP.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<mpls>
<te-global-attributes>
<mpls-admin-groups>
<admin-group>
<admin-group-name>A</admin-group-name>
<config>
<admin-group-name>A</admin-group-name>
<bit-position>0</bit-position>
</config>
</admin-group>
<admin-group>
<admin-group-name>B</admin-group-name>
<config>
<admin-group-name>B</admin-group-name>
<bit-position>1</bit-position>
</config>
</admin-group>
<admin-group>
<admin-group-name>C</admin-group-name>
<config>
<admin-group-name>C</admin-group-name>
<bit-position>2</bit-position>
</config>
</admin-group>
<admin-group>
<admin-group-name>D</admin-group-name>
<config>
<admin-group-name>D</admin-group-name>
<bit-position>3</bit-position>
</config>
</admin-group>
<admin-group>
<admin-group-name>E</admin-group-name>
<config>
<admin-group-name>E</admin-group-name>
<bit-position>4</bit-position>
</config>
</admin-group>
</mpls-admin-groups>
</te-global-attributes>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled/>
</config>
<interface-attributes>
<interface>
<interface-id>eth1</interface-id>
<interface-ref>
<config>
<interface>eth1</interface>
</config>
</interface-ref>
<config>
<interface-id>eth1</interface-id>
<enabled xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">true</enabled>
</config>
</interface>
<interface>
<interface-id>eth2</interface-id>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
<config>
<interface-id>eth2</interface-id>
<enabled xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">true</enabled>
</config>
</interface>
</interface-attributes>
</rsvp-te>
</signaling-protocols>
<lsps>
<constrained-path>
<named-explicit-paths>
<named-explicit-path>
<name>P1</name>
<config>
<name>P1</name>
</config>
</named-explicit-path>
</named-explicit-paths>
<tunnels>
<tunnel>
<name>T1</name>
<config>
<type
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:P2P</type>
<signaling-protocol
xmlns:oc-mplst="http://openconfig.net/yang/mpls-types">oc-mplst:PATH_SETUP_RSVP</signaling-protocol>
<name>T1</name>
</config>
<p2p-tunnel-attributes>
<config>
<destination>192.168.0.90</destination>
</config>
<p2p-primary-path>
<p2p-primary-path>
<name>Primary</name>
<config>
<name>Primary</name>
<use-cspf>false</use-cspf>
<explicit-path-name>P1</explicit-path-name>
</config>
<admin-groups>
<config>
<include-any-group>A</include-any-group>
<include-any-group>C</include-any-group>
</config>
</admin-groups>
</p2p-primary-path>
</p2p-primary-path>
</p2p-tunnel-attributes>
</tunnel>
</tunnels>
</constrained-path>
</lsps>
<global>
<interface-attributes>
<interface>
<interface-id>eth1</interface-id>
<config>
<interface-id>eth1</interface-id>
<mpls-enabled>true</mpls-enabled>
</config>
<interface-ref>
<config>
<interface>eth1</interface>
</config>
</interface-ref>
</interface>
<interface>
<interface-id>eth2</interface-id>
<config>
<interface-id>eth2</interface-id>
<mpls-enabled>true</mpls-enabled>
</config>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
</interface>
</interface-attributes>
</global>
<te-interface-attributes>
<interface>
<interface-id>eth1</interface-id>
<config>
<interface-id>eth1</interface-id>
<admin-group>A</admin-group>
<admin-group>B</admin-group>
<admin-group>C</admin-group>
</config>
<interface-ref>
<config>
<interface>eth1</interface>
</config>
</interface-ref>
</interface>
<interface>
<interface-id>eth2</interface-id>
<config>
<interface-id>eth2</interface-id>
<admin-group>D</admin-group>
<admin-group>E</admin-group>
</config>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
</interface>
</te-interface-attributes>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to add administrative group constraints to an LSP.
OcNOS#show running-config
...
!
admin-group A 0
admin-group B 1
admin-group C 2
admin-group D 3
admin-group E 4
...
!
router rsvp
!
...
!
interface eth1
label-switching
admin-group A
admin-group B
admin-group C
enable-rsvp
!
interface eth2
label-switching
admin-group D
admin-group E
enable-rsvp
!
...
!
rsvp-path P1 mpls
!
rsvp-trunk T1 ipv4
no primary cspf
primary include-any A
primary include-any C
to 192.168.0.90
!
...
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to add administrative group constraints to an LSP.
<admin-groups xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-global-te">
<admin-group>
<name>A</name>
<id>0</id>
<config>
<name>A</name>
<id>0</id>
</config>
</admin-group>
<admin-group>
<name>B</name>
<id>1</id>
<config>
<name>B</name>
<id>1</id>
</config>
</admin-group>
<admin-group>
<name>C</name>
<id>2</id>
<config>
<name>C</name>
<id>2</id>
</config>
</admin-group>
<admin-group>
<name>D</name>
<id>3</id>
<config>
<name>D</name>
<id>3</id>
</config>
</admin-group>
<admin-group>
<name>E</name>
<id>4</id>
<config>
<name>E</name>
<id>4</id>
</config>
</admin-group>
</admin-groups>
<mpls xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-mpls">
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
</config>
<label-switching>
<config>
<enable/>
</config>
</label-switching>
<mpls-interface-bandwidth>
<config>
<admin-group-name>A</admin-group-name>
<admin-group-name>B</admin-group-name>
<admin-group-name>C</admin-group-name>
</config>
</mpls-interface-bandwidth>
</interface>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<label-switching>
<config>
<enable/>
</config>
</label-switching>
<mpls-interface-bandwidth>
<config>
<admin-group-name>D</admin-group-name>
<admin-group-name>E</admin-group-name>
</config>
</mpls-interface-bandwidth>
</interface>
</interfaces>
</mpls>
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
<srlg>
<config>
<srlg-disjoint>preferred</srlg-disjoint>
</config>
</srlg>
</rsvp-instance>
<rsvp-paths>
<rsvp-path>
<path-name>P1</path-name>
<config>
<path-name>P1</path-name>
<path-type>mpls</path-type>
</config>
</rsvp-path>
</rsvp-paths>
<trunks>
<ingress-trunks>
<ingress-trunk>
<trunk-name>T1</trunk-name>
<config>
<trunk-name>T1</trunk-name>
<egress>192.168.0.90</egress>
<trunk-family>ipv4</trunk-family>
</config>
<sessions>
<session>
<trunk-session-type>primary</trunk-session-type>
<config>
<trunk-session-type>primary</trunk-session-type>
<disable-cspf/>
</config>
<admin-groups>
<admin-group>
<name>A</name>
<config>
<name>A</name>
<type>include-any</type>
</config>
</admin-group>
<admin-group>
<name>C</name>
<config>
<name>C</name>
<type>include-any</type>
</config>
</admin-group>
</admin-groups>
<path-state-block>
<config>
<path-name>P1</path-name>
</config>
</path-state-block>
</session>
</sessions>
</ingress-trunk>
</ingress-trunks>
</trunks>
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
<enable-rsvp/>
</config>
</interface>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
<enable-rsvp/>
</config>
</interface>
</interfaces>
</rsvp-te>