To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] trapd.log |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Fri, 14 May 2004 10:12:44 -0400 |
Delivery-date: | Fri, 14 May 2004 15:23:06 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <OFE3A0FE4F.99A74CA9-ON85256E94.004C82F5-85256E94.004CF44D@us.ibm.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
You should not get "Node Down" for a router. That's why there are different traps. Are you getting both Router Down and Node Down for the same devices or different ones? If different, check the object properties with ovobjprint -s <selection_name> for the affected devices. When isRouter = TRUE you should get Router Down for that device, otherwise it is Node Down. What level of code and what operating system? James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
In my trapd.log I find "Node Up" & "Node Down" traps for all types of devices including routers. There are also "Router Up" & "Router Down" traps in the log. There are very few of the "Node" traps for routers, but there are some. What is the difference between these types of traps? Thanks, Ernie Dusett IBM Global Services - Network Outsourcing Services Phone: (585)723-4311 Tie: 451 Fax: (585)720-7654 Pager: http://www.arch.com/cgi-bin/wwwpreproc.exe?PIN=5852381622 Internet: edusett@us.ibm.com |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] QoS WAN monitoring, James Shanks |
---|---|
Next by Date: | Re: [nv-l] trapd.log, Ernie Dusett |
Previous by Thread: | [nv-l] trapd.log, Ernie Dusett |
Next by Thread: | Re: [nv-l] trapd.log, Ernie Dusett |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web