On 4/27/07, Calvin Hendryx-Parker <[EMAIL PROTECTED]> wrote:
Chet Luther wrote:
> What's the output of: snmpwalk -v2c -c public localhost .1.3.6.1.2.1.4.21
bash-2.05b$ snmpwalk -v2c -c public localhost .1.3.6.1.2.1.4.21
RFC1213-MIB::ipRouteDest.10.200.0.0 = IpAddress: 10.200.0.0
RFC1213-MIB::ipRouteDest.10.200.0.1 = IpAddress: 10.200.0.1
RFC1213-MIB::ipRouteDest.10.200.0.2 = IpAddress: 10.200.0.2
RFC1213-MIB::ipRouteDest.10.200.0.3 = IpAddress: 10.200.0.3
RFC1213-MIB::ipRouteIfIndex.10.200.0.0 = INTEGER: 1
RFC1213-MIB::ipRouteIfIndex.10.200.0.1 = INTEGER: 5
RFC1213-MIB::ipRouteIfIndex.10.200.0.2 = INTEGER: 1
RFC1213-MIB::ipRouteIfIndex.10.200.0.3 = INTEGER: 1
RFC1213-MIB::ipRouteNextHop.10.200.0.0 = IpAddress: 10.200.0.1
RFC1213-MIB::ipRouteNextHop.10.200.0.1 = IpAddress: 10.200.0.1
RFC1213-MIB::ipRouteNextHop.10.200.0.2 = IpAddress: 10.200.0.1
RFC1213-MIB::ipRouteNextHop.10.200.0.3 = IpAddress: 10.200.0.1
RFC1213-MIB::ipRouteType.10.200.0.0 = INTEGER: direct(3)
RFC1213-MIB::ipRouteType.10.200.0.1 = INTEGER: direct(3)
RFC1213-MIB::ipRouteType.10.200.0.2 = INTEGER: direct(3)
RFC1213-MIB::ipRouteType.10.200.0.3 = INTEGER: direct(3)
RFC1213-MIB::ipRouteProto.10.200.0.0 = INTEGER: local(2)
RFC1213-MIB::ipRouteProto.10.200.0.1 = INTEGER: local(2)
RFC1213-MIB::ipRouteProto.10.200.0.2 = INTEGER: local(2)
RFC1213-MIB::ipRouteProto.10.200.0.3 = INTEGER: local(2)
RFC1213-MIB::ipRouteMask.10.200.0.0 = IpAddress: 255.255.255.255
RFC1213-MIB::ipRouteMask.10.200.0.1 = IpAddress: 255.255.255.255
RFC1213-MIB::ipRouteMask.10.200.0.2 = IpAddress: 255.255.255.255
RFC1213-MIB::ipRouteMask.10.200.0.3 = IpAddress: 255.255.255.255
I've snipped the irrelevant portions of that output out. Do you know
why your routing is setup this way? It looks like your interface is
setup with an IP of 10.200.0.1 and a netmask of 255.255.255.255, then
specific host routes (netmask 255.255.255.255) were added for every
single host on that subnet.
I don't presume to know how your network is setup, but off the top of
my head I can't understand why this would be necessary. Maybe you
could just set the netmask on that interface to 255.255.255.0 and
delete all of those host specific routes?
I'm probably missing something.. please let me know what it is. =}
--
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
