Hi Roberto,
I'm assuming you are using the trunk. Ticket 1121 is marked as fixed.
Is it still a problem?
Can Zenoss read the route table at that first router? Try this:
$ zenmodeler run --collect=Route --force
Zenoss tries to be smart and not re-read cisco configs if cisco says the
configuration has not changed. The --force option overrides this behaviour.
-Eric
Roberto Parra wrote:
Hi,
at now:
after the "BIG CHANGE TO TRUNK" event i'm having the "not in topology"
message on every router after the first.
I've run also the "zenmodeler run --collect=Route" but nothing change.
Can you help me?
<http://dev.zenoss.org/trac/ticket/1121>
http://dev.zenoss.org/trac/ticket/1121
When do you think you'll fix this bug?
It's impossible to use syslog events.
Regards
Roberto
------------------------------------------------------------------------
_______________________________________________
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
