nv-l
[Top] [All Lists]

FW: loadhosts Problem

To: nv-l@lists.tivoli.com
Subject: FW: loadhosts Problem
From: Stephen Elliott <selliott@epicrealm.com>
Date: Tue, 31 Oct 2000 13:50:35 -0600
My apologies, we're using NetView 6.0.1 on Solaris 2.6.

Regards,

Steve Elliott
Sr. Network Mgmt. Engineer
epicRealm, Inc.
214-570-4560

>  -----Original Message-----
> From:         Stephen Elliott  
> Sent: Tuesday, October 31, 2000 1:50 PM
> To:   'nv-l@tkg.com'
> Subject:      loadhosts Problem
> 
> All,
> 
> We build our entire database via loadhosts. While deleting and rebuilding
> one particular site, I'm getting an new error that's stopping the reload
> of the device file. Here's the command and output:
> 
> loadhosts -m 255.255.255.0 -v < /usr/sites/dfw1a.txt
> 
> Created UP host BB1.DFW1A(37174)
> Added UP interface xxx.xxx.182.124(37175)  to BB1.DFW1A
> Created UP host BB2.DFW1A(37178)
> Added UP interface xxx.xxx.182.125(37179)  to BB2.DFW1A
> Created UP host INTERXXX.DFW1A(37180)
> Added UP interface xxx.xxx.182.1(37181)  to INTERXXX.DFW1A
> Created UP host MGT301.DFW1A(37182)
> Added UP interface xxx.xxx.52.182.16(37183)  to MGT301.DFW1A
> Added UP interface xxx.xxx.182.120(37155)  to SRV3X1.DFW1A
> ERROR: Could not interface to node SRV3X1.DFW1A in topology: Requested
> object is unknown
> 
> The same file loaded completely, without error, several weeks ago. I've
> rebuilt the list with the same results. I've never seen the last response
> before: Requested object is unknown. It suggests that the node was not
> pingable, but the -p option is NOT set in the loadhosts command.
> Commenting out the offending line in the file doesn't help. The error
> occurs on the next entries as well. 
> 
> Anyone have any idea what the message means? 
> 
> Regards,
> 
> Steve Elliott
> Sr. Network Mgmt. Engineer
> epicRealm, Inc.


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web