If your firewall blocks ping then that's your problem. Your MLM will
merrily discover nodes on the same network as himself and will ship the
info to NetView in SNMP packets which should get through your firewall
on eithe TCP or UDP 161. However, NetView doesn't believe what an MLM
tells him unless he can get at least one ping from NetView to the end
node. If you find this behaviour perverse, please add a "me too" to my
enhancement request about this on
http://www.nv-l.org/twiki/bin/view/Netview/NetViewEnhancements#Enhancements_to_Mid_Level_Manage
Your best bet if you have 150 nodes out there is to construct a script
that uses the NetView loadhosts command to manually add them to the
NetView database and then configure those nodes in netmon.seed to be
SNMP-polled.
Effectively, MLM is a dead-duck for node discovery if it is behind a
ping-blocking firewall.
Cheers,
Jane
alejandro.gabay@reuters.com wrote:
Hi. We have a Netview 7.1.4 FP2 on Solaris 8. It is facing an NT MLM running on
a Windows 2000.
When running smconfig against the MLM NT. We see lots of discovered nodes
(around 150) but on the Netview itself we see no one. The connection between
the MLM and the NEtview server is going trhough a firewall that only pases TCP
UDP 161 and 162. Does anyone knows if MLM uses another port to pass objects'
status to the Netview Server?
B. Regards
Alejandro
-----------------------------------------------------------------
Visit our Internet site at http://www.reuters.com
To find out more about Reuters Products and Services visit http://www.reuters.com/productinfo
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <jane.curry@skills-1st.co.uk>. All rights
reserved.
|