Updating Local IP Address Pools for JUNOSe VRs
When you reconfigure local IP address pools on a JUNOSe VR, you must update in the directory the local IP addresses that the VR provides.
Before you update local IP address pools, make sure that:
- The JUNOSe router and VR appear in the directory.
- The VR has an operating SNMP agent.
- The host that supports SDX Admin or the SAE can communicate with the VR through SNMP.
- You have write permissions for the o=Network subtree.
There are two ways to add routers to the directory:
- SDX Admin—Updates on VR at a time.
- The poolRepublish command—simultaneously updates any number of VRs in the same directory.
Updating Local IP Address Pools with SDX Admin
To allow updates of IP address pools with SDX Admin, the host that supports SDX Admin must be able to communicate with the VR through SNMP. To update local IP address pools for a VR in the directory with SDX Admin:
- In the navigation pane, expand o=Network.
- In the navigation pane, expand the object for the router on which the VR is configured.
- Right-click the object for the VR in the navigation pane.
- Select Update IP Pools.
The SDX Admin dialog box appears.
- Enter the IP address for the VR, enter the SNMP community if the default value is incorrect, and click OK.
SDX Admin updates the local IP addresses for the VR in the directory and displays the information in the Local IP Address field of the Main tab in the VirtualRouter pane.
Updating Local IP Address Pools with the poolRepublish Command
You can use the poolRepublish command on the SAE host to update local IP address pools. You can specify multiple VRs with the poolRepublish command that use the same SNMP read community. For each VR you must specify the name of the VR, the name of the JUNOSe router on which it is configured, the VR's corresponding IP address, and the directory connection.
To update local IP addresses using the poolRepublish command:
- On the SAE host, access the folder /opt/UMC/sae/etc.
cd /opt/UMC/sae/etc- Run the command.
./poolRepublish -v vr1@erx1 -i 192.0.2.1 -v vr2@erx2 -i 192.0.2.3 -h 192.0.2.5 -w admin123 -D cn=umcAdmin,o=umc -b o=Network,o=umc -c publicThe software updates and displays the local IP address pools for each VR you specified.
vr1@erx1 pools: ([10.227.11.242 10.227.11.250][10.227.11.226 10.227.11.239]{10.227.11.208/255.255.255.240}{10.227.11.240/255.255.2 55.240}{10.227.11.224/255.255.255.240})vr2@erx2: ([10.227.12.242 10.227.12.250][10.227.12.226 10.227.12.239]{10.227.12.208/255.255.255.240}{10.227.12.240/255.255.2 55.240}{10.227.12.224/255.255.255.240})Syntax of poolRepublish Command
The syntax for the poolRepublish command is:
poolRepublish { { -v <vrName>@<routerName> -i <ipAddress>}*
-h <host> -b <baseDn> -D <bindDN> -w <password>
-c <readCommunity> ] | -H }<vrName>
- Name of the VR.
- Value—Text string (value is case sensitive and must match the name in the JUNOSe configuration)
- Guideline—You must enter a value for this property.
- Example—vr-boston
<routerName>
- Name of JUNOSe router on which VR is configured.
- Value—Text string (value is case sensitive and must match the name in the JUNOSe configuration)
- Example—erx1
<ipAddress>
<host>
- IP address or name of the host that supports the directory.
- Value—IP address or text string
- Example—192.0.2.2 or ottawa
<baseDn>
<bindDn>
- DN of the username for authentication with the directory server.
- Value—DN
- Example—cn=umcAdmin, o=umc
<password>
<readCommunity>
- Name of the SNMP read community for the VR. If the SNMP read community for a VR is defined in the directory, you do not need to specify this value.
- Value—Text string
- Example—public
-H
Troubleshooting the poolRepublish Command
You must specify the correct arguments for the poolRepublish command. In addition, the specified router and directory must be available for the command to run successfully.
If no SNMP read community is configured in the directory for the VR and you do not specify this value when you run the poolRepublish command, you will see the following error message:
Could not perform ip pools update due to No 'snmpReadCommunity' attribute is provided for virtual router: vr1@bigfootIf you run the poolRepublish command again and supply this SNMP read community, the command should run correctly.