|
Your comment on poll_all_ports happens to be opposite of the true meaning. I have grabbed some information from the troubleshooting guide and will place it here: From:
poll_all_ports=y To:
poll_all_ports=n With this configuration (poll_all_ports=n), the PSM function only status polls switch ports that do not have connections to them, which are devices attached to switch ports as determined by IBM Tivoli Switch Analyzer. The Layer 2 Discovery Report, as well as the Physical View of a switch via the Web Console, will indicate which switch ports have connections. These particular connected ports will be the ports "not" actually monitored by PSM when the poll_all_ports value is set to n. For these connected ports not monitored by PSM in this scenario, the NetView Interface Down event will trigger the correlation engine as before and result in the root cause event being generated for these particular ports. In general, when poll_all_ports is set to n, PSM will only manage (poll) switch ports that do not have connections to them, which include the following ports: 1. Switch ports in a redundant layer 2 path
Is it possible in ITSA to select specific ports on a switch to be status polled? My understanding of poll_all_ports in correlator.ini is that if you set it to no then it will only poll ports that have NetView-discovered layer 3 devices attached, rather than polling all ports? What happens if those attached devices are unmanaged? Does the switch port still get polled? Is there any way to look at a port (ideally in the physical view but any mechanism would do) and say "stop port monitoring on ports 1, 3 and 27", for example. Or," stop monitoring all ports whose names start fa*". Thanks, Jane -- 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.
|
Jane Curry <jane.curry@skills-1st.co.uk>
