This command canb show if there is constant L2 changes in the network which could cause interruptions to the SVIs ,if the timers are constantly resetting there is issues at layer 2 show spanning-tree detail | inc ieee|occurr|from|is exec ... View more

Hi are these switches running same IOS version ?   Are these switches L2 , if they are the SVI is only for MGMT , if SVI is dropping could be an STP issue i causing it too , the switch has very little config , trunk port set to allow vlan 2 only and the rest of the ports are vlan 1 , even though vlan 1 is not really blocked on a trunk should still be permitted if access ports are working on vlan 1 ... View more

Hi The config you have above should work fine in terms of design its not an issue , the BW you can place it on both but phsyical should work for all as its a 1 policy setup , the BW statement is only for the routing metrics calculations to define parameters of what which route gets added to the table , its optional statement but advised to use as its on the WAN if its plied to the physical the calculation will apply to the subs too , when you run the show policy-map interface x/x you will see everything's under the physical when applied like that , but if you have multiple LAN input policies you can see each individual one under the sub interfaces itself like show interface g0/0/0.100, so in your setup whatevers applied to wan will apply to the sub ... View more

Hi some older NICs may have required it but i dont think access was ever set that it had to be , definitely towards some ISPs WAN due to there local modems required hard set and still do , config also may have been carried over it happens all the time , recently replaced some daisy chained PCs connected to older phones , phones could only operate at 100mb so they required it , had to update the config when new phones went in that were 1GB capable , usually these days all access is auto and works well , only ever set it if far end has a reason too ... View more

Hi so theres a design setup you must follow to apply to subs , 1 outbound policy will cover all subs , but on LAN inbound you can have multiple , your right what you have there and yes it will work on sub by default , 1 policy fits all when outbound Cisco IOS logical interfaces do not inherently support a state of congestion and do not support the direct application of a service policy that applies a queuing method. Instead, you first need to apply shaping to the subinterface using either generic traffic shaping (GTS) or class-based shaping. Refer to Policing and Shaping for more information. https://www.cisco.com/c/en/us/support/docs/quality-of-service-qos/qos-policing/10104-qos-subint.html router(config)# interface ethernet0/0.1 router(config-subif)# service-policy output test CBWFQ : Not supported on subinterfaces ... View more

Thats right not supported on any NX switch currently , there IOS commands , not available in NX software ... View more

Hi wheres your snmp user config its hidden part of the config ? should be a line snmp-server user swi and you should really avail of AES and SHA if using SNMPv3 snmp user config does not show in running config if you copied this from somewhere , without it it wont work example xxxxxx#sh snmp us User name: xxxxxx Engine ID: 800000090300BCC49371D681 storage-type: nonvolatile active access-list: 5 Authentication Protocol: SHA Privacy Protocol: AES128 Group-name: XSNMPV3 User name: xxxxxxx Engine ID: 800000090300BCC49371D681 storage-type: nonvolatile active access-list: 6 Authentication Protocol: SHA Privacy Protocol: AES128 Group-name: XSNMPV3RW ... View more

is the cpu on the devices maxed out when you do a show proc cpu sorted ,fact you have multiple images would suggest resource general issue rather than SSH issue itself ,ssh requires alot more than telnet as its using crypto ... View more

You need to be able to type in CLi mode to do the IOS recovery from the switch prompt , try rebooting it if not already done, try change the cables too if possible , if this is a brand new switch you should be able return it under DOA or RMA in first 3 months warranty even without full support , the fact its getting to switch mode would suggest its working at some level ... View more

no license is bound to the chassis , upgrading software wont effect it if this is brand new and has not worked before , if the software upgrade does not work , return the switch if no usb you can use xmoden either , this guide shows you what you will see as the upgrade occurs , its same if its by usb just another transfer method to get the software onto the switch https://www.freeccnaworkbook.com/workbooks/ccna/recovering-a-corrupt-cisco-ios-image-on-a-catalyst-switch ... View more

Hi You should be using 3ks and 6ks for low latency , 9ks are store and forward switches if you want low latency for likes of super sensitive apps or stocks use cut through switches , nx 6ks and 3ks i use 91380s and 93240s ,stable switches but not specifically LL   3500s NX Lowest latency in the industry https://www.cisco.com/c/en/us/products/switches/nexus-3000-series-switches/index.html#~stickynav=1 ... View more

Hi yes Cisco support 64 as its IEEE standard , all vendors would as its the global standard that's set to work off so there is some consistence globally ,the 68 is just when the tag is added as a 4 byte extra even the doc in a way states it , the minimum size with tagging is 68 , so without tagging which Cisco supports too is 64 The 802.1Q tag is 4 bytes. Therefore, the resulting Ethernet frame can be as large as 1522 bytes. The minimum size of the Ethernet frame with 802.1Q tagging is 68 bytes. ... View more

Hi A collision can even be detected before the full 64 is sent , good read on co;collisions in this link below There are two types of collision: – “ordinary” – collision that detected before 512 bits of frame were sent – late – collision that detected after 512 bits of frame were sent https://yurmagccie.wordpress.com/2017/06/21/ethernet-frame-and-csmacd/ ... View more

Hi so it works on a flat network because its broadcasting , when you introduce another vlan a broadcast wont be sent through to prevent flooding by default , so the ip relay changes the broadcast to unicast packet and directs it specifically at the the PXE server IP address , thats how it connects   The fact you have done that config on switch side as its all that's required  and you know it works on flat vlan also rules out the server side , so the only part left to troubleshoot is whether the actual broadcast to unicast i happening as it crosses between vlans or if there is some irregular transfer of DHCP packets between source and destination when vlan is involved   Unfortunately the only way to check that is too see what is happening on the wire either by debug or by running a wire shark    pxe should work fine on a trunk or an access port  ... View more

Hi Thats all that's required in terms of config on the Cisco side so the DHCP will need to be debugged or caught in a pcap as its trying to initiate the boot to see if the DHCP offers and request are going and coming through the vlan interface to get to the PXE server , the only job for the switch is to forward the replay form broadcast to uni cast into the next vlan to the specifically set PXE server ... View more