Cisco CRS-1 - Carrier Routing System Router Migration Manual page 190

show controllers (Ethernet)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes the proper
task IDs. If you suspect user group assignment is preventing you from using a command, contact your
AAA administrator.
For the interface-path-id argument, use the following guidelines:
•
•
Task ID Task ID
cisco-support
interface
Examples Example: show controllers GigabitEthernet Command
The following example shows the output from the show controllers GigabitEthernet command:
RP/0/0/CPU0:Router# show controllers GigabitEthernet 0/4/0/0
port:0
good_octets_received: 6008282
bad_octets_received: 0
good_frames_received: 65020
bad_frames_received: 0
broadcast_frames_received: 11
multicast_frames_received: 49985
good_octets_sent: 4483774
good_frames_sent: 45648
broadcast_frames_sent: 0
multicast_frames_sent: 0
mac_transfer_error: 0
excessive_collision: 0
unrecog_mac_control_received: 0
fc_sent: 0
good_fc_received: 0
rx_over_flow_events: 0
undersize: 0
fragments: 0
oversize: 0
jabber: 0
mac_rcv_error: 0
bad_crc: 0
collisions: 0
late_collision: 0
rate_limit_dropped: 0
spi4_rx_frames: 0
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
3-30
If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between
values is required as part of the notation. An explanation of each component of the naming notation
is as follows:
rack: Chassis number of the rack.
–
slot: Physical slot number of the line card.
–
module: Module number. A physical layer interface module (PLIM) is always 0.
–
port: Physical port number of the interface.
–
If specifying a virtual interface, the number range varies, depending on interface type.
Operations
read
Note
read
Chapter 3 Cisco CRS-3 Carrier Routing System Router Command Changes
Required in addition to the interface (read) task ID to use the control
keyword.
OL-13669-03