02-24-2020 12:08 AM - edited 02-24-2020 01:53 AM
Hi there,
we are migrating our "old" MPLS-Backbone to Catalyst 9500 / 9300. During this Migration we remarked, that the neighbors (Catalyst 6500 and 6880) are increasing the giants count… I hope somebody can help finding out what is going wrong. Thanks!
The following IOS-Versions and Platforms are used:
It looks like this (RTR-1 can be either Catalyst 9300 or 9500 [in this case C9500-24Y4C], RTR-2 can be either Catalyst 6500 or 6880 [in this case WS-C6506-E]
-------------------------------------------------------------------------------------------------------
RTR-2 (Catalyst 6500 or 6880)
---------------------------------------------------------------------------------------------
RTR-2#sho int po100
Port-channel100 is up, line protocol is up (connected)
Hardware is EtherChannel, address is 0024.14a6.0d80 (bia 0024.14a6.0d80)
Description: WAN to RTR-1 [Po100] <ms>
Internet address is 10.1.1.2/30
MTU 9198 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 2/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s, media type is unknown
input flow-control is on, output flow-control is off
Members in this channel: Te3/3
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 29439000 bits/sec, 6777 packets/sec
5 minute output rate 83634000 bits/sec, 10251 packets/sec
L2 Switched: ucast: 8133999 pkt, 607113126 bytes - mcast: 31061663 pkt, 3877286028 bytes
L3 in Switched: ucast: 58507336931 pkt, 27814824957527 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 79029338746 pkt, 58326116108186 bytes mcast: 0 pkt, 0 bytes
58544738849 packets input, 27817362680710 bytes, 0 no buffer
Received 33956109 broadcasts (0 IP multicasts)
0 runts, 431330790 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
79062339770 packets output, 58232331329668 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
RTR-2#sho int po100 mtu
Port Name MTU
Po100 WAN to RTR-1 [Po10 9198
RTR-2#
RTR-2#ho runn int po100
Building configuration...
Current configuration : 309 bytes
!
interface Port-channel100
description WAN to RTR-1 [Po100] <ms>
mtu 9198
ip address 10.1.1.2 255.255.255.252
ip ospf authentication null
ip ospf network point-to-point
ip ospf dead-interval 3
ip ospf hello-interval 1
logging event link-status
logging event bundle-status
mpls ip
end
RTR-2#sho etherch 100 sum
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator
M - not in use, no aggregation due to minimum links not met
m - not in use, port not aggregated due to minimum links not met
u - unsuitable for bundling
d - default port
w - waiting to be aggregated
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
100 Po100(RU) LACP Te3/3(P)
Last applied Hash Distribution Algorithm: Fixed
RTR-2#sho runn int te3/3
Building configuration...
Current configuration : 238 bytes
!
interface TenGigabitEthernet3/3
description WAN to RTR-1 [Twe1/0/24] <m>
mtu 9198
no ip address
logging event link-status
logging event bundle-status
logging event spanning-tree status
channel-group 100 mode active
end
RTR-2#sho interface TenGigabitEthernet3/3 mtu
Port Name MTU
Te3/3 WAN to RTR-1 [Twe 9198
RTR-2#
-------------------------------------------------------------------------------------------------------
RTR-1 (Catalyst 9500 or 9300)
---------------------------------------------------------------------------------------------
RTR-1#sho int po100
Port-channel100 is up, line protocol is up (connected)
Hardware is EtherChannel, address is 6c8b.d348.f31f (bia 6c8b.d348.f31f)
Description: WAN to RTR-2 [Po100] <ms>
Internet address is 10.1.1.1/30
MTU 9198 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 2/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s, link type is auto, media type is N/A
input flow-control is on, output flow-control is unsupported
Members in this channel: Twe1/0/24
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 84369000 bits/sec, 10501 packets/sec
5 minute output rate 21932000 bits/sec, 6279 packets/sec
17127158611 packets input, 14334176858857 bytes, 0 no buffer
Received 9042101 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 9042100 multicast, 0 pause input
0 input packets with dribble condition detected
11829227138 packets output, 5568097929729 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
RTR-1#
RTR-1#sho int po100 mtu
Port Name MTU
Po100 WAN to RTR-2 [Po10 9198
RTR-1#
RTR-1#sho system mtu
Global Ethernet MTU is 9198 bytes.
RTR-1#
RTR-1#sho runn int po100
Building configuration...
Current configuration : 258 bytes
!
interface Port-channel100
description WAN to RTR-2 [Po100] <ms>
no switchport
ip address 10.1.1.1 255.255.255.252
ip ospf network point-to-point
ip ospf dead-interval 3
ip ospf hello-interval 1
logging event bundle-status
mpls ip
end
RTR-1#sho etherch 100 summ
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
A - formed by Auto LAG
Number of channel-groups in use: 17
Number of aggregators: 17
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
100 Po100(RU) LACP Twe1/0/24(P)
RTR-1#sho runn int twe1/0/24
Building configuration...
Current configuration : 209 bytes
!
interface TwentyFiveGigE1/0/24
description WAN to RTR-1 [Te3/3] <m>
no switchport
no ip address
logging event bundle-status
channel-group 100 mode active
service-policy output PM_QOS-OUT
end
RTR-1#sho interface TwentyFiveGigE1/0/24 mtu
Port Name MTU
Twe1/0/24 WAN to RTR-1 [Te3/ 9198
RTR-1#
Solved! Go to Solution.
02-25-2020 01:00 AM
Hello @WALTER GROSSENBACHER , @Georg Pauwen
>> 0 runts, 431330790 giants, 0 throttles
when Cisco acquired Catalyst company the Cisco Catalyst has its own CatOS Network Operating system.
On the fly I can tell you that these giants are likely just counted / classified as giants but not actually discarded.
C9x00 catalyst are new and they start with jumbo frame enabled by default for :
native datacenter support
native DNAC support with UDP VXVLAN encapsulation
This means that C9x00 do not account for giants as they can be edge nodes in a campus fabric in an SD Access campus fabric.
The combination of DNAC + ISE + UDP VxVLAN is making the the C9x00 with x>2 very interesting for a lot of new applications like IoT.
Edge nodes in DNAC campus fabric must have max MTU for the above reasons.
ISE provides security tags that allow also to avoid explosion of usage of TCAM entries.
I invite you to see the breakout session about C9x00 architecture from Cisco Live Barcelona I was there and I put several questions to the speaker
ciscolive.com
visit online library it is free not only for experts.
Hope to help
Giuseppe
02-24-2020 05:29 PM
02-24-2020 10:55 PM
Thanks for the answer!
But what I don't understand in this case, why the Catalyst 9300 & 9500 doesn't show any Giants on their interfaces even when packets >1500 bytes are passing through those devices...
02-25-2020 01:00 AM
Hello @WALTER GROSSENBACHER , @Georg Pauwen
>> 0 runts, 431330790 giants, 0 throttles
when Cisco acquired Catalyst company the Cisco Catalyst has its own CatOS Network Operating system.
On the fly I can tell you that these giants are likely just counted / classified as giants but not actually discarded.
C9x00 catalyst are new and they start with jumbo frame enabled by default for :
native datacenter support
native DNAC support with UDP VXVLAN encapsulation
This means that C9x00 do not account for giants as they can be edge nodes in a campus fabric in an SD Access campus fabric.
The combination of DNAC + ISE + UDP VxVLAN is making the the C9x00 with x>2 very interesting for a lot of new applications like IoT.
Edge nodes in DNAC campus fabric must have max MTU for the above reasons.
ISE provides security tags that allow also to avoid explosion of usage of TCAM entries.
I invite you to see the breakout session about C9x00 architecture from Cisco Live Barcelona I was there and I put several questions to the speaker
ciscolive.com
visit online library it is free not only for experts.
Hope to help
Giuseppe
02-25-2020 12:43 AM
Hello,
what if you increase the jumbo frame size on the interfaces to 9216 (mtu 9216) and the mpls mtu size to 1508 (mpls mtu 1508) ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide