Hi Valery,

Zenoss is unable to determine by the collected routing tables how to get from your zenoss machine to each of the machines listed below. It knows it can reach them, it just doesn't know which device provides access. This could happen if you have a router that is not modeled, or if a default route is hiding how data is routed.

-Eric

Valery V. Bobrov wrote:
Hello!

I have messages in zenping .log


2007-01-09 18:33:05 WARNING zen.ZenStatus: device 
'vrn04sa.yugovostok.transtk.ru' network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 
'sdsl77da.yugovostok.transtk.ru' network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 'etc1rc' network 
'10.16.29.1/32' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 'sdsl46da' network 
'10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 
'vrn03sa.yugovostok.transtk.ru' network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 
'dlink65.yugovostok.transtk.ru' network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 'ups65.yugovostok.transtk.ru' 
network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 'ups77.yugovostok.transtk.ru' 
network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 
'vrn02sb.yugovostok.transtk.ru' network '10.50.0.0/16' not in topology
2007-01-09 18:33:05 WARNING zen.ZenStatus: device 'sdsl65da' network 
'10.50.0.0/16' not in topology

What does this mean?
and how can it be solved?

Thank you

Yours sincerely,
   Valery
E-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------

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

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

Reply via email to