NTP Clock Syn MOP

Alcatel-Lucent
5060 Wireless Call

Server
NTP CLOCK CONFIGURATION

PROCEDURES
Method of Procedure
3HP700334506RJZZA ED 03 RL 01
Release ATCA Generic

All Rights Reserved Alcatel-Lucent 2009.
Copyright Statement
The information contained in this document is subject to change. Changes will occur only in accordance
with formal change control procedures.
This document contains proprietary information which is protected by copyright laws. All rights are
reserved. No part of this document may be photocopied, reproduced, or translated into another language
or program language without the prior written consent of Alcatel-Lucent, Inc.
Alcatel-Lucent, Inc. has prepared the information contained herein solely for the use by Alcatel-Lucent
employees, agents and customers. Dissemination of the information and/or concepts herein to other
parties is prohibited without Alcatel-Lucent's prior written consent..
Alcatel-Lucent acknowledges the following trademarks for company names or products mentioned within
Alcatel-Lucent documents:
UNIX is a registered trademark of The Open Group.
Windows is a registered trademark of Microsoft Corporation.
Java is a registered trademark of Sun Microsystems, Inc.
Status Release October 7, 2009

Alcatel-Lucent Welcome Center
Contact
http://www1.alcatel-lucent.com/comps/pages/carrier_support.jhtml
Alcatel-Lucent 5060 WCS NTP CLOCK CONFIGURATION PROCEDURES
Contents
Alcatel-Lucent Proprietary and Confidential
1 About this Document ..................................................................................................9

1.1 Audience ......................................................................................................... 9
1.2 Contents.......................................................................................................... 9
1.3 Safety Precautions.............................................................................................. 9
1.4 Related and Referred Documents ............................................................................ 9
1.5 Typographic Conventions .................................................................................... 10
1.6 Terminology.................................................................................................... 10
2 Estimated Time and Impact........................................................................................ 11
3 Prerequisites .......................................................................................................... 12
3.1 Assumptions ................................................................................................... 12
3.2 List of Items--Operations' Prerequisites .................................................................. 12
3.3 Detailed Inventory of software/hardware materials ................................................... 13
3.4 Reference Documents........................................................................................ 13
4 Elementary Procedures............................................................................................. 14
4.1 Preparation Procedures ...................................................................................... 14
4.1.1 Performing Maintenance Preparation (Optional) ........................................... 14
4.1.2 Performing a Database Backup (Optional) ................................................... 14
4.1.3 Performing a Pre-activity Health Check...................................................... 14
4.2 NTP Clock Configuration..................................................................................... 16
4.2.1 Setup NTP for WCS Rouzic cards............................................................... 16
4.2.2 Setup NTP for OmniSwitch 6850 ............................................................... 21
4.2.3 Setup NTP for ShMC cards ...................................................................... 22
4.2.4 Setup NTP for WCS Malban cards .............................................................. 23
4.3 Performing a Post-activity Health Check ................................................................. 24
5 Fallback Procedures ................................................................................................. 26
3HP700334506RJZZA ED 03 RL 01 3 / 28
History
Date Edition Author Comments
Feb 26, 2008 01 IP 01 Xu Meiqing MOP initial Draft
Apr 10,2008 01 PD 01 Xu Meiqing Update according to test result
Apr 22, 2008 01 PD 02 Xu Meiqing Incorporate updated MOP of 4.40 SP1.
May 20, 2008 01 PD 03 Xu Meiqing Adapt to the new template
June 6, 2008 01 PD 04 Li Yi Update according to ACE #50960
July 30, 2008 01 RL Li Yi Update according to France&Shanghai Test Report
Dec 08, 2008 02 RL Li Yi Fix PR #57575:

1. Add a new sec 4.2.4.
2. Specify title of sec 4.2.1, 4.2.3.
3. Update command of sec 4.2.2 step 7
Oct 07, 2009 03 PL 01 L. Sessions Fix PR 61280, added note and ATCA driftfile path in
Section 4.2.1.
3HP700334506RJZZA ED 03 RL 01 5 / 28
NTP CLOCK CONFIGURATION PROCEDURES Alcatel-Lucent 5060 WCS
Approvals

Organization Name Date
Alcatel-Lucent Engineering T. Sabourin Month dd, yyyy
Title: TPM AtriumX
Alcatel-Lucent R&D Ren Fangyi Month dd, yyyy

Industrialization
Title: Indus project leader W4.40
Alcatel-Lucent R&D Liu Quiming Month dd, yyyy
Title: TPM W4.40/ATCA
Alcatel-Lucent PLM O. Lenormand Month dd, yyyy
Title: Indus leader W4.40/ATCA
6 / 28 3HP700334506RJZZA ED 03 RL 01
Alcatel-Lucent Proprietary and Confidential Alcatel-Lucent 5060 WCS NTP CLOCK CONFIGURATION PROCEDURES
3HP700334506RJZZA ED 03 RL 01 7 / 28
1 About this Document

The NTP Clock Configuration MOP provides the recommended process for Network
Timing Protocol related provisioning on the Alcatel-Lucent 5060 Wireless Call Server
System.
1.1 Audience
The target audience for the NTP Clock Configuration MOP includes any person or
organization concerned with:
Performing maintenance tasks on the Alcatel-Lucent 5060 Wireless Call Server
system;
Switch technicians with a knowledgeable understanding of the WCS System;
Familiarity with LINUX administration procedures;
Personnel with root access privileges on the system.
1.2 Contents
The MOP contains next sections:
1. Perform pre-installation site checks;
2. Setup NTP for WCS cards
3. Setup NTP for Omniswitch 6850
4. Setup NTP for ShMC
5. Perform post-installation site checks.
1.3 Safety Precautions

The following labels indicate places in the procedures that may be hazardous to
either the equipment or to personnel.
Indicates that the described activity or situation, such as high voltage or electric
shock hazards, may result in serious personal injury or death.
Indicates that the described activity or situation may, or will, cause equipment
damage or serious performance problems.
Indicates that the described activity or situation may, or will, cause service
interruption.
[Editor's note: Use these labels within the procedures to indicate areas where
special attention is required, or additional information is necessary for proper
completion of the step.]
1.4 Related and Referred Documents

Refer to section 3.2.
3HP700334506RJZZA ED 03 RL 01 9 / 28
1.5 Typographic Conventions

This document uses the following typographic conventions:

text in italics: document titles, section title,
text in bold: menu, option, tab, parameter names, text typed by an operator,
window and dialog box names, important information
Text in [bold italics]: site specific variable information provided by the
customer
text in [text]: explanation of section for writer (should be deleted after the
section is complete ), or parameters format
text in courier: messages displayed by the system.
1.6 Terminology
The following terminology is used in this document:
The terminology used is that specified by the International Telecommunication
Union Telecommunication standardization sector (ITU-T) and European
Telecommunications Standards Institute (ETSI) standards.
On the GUI, WSS indicates the Wireless Call Server (WCS).
Procedures described in this guide are performed using a mouse. "Click" means
use the left mouse button. "Right-click" means use the right mouse button.
10 / 28 3HP700334506RJZZA ED 03 RL 01
2 Estimated Time and Impact

Procedure Estimated Time to Complete Estimated Outage
Performing a pre-activity health check 20 minutes 00 minutes
Setup NTP for WCS Rouzic cards 30 minutes 00 minutes
Setup NTP for Omniswitch 6580 30 minutes (15 minutes/switch) 00 minutes
Setup NTP for ShMC cards 5 minutes/ ShMC, hardware 00 minutes

configuration dependent
Setup NTP for WCS Malban cards 10 minutes/ Malban 00 minutes
Post Activity Health Check 15 minutes 00 minutes
3HP700334506RJZZA ED 03 RL 01 11 / 28
3 Prerequisites
Note: This chapter describes the prerequisite that has to be fulfilled prior to the

procedure execution.
It means that what is written here is NOT a procedure. It is a list of conditions to be
satisfied before the execution of the procedure.
Consequently, we don't have to refer again in the key procedures, that the
conditions are satisfied.
3.1 Assumptions
Ensure that the following conditions have been met before beginning this
procedure:
Maintenance personnel are familiar with Linux OS and commands.
Maintenance personnel are familiar with Alcatel-Lucent 5060 WCS ATCA system
hardware.
Check the availability of NTP Server IP Address collected in the field Data book
section 'NTP IP Address'.
Perform all health checks prior to executing this MOP.
3.2 List of Items--Operations' Prerequisites

The following table lists the Operations' prerequisites.
Table 1 Operations prerequisites - Provisioning SMS......
Items Key Procedures Category Originator Optional /

Mandatory
WCS 5060 CSD (Customer ALL document TPM O

Status document)
WCS 5060 PSR (Product ALL document TPM O

Software Release)
Wiring booklet None document TPM O
WCS 5060 LDF ALL Document TPM O
Adams tool None software Tool TPM O
Databook ALL Document TPM M
IP Conf Plan ALL Document TPM M
12 / 28 3HP700334506RJZZA ED 03 RL 01
3.3 Detailed Inventory of software/hardware materials

Before start the procedure of NTP configuration, all the software/hardware
materials concerned should be download and ready.

Table 2 List of Software/Hardware materials
Name Category Description Download Path
NTP Server IP document From customer

Addresses
Omniswitch 6850 document From customer

IP Addresses
ShMC cards IP document From customer

Addresses
3.4 Reference Documents

Note: This section lists the documents which are referred explicitly in the current
document.
It can be either because we refer to an information which has to be known to
execute the procedure (as an input information), or because we refer to another
MOP procedure in the current one.
In any case the referred document should arrive on site and be prepared in
Operation package by the Operations.
We should only refer to documents which are in the scope of the Operations.
Following documents are required.
1. Databook, ....., section x for NTP IP Address.
3HP700334506RJZZA ED 03 RL 01 13 / 28
4 Elementary Procedures
4.1 Preparation Procedures

4.1.1 Performing Maintenance Preparation (Optional)
Not applicable.
4.1.2 Performing a Database Backup (Optional)

Not applicable.
4.1.3 Performing a Pre-activity Health Check
Estimated Time to Complete: 20 minutes

Estimated Outage: 00 minutes
Perform a pre-activity health check

Note If any results from the Pre-Activity Health Check are abnormal or unexpected, take
action to verify and follow normal escalation procedure before executing the MOP.
Prerequisite(s) None
Normal procedure To perform a pre-activity WCS system health check:

1. Check the WEM and ensure there are no major Alarms and all SIM cards are
active and in service.
2. If any known alarms are present, have customer NOC acknowledge them.
3. Copy all output from Pre Health Checks to a log file and store in a common file
location. This file will be compared later against the data collected in the Post
Activity Health Check.
Note Alcatel-Lucent employees should store this data in the following location:
O:\CustomerSupport\Maint_Activities\<Customer>\<Site>\<Date_MOP_Perform
ed>\
4. Ensure primary SAM is active and all other cards are active/standby
a) SSH to the Primary SAM.
Type:
SSH <primary_sam_addr>
Press ENTER.
b) If primary SAM is standby:
Right click the active SAM and select Active SAM Control > Hot
Switchover. In case of 'Hot Switchover' command failure, use the 'Switch
14 / 28 3HP700334506RJZZA ED 03 RL 01
Active SAM' command.

If primary SAM is already active, then ignore this step.
c) Type:
oamf_cards
Press ENTER.
d) Ensure that Inactive does not appear on the output for the SIM cards.
e) Ensure that Not operational does not appear on the output for all other
cards.
5. Check SS7 links' status.
Type:
SSH <Primary sam addr>
Press ENTER.
b) Type:
ss7LinkInfo a
Press ENTER.
Verify that all applicable SS7 links are in service (ISV), uninhibited (notInh),
and not congested (notCon).
6. Check the number of active calls on CCMs.
From the primary SAM type:
getCallsOnCCM.sh ccm
Press ENTER.
Or via the WEM in Tools > EMS Scripts > Argument Input and then type:
ccm
Press Start.
7. Check the number of active subscribers on CCMs.
countVLRRecords.sh
Press ENTER.
8. For each CCM on which the previous script is run, record the results.
This data will be compared against the data collected in the Post Activity
Health Check. The number of active subscribers should not differ significantly.
9. Check for any core dumps that might have occurred.
Type:
rshCmd ls ltr /stats/core/* all
Press ENTER.
10. Ensure that replication is in good standing on SAM, DDM, and CCM.
Type:
rshCmd p checkrep.sh sam ddm ccm
Press ENTER.
There should be:
35 replication PIDs for SAMs,
7 for DDMs (5 on a 2 DDM system), and
5 for CCMs.
Note There should be no DDM or CCM replication for GMSC.
3HP700334506RJZZA ED 03 RL 01 15 / 28
11. Check that the software version is the correct patch level available on the WCS.
Type:
cat /space/stats/Atrium_Release_Info.txt
Press ENTER.

12. Check the available capacity of the file systems.
Type:
rshCmd df k all
13. Ensure that no file systems are over 70% capacity.
14. End.
4.2 NTP Clock Configuration

4.2.1 Setup NTP for WCS Rouzic cards
Normal procedure To configure NTP Clock:

1. SSH into the primary SAM using proper userid and password.
ssh < primary_sam_addr >.
2. Test the IP connectivity to the NTP server from each SAM by issuing the
following command:
From each SAM, run:
ping < ntp_server_addr >
i.e. ping 110.100.133.121
Repeat if you have the secondary NTP server.
3. On the primary SAM, verify that the /etc/ntp.conf file contains the following
entries. If all of the entries are not in the ntp.conf file change it to match the
following:
vi /etc/ntp.conf
server < primary_ntp_server_addr> prefer
server < secondary_ntp_server_addr >
server 127.127.1.0
fudge 127.127.1.0 stratum 10
peer <hostname_secondary_sam >
Note There are two different hardware configurations for a WCS. The steps below
are annotated where there is a difference between Netra and ATCA by a
statement similar to [for SUN Netra WCS]
(Example: chmss965_sam_1_5_1 for hostname_secondary_sam.)
16 / 28 3HP700334506RJZZA ED 03 RL 01
enable auth monitor

driftfile /var/ntp/ntp.drift [for SUN Netra WCS]
driftfile /var/lib/ntp/drift [for ATCA WCS]
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable
4. Save the file after making changes by typing ESC:wq!.
5. Switch to the secondary SAM by typing goCard <secondary_sam_addr>.
6. On the secondary SAM, verify that the /etc/ntp.conf file contains the
following entries. If all of the entries are not in the ntp.conf file change it to
the following:
Note: This step can be shorted/secured by first copying the /etc/ntp.conf file
from the primary SAM to the secondary SAM by: "rcp /etc/ntp.conf
SAM014:/etc/" as an example
vi /etc/ntp.conf
server <primary_ntp_server_addr> prefer
server < secondary_ntp_server_addr>
server 127.127.1.0
fudge 127.127.1.0 stratum 10
peer <hostname_primary_sam>
(Example: chmss965_sam_1_4_1 for hostname_primary_sam.)
enable auth monitor

statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable
7. Save the file after making changes by typing ESC:wq!
8. Return to the primary SAM by typing exit twice.
9. Using the goCard command, switch to one of the nonSAM cards and perform
the following step.
10. On the non-SAM card, check the ntp.conf file and, if necessary, change it to
match the following:
vi /etc/ntp.conf
server <hostname_primary_SAM> prefer
3HP700334506RJZZA ED 03 RL 01 17 / 28
server <hostname_secondary_SAM>

11. Save the file after making changes by typing ESC:wq!
12. Copy the nonSAM card ntp.conf to all of the other nonSAM cards by typing:
cpFiles /etc/ntp.conf d /etc/ ccm ddm sim ipm
13. Return to the primary SAM by typing exit twice.
14. Stop the NTP daemon on all cards by executing the following command on the
primary SAM:
bvueuma_sam_1_6_1:> rshCmd p /etc/rc.d/init.d/ntpd stop all
The expected results should appear similar to:
On SIM001 10.100.2.20 bvueuma_sim_1_1_4 ...
On SIM002 10.100.2.21 bvueuma_sim_1_1_5 ...
On IPM003 10.100.2.22 bvueuma_ipm_1_1_6 ...
On SAM013 10.100.2.35 bvueuma_sam_1_5_1 ...
On SAM014 10.100.2.37 bvueuma_sam_1_6_1 ...
On DDM015 10.100.2.39 bvueuma_ddm_1_7_1 ...
On DDM016 10.100.2.41 bvueuma_ddm_1_8_1 ...
15. On the primary SAM, sync up the time with NTP server:
/usr/sbin/ntpdate <primary_ntp_server_addr>.
The following output is an example of the /usr/sbin/ntpdate command
failure:
27 Sep 13:59:45 /usr/sbin/ntpdate[29356]: the NTP socket is
in use, exiting.
Stop the NTP Daemon on Primary SAM using command: /etc/rc.d/init.d/ntpd

stop and run /usr/sbin/ntpdate command again:
The following is an example of the command executed successfully:
27 Sep 14:01:17 /usr/sbin/ntpdate[29458]: adjust time server
10.25.63.11 offset 0.000868 sec
16. On the primary SAM, bring up the NTP daemon by typing:
/etc/rc.d/init.d/ntpd start
Note: Wait until the clocks sync up with the NTP server. It may take 2 to 3
minutes for this to happen
17. Use this command and verify that the clock is in sync with the NTP server:
18 / 28 3HP700334506RJZZA ED 03 RL 01
ntpq c peers
Note: An example of the output is shown below. The character * on the
first line indicates the system clock is synced up with External NTP server. The
synchronization source appears with an asterisk (*) or the letter o in front of

it in the output. If no servers are within the maximum distance, the potential
synchronization source has a pound sign (#) in front of it. Any other servers
which survive the clustering algorithm have a plus sign (+) in front of the
hostname in the ntpq peers output.
==============================================================================
LOCAL(0) LOCAL(0) 10 l 18 64 377 0.00 0.000 10.01
*172.22.103.122 143.209.238.179 3 u 35 128 377 0.78 -0.136 3.17
OPSTEC1_sam_1_6 0.0.0.0 16 u 39 64 0 0.00 0.000 16000.0
18. Sync up the clock on the secondary SAM with the primary SAM by executing the
following command:
rshCmd p /usr/sbin/ntpdate <primary_sam_internal_addr>
<secondary_sam_nodenum>
Note: If an error message that NTP Socket is in use displays. Using
goCard to switch to the Secondary SAM, stop the NTP Daemon by
etc/rc.d/init.d/ntpd stop and wait for 10-15 minutes after the Daemon of
primary SAM has brought up and then run /usr/sbin/ntpdate command again.
Return to the primary SAM by typing exit twice.
19. Sync up the clocks on the rest of the cards with the primary SAM by executing
the following command:
rshCmd p /usr/sbin/ntpdate <primary_sam_internal_addr> nonsam
Note: If error message NTP Socket is in use of a faulty card displays.
Using goCard to switch to the faulty card, stop the NTP Daemon by
/etc/rc.d/init.d/ntpd stop and run /usr/sbin/ntpdate command again. Return
to the primary SAM by typing exit twice.
20. Bring up the NTP daemons on the rest of the cards by executing the following
commands on the primary SAM:
a) rshCmd p /etc/rc.d/init.d/ntpd start <secondary_sam_nodenum>
b) rshCmd p /etc/rc.d/init.d/ntpd start nonsam
21. Wait for all cards to sync up by running the following command on primary SAM:
rshCmd -p /usr/sbin/ntpq c peers all
22. Look for * character on the output of every node as shown in the example
below:
OPSTEC1_sam_1_5_1:> rshCmd 'ntpq -c peers' all
On SIM001 10.161.135.148 OPSTEC1_sim_1_1_4 ...
remote refid st t when poll reach delay offset disp
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 60 64 377 0.35 -0.113 0.09
+OPSTEC1_sam_1_6 172.22.103.122 4 u 60 64 377 0.24 -0.844 0.06
On SIM002 10.161.135.149 OPSTEC1_sim_1_1_5 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 58 64 377 0.58 -0.163 0.05
+OPSTEC1_sam_1_6 172.22.103.122 4 u 58 64 377 0.44 -0.902 0.12
On SIM003 10.161.135.150 OPSTEC1_sim_1_1_6 ...
3HP700334506RJZZA ED 03 RL 01 19 / 28
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 55 64 377 0.47 -0.107 0.05
+OPSTEC1_sam_1_6 172.22.103.122 4 u 55 64 377 0.32 -0.913 0.11
On SIM004 10.161.135.151 OPSTEC1_sim_1_1_7 ...

==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 53 64 377 0.53 -0.107 0.02
+OPSTEC1_sam_1_6 172.22.103.122 4 u 53 64 377 0.38 -0.921 0.14
On SIM005 10.161.135.152 OPSTEC1_sim_1_1_8 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 50 64 377 0.52 -0.033 0.03
+OPSTEC1_sam_1_6 172.22.103.122 4 u 50 64 377 0.38 -0.772 0.11
On SIM006 10.161.135.153 OPSTEC1_sim_1_1_9 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 48 64 377 0.58 -0.081 0.06
+OPSTEC1_sam_1_6 172.22.103.122 4 u 48 64 377 0.44 -0.916 0.06
On SIM007 10.161.135.154 OPSTEC1_sim_1_1_10 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 45 64 377 0.50 -0.065 0.05
+OPSTEC1_sam_1_6 172.22.103.122 4 u 45 64 377 0.41 -0.947 0.14
On SAM013 10.161.135.163 OPSTEC1_sam_1_5_1 ...
==============================================================================
LOCAL(0) LOCAL(0) 10 l 44 64 377 0.00 0.000 10.01
*172.22.103.122 143.209.238.179 3 u 125 128 377 1.08 -0.130 0.08
+OPSTEC1_sam_1_6 172.22.103.122 4 u 9 64 357 0.50 -0.775 0.53
On SAM014 10.161.135.165 OPSTEC1_sam_1_6_1 ...
==============================================================================
LOCAL(0) LOCAL(0) 10 l 42 64 377 0.00 0.000 10.01
*172.22.103.122 143.209.238.179 3 u 41 64 377 0.92 0.471 0.06
+OPSTEC1_sam_1_5 172.22.103.122 4 u 40 64 376 0.46 0.752 0.56
On DDM015 10.161.135.167 OPSTEC1_ddm_1_7_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 44 64 377 0.34 -0.083 0.03
+OPSTEC1_sam_1_6 172.22.103.122 4 u 44 64 377 0.38 -0.834 0.06
On DDM016 10.161.135.169 OPSTEC1_ddm_1_8_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 41 64 377 0.37 -0.082 0.06
+OPSTEC1_sam_1_6 172.22.103.122 4 u 1 128 377 0.41 -0.918 0.09
On DDM017 10.161.135.171 OPSTEC1_ddm_1_9_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 39 64 377 0.46 -0.044 0.03
+OPSTEC1_sam_1_6 172.22.103.122 4 u 39 64 377 0.38 -0.849 0.05
On CCM018 10.161.135.173 OPSTEC1_ccm_1_10_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 36 64 377 0.47 -0.070 0.02
+OPSTEC1_sam_1_6 172.22.103.122 4 u 36 64 377 0.35 -0.864 0.09
On CCM019 10.161.135.175 OPSTEC1_ccm_1_11_1 ...
20 / 28 3HP700334506RJZZA ED 03 RL 01
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 34 64 377 0.49 -0.061 0.02
+OPSTEC1_sam_1_6 172.22.103.122 4 u 34 64 377 0.35 -0.852 0.06
On CCM020 10.161.135.177 OPSTEC1_ccm_1_12_1 ...

==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 32 64 377 0.35 -0.105 0.06
+OPSTEC1_sam_1_6 172.22.103.122 4 u 32 64 377 0.26 -0.763 0.08
On CCM021 10.161.135.179 OPSTEC1_ccm_1_13_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 29 64 377 0.41 -0.001 0.05
+OPSTEC1_sam_1_6 172.22.103.122 4 u 29 64 377 0.38 -0.836 0.08
On CCM022 10.161.135.181 OPSTEC1_ccm_1_14_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 27 64 377 0.41 -0.107 0.08
+OPSTEC1_sam_1_6 172.22.103.122 4 u 27 64 377 0.32 -0.895 0.08
On CCM023 10.161.135.183 OPSTEC1_ccm_1_15_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 25 64 377 0.44 -0.063 0.12
+OPSTEC1_sam_1_6 172.22.103.122 4 u 25 64 377 0.38 -0.892 0.15
On CCM024 10.161.135.185 OPSTEC1_ccm_1_16_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 23 64 377 0.55 -0.057 0.06
+OPSTEC1_sam_1_6 172.22.103.122 4 u 23 64 377 0.46 -0.859 0.06
On CCM025 10.161.135.187 OPSTEC1_ccm_1_17_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 21 64 377 0.52 -0.103 0.11
+OPSTEC1_sam_1_6 172.22.103.122 4 u 21 64 377 0.44 -0.885 0.09
On CCM026 10.161.135.189 OPSTEC1_ccm_1_18_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 18 64 377 0.37 -0.054 0.05
+OPSTEC1_sam_1_6 172.22.103.122 4 u 18 64 377 0.27 -0.873 0.09
On CCM027 10.161.135.191 OPSTEC1_ccm_1_19_1 ...
==============================================================================
*OPSTEC1_sam_1_5 172.22.103.122 4 u 16 64 377 0.50 -0.065 0.06
+OPSTEC1_sam_1_6 172.22.103.122 4 u 16 64 377 0.41 -0.902 0.05
23. Exit the SSH session.
4.2.2 Setup NTP for OmniSwitch 6850

Estimated Time to Complete: 30 minutes (15 mins/switch)
Note: The procedure MUST be applied to both Omniswitch 6850 devices
successively.
1. From the primary SAM , login to OmniSwitch via telnet by the internal address
of the OmniSwitch.
3HP700334506RJZZA ED 03 RL 01 21 / 28
e.g.: 192.168.255.7 for R1 and 192.168.255.8 for R2

Note: for additional information refers to MOP "Omniswitch 6850 Ethernet
Switch Configuration" 3HP700334503RJZZA.

2. Test the IP connectivity to the SAM by issuing next command:
ping <primary_sam_internal_addr>
3. Backup original boot.cfg file:
cp /flash/working/boot.cfg /flash.working/boot.cfg.ori
4. Verify that the /flash/working/boot.cfg file contains the following entries. If
all of entries are not in boot.cfg file, change it to match the following:
ntp client enable
ntp server <primary_sam_internal_addr> prefer
ntp server <secondary_sam_internal_addr>
5. Save file after making changes by typing :ESC:wq!.
6. Restart Omniswitch to register changes:
reload working no rollback-timeout
7. After these operations you can check your configuration by typing commands:
show ntp client
show ntp client server-list
show ntp server status
8. If NTP works properly then save configuration to certified by command:
copy working certified
9. Repeat procedure for second Omniswitch 6850 device.
4.2.3 Setup NTP for ShMC cards

Estimated Time to Complete: 5 minutes/ShMC Hardware configuration dependent
Note: The procedure MUST be applied to all the ShMC cards successively. (2. 4. 6
according to WCS model)
1. From the primary SAM, telnet to the internal RMCP address of the active ShMC
of first ACTA shelf (e.g.: 192.168.255.45 for shelf AB)
telnet <RMCP address of active ShMC>
2. Check the status of ShMc by command
clia shmstatus
3. If current manager is not active, then either connect to active manager or
perform switchover by command
clia switchover
Note: If you use RS session ETH0 address will migrate from front panel to back
panel side.
22 / 28 3HP700334506RJZZA ED 03 RL 01
4. setenv time_proto ntp

5. setenv time_server <primary_SAM_internal_addr>
6. reboot
After reboot all new settings will be applied.

Note: Reboot will initiate a ShMC switchover, this will break connection to
current ShMC.
Note: Starting from release 2.3.2 this process will be automated.
7. Telnet again to RMCP address to connect to the newly active ShMC.
8. Repeat procedure for both ShMC of the other ACTA shelves.
4.2.4 Setup NTP for WCS Malban cards

Estimated Time to Complete: 10 minutes/Malban
To configure NTP clock in Malban cards.

1. SSH into the primary SAM using proper userid and password.
ssh <OAM_primary_sam_addr>
2. From the SAM, SSH to the first Malban card using proper userid and password
(currently root / alatcav2). The Malban cards have internal IP addresses
which are defined in the "External and Internal IP addressing plan" MOP, for
example 192.168.255.71 for Malban slot 7 of the ATCA shelf AB :
ssh 192.168.255.71 (internal IP address of the Malban card)
3. Edit the ntp.conf file :
cd /etc
vi /etc/ntp.conf
4. Check/add the following lines :
server <primary_sam_internal_addr> prefer
server <secondary_sam_internal_addr>
driftfile /etc/ntp/drift
Then save the file.
5. Copy the Malban ntp.conf file to ALL the other Malban cards one by one:
scp /etc/ntp.conf <Malban_internal_addr>:/etc/.
Proceed with next Malban card.
6. Stop the NTP daemon on current Malban card :
/etc/rc.d/init.d/ntp stop
7. Check the NTP daemon is really stopped, else kill the relating process :
3HP700334506RJZZA ED 03 RL 01 23 / 28
ps -edf | grep ntp

kill -9 xxxx (xxxx : NTP process PID)
8. Synchronize the Malban clock with the primary SAM :

cd /usr/sbin/
./ntpdate <primary_sam_internal_addr>
9. Start the NTP daemon on current Malban card :
/etc/rc.d/init.d/ntp start
10. Check the date id OK compared to primary SAM :
date
11. Disconnect from the current and connect to the next one :
exit
ssh 192.168.255.72 (next Malban internal IP address)
12. Repeat the sequence from step 6 (stopping NTP daemon etc...)
4.3 Performing a Post-activity Health Check

Prerequisite(s) None
Normal procedure To perform the following activity health checks:

1. Ensure primary SAM is active
If primary SAM is standby, make it active by selecting Hot Switchover from
the active SAM on the WEM. In case of ' 'Hot Switchover' command failure, use
the "Switch Active SAM" command.
2. Check the WEM and ensure that there are no major or new Alarms and all SIM
cards are active and in service.
3. All output from Post Health Checks should be copied to a log file and stored in a
common file location. This file should be compared against the data that was
collected in the Pre Activity Health Check.
Note: Alcatel-Lucent employees should compare this data with the data collected and
stored in the following location:
O:\CustomerSupport\Maint_Activities\<Customer>\<Site>\<Date_MOP_Perfor
med>\
4. Ensure primary SAM is active and all other cards are active/standby
a) SSH to the Primary SAM
Type:
24 / 28 3HP700334506RJZZA ED 03 RL 01
SSH <primary sam addr>

Press <Enter>
b) If primary SAM is standby:
Right click the active SAM and select Active SAM Control > Hot
Switchover. In case of 'Hot Switchover' command failure, use the 'Switch
Active SAM' command.
c) Type:
oamf_cards
Press <Enter>
d) Ensure that Inactive does not appear on the output for any of the cards.
e) Ensure that Not operational does not appear on the output for all other
cards.
5. Check SS7 links status.
Type:
SSH <primary sam Addr>
Press <Enter>.
b) Type:
ss7LinkInfo a
Press <Enter>
Verify that all applicable SS7 links are in service (ISV), uninhibited (notInh),
and not congested (notCon).
6. Check the number of active calls on CCMs.
getCallsOnCCM.sh ccm
Press <ENTER>.
Or via the WEM in Tools > EMS Scripts > Argument Input and then type
in ccm and press Start.
7. Check the number of active subscribers on CCMs.

countVLRRecords.sh
Press <ENTER>.
For each CCM on which the previous script is run, record the results. This data
will be compared against the data collected in the Post Activity Health Check.
The number of active subscribers should not differ significantly.
8. Check the WEM and ensure that there are no major or new Alarms and all SIM
cards are active and in service.
9. Check that the NTP peerstats, loopstats and clockstats log files are generated
and stored in the /var/ntp/ntpstats directory.
3HP700334506RJZZA ED 03 RL 01 25 / 28
10. Ensure that replication is in good standing on SAM, DDM, and CCM.
Type:
rshCmd p checkrep.sh sam ddm ccm

Press <Enter>.
There should be:

35 replication PIDs for SAMs,
7 for DDMs (5 on a 2 DDM system), and
5 for CCMs.
Note: There should be no DDM or CCM replication for GMSC.

11. Check for any core dumps that might have occurred.
Type:
rshCmd ls ltr /stats/core/* all
Press <Enter>.
12. Check the available capacity of the file systems.
Type:
rshCmd df k all
Press <Enter>.
13. Ensure that no file systems are over 70% capacity.
14. The customer should perform basic test calls.
5 Fallback Procedures
Estimated Time to Complete: xx minutes
Estimated Outage: xx minutes
There are no fall back procedures associated with setting the NTP clock
configuration. If these procedures have not been successfully accomplished,
contact your next level of support for assistance.
26 / 28 3HP700334506RJZZA ED 03 RL 01
Alcatel-Lucent Proprietary and Confidential Alcatel-Lucent 5060 WCS NTP CLOCK CONFIGURATION PROCEDURES
Abbreviation
C
CCM Call Control Module
CSD Customer Status document
CST Central European Summer Time
D
DDM Data Distributed Module
E
ESD Electro Static Discharge
ETSI European Telecommunications Standards Institute
ITU-T International Telecommunication Union Telecommunication
L
LDF Level Definition File
M
MOP Method of Procedure
N
NOC Network Operation Center
NTP Network Terminal Protocol
P
PHR Product Hardware Release
PSR Product software release
3HP700334506RJZZA ED 03 RL 01 27 / 28

S
SAM System Admin Module
SIM Signaling Interface Module
SSH Secure Shell
T
TPM Technical project manager
U
UTC Universal Time Coordinated
W
WCS Wireless Call Server
WEM Wireless Element Manager
WMG Wireless Media Gateway
WSS Wireless Soft Switch
28 / 28 3HP700334506RJZZA ED 03 RL 01

NTP Clock Syn MOP

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

NTP Clock Syn MOP

Transféré par

Droits d'auteur :

Formats disponibles

Alcatel-Lucent

5060 Wireless Call

NTP CLOCK CONFIGURATION

Release ATCA Generic

Status Release October 7, 2009

1 About this Document ..................................................................................................9

Date Edition Author Comments

Feb 26, 2008 01 IP 01 Xu Meiqing MOP initial Draft

Apr 10,2008 01 PD 01 Xu Meiqing Update according to test result

Apr 22, 2008 01 PD 02 Xu Meiqing Incorporate updated MOP of 4.40 SP1.

May 20, 2008 01 PD 03 Xu Meiqing Adapt to the new template

June 6, 2008 01 PD 04 Li Yi Update according to ACE #50960

July 30, 2008 01 RL Li Yi Update according to France&Shanghai Test Report

Dec 08, 2008 02 RL Li Yi Fix PR #57575:

Alcatel-Lucent Proprietary and Confidential

Alcatel-Lucent Engineering T. Sabourin Month dd, yyyy

Title: TPM AtriumX

Alcatel-Lucent R&D Ren Fangyi Month dd, yyyy

Alcatel-Lucent R&D Liu Quiming Month dd, yyyy

Title: TPM W4.40/ATCA

Alcatel-Lucent PLM O. Lenormand Month dd, yyyy

Title: Indus leader W4.40/ATCA

1 About this Document

1.3 Safety Precautions

1.4 Related and Referred Documents

1.5 Typographic Conventions

Alcatel-Lucent Proprietary and Confidential

2 Estimated Time and Impact

Performing a pre-activity health check 20 minutes 00 minutes

Setup NTP for WCS Rouzic cards 30 minutes 00 minutes

Setup NTP for Omniswitch 6580 30 minutes (15 minutes/switch) 00 minutes

Setup NTP for ShMC cards 5 minutes/ ShMC, hardware 00 minutes

Setup NTP for WCS Malban cards 10 minutes/ Malban 00 minutes

Post Activity Health Check 15 minutes 00 minutes

Alcatel-Lucent Proprietary and Confidential

3.2 List of Items--Operations' Prerequisites

Items Key Procedures Category Originator Optional /

WCS 5060 CSD (Customer ALL document TPM O

WCS 5060 PSR (Product ALL document TPM O

Wiring booklet None document TPM O

WCS 5060 LDF ALL Document TPM O

Adams tool None software Tool TPM O

Databook ALL Document TPM M

IP Conf Plan ALL Document TPM M

3.3 Detailed Inventory of software/hardware materials

materials concerned should be download and ready.

Name Category Description Download Path

NTP Server IP document From customer

Omniswitch 6850 document From customer

ShMC cards IP document From customer

3.4 Reference Documents

Alcatel-Lucent Proprietary and Confidential

4.1.2 Performing a Database Backup (Optional)

4.1.3 Performing a Pre-activity Health Check

Estimated Time to Complete: 20 minutes

Perform a pre-activity health check

Normal procedure To perform a pre-activity WCS system health check:

Active SAM' command.

Note There should be no DDM or CCM replication for GMSC.

Alcatel-Lucent Proprietary and Confidential

4.2 NTP Clock Configuration

Normal procedure To configure NTP Clock:

(Example: chmss965_sam_1_5_1 for hostname_secondary_sam.)

enable auth monitor