Hi looks like thats a limitation your hitting on the switches , has to be on a physical IP interface same as the 3k series https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/16-8/configuration_guide/nmgmt/b_168_nmgmt_9400_cg/b_168_nmgmt_9400_cg_chapter_0111.html Layer 2, VLAN and Layer 3 interfaces are supported, but the device does not support SVI and tunnels. ... View more

Hi It needs to be under the vlan interface any interface with an IP enabled ... View more

Hi it must be applied to a LAYER 3 interface with Ip enabled,is that ten gig interface layer 2 or 3 ? its an l3 command your applying ... View more

If your stuck with anything just post back to the thread we can take a look but that should get you started at least with some basics steps ... View more

Hi this may help , some good pointers in both links https://www.petri.com/troubleshoot-vlan-switch https://www.pluralsight.com/blog/it-ops/cisco-network-troubleshooting ... View more

Yes thats particular to NetApp storage traffic and very specific applications ,the traffic can be packaged and moved in a certain way it reduces cpu load , https://library.netapp.com/ecmdocs/ECMP1368834/html/GUID-D3AB10A1-D15A-490D-8DCE-34BE73C3DACF.html ... View more

Yes wireshark it probably best way to pinpoint it but it can still be enabled on GB interfaces too but may not suit your setup as you said https://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a00806ec94e.html#wp1895752 Jumbo frames are larger than standard frames and require fewer frames. Therefore, you can reduce the CPU processing overhead by using jumbo frames with your network interfaces. ... Jumbo frames can be used for all Gigabit and 10 Gigabit Ethernet interfaces that are supported on your storage system. ... View more

On our global network we use LA as a monitoring tool as we have IWAN running on top of transport network,its really good , its uses netflow and ip sla in the background , it actually pushes it out from the app to the routers what its requires and pulls all the stats and graphs them , you can run specific jitter reports , just an option https://community.liveaction.com/documentation/livenx/7-x/user-guide/ ... View more

Yes that caught me before but if you read the docs some say this too on the 5ks Note: For L2, you cannot set the MTU per interface but only system wide. Now thats changed on my 9ks you can do both, i recently looked into it as we have an enclave a DC within in a DC and those switches someone wanted storage connected and i had to check it wasnt going to break the other systems connected , some ports can be 9216 and some 1500 and it can be global , but once its set system wide at L2 on switches that only support that then all ports will accept 9216 but may still show as 1500 I agree it should change once global it should show all ports same ... View more

Hi Nick there usually auto generated after crashes , is there a reason your trying to manually generate one ? Denali Doc https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/16-1/configuration_guide/b_161_consolidated_3650_cg/b_161_consolidated_3650_cg_chapter_01101001.html#concept_55C49AEF142443A09D587DD1A9AA7822 System reports are generated in these situations: In case of a switch failure—A system report is generated on the member that failed; reports are not generated on other members in the stack. In case of a switchover—System reports are generated only on high availability (HA) member switches. reports are not generated for non-HA members. The system does not generate reports in case of a reload. During a process crash, the following is collected locally from the switch: Full process core Tracelogs IOS syslogs (not guaranteed in case of non-active crashes) System process information Bootup logs Reload logs Certain types of /proc information This information is stored in separate files which are then archived and compressed into one bundle. This makes it convenient to get a crash snapshot in one place, and can be then moved off the box for analysis. This report is generated before the switch goes down to rommon/bootloader. ... View more

so system wide jumbo is enabled then by default in the background for L2 ,odd because my 5/7/9ks dont do this , maybe its something specific to the 3ks but that statement would suggest its ready to support any jumbo frames , so if something is sending them the ports are ready to receive it system jumbomtu 9216 ... View more

hi Just really amount of watts it can take , some newer devices are using + require more power https://blog.twinstate.com/poe-vs-poe-plus One difference between PoE and PoE+ is the actual Institute of Electrical and Electronics Engineers (IEEE) standards themselves. PoE is 802.3af, while PoE+ is 802.3at. Currently, the max amount of power provided over Cat5 cabling is 15.4 watts for PoE and 25.5 watts for PoE+ ... View more

sorry it showed in lower case for me , if you checked upper # sh run all | i mtu system jumbomtu 9216 sh ver | i n3000 kickstart image file is: bootflash:///n3000-uk9-kickstart.6.0.2.U2.3.bin system image file is: bootflash:///n3000-uk9.6.0.2.U2.3.bin ############################## sh run all | i mtu system jumbomtu 9216 class-map type control-plane match-any copp-s-l3mtufail class copp-s-l3mtufail mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 ... View more