One of my switches SW03 (1.33) is unable to ping anything in the 254 subnet/VLAN. when I do a sh arp I see numerous subnets coming in from my Gig1/1/2 interface which connects to my to SW00 switch. The guy before me setup this up in a odd way where that interface has a 1.33 address (configured no switch port) and the port on the other side is configured to vlan 255 (subnet 1.0). I have 2 other interfaces (Gig1/1/1 & Gigi 1/1/14) that appear to be trunking all vlans to include 254 but sh arp shows everything is coming in through Gig1/1/2
When I traceroute to *.*.254.1, 254.9 or others I get a route that sends me to other access switches (*.*.1.38) which confounds me.
I would think when you do a sh arp you should be able to ping any of the addresses in that arp table?
I did a sh spanning-tree blocked ports and shows me VLAN0001,131,139,155,255 blocked on gi1/1/1 (SW04), but that should not be affecting anything right?
This switch has no routing statements in it so it is acting as a layer 2.
Any extra tips or commands would be appreciated at this point.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.