Port-Channel Commands
show port-channel summary
show port-channel summary
import requests
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.2",
"sid": "eoc",
"outputs": {
"output": {
"input": "show port-channel summary",
"msg": "Success",
"code": "200",
"body": {
"TABLE_channel": {
"ROW_channel": [{
"group": "12",
"port-channel": "port-channel12",
"layer": "S",
"status": "D",
"type": "Eth",
"prtcl": "NONE"
}, {
"group": "22",
"port-channel": "port-channel22",
"layer": "S",
"status": "U",
"type": "Eth",
"prtcl": "NONE",
"TABLE_member": {
"ROW_member": {
"port": "Ethernet9/33",
"port-status": "P"
}
}
}, {
"group": "63",
"port-channel": "port-channel63",
"layer": "R",
"status": "D",
"type": "Eth",
"prtcl": "NONE"
}, {
"group": "123",
"port-channel": "port-channel123",
"layer": "S",
"status": "D",
"type": "Eth",
"prtcl": "NONE"
}, {
"group": "154",
"port-channel": "port-channel154",
"layer": "R",
"status": "D",
"type": "Eth",
"prtcl": "NONE"
}]
}
}
}
}
}
}
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.2(1).
| CLI Output |
|---|
|
show port-channel traffic
show port-channel traffic
import requests
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.2",
"sid": "eoc",
"outputs": {
"output": {
"input": "show port-channel traffic",
"msg": "Success",
"code": "200",
"body": {
"TABLE_channel": {
"ROW_channel": {
"chanId": "22",
"port": "Ethernet9/33",
"rx-ucst": "100.00",
"tx-ucst": "100.00",
"rx-mcst": "100.00",
"tx-mcst": "100.00",
"rx-bcst": "100.00",
"tx-bcst": "100.00"
}
}
}
}
}
}
}
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.2(1).
| CLI Output |
|---|
|
show port-channel compatibility-parameters
show port-channel compatibility-parameters
import requests
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)
{
"parameter": [
"port mode",
"speed",
"MTU",
"MEDIUM",
"Span mode",
"load interval",
"span port headers",
"sub interfaces",
"Duplex Mode",
"Ethernet Layer",
"Span Port",
"Storm Control",
"Flow Control",
"Capabilities",
"Capabilities speed",
"Capabilities duplex",
"rate mode",
"Capabilities FabricPath",
"Port has PVLAN config",
"1G port is not capable of acting as peer-link",
"EthType",
"shared interface",
"Capabilities SpanDest",
"Module Type Incompatible",
"Port Mode Fabricpath Incompatible",
"Rewrite Translate - Rate Mode shared, Incompatible",
"FEX - PVLAN promiscuous config",
"vmtracker enable mismatch",
"Capabilities FEC",
"port",
"port",
"switching port",
"port access VLAN",
"port native VLAN",
"port allowed VLAN list",
"VLAN translation mapping list",
"Members should have same fex config",
"FEX pinning max-links not one",
"Multiple port-channels with same Fex-id",
"Pinning Params",
"All HIF member ports not in same pinning group",
"Slot in host vpc mode",
"Members in multiple FEX",
"Members are of different type",
"port egress queuing policy",
"Port Security policy",
"Port priority-flow-control",
"Dot1x policy",
"PC Queuing policy",
"PC Queuing policy",
"PVLAN port config",
"Emulated switch port type policy",
"Cannot add a Fex-AA port to a port-channel which already user-configured as
a vPC",
"VFC bound to port",
"VFC bound to port channel",
"VFC bound to FCoE capable port channel",
"VFC bound to FCoE capable port channel",
"EVC EFP configured under port channel member",
"Fex ports for span",
"shut lan",
"VPC orphan port suspend configured under port channel member",
"tag native",
"VNSEG VSI configured under port channel member",
"VNSEG VSI Id for FEX > 62",
"VNSEG VSI configured under port channel and VSI under FEX member have overl
apping mappings",
"VNSEG VSI Id and profile name mismatch on FEX member with those on Port-cha
nnel",
"VNSEG VSI type mismatch on FEX member with those on Port-channel",
"PLSM EDP port type policy",
"Port priority-flow-control long-distance",
"Port channel LFC-PFC compat check fail",
"CTS mode",
"CTS SGT propagation",
"CTS SGT policy",
"CTS peer identity",
"CTS SGT configuration",
"CTS replay protection",
"FEX - Storm-control config",
"MKA MACSEC compat check",
"MKA SAP compat check"
],
"description": [
"Members must have the same port mode configured, either E,F or AUTO. If \nt
hey 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.",
"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.",
"Members have to have the same MTU configured. This only applies to ethernet
\nport-channel.",
"Members have to have the same medium type configured. This only applies to
\nethernet port-channel.",
"Members must have the same span mode.",
"Member must have same load interval configured.",
"The exclude header span config must either be present or absent on all \nme
mbers.",
"Members must not have sub-interfaces.",
"Members must have same Duplex Mode configured.",
"Members must have same Ethernet Layer (switchport/no-switchport) configured
.",
"Members cannot be SPAN ports.",
"Members must have same storm-control configured.",
"Members must have same flowctrl configured.",
"Members must have common capabilities.",
"Members must have common speed capabilities.",
"Members must have common speed duplex capabilities.",
"Members must have the same rate mode configured.",
"Members must have common fabricpath capability.",
"Members must have same pvlan configuration",
"Members must be 10G to become part of a vPC peer-link.",
"Members must have same EthType configured.",
"Members can not be shared-interfaces.",
"Members must be capable of span destination configuration",
"Module type for interfaces is not compatible.",
"Members are Fabricpath Enforce locked, not compatible.",
"Members have rate mode shared,and rewrite translate exists on the channel \
ngroup,Not compatible.",
"FEX ports cannot have private VLAN promiscuous or promiscuous trunk configs
",
"Members have vmtracker enable mismatch",
"Members must have common FEC capabilities.",
"Members port VLAN info.",
"Members port does not exist.",
"Members must be switching port, Layer 2.",
"Members must have the same port access VLAN.",
"Members must have the same port native VLAN.",
"Members must have the same port allowed VLAN list.",
"Members must have the same VLAN translation list.",
"Members must have same FEX configuration.",
"FEX pinning max-links config is not one.",
"Multiple port-channels to same FEX not allowed.",
"Members must have the same pinning parameters.",
"All HIF member ports not in same pinning group",
"Cannot add cfged slot member to fabric po vpc.",
"Members must belong to same FEX.",
"Members must of same interface type.",
"10G port-channel members must have the same egress queuing policy as the \n
port-channel.",
"Members must have the same port-security enable status as port-channel",
"PFC config should be the same for all the members",
"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 \nchanne
l",
"Queuing policy for Non-DCE PC should be non-dce",
"Queuing policy for the PC should be same as system queuing policy",
"Members must have same PVLAN port configuration.",
"vPC ports in emulated switch complex should be L2MP capable.",
"Fex-AA ports can not be configured as a member port of already-configured \
nvPC port-channel.",
"Members cannot have VFCs bound to them.",
"Port Channels that have VFCs bound to them cannot have more than one member
",
"Port Channels that have VFCs bound to them cannot have non fcoe capable \nm
ember",
"Port Channels that have VFCs bound to them cannot have non fcoe licensed \n
member",
"Port Channel members cannot have EVC EFP configured under them",
"Port-Channel is already a SPAN source. Cannot add FEX ports connected \nthr
ough F2/F2E series line cards to this PC",
"Members cannot have shut lan configured",
"Port channel members cannot have vPC orphan port suspend configured under \
nthem",
"Members must have same native vlan tagging configured",
"Port Channel members cannot have VNSEG VSI configured under them",
"VNSEG VSI Id greater than 62 not allowed on FEX Ports",
"VNSEG VSI configured under port channel and VSI under FEX member should not
\nhave overlapping mappings",
"FEX Port Channel members and port-channel configuration for VSI Id and \npr
ofile name should match",
"All FEX ports should have same VSI Type - STATIC/VDP/DFS",
"EDP ports should fail to be part of Port Channel",
"PFC_LD config should be the same for all the members",
"PFC of PC to be turned OFF when LFC is ON or LFC of PC to be default, to \n
add DCE member",
"Members must have the same CTS mode configured (either \"cts manual\" or \"
cts \ndot1x\" or no cts)",
"SGT propagation must either be enabled or disabled on all members",
"Members must all have either \"policy static\" or \"policy dynamic\" or no
\npolicy configured",
"Members must all have the same peer identity configured",
"Members must all have the same SGT configured",
"Replay protection must either be enabled or disabled on all members",
"FEX ports cannot have storm-control configs",
"Members cannot have MKA enabled before adding to PO with/without MKA macsec
",
"Members cannot have CTS SAP enabled while adding to PO with MKA macsec"
]
}
switch# show port-channel compatibility-parameters | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3" xmlns:nf="urn:ie
tf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<compatibility-parameters>
<__XML__OPT_Cmd_show_port_channel_compat_parm___readonly__>
<__readonly__>
<parameter>port mode</parameter>
<description>Members must have the same port mode configured, either E,F
or AUTO. If
they are configured in AUTO port mode, they have to negotiate E or F mode
when they come up. If a member negotiates a different mode, it will be
suspended.
</description>
<parameter>speed</parameter>
<description>Members must have the same speed configured. If they are con
figured in AUTO
speed, they have to negotiate the same speed when they come up. If a member
negotiates a different speed, it will be suspended.
</description>
<parameter>MTU</parameter>
<description>Members have to have the same MTU configured. This only appl
ies to ethernet
port-channel.
</description>
<parameter>MEDIUM</parameter>
<description>Members have to have the same medium type configured. This o
nly applies to
ethernet port-channel.
</description>
<parameter>Span mode</parameter>
<description>Members must have the same span mode.
</description>
<parameter>load interval</parameter>
<description>Member must have same load interval configured.
</description>
<parameter>span port headers</parameter>
<description>The exclude header span config must either be present or abs
ent on all
members.
</description>
<parameter>sub interfaces</parameter>
<description>Members must not have sub-interfaces.
</description>
<parameter>Duplex Mode</parameter>
<description>Members must have same Duplex Mode configured.
</description>
<parameter>Ethernet Layer</parameter>
<description>Members must have same Ethernet Layer (switchport/no-switchp
ort) configured.
</description>
<parameter>Span Port</parameter>
<description>Members cannot be SPAN ports.
</description>
<parameter>Storm Control</parameter>
<description>Members must have same storm-control configured.
</description>
<parameter>Flow Control</parameter>
<description>Members must have same flowctrl configured.
</description>
<parameter>Capabilities</parameter>
<description>Members must have common capabilities.
</description>
<parameter>Capabilities speed</parameter>
<description>Members must have common speed capabilities.
</description>
<parameter>Capabilities duplex</parameter>
<description>Members must have common speed duplex capabilities.
</description>
<parameter>rate mode</parameter>
<description>Members must have the same rate mode configured.
</description>
<parameter>Capabilities FabricPath</parameter>
<description>Members must have common fabricpath capability.
</description>
<parameter>Port has PVLAN config</parameter>
<description>Members must have same pvlan configuration
</description>
<parameter>1G port is not capable of acting as peer-link</parameter>
<description>Members must be 10G to become part of a vPC peer-link.
</description>
<parameter>EthType</parameter>
<description>Members must have same EthType configured.
</description>
<parameter>shared interface</parameter>
<description>Members can not be shared-interfaces.
</description>
<parameter>Capabilities SpanDest</parameter>
<description>Members must be capable of span destination configuration
</description>
<parameter>Module Type Incompatible</parameter>
<description>Module type for interfaces is not compatible.
</description>
<parameter>Port Mode Fabricpath Incompatible</parameter>
<description>Members are Fabricpath Enforce locked, not compatible.
</description>
<parameter>Rewrite Translate - Rate Mode shared, Incompatible</parameter>
<description>Members have rate mode shared,and rewrite translate exists o
n the channel
group,Not compatible.
</description>
<parameter>FEX - PVLAN promiscuous config</parameter>
<description>FEX ports cannot have private VLAN promiscuous or promiscuou
s trunk configs
</description>
<parameter>vmtracker enable mismatch</parameter>
<description>Members have vmtracker enable mismatch
</description>
<parameter>Capabilities FEC</parameter>
<description>Members must have common FEC capabilities.
</description>
<parameter>port</parameter>
<description>Members port VLAN info.
</description>
<parameter>port</parameter>
<description>Members port does not exist.
</description>
<parameter>switching port</parameter>
<description>Members must be switching port, Layer 2.
</description>
<parameter>port access VLAN</parameter>
<description>Members must have the same port access VLAN.
</description>
<parameter>port native VLAN</parameter>
<description>Members must have the same port native VLAN.
</description>
<parameter>port allowed VLAN list</parameter>
<description>Members must have the same port allowed VLAN list.
</description>
<parameter>VLAN translation mapping list</parameter>
<description>Members must have the same VLAN translation list.
</description>
<parameter>Members should have same fex config</parameter>
<description>Members must have same FEX configuration.
</description>
<parameter>FEX pinning max-links not one</parameter>
<description>FEX pinning max-links config is not one.
</description>
<parameter>Multiple port-channels with same Fex-id</parameter>
<description>Multiple port-channels to same FEX not allowed.
</description>
<parameter>Pinning Params</parameter>
<description>Members must have the same pinning parameters.
</description>
<parameter>All HIF member ports not in same pinning group</parameter>
<description>All HIF member ports not in same pinning group
</description>
<parameter>Slot in host vpc mode</parameter>
<description>Cannot add cfged slot member to fabric po vpc.
</description>
<parameter>Members in multiple FEX</parameter>
<description>Members must belong to same FEX.
</description>
<parameter>Members are of different type</parameter>
<description>Members must of same interface type.
</description>
<parameter>port egress queuing policy</parameter>
<description>10G port-channel members must have the same egress queuing p
olicy as the
port-channel.
</description>
<parameter>Port Security policy </parameter>
<description>Members must have the same port-security enable status as po
rt-channel
</description>
<parameter>Port priority-flow-control</parameter>
<description>PFC config should be the same for all the members
</description>
<parameter>Dot1x policy</parameter>
<description>Members must have host mode as multi-host with no mab config
uration. Dot1X
cannot be enabled on members when Port Security is configured on port
channel
</description>
<parameter>PC Queuing policy</parameter>
<description>Queuing policy for Non-DCE PC should be non-dce
</description>
<parameter>PC Queuing policy</parameter>
<description>Queuing policy for the PC should be same as system queuing p
olicy
</description>
<parameter>PVLAN port config</parameter>
<description>Members must have same PVLAN port configuration.
</description>
<parameter>Emulated switch port type policy</parameter>
<description>vPC ports in emulated switch complex should be L2MP capable.
</description>
<parameter>Cannot add a Fex-AA port to a port-channel which already user-
configured as a vPC</parameter>
<description>Fex-AA ports can not be configured as a member port of alrea
dy-configured
vPC port-channel.
</description>
<parameter>VFC bound to port</parameter>
<description>Members cannot have VFCs bound to them.
</description>
<parameter>VFC bound to port channel</parameter>
<description>Port Channels that have VFCs bound to them cannot have more
than one member
</description>
<parameter>VFC bound to FCoE capable port channel</parameter>
<description>Port Channels that have VFCs bound to them cannot have non f
coe capable
member
</description>
<parameter>VFC bound to FCoE capable port channel</parameter>
<description>Port Channels that have VFCs bound to them cannot have non f
coe licensed
member
</description>
<parameter>EVC EFP configured under port channel member</parameter>
<description>Port Channel members cannot have EVC EFP configured under th
em
</description>
<parameter>Fex ports for span</parameter>
<description>Port-Channel is already a SPAN source. Cannot add FEX ports
connected
through F2/F2E series line cards to this PC
</description>
<parameter>shut lan</parameter>
<description>Members cannot have shut lan configured
</description>
<parameter>VPC orphan port suspend configured under port channel member</
parameter>
<description>Port channel members cannot have vPC orphan port suspend con
figured under
them
</description>
<parameter>tag native</parameter>
<description>Members must have same native vlan tagging configured
</description>
<parameter>VNSEG VSI configured under port channel member</parameter>
<description>Port Channel members cannot have VNSEG VSI configured under
them
</description>
<parameter>VNSEG VSI Id for FEX > 62</parameter>
<description>VNSEG VSI Id greater than 62 not allowed on FEX Ports
</description>
<parameter>VNSEG VSI configured under port channel and VSI under FEX memb
er have overlapping mappings</parameter>
<description>VNSEG VSI configured under port channel and VSI under FEX me
mber should not
have overlapping mappings
</description>
<parameter>VNSEG VSI Id and profile name mismatch on FEX member with thos
e on Port-channel</parameter>
<description>FEX Port Channel members and port-channel configuration for
VSI Id and
profile name should match
</description>
<parameter>VNSEG VSI type mismatch on FEX member with those on Port-chann
el</parameter>
<description>All FEX ports should have same VSI Type - STATIC/VDP/DFS
</description>
<parameter>PLSM EDP port type policy</parameter>
<description>EDP ports should fail to be part of Port Channel
</description>
<parameter>Port priority-flow-control long-distance</parameter>
<description>PFC_LD config should be the same for all the members
</description>
<parameter>Port channel LFC-PFC compat check fail</parameter>
<description>PFC of PC to be turned OFF when LFC is ON or LFC of PC to be
default, to
add DCE member
</description>
<parameter>CTS mode</parameter>
<description>Members must have the same CTS mode configured (either "
;cts manual" or "cts
dot1x" or no cts)
</description>
<parameter>CTS SGT propagation</parameter>
<description>SGT propagation must either be enabled or disabled on all me
mbers
</description>
<parameter>CTS SGT policy</parameter>
<description>Members must all have either "policy static" or &q
uot;policy dynamic" or no
policy configured
</description>
<parameter>CTS peer identity</parameter>
<description>Members must all have the same peer identity configured
</description>
<parameter>CTS SGT configuration</parameter>
<description>Members must all have the same SGT configured
</description>
<parameter>CTS replay protection</parameter>
<description>Replay protection must either be enabled or disabled on all
members
</description>
<parameter>FEX - Storm-control config</parameter>
<description>FEX ports cannot have storm-control configs
</description>
<parameter>MKA MACSEC compat check</parameter>
<description>Members cannot have MKA enabled before adding to PO with/wit
hout MKA macsec
</description>
<parameter>MKA SAP compat check</parameter>
<description>Members cannot have CTS SAP enabled while adding to PO with
MKA macsec
</description>
</__readonly__>
</__XML__OPT_Cmd_show_port_channel_compat_parm___readonly__>
</compatibility-parameters>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|
show port-channel database [interface port-channel 22]
show port-channel database [interface port-channel 22]
import requests
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 port-channel 22",
"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)
{
"TABLE_interface": {
"ROW_interface": {
"interface": "port-channel22",
"last-membership-update": "successful",
"total-ports": 2,
"total-up-ports": 2,
"first_operational-port": "Ethernet2/20",
"age-of-channel": "8d:20h:43m:06s",
"time-since-last-bundle": "8d:20h:43m:06s",
"last-bundled-member": "Ethernet2/22",
"TABLE_member": {
"ROW_member": [
{
"port": "Ethernet2/20",
"mode": "on",
"port-status": "up"
},
{
"port": "Ethernet2/22",
"mode": "on",
"port-status": "up"
}
]
}
}
}
}```
```XML
switch# show port-channel database interface port-channel 22 | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3" xmlns:nf="urn:ie
tf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<database>
<__XML__OPT_Cmd_show_port_channel_database_interface>
<interface>
<__XML__INTF_if0>
<__XML__PARAM_value>
<__XML__INTF_output>port-channel22</__XML__INTF_output>
</__XML__PARAM_value>
</__XML__INTF_if0>
</interface>
<__XML__OPT_Cmd_show_port_channel_database___readonly__>
<__readonly__>
<TABLE_interface>
<ROW_interface>
<interface>port-channel22</interface>
<last-membership-update>successful</last-membership-update>
<total-ports>2</total-ports>
<total-up-ports>2</total-up-ports>
<first_operational-port>Ethernet2/20</first_operational-port>
<age-of-channel>8d:20h:42m:41s</age-of-channel>
<time-since-last-bundle>8d:20h:42m:41s</time-since-last-bundle>
<last-bundled-member>Ethernet2/22</last-bundled-member>
<TABLE_member>
<ROW_member>
<port>Ethernet2/20</port>
<mode>on</mode>
<port-status>up</port-status>
</ROW_member>
<ROW_member>
<port>Ethernet2/22</port>
<mode>on</mode>
<port-status>up</port-status>
</ROW_member>
</TABLE_member>
</ROW_interface>
</TABLE_interface>
</__readonly__>
</__XML__OPT_Cmd_show_port_channel_database___readonly__>
</__XML__OPT_Cmd_show_port_channel_database_interface>
</database>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|
show port-channel rbh-distribution interface port-channel 22
show port-channel rbh-distribution interface port-channel 22
import requests
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 rbh-distribution interface port-channel 22",
"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)
{
}
switch# show port-channel rbh-distribution interface port-channel 22 | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3" xmlns:nf="urn:ie
tf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<rbh-distribution>
<__XML__OPT_Cmd_show_port_channel_rbh_interface>
<interface>
<__XML__INTF_if0>
<__XML__PARAM_value>
<__XML__INTF_output>port-channel22</__XML__INTF_output>
</__XML__PARAM_value>
</__XML__INTF_if0>
</interface>
<__XML__OPT_Cmd_show_port_channel_rbh___readonly__>
<__readonly__>
<TABLE_channel>
<ROW_channel>
<chan-id>22</chan-id>
<port>Ethernet2/20</port>
<rbh>4</rbh>
<rbh>5</rbh>
<rbh>6</rbh>
<rbh>7</rbh>
<num_of_buckets>4</num_of_buckets>
</ROW_channel>
<ROW_channel>
<chan-id>22</chan-id>
<port>Ethernet2/22</port>
<rbh>0</rbh>
<rbh>1</rbh>
<rbh>2</rbh>
<rbh>3</rbh>
<num_of_buckets>4</num_of_buckets>
</ROW_channel>
</TABLE_channel>
</__readonly__>
</__XML__OPT_Cmd_show_port_channel_rbh___readonly__>
</__XML__OPT_Cmd_show_port_channel_rbh_interface>
</rbh-distribution>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|
show port-channel summary interface port-channel 22
show port-channel summary interface port-channel 22
import requests
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 interface port-channel 22",
"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)
{
"TABLE_channel": {
"ROW_channel": {
"group": 22,
"port-channel": "port-channel22",
"layer": "S",
"status": "U",
"type": "Eth",
"prtcl": "NONE",
"TABLE_member": {
"ROW_member": [
{
"port": "Ethernet2/20",
"port-status": "P"
},
{
"port": "Ethernet2/22",
"port-status": "P"
}
]
}
}
}
}
switch# show port-channel summary interface port-channel 22 | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3" xmlns:nf="urn:ie
tf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<summary>
<__XML__OPT_Cmd_show_port_channel_summary_interface>
<interface>
<__XML__INTF_if0>
<__XML__PARAM_value>
<__XML__INTF_output>port-channel22</__XML__INTF_output>
</__XML__PARAM_value>
</__XML__INTF_if0>
</interface>
<__XML__OPT_Cmd_show_port_channel_summary___readonly__>
<__readonly__>
<TABLE_channel>
<ROW_channel>
<group>22</group>
<port-channel>port-channel22</port-channel>
<layer>S</layer>
<status>U</status>
<type>Eth</type>
<prtcl>NONE</prtcl>
<TABLE_member>
<ROW_member>
<port>Ethernet2/20</port>
<port-status>P</port-status>
</ROW_member>
<ROW_member>
<port>Ethernet2/22</port>
<port-status>P</port-status>
</ROW_member>
</TABLE_member>
</ROW_channel>
</TABLE_channel>
</__readonly__>
</__XML__OPT_Cmd_show_port_channel_summary___readonly__>
</__XML__OPT_Cmd_show_port_channel_summary_interface>
</summary>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|
Group Port- Type Protocol Member Ports Channel
22 Po22(SU) Eth NONE Eth2/20(P) Eth2/22(P)
show port-channel traffic interface port-channel 22
show port-channel traffic interface port-channel 22
import requests
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 interface port-channel 22",
"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)
{
"TABLE_channel": {
"ROW_channel": [
{
"chanId": 22,
"port": "Ethernet2/20",
"rx-ucst": 65.14,
"tx-ucst": 30.3,
"rx-mcst": 50.0,
"tx-mcst": 49.99,
"rx-bcst": 6.89,
"tx-bcst": 57.14
},
{
"chanId": 22,
"port": "Ethernet2/22",
"rx-ucst": 34.85,
"tx-ucst": 69.69,
"rx-mcst": 49.99,
"tx-mcst": 50.0,
"rx-bcst": 93.1,
"tx-bcst": 42.85
}
]
}
}
switch# show port-channel traffic interface port-channel 22 | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3" xmlns:nf="urn:ie
tf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<traffic>
<__XML__OPT_Cmd_some_cmd_interface>
<interface>
<__XML__INTF_if0>
<__XML__PARAM_value>
<__XML__INTF_output>port-channel22</__XML__INTF_output>
</__XML__PARAM_value>
</__XML__INTF_if0>
</interface>
<__XML__OPT_Cmd_some_cmd___readonly__>
<__readonly__>
<TABLE_channel>
<ROW_channel>
<chanId>22</chanId>
<port>Ethernet2/20</port>
<rx-ucst>65.14</rx-ucst>
<tx-ucst>30.30</tx-ucst>
<rx-mcst>50.00</rx-mcst>
<tx-mcst>49.99</tx-mcst>
<rx-bcst>6.89</rx-bcst>
<tx-bcst>57.14</tx-bcst>
</ROW_channel>
<ROW_channel>
<chanId>22</chanId>
<port>Ethernet2/22</port>
<rx-ucst>34.85</rx-ucst>
<tx-ucst>69.69</tx-ucst>
<rx-mcst>49.99</rx-mcst>
<tx-mcst>50.00</tx-mcst>
<rx-bcst>93.10</rx-bcst>
<tx-bcst>42.85</tx-bcst>
</ROW_channel>
</TABLE_channel>
</__readonly__>
</__XML__OPT_Cmd_some_cmd___readonly__>
</__XML__OPT_Cmd_some_cmd_interface>
</traffic>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|
show port-channel usage
show port-channel usage
import requests
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 usage",
"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)
{
"total-channel-number-used": 3,
"used-range-low": [
"22",
"1516",
"3132"
],
"unused-range-low": [
"1",
"23",
"1517",
"3133"
],
"unused-range-hi": [
"21",
"1515",
"3131",
"4096"
]
}
switch# show port-channel usage | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3" xmlns:nf="urn:ie
tf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<usage>
<__XML__OPT_Cmd_show_port_channel_usage___readonly__>
<__readonly__>
<total-channel-number-used>3</total-channel-number-used>
<used-range-low>22</used-range-low>
<used-range-low>1516</used-range-low>
<used-range-low>3132</used-range-low>
<unused-range-low>1</unused-range-low>
<unused-range-hi>21</unused-range-hi>
<unused-range-low>23</unused-range-low>
<unused-range-hi>1515</unused-range-hi>
<unused-range-low>1517</unused-range-low>
<unused-range-hi>3131</unused-range-hi>
<unused-range-low>3133</unused-range-low>
<unused-range-hi>4096</unused-range-hi>
</__readonly__>
</__XML__OPT_Cmd_show_port_channel_usage___readonly__>
</usage>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|
Used : 22 , 1516 , 3132
Unused: 1 - 21 , 23 - 1515 , 1517 - 3131 , 3133 - 4096
show port-channel capacity
show port-channel capacity
import requests
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 capacity",
"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)
{
"total": 768,
"used": 3,
"free": 757,
"percentage_used": 0
}
switch# show port-channel capacity | xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<nf:rpc-reply xmlns="http://www.cisco.com/nxos:1.0:eth_pcm_dc3_admin" xmlns:nf="
urn:ietf:params:xml:ns:netconf:base:1.0">
<nf:data>
<show>
<port-channel>
<capacity>
<__XML__OPT_Cmd_show_port_channel_capacity___readonly__>
<__readonly__>
<total>768</total>
<used>3</used>
<free>757</free>
<percentage_used>0</percentage_used>
</__readonly__>
</__XML__OPT_Cmd_show_port_channel_capacity___readonly__>
</capacity>
</port-channel>
</show>
</nf:data>
</nf:rpc-reply>
]]>]]>
For command descriptions, see the Cisco Nexus 7000 Series Switches Command References.
Note: This sample output is generated for Cisco Nexus 7000 Series NX-OS Release 8.3(1).
| CLI Output |
|---|
|