Command of the Day

Reply
Guru Elite
Posts: 20,424
Registered: ‎03-29-2007

COTD: show port stats

In networking, every frame that we cannot send reliably will cause degradation. This is even more important in wireless because it is a shared medium. Wireless frames are encapsulated in wired frames and if those cannot be sent reliably, they will negatively impact the wireless frames they are carrying. A very common troubleshooting step for degradation and packet loss of wireless clients is to see if any ports on your controller is sustaining errors, due to a mismatch or something else. You would use "show port stats" to see all of your interfaces on your controller at one time:

(2400.arubanetworks.com) #show port stats

Port Statistics
---------------
Port PacketsIn PacketsOut BytesIn BytesOut InputErrorBytes OutputErrorBytes CRCErrors
---- --------- ---------- ------- -------- --------------- ---------------- ---------
FE1/0 252 208 33486 17254 68631 0 45
FE1/1 210 231 29486 24729 0 0 0
FE1/2 392562 385465 60084852 37897568 6723 0 146
FE1/3 289098 231650 68851847 22253789 102 0 3
FE1/4 216 42581 79366 2025938 0 0 0
FE1/5 370841 386714 54242068 39491720 0 0 0
FE1/6 0 0 0 0 0 0 0
FE1/7 373589 387750 53576835 39097062 0 0 0
FE1/8 0 0 0 0 0 0 0
FE1/9 0 0 0 0 0 0 0
FE1/10 0 0 0 0 0 0 0
FE1/11 0 0 0 0 0 0 0
FE1/12 0 0 0 0 0 0 0
FE1/13 0 0 0 0 0 0 0
FE1/14 0 0 0 0 0 0 0
FE1/15 0 0 0 0 0 0 0
FE1/16 0 0 0 0 0 0 0
FE1/17 0 0 0 0 0 0 0
FE1/18 0 0 0 0 0 0 0
FE1/19 0 0 0 0 0 0 0
FE1/20 0 0 0 0 0 0 0
FE1/21 0 0 0 0 0 0 0
FE1/22 0 0 0 0 0 0 0
FE1/23 218396 292703 47740181 76306290 0 0 0
GE 1/24 0 0 0 0 0 0 0
GE 1/25 0 0 0 0 0 0 0


You could also dig into the individual interface to see the nature of those errors:

(2400.arubanetworks.com) #show interface fastethernet 1/0

FE 1/0 is up, line protocol is up
Hardware is FastEthernet, address is 00:0B:86:42:FB:61 (bia 00:0B:86:42:FB:61)
Description: FE1/0
Encapsulation ARPA, loopback not set
Configured: Duplex ( AUTO ), speed ( AUTO )
Negotiated: Duplex (Full), speed (100 Mbps)
MTU 1500 bytes, BW is 100 Mbit
Last clearing of "show interface" counters 0 day 22 hr 54 min 11 sec
link status last changed 0 day 22 hr 50 min 13 sec
476035 packets input, 62078780 bytes
Received 17 broadcasts, 4529206 runts, 8 giants, 0 throttles
68910270 input error bytes, 72249 CRC, 162374 frame
0 multicast, 476018 unicast
382851 packets output, 61625139 bytes
0 output errors bytes, 0 deferred
0 collisions, 0 late collisions, 0 throttles
This port is TRUSTED
POE Status of the port is ON


You can clear the counters on that interface to see if the errors keep mounting:



You could also see what MAC address is physically connected to that port:

(2400.arubanetworks.com) #show datapath bridge table | include 1/0
00:0B:86:C5:0D:64 1000 1000 1/0


In this case, an AP is physically connected to that port (00:0B:86 is an Aruba OID), so you can use "show ap database long" to see which AP that is by searching for it's wired mac address:


(2400.arubanetworks.com) #show ap database long | include 00:0b:86:c5:0d:64
AP70-A default 70 1.1.1.249 Up 8m:48s 10.69.2.2 00:0b:86:c5:0d:64 A60065914 1/0 AP70-A.Floor 1.New Building.Main Campus N/A


Looks like our AP70-A is having physical issues!

note: The AP database stores the AP mac addresses in lower case format, so you need to change your alpha hex digits to lower case before you do the search directly above.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: