Hi Antonis, When the loss of connectivity happens - do you still have a valid ARP entry on the ME3600 for the Patton? If so - what happens if you clear that ARP entry on ME3600 manually and then try to ping the Patton?
kind regards Pshem On 4 July 2013 04:56, Antonis Vosdoganis <[email protected]> wrote: > There are 2 traces one from 3600 and one from 2960. The one you are > refering is from 2960. With 2960 there is no problem. > Στις 3 Ιουλ 2013 7:31 μ.μ., ο χρήστης "Aaron" <[email protected]> έγραψε: > >> you mentioned... >> >> > Cisco ME3600X is not responding to Patton ARP request so Patton is >> > losing ip connectivity since is thinking that Default Gateway is down. >> >> ...but i see in this wireshark sniff "ARP_WS-C2960G-8TC-L.pcapng" frame >> number 14 that the cisco (i assume it's the me3600) does in fact arp reply >> to the patton... >> >> 00 21 d7 cb 69 c1 - sender mac - cisco says i am 46.245.137.1 >> >> 00 a0 ba 05 ad c3 - target mac - patton - 46.245.137.3 >> >> to prove that the cisco me3600 is sending this maybe you could... >> >> sh interface | in bia >> >> look for "0021.d7cb.69c1" >> >> Aaron >> >> >> -----Original Message----- >> From: Nick Hilliard [mailto:[email protected]] >> Sent: Wednesday, July 03, 2013 11:18 AM >> To: Antonis Vosdoganis >> Cc: Aaron; cisco-nsp >> Subject: Re: [c-nsp] CISCO ME3600X ARP ISSUE >> >> Can't really tell much from the pcap files: >> >> http://cloudshark.org/captures/ac6ed1c8470a >> http://cloudshark.org/captures/fda45ed488b0 >> >> The timestamps don't overlap. >> >> If it works and then stops working, that could be an arp/L2 cam timeout. >> Make sure that the arp timer on the switch is configured to be lower than >> the cam timer on your 2960. >> >> me3600: show interfaces vlan 333 | i ARP >> c2960: show mac address-table aging-time >> >> Nick >> >> On 03/07/2013 17:05, Antonis Vosdoganis wrote: >> > Sorry if i didn't make it clear. There is ip connectivity when i boot >> > up the patton gateway. The problem appears 20 minutes after when >> > patton sends the arp request. >> > >> > Also the traffic from patton is untagged that's why encapsulation >> > untagged is applied under service instance. >> > >> > Patton has ip address 46.245.137.3 255.255.255.248 and static route >> > 0.0.0.0 >> > 0.0.0.0 46.245.137.1 >> > >> > I am not in the office to send you the 2960 configuration but i will >> tomorrow. >> > >> > I am attaching again the traces. >> > >> > >> > >> > On Wed, Jul 3, 2013 at 6:15 PM, Aaron <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > As Nick mentioned, given you are untagging on the patton side, since >> you >> > should be since you are untagged on the me3600 service instance >> 333... >> > >> > Go to the " Patton SmartNode 4528 Voip Gateway Router" and check it's >> ip >> > address, subnet mask and def gw .... make sure they are ... >> > >> > Ip address - ip address 46.245.137.2 or .3 or .4 or .5 or .6 >> > Mask - 255.255.255.248 >> > Def gw - 46.245.137.1 >> > >> > Aaron >> > >> > >> > -----Original Message----- >> > From: cisco-nsp [mailto:[email protected] >> > <mailto:[email protected]>] On Behalf Of Nick >> > Hilliard >> > Sent: Wednesday, July 03, 2013 9:46 AM >> > To: Antonis Vosdoganis >> > Cc: [email protected] <mailto:[email protected]> >> > Subject: Re: [c-nsp] CISCO ME3600X ARP ISSUE >> > >> > On 03/07/2013 13:30, Antonis Vosdoganis wrote: >> > > I am facing a issue with our Metro Ethernet switch. I have directly >> > > connected a Patton SmartNode 4528 Voip Gateway Router to the Cisco >> > > Switch which is the Default Gateway (46.245.137.1). Patton GW every >> 20 >> > > minutes sends an ARP request asking for default gateways mac >> address. >> > > >> > > Cisco ME3600X is not responding to Patton ARP request so Patton is >> > > losing ip connectivity since is thinking that Default Gateway is >> down. >> > >> > Hi Antonis, >> > >> > Your attachments didn't come through. Can you post them on >> > http://cloudshark.org/ so that we can take a look? >> > >> > > Routing Protocol is ISIS. I have made the some tests with a >> Catalyst >> > > 2960G which is responding to Patton ARP request. >> > >> > ISIS has nothing to do with default gateways. >> > >> > You haven't provided enough configuration to determine what the >> problem is. >> > What vlan is the patton device connected to, and what are the port >> > configuration settings on the Catalyst 2960G for the ports which >> connect to >> > the ME3600 and the Patton device. >> > >> > If the patton device is on vlan 333 and the 2960G-ME3600X link is >> > configured >> > as a dot1q trunk on the 2960 side, then you need to use this on the >> ME3600X >> > side: >> > >> > -- >> > interface GigabitEthernet0/23 >> > switchport trunk allowed vlan none >> > switchport mode trunk >> > service instance 333 ethernet >> > encapsulation dot1q 333 >> > rewrite ingress tag pop 1 symmetric >> > bridge-domain 333 >> > >> > interface Vlan333 >> > [blah] >> > -- >> > >> > Nick >> > >> > > >> > > >> > > >> > > Switch Port configuration >> > > >> > > interface GigabitEthernet0/23 >> > > >> > > switchport trunk allowed vlan none >> > > >> > > switchport mode trunk >> > > >> > > load-interval 30 >> > > >> > > service instance 333 ethernet >> > > >> > > encapsulation untagged >> > > >> > > service-policy input CORPORATE_IN_10MB >> > > >> > > service-policy output CORPORATE_OUT_10MB >> > > >> > > bridge-domain 333 >> > > >> > > >> > > >> > > interface Vlan333 >> > > >> > > bandwidth 10000 >> > > >> > > ip address 46.245.137.1 255.255.255.248 >> > > >> > > load-interval 30 >> > > >> > > >> > > >> > > #show ip protocols >> > > >> > > *** IP Routing is NSF aware *** >> > > >> > > Routing Protocol is "isis" >> > > >> > > Outgoing update filter list for all interfaces is not set >> > > >> > > Incoming update filter list for all interfaces is not set >> > > >> > > Redistributing: static, isis >> > > >> > > Address Summarization: >> > > >> > > None >> > > >> > > Maximum path: 4 >> > > >> > > Passive Interface(s): >> > > >> > > Vlan333 >> > > >> > > Loopback0 >> > > >> > > >> > > >> > > Cisco ME3600X is running IOS me360x-universalk9-mz.153-1.S1.bin >> > > >> > > I have attached 2 wireshark traces one from 3600 and one from 2960. >> > > >> > > >> > > >> > > Regards >> > > >> > > >> > > >> > > Antonis. >> > > _______________________________________________ >> > > cisco-nsp mailing list [email protected] >> > <mailto:[email protected]> >> > > https://puck.nether.net/mailman/listinfo/cisco-nsp >> > > archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > >> > >> > _______________________________________________ >> > cisco-nsp mailing list [email protected] >> > <mailto:[email protected]> >> > https://puck.nether.net/mailman/listinfo/cisco-nsp >> > archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > >> > >> >> > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
