Configuring LACP

This section contains payload examples to demonstrate how to use the NX-API REST API to configure LACP on the Cisco Nexus 3000 and 9000 Series switches.

Enabling LACP

Enabling LACP

POST http://<IP_Address>/api/mo/sys/fm.json

{
"fmEntity": {
  "children": [
    {
      "fmLacp": {
        "attributes": {
          "adminSt": "enabled"
}}}]}}      

{
    imdata": []
}

<System>
  <fm-items>
    <lacp-items>
      <adminSt>enabled</adminSt>
    </lacp-items>
  </fm-items>
</System>


CLI Command

The CLI command below is the equivalent to the payload example displayed in the pane on the right.

feature lacp

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
fmEntity sys/fm
fmLacp sys/fm/lacp


fmLacp Properties

The following table contains information about the fmLacp 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 NameData TypeDescriptionValues
adminStfm:AdminState
(scalar:Enum8)		Admin statusSELECTION:
1 - enabled
2 - disabled
DEFAULT: disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Disabling LACP

Disabling LACP

POST http://<IP_Address>/api/mo/sys/fm.json

{
"fmEntity": {
  "children": [
    {
      "fmLacp": {
        "attributes": {
          "adminSt": "disabled"
}}}]}}      

{
    imdata": []
}

<System>
  <fm-items>
    <lacp-items>
      <adminSt>disabled</adminSt>
    </lacp-items>
  </fm-items>
</System>


CLI Command

The CLI command below is the equivalent to the payload example displayed in the pane on the right.

no feature lacp

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
fmEntity sys/fm
fmLacp sys/fm/lacp


fmLacp Properties

The following table contains information about the fmLacp 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 NameData TypeDescriptionValues
adminStfm:AdminState
(scalar:Enum8)		Admin statusSELECTION:
1 - enabled
2 - disabled
DEFAULT: disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring LACP Rate Fast

Configuring LACP Rate Fast

POST http://<IP_Address>/api/mo/sys/lacp.json

{
"lacpEntity": {
  "children": [
    {
      "lacpInst": {
        "children": [
          {
            "lacpIf": {
              "attributes": {
                "id": "eth1/2",
                "txRate": "fast"

}}}]}}]}}     

{
    imdata": []
}

<System>
  <lacp-items>
    <inst-items>
      <if-items>
        <If-list>
          <id>eth1/2</id>
          <txRate>fast</txRate>
        </If-list>
      </if-items>
    </inst-items>
  </lacp-items>
</System>

The LACP rate fast feature is used to set the rate (once every second) at which the LACP control packets are sent to an LACP-supported interface.


CLI Command

The CLI command below is the equivalent to the payload example displayed in the pane on the right.

interface ethernet 1/2
 lacp rate fast

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
lacpEntity sys/lacp
lacpInst sys/lacp/inst
lacpIf sys/lacp/inst/if-{[id]}


lacpIf Properties

The following table contains information about the lacpIf 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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
txRatelacp:TxRate
(scalar:Enum8)		Specifies the rate at which the LACP packets are transmitted.SELECTION:
1 - normal
2 - fast
DEFAULT: normal


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring LACP Rate Normal

Configuring LACP Rate Normal

POST http://<IP_Address>/api/mo/sys/lacp.json

{
"lacpEntity": {
  "children": [
    {
      "lacpInst": {
        "children": [
          {
            "lacpIf": {
              "attributes": {
                "id": "eth1/2",
                "txRate": "normal"

}}}]}}]}}     

{
    imdata": []
}

<System>
  <lacp-items>
    <inst-items>
      <if-items>
        <If-list>
          <id>eth1/2</id>
          <txRate>normal</txRate>
        </If-list>
      </if-items>
    </inst-items>
  </lacp-items>
</System>

Specifies that LACP control packets are ingressed at the normal rate, every 30 seconds after the link is bundled.


CLI Command

The CLI command below is the equivalent to the payload example displayed in the pane on the right.

interface ethernet 1/2
 lacp rate normal

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
lacpEntity sys/lacp
lacpInst sys/lacp/inst
lacpIf sys/lacp/inst/if-{[id]}


lacpIf Properties

The following table contains information about the lacpIf 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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
txRatelacp:TxRate
(scalar:Enum8)		Specifies the rate at which the LACP packets are transmitted.SELECTION:
1 - normal
2 - fast
DEFAULT: normal


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the MAC Address to be Used for the LACP Protocol Exchanges (Role: Primary)

Configuring the MAC Address to be Used for the LACP Protocol Exchanges (Role: Primary)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "lacpEntity": {
    "children": [
      {
        "lacpInst": {
          "attributes": {
            "adminRole": "primary",
            "adminSysMac": "12:34:12:34:12:34"
}}}]}}

{
    "imdata": []
}

<System>
  <lacp-items>
    <inst-items>
      <adminRole>primary</adminRole>
      <adminSysMac>12:34:12:34:12:34</adminSysMac>
    </inst-items>
  </lacp-items>
</System>


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.

lacp system-mac 1234.1234.1234 role primary

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
lacpEntity sys/lacp
lacpInst sys/lacp/inst


lacpInst Properties

The following table contains information about the lacpInst 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 NameData TypeDescriptionValues
adminRolelacp:SysRole
(scalar:Enum8)		System RoleSELECTION:
1 - primary
2 - secondary
DEFAULT: primary
adminSysMaclacp:SysMac
(address:MAC)		System MACValue must match MM:MM:MM:SS:SS:SS format


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the MAC Address to be Used for the LACP Protocol Exchanges (Role: Secondary)

Configuring the MAC Address to be Used for the LACP Protocol Exchanges (Role: Secondary)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "lacpEntity": {
    "children": [
      {
      "lacpInst": {
        "attributes": {
          "adminRole": "secondary",
          "adminSysMac": "12:34:12:34:12:34"
}}}]}}

{
    "imdata": []
}

<System>
  <lacp-items>
    <inst-items>
      <adminRole>secondary</adminRole>
      <adminSysMac>12:34:12:34:12:34</adminSysMac>
    </inst-items>
  </lacp-items>
</System>


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.

lacp system-mac 1234.1234.1234 role secondary

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
lacpEntity sys/lacp
lacpInst sys/lacp/inst


lacpInst Properties

The following table contains information about the lacpInst 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 NameData TypeDescriptionValues
adminRolelacp:SysRole
(scalar:Enum8)		System RoleSELECTION:
1 - primary
2 - secondary
DEFAULT: primary
adminSysMaclacp:SysMac
(address:MAC)		System MACValue must match MM:MM:MM:SS:SS:SS format


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Resetting to Use the Default VDC MAC Address

Resetting to Use the Default VDC MAC Address

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "lacpEntity": {
    "children": [
      {
        "lacpInst": {
          "attributes": {
            "adminRole": "primary",
            "adminSysMac": "00:50:56:8A:67:9F"
}}}]}}

{
    "imdata": []
}

<System>
  <lacp-items>
    <inst-items>
      <adminRole>primary</adminRole>
      <adminSysMac>00:50:56:8A:67:9F</adminSysMac>
    </inst-items>
  </lacp-items>
</System>


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 lacp system-mac

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
lacpEntity sys/lacp
lacpInst sys/lacp/inst


lacpInst Properties

The following table contains information about the lacpInst 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 NameData TypeDescriptionValues
adminRolelacp:SysRole
(scalar:Enum8)		System RoleSELECTION:
1 - primary
2 - secondary
DEFAULT: primary
adminSysMaclacp:SysMac
(address:MAC)		System MACValue must match MM:MM:MM:SS:SS:SS format


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Querying the LACP Configuration

Querying the LACP Configuration

GET http://<IP_Address>/api/node/mo/sys/lacp/inst.json

{
  "totalCount": "1",
  "imdata": [
    {
      "lacpInst": {
        "attributes": {
          "adminPrio": "32768",
          "adminSt": "enabled",
          "childAction": "",
          "ctrl": "",
          "dn": "sys/lacp/inst",
          "lacpctrl": "",
          "modTs": "2016-10-12T14:40:10.978+00:00",
          "monPolDn": "uni/fabric/monfab-default",
          "name": "",
          "operErr": "",
          "operPrio": "32768",
          "persistentOnReload": "true",
          "status": "",
          "sysMac": "00:00:00:00:00:00",
          "uid": "0"
        }
      }
    }
  ]
}

Note: The property information for this example was added in Release 9.3(3).


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.

MODN
lacpInst sys/lacp/inst


lacpInst Properties

The following table contains information about the lacpInst 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 NameData TypeDescriptionValues
adminPriolacp:SysPrio
(scalar:Uint16)		Specifies the LACP instance administrative system priority.
RANGE: [1 , 65535]
DEFAULT: 32768
adminSt
nw:AdminSt
scalar:Enum8		The administrative state of the object or policy.SELECTION:
  • 1 - enabled
  • 2 - disabled
  • DEFAULT: enabled(1)
    • childAction
    mo:ModificationChildAction
    scalar:Bitmask32    		Delete or ignore. For internal use only.SELECTION:
  • 16384u - deleteAll
  • 4096u - ignore
  • 8192u - deleteNonPresent
  • DEFAULT: 0
    • ctrl
    nw:InstCtrl
    scalar:Bitmask64    		The control state.SELECTION:
  • 1ull - stateful-ha
  • DEFAULT: 0
    • dn
    reference:BinRef    		A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module.
    lacpctrllacp:LACPInstCtrl
    (scalar:Bitmask32)    		Instance ControlSELECTION:
    1 - rapid-transition
    modTsmo:TStamp
    (scalar:Date)    		The time when this object was last modified.SELECTION:
    0 - never
    DEFAULT: never
    monPolDn
    reference:BinRef    		The monitoring policy attached to this observable object.
    name
    naming:Name256
    string:Basic    		The name of the object. RANGE: Min: "0" Max: "128"
    operErrnw:OperErrQual
    (scalar:Bitmask64)    		Operational Errors QualifierSELECTION:
    1 - init-err
    2 - mem-err
    4 - ipc-err
    8 - int-err
    16 - sock-err
    32 - proto-err
    operPriolacp:SysPrio
    (scalar:Uint16)    		Specifies the LACP instance operational system priority.
    RANGE: [1 , 65535]
    DEFAULT: 32768
    persistentOnReload
    mo:Persistent
    scalar:Enum8    		NO COMMENTSSELECTION:
  • 0 - false
  • 1 - true
  • DEFAULT: true(1)
    • statusmo:ModificationStatus
    (scalar:Bitmask32)    		The upgrade status. This property is for internal use only.SELECTION:
    2 - created
    4 - modified
    8 - deleted
    16 - replaced
    sysMaclacp:SysMac
    (address:MAC)    		Specifies the instance System MAC.Value must match MM:MM:MM:SS:SS:SS format
    uid
    scalar:Uint16    		A unique identifier for this object.


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    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:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring Delayed LACP on the Port Channel

    Configuring Delayed LACP on the Port Channel

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
  "interfaceEntity": {
    "children": [
      {
        "pcAggrIf": {
          "attributes": {
            "id": "po123",
            "lacpDelayMode": "enable"
}}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <lacpDelayMode>enable</lacpDelayMode>
      </AggrIf-list>
    </aggr-items>
  </intf-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.

    interface port-channel 123
      lacp mode delay


    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.

    MODN
    interfaceEntity sys/intf
    pcAggrIf sys/intf/aggr-[po123]


    pcAggrIf Properties

    The following table contains information about the pcAggrIf 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 NameData TypeDescriptionValues
    idnw:IfId
    (base:IfIndex)    		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
    lacpDelayModescalar:Enum8
    		Configuring LACP delay mode
    DEFAULT: disable


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    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:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting Delayed LACP on the Port Channel

    Deleting Delayed LACP on the Port Channel

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
  "interfaceEntity": {
    "children": [
      {
        "pcAggrIf": {
          "attributes": {
            "id": "po123",
            "lacpDelayMode": "disable"
}}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <lacpDelayMode>disable</lacpDelayMode>
      </AggrIf-list>
    </aggr-items>
  </intf-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.

    interface port-channel 123
      no lacp mode delay


    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.

    MODN
    interfaceEntity sys/intf
    pcAggrIf sys/intf/aggr-[po123]


    pcAggrIf Properties

    The following table contains information about the pcAggrIf 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 NameData TypeDescriptionValues
    idnw:IfId
    (base:IfIndex)    		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
    lacpDelayModescalar:Enum8
    		Configuring LACP delay mode
    DEFAULT: disable


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    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:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring Delayed LACP on the Port Channel

    Configuring Delayed LACP on the Port Channel

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
  "interfaceEntity": {
    "children": [
      {
        "pcAggrIf": {
          "attributes": {
            "id": "po123",
            "lacpDelayMode": "enable",
            "layer": "Layer2",
            "userCfgdFlags": "admin_layer"
}}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <lacpDelayMode>enable</lacpDelayMode>
        <layer>Layer2</layer>
        <userCfgdFlags>admin_layer</userCfgdFlags>
      </AggrIf-list>
    </aggr-items>
  </intf-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.

    interface port-channel 123
      switchport
       lacp mode delay


    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.

    MODN
    interfaceEntity sys/intf
    pcAggrIf sys/intf/aggr-[po123]


    pcAggrIf Properties

    The following table contains information about the pcAggrIf 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 NameData TypeDescriptionValues
    idnw:IfId
    (base:IfIndex)    		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
    lacpDelayModescalar:Enum8
    		Configuring LACP delay mode
    DEFAULT: disable
    layerl1:Layer
    (scalar:Enum8)    		Administrative port layerSELECTION:
    1 - Layer2
    2 - Layer3
    DEFAULT: pltfmDfltLayer
    userCfgdFlagsl1:userCfgdFlags
    (scalar:Bitmask8)    		Port User Config FlagsSELECTION:
    0 - none
    1 - admin_state
    2 - admin_layer
    4 - admin_router_mac
    8 - admin_dce_mode
    16 - admin_mtu
    DEFAULT: none


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    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:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting Delayed LACP on the Port Channel

    Deleting Delayed LACP on the Port Channel

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
  "interfaceEntity": {
    "children": [
      {
        "pcAggrIf": {
          "attributes": {
            "id": "po123",
            "lacpDelayMode": "disable",
            "layer": "Layer2",
            "userCfgdFlags": "admin_layer"
}}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <lacpDelayMode>disable</lacpDelayMode>
        <layer>Layer2</layer>
        <userCfgdFlags>admin_layer</userCfgdFlags>
      </AggrIf-list>
    </aggr-items>
  </intf-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.

    interface port-channel 123
      switchport
       no lacp mode delay


    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.

    MODN
    interfaceEntity sys/intf
    pcAggrIf sys/intf/aggr-[po123]


    pcAggrIf Properties

    The following table contains information about the pcAggrIf 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 NameData TypeDescriptionValues
    idnw:IfId
    (base:IfIndex)    		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
    lacpDelayModescalar:Enum8
    		Configuring LACP delay mode
    DEFAULT: disable
    layerl1:Layer
    (scalar:Enum8)    		Administrative port layerSELECTION:
    1 - Layer2
    2 - Layer3
    DEFAULT: pltfmDfltLayer
    userCfgdFlagsl1:userCfgdFlags
    (scalar:Bitmask8)    		Port User Config FlagsSELECTION:
    0 - none
    1 - admin_state
    2 - admin_layer
    4 - admin_router_mac
    8 - admin_dce_mode
    16 - admin_mtu
    DEFAULT: none


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    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:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html