[c-nsp] Cisco 7304-NSE100 ICMP messages originated from 0.0.0.0

[Tassos Chatzithomaoglou]

Yes, that is a "known" bug of PXF, EC and SB IOS.

 > CSCsj02377
 > ICMP messages generated on port channels use 0.0.0.0 address (from phy)
 >
 > Release-note:
 > =================
 > Symptom:
 > ICMP unreach messages generated by c10k when port channels in use
 >
 > Conditions:
 > when the port channel is obliged to generate an icmp unreach
 >
 > Workaround:
 > none.
 >
 > ===


We're waiting for a fix in next SB release (according to the DE).
If you disable PXF, it should work fine.

--
Tassos


Michiel Van Opstal wrote on 22/1/2008 11:50 μμ:
> Dear Colleagues,
> 
> I have a cisco 7304 with Dual NSE100 in SSO config running 12.2(31)SB10
> and I am observing ICMP messages being sent from 0.0.0.0 as source
> address. Did anyone observe this behaviour before?
> I am suspecting this meight be related to port-channel configuration on this specific 7304.
> 
> 
> future# traceroute www.google.be
> traceroute: Warning: www.google.be has multiple addresses; using 66.249.93.147
> traceroute to www.l.google.com (66.249.93.147), 30 hops max, 40 byte packets
>  1  193.202.9.1 (193.202.9.1)  0.413 ms  0.311 ms  0.285 ms
>  2  * * *
>  3  ge-4-0.bb1.bru2.be.gbxs.net (193.27.64.50)  34.700 ms  198.130 ms  6.055 ms
>  4  so-7-0-0-0.bb1.ams3.nl.gbxs.net (83.143.243.18)  5.168 ms  4.950 ms  4.976 ms
>  5  core2.ams.google.com (195.69.145.100)  5.403 ms  5.203 ms  5.186 ms
>  6  209.85.254.90 (209.85.254.90)  5.834 ms  5.587 ms  5.606 ms
>  7  72.14.232.141 (72.14.232.141)  8.466 ms  15.522 ms  8.153 ms
>  8  72.14.233.83 (72.14.233.83)  8.592 ms  8.360 ms  8.243 ms
>  9  66.249.94.54 (66.249.94.54)  8.917 ms  18.335 ms  17.992 ms
> 10  ug-in-f147.google.com (66.249.93.147)  9.133 ms  9.215 ms  9.738 ms
> 
> 
> 
> 21:39:01.096148 IP 193.202.9.1 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:01.097391 IP 193.202.9.1 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:01.097788 IP 193.202.9.1 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 
> 21:39:01.098675 IP 0.0.0.0 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:06.099358 IP 0.0.0.0 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:11.100158 IP 0.0.0.0 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 
> 21:39:16.134864 IP ge-4-0.bb1.bru2.be.gbxs.net > future.as3322.net: ICMP time exceeded in-transit, length 148
> 21:39:16.334467 IP ge-4-0.bb1.bru2.be.gbxs.net > future.as3322.net: ICMP time exceeded in-transit, length 148
> 21:39:16.340555 IP ge-4-0.bb1.bru2.be.gbxs.net > future.as3322.net: ICMP time exceeded in-transit, length 148
> 21:39:16.345534 IP so-7-0-0-0.bb1.ams3.nl.gbxs.net > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.351504 IP so-7-0-0-0.bb1.ams3.nl.gbxs.net > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.356497 IP so-7-0-0-0.bb1.ams3.nl.gbxs.net > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.361742 IP core2.ams.google.com > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.382117 IP core2.ams.google.com > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.387332 IP core2.ams.google.com > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.392948 IP 209.85.254.90 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.625195 IP 209.85.254.90 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.630835 IP 209.85.254.90 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.639089 IP 72.14.232.141 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.740594 IP 72.14.232.141 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.748776 IP 72.14.232.141 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.757164 IP 72.14.233.83 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.939347 IP 72.14.233.83 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.947625 IP 72.14.233.83 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:16.956294 IP 66.249.94.54 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:17.136511 IP 66.249.94.54 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:17.154543 IP 66.249.94.54 > future.as3322.net: ICMP time exceeded in-transit, length 36
> 21:39:17.163454 IP ug-in-f147.google.com > future.as3322.net: ICMP ug-in-f147.google.com udp port 33462 unreachable, length 36
> 21:39:17.340377 IP ug-in-f147.google.com > future.as3322.net: ICMP ug-in-f147.google.com udp port 33463 unreachable, length 36
> 21:39:17.350141 IP ug-in-f147.google.com > future.as3322.net: ICMP ug-in-f147.google.com udp port 33464 unreachable, length 36
> 
> 
> Kind Regards,
> Michiel
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>