RE: [nv-l] ping timeout in NV
2002-03-19 19:26:05
I have two AIX 4.3.3 systems. One running NetView 7.1 and one running NetView 6.0.2
On 6.0.2 if I set the timeout value using xnmsnmpconf, and then use nmdemandpoll to demand poll the device, the timeout value shown by ovtopodump has changed. (It did NOT change, until I performed the demand poll).
On 7.1 this does not work. I set the timeout value using xnmsnmpconf->replace->apply->cancel (just like 6.0.2) and then nmdemandpoll the ip address (the ip address was the same as the entry I replaced in xnmsnmpconf). The timeout value is not changed.
In release 6.0.2 I ran ovtopodump -rlo nnn (object id of the node), and saw:
CREATE TIME: Wed Oct 10 09:26:05 CDT 2001
MODIFIED TIME: Tue Mar 19 17:56:31 CST 2002
SYMBOL CHANGE TIME: Tue Mar 19 17:56:31 CST 2002
On 7.1 nmdemandpoll did not update the MODIFIED TIME, or SYMBOL CHANGED TIME of the node. All three entries remained the same.
CREATE TIME: Wed Mar 13 12:02:07 CST 2002
MODIFIED TIME: Wed Mar 13 12:02:07 CST 2002
SYMBOL CHANGE TIME: Wed Mar 13 12:02:07 CST 2002
Here's an excerpt from the 7.1 demand poll:
18:05:48 ***** Starting demand poll of node n3006101935.rchland.ibm.com *****
18:05:48 Interface 9.5.144.218 (currently up)
18:05:48 Interface 9.5.144.218(Token_Ring) is UP Responded to ping
18:05:48 Current polling parameters
18:05:48 scheduled configuration check at 03/20/02 17:57:29
18:05:48 scheduled new node poll at 03/19/02 19:34:30
18:05:48 auto-adjusted polling interval is 24780 seconds
18:05:48 Get system identifier
This is part of the 6.0.2 demand poll output:
17:56:31 ***** Starting demand poll of node 10.10.10.241 *****
17:56:31 Interface 10.10.10.241 (currently up)
17:56:31 Interface 10.10.10.241(utp) is UP Responded to ping
17:56:31 Current polling parameters
17:56:31 scheduled configuration check at 03/20/02 16:42:51
17:56:31 scheduled new node poll at 03/19/02 17:59:24
17:56:31 auto-adjusted polling interval is 900 seconds
17:56:31 Get system identifier
Ed Boos
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [nv-l] ping timeout in NV, James Shanks
- Re: [nv-l] ping timeout in NV, Can Huynh
- Re: [nv-l] ping timeout in NV, James Shanks
- Re: [nv-l] ping timeout in NV, Can Huynh
- RE: [nv-l] ping timeout in NV, Barr, Scott
- RE: [nv-l] ping timeout in NV, James Shanks
- [nv-l] ping timeout in NV, can huynh
- RE: [nv-l] ping timeout in NV, Barr, Scott
- Re: [nv-l] ping timeout in NV, can huynh
- RE: [nv-l] ping timeout in NV,
Ed Boos <=
|
|
|