Hi I am running 4.2(1)N2(1a) on my N5K. I have a N5K connectd to N2K. PC connected to the N2K doing large packet ping. WHen i do a "show interface eth101/1/1" where the PC is connected. I can't see the jumbo frame statistics. WHen i do a "show interface eth1/1" (ports where N5K is connected to N2K), i can see jumbo frame statistics. Attached is the output. Just want to confirm if this is the correct behaviour. THanks Eng Wee
If you look the ports on the N5K with the FEX connected by issuing " sh queuing inter eth 1/1" or whatever interface your FEX is connected to you should see the actual harware MTU instead of the visual defect on the show interface command. I agree that this bug is REALLY annoying to work with.
sh queuing inter eth 1/1
Ethernet1/1 queuing information:
qos-group sched-type oper-bandwidth
0 WRR 50
1 WRR 50
q-size: 243200, HW MTU: 9280 (9216 configured)
drop-type: drop, xon: 0, xoff: 1520
on the indivduidal fex port I have no idea as I don't have any hosts running jumbo MTU on the 1gig interfaces, but agree I don't see any easy way to see if the jumo counters are not incrementing.
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...