For some of the 3G BBU no script is provided you need to modify the given IPs till everything works

fine.
The following is an illustration of the steps to be taken to modify IPs explaining the old existing
parameters and the new parameters to be modified.

I will take an example of site DXB6420 to illustrate how to do modifications.

IP Address for Traffic IP Address for OM

Technology Physical IP Physical IP
Gateway IP Address Vlan-1 Gateway IP Address Vlan-2
Address Address

3G 10.212.217.129/27 10.212.217.157 900 10.235.88.161/27 10.235.88.180 970

Before starting any modification make sure that for both links you can you can use ping tool to ping the
gateway using the IPs and VLANs given in the IP plan sheet.

The parameters to be modified are

1. DEV IP

2. OM Channel

3. SCTP LNK

4. VLAN map

5. IP Route (IPRT)

6. USER PLANEHOST

7. IP CLOCKLNK

From the given IP plan we see that we have one link for traffic and one link for O&M. For each link we
are required to add its DEVIP, add its VLANMAP, modify its IPRT and modify the OMCH for OM link and
SCTPLINK for traffic link. The user plane host IP should be changed so that it becomes the same as the
physical traffic IP. The IPCLCKLINK client IP needs to be modified as well the same as the physical traffic
IP.

For each parameter the screen shot of the parameter before modification will be shown and a screen
shot during modification will be shown as well.
Author: Balthazar Temu (Bata)
DEVIP

Before modification the screenshot of the DEVIP is shown below

Since the IP address 10.236.57.4 is different from our two physical IPs given in the sheet i.e
10.212.217.157 and 10.235.88.180 we have to add the two physical IPs.

For every channel we are supposed to define one DEV IP. The DEV IP is the physical IP given in the IP
sheet. Since we have two channels we are supposed to have two DEV IPs, one is the OM physical IP and
the other is traffic physical IP.

So we add DEVIP 10.212.217.157 for traffic and 10.235.88.180 for OM

See the screenshot below

Author: Balthazar Temu (Bata)

Adding 10.212.217.157 for traffic channel

Author: Balthazar Temu (Bata)

Adding 10.235.88.180 for OM channel

After DEVIP modification is done LST DEVIP will give the result below

Author: Balthazar Temu (Bata)

The DEVIP in the last row will be removed after modifications of all parameters are done as it will not be
easy to remove now since it is in use with other parameters. There are many pointers to this device IP
now. After all modifications are done there wont be anything pointing to this device, then we can easily
remove it.

OM Channel

The screenshot below is the OMCH before modification

Author: Balthazar Temu (Bata)

We can change the parameters of OMCH by simply MOD OMCH command as shown below

After OMCH modification is done LST OMCH will give the result below

Author: Balthazar Temu (Bata)

SCTPLINK
Before any modification is done LST SCTPLINK result will be as shown below

We only need to modify the first local IP Address 10.236.57.4 to 10.212.217.157 for link No 0, 1 &2
Author: Balthazar Temu (Bata)
See the screenshot below

We have to repeat the procedure for link number 1 and 2.

After modifying all of the three links the result of DSP SCTPLINK will be as shown below

Author: Balthazar Temu (Bata)

 VLANMAP
Before any modification is done the result of LST VLANMAP is shown below, no any VLANMAP
information is available.

VLANMAP is added by ADD VLANMAP command see below

Author: Balthazar Temu (Bata)

This step above will add the OM VLANMAP of 970 VLAN ID as given in the IP sheet.

This step shown on the screenshot above will add the traffic VLANMAP of 900 VLAN ID as given in the IP
sheet.

After both of the VLANs are added the command LST VLANMAP gives the result below

Author: Balthazar Temu (Bata)

IP Route (IPRT)

Before modification when we LST IPRT

First we have to identify which IPRT is for OM and which is for traffic. It is easy to do so, just look at the
destination IP, 10.238.145.0 is normally the destination IP for M2000 for Dubai region when used in
IPRT. Here we have to modify the mask and the next hope the mask should be 255.255.255.224 and the
next hop should be 10.235.88.161 which is the next hop given in the IP sheet.

Thus we have to remove route index number 10 as shown below

Author: Balthazar Temu (Bata)

Then we add the IPRT with the new mask and next hop IP as shown below

Then we identify the IPRT for traffic, the route index number 5 is the IPRT for traffic since the
destination is 10.238.11.25 which is the destination for traffic link as shown by DSP SCTPLINK result
shown previously.

Thus we have to remove route index number 5 just by using the command RMV IPRT with route index
filled as 5 then add the new route index number 5 as shown below

Author: Balthazar Temu (Bata)

After the IPRT for traffic and for OM are added we then change the next hop IPs of the remaining IPRTs
from 10.236.57.1 to the next hop for traffic given in the IP plan which is 10.212.217.129. This is done
because those remaining IPRT just like clock link for synchronization use the next hop of traffic in
defining their route since they use the same route as traffic the only difference being they have
different destinations.

After all modifications are done on IPRT when we run the command LST IPRT we should have the
following result

Author: Balthazar Temu (Bata)

 USER PLANEHOST
For this site there was no any result for user plane host see the screenshot below, so we dont
do anything on the USER PLANEHOST if we dont have any existing one.

If at all you have any details for the existing user plane host then you should modify them by MOD
USERPLANEHOST and then you should change only the local IP to be the physical IP for traffic given in
the sheet i.e 10.212.217.157. All the other fields will remain unchanged.

Author: Balthazar Temu (Bata)

IP CLOCKLNK
The result of LST IPCLKLINK before any modification is shown below

We are supposed to modify the Client IP for both links to be the physical IP for traffic given in the sheet
i.e we should change thr client IP from 10.236.57.4 to 10.212.217.157.

To do this we have to remove IPCLKLINK 0 first

Author: Balthazar Temu (Bata)

Then we add the new IPCLKLINK 0 with the client IP of 10.212.217.157

Then we remove IPCLKLINK 1

Author: Balthazar Temu (Bata)

Then we add the new IPCLKLINK 1 with the client IP of 10.212.217.157

Author: Balthazar Temu (Bata)

Some of the 3 G have IP PATH , this is an example of it,

We have to change the IP address from 10.236.57.4 to 10.212.217.15, we can easily do it by MOD
IPPATH command.

REMOVING THE DEVIP 10.236.57.4

After all this modification is done we can now remove the DEVIP 10.236.57.4 since nothing is pointing to
it currently, using the command RMV DEVIP we can easily remove this old traffic IP.

Author: Balthazar Temu (Bata)