Managing port-level configuration interactions
For features that are configured on specific switch ports in a stack, the configuration procedures are the same as for stand-alone switches, but the port designations for the ports in the stack are modified. Each port is identified by the stack member ID of its switch, followed by a slash and then the port number as it is shown on the switch. For example, for a switch with stack member ID 3, port 10 on that switch would be identified as port 3/10.
Viewing show interfaces brief output for port 3/10
switch(config)# show interfaces brief 3/10
Status and Counters - Port Status
| Intrusion MDI Flow Bcast
Port Type | Alert Enabled Status Mode Mode Ctrl Limit
------------ --------- + --------- ------- ------ ---------- ---- ---- -----
3/10 100/1000T | No Yes Down 1000FDx off 0
Similarly, CLI commands requiring specific port (interface) numbers on a 2930M switch configured for stacking require the modified port designations. For example, to enter the port context for port 10 on stack member 2, type:
switch(config)# interface 2/10
switch(eth-2/10)#_
In the output containing designated port numbers for a 2930M switch configured for stacking, the port numbers are likewise listed in the modified format.
Viewing show interfaces config output
switch(config)# show interfaces config
Port Settings
Port Type | Enabled Mode Flow Ctrl MDI
------ --------- + ------- ------------ --------- ----
1/1 100/1000T | Yes Auto Disable Auto
1/2 100/1000T | Yes Auto Disable Auto
1/3 100/1000T | Yes Auto Disable Auto
.
.
.
2/1 100/1000T | Yes Auto Disable Auto
2/2 100/1000T | Yes Auto Disable Auto
2/3 100/1000T | Yes Auto Disable Auto
2/4 100/1000T | Yes Auto Disable Auto
.
.
.
Attempting to enter a CLI command for a port on a stack member without using the modified port number format generates a “Module not present...” message such as the following:
switch(config)# interface 10
Module not present for port or invalid port: 10