Hello,
Waris, in this moment I cannot capture packets because the device is running
ok. So, now the packets are correctly forwarded. We changed the SFPs and
checked the SDH network and all is ok. The ME3600 has customer devices
connected that we also manage and in these customer devices we see the "input
errors" in the "show interface" command.
Ramji, during the issue, I see the input error counter and CRC. This is the
output of one of the customer devices connected to the ME3600. I see the same
in my routers and the customer devices that I manage:
GEC#sh interfaces gigabitEthernet 0/24
GigabitEthernet0/24 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is f029.299a.c018 (bia f029.299a.c018)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 3/255, rxload 15/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 1000Mb/s, media type is LX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters 10w1d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 61712000 bits/sec, 12116 packets/sec
5 minute output rate 14649000 bits/sec, 11323 packets/sec
57831794972 packets input, 37874524124404 bytes, 0 no buffer
Received 2014804 broadcasts (36949 multicasts)
0 runts, 0 giants, 0 throttles
106923 input errors, 106923 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 36949 multicast, 0 pause input
0 input packets with dribble condition detected
51903725030 packets output, 8974825457660 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Best Regards,
Jordi.
From: [email protected]
To: [email protected]; [email protected]; [email protected]
Subject: RE: [c-nsp] ME3600 FCS packet generation issue
Date: Fri, 24 Oct 2014 09:42:06 +0000
Hi Jordi,
When you say that the packet is getting dropped by the peer router, are you
seeing CRC errors on it?
Thanks,
Ramji
From: Waris Sagheer (waris)
Sent: Friday, October 24, 2014 3:11 PM
To: Jordi Magrané Roig; [email protected]
Cc: Ramji Vasudevan (ramji)
Subject: Re: [c-nsp] ME3600 FCS packet generation issue
Jordi,
Can you please capture the packet? Are there any layer 1 issue in the network?
Ramji,
Have you come across any such issue on ME3600X?
Best Regards,
Waris Sagheer
Technical Marketing Manager
Service Provider Access Group (SPAG)
[email protected]
Phone: +1 408 853 6682
Mobile: +1 408 835 1389
CCIE - 19901
This email may contain confidential and privileged material for the sole use of
the intended recipient. Any review, use, distribution or disclosure by others
is strictly prohibited.
If you are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all copies of
this message.
For corporate legal information go
to:http://www.cisco.com/web/about/doing_business/legal/cri/index.html
From:
Jordi Magrané Roig <[email protected]>
Date: Friday, October 24, 2014 at 1:12 AM
To: "[email protected]" <[email protected]>
Subject: [c-nsp] ME3600 FCS packet generation issue
Hello,
My name is Jordi. I have a strange issue with one of my
ME3600. I have a ME3600 connected to a C7609 via the G0/24 port and
connected to another ME3600 connected via G0/22 port. In the middle of
the connection between the two ME3600 there is a SDH network (Ethernet
over SDH). I have a recurring issue in the ME3600, for some reason when
the device receive a packet and forwards the packet, the device sends
the packet with FCS errors, so the other end detects the "input error"
and drops the packet. I don't know if the device sends the data
corrupted or makes wrong the calculation of the FCS. The device can work
correctly during two months and some day the device starts with this
problem. Reloading the device fixes the issue during a time. I saw the
issue for the first time at June. I changed the device, but the issue
appeared again and I upgraded the IOS from 15.3(3)S to 15.4(2)S1 but
still the same. I think that this issue could be a bug but I don't know
which event triggers the issue. Someone could help me?
Thank you very much and sorry for my English.
_______________________________________________
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/
