Configuring Port-Channel Parameters
Configuring the Load-Defer Time Interval
Configuring the Load-Defer Time Interval
POST http://<mgmt0_IP>/api/mo/sys/pc.json
{
"pcEntity": {
"children": [
{
"pcInst": {
"attributes": {
"loadDeferTime": "351"
}}}]}}
{
imdata:[]
}
<System>
<pc-items>
<pc-items>
<loadDeferTime>351</loadDeferTime>
</pc-items>
</pc-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.
port-channel load-defer 351
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 |
---|---|
pcEntity | sys/pc |
pcInst | sys/pc/pc |
pcInst Properties
The following table contains information about the pcInst 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 |
---|---|---|---|
loadDeferTime | pc:LoadDeferTime (scalar:Uint32) | Load defer timeout | RANGE: [1 , 1800] DEFAULT: 120 |
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 Load-Defer Time Interval
Deleting the Load-Defer Time Interval
POST http://<mgmt0_IP>/api/mo/sys/pc.json
{
"pcEntity": {
"children": [
{
"pcInst": {
"attributes": {
"loadDeferTime": "120"
}}}]}}
{
imdata:[]
}
<System>
<pc-items>
<pc-items>
<loadDeferTime>120</loadDeferTime>
</pc-items>
</pc-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 port-channel load-defer 351
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 |
---|---|
pcEntity | sys/pc |
pcInst | sys/pc/pc |
pcInst Properties
The following table contains information about the pcInst 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 |
---|---|---|---|
loadDeferTime | pc:LoadDeferTime (scalar:Uint32) | Load defer timeout | RANGE: [1 , 1800] DEFAULT: 120 |
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 Port-Channel Hash-Distribution When Type Is Fixed
Configuring Port-Channel Hash-Distribution When Type Is Fixed
POST http://<mgmt0_IP>/api/mo/sys/pc.json
{
"pcEntity": {
"children": [
{
"pcInst": {
"attributes": {
"hashDist": "fixed"
}}}]}}
{
imdata:[]
}
<System>
<pc-items>
<pc-items>
<hashDist>fixed</hashDist>
</pc-items>
</pc-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.
port-channel hash-distribution fixed
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 |
---|---|
pcEntity | sys/pc |
pcInst | sys/pc/pc |
pcInst Properties
The following table contains information about the pcInst 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 |
---|---|---|---|
hashDist | pc:PCHashDist (scalar:Enum8) | Hash distribution type | SELECTION: 1 - adaptive 2 - fixed DEFAULT: adaptive |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Port-Channel Hash-Distribution When Type Is Fixed
Deleting Port-Channel Hash-Distribution When Type Is Fixed
POST http://<mgmt0_IP>/api/mo/sys/pc.json
{
"pcEntity": {
"children": [
{
"pcInst": {
"attributes": {
"hashDist": "adaptive"
}}}]}}
{
imdata:[]
}
<System>
<pc-items>
<pc-items>
<hashDist>adaptive</hashDist>
</pc-items>
</pc-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 port-channel hash-distribution fixed
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 |
---|---|
pcEntity | sys/pc |
pcInst | sys/pc/pc |
pcInst Properties
The following table contains information about the pcInst 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 |
---|---|---|---|
hashDist | pc:PCHashDist (scalar:Enum8) | Hash distribution type | SELECTION: 1 - adaptive 2 - fixed DEFAULT: adaptive |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Port-Channel Hash-Distribution When Type Is Adaptive
Configuring Port-Channel Hash-Distribution When Type Is Adaptive
POST http://<mgmt0_IP>/api/mo/sys/pc.json
{
"pcEntity": {
"children": [
{
"pcInst": {
"attributes": {
"hashDist": "adaptive"
}}}]}}
{
imdata:[]
}
<System>
<pc-items>
<pc-items>
<hashDist>adaptive</hashDist>
</pc-items>
</pc-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.
port-channel hash-distribution adaptive
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 |
---|---|
pcEntity | sys/pc |
pcInst | sys/pc/pc |
pcInst Properties
The following table contains information about the pcInst 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 |
---|---|---|---|
hashDist | pc:PCHashDist (scalar:Enum8) | Hash distribution type | SELECTION: 1 - adaptive 2 - fixed DEFAULT: adaptive |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Port-Channel Hash-Distribution When Type Is Adaptive
Deleting Port-Channel Hash-Distribution When Type Is Adaptive
POST http://<mgmt0_IP>/api/mo/sys/pc.json
{
"pcEntity": {
"children": [
{
"pcInst": {
"attributes": {
"hashDist": "adaptive"
}}}]}}
{
imdata:[]
}
<System>
<pc-items>
<pc-items>
<hashDist>adaptive</hashDist>
</pc-items>
</pc-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 port-channel hash-distribution adaptive
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 |
---|---|
pcEntity | sys/pc |
pcInst | sys/pc/pc |
pcInst Properties
The following table contains information about the pcInst 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 |
---|---|---|---|
hashDist | pc:PCHashDist (scalar:Enum8) | Hash distribution type | SELECTION: 1 - adaptive 2 - fixed DEFAULT: adaptive |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Load Balance Resilient Mode
Configuring the Load Balance Resilient Mode
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"pcLbRes": "yes"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<pcLbRes>yes</pcLbRes>
</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.
port-channel load-balance2 resilient
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 |
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 |
---|---|---|---|
pcLbRes | platform:PcLbRes (scalar:Enum8) | Pc load-balance resilient | SELECTION: 1 - yes 2 - no DEFAULT: no |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Load Balance Resilient Mode
Deleting the Load Balance Resilient Mode
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"pcLbRes": "no"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<pcLbRes>no</pcLbRes>
</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 port-channel load-balance2 resilient
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 |
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 |
---|---|---|---|
pcLbRes | platform:PcLbRes (scalar:Enum8) | Pc load-balance resilient | SELECTION: 1 - yes 2 - no DEFAULT: no |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide: