Hi guys,
Thanks for the replies.
This would sound strange, but my PC/DHCP segments are configured to "@"
in my netmon.seed, so i guess they should be discovered and polled by
using ping.
But how come only certain PCs/DHCP IPs would be polled by snmp?
I've checked my ovsnmp.conf and there's no PC/DHCP address listed in
here.
Is there another location whereby nv store's an object's polling method?
best regards,
sixx
________________________________
From: nv-l-bounces AT lists.ca.ibm DOT com
[mailto:nv-l-bounces AT lists.ca.ibm DOT com] On Behalf Of James Shanks
Sent: Monday, January 08, 2007 10:22 PM
To: Tivoli NetView Discussions
Subject: RE: [NV-L] Objects turning red after awhile even when up?
Francois is correct. DHCP entries are indicated by "@", not by "$". You
are forcing netmon to use SNMP polling with that. Here's an excerpt from
the Window netmon.seed file
DHCP Support
#
# Use the prefix '@' to signify DHCP addresses, followed by
# the same IP address ranges that are configured on your DHCP
# servers. Use the same syntax for ranges and wildcards as the
# entries above. For instance, suppose the address
# range 1.1.1.1 to 1.1.1.255 is reserved for DHCP clients, except for
# 1.1.1.10 to 1.1.1.15 which are dedicated to print servers, etc.
# Also, everything in the range 1.2.252-255.*
# This would be represented as,
#
# @1.1.1.1-9
# @1.1.1.16-255
# @1.2.252-255.*
#
# SNMP Status Support
#
# Nodes that have serial interface cards will automatically use SNMP
# to query for ifAdminStatus and ifOperStatus for ALL interfaces on
# that node. Specify other nodes you would like to use SNMP to query
# for status instead of ICMP pings here.
#
# Use the prefix '$', and use the same syntax for ranges and wildcards
# described above. For instance,
#
# $1.1.2-10.221-230
#
# Use the prefix '^', to indicate exceptions in the ranges or wildcards,
# including routers that netmon would normally enable SNMP status
# polling such as those with Unnumbered serial interfaces.
#
# ^1.1.9-10.230
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
Francois Le Hir <flehir AT ca.ibm DOT com>
Francois Le Hir <flehir AT ca.ibm DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
01/08/2007 08:46 AM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
cc
Subject
RE: [NV-L] Objects turning red after awhile even when up?
I am using an Unix version of Netview so this "DHCP" feature is not
available for me. On my netview, the "$" means that I force the status
polling of an (or range of) object to snmp. Removing the "$" turns back
the status polling to ping. (Unless specific cases like unnumbered
interfaces...). You should double-check the documentation for your seed
file as I am surprised that $ has a different meaning on windows. I am
aware of this DHCP monitoring feature on windows, but don't remember how
is it used.
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Technology Services
Phone: (514) 964 2145
<sixxl AT cse.com DOT sg>
<sixxl AT cse.com DOT sg>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
01/07/2007 10:23 PM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
<nv-l AT lists.ca.ibm DOT com>
cc
Subject
RE: [NV-L] Objects turning red after awhile even when up?
Hi guys,
Thanks for the prompt reply!
The pc segment is already configured using "$" to signify DHCP clients.
Strange thing is this status issue only occurs to new PCs added to the
segment as they are replacing the old existing NT PCs to XP machines.
I believe the new PCs took the old IP addresses as most of them is on
DHCP and some on static.
btw how do i change the object's polling from SNMP to ping? Edit the
object in ovsnmp.conf file? Or should i delete the object and let nv
rediscover it again?
best regards,
sixx
________________________________
From: nv-l-bounces AT lists.ca.ibm DOT com [
mailto:nv-l-bounces AT lists.ca.ibm DOT com
<mailto:nv-l-bounces AT lists.ca.ibm DOT com> ] On Behalf Of Leslie Clark
Sent: Friday, January 05, 2007 10:20 PM
To: Tivoli NetView Discussions
Subject: Re: [NV-L] Objects turning red after awhile even when up?
Good answer, Francois!
Cordially,
Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
(248) 552-4968 Voicemail, Fax, Pager
Francois Le Hir <flehir AT ca.ibm DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
01/05/2007 09:02 AM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
cc
Subject
Re: [NV-L] Objects turning red after awhile even when up?
You issue is probably because netmon is trying to monitor the status of
this object using snmp instead of ping. If it doesn't answer to snmp, it
will still show down, even if it respond to ping.
The way this is configured is usually with the "$" in the netmon seed
file.
You can test if this is the problem with the quicktest command: it will
do a status polling using the same method as netmon.
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Technology Services
<sixxl AT cse.com DOT sg>
<sixxl AT cse.com DOT sg>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
01/04/2007 10:25 PM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
<nv-l AT lists.ca.ibm DOT com>
cc
Subject
[NV-L] Objects turning red after awhile even when up?
Hi there,
I'm a new netview administrator and facing an issue. We've got a netview
is a default installation with a configured netmon.seed, netview
discovers all objects and all device status are reflected properly when
down. On the user PC objects sometimes it would turn red signifying down
status. Verfication of the physical PC is up and netview doing test ping
would turn the object to green. After leaving the object for awhile it
would turn red again, even though the PC is up.
Please advice on what steps should I take to resolve this issue.
The netview is 7.1.4 FP4 running on a windows 2003 server and console is
using remote desktop to monitor the netview.
Best regards,
Sixx
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l
<http://lists.ca.ibm.com/mailman/listinfo/nv-l> (Browser access limited
to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l
<http://lists.ca.ibm.com/mailman/listinfo/nv-l> (Browser access limited
to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l
<http://lists.ca.ibm.com/mailman/listinfo/nv-l> (Browser access limited
to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
