About jrobnett

jrobnett · 09-11-2009

We recently upgraded a Catalyst 4506 switch fromcat4000-is-mz.121-13.EW.bin tocat4500-entservices-mz.122-53.SG.binThe switch has multiple VLAN's with catalyst 3550 switches connected to it.We have numerous Linux, Windows, Printers that require DHCP t...

jrobnett · 09-11-2009

We recently upgraded a Catalyst 4506 switch fromcat4000-is-mz.121-13.EW.bin tocat4500-entservices-mz.122-53.SG.bin The switch has multiple VLAN's with catalyst 3550 switches connected to it. We have numerous Linux, Windows, Printers that requi...

jrobnett · 09-08-2009

We have 20+ instruments which sent multicast alerts when certain monitor values are out of range. We've recently discovered that as long as they send alerts relatively constantly we never drop a packet. If they only send alerts every 10 minutes ...

jrobnett · 09-11-2009

We now have a clear indication that its the IOS. It's not accurate to say the IOS munges up the various fields in the DHCP reply.They're being modified in a way that's different than in the older version. The Nucleus OS on these boards can't parse ...

jrobnett · 09-11-2009

We see that these boards, if on the same VLAN as the DHCP work just fine, the implication is the process of forwarding the DHCPOFFER is munging up the netmask field. When they're on the same VLAN the entire process is switched, no layer3 routing/fo...

jrobnett · 09-11-2009

No it's not at least explicitly set. The switch only has a helper address which is working fine. The DHCP server is receiving the request and sending the reply. Most devices continue to work just fine. We have some evidence that the boards are ...

jrobnett · 09-09-2009

There's some hint that the expiry timer *only* applies to sparse routes. Prior to today we had both sparse and sparse-dense routes within an (S,G) group.(10.80.126.128, 239.192.2.3), 00:00:07/00:02:52, flags: T Incoming interface: Vlan626, RPF nbr ...

jrobnett · 09-08-2009

In our environment it's many (28) devices sending to few (2 or 3) logging hosts. I think we'll be ok memory wise. Generally all mappings are resident anyway. It's when they go quiescent for longer than the expire time and have to be recreated ...

Member Since	‎04-03-2008 12:11 PM
Date Last Visited	‎08-18-2017 03:53 AM
Posts	9
Total Helpful Votes Received	4

User Statistics

User Activity

DHCP forwarding issue with 122-53.SG

DHCP forwarding issue with 122-53.SG

sg-expiry-timer and show ip mroute output

Re: DHCP forwarding issue with 122-53.SG

Re: DHCP forwarding issue with 122-53.SG

Re: DHCP forwarding issue with 122-53.SG

Re: sg-expiry-timer and show ip mroute output

Re: sg-expiry-timer and show ip mroute output