RSVP-TE OpenConfig Translation
General Restrictions
The general restrictions are as follows:
• RSVP-TE configuration is always given in “default” network-instance.
• 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 RSVP-TE Instance
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to create an RSVP-TE router instance.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to create an RSVP-TE router instance.
<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>
OcNOS CLI Command
The below CLI command is used to create an RSVP-TE router instance.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to create an RSVP-TE router instance.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-network-instance">
<network-instance>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
</network-instance>
<network-instance>
<instance-name>management</instance-name>
<instance-type>vrf</instance-type>
</network-instance>
</network-instances>
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
</rsvp-instance>
</rsvp-te>
Configure RSVP-TE hello-interval
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to configure the hello-interval attribute for a given RSVP-TE router.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to configure the hello-interval attribute for a given RSVP-TE router.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<config>
<name>default</name>
<type xmlns:oc-ni-types="http://openconfig.net/yang/network-instance-types">oc-ni-types:DEFAULT_INSTANCE</type>
</config>
<mpls>
<signaling-protocols>
<rsvp-te>
<global>
<hellos>
<config>
<hello-interval>1</hello-interval>
</config>
</hellos>
</global>
</rsvp-te>
</signaling-protocols>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to configure the hello-interval attribute for a given RSVP-TE router.
OcNOS#show running-config rsvp
!
router rsvp
hello-interval 1
srlg-disjoint preferred
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to configure the hello-interval attribute for a given RSVP-TE router.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-network-instance">
<network-instance>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
<vrf xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-vrf">
<config>
<vrf-name>default</vrf-name>
</config>
</vrf>
<config>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
</config>
</network-instance>
</network-instances>
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<global>
<hellos>
<config>
<hello-interval>1</hello-interval>
</config>
</hellos>
</global>
<config>
<rsvp>rsvp</rsvp>
</config>
</rsvp-instance>
</rsvp-te>
Enable RSVP-TE Signaling on an Interface
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuratio
Use this configuration to enable RSVP-TE signaling on a given interface.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to enable RSVP-TE signaling on a given interface.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<config>
<name>default</name>
<type xmlns:oc-ni-types="http://openconfig.net/yang/network-instance-types">oc-ni-types:DEFAULT_INSTANCE</type>
</config>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled />
</config>
<interface-attributes>
<interface>
<interface-id>xe1</interface-id>
<config>
<interface-id>xe1</interface-id>
</config>
</interface>
</interface-attributes>
</rsvp-te>
</signaling-protocols>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to enable RSVP-TE signaling on a given interface.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
interface xe1
enable-rsvp
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to enable RSVP-TE signaling on a given interface.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-network-instance">
<network-instance>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
<vrf xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-vrf">
<config>
<vrf-name>default</vrf-name>
</config>
</vrf>
<config>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
</config>
</network-instance>
</network-instances>
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
</rsvp-instance>
<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
<enable-rsvp />
</config>
</interface>
</interfaces>
</rsvp-te>
Configure RSVP-TE hello-interval on an Interface
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to configure RSVP-TE hello-interval on a given interface. This configuration overrides the hello-interval configured for the RSVP-TE router instance.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to configure RSVP-TE hello-interval on a given interface.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<config>
<name>default</name>
<type xmlns:oc-ni-types="http://openconfig.net/yang/network-instance-types">oc-ni-types:DEFAULT_INSTANCE</type>
</config>
<mpls>
<signaling-protocols>
<rsvp-te>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled />
</config>
<interface-attributes>
<interface>
<interface-id>xe1</interface-id>
<interface-ref>
<config>
<interface>xe1</interface>
</config>
</interface-ref>
<config>
<interface-id>xe1</interface-id>
</config>
<hellos>
<config>
<hello-interval>1</hello-interval>
</config>
</hellos>
</interface>
</interface-attributes>
</rsvp-te>
</signaling-protocols>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to configure RSVP-TE hello-interval on a given interface.
OcNOS#show running-config rsvp
!
router rsvp
srlg-disjoint preferred
!
interface xe1
enable-rsvp
rsvp hello-interval 1
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to configure RSVP-TE hello-interval on a given interface.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-network-instance">
<network-instance>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
<vrf xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-vrf">
<config>
<vrf-name>default</vrf-name>
</config>
</vrf>
<config>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
</config>
</network-instance>
</network-instances>
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<config>
<rsvp>rsvp</rsvp>
</config>
</rsvp-instance>
<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
<enable-rsvp />
</config>
<hellos>
<config>
<hello-interval>1</hello-interval>
</config>
</hellos>
</interface>
</interfaces>
</rsvp-te>
Configure RSVP-TE Graceful-restart
Release
This configuration was introduced in OcNOS version 6.6.0.
Configuration
Use this configuration to configure RSVP-TE graceful-restart attribute.
OpenConfig NetConf Payload
Here is a sample OpenConfig NetConf Payload to configure RSVP-TE graceful-restart attribute.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<config>
<name>default</name>
<type xmlns:oc-ni-types="http://openconfig.net/yang/network-instance-types">oc-ni-types:DEFAULT_INSTANCE</type>
</config>
<mpls>
<signaling-protocols>
<rsvp-te>
<global>
<graceful-restart>
<config>
<enable>true</enable>
<restart-time>10000</restart-time>
</config>
</graceful-restart>
</global>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-augments">
<enabled />
</config>
</rsvp-te>
</signaling-protocols>
</mpls>
</network-instance>
</network-instances>
OcNOS CLI Command
The below CLI command is used to configure RSVP-TE graceful-restart attribute.
OcNOS#show running-config rsvp
!
router rsvp
graceful-restart
graceful-restart restart-time 10000
srlg-disjoint preferred
!
OcNOS NetConf Payload
Here is a sample OcNOS NetConf Payload to configure RSVP-TE graceful-restart attribute.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-network-instance">
<network-instance>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
<vrf xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-vrf">
<config>
<vrf-name>default</vrf-name>
</config>
</vrf>
<config>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
</config>
</network-instance>
</network-instances>
<rsvp-te xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-rsvp">
<rsvp-instance>
<global>
<graceful-restart>
<config>
<enable-graceful-restart />
<restart-time>10000</restart-time>
</config>
</graceful-restart>
</global>
<config>
<rsvp>rsvp</rsvp>
</config>
</rsvp-instance>
</rsvp-te>