|
|
Assigning Multiple Virtual IP Addresses by Device or User Name
Technical Note 2165
Last Reviewed 07-Apr-2008
Applies To
Mobility client and server, version 6.00 and higher
Printer-friendly version
Summary
This tech note describes how to assign many static virtual IP addresses (VIP addresses) at once using the Sun ONE (Mobility warehouse) console.
The standard way to assign static VIP addresses to individual users or devices is via the Virtual Address—Allocation setting on the Client Settings page in the Mobility console, described in the documentation and in tech note 2166. This can be time-consuming if you need to assign a large number of IP addresses at one time. This tech note describes a way to assign multiple static VIP addresses using these steps:
Export a list of users or devices from the Mobility warehouse into a text file.
Edit the text file, adding static VIP addresses.
Import the file back into the warehouse, which will update the settings.
The procedures for assigning VIP addresses by user or device are similar, but the details vary enough that they are described separately below.
Assigning VIP Addresses by User
Mobility warehouse data is stored in the LDAP Data Interchange Format (LDIF) format. These instructions assume that the users who will be assigned a static VIP address are already defined in the warehouse.
A) Create an LDIF template with nmwdump.exe
On the Mobility Server:
Open a command prompt and point to the folder for the Mobility server:
cd \Program Files\NetMotion Server
Enter the following case-sensitive command:
Nmwdump.exe nmw-PrivObjectClass=16 dn > users.ldif
This creates a text file called users.ldif with one entry per user that will look something like this:
version: 1
dn: cn=NMWCO\\juliar,ou=NMWClientRoot,ou=NMWRoot, ...
... o=NetMotion,dc=dtest,dc=nmwco,dc=com
dn: cn=NMWCO\\ericm,ou=NMWClientRoot,ou=NMWRoot, ...
... o=NetMotion,dc=dtest,dc=nmwco,dc=com
|
Each dn is returned on one long line; an ellipsis (...) indicates where the line is wrapped.
B) Edit users.ldif and add static VIP assignments
Open users.ldif with a text editor (Notepad.exe, for example).
Add the following text below the entry for each user to whom you are assigning a static VIP address:
changetype: modify
replace: nmwAddressAllocationType
nmwAddressAllocationType: 2
-
replace: nmwStaticAddr
nmwStaticAddr: 10.128.5.60
-
replace: nmwDisplayForOverride
nmwDisplayForOverride: 1
|
where nmwStaticAddr (in bold) is set to the static VIP address. The other attributes must have the values shown above. Note the dash ('-') between attributes—this is important. Remove any users from users.ldif for whom you do not want to set a static VIP address. Be sure to leave a blank line between each entry (before each "dn: " line), as in the example below.
In this example, static VIP addresses are set for two users:
version: 1
dn: cn=NMWCO\\juliar,ou=NMWClientRoot,ou=NMWRoot, ...
... o=NetMotion,dc=dtest,dc=nmwco,dc=com
changetype: modify
replace: nmwAddressAllocationType
nmwAddressAllocationType: 2
-
replace: nmwStaticAddr
nmwStaticAddr: 10.128.5.60
-
replace: nmwDisplayForOverride
nmwDisplayForOverride: 1
dn: cn=NMWCO\\ericm,ou=NMWClientRoot,ou=NMWRoot, ...
... o=NetMotion,dc=dtest,dc=nmwco,dc=com
changetype: modify
replace: nmwAddressAllocationType
nmwAddressAllocationType: 2
-
replace: nmwStaticAddr
nmwStaticAddr: 10.128.5.61
-
replace: nmwDisplayForOverride
nmwDisplayForOverride: 1
|
C) Import users.ldif on the warehouse
On your primary warehouse (if you have only one warehouse, it is the primary) open the Sun ONE Directory Server console—on the Start menu, click Programs, Sun ONE Server Products, Sun ONE Server Console 5.2—and log in using your warehouse userid (default is admin) and password.
On the Servers and Applications tab, expand the tree until you see your Directory Server listing. Select your server, and then click Open.
On the Tasks tab, click Import from LDIF.
In the Import LDIF dialog box, enter the path to your LDIF file, or click Browse to select it.
Do not select the Add only check box.
Click OK to import the file.
D) Verify the VIP address assignments
Open the Mobility Console and verify that the users are listed on the Client Settings page and that they have static VIP addresses assigned to them.
Assigning VIP Addresses by Device
On the Mobility Server:
Open a command prompt and point to the folder for the Mobility server:
cd \Program Files\NetMotion Server
Enter the following case-senstitive command (the -T tells it to not wrap the dn line):
Nmwdump -T nmw-PrivObjectClass=4 dn nmwDeviceAlias > devices.ldif
This will create a file called devices.ldif that contains an entry for each device on your server.
Open devices.ldif with a text editor like Notepad.exe. The contents will look something like this (each dn is returned on one long line; an ellipsis (...) indicates where the line is wrapped):
version: 1
dn: cn=01C43D03CD7C65EA00B0D0490A6100D,ou=New,ou=NMWClientRoot, ...
... ou=NMWRoot,o=NetMotion,dc=nmwco,dc=com
nmwDeviceAlias: BRICKMAN
dn: cn=01C457D4E3964010000D56C2AE78002,ou=New,ou=NMWClientRoot, ...
... ou=NMWRoot,o=NetMotion,dc=nmwco,dc=com
nmwDeviceAlias: MC50161
dn: cn=01C3D9E5688DCFFC1C3D9E5688DC00C,ou=New,ou=NMWClientRoot, ...
... ou=NMWRoot,o=NetMotion,dc=nmwco,dc=com
nmwDeviceAlias: C05924
dn: cn=01C4847CD8B8FE3A00B0D0490A61052,ou=New,ou=NMWClientRoot, ...
... ou=NMWRoot,o=NetMotion,dc=nmwco,dc=com
nmwDeviceAlias: ERICM-LAPTOP
|
Look at the nmwDeviceAlias lines to identify the client(s) to which you want to assign static VIP addresses. Make the following edits (see below for an example):
Delete all of the devices that will not be assigned a static VIP address, but leave the first line (version: 1).
Place a comment character ('#') in front of the remaining nmwDeviceAlias lines (you can remove this line, but that makes it difficult to tell which client you are working with).
Add the following text after each device's nmwDeviceAlias line:
changetype: modify
replace: nmwAddressAllocationType
nmwAddressAllocationType: 2
-
replace: nmwStaticAddr
nmwStaticAddr: 10.1.1.104
-
replace: nmwDisplayForOverride
nmwDisplayForOverride: 1
|
where nmwStaticAddr (in bold) is set to the address you want. Note the dash ('-') between attributes—this is important. Be sure to leave a blank line between each entry (before each "dn: " line), as in the example below.
Save your changes to devices.ldif.
After making the above changes you should have something that looks like this:
version: 1
dn: cn=01C4847CD8B8FE3A00B0D0490A61052,ou=New,ou=NMWClientRoot, ...
... ou=NMWRoot,o=NetMotion,dc=nmwco,dc=com
#nmwDeviceAlias: ERICM-LAPTOP
changetype: modify
replace: nmwAddressAllocationType
nmwAddressAllocationType: 2
-
replace: nmwStaticAddr
nmwStaticAddr: 10.1.1.104
-
replace: nmwDisplayForOverride
nmwDisplayForOverride: 1
dn: cn=01C43D03CD7C65EA00B0D0490A6100D,ou=New,ou=NMWClientRoot, ...
... ou=NMWRoot,o=NetMotion,dc=nmwco,dc=com
#nmwDeviceAlias: BRICKMAN
changetype: modify
replace: nmwAddressAllocationType
nmwAddressAllocationType: 2
-
replace: nmwStaticAddr
nmwStaticAddr: 10.1.1.105
-
replace: nmwDisplayForOverride
nmwDisplayForOverride: 1
|
Import devices.ldif on the warehouse:
On your primary warehouse (if you have only one warehouse, it is the primary) open the Sun ONE Directory Server console—on the Start menu, click Programs, Sun ONE Server Products, Sun ONE Server Console 5.2—and log in using your Warehouse password.
On the Servers and Applications tab, expand the tree until you see your Directory Server listing. Select your server, and then click Open.
On the Tasks tab, click Import from LDIF.
In the Import LDIF dialog box, enter the path to your LDIF file, or click Browse to select it.
Do not select the Add only check box.
Click OK to import the file. A successful import will indicate something like "2 objects imported, 0 objects rejected." If it fails you probably have a typo in your Devices.ldif file.
Verify the VIP assignments
Open the Mobility console and verify that the devices are listed on the Client Settings page and that they have the correct static VIP addresses assigned to them. A client will be assigned its new static VIP address the next time it connects.
Related Information
2166
|
Setting up a Virtual IP Address Scheme
|
9979
|
NetMotion Mobility Technical Notes
|
Please comment on this technical note.
|

|
|
|