Configuring MPLS Layer 3 VPN Load Balancing
Load balancing distributes traffic so that no individual router is overburdened. In an MPLS Layer 3 network, you can achieve load balancing by using the Border Gateway Protocol (BGP). When multiple iBGP paths are installed in a routing table, a route reflector advertises only one path (next hop). If a router is behind a route reflector, all routes that are connected to multihomed sites are not advertised unless a different route distinguisher is configured for each virtual routing and forwarding instance (VRF). (A route reflector passes learned routes to neighbors so that all iBGP peers do not need to be fully meshed.).
For more information, see the Cisco Nexus 9000 Series NX-OS Label Switching Configuration Guide:
Configuring Label-IP Load Balancing
Configuring Label-IP Load Balancing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"pcMplsLbLabelIp": "LABEL_IP"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<pcMplsLbLabelIp>LABEL_IP</pcMplsLbLabelIp>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(1).
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 load-sharing label-ip
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 |
---|---|
platformEntity | sys/pltfm |
topSystem | sys |
platformEntity Properties
The following table contains information about the platformEntity 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 |
---|---|---|---|
pcMplsLbLabelIp | platform:PcMplsLbLabelIp (scalar:Enum8) | Mpls load-balance label ip | SELECTION: 0 - DEFAULT 1 - LABEL_IP DEFAULT: DEFAULT |
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 Label-IP Load Balancing
Deleting Label-IP Load Balancing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"pcMplsLbLabelIp": "DEFAULT"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<pcMplsLbLabelIp>DEFAULT</pcMplsLbLabelIp>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no mpls load-sharing label-ip
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 |
---|---|
platformEntity | sys/pltfm |
topSystem | sys |
platformEntity Properties
The following table contains information about the platformEntity 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 |
---|---|---|---|
pcMplsLbLabelIp | platform:PcMplsLbLabelIp (scalar:Enum8) | Mpls load-balance label ip | SELECTION: 0 - DEFAULT 1 - LABEL_IP DEFAULT: DEFAULT |
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 Label-Only Load Balancing
Configuring Label-Only Load Balancing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"pcMplsLbLabelOnly": "LABEL_ONLY"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<pcMplsLbLabelOnly>LABEL_ONLY</pcMplsLbLabelOnly>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(1).
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 load-sharing label-only
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 |
---|---|
platformEntity | sys/pltfm |
topSystem | sys |
platformEntity Properties
The following table contains information about the platformEntity 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 |
---|---|---|---|
pcMplsLbLabelOnly | platform:PcMplsLbLabelOnly (scalar:Enum8) | Mpls load-balance label only | SELECTION: 0 - DEFAULT 1 - LABEL_ONLY DEFAULT: DEFAULT |
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 Label-Only Load Balancing
Deleting Label-Only Load Balancing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"pcMplsLbLabelOnly": "DEFAULT"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<pcMplsLbLabelOnly>DEFAULT</pcMplsLbLabelOnly>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no mpls load-sharing label-only
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 |
---|---|
platformEntity | sys/pltfm |
topSystem | sys |
platformEntity Properties
The following table contains information about the platformEntity 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 |
---|---|---|---|
pcMplsLbLabelOnly | platform:PcMplsLbLabelOnly (scalar:Enum8) | Mpls load-balance label only | SELECTION: 0 - DEFAULT 1 - LABEL_ONLY DEFAULT: DEFAULT |
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: