Starent 16000 PDSN MOP – Adding IP Pools

Purpose

The purpose of this Method Of Procedure (MOP) is to add ranges of IP Addresses, called “pools”, to the Starent 16000 PDSN. An IP address from an IP pool is assigned to a subscriber by the PDSN when a data session is initiated.

Procedure

Begin this procedure by creating a backup of the PDSN configuration file. Use the copy command to create a new configuration file.

[local]pdsn1# copy /flash/system.cfg /flash/system.backupfile.cfg <CR>

The file called system.backupfile.cfg is created as a contingency in the event a problem occurs during execution of this method.

Begin the actual procedure. Enter configuration mode.

[local]pdsn1# configure<CR>

Enter the context called dest.

[local]pdsn1 (config)# context dest<CR>

Enter the command to add the IP range.

[dest]pdsn1(config-ctx)# ip pool <pool> <start> <netmask> private 0

Where pool is the name you want to assign to this range of IP addresses, start is the first IP address in the range being added, and netmask is the netmask which describes the entire range being added.

For example, if 2 contiguous class C addresses are added, 10.252.254.0 and 10.252.255.0, use this command:

[dest]pdsn1(config-ctx)# ip pool <pool> 10.252.254.1 255.255.254.0 private 0<CR>

In this command private means the IP addresses will only be assigned from this pool to subscribers having an AAA profile which calls this pool.

This is the preferred form of this command because in addition to adding the pool correctly on the PDSN it also causes only a single entry to be created in the connecting router’s OSPF routes table.

There is another form of this command which uses the range option rather than a netmask. This other form is better avoided when possible because using it will cause the to create many entries in the connecting router’s OSPF routes table. Perhaps as many as 8 entries per class C address range. Use of this form cannot be avoided when the netmask cannot be created with contiguous set bit positions. Take this into consideration if discretion can be exercised when choosing specific IP address ranges to add. Careful choices can greatly reduce the length and complexity of the OSPF routes table.
Continue with the procedure by exiting the dest context.

[dest]pdsn1(config-ctx)# exit<CR>

This returns the configuration prompt.

[local]pdsn1(config)#

After data-fill changes save the configuration:

[local]pdsn1(config)# save configuration /flash/system.cfg <CR>

After saving the changes, sync the files between the active and inactive cards. Type the card spc synchronize command to synchronize the files to the standby SPC:

[local]pdsn1(config)# card spc synchronize filesystem all <CR>

Compares the files on the two SPCs and determine which files need to be synchronized between the active SPC in slot 8 and the standby SPC in slot 9.

Roll-Back Procedure

Commands:

Enter configuration mode

[local]pdsn1# config<CR>

Delete the previously added IP pool called pool

[local]pdsn1(config)# no ip pool <pool> <CR>

After data-fill changes: If the shelf configuration is acceptable type the save configuration command:

[local]pdsn1(config)# save configuration /flash/system.cfg<CR>

After saving the changes, sync the files between the active and inactive cards. Type the card spc synchronize command to synchronize the files to the standby SPC:

[local]pdsn1(config)# card spc synchronize filesystem all<CR>

Compare the files on the two SPCs and determine which files need to be synchronized between the active SPC in slot 8 and the standby SPC in slot 9.