nnmnodedelete.ovpl — Remove node(s) and associated data from the NNM topology database
nnmnodedelete.ovpl
-help |
-node <hostName> |
-rm <Regional NNMi management server> |
-file <filename>
[-u <username> -p <password>]
[-jndiHost <hostName> Default: localhost]
[-jndiPort <port> Default: 1099]
nnmnodedelete.ovpl removes a node and
its associate data like interfaces, ip addresses etc from the system.
If this results in empty VLANs and/or subnets they will be removed as well.
If incidents point to this node, the Source Node field will be blanked out,
but the incidents will not be removed.
The node is identified using the hostName field.
The -rm option accepts the name of a Regional NNMi management server. Nodes that are managed by that Regional Manager, will be removed from the local database.
The -file option accepts a file with a single entry specified per line. Each line has the following format:
HostName # (optional comment to help identify the node, if desired)
Where:
HostName = the host name of the node you wish to add.
Comments can be deliminated with a # character.
nnmnodedelete.ovpl supports the following options:
-node <hostName>
The hostname of the node to delete.
-rm <RegionalManagerName>
The name of the Regional NNMi management server.
-file <fileName>
Specify a text file to read the nodes from.
-u <username>
Supply the NNMi administrator username to run the script. This script requires
the NNMi administrator username unless you use an nnm.properties file.
See the nnm.properties.4 reference page for more information.
-p <password>
Supply the NNMi administrator password to run the script. This script requires
the NNMi administrator password unless you use an nnm.properties file.
See the nnm.properties.4 reference page for more information.
-jndiHost <serverName>
The server JNDI host; default is
localhost.
-jndiPort <port>
The server JNDI port; default is 1099.
-help
Prints the usage statement.
nnmnodedelete.ovpl -u username -p password -node myNode
Removes the node myNode.
(You must provide an NNM username and password.)
nnmnodedelete.ovpl -u username -p password -rm myRegionalManager
Removes all nodes associated with myRegionalManager
(You must provide an NNM username and password.)
nnmnodedelete.ovpl -u username -p password -file myFile
Reads the nodes specified in the myFile file
and attempts to remove them from the database.
(You must provide an NNM username and password.)
nnmnodedelete.ovpl returns the following exit codes:
0
Operation was successful.
1
An error occured; see error message for details.
2
Partly successful but some nodes were not deleted; see error messages for details.
The deleted node could be rediscovered if it was created due to a
Auto Discovery Rule.
The workaround would be to add the node's ip address to
the Excluded IP Addresses entry
in the Discovery Configuration form.
nnmseeddelete.ovpl(1M), nnmnoderediscover.ovpl(1M), nnmtopodump.ovpl(1M), nnmresetembdb.ovpl(1M), nnm.properties(4).