nv-l
[Top] [All Lists]

[nv-l] Strange Situation Regarding Selection Name

To: <nv-l@lists.us.ibm.com>
Subject: [nv-l] Strange Situation Regarding Selection Name
From: "Catalina Martinez" <Catalina.Martinez@tlc.state.tx.us>
Date: Fri, 24 Mar 2006 10:22:34 -0600
Delivery-date: Fri, 24 Mar 2006 16:23:12 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcZPXyhy0rVZVekyTWC/+czFV32QOg==
Thread-topic: Strange Situation Regarding Selection Name

Hello,

 

Netview 7.1.4 FP 4

AIX 5.2 ML 6

 

Our devices (servers, switches and routers) were discovered and selection name was the fully qualified name (from DNS). Several nodes discovered after initial discovery, discovered ok, dns name used in selection name.

 

PROBLEM: Something happened last night, all the WAN devices (and a few servers) had IP addresses in  the Selection Name instead of the FQN (yesterday afternoon  the selection name was the fully qualified name. If I do a demand poll, the SELECTION NAME/IP is changed to the fully qualified name.

 

1)There is no indication that the NODES were deleted or added.

 

2)DNS is being run on the Netview Server (so Netview is its own dns server).

 

3) what would cause Netview to change the Selection Name?

 

4)  the only traps, are "System Name Change" on the event windows starting at around 5:45pm yesterday.

 

Any ideas on how to troubleshoot this?

 

Thanks

 

<Prev in Thread] Current Thread [Next in Thread>
  • [nv-l] Strange Situation Regarding Selection Name, Catalina Martinez <=

Archive operated by Skills 1st Ltd

See also: The NetView Web