Hi Chet,

Thanks for your persistence on this issue. I have found out a few more things and noted them below...

Chet Luther wrote:
I dug into this, and now understand what the problem is. Unfortunately
I can't come up with an easy solution for it. FreeBSD has a concept of
"cloned" routes that are automatically generated by the kernel. In
your netstat output you can see that your 10.200/24 route has the UC
flags. The C stands for clone. This means that anytime your system
looks up a route in that network, a cloned route will be generated.
NetSNMP is reporting these cloned routes thus causing Zenoss not to be
able to model your routing table properly.

I don't think that is the exact issue here since the other interfaces that are links are also flagged with the same flags, but show up as direct routes in the zenoss OS screen.

This issue only occurs on boxes that are allowed to route packets between interfaces by using the gateway_enable flag in rc.conf. Aparently once you do this it chooses one of the interfaces and adds a route that represents the broadcast address into the table. This is the entry flagged with a "b".

I have 3 servers setup this way and all three of them have this same behavior. The interface flagged with a "b" won't show on the zenoss routes. It doesn't matter if it is an internal private IP or a public routeable IP as I have boxes doing it for either one.

It seems like a bug in the zenoss discovery phase and modeling to ignore these routes. What do you think?

The third option and maybe easiest option would be to live without the
topology detection until 2.0 comes out and you can manually set your
routes.

I'll look forward to 2.0 for sure so I can more easily work around these issues.

Thanks Again,
Calvin


--
S i x  F e e t  U p , I n c .  |  "Nowhere to go but open source"
Silicon Valley: +1 (650) 401-8579 x602
Midwest: +1 (317) 861-5948 x602
Toll-Free: 1-866-SIX-FEET
mailto:[EMAIL PROTECTED]
http://www.sixfeetup.com  |  Zope/Plone Custom Development

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to