show port-channel compatibility-parameters
show port-channel compatibility-parameters
import json
"""
Modify these please
"""
url='http://<IP_Address>/ins'
switchuser='<User_ID>'
switchpassword='<Password>'
myheaders={'content-type':'application/json'}
payload={
"ins_api":{
"version": "1.0",
"type": "cli_show",
"chunk": "0",
"sid": "1",
"input": "show port-channel compatibility-parameters ",
"output_format": "json"
}
response = requests.post(url,data=json.dumps(payload), headers=myheaders,auth=(switchuser,switchpassword)).json()
output = json.dumps(response, indent=4, sort_keys=True)
{
"ins_api": {
"type": "cli_show",
"version": "1.0",
"sid": "eoc",
"outputs": {
"output": {
"input": "show port-channel compatibility-parameters ",
"msg": "Success",
"code": "200",
"body": {
"TABLE_compatibility": {
"ROW_compatibility": [
{
"parameter": "port mode",
"description": "Members must have the same port mode configured, either E,F or AUTO. If \nthey are configured in AUTO port mode, they have to negotiate E or F mode \nwhen they come up. If a member negotiates a different mode, it will be \nsuspended."
},
{
"parameter": "speed",
"description": "Members must have the same speed configured. If they are configured in AUTO \nspeed, they have to negotiate the same speed when they come up. If a member \nnegotiates a different speed, it will be suspended."
},
{
"parameter": "MTU",
"description": "Members have to have the same MTU configured. This only applies to ethernet \nport-channel."
},
{
"parameter": "MEDIUM",
"description": "Members have to have the same medium type configured. This only applies to \nethernet port-channel."
},
{
"parameter": "Span mode",
"description": "Members must have the same span mode."
},
{
"parameter": "load interval",
"description": "Member must have same load interval configured."
},
{
"parameter": "port Voice VLAN",
"description": "Members must not have voice vlan configured."
},
{
"parameter": "VLAN translation mapping list",
"description": "Members must have the same VLAN translation list."
},
{
"parameter": "sub interfaces",
"description": "Members must not have sub-interfaces."
},
{
"parameter": "Duplex Mode",
"description": "Members must have same Duplex Mode configured."
},
{
"parameter": "Ethernet Layer",
"description": "Members must have same Ethernet Layer (switchport/no-switchport) configured."
},
{
"parameter": "Span Port",
"description": "Members cannot be SPAN ports."
},
{
"parameter": "Storm Control",
"description": "Members must have same storm-control configured."
},
{
"parameter": "Switchport Block",
"description": "Members must have same switchport block configured."
},
{
"parameter": "Switchport Isolated",
"description": "Members must have same switchport isolated configured."
},
{
"parameter": "Flow Control",
"description": "Members must have same flowctrl configured."
},
{
"parameter": "Capabilities",
"description": "Members must have common capabilities."
},
{
"parameter": "Capabilities speed",
"description": "Members must have common speed capabilities."
},
{
"parameter": "Capabilities duplex",
"description": "Members must have common speed duplex capabilities."
},
{
"parameter": "Port has PVLAN config",
"description": "Members must have same pvlan configuration"
},
{
"parameter": "rate mode",
"description": "Members must have the same rate mode configured."
},
{
"parameter": "Capabilities FabricPath",
"description": "Members must have common fabricpath capability."
},
{
"parameter": "1G port is not capable of acting as peer-link",
"description": "Members must be 10G to become part of a vPC peer-link."
},
{
"parameter": "EthType",
"description": "Members must have same EthType configured."
},
{
"parameter": "shared interface",
"description": "Members can not be shared-interfaces."
},
{
"parameter": "Capabilities SpanDest",
"description": "Members must be capable of span destination configuration"
},
{
"parameter": "Module Type Incompatible",
"description": "Module type for interfaces is not compatible."
},
{
"parameter": "Port Mode Fabricpath Incompatible",
"description": "Members are Fabricpath Enforce locked, not compatible."
},
{
"parameter": "Buffer boost",
"description": "Members must have same buffer-boost configuration."
},
{
"parameter": "vmtracker enable mismatch",
"description": "Members have vmtracker enable mismatch"
},
{
"parameter": "Port Type",
"description": "Members must be all server or all fabric facing ports."
},
{
"parameter": "Sflow enabled port",
"description": "Members cannot be Sflow enabled ports"
},
{
"parameter": "Switchport Mac-learn",
"description": "Members must have same switchport mac-learn configured."
},
{
"parameter": "switchport virtual-ethernet-bridge enabled port",
"description": "Members must have same switchport virtual-ethernet-bridge configured."
},
{
"parameter": "port-type fabric",
"description": "Members must have same port-type configured."
},
{
"parameter": "port",
"description": "Members port VLAN info."
},
{
"parameter": "port",
"description": "Members port does not exist."
},
{
"parameter": "switching port",
"description": "Members must be switching port, Layer 2."
},
{
"parameter": "port access VLAN",
"description": "Members must have the same port access VLAN."
},
{
"parameter": "port native VLAN",
"description": "Members must have the same port native VLAN."
},
{
"parameter": "port allowed VLAN list",
"description": "Members must have the same port allowed VLAN list."
},
{
"parameter": "controller interface",
"description": "The interface is assigned to controller"
},
{
"parameter": "port MULTI-TAG",
"description": "Members must have allow-multi-tag configured."
},
{
"parameter": "Members should have same fex config",
"description": "Members must have same FEX configuration."
},
{
"parameter": "FEX pinning max-links not one",
"description": "FEX pinning max-links config is not one."
},
{
"parameter": "Multiple port-channels with same Fex-id",
"description": "Multiple port-channels to same FEX not allowed."
},
{
"parameter": "Pinning Params",
"description": "Members must have the same pinning parameters."
},
{
"parameter": "All HIF member ports not in same pinning group",
"description": "All HIF member ports not in same pinning group"
},
{
"parameter": "Slot in host vpc mode",
"description": "Cannot add cfged slot member to fabric po vpc."
},
{
"parameter": "Members in multiple FEX",
"description": "Members must belong to same FEX."
},
{
"parameter": "Members are of different type",
"description": "Members must of same interface type."
},
{
"parameter": "port egress queuing policy",
"description": "10G port-channel members must have the same egress queuing policy as the \nport-channel."
},
{
"parameter": "port channel egress queuing policy",
"description": "port channel egress queuing policy with fex interface memberun-supported \npolicy"
},
{
"parameter": "Port Security policy",
"description": "Members must have the same port-security enable status as port-channel"
},
{
"parameter": "Port priority-flow-control",
"description": "PFC config should be the same for all the members"
},
{
"parameter": "Dot1x policy",
"description": "Members must have host mode as multi-host with no mab configuration. Dot1X \ncannot be enabled on members when Port Security is configured on port \nchannel"
},
{
"parameter": "PVLAN port config",
"description": "Members must have same PVLAN port configuration."
},
{
"parameter": "VFC bound to member port of port channel.",
"description": "Fail to add additional interface to port channel"
},
{
"parameter": "Fex ports for span",
"description": "Port-Channel is already a SPAN source. Cannot add FEX ports connected \nthrough Ricard to this PC"
},
{
"parameter": "VNSEG VSI configured under port channel member",
"description": "Port Channel members cannot have VNSEG VSI configured under them"
},
{
"parameter": "Speed auto-negotiation",
"description": "Members must be configured to have the same auto-negotiation rules"
},
{
"parameter": "shut lan",
"description": "Members cannot have shut lan configured"
},
{
"parameter": "MACSEC compat check",
"description": "Members cannot have macsec enabled before adding to PO with macsec"
}
]
}
}
}
}
}
}
The CLI output example below corresponds to the payload example in the code pane on the right. For more information about the show port-channel compatibility-parameters command, see the CLI command reference:
Note: This example was added in Cisco NX-OS Release 9.2(1).
| CLI Output |
|---|
|
show port-channel database interface po50
show port-channel database interface po50
import json
"""
Modify these please
"""
url='http://<IP_Address>/ins'
switchuser='<User_ID>'
switchpassword='<Password>'
myheaders={'content-type':'application/json'}
payload={
"ins_api":{
"version": "1.0",
"type": "cli_show",
"chunk": "0",
"sid": "1",
"input": "show port-channel database interface po50 ",
"output_format": "json"
}
response = requests.post(url,data=json.dumps(payload), headers=myheaders,auth=(switchuser,switchpassword)).json()
output = json.dumps(response, indent=4, sort_keys=True)
{
"ins_api": {
"type": "cli_show",
"version": "1.0",
"sid": "eoc",
"outputs": {
"output": {
"input": "show port-channel database interface po50 ",
"msg": "Success",
"code": "200",
"body": {
"TABLE_interface": {
"ROW_interface": {
"interface": "port-channel50",
"last-membership-update": "successful",
"total-ports": "2",
"total-up-ports": "2",
"first_operational-port": "Ethernet1/12",
"age-of-channel": "0d:06h:24m:39s",
"time-since-last-bundle": "0d:06h:24m:48s",
"last-bundled-member": "Ethernet1/11",
"TABLE_member": {
"ROW_member": [
{
"port": "Ethernet1/11",
"mode": "active",
"port-status": "up"
},
{
"port": "Ethernet1/12",
"mode": "active",
"port-status": "up"
}
]
}
}
}
}
}
}
}
}
The CLI output example below corresponds to the payload example in the code pane on the right. For more information about the show port-channel database interface po50 command, see the CLI command reference:
Note: This example was added in Cisco NX-OS Release 9.2(1).
| CLI Output |
|---|
|
show port-channel summary
show port-channel summary
import json
"""
Modify these please
"""
url='http://<IP_Address>/ins'
switchuser='<User_ID>'
switchpassword='<Password>'
myheaders={'content-type':'application/json'}
payload={
"ins_api":{
"version": "1.0",
"type": "cli_show",
"chunk": "0",
"sid": "1",
"input": "show port-channel summary ",
"output_format": "json"
}
response = requests.post(url,data=json.dumps(payload), headers=myheaders,auth=(switchuser,switchpassword)).json()
output = json.dumps(response, indent=4, sort_keys=True)
{
"ins_api": {
"type": "cli_show",
"version": "1.0",
"sid": "eoc",
"outputs": {
"output": {
"input": "show port-channel summary ",
"msg": "Success",
"code": "200",
"body": {
"TABLE_channel": {
"ROW_channel": [
{
"group": "1",
"port-channel": "port-channel1",
"layer": "S",
"status": "U",
"type": "Eth",
"prtcl": "LACP",
"TABLE_member": {
"ROW_member": {
"port": "Ethernet1/31",
"port-status": "P"
}
}
},
{
"group": "2",
"port-channel": "port-channel2",
"layer": "S",
"status": "U",
"type": "Eth",
"prtcl": "LACP",
"TABLE_member": {
"ROW_member": [
{
"port": "Ethernet1/39",
"port-status": "P"
},
{
"port": "Ethernet1/41",
"port-status": "P"
}
]
}
}
]
}
}
}
}
}
}
The CLI output example below corresponds to the payload example in the code pane on the right. For more information about the show port-channel summary command, see the CLI command reference:
Note: This example was added in Cisco NX-OS Release 9.2(1).
| CLI Output |
|---|
|
show port-channel traffic
show port-channel traffic
import json
"""
Modify these please
"""
url='http://<IP_Address>/ins'
switchuser='<User_ID>'
switchpassword='<Password>'
myheaders={'content-type':'application/json'}
payload={
"ins_api":{
"version": "1.0",
"type": "cli_show",
"chunk": "0",
"sid": "1",
"input": "show port-channel traffic ",
"output_format": "json"
}
response = requests.post(url,data=json.dumps(payload), headers=myheaders,auth=(switchuser,switchpassword)).json()
output = json.dumps(response, indent=4, sort_keys=True)
{
"ins_api": {
"type": "cli_show",
"version": "1.0",
"sid": "eoc",
"outputs": {
"output": {
"input": "show port-channel traffic ",
"msg": "Success",
"code": "200",
"body": {
"TABLE_channel": {
"ROW_channel": [
{
"chanId": "1",
"port": "Ethernet1/31",
"rx-ucst": "100.00",
"tx-ucst": "100.00",
"rx-mcst": "100.00",
"tx-mcst": "100.00",
"rx-bcst": "0.0",
"tx-bcst": "100.00"
},
{
"chanId": "2",
"port": "Ethernet1/39",
"rx-ucst": "0.0",
"tx-ucst": "99.99",
"rx-mcst": "49.93",
"tx-mcst": "99.02",
"rx-bcst": "0.0",
"tx-bcst": "99.99"
},
{
"chanId": "2",
"port": "Ethernet1/41",
"rx-ucst": "100.00",
"tx-ucst": "0.00",
"rx-mcst": "50.06",
"tx-mcst": "0.97",
"rx-bcst": "0.0",
"tx-bcst": "0.00"
}
]
}
}
}
}
}
}
The CLI output example below corresponds to the payload example in the code pane on the right. For more information about the show port-channel traffic command, see the CLI command reference:
Note: This example was added in Cisco NX-OS Release 9.2(1).
| CLI Output |
|---|
|