I have an SF-302 configured in router mode and I'm trying to figure out why it's dropping traffic that's supposed to be switched from one port to another. Very simple config (this is the entire config):
port monitor gigabitethernet2 tx
interface vlan 1
ip address 192.168.1.1 255.255.255.128
ip address 192.168.2.2 255.255.255.252
ip route 0.0.0.0 0.0.0.0 192.168.2.1
interface vlan 1
no ip address dhcp
bonjour interface range vlan 1
no snmp-server server
switchport mode access
What's happening is that I have two JDSU ethernet testers - one is at 192.168.1.2 and one is at 192.168.2.1. I am able to ping both of them from the switch and both IPs are the ARP table:
They are also able to ping each other without fail. When I attempt a traffic load test from 192.168.2.1, the traffic reaches the 192.168.1.2 device connected to Fa1, loops back as it should, and the 192.168.1.2 device sends the traffic back through Fa1, but it never gets to its destination on Gi2. It's silently dropped within the switch. No errors on the interface counters, either.
There is nothing connected to this switch (it's in a lab) besides these two testers and a Wireshark capture server on Fa8. Wireshark doesn't seem to show any problems with the packets or frames that would cause them to be dropped. If there were such problems, I would imagine they would be dropped prior to entering port Fa1.
The same two testers connected to an ME3400-2CS with the same routing configuration work fine, so I'm confident it's not the tester configuration. How can I tell where or why the traffic is being dropped?
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.