nnmloadipmappings.ovpl — load overlapping IP address information
nnmloadipmappings.ovpl
-f mapping file
[-u <username> -p <password>]
[-jndiHost <hostName> Default: localhost]
[-jndiPort <port> Default: 1099]
nnmloadipmappings.ovpl allows
customer to load IP address mappings configured in static NAT
[RFC2663] environment from a text file. The loaded mappings
will be populated into the corresponding IP Address inventory.
The -f option accepts a file with a single entry specified per line. Each line has the following format:
Tenant Name, "Public IP Address", "Private IP Address"
Where:
Tenant Name = The name of a tenant.
Public IP Address = A specific NATed IPv4 address exposed to the ourside network.
Private IP Address = A specific internal IPv4 address corresponding to the NATed public IP address.
Comments can be deliminated with a # character.
Note that one public IP address can only map to one private IP address in a tenant. Same for the private IP address in a tenant, it only can map to one public IP address. However, multiple mappings on a device is supported.
The nnmloadipmappings.ovpl command recognizes the following parameters and options:
-f mapping file
Specify a text file to read the IP Address mappings from.
-u <username>
Supply the NNMi administrator password to run the script. Required unless a nnm.properties(4) file exists.
-p <password>
Supply the NNMi administrator password to run the script. Required unless a nnm.properties(4) file exists.
-jndiHost <serverName>
The server JNDI host; default is
localhost.
-jndiPort <port>
The server JNDI port; default is 1099.
Load IP address mappings from a file name that is named Tenant1Mappings.txt:
nnmloadipmappings.ovpl -f /tmp/Tenant1Mappings.txt
Load IP address mappings from a file name that is named Tenant2Mappings.txt with username and password:
nnmloadipmappings.ovpl -u username -p password -f /tmp/Tenant2Mappings.txt