20500-196 - (9353 WMS OAM Parameters Network Reconfiguration Procedure) - 01.05-Preliminary

NN-20500-196
Wireless Service Provider Solutions
W-CDMA
Alcatel-Lucent 9353 Management System
OAM Parameters Network Reconfiguration
Procedure
NN-20500-196 01.05 / EN Preliminary September 2008
W-CDMA
OAM Parameters Network Reconfiguration Procedure
Document number: NN-20500-196
Document issue: 01.05 / EN
Document status: Preliminary
Product release: UA06.0
Date: September 2008
Copyright © 2008 Alcatel-Lucent,

ALCATEL-LUCENT CONFIDENTIAL
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write
protected"; it may be altered only by authorized persons. While copies may be printed, it is not
recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies
taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of
Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all
information contained herein confidential, shall disclose the information only to its employees with a need
to know, and shall protect the information from disclosure and dissemination to third parties. Except as
expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information
contained herein. If you have received this document in error, please notify the sender and destroy it
immediately.
Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks
of Alcatel-Lucent, Alcatel and Lucent Technologies.
All other trademarks are the property of their owners.

Publication history i
PUBLICATION HISTORY
SYSTEM RELEASE: UA06.0
September 2008
Issue 01.05/EN Preliminary
Update after internal review.
August 2008
Issue 01.04/EN Draft
UA06.0 Update for DR4
The procedures Deactivate the OS Hardening Tool and Create a New ROC Configuration
File to Change the Network Parameters were updated.
June 20th 2008

UA06.0 Pre DR4
April 21st 2008

Update following internal review
March 17th 2008

Issue 01.01 / EN Draft
Update for UA06.0 / OAM06.0
Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

Table of contents ii
1 About this Publication................................................................................................................................................... 1

2 UMTS Access Network Collection Roadmap...............................................................................................................3
3 What is New.................................................................................................................................................................... 4
4 Requirements................................................................................................................................................................. 5
5 Network Parameters Reconfiguration.......................................................................................................................... 6
5.1 Prerequisites..............................................................................................................................................................7
5.2 System Impact........................................................................................................................................................... 8
5.3 Description.................................................................................................................................................................9
5.4 Troubleshooting....................................................................................................................................................... 11
6 Sheets............................................................................................................................................................................12
6.1 Check Hosts before the Network Reconfiguration...................................................................................................14
6.2 Deactivate the IP Filter............................................................................................................................................ 17
6.3 Deactivate the OS Hardening Tool.......................................................................................................................... 18
6.4 Create a New Default Router Configuration File to Change the Network Parameters............................................ 20
6.5 Create a New ROC Configuration File to Change the Network Parameters........................................................... 22
6.6 Reconfiguration of the Spare System Controller of the Sun Fire 4800/4900...........................................................26
6.7 Launch the Network Reconfiguration Process.........................................................................................................29
6.8 Reconfigure the Network Hardware.........................................................................................................................34
6.9 Special Operations for the Sun Fire 4800/4900.......................................................................................................42
6.10 Special Operations for the Netra 240.................................................................................................................... 48
6.11 Activate the IP Filter...............................................................................................................................................51
6.12 Activate the OS Hardening Tool............................................................................................................................ 52
6.13 Clients Reconfiguration Operations....................................................................................................................... 54
6.14 Backup/Restore Reconfiguration Operations........................................................................................................ 55
6.15 DHCP Reconfiguration.......................................................................................................................................... 56
7 Abbrevations and definitions......................................................................................................................................59
NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

List of figures iii
Figure 1 - Example of DHCP parameters........................................................................................................... ......... 57

1
1 About this Publication

The change of network parameters (hostname, but more importantly IP address) on one or several
OAM servers is not a common operation. Since changing these OAM parameters is very time
consuming, customers should use an adequate tool. This document describes such a tool.
Scope of this Document

This document deals with modification of the OAM network parameters. Allowed modifications are
hostnames, IP address or netmask changes of any OAM server.
This document covers all 9353 WMS supported.
Specifically, the scope of this feature doesn't cover:
• All the OAM clients
• All networking equipments like firewalls or routers. so additional modification must be done in
order to have back an operational network after modification.
The operator must ensure that the forecasted network modification still complies with Alcatel-Lucent
OAM guidelines and rules.
Audience
This document is for all persons involved in the modification of the network parameters of the OAM
servers. This person must have knowledge of the system administration and the OAM administration
and configuration.
Please Read Carefully

The utmost care was taken to prevent any unexpected event to occur during this procedure. Thus, if
you feel you have to cope with a problem or a situation the procedure does not explicitly or
accurately deal with, call your Alcatel-Lucent Regional Support Center for help.
CAUTION
In order to plan the network reconfiguration, the operator must
entirely read this document and asks the local support for all the
information needed before executing this procedure.
CAUTION
It is mandatory that, prior to start the network reconfiguration, a
backup of the server is available.

2
CAUTION
It is STRONGLY RECOMMENDED that, at the end of the network
reconfiguration, a full system and data backup of the servers is
performed.
Related Documents
• [R1] IM 30-0234 UMTS UA06.0 DHCP Activation in a service UTRAN
• [R2] NN-10300-036 Alcatel-Lucent 9353 Management System - Workstation Client / Application
Installation
• [R3] NN-20500-073 Alcatel-Lucent 9353 Management System - OAM Upgrade Procedure
• [R4] NN-10300-035 Alcatel-Lucent 9353 Management System - Backup and Restore
• [R5] Sun StorEdge™ Disk Array Installation, Operation and Service Manual

3
2 UMTS Access Network Collection Roadmap
For a collection roadmap, see UMTS Access Document Collection - Overview and update summary
(NN-20500-050).

4
3 What is New
•
Update after internal review.
•
UA06.0 Update for DR4
The procedures Deactivate the OS Hardening Tool and Create a New ROC Configuration File to
Change the Network Parameters were updated.
•
UA06.0 Pre DR4
•
Update following internal review
•
Issue 01.01 / EN Draft
Update for UA06.0 / OAM06.0

5
4 Requirements
Resources
• A UNIX Systems and Network engineer.
• A system console on each OAM Server must be available (system console can be a station
connected to a Xyplex/Annex).

6
5 Network Parameters Reconfiguration

7
5.1 Prerequisites
• Operator performing this procedure must have root access on all OAM servers.
• Detailed description of Old and New ROC topologies must be available.
• The OAM server must be installed with standard procedures.
• Packages NNWINSC, NNWINST, NNWCOMC, NNWCOMT and NNNETUPD must be installed
on all OAM servers.
CAUTION
Before proceeding the network change, the operator MUST Backup
all the OAM servers of the ROC (See the [R4] document).
If the network reconfiguration includes the disks arrays (on SF4800/4900), the operator must ensure
that the state of disks arrays are correct.
Note: Disks arrays must be on the same sub-networks (OAM_OAM group) as the host.
If the network reconfiguration includes one or more Uninterruptible Power Supply (UPS), the operator
must ensure that the states of UPS are correct.
If the network reconfiguration includes the System Controller of a Sun Fire 4800/4900 or a Netra 240,
the operator must be prepared to change manually the network parameters of this System Controller.

8
5.2 System Impact
Applications
All OAM applications are stopped on all OAM servers of the ROC during the network reconfiguration.
Allow Remote Root Access

Prior to start network reconfiguration, all the hosts of the ROC are unhardened for the root user i.e.
remote accesses for the user root are enabled. Once reconfiguration is performed, authentication
credentials for root user are restored to their original value to disable remote access for the root user.
Routing
The IP address of the router(s) of the local network is not stored in the ROC configuration file. So
before launching the network reconfiguration and according the network reconfiguration, the operator
has to:
• Define the IP address(es) of the new router(s).
These IP addresses are stored in a file ("/etc/defaultrouter-new") on each OAM server of the ROC.
This file has the same format as the "/etc/defaultrouter" file.
During the network reconfiguration, a message is displayed on the console to inform the operator to
change the network hardware. At this time, the operator has to unplug all the Ethernet wires and
perform the hardware changes. The network reconfiguration resumes when at least one network
interface is up again (i.e. one Ethernet cable is connected to the network).

9
5.3 Description
The chosen solution is based on a manager/agent pattern. The operator has to launch the ROC
network update on the system console of the PMS, which activates network update managers on
each OAM servers.
Then the managers calls some network updater agents depending on the OAM products installed on
the machines.
Information Required
The network information of the ROC is stored in the ROC configuration file.
To apply the change, the process uses these files on each server of the ROC:
• The original ROC configuration file:
"/opt/nortel/config/iut_tools/roc/iut_rocconfig.cfg"
• The new ROC configuration file:
"/opt/nortel/config/iut_tools/roc/new_rocconfig.cfg"
• The new router information file (optional):
"/etc/defaultrouter-new"
Scheduling
The following table gives the sequence
Checks
OS phase before Wiring
"Wiring"
PRODUCT reconfiguration
Finalize reconfiguration
Clients reconfiguration operations
Backup/Restore reconfiguration operations (if applicable)
DHCP reconfiguration (if applicable)
Note: Time required by 'Wiring' phase depends on ROC size and amount of changes that must
be done.

10
Result
After the whole process,
• The original ROC configuration file is now:
"/opt/nortel/config/iut_tools/roc/old_rocconfig.xml"
• The new ROC configuration file is now the current ROC configuration file:
"/opt/nortel/config/iut_tools/roc/iut_rocconfig.xml"
If a new router configuration file exists:
• The original router configuration file is now:
"/etc/defaultrouter-old"
• The new router configuration file is now the current configuration file:
"/etc/defaultrouter"

11
5.4 Troubleshooting
User Configuration
The process does not change the user configuration automatically, so each user must correct his
personal configuration to take account of the network changes. In particular, the SSH configuration
file of each user depends of the hostname and the IP addresses and has to be changed manually.
9353 WMS Layout Background Image

In case of OAM Primary Main Server hostname change, the 9353 WMS layout background image
will be lost after the OAM Parameters Network reconfiguration Procedure. So if you do change the
hostname of OAM Primary Main Server, you will need to set again the background image for all
layouts, following the On Line help on "Framework Overview and Procedures" - chapter "Layout
Editor" Procedure "Setting the background image".
Fallback
No fallbacks are available. If the network update was not performed successfully, the server can be
put back to the original network configuration.
To recover the original ROC configuration, the operator has to:
• Move faulty ROC server back in the old network.
• If applicable to this server, restore the network parameters of disks arrays (refer to documents
[R5]).
• Perform a full system restore, and data restore if necessary, on the server (refer to the document
[R4].

12
6 Sheets
The following provides the high level overview of steps necessary to successfully complete the
network reconfiguration:
• 1 Check Hosts before the Network Reconfiguration
Target host: PMS
• 2 Deactivate the IP Filter
Target host: All OAM servers
• 3 Deactivate the OS Hardening Tool
• 4 Create a New Default Router Configuration File to Change the Network Parameters
• 5 Create a New ROC Configuration File to Change the Network Parameters
Target host: PMS and SMS
• 6 Reconfiguration of the Spare System Controller of the Sun Fire 4800/4900
Target host: All SF4800/4900 servers
• 7 Launch the Network Reconfiguration Process
• 8 Reconfigure the Network Hardware
• 9 Special Operations for the Sun Fire 4800/4900
• 10 Special Operations for the Netra 240
Target host: All Netra 240 servers
• 11 Activate the IP Filter
• 12 Activate the OS Hardening Tool
• 13 Clients Reconfiguration Operations
Target host: PC/UNIX Clients
• 14 Backup/Restore Reconfiguration Operations
Target host:

13
— All OAM servers

— Backup/Restore Server
• 15 DHCP Reconfiguration

14
6.1 Check Hosts before the Network Reconfiguration

The purpose of this sheet is to perform some checks before launching a network update.
Target host: all OAM servers
Initial Status
For each host of the ROC, the machine is running and a root session is available.
Execution Time
It takes about 10 minutes to perform these steps on each host of the ROC.
Procedure
Step Action
1. From the Primary Main Server, launch the update network pre-checks.
Under a root session, enter the next command:
(root) # /opt/nortel/shell/iut_tools/network_updater/iut_launchrocchecknetworkupdate.sh
-Y
For example:
2. Wait for the following log to be displayed

15
Note: To perform the update, the result of the previous command must be OK!
--End--
Troubleshooting
If these checks failed because a machine that is not belonging to the ROC is unreachable:
• Remove this machine from file /etc/hosts
• Perform the following command:
(root) # /opt/nortel/shell/iut_tools/network_updater/iut_launchrocchecknetworkupdate.sh –Y
–restart
For example:
Each error that appears during these checks has to be corrected one by one before the update.
These checks MUST be performed again after correction and procedure cannot be resumed unless
checks are passed without any errors.
Final Status
The network update can be launched.

16

17
6.2 Deactivate the IP Filter

The purpose of this sheet is to deactivate the IP Filter.
Initial Status
The OAM server is running and a root session is available.
Execution Time
It takes about 1 minute to perform this step.
Procedure
Step Action
1. Use the following command under a root session:

(root) # /opt/nortel/shell/ipf/ipf_act.sh -d
For example:
--End--
Final Status
The IP Filter is deactivated.

18
6.3 Deactivate the OS Hardening Tool

The purpose of this sheet is to deactivate the OS-Hardening feature (if applicable).
Initial Status
The machine is running and a root session is available.
The OS-Hardening feature must be activated.
Execution Time
It takes about 30 minutes to perform these steps.
Procedure
Step Action
1. On each server of the ROC, log on as root.
2. Check if the machine is hardened. Under a root login:

(root) # /SECURITY/<Package Name>/bin/showstatus
where
• <Package Name> can be:
— NNoshmai if server (Primary or secondary)
— NNoshcli if client
• <Version> is the UMTS version
• <Server Type> can be: 'Main' on a Primary or Secondary Main Server
Following steps must be executed only if your system is HARDENED (i.e. the previous
command result is equal to "The system is hardened with configuration …")
3. Deactivate the OS-Harden module. Under a root session:

(root)#init 0

19
{0} ok boot -s
When the server reboots in single user mode, under a root login, launch the following commands:
(root)#montall
(root)# /SECURITY/<Package Name>/bin/Solaris OsUnHarden -p <Package Name>
where
• <Package Name> can be:
— NNoshmai if server (Primary or secondary)
— NNoshcli if client
(root)#init 6
--End--
Final Status
The OS-Hardening feature is deactivated on each server of the ROC.

20
6.4 Create a New Default Router Configuration File to Change the

Network Parameters
The purpose of this sheet is to create a new default router configuration file in order to update the
network parameters configuration. This file is needed only if the OAM server will be on another
sub-network after the network reconfiguration. This file is created on each OAM server.
Initial Status
Execution Time
Procedure
Step Action
1. On each OAM server :

Copy the original default router configuration file to the new default router configuration file.
Under a root session:
(root) # cd /etc
(root) # cp –p defaultrouter defaultrouter-new
For example:
2. Modify the new default router configuration file, under a root session:
(root) # vi defaultrouter-new
For example:
Note: Be Careful: Do not edit the current default router configuration file.
Tips: As this file can contain several IP addresses, the operator can keep the old gateway entries

21
to ease the network reconfiguration.

Note about routing tables: As the OAM servers can be in a network with several subnets, the
operator can use some routing tables configured automatically during the boot on the different
OAM servers.
The server will use this defaultrouter file, when it doesn#t find any network or sub network where
to send the data.
The routes associated to the routers can be statically declared for each subnet as follows.
For example for subnet2:
• route add -net IP_address_OfaSubnet IP_address_routerA_OnSubnet2
• route add -net IP_address_OfaSubnet IP_address_routerB_OnSubnet2
If some routing tables are automatically declared during the boot of this server, please contact
your local administrator and check if some modifications are mandatory after network
reconfiguration. Then modify those routing tables that will be taken into account at the next
reboot of the server.
--End--
Final Status
The new default router configuration file is created.

22
6.5 Create a New ROC Configuration File to Change the Network

Parameters
The purpose of this sheet is to create a new ROC configuration file in order to update the network
parameters configuration.
Target host: Primary Main Server and Secondary Main Server
Initial Status
The OAM servers are running and a root session is available.
Execution Time
Requirements
IPMP groups (OAM_OAM, OAM_BKP and OAM_NE) require 3 IP addresses (2 IP test addresses +
1 IP data address) for each of them.
All IP addresses, which are part of a same group, must belong to the same subnet, so in case of a
subnet change on one IPMP group, ask 3 IP addresses for the IPMP group on the new subnet.
In case of subnet change on OAM_OAM group with a SF4800, ask 1 IP address for each T3 on the
new OAM_OAM group subnet. (T3 must be in the OAM_OAM group subnet).
In case of subnet change on OAM_OAM group with a SF4900-SE6120, ask 1 IP address for SE6120
disks arrays on the new OAM_OAM group subnet. (The SE6120 must be in the OAM_OAM group
subnet).
In case of subnet change on OAM_OAM group with a SF4900-ST6140, ask 2 IP address for ST6140
disks arrays on the new OAM_OAM group subnet. (The ST6140 must be in the OAM_OAM group
subnet).
Procedure
Step Action
1. Copy the original ROC configuration to the new ROC configuration file.
(root) # cd /opt/nortel/config/iut_tools/roc
(root) # cp iut_rocconfig.cfg new_rocconfig.cfg

23
For example
2. Modify the new ROC configuration file

Under a root session edit the file
Note: Be Careful: Do not edit the current ROC configuration file.

To change the network parameters, update the following fields in the new ROC configuration file:
You cannot modify another kind of fields (Machine.Hostname, DNS_DOMAIN, ROCNAME,

Platform, Role, Function, Option, Passwd, Osi) and you must preserve the number of the existing
network fields. For example, if the Server '1' has three hostnames, you cannot remove a host
name or add another host name. The same restriction is applied to the IP addresses and the
netmasks.
3. Save the current ROC configuration files

(root) # cp -p iut_rocconfig.cfg iut_rocconfig.cfg.backup
(root) # cp -p iut_rocconfig.xml iut_rocconfig.xml.backup
For example:
4. Generate the new ROC configuration XML file

(root) # /opt/nortel/shell/iut_tools/common/iut_addmachineinroc.sh -xml
-filenew_rocconfig.cfg -L /opt/nortel/logs/iut_tools/iut_networkupdate.log
(root) # cp -p iut_rocconfig.cfg.backup iut_rocconfig.cfg
(root) # cp -p iut_rocconfig.xml.backup iut_rocconfig.xml
For example:

24
5. Check the network parameters change between the new and the old ROC configuration files.
(root) # /opt/nortel/shell/iut_tools/network_updater/iut_checknetworkupdate.sh -roc -L
/opt/nortel/logs/iut_tools/iut_networkupdate.log
For example:
Note: Be Careful: To perform the update, the result of the previous command must be OK. In
case of error, check the new_rocconfig.cfg file content and perform again the step 4.
6. Copy the file new_rocconfig.cfg to the other servers of the ROC

On the PMS, and for every server except the PMS, as root, run the following commands:
(root) # scp -p /opt/nortel/config/iut_tools/roc/new_rocconfig.* <Remote Server
Name>:/opt/nortel/config/iut_tools/roc
#ssh <Remote Server Name> "chown oamops:oamgroup
/opt/nortel/config/iut_tools/roc/new_rocconfig.*"
For example:
Note: Where Remote Server Name = name of the server where the file must be copied to.
7. Goes to the Secondary Main Server
8. Edit the file new_rocconfig.cfg in order to modify both lines:

Machine.Hostname = <The content of Server.2.Ethernet_Port.Hostname.0>
Machine.Role = SecondaryMainServer
9. ON the SMS execute the steps 3, 4, 5

25
--End--
Final Status
The new ROC configuration file is created.

26
6.6 Reconfiguration of the Spare System Controller of the Sun Fire

4800/4900
This sheet is about the reconfiguration of the Spare System Controller of the Sun Fire 4800/4900.
If the network reconfiguration doesn#t include the System Controller, the operator can skip this sheet.
Initial Status
A terminal session is available. All operations are managed from this terminal session.
Execution Time
Requirements
In the next sections, 'SSC_Hostname' (respectively 'SSC_IPAddress') stands for the current name
(respectively IP Address) of the Spare System Controller (SSC).
Procedure
Step Action
1. On a session, enter:
Note: Check for the message "Spare System Controller".
2. Change the network parameters of the Spare System Controller.

Under the monitor prompt, enter:
SSC_Hostname:sc> setupplatform -p network
For example:

27
Note: Note: following entries are optional :

• <new_DNSdomain>,
• <new_Primary_DNS_Server>,
• <new_Secondary_DNS_Server>.
3. Enable the failover configuration.

SSC_Hostname:sc> setfailover on
For example:
Note: Wait 20 seconds before applying next step.

SSC_Hostname:sc> showfailover
For example:
4. If the previous command does not display the 'SC Failover: enabled and active' message, you
can skip this step.
• Connect on the master System Controller: Under the monitor prompt, enter:

28
Note: <SC_IPAddress> is the address of the Main System Controller.

• Enable the failover configuration on the master System Controller. Under the monitor prompt,
enter:
SC_Hostname:sc> setfailover on
For example:
Note: Wait 20 seconds before applying next step

• Check the failover configuration on the Spare System Controller. Under the monitor prompt,
enter:
SSC_Hostname:sc> showfailover
For example:
Note: If the previous command does not display the 'SC Failover: enabled and active'
message, please call your Alcatel-Lucent Regional Support Center.
5. Reboot the Spare System Controller.

SSC_Hostname:sc> reboot -y
For example:
--End--
Final Status
The network reconfiguration of the Spare System Controller is done.

29
6.7 Launch the Network Reconfiguration Process

The purpose of this sheet is to launch the network reconfiguration process.
Target host: all OAM servers.
Initial Status
The machine is running and a root session is available on the system console
Execution Time
Procedure
Step Action
1. Connect on the system console.
• If a graphical environment is used (CDE for instance), you must skip it and switch to the
console mode. Under a terminal session, enter
# svcadm disable –t gdm2-login
For example:
Then login as root on the system console.

Note: This is needed because the X environment uses the IP addresses and is stopped
during the network reconfiguration.
• If the OAM server is a SF4800/4900, the operator must be connected on the Master System
Controller:
<SC_IPAddress> is the address of the Main System Controller

Note: Do not use the logical IP Address of the System Controller cards.
• If the OAM server is connected to a terminal server (Xyplex, Annex), you must be connected
on the terminal server:

30
<TS_IPAddress> is the address of the terminal server.
2. On the system console of the OAM Server, check that this is really a system console:
3. If the IP address is changed but the hostname is unchanged:

• Use SMC console to clear theirs associated alarms
Note: Otherwise these alarms will remain "active" after the IP change process.
• Stop the SMC service, under a root session.
For a Primary Main Server, launch the command:
# /opt/SUNWsymon/sbin/es-stop -A
For example:
• For the other type of server, launch the command:

# /opt/SUNWsymon/sbin/es-stop -a
For example:
4. Start the network reconfiguration process.

Enter the following command under a root session:
(root) # /opt/nortel/shell/iut_tools/common/iut_engine.sh -v -f
/opt/nortel/config/iut_tools/module/iut_networkupdatemanager.xml -L
For example:
The network reconfiguration process is finished when the following message is displayed:

31
Note: On the SF4800/4900 servers, the following error messages might appear on the
console if the network parameters are modified on the disk arrays. Those messages can safely
be ignored as there is no operational impact on the procedure.

32
5. Depending on the server configuration, execute the following operation

• If hardware changes must be done on the server or if the IP addresses of the T3/SE6120
disks arrays are changed , then power off the system:
• Else, reboot it:
Note: The operator must be connected on the system console. Otherwise the current terminal
is disconnected during the process and the user has to log on the system console to look at
the final result. The operator cannot use the graphic environment.
Note: The "init 5" command leads to an electric shutdown on the server machine, except on
SF4800/4900 platforms.
--End--

33
Troubleshooting
• If the reconfiguration process exits with the NOK status
To resume the reconfiguration process, perform the following steps on each failed server:
— Look for error message(s) in the log file to find the problem(s).
— Fix the problem (call your Alcatel-Lucent Regional Support Center if you cannot fix the
problem by yourself).
— Resume the reconfiguration process with the following command:
For example:
• If you meet problems that you cannot resolve by yourself, call your Alcatel-Lucent Regional
Support Center.
Final Status
The network reconfiguration process is done.
The user can change the hardware with the next sheet.

34
6.8 Reconfigure the Network Hardware

The purpose of this sheet is to reconfigure or change the network hardware.
Target host: all OAM servers.
Initial Status
The network reconfiguration process is done and a system console is available on every OAM
servers.
Execution Time
The duration of the hardware reconfiguration (for example 'Wiring') depends on the hardware.
The OAM applications reconfiguration takes about 120 minutes.
Procedure
Step Action
1. You must now proceed with the hardware reconfiguration:
• If the IP addresses of the T3/SE6120 disks arrays are changed or if the disks arrays must be
moved, power them off.
• If the server is not a SF4800/4900, power it off and start wiring phase, for example:
— Unplug servers.
— Move machines (including UPS and T3/SE6120/ST6140).
— Change network hardware.
— Configure network hardware.
— Plug back servers.
• If the server is a SF4800/4900, you must apply the actions described in the sheet Special
Operations for the Sun Fire 4800/4900 before going to the next action.
• If the server is a Netra 240, you must apply the actions described in the sheet Special
Operations for the Netra 240 before going to the next action.
2. When the hardware reconfiguration is done, you must power on all OAM servers.
• Power on the disk arrays if they were previously powered off.

• If the host is not a SF4800/4900: power on the server and reconnect on the system console.
• If the host is a SF4800/4900: you must be connected on the Master System Controller. Under

35
the monitor prompt, enter:
3. Log on each server, as soon as it is booted.

(root) # /opt/nortel/shell/iut_tools/network_updater/iut_checknetworkupdate.sh -
post -L /opt/nortel/logs/iut_tools/iut_networkupdate.
For example:
Note: This command may take several minutes (especially when there are some network
problems), do not proceed with the next steps if the previous command is not successful on all
the servers
4. On the Primary Main Server, under a root session, run the following command to synchronize the
ROC configuration across all the servers:
(root) # /opt/nortel/shell/iut_tools/common/iut_addmachineinroc.sh -export
-L /opt/nortel/logs/iut_tools/iut_networkupdate.log
For example:
5. On each server, under a root session, enter the next command:

/opt/nortel/logs/iut_tools/iut_networkupdate.log -continue
For example:

36
• On the PMS, this command will lead to server reboot.

• On other servers, wait for the following message to be displayed:
Note: During the Network reconfiguration, several SAML and SMC error messages are
displayed on the console. Do not pay attention to those exception messages until the Network
reconfiguration is finished.
6. After PMS reboot, wait for the reconfiguration process completion before doing anything else on
other servers.
The following message can be found in the logs file on the PMS at the end of the configuration
process:

37
Then, on each other ROC server, under a root session, type the following command:
root) # /opt/nortel/shell/iut_tools/common/iut_engine.sh –v –f
/opt/nortel/config/iut_tools/module/iut_networkupdatemanager.xml –continue
For example:

38
This command will lead the server to reboot. At the end of the reconfiguration process, the same
messages as above can be found in the logs file on each server.
7. After the end of reconfiguration process, login on the Primary Main Server and launch the SMC
console.
Check the OAM platform hardware and software components.
(root) # /opt/SUNWsymon/sbin/es-start –c
For example
--End--
Troubleshooting
• Troubleshooting for action 2:
If the IP address of the T3/SE6120/ST6140 disks arrays is being changed, the following error
message may appear on the server's console when rebooting:

39
To resume normally the boot process, log on the server's console and type the following command:
The servers then reboots smoothly.

• If the reconfiguration process exits with the NOK status.
To resume the reconfiguration process, perform the following steps on each failed server:
• Look for error message(s) in the log file to find the problem.
• Fix the problem (call your Alcatel-Lucent Regional support Center if you cannot fix the problem by
yourself).
• Resume the reconfiguration process with the following command:

40
/opt/nortel/logs/iut_tools/iut_networkupdate.log -continue
For example:

Note: The script iut_serverregistration.sh can fail on the primary and the secondary main servers
due to a file format exception introduced on the tumsbb configuration. Then apply this work
around:
• On the primary main server,
start and stop tumsbb to re-create the correct configuration file:
(root) # /opt/nortel/PresideNSP/current_NSPcore/bin/tumsbb.sh 10207
For example:
• On the secondary main server,

start and stop tumsbb to re-create the correct configuration file:
(root) # /opt/nortel/PresideNSP/current_NSPcore/bin/tumsbb.sh 10303
For example:
Then hit "Ctrl C' in order to return to (root) #

Resume the reconfiguration process at the step 5
If the SMC console launch fails with the following error message: "A remote exception occurred
during initialization, possibly due to a server or network failure. Please verify the accessibility of the
server host and application", launch the following command as root user on the Primary Main Server:
(root) # /opt/SUNWsymon/sbin/es-start –s&
For example:
If some processes on the secondary main server are not started (for example: fmbb, tumsbb, or hfb),
then connect to the Secondary Main Server.

41
Edit the following file and update the hostname of the SMS:
(root) # vi /opt/nortel/config/applications/security/isclient/is_auth.conf
For example:
Edit the following file and update the hostname of the SMS:
(root) # vi /opt/nortel/config/applications/security/isclient/is_client.env
For example:
Restart the processes which were not started.

If you meet problems that you cannot resolve by yourself, please call your Alcatel-Lucent Regional
Support Center.
Final Status
The network reconfiguration is done.

42
6.9 Special Operations for the Sun Fire 4800/4900

This sheet is about some special operations need for the Sun Fire 4800/4900 like:
• Reconfiguration of the System Controller
• Power off/on
Initial Status
The system console displays now the Open Boot Prom (OBP) prompt.
Execution Time
Prerequisites
In the next sections, for the parameters of the Main System Controller (SC):
• 'SC_Hostname' stands for the current name
• 'SC_IPAddress' stands for the IP Address.
Procedure
Step Action
1. The operator must be connected on the System Controller:
If the network reconfiguration does not include the System Controller, you can skip the next three
steps.
2. Change the network parameters of the System Controller.

SC_Hostname:SC> setupplatform -p network -p loghost -p sc -p snmp \ –p sntp
For example:

43
Note: Following entries are optional:

• <new_DNSdomain>
• <new_Primary_DNS_Server>

44
• <new_Secondary_DNS_Server>
• <new_SNTP_Server>
3. Display the available domains:

SC_Hostname:SC> showkeyswitch
For example
Note: In the example above, only the domain A is available.
4. Under the monitor prompt, enter:
5. If the SF4800/4900 will not be moved , reboot the System Controller.

45
Now, go back to the sheet Reconfigure the Network Hardware.
6. If the SF4800/4900 needs to be moved, apply the procedure for stopping the machine.
Here is a summary of the procedure:
Then enter the following commands on the SC prompt :

SC_Hostname:SC> poweroff grid0
SC_Hostname:SC> disconnect
For example:
Now you must electrically power off your SF4800/4900.

Here is a summary of the procedure
• Turn the key switch on the FrameManager to the OFF position,
• Turn OFF the AC input boxes,
• Turn OFF the RTS modules in the SF4800/4900 rear,
• Turn OFF the RTS modules in the SF4800/4900 front.
7. Now you can perform the hardware reconfiguration:

• Unplug the wires,
• Move the server,
• Plug the wires.
8. Now you must electrically power on your SF4800/4900

46
Here is a summary of the procedure:

• Turn ON the RTS modules in the SF4800/4900 front
• Turn ON the RTS modules in the SF4800/4900 rear,
• Turn ON the AC input boxes,
• Turn the key switch on the FrameManager to the ON position.
9. Connect on the System Controller:
Note: Do not use the logical IP Address of the System Controller cards
10. Then enter the following commands on the SC prompt:

SC_Hostname:SC> poweron grid0
For example:
11. Enter the following commands:

SC_Hostname:SC> console a
For example:
12. Enable the auto-boot PROM variable. On the system console with the OBP prompt, enter:
{ok} setenv auto-boot? true
For example:

47
--End--
Final Status
The network reconfiguration of the System Controller is done

48
6.10 Special Operations for the Netra 240

This sheet is about some special operations need for the Netra 240 like:
• Reconfiguration of the System Controller,
• Power off/on.
Target host: All Netra 240 servers
Initial Status
The system console displays now the OBP prompt.
Execution Time
Prerequisites
In the next sections, for the parameters of the System Controller (SC):
• 'SC_Hostname' stands for the current name,
• 'SC_IPAddress' stands for the IP Address,
• 'SC_Netmask' stands for the Netmask,
• 'SC_Router' stands for Router IP Address.
If the network reconfiguration does not include the System Controller, you can go back to the sheet
Reconfigure the Network Hardware.
Procedure
Step Action
1. You must be connected on the System Controller:
Note: Do not use logical IP Address of the System Controller cards.
2. Change the network parameters of the System Controller.


49
3. If the Netra 240 will not be moved:

50
Reboot the System Controller.
4. If the Netra 240 needs to be moved, you have to apply the procedure for stopping the machine.
--End--
Final Status
The network reconfiguration of the System Controller is done.

51
6.11 Activate the IP Filter

The purpose of this sheet is to activate the IP Filter.
Initial Status
Execution Time
It takes about 1 minute to perform this step.
Procedure
Step Action
1. Run the following command under a root session:

(root) # /opt/nortel/shell/ipf/ipf_act.sh -a
For example:
--End--
Final Status
The IP Filter is activated.

52
6.12 Activate the OS Hardening Tool

The purpose of this sheet is to re-activate the OS-Hardening feature (if applicable).
Initial Status
The machine is running and a root session is available.
The OS-Hardening feature needs to be re-activated.
Execution Time
Procedure
Step Action
1. For each server of the ROC:

Log on as root.
2. Check if the machine is hardened.

Under a root login:
# /SECURITY/*osh*/bin/showstatus
For example:
where:
• <Version> is the UMTS version,
• <Level> is the installed patch level.
Following steps must be executed only if your system is not HARDENED (i.e. the previous
command result is equal to "The system is not hardened") and if this feature was
deactivated in a previous step.
3. Activate the OS-Harden module.

53
When the server reboots in single user mode, under a root session, launch the following
command:
(root) # /SECURITY/*osh*/bin/Solaris_OsHarden –p NNosh<tag>
where:
• <tag> = mai if on PrimaryMainServer or SecondaryMainServer
• <tag> = srs if on SRSServer
• <tag> = cli if on Client
For example:
• <Server Type> = Main on a Primary or Secondary Main Server

The machine reboots
--End--
Final Status
The system is hardened.

54
6.13 Clients Reconfiguration Operations

The purpose of this sheet is to reconfigure PC or UNIX clients after the network reconfiguration
process.
Target host: PC/UNIX clients.
Initial Status
The machine is running and, for UNIX clients a root session is available.
Execution Time
It takes about 10 minutes per client to perform these steps.
Procedure
Step Action
1. Reconfigure UNIX clients.

Refer to the document [R2] section UNIX workstation installation.
• Installing the the JRE
• Configuring SRI
2. Reconfigure PC clients.
Refer to the document [R2] section PC installation
• Installing JRE and JNLP for NSP
• Configuring the SRI
--End--
Final Status
The PC/UNIX clients can connect to the OAM servers.

55
6.14 Backup/Restore Reconfiguration Operations

This sheet is only applied to customers who use Veritas NetBackup as their centralized B&R
solution.
Target host: B&R server and all OAM servers
Initial Status
The machines are running and a root session is available.
The document [R4] is available.
Execution Time
Procedure
Step Action
1. Log on each OAM server of the ROC.
2. On each server, create new backup class information.

Refer to the document [R4].
3. Log on B&R server.

(i.e. Veritas NetBackup master server)
4. Reconfigure the backup class for each OAM server on the B&R server.
Refer to the document [R4].
--End--
Final Status
The B&R server and clients reconfiguration is done.

56
6.15 DHCP Reconfiguration

This sheet is about reconfiguration of DHCP server (if applicable).
Target host: DHCP server
Initial Status
The machines are running and a root session is available.
Document [R1] UMTS UA06.0 DHCP Activation in a service UTRAN Installation Method 30-0234 is
available.
Execution Time
Note: This procedure applies for each subnet address (from the list of subnet addresses of the
DHCP client).
Procedure
Step Action
1. Check your DHCP server configuration:

• The DHCP server is not an OAM server: The operator should contact his local administrator
to check if a new configuration is mandatory.
• The DHCP server is collocated to an OAM and the DHCP configuration was not performed by
OAM installation tool: The operator should contact his local administrator to check if a new
configuration is mandatory.
• The DHCP server is collocated to an OAM and the DHCP configuration was performed by
OAM installation tool: To reconfigure DHCP server, refer to the document [R1] UMTS UA06.0
DHCP Activation in a service UTRAN Installation Method 30-0234
2. DHCP Commissioning
1. On the Main Server, configure the DHCP tabs.
Type the following command, under a root login:
Example:
# /opt/nortel/shell/iut_tools/common/iut_dhcpconfiguration.sh –add –S<Subnet
DHCP Client> -N<Netmask DHCP Client> -R<IP@aggragation point > -I<Start
DHCPIP> -n<IP Address Number> -i<InterfaceNumberList>

57
2. Make sure that your DHCP Client machines are reachable by editing the /etc/defaultrouter file
and/or the S97 router one.
Type the following commands:
Example:
# route add net <Subnet DHCP Client> <Gateway Ip Address>
# echo "route add net <Subnet DHCP Client>< Gateway IpAddress>"
>>/etc/rc2.d/S97qferouter
There are two cases:
— Or there is a direct connection (HUB, switchether), then <Gateway IP@> is equal to
RNC-IN IP@>.
— Or there is no direct connection, then <GatewayIPAddress> is equal to the first router in
the path.
3. Check the DHCP parameters, type the following command:
Example:
# /usr/sbin/dhtadm –P
See Example of DHCP parameters below for more details.
4. Restart the DHCP, type the following commands:
Example:
# /etc/init.d/dhcp stop
# /etc/init.d/dhcp start
Figure 1 Example of DHCP parameters
Note: 1-NodeB Port = 18 157 means: nodeb port = 6301 (6301 converted to hexadecimal
=189D, 18 stay 18 and 9D is converted to decimal 9D = 157)
Note: 2-OAM Number = 01 means: 1 oam number (01)
Note: 3-OAM IP Address= 47.164.97.104 means oam IP address, it corresponds to the qfe2
or ce1 (depending the hardware configuration of the MAIN server)
Note: 4-OAM Port = 18 157 means: oam port = 6301 (6301 converted to hexadecimal =189D,

58
18 stay 18 and 9D is converted to decimal 9D = 157)

IMPORTANT: The 2 port number (nodeb port and oam port) should be the same.
--End--
Final Status
The DHCP server reconfiguration is done.

59
7 Abbrevations and definitions
Abbrevations
• 9353 WMS Alcatel-Lucent 9353 Management System
• OAM Operation, Administration and Maintenance
• ROC Regional Operational Center
• PMS Primary Main Server
• B&R Backup and Restore
• SRS Software Repository Server
• UPS Uninterruptible Power Supply
• NSP Network Services Platform
• CDROM Compact Disc Read Only Memory
• SSC Spare System Controller
• SMC Sun Management Center
• RTS Redundant Transfer Switch
• GUI Graphical User Interface
• DHCP Dynamic Host Configuration Protocol
• UMTS Universal Mobile Telecommunications System
• SF4800 SunTM FireTM 4800 Server
• SF4900 SunTM FireTM 4900 Server
• ST6140 SunTM StorageTekTM 6140 Array
• T3 SunTM T3 StorEdge
Definitions
Main Server
SUN server providing coresident CM, FM, PM real-time for Access, Circuit Core and Packet
Core Networks.
Fallback
It consists in getting back to your original configuration (before network update)

60

W-CDMA
OAM Parameters Network Reconfiguration Procedure
Copyright © 2008 Alcatel-Lucent,

ALCATEL-LUCENT CONFIDENTIAL
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered
only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access
to the current issue. Any hardcopies taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as
expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the
information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third
parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained
herein. If you have received this document in error, please notify the sender and destroy it immediately.
Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of Alcatel-Lucent, Alcatel
and Lucent Technologies.
All other trademarks are the property of their owners.
Document number: NN-20500-196

Document issue: 01.05 / EN
Document status: Preliminary
Product Release: UA06.0
Date: September 2008

20500-196 - (9353 WMS OAM Parameters Network Reconfiguration Procedure) - 01.05-Preliminary

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

20500-196 - (9353 WMS OAM Parameters Network Reconfiguration Procedure) - 01.05-Preliminary

Hochgeladen von

Copyright:

Verfügbare Formate

NN-20500-196

Wireless Service Provider Solutions

Copyright © 2008 Alcatel-Lucent,

All other trademarks are the property of their owners.

June 20th 2008

April 21st 2008

March 17th 2008

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

1 About this Publication................................................................................................................................................... 1

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

Figure 1 - Example of DHCP parameters........................................................................................................... ......... 57

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

1 About this Publication

Scope of this Document

Please Read Carefully

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

2 UMTS Access Network Collection Roadmap

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

5 Network Parameters Reconfiguration

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

5.2 System Impact

Allow Remote Root Access

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

9353 WMS Layout Background Image

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

— All OAM servers

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

6.1 Check Hosts before the Network Reconfiguration

2. Wait for the following log to be displayed

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

6.2 Deactivate the IP Filter

1. Use the following command under a root session:

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

6.3 Deactivate the OS Hardening Tool

1. On each server of the ROC, log on as root.

2. Check if the machine is hardened. Under a root login:

3. Deactivate the OS-Harden module. Under a root session:

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

6.4 Create a New Default Router Configuration File to Change the

1. On each OAM server :

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

to ease the network reconfiguration.

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

6.5 Create a New ROC Configuration File to Change the Network

NN-20500-196 01.05 / EN Preliminary September 2008 Copyright © 2008 Alcatel-Lucent

2. Modify the new ROC configuration file

Note: Be Careful: Do not edit the current ROC configuration file.

You cannot modify another kind of fields (Machine.Hostname, DNS_DOMAIN, ROCNAME,

3. Save the current ROC configuration files

4. Generate the new ROC configuration XML file

Copyright © 2008 Alcatel-Lucent OAM Parameters Network Reconfiguration Procedure

6. Copy the file new_rocconfig.cfg to the other servers of the ROC

7. Goes to the Secondary Main Server