Configuring LDP Discovery
Configuring LDP Discovery Hello Interval
Configuring LDP Discovery Hello Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryHello": {
"attributes": {
"helloIntvl": "10"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoveryhello-items>
<helloIntvl>10</helloIntvl>
</discoveryhello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
discovery hello interval 10
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryHello | sys/ldp/discovery/discoveryhello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryHello Properties
The following table contains information about the mplsldpDiscoveryHello 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 |
|---|---|---|---|
| helloIntvl | mplsldp:IntvlTime (scalar:Uint16) | LDP discovery Hello interval defines the period of time between the sending of consecutive hello messages. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 5 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting LDP Discovery Hello Interval
Deleting LDP Discovery Hello Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryHello": {
"attributes": {
"helloIntvl": "5"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoveryhello-items>
<helloIntvl>5</helloIntvl>
</discoveryhello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
no discovery hello interval 10
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryHello | sys/ldp/discovery/discoveryhello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryHello Properties
The following table contains information about the mplsldpDiscoveryHello 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 |
|---|---|---|---|
| helloIntvl | mplsldp:IntvlTime (scalar:Uint16) | LDP discovery Hello interval defines the period of time between the sending of consecutive hello messages. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 5 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Router to Respond to Requests for Targeted-Hello Messages from All Neighbors
Configuring the Router to Respond to Requests for Targeted-Hello Messages from All Neighbors
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"children": [
{
"mplsldpDisTgtHelloAccept": {
"attributes": {
"accept": "yes",
"pfxList": ""
}}}]}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<distgthelloaccept-items>
<accept>true</accept>
<pfxList></pfxList>
</distgthelloaccept-items>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
discovery targeted-hello accept
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
| mplsldpDisTgtHelloAccept | sys/ldp/discovery/discoverytgthello/distgthelloaccept |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDisTgtHelloAccept Properties
The following table contains information about the mplsldpDisTgtHelloAccept 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 |
|---|---|---|---|
| accept | scalar:Bool | The accept property configures the router to respond to requests for targeted-hello messages from all neighbors | SELECTION: true or false DEFAULT: true |
| pfxList | mplsldp:LdpPrefixListName (string:Basic) | Neighbor prefix list to specify acceptable targeted hello sources | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Router to Respond to Requests for Targeted-Hello Messages from All Neighbors
Deleting the Router to Respond to Requests for Targeted-Hello Messages from All Neighbors
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"children": [
{
"mplsldpDisTgtHelloAccept": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<distgthelloaccept-items nc:operation="delete">
</distgthelloaccept-items>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
no discovery targeted-hello accept
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
| mplsldpDisTgtHelloAccept | sys/ldp/discovery/discoverytgthello/distgthelloaccept |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDisTgtHelloAccept Properties
The following table contains information about the mplsldpDisTgtHelloAccept 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 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Router to Respond to Requests for Targeted-Hello Messages from Neighbors Specified by the Prefix List
Configuring the Router to Respond to Requests for Targeted-Hello Messages from Neighbors Specified by the Prefix List
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"children": [
{
"mplsldpDisTgtHelloAccept": {
"attributes": {
"pfxList": "prefix"
}}}]}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<distgthelloaccept-items>
<pfxList>prefix</pfxList>
</distgthelloaccept-items>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
discovery targeted-hello accept from prefix
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
| mplsldpDisTgtHelloAccept | sys/ldp/discovery/discoverytgthello/distgthelloaccept |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDisTgtHelloAccept Properties
The following table contains information about the mplsldpDisTgtHelloAccept 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 |
|---|---|---|---|
| pfxList | mplsldp:LdpPrefixListName (string:Basic) | Neighbor prefix list to specify acceptable targeted hello sources | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Router to Respond to Requests for Targeted-Hello Messages from Neighbors Specified by the Prefix List
Deleting the Router to Respond to Requests for Targeted-Hello Messages from Neighbors Specified by the Prefix List
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"children": [
{
"mplsldpDisTgtHelloAccept": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<distgthelloaccept-items nc:operation="delete">
</distgthelloaccept-items>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
no discovery targeted-hello accept from prefix
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
| mplsldpDisTgtHelloAccept | sys/ldp/discovery/discoverytgthello/distgthelloaccept |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDisTgtHelloAccept Properties
The following table contains information about the mplsldpDisTgtHelloAccept 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 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Discovery Hello Holdtime for Nondirectly Connected LDP Sessions
Configuring Discovery Hello Holdtime for Nondirectly Connected LDP Sessions
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"attributes": {
"tgtHelloHoldtime": "50"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<tgtHelloHoldtime>50</tgtHelloHoldtime>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
discovery targeted-hello holdtime 50
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryTgtHello Properties
The following table contains information about the mplsldpDiscoveryTgtHello 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 |
|---|---|---|---|
| tgtHelloHoldtime | mplsldp:TgtHoldTime (scalar:Uint16) | LDP discovery Targeted Hello holdtime defines the period of time that a discovered LDP neighbor is remembered without receipt of an LDP hello message from the neighbor. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 90 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Discovery Hello Holdtime for Nondirectly Connected LDP Sessions
Deleting Discovery Hello Holdtime for Nondirectly Connected LDP Sessions
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"attributes": {
"tgtHelloHoldtime": "90"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<tgtHelloHoldtime>90</tgtHelloHoldtime>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
no discovery targeted-hello holdtime 50
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryTgtHello Properties
The following table contains information about the mplsldpDiscoveryTgtHello 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 |
|---|---|---|---|
| tgtHelloHoldtime | mplsldp:TgtHoldTime (scalar:Uint16) | LDP discovery Targeted Hello holdtime defines the period of time that a discovered LDP neighbor is remembered without receipt of an LDP hello message from the neighbor. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 90 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Discovery Hello Interval for Nondirectly Connected LDP Sessions
Configuring Discovery Hello Interval for Nondirectly Connected LDP Sessions
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"attributes": {
"tgtHelloIntvl": "15"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<tgtHelloIntvl>15</tgtHelloIntvl>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
discovery targeted-hello interval 15
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryTgtHello Properties
The following table contains information about the mplsldpDiscoveryTgtHello 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 |
|---|---|---|---|
| tgtHelloIntvl | mplsldp:TgtIntvlTime (scalar:Uint16) | LDP discovery Targeted Hello interval defines the period of time between the sending of consecutive hello messages. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 10 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Discovery Hello Interval for Nondirectly Connected LDP Sessions
Deleting Discovery Hello Interval for Nondirectly Connected LDP Sessions
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryTgtHello": {
"attributes": {
"tgtHelloIntvl": "10"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoverytgthello-items>
<tgtHelloIntvl>10</tgtHelloIntvl>
</discoverytgthello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
no discovery targeted-hello interval 15
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryTgtHello | sys/ldp/discovery/discoverytgthello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryTgtHello Properties
The following table contains information about the mplsldpDiscoveryTgtHello 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 |
|---|---|---|---|
| tgtHelloIntvl | mplsldp:TgtIntvlTime (scalar:Uint16) | LDP discovery Targeted Hello interval defines the period of time between the sending of consecutive hello messages. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 10 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring LDP Discovery Hello Holdtime
Configuring LDP Discovery Hello Holdtime
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryHello": {
"attributes": {
"helloHoldtime": "100"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoveryhello-items>
<helloHoldtime>100</helloHoldtime>
</discoveryhello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
discovery hello holdtime 100
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryHello | sys/ldp/discovery/discoveryhello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryHello Properties
The following table contains information about the mplsldpDiscoveryHello 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 |
|---|---|---|---|
| helloHoldtime | mplsldp:HelloHoldTime (scalar:Uint16) | LDP discovery Hello holdtime defines the period of time that a discovered LDP neighbor is remembered without receipt of an LDP hello message from the neighbor. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 15 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting LDP Discovery Hello Holdtime
Deleting LDP Discovery Hello Holdtime
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"mplsldpLDP": {
"attributes": {
"adminSt": "enabled"
},
"children": [
{
"mplsldpDiscovery": {
"children": [
{
"mplsldpDiscoveryHello": {
"attributes": {
"helloHoldtime": "15"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<ldp-items>
<adminSt>enabled</adminSt>
<discovery-items>
<discoveryhello-items>
<helloHoldtime>15</helloHoldtime>
</discoveryhello-items>
</discovery-items>
</ldp-items>
</System>
Note: This example was added in Release 9.3(3).
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.
mpls ldp configuration
no discovery hello holdtime 100
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 |
| mplsldpLDP | sys/ldp |
| mplsldpDiscovery | sys/ldp/discovery |
| mplsldpDiscoveryHello | sys/ldp/discovery/discoveryhello |
mplsldpLDP Properties
The following table contains information about the mplsldpLDP 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 |
mplsldpDiscoveryHello Properties
The following table contains information about the mplsldpDiscoveryHello 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 |
|---|---|---|---|
| helloHoldtime | mplsldp:HelloHoldTime (scalar:Uint16) | LDP discovery Hello holdtime defines the period of time that a discovered LDP neighbor is remembered without receipt of an LDP hello message from the neighbor. The range is from 1 to 65535 seconds | RANGE: [1 , 65535] DEFAULT: 15 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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: