How to verify Jumbo frame support for AP and controller

Aruba Employee
Requirement:

After enabling jumbo frames if we want to verify the MTU for controller and AP.



Solution:

We can check below command.

 

show datapath port 

 

 

Datapath Port Table Entries

---------------------------

 

Flags: Q - trunk,  T - trusted, B - blocked,  L - LAG

       M - tunneled node, X - xSec, J - Jumbo enabled

 

Port      PVID  Ingress ACL  Egress ACL  Session ACL   MTU       Flags

--------  ----  -----------  ----------  -----------   ------    ------

0/0/0     1000  0            0           0            9000      TJ

0/0/1     1     0            0           0            9000      QTJ

0/0/2     1     0            0           0            1500      B

0/0/3     1     0            0           0            1500      B

0/0/4     1     0            0           0            1500      B

0/0/5     1     0            0           0            1500      B

 

 

However, the bss-table  output shows the tunnel MTU.

 

show ap bss-table ap-name "AP-039-Test-RI-1"

 

 

fm (forward mode): T-Tunnel, S-Split, D-Decrypt Tunnel, B-Bridge (s-standard, p-persistent, b-backup, a-always), n-anyspot

 

Aruba AP BSS Table

------------------

bss                ess  port  ip            phy    type  ch/EIRP/max-EIRP  cur-cl  ap name           in-t(s)  tot-t  mtu   acl-state  acl  fm

---                ---  ----  --            ---    ----  ----------------  ------  -------           -------  -----  ---   ---------  ---  --

18:64:72:29:60:d0       N/A   129.10.1.250  a-VHT  am    ?/?/?             0       AP-039-Test-RI-1  0        40s    1500  -          2    Bs

18:64:72:29:60:c0       N/A   129.10.1.250  g-HT   am    ?/?/?             0       AP-039-Test-RI-1  0        40s    1500  -          2    Bs

 

 

 

For AP, we can see the MTU for eth0 and Eth1 in below output taken from AP- techsupport.

 

ifconfig output for eth0

------------------------

eth0      Link encap:Ethernet  HWaddr 18:64:72:CA:96:0C 

---------------------------------------------------------

          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:9000  Metric:1

          RX packets:378 errors:0 dropped:0 overruns:0 frame:0

          TX packets:173 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:51711 (50.4 KiB)  TX bytes:108517 (105.9 KiB)

          Base address:0x6000

 

          Rx broadcast packet:0         Rx broadcast packet per second:0

          Rx multicast packet:0         Rx multicast packet per second:0

          Tx broadcast packet:0         Tx broadcast packet per second:0

          Tx multicast packet:0         Tx multicast packet per second:0

 

ifconfig output for eth1

------------------------

eth1      Link encap:Ethernet  HWaddr 18:64:72:CA:96:0C 

---------------------------------------------------------

          UP BROADCAST SLAVE MULTICAST  MTU:9000  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Base address:0xe000

 

          Rx broadcast packet:0         Rx broadcast packet per second:0

          Rx multicast packet:0         Rx multicast packet per second:0

          Tx broadcast packet:0         Tx broadcast packet per second:0

          Tx multicast packet:0         Tx multicast packet per second:0



Configuration:

show datapath port 

 

 

Datapath Port Table Entries

---------------------------

 

Flags: Q - trunk,  T - trusted, B - blocked,  L - LAG

       M - tunneled node, X - xSec, J - Jumbo enabled

 

Port      PVID  Ingress ACL  Egress ACL  Session ACL   MTU       Flags

--------  ----  -----------  ----------  -----------   ------    ------

0/0/0     1000  0            0           0            9000      TJ

0/0/1     1     0            0           0            9000      QTJ

0/0/2     1     0            0           0            1500      B

0/0/3     1     0            0           0            1500      B

0/0/4     1     0            0           0            1500      B

0/0/5     1     0            0           0            1500      B

 

 

However, the bss-table  output shows the tunnel MTU.

 

show ap bss-table ap-name "AP-039-Test-RI-1"

 

 

fm (forward mode): T-Tunnel, S-Split, D-Decrypt Tunnel, B-Bridge (s-standard, p-persistent, b-backup, a-always), n-anyspot

 

Aruba AP BSS Table

------------------

bss                ess  port  ip            phy    type  ch/EIRP/max-EIRP  cur-cl  ap name           in-t(s)  tot-t  mtu   acl-state  acl  fm

---                ---  ----  --            ---    ----  ----------------  ------  -------           -------  -----  ---   ---------  ---  --

18:64:72:29:60:d0       N/A   129.10.1.250  a-VHT  am    ?/?/?             0       AP-039-Test-RI-1  0        40s    1500  -          2    Bs

18:64:72:29:60:c0       N/A   129.10.1.250  g-HT   am    ?/?/?             0       AP-039-Test-RI-1  0        40s    1500  -          2    Bs

 

 

 

For AP, we can see the MTU for eth0 and Eth1 in below output taken from AP- techsupport.

 

ifconfig output for eth0

------------------------

eth0      Link encap:Ethernet  HWaddr 18:64:72:CA:96:0C 

---------------------------------------------------------

          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:9000  Metric:1

          RX packets:378 errors:0 dropped:0 overruns:0 frame:0

          TX packets:173 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:51711 (50.4 KiB)  TX bytes:108517 (105.9 KiB)

          Base address:0x6000

 

          Rx broadcast packet:0         Rx broadcast packet per second:0

          Rx multicast packet:0         Rx multicast packet per second:0

          Tx broadcast packet:0         Tx broadcast packet per second:0

          Tx multicast packet:0         Tx multicast packet per second:0

 

ifconfig output for eth1

------------------------

eth1      Link encap:Ethernet  HWaddr 18:64:72:CA:96:0C 

---------------------------------------------------------

          UP BROADCAST SLAVE MULTICAST  MTU:9000  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Base address:0xe000

 

          Rx broadcast packet:0         Rx broadcast packet per second:0

          Rx multicast packet:0         Rx multicast packet per second:0

          Tx broadcast packet:0         Tx broadcast packet per second:0

          Tx multicast packet:0         Tx multicast packet per second:0



Verification

show datapath port 

 

 

Datapath Port Table Entries

---------------------------

 

Flags: Q - trunk,  T - trusted, B - blocked,  L - LAG

       M - tunneled node, X - xSec, J - Jumbo enabled

 

Port      PVID  Ingress ACL  Egress ACL  Session ACL   MTU       Flags

--------  ----  -----------  ----------  -----------   ------    ------

0/0/0     1000  0            0           0            9000      TJ

0/0/1     1     0            0           0            9000      QTJ

0/0/2     1     0            0           0            1500      B

0/0/3     1     0            0           0            1500      B

0/0/4     1     0            0           0            1500      B

0/0/5     1     0            0           0            1500      B

 

 

However, the bss-table  output shows the tunnel MTU.

 

show ap bss-table ap-name "AP-039-Test-RI-1"

 

 

fm (forward mode): T-Tunnel, S-Split, D-Decrypt Tunnel, B-Bridge (s-standard, p-persistent, b-backup, a-always), n-anyspot

 

Aruba AP BSS Table

------------------

bss                ess  port  ip            phy    type  ch/EIRP/max-EIRP  cur-cl  ap name           in-t(s)  tot-t  mtu   acl-state  acl  fm

---                ---  ----  --            ---    ----  ----------------  ------  -------           -------  -----  ---   ---------  ---  --

18:64:72:29:60:d0       N/A   129.10.1.250  a-VHT  am    ?/?/?             0       AP-039-Test-RI-1  0        40s    1500  -          2    Bs

18:64:72:29:60:c0       N/A   129.10.1.250  g-HT   am    ?/?/?             0       AP-039-Test-RI-1  0        40s    1500  -          2    Bs

 

 

 

For AP, we can see the MTU for eth0 and Eth1 in below output taken from AP- techsupport.

 

ifconfig output for eth0

------------------------

eth0      Link encap:Ethernet  HWaddr 18:64:72:CA:96:0C 

---------------------------------------------------------

          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:9000  Metric:1

          RX packets:378 errors:0 dropped:0 overruns:0 frame:0

          TX packets:173 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:51711 (50.4 KiB)  TX bytes:108517 (105.9 KiB)

          Base address:0x6000

 

          Rx broadcast packet:0         Rx broadcast packet per second:0

          Rx multicast packet:0         Rx multicast packet per second:0

          Tx broadcast packet:0         Tx broadcast packet per second:0

          Tx multicast packet:0         Tx multicast packet per second:0

 

ifconfig output for eth1

------------------------

eth1      Link encap:Ethernet  HWaddr 18:64:72:CA:96:0C 

---------------------------------------------------------

          UP BROADCAST SLAVE MULTICAST  MTU:9000  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Base address:0xe000

 

          Rx broadcast packet:0         Rx broadcast packet per second:0

          Rx multicast packet:0         Rx multicast packet per second:0

          Tx broadcast packet:0         Tx broadcast packet per second:0

          Tx multicast packet:0         Tx multicast packet per second:0

Version history
Revision #:
2 of 2
Last update:
‎03-31-2017 03:03 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: