OMCR Manual

Wireless Service Provider Solutions
OMC--RPreventiveand
CorrectiveMaintenanceManual
PE/DCL/DD/0032 15.03/EN Preliminary March 2004
411--9001--032
<32> : OMC--R PreventiveandCorrectiveMaintenanceManual
OMC--RPreventiveandCorrective
MaintenanceManual
Document number: PE/DCL/DD/0032
411--9001--032
Document status: Preliminary
Document issue: 15.03/EN
Product release: GSM/BSS V15.0
Date: March 2004
Copyright 1999--2004 Nortel Networks, All Rights Reserved
Originated in France
NORTEL NETWORKS CONFIDENTIAL:
The informationcontainedinthis document is the property of Nortel Networks. Except as specifically authorizedinwritingby Nortel
Networks, the holder of this document shall keepthe informationcontainedhereinconfidential andshall protect same inwhole or inpart
fromdisclosure anddisseminationto thirdparties anduse for evaluation, operationandmaintenance purposes only.
Youmay not reproduce, represent, or downloadthroughany means, the informationcontainedhereininany way or inany formwithout
prior writtenconsent of Nortel Networks.
The followingare trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL
Globemark, S2000, S2000E, S2000H, S2000L S4000, S8000, S8002. GSMis a trademark of FranceTelecom.
Sun, Ultrastation, Ultra5, Ultra Enterprise are registeredtrademarks of SunMicrosystems, Inc.
All SPARC trademarks are usedunder license andare trademarks or registeredtrademarks of SPARC International, Inc. inthe United
States andother countries. Sybase is a registeredtrademark of Sybase, Inc. Lexmark is a registeredtrademark of Lexmark
International, Inc.
All other brandandproduct names are trademarks or registeredtrademarks of their respective holders.
Publication History Nortel Networks Confidential iii
OMC--RPreventiveandCorrectiveMaintenanceManual Copyright E 1999--2004 Nortel Networks
PUBLICATIONHISTORY
Systemrelease: GSM/BSS V15.0
March2004
Issue15.03/EN Preliminary
Upissuedthismanual for apreliminaryrelease
J anuary2004
Issue15.02/EN Draft
Madeupdatetoapplicabilityof theproceduresaddressingV15.0insteadof V14.3.
December 2003
Issue15.01/EN Draft
Addedchanges fromfeatureOAM--24032, Centralizedinstallationandupgrade
service. Added descriptions of new GUI Sequencer, Jumpstart service,
LiveUpgradeservice, andFlashArchiveinstallationcapability.
October 2003
Incorporatedtechnical changesfromTiger Team comments.
UpdateaccordingCR Q00772386--01, changedfault number 30519, cause52965
description.
UpdateaccordingCR Q00756849--01: updateof Chapter 1.3.2.4.
August2003
UpdateaccordingCRQ00642796--01: updateof alarms52311and52312(Chapter
5.5)
Publication History
Nortel Networks Confidential
iv
PE/DCL/DD/0032
411--9001--032
Preliminary 15.03/EN March 2004 Copyright E 1999--2004 Nortel Networks
UpdateaccordingCR Q00184571--03: OMC--R applicativebackuptool defect
(Chapter 1.13)
UpdateaccordingCR Q00671374Cevennes A5200: Alarm30533not inNTP
PE/DCL/DD/032 inchapter 5Updateof 30531, 30532, 30533fault numbers
Update fault number sources: 30500--30503, 30505, 30508, 30510--527, 31001
accordingtoexternal document: SIEQ3OMC--Rdocument2.4: Eventmediation
(PE/MD/DD/000309.10/EN)
Publication History Nortel Networks Confidential v
April 2003
Minor editorial update
J anuary2003
UpdateaccordingCRQ00435793: ORF/GPRS: questionabout useof ftppcuuser
onV12.4B, C andD (Chapter 1.15)
Thefollowingitemshavebeenintroduced:
OMC--R monoboxMaintenancechecksinchapter 3.3.1.3,
OMC--R monoboxPreventivemaintenancebackupinchapter 3.3.2.3
OMC--R monoboxSystemglobal restorationinchapter 4.2.1.3
November 2002
Minor editorial update
UpdateaccordingnewV14.3feature:
PR1561: SUN Fire880introductionasmonoboxOMC--R server
Systemrelease: GSM/BSS V13
November 2002
Issue13.09/EN Standard
UpdateaccordingnewV13.2bfeature:
PR1562: OMC--R capacityimprovement (3200cells)
August2002
ChangedtoStandard-- Minor editorial update
UpdateaccordingnewV13.2bfeature:
PR1295: OMC--R T3xx Storage Array support (13849) in chapters 1.2.4.6,
12.4.7, 1.2.5.13, 1.2.7.1, 3.2.2.1
Publication History
vi
PE/DCL/DD/0032
411--9001--032
Updateafter review
April 2002
Issue13.06/EN Draft
Introduction: CentralizedarchivingChapter 1.13
March2002
UpdateaccordingtoCR Q00215765(Section1.2.6.1)
May2001
Introduction: RestorePCUSN filesystem, Chapter 1
Update:
NTP restructuring:
Theproceduresof thepreventiveandcorrectivemaintenanceareremoved, refer to
the procedures DS/OMC/APP/0012, DS/OMC/APP/0016, DS/OMC/APP/0017
andDS/OMC/APP/0024.
Toobtainthelatest updateof theseprocedures, call themanufacturer.
Updateafter review
Updatehardware, E4503server, Chapter 1
Integrationof tool cf_save_tools.xininteractivemode, Chapter 1
Updateof 30517fault number, Chapter 5
Changedfor fault numbers: cause bysource, Chapter 5
Call themanufacturer, Chapters4and5
Integrationof feature: FM1273PCU OAM configurationbackup, all Chapters
Integration of service request EE00911 partitions of archive/restore,
Paragraphs 1.10.3and1.10.4
February2001
Issue13.02/EN Draft
Publication History Nortel Networks Confidential vii
Update:
OMC-R Preventiveprocedures:
OMC-R preventive maintenance backup (DS/OMC/APP/0016 04.42/EN),
Paragraph3.5
Correctivemaintenanceprocedures:
OMC-R system global restoration (DS/OMC/APP/0017 04.47/EN),
Paragraph 4.2
Integrationof feature
FM1273: PCU OAM configurationbackup
October 2000
Updateof hardware: S1000, SSA, Sparc5, ROT not supported
Update:
NoFix check of the Sybase database (DS/OMC/APP/0012 04.03/EN),
Paragraph3.3
OMC-R maintenance checks (DS/OMC/APP/0024 04.41/EN),
Paragraph 3.4
Paragraph3.5
Paragraph 4.2
Fix check of the Sybase database (DS/OMC/APP/0012 04.03/EN),
Paragraph4.3
A5XXX disk arraydevicemaintenance, Paragraph4.4
Systemrelease: GSM/BSS V12
September 2001
Noupdatefor 12.4C Customer Readinessrelease.
Publication History
viii
PE/DCL/DD/0032
411--9001--032
May2001
Introduction: RestorePCUSN filesystem, Chapter 1
NTP restructuring:
Theproceduresof thepreventiveandcorrectivemaintenanceareremoved, refer to
the procedures DS/OMC/APP/0012, DS/OMC/APP/0016, DS/OMC/APP/0017
andDS/OMC/APP/0024.
Updateafter review
Updatehardware, E4503server, Chapter 1
Integrationof tool cf_save_tools.xininteractivemode, Chapter 1
Updateof 30517fault number, Chapter 5
Changedfor fault numbers: cause bysource, Chapter 5
Call themanufacturer, Chapters4and5
Integrationof feature: FM1273PCU OAM configurationbackup, all Chapters
September 2000
Update:
OMC-R maintenancechecks(DS/OMC/APP/002404.41/EN), Paragraph 3.4
Paragraph 4.2
correctivemaintenance: oneparagraphfor A5XXX or SSA disk array device,
Paragraph4.4
Integrationof servicerequest SR 30331914script croot for ds_omcAutoStart. sh
tool, sheets4, 8, and13, Paragraph4.2.8
Publication History Nortel Networks Confidential ix
J une2000
Updateafter review
Paragraph 3.4
Paragraph3.5
Preliminarytests, Paragraph4.1.1.
Paragraph 4.2
SSA disk arraydevicemaintenance, Paragraph4.5
Integration of service request SR 30315343threshold suppression for synthetic
counters(fault number 31200)
March2000
Issue12.07/EN Draft
Introductionof GPRS.
Updatefault numbers31200, 30508, 30519, 30523, Chapter 5.
Addfault numbers30074, 30529, 30530, Chapter 5.
Integrationof servicerequest SR 30112372OMC-R outageduetopassiveserver
failure(NFI 94) OMC-R defenceandmonitoringChapter 2.
Integrationof servicerequestSR30321386orGV90378introduceinAugust1999
withGV90102andNK91510
J anuary2000
Update
OMC-R Administrationprocedures, Chapter 1
Descriptionof themaintenance, Chapter 2
Publication History
x
PE/DCL/DD/0032
411--9001--032
OMC-R operational test procedures: A5XXX, Paragraph3.2.2.1
Paragraph 3.4
Paragraph3.5
Preliminarytests, Paragraph4.1.1.
Paragraph 4.2
SSA disk arraydevicemaintenance, Paragraph4.5
Transfer:
Backgroundscreenstransfer fromNTP <08>, Chapter 1
Integrationof servicerequest SR EE91155Maintenanceprocedures of theSSA
disk arraydevice, Paragraph4.5
November 1999
Minor editorial update.
Updateafter review
Sybasedatabasecheck (DS/OMC/APP/001204.03/EN), Paragraph3.3
Paragraph 3.4
Paragraph3.5
Paragraph 4.2
Sybasedatabasefix(DS/OMC/APP/001204.03/EN), Paragraph4.3
Publication History Nortel Networks Confidential xi
Updatefault numbers- Helponline
August1999
Issue12.02/EN Draft
Update:
Newtitleof theNTP: OMC-R preventiveandcorrectivemaintenance
31200fault number
Transfer:
OMC-R administrationpresentationtransfersinNTP <06>
TheprocedureEFT check transfersinNTP <34>
TheprocedureBSSmaintenancecheckstransfersinNTP <34>
The procedure BSS Network configuration check and fix transfers in
NTP <34 >
Integrationof servicerequest GV90102or NK91510
Pathtolaunchds_restore.shshell, Paragraph4.2Fiche3
Integrationof servicerequest 30125562
ModifyZaptool, Paragraph1.2.5
Integrationof servicerequest NK91343
Interactif modeof thecf_save_tool.xtool, Paragraph4.2Fiche9
J une1999
Issue12.01/EN Preliminay
NewNTP revisionfor V12release.
Thefollowingitemshavebeenupdated.
Thetopologicconventions, Chapter 5, areintegratedinAbout thisdocument
OMC-R AdministrationPresentation
OMC-R AdministrationProcedures, Chapter 1
start-up, shutdown(singleserver), Paragraph1.2
retrievingtheOMC-R context (zap.sh), Paragraph1.2.4.13
OMC-R Defense, Chapter 2
Publication History
xii
PE/DCL/DD/0032
411--9001--032
Scheduling, Paragraph3.1.2
Sybasedatabasecheck (DS/OMC/APP/001204.01/EN), Paragraph3.3
EFT check (DS/OMC/APP/000404.01/EN)
Paragraph 3.4
BSSmaintenancechecksfromtheOMC-R (DS/BSS/APP/000104.02/EN)
BSSNetwork configurationcheck (PE/OMC/APP/012001.02/EN)
Paragraph3.5
Paragraph 4.2
Sybasedatabasefix (DS/OMC/APP/001204.02/EN), Paragraph4.3
BSSNetwork configurationfix(PE/OMC/APP/012001.02/EN)
Fault Numbers, Chapter 5
Deletionof Neighboringcellscheck inNTP <34>
Integrationof features
FM796: centralizedarchivage
FM793: server securization
CM 954: outsideDNSserver
CM955: outsideNISserver
PR910: singleserver, all chapter
CM956: RemoteoperationinLineModeviaXyplex, Chapters3and4
Integrationof servicerequest SR 30104630
Centralizedarchiving/savingondisk
disaster plan/OMC-R server security
Integrationof servicerequest SR HK90135E4XXX server front power keyin
secureposition, Paragraphs1.2.3.6, 1.2.3.7and1.2.3.8
Integration of service request SR 30091469 Forbid use of [STOP], [A],
Paragraphs1.7.1.4and1.7.2.4
Table of contents Nortel Networks Confidential xiii
Aboutthis document 0--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Applicability 0--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audience 0--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites 0--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related documents 0--2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Howthis document is organized 0--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specific typographical conventions for procedures 0--4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vocabulary conventions 0--8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Graphic Conventions 0--8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Regulations 0--9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 OMC-Radministrationprocedures 1--1 . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction 1--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Centralized Installation and Upgrade Services 1--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Centralized GUI Sequencer 1--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 J umpstart service 1--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3 Flash Archive 1--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4 Live Upgrade service 1--4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 OMC-R start-up, shutdown, and switchover 1--6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Operating rules 1--6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 OMC-R machine operating states 1--6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3 Background menu 1--7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.4 Starting an OMC-R 1--11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.5 Shutting down the OMC--R 1--24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.6 Retrieving the OMC-R context 1--39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.7 Activating an OMC--R switchover in dual-server configuration 1--42 . . . . . . .
1.4 Connection of an X Terminal to an OMC-R site 1--48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 Connecting an X terminal in a standard configuration 1--48 . . . . . . . . . . . . . . .
1.4.2 Connection of an X terminal (X terminal server outside OMC-R) 1--50 . . . . .
1.5 Using the Xyplex and configuration display 1--52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1 Connecting to the local OMC-R Ethernet network 1--52 . . . . . . . . . . . . . . . . . .
1.5.2 Configuration display 1--53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Using the floppy drive 1--55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1 Formatting a floppy in DOS format 1--55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2 Mounting a floppy 1--56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Managing print jobs 1--57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.1 Additional information 1--57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents
xiv
PE/DCL/DD/0032
411--9001--032
1.7.2 Activating a printout 1--57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.3 List of ongoing print jobs 1--60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 Connecting and disconnecting a DAT drive to a workstation 1--62 . . . . . . . . . . . . . . . . . .
1.8.1 Connecting a DAT drive 1--62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.2 Disconnecting a DAT drive 1--64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9 Configuring the Cisco router (V11) 1--66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.1 Introduction 1--66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.2 Tool details 1--66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10 Checking the access rights of software components 1--71 . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1 Introduction 1--71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2 Prerequisites 1--71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3 Initial state 1--71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.4 Actions 1--71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.5 Final state 1--71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11 Archive / restore (OMC-R agent) 1--72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11.1 Purpose 1--72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11.2 Operating rules 1--72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11.3 Archive procedure 1--73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11.4 Restore procedure 1--74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11.5 Procedure for checking an archive cartridge 1--75 . . . . . . . . . . . . . . . . . . . . . .
1.12 Archive / restore (OMC-R Manager) 1--76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12.1 Purpose 1--76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12.2 Operating rules 1--76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12.3 Archive procedure 1--77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12.4 Restore procedure 1--78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12.5 Procedure for checking an archive cartridge 1--79 . . . . . . . . . . . . . . . . . . . . . .
1.13 Centralized archiving configuring procedure 1--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.13.1 Purpose 1--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.13.2 Operating rules 1--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.13.3 Prerequisites 1--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.13.4 OMC--R impact 1--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.13.5 NFS server configuration 1--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.14 Archiving/Restoring via cf_save_tool.x 1--93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.14.1 Cf_save_tool.x usage 1--93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.14.2 OMC--R data archiving/restoring in interactive mode 1--96 . . . . . . . . . . . . . . .
1.14.3 PCU OAM configuration backup/restoring via command line 1--100 . . . . . . . .
Table of contents Nortel Networks Confidential xv
1.15 Restore PCUSN file system 1--105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.15.1 Introduction 1--105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.15.2 Initial status 1--105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.15.3 Actions 1--105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.16 Backup/Restore for PCUOAM of PCUSN configuration files 1--107 . . . . . . . . . . . . . . . . . .
1.16.1 Introduction 1--107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.16.2 Prerequisites 1--107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.16.3 Step 1 1--108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.16.4 Step 3 1--114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Descriptionof theOMC-Rmaintenance 2--1 . . . . . . . . . . . . . . . . . . . . . .
2.1 Introduction 2--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 OMC-R defense and monitoring 2--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Defense 2--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 OMC-R monitoring 2--4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 OMC-Rpreventivemaintenance 3--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Introduction 3--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 List of preventive maintenance procedures 3--1 . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Scheduling of OMC-R preventive maintenance operations 3--1 . . . . . . . . . .
3.2 OMC-R operational test procedures 3--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Introduction 3--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Hardware operational diagnostics 3--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Preventive maintenance for each OMC-R unit 3--13 . . . . . . . . . . . . . . . . . . . . .
3.3 Preventive maintenance procedures 3--19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 OMC-R maintenance checks 3--19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 OMC-R preventive maintenance backup 3--20 . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 Sybase database check 3--22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 OMC-Rcorrectivemaintenance 4--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Preliminary information 4--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Prerequisite 4--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Preliminary tests 4--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Checks 4--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Corrective maintenance procedure 4--15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 OMC-R systemglobal restoration 4--15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents
xvi
PE/DCL/DD/0032
411--9001--032
4.2.2 Sybase database fix 4--16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 A5XXX disk array device maintenance 4--17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Purpose 4--17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Scope 4--17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 Scheduling 4--17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4 Prerequisite 4--18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.5 Systemimpact 4--18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.6 Actions 4--19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.7 Sequence tables 4--23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.8 Sheets 4--25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Procedures associatedwithOMC-Rnotifications 5--1 . . . . . . . . . . . .
5.1 Introduction 5--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 OMC-R notifications 5--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 OMC-R alarms 5--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Maintenance procedure sheet breakdown 5--1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Table of fault numbers 5--2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Fault number: 30020 5--3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.2 Fault number: 30030 5--4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3 Fault number: 30041 5--5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4 Fault number: 30052 5--6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.5 Fault number: 30060 5--7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.6 Fault number: 30061 5--8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.7 Fault number: 30063 5--9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.8 Fault number: 30071 5--10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.9 Fault number: 30072 5--11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.10 Fault number: 30073 5--12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.11 Fault number: 30074 5--13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.12 Fault number: 30130 5--14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.13 Fault number: 30131 5--15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.14 Fault number: 30500 5--16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.15 Fault number: 30501 5--19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.16 Fault number: 30502 5--21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.17 Fault number: 30503 5--22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.18 Fault number: 30504 5--23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.19 Fault number: 30505 5--24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents Nortel Networks Confidential xvii
5.5.20 Fault number: 30506 5--26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.21 Fault number: 30507 5--27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.22 Fault number: 30508 5--28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.23 Fault number: 30509 5--29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.24 Fault number: 30510 5--30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.25 Fault number: 30511 5--31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.26 Fault number: 30512 5--32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.27 Fault number: 30513 5--33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.28 Fault number: 30514 5--35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.29 Fault number: 30515 5--36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.30 Fault number: 30516 5--37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.31 Fault number: 30517 5--39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.32 Fault number: 30519 5--40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.33 Fault number: 30520 5--42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.34 Fault number: 30521 5--44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.35 Fault number: 30522 5--46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.36 Fault number: 30523 5--47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.37 Fault number: 30524 5--49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.38 Fault number: 30526 5--50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.39 Fault number: 30527 5--52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.40 Fault number: 30528 5--53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.41 Fault number: 30529 5--55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.42 Fault number: 30530 5--56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.43 Fault number 30531 5--57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.44 Fault number 30532 5--58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.45 Fault number 30533 5--59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.46 Fault number: 30600 5--60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.47 Fault number: 30601 5--61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.48 Fault number: 30602 5--62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.49 Fault number: 30603 5--63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.50 Fault number: 30604 5--64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.51 Fault number: 30605 5--65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.52 Fault number: 30607 5--66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.53 Fault number: 30608 5--67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.54 Fault number: 30609 5--68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.55 Fault number: 30610 5--69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents
xviii
PE/DCL/DD/0032
411--9001--032
5.5.56 Fault number: 30611 5--70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.57 Fault number: 30612 5--71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.58 Fault number: 30613 5--72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.59 Fault number: 30614 5--73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.60 Fault number: 30615 5--74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.61 Fault number: 30616 5--75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.62 Fault number: 30617 5--76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.63 Fault number: 30618 5--77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.64 Fault number: 30620 5--78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.65 Fault number: 30621 5--79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.66 Fault number: 30622 5--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.67 Fault number: 30623 5--81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.68 Fault number: 30624 5--82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.69 Fault number: 30627 5--83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.70 Fault number: 31000 5--84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.71 Fault number: 31001 5--85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.72 Fault number: 31006 5--86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.73 Fault number: 31007 5--87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.74 Fault number: 31008 5--88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.75 Fault number: 31009 5--89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.76 Fault number: 31010 5--90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.77 Fault number: 31100 5--91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.78 Fault number: 31200 5--92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.79 Fault number: 31201 5--105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.80 Fault number: 31300 5--106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.81 Fault number: 31400 5--107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.82 Fault number: 31401 5--108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.83 Fault number: 31402 5--109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.84 Fault number: 31403 5--110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.85 Fault number: 31404 5--111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.86 Fault number: 31405 5--112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.87 Fault number: 31406 5--113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.88 Fault number: 31407 5--114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.89 Fault number: 31408 5--115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.90 Fault number: 31409 5--116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.91 Fault number: 31500 5--117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents Nortel Networks Confidential xix
5.5.92 Fault number: 31501 5--118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.93 Fault number: 31600 5--119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.94 Fault number: 31700 5--120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.95 Fault number: 31800 5--121 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.96 Fault number: 31801 5--122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.97 Fault numbers: 39500 and 39550 5--123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.104 Fault numbers: 39507 to 39549 and 39557 to 39599 5--137 . . . . . . . . . . . . . . .
5.6 BDA audit1 5--139 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of figures
xx
PE/DCL/DD/0032
411--9001--032
Figure 1--1 OMC-R machine state transition diagram 1--2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1--2 Command menu on server background screen 1--10 . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1--3 Command menu on background of a local or remote workstation screen 1--10 . . .
Figure 1--4 Command menu on background of X terminal screen 1--11 . . . . . . . . . . . . . . . . . . .
Figure 1--5 <Halt State>screen 1--46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1--6 UNIX login screen for launching the OMC-R application 1--46 . . . . . . . . . . . . . . . . .
Figure 1--7 Browser screen 1--47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1--8 Access to UNIX window 1--47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1--9 Cisco router configuration tool (V11) 1--67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3--1 A5XXX display unit 3--6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3--2 Example of the workstation and active server status 3--11 . . . . . . . . . . . . . . . . . . . .
Figure 3--3 Example of the passive server status 3--12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3--4 DAT drive 3--18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4--1 Flowchart of the preliminary tests 4--2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4--2 Date / time diagram 4--13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4--3 Flowchart of the A5XXX broken disk 4--20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4--4 Flowchart of the A5XXX broken function 4--22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of tables Nortel Networks Confidential xxi
Table 1--1 Details of each choice 1--7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of sheets
xxii
PE/DCL/DD/0032
411--9001--032
Preventivemaintenancefor eachOMC-Runit 3--15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 1 Cleaning the heads of the DDS tape drive 3--15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 2 Check of the DDS cartridge drive 3--17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A5XXXdiskarraydevicemaintenance 4--26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 1 Check the A5XXX display unit 4--26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 2 Analyze of the notifications 4--28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 3 rebuildmirror.sh tool 4--30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 4 repair_db.sh tool 4--31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 5 repair_A5000.sh tool for A5XXX disk array device 4--33 . . . . . . . . . . . . . . . . . . . . . .
Sheet 6 stat_db.sh tool 4--36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sheet 7 Check format </dev/null with A5XXX disk array device 4--39 . . . . . . . . . . . . . . . . . .
List of fault numbers Nortel Networks Confidential xxiii
30020 : Incorrect event received by observation management 5--3 . . . . . . . . . . . . . . . . . . . . . .
30030 : Incorrect event received by fault management 5--4 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30041 : Late bss event in queue 5--5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30052 : Purging alarms on saturation 5--6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30060 : Association management error (open or abort) 5--7 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30061 : BDA state change 5--8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30063 : Error on BSC software 5--9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30071 : Anomaly in BSC answer 5--10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30072 : Anomaly in command acknowledgement fromBSC 5--11 . . . . . . . . . . . . . . . . . . . . . . . .
30073 : Error in spontaneous BSC message 5--12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30074 : Communication problemwith a workstation 5--13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30130 : Begin of BDE save 5--14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30131 : End of BDE save 5--15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30500 : OMC-R software error on UNIX primitive invocation 5--16 . . . . . . . . . . . . . . . . . . . . . . . .
30501 : Forked process internal error 5--19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30502 : Semaphore error 5--21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30503 : Shared memory error 5--22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30504 : Memory allocation error 5--23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30505 : TLI (or socket) error 5--24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30506 : Active server swap space overflow 5--26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30507 : Internal database error 5--27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30508 : Active server database error 5--28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30509 : Backup server database error 5--29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30510 : OMC common services internal error 5--30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30511 : Chained list internal error 5--31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30512 : Delay service internal error 5--32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30513 : Coding/decoding event error 5--33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30514 : Task monitoring failure 5--35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30515 : Communication error with BSS 5--36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30516 : Active server access disk error 5--37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30517 : Active server communication error 5--39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30519 : Backup server communication error 5--40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30520 : Message service error 5--42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30521 : Application software error 5--44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30522 : Link error 5--46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30523 : Performance management internal error 5--47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of fault numbers
xxiv
PE/DCL/DD/0032
411--9001--032
30524 : Configuration management internal error 5--49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30526 : Sparc Storage Array device error 5--50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30527 : CMIS service provider error 5--52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30528 : Time function error 5--53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30529 : MDP data error 5--55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30530 : MDM service error 5--56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30531 : T3 device internal error 5--57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30532 : T3 device unreachable 5--58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30533 : error on passive server 5--59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30600 : OMC-R software error on UNIX primitive invocation counter threshold exceeded 5--60
30601 : Forked process internal error counter threshold exceeded 5--61 . . . . . . . . . . . . . . . . . .
30602 : Semaphore error counter threshold exceeded 5--62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30603 : Shared memory error counter threshold exceeded 5--63 . . . . . . . . . . . . . . . . . . . . . . . . .
30604 : Memory allocation error counter threshold exceeded 5--64 . . . . . . . . . . . . . . . . . . . . . . .
30605 : TLI (or socket) error counter threshold exceeded 5--65 . . . . . . . . . . . . . . . . . . . . . . . . . .
30607 : Internal database error counter threshold exceeded 5--66 . . . . . . . . . . . . . . . . . . . . . . . .
30608 : Active server database error counter threshold exceeded 5--67 . . . . . . . . . . . . . . . . . . .
30609 : Backup server database error counter threshold exceeded 5--68 . . . . . . . . . . . . . . . . . .
30610 : OMC common services internal error counter threshold exceeded 5--69 . . . . . . . . . . .
30611 : Chained list internal error counter threshold exceeded 5--70 . . . . . . . . . . . . . . . . . . . . . .
30612 : Delay service internal error counter threshold exceeded 5--71 . . . . . . . . . . . . . . . . . . . .
30613 : Coding/decoding event error counter threshold exceeded 5--72 . . . . . . . . . . . . . . . . . . .
30614 : Task monitoring failure counter threshold exceeded 5--73 . . . . . . . . . . . . . . . . . . . . . . . .
30615 : Communication error with BSS counter threshold exceeded 5--74 . . . . . . . . . . . . . . . . .
30616 : Active server access disk error counter threshold exceeded 5--75 . . . . . . . . . . . . . . . . .
30617 : Active server communication error counter threshold exceeded 5--76 . . . . . . . . . . . . . .
30618 : Backup server access disk error counter threshold exceeded 5--77 . . . . . . . . . . . . . . .
30620 : Message service error counter threshold exceeded 5--78 . . . . . . . . . . . . . . . . . . . . . . . .
30621 : Application software error counter threshold exceeded 5--79 . . . . . . . . . . . . . . . . . . . . .
30622 : Link error counter threshold exceeded 5--80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30623 : Performance management internal error counter threshold exceeded 5--81 . . . . . . . .
30624 : Configuration management internal error counter threshold exceeded 5--82 . . . . . . . .
30627 : CMIS service provider error counter threshold exceeded 5--83 . . . . . . . . . . . . . . . . . . .
31000 : Partition full 5--84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31001 : BSC clock drift 5--85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31006 : Shutdown requested 5--86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of fault numbers Nortel Networks Confidential xxv
31007 : Immediate shutdown 5--87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31008 : MD-R/Manager time difference has exceeded the threshold cfDtDiffThreshold 5--88 .
31009 : The MD-R server has switched over 5--89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31010 : BDE-BDA check-up 5--90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31100 : Anomalies threshold exceeded 5--91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31200 : Counter exceeding upper threshold 5--92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31201 : Counter exceeding lower threshold 5--105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31300 : Filling threshold exceeded 5--106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31400 : Message BSC number different fromlink BSC number 5--107 . . . . . . . . . . . . . . . . . . . . .
31401 : Unknown association identity 5--108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31402 : Unknown family identity 5--109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31403 : Unknown CODOP 5--110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31404 : Message of association family not expected 5--111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31405 : Processing of current spontaneous message aborted after reception of new
spontaneous message 5--112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31406 : Reception of a message on a no-etablished association 5--113 . . . . . . . . . . . . . . . . . . . .
31407 : Reception of a negative TGE acknowledgement 5--114 . . . . . . . . . . . . . . . . . . . . . . . . . . .
31408 : Renunciation of TGE sending attempts 5--115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31409 : Spontaneous message not acknowledged within agreed time by application 5--116 . . .
31500 : RGE not expected 5--117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31501 : No BSC response for association supervision 5--118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31600 : LAPB down 5--119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31700 : Several unsuccessful logins 5--120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31800 : The following counters are not available for the current BSC release 5--121 . . . . . . . . .
31801 : The request did not succeed to the following counters 5--122 . . . . . . . . . . . . . . . . . . . . . .
39500 and 39550 : Anomalies threshold exceeded 5--123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39507 to 39549 and 39557 to 39599 : Anomalies threshold exceeded 5--137 . . . . . . . . . . . . . . . . . . .
List of procedures
xxvi
PE/DCL/DD/0032
411--9001--032
Procedure 1--1
Installing OMC--R Software 1--4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 1--2
Upgrading OMC--R Software 1--5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this document Nortel Networks Confidential 0--1
ABOUT THIS DOCUMENT
This document is the preventive and corrective Maintenance Manual of an
Operations andMaintenanceCenter of Radio subsystems (OMC-R) of theGSM
Network.
Applicability
This document applies to the GSM850, GSM900, GSM1800, GSM1900,
GSM850-1900, GSM900-1800, GSM1800-1900 or GSM-R digital wireless
system.
This document applies to the V15.0 BSS system release. It describes the
maintenanceof theOMC-R.
TheBSC 2Gdoesnot support theV15.0features. OnlytheBSC e3supportsthe
V15.0features.
Thisdocumentispartof theBSSNortel NetworksTechnical Publications(NTPs).
ItiscloselyassociatedwiththeOMC-RUser Manual andtheOMC-RArchitecture
andReferenceManual.
Audience
Thisdocument isintendedfor:
theOMC-R administrators
theOMC-R maintenanceattendants
theGSM network engineers
andfor userswhowant toknowmoreabout theOMC-R
Prerequisites
Usersmust befamiliar withUNIX system, theRelational DataBaseManagement
System(RDBMS) andnetworkingprinciples.
Alsotheymust befamiliar withthefollowingNTPs:
<00> : BSSProduct DocumentationOverview
<01> : BSSOverview
<06> : OMC--R ArchitectureandReferenceManual
<07> : BSSOperatingPrinciples
<39> : BSSMaintenancePrinciples
About this document
0--2
PE/DCL/DD/0032
411--9001--032
Relateddocuments
TheNTPs listedinabovePrerequisitesparagrapharequotedinthedocument as
well asthefollowingones:
<34> : BSSOperatingprocedures
<41> : BSC MaintenanceManual
<46> : S2000/S2000E BTSMaintenanceManual
<47> : S4000BTSMaintenanceManual
<49> : S2000H/L BTSMaintenanceManual
<50> : TML (BSC/TCU) User Manual
<101> : Fault Number Description-- Volume1of 6: BSC andTCU
<102> : Fault Number Description-- Volume2of 6: S2000/S2000E and
S4000BTS
<103> : Fault Number Description-- Volume3of 6: S8000andS8002BTS
<104> : Fault Number Description-- Volume4of 6: S2000H/L and
e--cell BTS
<125> : ObservationCounter Dictionary
<128> : OMC--R User Manual -- Volume1of 3: Object andFault menus
<129> : OMC--R User Manual -- Volume2of 3: Configuration, Performance,
andMaintenancemenus
<130> : OMC--R User Manual -- Volume3of 3: Security, Administration,
SMS--CB, andHelpmenus
<131> : Fault Number Description: BSC/TCU e3
<132> : BSC/TCU e3MaintenanceManual
<143> : S12000BTSFault Numbers
241--6001--807Passport/SNMP DevicesBackupandRestoreUser Guide
Howthis documentis organized
Chapter 1: describes theOMC-R administration procedures. They concernthe
systemmanagement of the OMC-R not including the operational
applications.
Chapter 2: describes the maintenance of the OMC-R, the principles used for
defenseandsupervisionof theOMC-R.
Chapter 3: providesthepreventivemaintenanceprocedures.
Chapter 4: providesthecorrectivemaintenanceprocedures.
Chapter 5: alsoprovidesthemaintenanceproceduresassociatedwiththeOMC-R
notifications.
Refer to theindex of fault numbers to locatequickly thecorrectiveaction for a
particular notification.
About this document
0--4
PE/DCL/DD/0032
411--9001--032
Specific typographical conventions for procedures
Theconventionsdescribedhereafter onlyapplytothefollowingprocedures:
Chapter 1: OMC-R administrationprocedures
Chapter 3: OMC-R preventivemaintenanceprocedures
Chapter 4: OMC-R correctivemaintenanceprocedures
Chapter 5: ProceduresassociatedwithOMC-R notifications
General conventions
A wordinitalicstyle(italic) meansaparameter tosubstitutebyitsvalue.
To indicateonwhichmachinetheactions shouldberun, thefollowingsyntax is
used:
ONALOCAL WORKSTATION
Conditional commandsareindicatedwiththefollowingsyntax:
For all theunlockedbscMdInterfaceobjects:
{
.....
}
Interactivegraphical sessions
Thegraphical interactivecommandsaredescribedwiththefollowingsyntax:
CONVENTIONUSED MEANING
GOTO Title go to the windownamed Title
SELECT Save - OK click with the mouse on the buttons or
options named Save, then OK.
SELECT_OBJ omc select the object omc
SET State =lockedT2 =30s enter with the keyboard the values of
the parameters
CLOSE Title Quit the windownamed Title
Interactiveterminal sessions
Aninteractivesessiononaterminal canbeobtainedusingtwomethods:
choosingtheAccess t o Uni x optionof thebackgroundmenuontheserver
or thestation
openaremoteconnectiontotheserveror thestationfromashell windowonany
other machine, usingthet el net or r l ogi n command
Aninteractivesessiononaterminal (lineterminal or CommandTool window) is
describedwiththefollowingsyntax:
CONVENTIONUSED MEANING
Cour i er New All characters of a terminal session are
in Courier Newfont.
bol d The lines, commands, or parameters
entered with the keyboard are in bold
style.
i t al i c A variable output display is in italic
style. The words in italic have to be
substituted by real values.
i t al i c- bol d An input parameter which should be
substituted by its value is in italic and
bold style.
The ENTER key has to be pressed.
[Ctrl],[c] The Ctrl and c keys have to be pressed
simultaneously. Caution: A on the
Qwerty keyboard, Q on the Azerty
keyboard.
. . . . . . . . . . A group of dots replace a certain
number of lines.
A command line is truncated and
continues on the next line.
%or ( user ) % The C shell prompt
$ or ( user ) $ The Bourne and Korn shell prompt
# or ( r oot ) # The root super-user prompt in any shell
About this document
0--6
PE/DCL/DD/0032
411--9001--032
Terminal sessionsample:
Under omc l ogi n:
/ ( omc) %cd my_di r ect or y
my_di r ect or y ( omc) %l s
a. out i _am_a_shor t _f i l e_wi t h_a_r eal l y_i _mean_r eal l y_no_but _
unbel i evabl y_l ong_name
. . . . . .
t ot o. o
my_di r ect or y ( omc) %vi my_f i l e
my_di r ect or y ( omc) %
The typographic conventions of a terminal session are also used to display the
content of aUNIX file.
Sequencetablepresentation
Sequence tables list the operations to be performed during a procedure. Each
operation is described completely in the sheet referenced by its number in the
sequencetable.
Thesheetsarenot alwayspresentedintheexecutionorder. Refer tothesequence
tablestodeterminetheorder executionfor thesheets.
Eachtimeanoperationisperformed, theoperator shouldnotetheresultintheOK
or NOK column.
if theresult isOK, thenextoperationisdescribedinthefollowinglineof
thetable
if theresultisNOK,theprocedurecannotbecontinued.Thenextoperation
couldbeindicatedinthelastcolumnof thecurrentlineandiseitherafallbackora
troubleshooting step. In case of a fallback, the fallback procedure should be
startedat thespecifiedstep.
A sheetmayneedtobeexecutedatdifferentstagesof theprocedureandindifferent
contexts. Inthat case, aset of input parametersfor thesheet indicatesthecontext.
A sequencetablehasthefollowingformat:
Step Operation description Sheet no. OK or
NOK
Fall--
back
step
Input Parameters
1 Description of the operation 1
Parameter1 =value
Parameter2 =value
Parameter1 =value
Sequencetableformat
Name and value of the
file entry parameters
(optional)
Time required for the step
Sheet number
Result of the operation
filled in by the operator
Fallback step (eventual)
if the result of the
operation is NOK
mn
n1 OK F1 30
n2 OK F1 280
n4 OK F6 5
About this document
0--8
PE/DCL/DD/0032
411--9001--032
Vocabulary conventions
TheglossaryisincludedintheNTP <00>.
Graphic Conventions
Thefollowingsymbolsareusedintheflowcharts.
Start of the flowchart, showing a start point in the
formof the state of the subsystemor a fault
number.
Action to be taken by the operator.
Condition.
SafetyRegulations
Introduction
All the following steps must be taken during the various cabinet maintenance
proceduresinorder toguaranteepersonnel andequipment safety.
Account must betakenof thefollowingaspects:
general personnel safetyinstructions
equipment safetyinstructions
Precautionarymessages
Caution, anddanger messagesindicatethefollowingpossiblerisks:
CAUTION
Serviceinterruption
CAUTION
Equipmentdamage
DANGER
Personnel safetyrules
About this document
0--10
PE/DCL/DD/0032
411--9001--032
PAGE INTENTIONALLY LEFT BLANK
OMC-R administration procedures Nortel Networks Confidential 1--1
1 OMC-RADMINISTRATIONPROCEDURES
1.1 Introduction
Thischapter providesthefollowingproceduresfor administratorswhosupportan
OperationsandMaintenanceCenter of Radio(OMC-R) subsystem:
usingCentralizedInstallationandUpgradeServices(CIUS)
startinganOMC-R
shuttingdownanOMC-R
retrievinganOMC-R context (zap)
activatinganOMC-R switchover
connectinganX terminal toanOMC-R site
usingtheXyplex
usingthefloppydrive
managingprint jobs
connectinganddisconnectingaDAT drivetoaworkstation
configuringtherouter (CiscoV11)
checkingtheaccessrightsof softwarecomponents
archivingandrestoringanOMC-R agent (MD-R)
archivingandrestoringanOMC-R Manager (OMC-R)
Thefollowingproceduresof configurationarenotdescribed, call themanufacturer:
transferringOMC-R OEM equipment
transferringanOMC-R workstation
transferringanSDO
configuringanOMC-R multi-OMC
configuringanOMC-R multi-MMI display
configuringanNIS/DNS
configuringor transferringother equipment
OMC-R administration procedures
1--2
PE/DCL/DD/0032
411--9001--032
Off state
Power off
Haltstate
Power on
Shutdown UNIX
UNIX Operating state
Stop application
Start
application
Boot
Application running
Figure1--1 OMC-Rmachinestatetransitiondiagram
1.2 CentralizedInstallationandUpgradeServices
The Base Station System(BSS) software provides Centralized Installation and
UpgradeServices(CIUS) thatfacilitateandautomatemuchof theprocesstoinstall
or upgrade software on a regular OMC--R workstation. (The Centralized
InstallationandUpgradeServicesdonot runonanSDOor PCUOAM.)
An OMC--R workstation cannot run CIUS functions and OMC--R client
applicationsat thesametime. Thesystemprovidesameanstotogglebetweenthe
CIUSfunctionsandclient applications.
TheCIUSpackageincludesthefollowingcomponents:
CentralizedGraphical User Interface(GUI) Sequencer
Jumpstart service
FlashArchive
LiveUpgradeservice
Note: TheJumpstart, FlashArchive, andLiveUpgradecomponentsareall based
onSuntechnologies.
1.2.1 CentralizedGUI Sequencer
The Centralized GUI sequencer automatically runs installation and upgrade
scenariosfor aregular OMC--R worstation. Thesequencer alsocapturesessential
datafor thesescenarios. For moreinformation, seeInstallingOMC--Rsoftware
or UpgradingOMC--R software.
1.2.2 J umpstartservice
TheJumpstart component supportsremoteandautomaticinstallationof operating
system, third--party, andOMC--Rsoftware. Itreducesthetimeneededforupgrades
andinstallationandreducesmanual processerrors.TheJumpstarttool alsoprovides
anautomatedenvironment for testingandregressiontesting.
TheJumpstart servicesupportsandworkswithFlashArchivesandLiveUpgrade.
1.2.3 FlashArchive
TheCIUSfunctionsprovideaFlashArchivefor eachof thefollowing:
theOMC--R workstation(U5or SB150)
aSunSolaris8, SFV880server
A Flash Archiveis asnapshot of all softwareand files, including theoperating
system, softwarepatches, andapplications, onasystem. A FlashArchive, created
aftersoftwarehasbeeninstalledonamastersystembutbeforethatsystemhasgone
intoproduction, candramaticallyincreasethespeedof installation.
1--4
PE/DCL/DD/0032
411--9001--032
TheFlashArchiveswork inconjuctionwiththeJumpstart component.
BecauseaFlashArchivedoesnot reflect final partitioning, it supportsanymodel
of ULTRA5(4GB, 8GB, or 20GB) or SunBlade150(40+GB). A FlashArchive
for anOMC--Rworkstationisalsouseful for anSDOor PCUOAM. For SDOand
PCUOAM systems, DS--OAM tools areavailableto install softwarethat may be
missingfromtheFlashArchive.
ATTENTION
FlashArchivesonlysupport systemswithaSolaris8, SFV880server.
1.2.4 LiveUpgradeservice
TheLiveUpgradeserviceprovidesadditional enhancementstotheinstallationand
upgradeprocess. LiveUpgradeusesaboot environment (aset of filesystemsand
associatedmountpoints) ononeor moredisks. A bootenvironmentprovidesmore
flexibilitythanasingleboot disk. TheLiveUpgradeserviceprovidesacommand
lineinterfacetocreate, populate, manipulate, andactivateboot environments.
TheLiveUpgradeserviceworksinconjuctionwiththeJumpstart component.
ATTENTION
TheLiveUpdatecomponent isonlyavailablefor aSolaris8, SFV880server.
Procedure1--1
InstallingOMC--RSoftware
Toinstall softwareonanOMC--R server:
1. Use the dedicated CD--ROM and GigaTape for the system to begin the
installation.
2. UsetheGUI sequencer toobtaintheessential datafor theinstallation.
3. Runaremotepre--installationcheck oneachcomponent of theOMC--R.
ATTENTION
Defectivecomponentsmaycausetheinstallationtofail.
4. Preparetheinstallationsequence.
5. Playinstallationsequence.
6. RuntheCIUSfunctionstoinstall theOMC--R software.
7. Toggle the OMC--R workstation to disable CIUS functions and enable the
OMC--R client applications.
Procedure1--2
UpgradingOMC--RSoftware
ToupgradethesoftwareonanOMC--R server:
1. ToggletheOMC--R workstationtodisabletheclient applicationsandenable
CIUSfunctions.
2. UsethededicatedCD--ROMandGigaTapeforthesystemtobegintheupgrade.
Note: TheGUI sequencerautomaticallyobtainstheessential datafortheupgrade.
3. Runaremotepre--installationcheck oneachcomponent of theOMC--R.
ATTENTION
Defectivecomponentsmaycausetheupgradetofail.
4. Preparetheupgradesequence.
5. Playupgradesequence.
6. RuntheCIUSfunctionstoupgradetheOMC--R software.
7. Toggle the OMC--R workstation to disable CIUS functions and enable the
OMC--R client applications.
1--6
PE/DCL/DD/0032
411--9001--032
1.3 OMC-Rstart-up, shutdown, andswitchover
Theseproceduresallowtheoperator tostart-upandshutdownanOMC-R andto
switchover tothebackupserver if necessary.
In the procedure description tables, the screens corresponding to MMI
communications can be referred to in NTPs <128>to <130>. The screens
specific to start-up, shutdown, and switchover are shown at the end of this
paragraph.
TheTimeserver featureisonlysupportedonDBT GSM--Rnetwork. WithinDBT
network, onlyanOMC--RWorkstationandnot anOMC--Rserver, SDOserver, or
aPCU server fromtheOMC network.
If transfersbetweenworkstationsarelonger thannormal, contact thenext level
of support.
1.3.1 Operatingrules
Theseproceduresarefor theOMC-R administrator withaccessrightstoOMC-R
shutdown command classes and in possession of the UNIX super-user (root)
password.
DuringtheOMC-R shutdown, messagesfromthesupervisedBSSsarestoredfor
24hours(Refer toNTP <07>).
Theworkstationsandserverscanbeshutdowninanyorder.
1.3.2 OMC-Rmachineoperatingstates
Four clearly identified operating states characterize each OMC-R machine,
server(s) andworkstations:
off whenthemachineisnot powered
haltwhenthemachineispoweredandcontrolledbyamonitor thatisresident
inPROM
UNIX whentheoperatingsystemisloadedandcontrolsthemachine
A Motif backgroundscreenisdisplayedonworkstationsrunningintheUNIX
state.
applicationrunning whenthemachineisoperatingunder nominal conditions
The start-up and shutdown procedures performed on different machines are
determinedbystatetransitions.
Figure 1--1isthediagramof OMC-R machinestatetransitions.
A proceduredescribeseachstatetransitionintheremainder of theChapter.
1.3.3 Backgroundmenu
Thebackgroundmenuallowsuserstoaccessdifferent utilities.
Movethecursor out of all thewindowsopenontheterminal screenandclick the
menu mousebuttontodisplaythebackgroundmenu.
Thebackgroundmenuoptions, listedinTable1--1, aredifferent for eachof
thefollowing:
theserver console(seeFigure 1--2)
alocal or mono-OMC remoteworkstation(seeFigure 1--3)
amulti-OMC remoteworkstation
anX terminal (seeFigure 1--4)
Option Server
console
Mono-OMC
workstation
Multi-OMC
workstation
Xterminal
Refresh screen x x x x
Printing x x x x
Consult BSS documentation x x x x
Control the local application
state
x x x x
Start the local application x x x
Restart the graphic
application
x
Connect to an OMC-R x
Access to UNIX x x x x
Mount a floppy disk x x
Eject a floppy disk x x
Router Configuration (Cisco)
(V11)
x x
Utilities x x x x
Alarms Ext Bts x x x x
Table1--1 Details of eachchoice
Refreshscreen
Thisoptionresetsthestateof theterminal screen(fromanOpenWindows point
of view).
1--8
PE/DCL/DD/0032
411--9001--032
Printing
Thisoptionallowsuserstoprint atext or thecontentsof awindow.
Toprint atext, select thetext andinthePrint screenmenu, select thePrint the
selectionoption.
Nowarningmessageisissuedwhennotext isselected.
Toprint thecontentsof awindow, select thePrint awindowoptioninthePrint
screenmenu. Whenthecursor hasturnedintoacross, moveitinsidethedesired
windowandclick theselect mousebutton.
Anareaof thewindowthatisnotvisibleonthescreen(backgrounddisplay)does
not appear ontheprintout. Theprintout lookslikeasnapshot of thescreen.
ConsultBSSdocumentation
This option is used to consult on-line BSS product documentation stored on
CD-ROM andstartstheWorldViewapplication. Refer toNTP<130>.
Control thelocal applicationstate
ThisoptionisusedtodisplayinformationontheOMC-Rserversandtheterminal
wherethecommandisissuedinaspecial window.
Startthelocal application
This optionis only availableonanOMC-R server console, onalocal or remote
workstationandallowstheuser tostart theOMC applicationontheserver where
thecommandisissuedafter theapplicationhasbeenstopped.
Startthegraphicapplication
ThisoptionisonlyavailableonanX terminal andallowstheuser tostarttheOMC
applicationfortheXterminal wherethecommandisissuedaftertheapplicationhas
beenstopped.
ConnecttoanOMC-R
This option is only available on remote workstations that can be connected to
different OMC-Rsitesandallowstheuser tochoosetheOMC-Rsitetowhichthe
workstationisconnected.
Note
If this option does not appear in the background menu, check whether the
workstationhasbeendeclaredasamulti-OMC workstationinthefiles:
/ CMN/ base/ conf i g/ cf Sup_host s. cf g
/ CMN/ base/ conf i g/ omc_conf i gur e. cf g
Eachconfigurationlinecontainsthefollowingitems:
<machineNumber><machineHostName><role>[stationType]
If [stationType] equals MULTIOMC, execute the majmenu shell in the
/ home/ omc directory and choosetheMwmoptionin thebackground menuto
maketheConnect toanOMC-Roptionappear.
AccesstoUNIX
ThisoptionisusedtologintoUNIX asanyUNIX user. Afterenteringthenameand
password, theuser canaccessUNIX commandswithall theuser permissions.
Toget out of UNIX, enter thelogoutcommandor suppresstheUNIX window.
Reminder: Duringaworksession, auser canlogintoUNIX byselectingtheUnix
tool optionintheAdministrationmenuof anOMC-R Browser window.
Mountafloppydisk
This optiontells UNIX to activatethefloppy drivesincetheuser has installeda
floppydisk inthedrive.
Ejectafloppydisk
ThisoptiontellsUNIX todeactivatethefloppydrive. Thefloppydiskisphysically
ejectedfromthedrive.
Router Configuration(V11)
This optionis usedto configuretheCisco router V11(seeParagraph1.9in this
Chapter).
Utilities
Thisoptionisusedtostart MwmwhentheMotif isstopped.
AlarmsExtBts
Thisoptionisusedtochangethenamesof BTSalarms(Refer toNTP<128>).
1--10
PE/DCL/DD/0032
411--9001--032
Refresh screen
Printing...
Consult BSS documentation
Control the local application state
Start the local application
Alarms Ext Bts
Access to UNIX
Router Configuration
Utilities ...
Figure1--2 Commandmenuonserver backgroundscreen
Refresh screen
Printing...
Alarms Ext Bts
Start the local application
Access to UNIX
Mount a floppy disk
Eject a floppy disk
Utilities...
Figure1--3 Commandmenuonbackgroundof alocal or remote
workstationscreen
Refresh screen
Printing...
Alarms Ext Bts
Start the graphic application
Access to UNIX
Utilities...
Figure1--4 Commandmenuonbackgroundof Xterminal screen
1.3.4 StartinganOMC-R
1.3.4.1 General rules
Thestart-upfunctionperformsasetof operationstoestablishtherunningmodeof
eachOMC configurationmachine.
Accordingtotheinstallationconfiguration:
start-upisautomaticallyexecutedwhenthemachineispowered-upor rebooted
start-up is activated by selecting the appropriate itemfromthe background
screenmenu
Thestart-upfunctionfirstchecksthatanOMC-Rapplication(mediationfunction,
manager function, or workstation) isnot alreadyrunningonthemachine.
It synchronizes the various machines. This synchronization is necessary for
consistencybetweenthemachineroleandtheroleof other accessiblemachines.
Thefollowingsectionsdescribethestart-upproceduresfor eachmachine.
1--12
PE/DCL/DD/0032
411--9001--032
1.3.4.2 List of start-up procedures
Thefollowingproceduresforstarting-upanOMC-Rmachine(server/workstation)
aredescribedinthissection:
power-upof alocal workstation
start-upof theOMC-R application(workstationor STATSDO)
boot-upof alocal workstation
power-upof theserver (UltraEnterprise45XX or FireV880) insingle-server
configuration
power-upof thepassiveserver(UltraEnterprise45XX / 4XXX orFireV880) in
dual-server configuration
power-upof theactiveserver (UltraEnterprise45XX / 4XXX or FireV880) in
start-upof theapplicationonaserver(UNIXstate)insingle-serverconfiguration
start-upof theapplicationonaserver (UNIX state) indual-server configuration
power-upof anX terminal
start-upof theapplicationonanX terminal
switchover of amulti-OMC-R workstation
1.3.4.3 Power-up of a local workstation
Introduction
Thisproceduredescribesthepower-upof alocal workstation.
Prerequisites
Theworkstationmust beconnectedtotheOMC-R Local AreaNetwork.
Initial state
Theworkstationispowered-down.
Actions
1. Set theON/OFF switchtoON
Test messages.
2. TheSolarisscreenisdisplayed.
3. TheMotif screenisdisplayed.
4. TheOMC-R Browser windowisdisplayed(seeFigure 1--7).
5. Processingcarriedout:
start-upof UNIX operatingsystem
runningof theclient part of theOMC application
Final state
TheOMC-R applicationisrunningonthelocal workstation.
1--14
PE/DCL/DD/0032
411--9001--032
1.3.4.4 Start-up of the OMC-R application (workstation or STATSDO)
Introduction
This procedure describes the start-up of the OMC-R application on a powered
workstation. ItallowstheOMC-Rapplicationtoberunfromthebackgroundscreen
(timerequired: approximately4minutes).
Prerequisites
Initial state
TheworkstationisinUNIX runningstate.
Actions
1. Movethemousepointer onto the background screen and press theMENU
(right) buttonof themouse.
TheCommands menuisdisplayed(seeFigure 1--3).
2. Select theStart thelocal application optionwiththeSELECT (left) button
of themouse.
Thisphaseallowstheclient part of theOMC-R applicationtoberun.
3. A confirmationmessageisdisplayed:
Areyousureyouwant torestart thelocal application[y/n]?
Your choice:
4. Confirmthecommand.
Y
5. Theconfirmationwindowdisappears.
6. TheOMC-R browser windowisdisplayed(seeFigure 1--7).
Final state
TheOMC-R applicationisrunningonthelocal workstation.
1.3.4.5 Boot-up of a local workstation
Introduction
ThisprocedureallowstheOMC applicationtoberunfromthehalt state.
Prerequisites
Initial state
TheWorkstationisinhalt state.
Actions
1. RuntheUNIX operatingsystemandthentheOMC-R application:
boot
2. Test messagesaredisplayed.
3. TheSolarisscreenisdisplayed.
4. TheMotif screenisdisplayed.
Final state
TheOMC-R applicationisrunningontheworkstation.
1--16
PE/DCL/DD/0032
411--9001--032
1.3.4.6 Power-up of the server E45XX or SFV880 in single-server configuration
Introduction
Thisproceduredescribeshowtopower uptheserver E45XX or SFV880.
Prerequisites
Theserver must beconnectedtotheOMC-R Local AreaNetwork.
Theserver must beconnectedtooneA5XXX or T3.
Initial state
Theserver isswitchedoff.
Thedisk arraydeviceA5XXX or T3isswitchedoff.
Actions
1. Check that theON/OFF switchof thepassiveserver isset toOFF (CPU and
screen).
2. Set thekeyof theserver toOFF.
3. Power upthedisk arraydeviceA5XXX or T3.
4. Power uptheserver:
This step enables theUNIX operating systemto bebooted and thepassive
server tobebooted.
4.1 Power upthegraphicscreenconnectedtotheserver.
4.2 Power uptheserver byusingtheswitchontherear panel.
4.3 Set thekeyonthefront panel of theserver tolocked.
This means thesystemis running in securemodeand will not respondto
commandsinmodeOBP fromtheconsole.
TheUNIX workingenvironment appears.
Amessageisdisplayedinthewindowof theconsoleindicatingthattheserver
isstartingup.
Final state
TheOMC-R applicationisrunningontheserver.
1.3.4.7 Power-up of the passive server (E45XX or E4XXX) in dual-server configuration
Introduction
Thisproceduredescribeshowtopower upthepassiveserver (E45XX or E4XXX).
Prerequisites
Theactiveserver andpassiveserver mustbeconnectedtotheOMC-RLocal Area
Network.
Theactiveserver andpassiveserver must beconnectedtooneA5XXX or T3.
Initial state
Thepassiveserver andactiveserver areswitchedoff.
OneA5XXX or T3isswitchedoff.
Actions
1. Check that theON/OFF switchof thepassiveserver isset toOFF (CPU and
screen).
3. Power uponeA5XXX or T3.
This step enables theUNIX operating systemto bebooted and thepassive
server tobebooted.
4.1 Power upthegraphicscreenconnectedtothepassiveserver.
4.2 Power uptheserver byusingtheswitchontherear panel.
isstartingup.
Final state
TheOMC-R applicationisrunningonthepassiveserver.
1--18
PE/DCL/DD/0032
411--9001--032
1.3.4.8 Power-up of the active server (E45XX or E4XXX) in dual-server configuration
Introduction
Thisproceduredescribeshowtopower uptheactiveserver.
Prerequisites
The active server and passive server are connected to the OMC-R Local Area
Network.
Theactiveserver andpassiveserver areconnectedtooneA5XXX or T3.
Initial state
Thepassiveserver isbootedupandtheactiveserver isswitchedoff.
Actions
1. Check that theON/OFF switchof theactiveserver is set to OFF (CPU and
screen).
ThisstepenablestheUNIXoperatingsystemtobebootedandtheactiveserver
tobebooted.
3.1 Power-upof thegraphicscreenconnectedtotheactiveserver.
3.2 Power-upof theserver byusingtheswitchontherear panel.
isstarting-up.
Final state
TheOMC-R applicationisrunningontheactiveserver.
1.3.4.9 Start-up of the OMC-R application on a server (UNIX state) in single-server
configuration
Introduction
Thisproceduredescribeshowtostart-uptheOMC-R applicationonaserver.
Prerequisites
Theserver isconnectedtotheOMC-R Local AreaNetwork.
Initial state
Theserver isinUNIX running state.
Actions
2. Select theStart thelocal application option withtheSELECT (left) button
of themouse.
Thisstepenablestheclient part of theOMC-R applicationtoberun.
A standbymessageisdisplayed.
Areyousureyouwant torestart thelocal application[y/n] ?
Your choice:
Y
5. TheOMC-R applicationisrunning.
Control theOMC-R applicationstate(seeParagraph3.2.2.8).
Final state
TheOMC-R applicationisrunningonserver.
1--20
PE/DCL/DD/0032
411--9001--032
1.3.4.10 Start-up of the OMC-R application on one server (UNIX state) in dual-server
configuration
Introduction
Thisproceduredescribeshowtostart-uptheOMC-Rapplicationonaserver. The
procedurecanberunononeof thetwo servers(passivethenactive, if necessary
twiceoperations1to6).
Prerequisites
The main server and backup server are connected to the OMC-R Local Area
Network.
Initial state
Themainserver andbackupserver areinUNIX running state.
Actions
2. Select theStart thelocal application option withtheSELECT (left) button
of themouse.
Thisstepenablestheclient part of theOMC-R applicationtoberun.
A standbymessageisdisplayed.
Areyousureyouwant torestart thelocal application[y/n] ?
Your choice:
Y
5. TheOMC-R applicationisrunning.
Dependingontheinitial conditions(main or backup declaration, stateof
theother server), theserver will bootupaccordingtothedecisiontreeshown
inNTP <06>.
6. Control theOMC-R applicationstate(seeParagraph3.2.2.8).
Final state
TheOMC-R applicationisrunningononeor twoservers.
WhentheOMC-R restart sequenceiscomplete, theuser must cancel thelossof
mirroring detectionalarm, if present. Otherwise, theuser will not receivefurther
alarmsif themirroringfunctionislost at alater time.
1.3.4.11 Powering up of an X terminal
Introduction
Thisproceduredescribeshowtopower upanX terminal. Itisapplicabletoalocal
or remoteX terminal. It specifies thevarious operations carried out during this
powering-upoperation
Prerequisites
TheX terminal is connectedto theOMC-R Local AreaNetwork or to aremote
network that isassignedtoanX terminal server.
Initial state
TheX terminal isswitchedoff.
Actions
1. Set theON/OFF switchof theX terminal toON.
This step enables the UNIX operating system to be started-up on the
X terminal.
2. TheAccesstoUNIX windowisdisplayed(seeFigure 1--8).
3. RunMotif ontheX terminal:
Login: omc, password
4. Checkthatthebackgroundscreenmenuisavailable: Call uptheCommands
menu. Move the mouse pointer onto the background screen and press the
MENU buttonof themouse.
5. TheCommands menuisdisplayed(seeFigure 1--4).
6. ReturntotheMotif backgroundscreen: wait someseconds.
Final state
TheX terminal isrunning.
1--22
PE/DCL/DD/0032
411--9001--032
1.3.4.12 Start-up of the application on an X terminal
Introduction
Thisproceduredescribesthestart-upof theOMC-Rapplicationonalocal orremote
X terminal.
Prerequisites
network. X terminal is assignedto an X terminal server and to aMMI graphics
server.
Initial state
Thebackgroundscreenisavailable.
Actions
buttonof themouse.
2. TheCommands menuisdisplayed.
3. Select theStart thegraphical application optionwiththeSELECT button
of themouse.
Thisactionenablestheclient part of theOMC applicationtoberestarted.
4. Confirmationrequested: Thefollowingmessageisdisplayed:
Areyousureyouwant torestart thegraphical application[y/n]?
Your choice:
Y
5. Theconfirmationwindowdisappears.
6. Standbymessagesaredisplayed.
Final state
TheOMC-R applicationisrunningontheX terminal.
1.3.4.13 Switchover of a multi-OMC-R workstation
Introduction
This procedure allows users to switch fromone OMC-R application to another
OMC-R application.
Prerequisites
The workstation must be connected to the OMC-R Local Area Network. The
OMC-R applicationmust berunning.
Initial state
Thebackgroundscreenisavailable.
Actions
1. Shut downtheMMI application.
1.1 Select theOMC-R object:
GOTO OMC-R Browser
SELECT_OBJ OMC-R
1.2 Shut downtheOMC-R application:
GOTO OMC-R Browser
SELECT Configuration- omc - Shut down
Thefollowingmessageisdisplayed: TheOMC-R iscompletelystopped.
2. Select theoptionConnect toanOMC-R fromthebackgroundmenu.
3. Select therequestedOMC-R.
Theworkstationrestarts.
Final state
A newOMC-R applicationisworkingontheworkstation.
1--24
PE/DCL/DD/0032
411--9001--032
1.3.5 ShuttingdowntheOMC--R
1.3.5.1 General rules
Several user commandsshutdownall or part of theOMC-R system:
acommandtoshut downtheOMC-R applicationsontheusersmachine
acommandtoshutdowntheOMC-Rapplicationsontheactiveserverandonthe
backupserver
acommandtoshut downtheOMC-R applicationsontheentiresystem(server
andworkstations). Themulti-OMCworkstationsconnectedtothisserverwill be
shutdown
Theabovecommands causeasoft shutdownof theOMC-R. Any process that is
runningandmust not beinterruptedpreventsthesystemfromshuttingdown. The
user isinformedthat theshutdownisbeingdelayed. After aconfigurablestandby
threshold, if aprocesscannot beinterrupted, theshutdownisabrutal shutdown.
TheOMC-R systemcanalsobeshut downasfollows:
onadefenseaction
onacritical anomalyduringthestart-upsequence
fromthebackgroundscreenmenu
Intheabovecases, theOMC-R shutdownisabrutal shutdown. Theexecutionof
acommandinprogressisnot guaranteed. TheOMC-R systemcanbeshut down
withMMI it issoft shutdown.
OMC--RBrowser windowonOMC level
omc object
Shutworkstationdown Shutserver down
Shutdown
(all machines stop)
(active server stops) (workstation stops)
TheOMC-R shutdownprocedureconsistsof:
sending a shutdown message to all OMC-R applications that are currently
running (manager function, workstation, or mediation function). These
functions must acknowledge the message and carry out their own shutdown
procedure
shuttingdownall theaboveapplicationsif theyarenot completed
shuttingdownSybase
After ashutdown, themachinedisplaystheUNIX promptandnoOMCapplication
isrunning. TheOMC systemcanbereset if necessary.
1.3.5.2 List of shutdown procedures
The following procedures for shutdown of an OMC-R machine
(server/workstation) aredescribedinthissection:
Stationor STATSDOapplicationshutdown
UNIX workstationshutdown
Poweringdownaworkstation
Applicationshutdownof oneserver fromalocal workstationinsingle-server
configuration
Application shutdown of two servers fromalocal workstation indual-server
configuration
Applicationshutdownfromserversinsingle-server configuration
Applicationshutdownfromserversindual-server configuration
UNIX server shutdowninsingle-server configuration
UNIX server shutdownindual-server configuration
Power-downof aserver (UltraEnterprise45XX or FireV880) insingle-server
configuration
Power-down of a server (Ultra Enterprise 45XX/4XXX or Fire V880) in
Shutdownof theapplicationsoftwareonanX terminal
Power-downof anX terminal
1--26
PE/DCL/DD/0032
411--9001--032
1.3.5.3 Station or STATSDO application shutdown
Introduction
This procedure describes the shutdown of an application on a local or remote
workstation.
Prerequisites
ThestationisconnectedtotheOMC-RLocal AreaNetworkortoaremotenetwork.
Initial state
TheOMC-R applicationisoperational ontheworkstation.
Actions
1. Select theOMC-R object:
GOTO OMC-R Browser
SELECT_OBJ OMC-R
2. Shut downtheOMC-R application:
GOTO OMC-R Browser
SELECT Configuration-- omc -- Shut workstationdown
3. OMC-R applicationsoftwareisshut downontheworkstation.
Final state
TheworkstationisintheUNIX operation status.
1.3.5.4 UNIX workstation shutdown
Introduction
Thisproceduredescribestheshutdownof UNIX onalocal or remoteworkstation.
Prerequisites
Theworkstationis connectedtotheOMC-R Local AreaNetwork or to aremote
network.
Initial state
TheworkstationisinUNIX running state. Theapplicationhasbeenshut down.
Actions
1. OpentheAccesstoUNIX window(seeFigure 1--8).
2. IntheAccesstoUNIX window:
croot, password
3. Flashupdateof theharddisk:
sync
4. UNIX shutdown:
init0
TheUNIX operatingsystemisshut down; theworkstationisinhalt state.
5. The<Halt state>screenisdisplayed(seeFigure 1--5).
Final state
Theworkstationisinhalt state.
1--28
PE/DCL/DD/0032
411--9001--032
1.3.5.5 Powering down a workstation
Introduction
Thisproceduredescribesthepowering-downof alocal or remoteworkstation.
Prerequisites
Theworkstationis connectedtotheOMC-R Local AreaNetwork or to aremote
network.
Initial state
Stationinhalt state.
Actions
Set theON/OFF switchtoOFF.
Final state
Theworkstationispowereddown.
1.3.5.6 Application shutdown of one server froma local workstation in single-server
configuration
Introduction
Thisproceduredescribestheshutdownof oneserver fromalocal workstation.
Prerequisites
Theserver isoperational: (OMC-R applicationsoftwarerunning).
TheManMachineInterfaceisavailableononeworkstation.
Initial state
Activeserver isinapplicationrunningstate.
Actions
GOTO OMC-R Browser
SELECT_OBJ OMC-R
2. ShutdowntheOMC-R application:
GOTO OMC-R Browser
SELECT Configuration-- omc -- Shut server down
Final state
Theserver isintheUNIX operation status.
1--30
PE/DCL/DD/0032
411--9001--032
1.3.5.7 Application shutdown froma local workstation in dual-server configuration
Introduction
Thisproceduredescribestheshutdownof twoserversfromalocal workstation.
Prerequisites
Theactiveserver andpassiveserver areoperational, OMC-Rapplicationsoftware
is running on both servers. The Man Machine Interface is available on one
workstation.
Initial state
Activeserverisinapplicationrunningstate. Passiveservermonitoringtheactive
server.
Actions
GOTO OMC-R Browser
SELECT_OBJ OMC-R
2. ShutdowntheOMC-R application:
GOTO OMC-R Browser
SELECT Configuration-- omc -- Shut server down
Final state
ThetwoserversareintheUNIX operation status.
1.3.5.8 Application shutdown fromservers in single-server configuration
Introduction
This proceduredescribes theshutdownof theOMC-R applicationfromaserver.
It isapplicableinthecasewheretheMMI isnot available.
Prerequisites
Theserver isoperational. OMC-R applicationisrunningontheserver.
Initial state
Theserver isinapplicationrunningstate.
Actions
Ontheserver:
1. OpentheAccesstoUNIX window(seeFigure 1--6)
2. IntheAccesstoUNIX window, loginasanomc user:
omc, password
3. Applicationshutdown:
appstop
Final state
Theserver isintheUNIX running state.
1--32
PE/DCL/DD/0032
411--9001--032
1.3.5.9 Application shutdown fromservers in dual-server configuration
Introduction
This proceduredescribestheshutdownof theOMC-R applicationfromaserver,
thatistheshutdownof theapplicationontheactiveserverandonthebackupserver.
It isapplicableinthecasewheretheMMI isnot available.
Prerequisites
Mainserver andbackupserver areoperational, OMC-R applicationisrunningon
bothservers.
Initial state
Mainserver isinapplicationrunningstate. Backupserver monitoringtheactive
server.
Actions
Ononeof theservers:
1. OpentheAccesstoUNIX window(seeFigure 1--6)
2. IntheAccesstoUNIX window, loginasanomc user:
omc, password
3. Applicationshutdown:
appstop
Final state
BothserversareintheUNIX running state.
1.3.5.10 UNIX Server shutdown in single-server configuration
Introduction
Thisproceduredescribestheshutdownof theUNIX operatingsystemonaserver.
Prerequisites
Theserver isoperational, OMC-R applicationisrunningontheserver.
Initial state
Theserver isinUNIX running state.
Actions
croot, password
sync
4. ShutdowntheUNIX operatingsystemandput theserver inhalt state:
init0
Final state
Theserver isinhalt state.
1--34
PE/DCL/DD/0032
411--9001--032
1.3.5.11 UNIX Server shutdown in dual-server configuration
Introduction
Thisproceduredescribestheshutdownof theUNIX operatingsystemonaserver.
Prerequisites
Mainserver andbackupserver areoperational, OMC-Rapplicationisrunningon
bothservers.
Initial state
Mainserver andbackupserver areinUNIX running state.
Actions
croot, password
sync
4. ShutdowntheUNIX operatingsystemandput theserver inhalt state:
init0
Final state
1.3.5.12 Power-down of a server (Ultra Enterprise E45XX or Fire V880) in single-server
configuration
Introduction
Thisproceduredescribesthepower-downof anUltraEnterprise45XX server or a
FireV880server .
Prerequisites
Theserver isconnectedtotheOMC-R Local AreaNetwork.
Initial state
Actions
1. Set theON/OFF switchtoOFF.
2. Set thekeytoOFF.
3. Shut downoneA5XXX or T3(if theyarestill powered-up).
Set theON/OFF switchondisk arraydeviceA5XXX or T3toOFF.
Final state
Theserver anddisk arraydevicearepowereddown.
1--36
PE/DCL/DD/0032
411--9001--032
1.3.5.13 Power-down of a server (Ultra Enterprise 45XX/E4XXX or Fire V880) in dual-server
configuration
Introduction
This procedure describes the power-down of an Ultra Enterprise
45XX/4XXX server or aFireV880server.
Prerequisites
The active server and passive server are connected to the OMC-R Local Area
Network.
Initial state
Theactiveserver andpassiveserver areinhalt state.
Actions
1. Set theON/OFF switchtoOFF.
2. Set thekeytoOFF.
3. ShutdowntheA5XXX or T3diskarraydevice(if theyarestill powered-up).
Set theON/OFF switchonA5XXX or T3disk arraydevicetoOFF.
Final state
Theserver anddisk arraydevicearepowereddown.
1.3.5.14 X terminal application shutdown in dual-server configuration
Introduction
Thisproceduredescribestheshutdownof theapplicationonanXterminal. All tasks
present ontheX terminal areinterrupted.
Prerequisites
network andassignedtoanX terminal server.
Initial state
Mainserver isinapplicationstate. Backgroundserver monitoringtheactiveserver.
Actions
buttonof themouse.
2. TheCommands menuisdisplayed.
3. Select theClose optionwiththeSELECT buttonof themouse.
Thisallowstheapplicationtobeshut downontheX terminal.
4. Request for confirmation.
Thefollowingmessageisdisplayed: Areyouabsolutelysureyouwanttostop
thisapplication?: y/n
5. Answer Y
Final state
TheapplicationisshutdownontheX terminal.
1--38
PE/DCL/DD/0032
411--9001--032
1.3.5.15 Powering down an X terminal
Introduction
Thisproceduredescribesthepowering-downof alocal or remoteX terminal.
Prerequisites
network.
Initial state
TheX terminal isinhalt state.
Actions
Set theON/OFF switchof theX terminal toOFF.
Final state
TheX terminal ispowereddown.
1.3.6 RetrievingtheOMC-Rcontext
CAUTION
Do notlaunchthezap.shtool beforethebackupof thefiles.
1.3.6.1 Introduction
This proceduredescribes thezap.shtool, whichallows users to retrieveOMC-R
context (diagnosisfiles, session, notifications) andnoticeableevents(Sybaseand
application) intheevent of aserver problem.
Thezap.shtool isavailablewiththeOMC-R application.
Thezap.shtool alsocompressesandsavesthecorefiles.
1.3.6.2 Prerequisite
Thezap.shtool must beinstalledwithzap.cfgconfigurationfile.
1.3.6.3 Initial state
An OMC-R server problem(switchover, brutal shutdown, reboot, corefile) has
occurred.
1.3.6.4 Backup ZAP files
Enter thefollowingcommandsfor saveonDAT:
. . . ( r oot ) # cd / home/ omc/ zap
. . . ( r oot ) # tar cvf / dev/ rmt/ 0
zap_<host name>_<YYYYMMDD>_<hhmm>.
*

Enter thefollowingcommandfor displaythefilelist ontheDAT:
. . . ( r oot ) # tar tvf / dev/ rmt/ 0
zap_<hostname>_<YYYYMMDD>_<hhmm>. *
Under r oot l ogi n:
. . . ( r oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
1.3.6.5 Further Actions
Executethezap.shtool onthesamedayandassoonaspossibleafter theoccurrence
of aserver problem, havingfirst backedupthelast files.
1--40
PE/DCL/DD/0032
411--9001--032
Sendtheresult filestothemanufacturer bye-mail, onaDAT, or onafloppydisk
for analysis.
Executionof zap.sh
OpentheAccesstoUNIX window
Loginasaomc or root user:
login, password
Execute:
. . . ( omc) %cd / CMN/ base/ tool s/ shel l
. . . ( omc) %zap. sh
or
. . . ( r oot ) # cd / CMN/ base/ tool s/ shel l
. . . ( r oot ) # zap. sh
Logout of root, if necessary.
. . . ( r oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
Without option, thetool executeonthelocal machine.
With-aoption:
fromaserver: thetool isexecutedoneachmachineof theconfiguration
fromastation: thetool isexecutedonserversandthisstation
Enter -hFULL optionfor moreinformation.
Resultfiles
Thetool generates aresult filein HOME directory of omc user for example
/home/omc/zap:
zap_<hostname>_<YYYYMMDD>_<hhmm>.tar
andafile:
zap_<hostname>_<YYYYMMDD>_<hhmm>.log
Withhostnametheserver nameandYYYYMMDD, hhmmrepresentingrespectively
theyear, thedateandthetimeof execution.
Retrievethesefilesandsendthemtothemanufacturer.
1.3.6.6 Final state
Nostatechange.
A. Appendices
A1. Manual execution of get_core.sh
Thistool canbeexecutedindependentlytosearchandretrievethecompressedcore
files.
Thesyntaxisget_core.shhostname/directory.
hostnameisgivenastheshell canbeexecutedonaremotemachineand/directory
isthedirectoryof theresult files(tmpfor example).
A2. Manual execution of pow.sh
Inthesameway, thetool pow.shcanbeexecutedtoappreciatethestateof amachine.
This tool searches the core files (to retrieve them, use zap.sh or get_core.sh),
analysesthediagnosisfiles, indicatestherestartingcauses.
Thesyntaxispow.sh[hostname] wherehostnameisanoptional parameter which
canbegivenfor executiononaremotemachine.
1--42
PE/DCL/DD/0032
411--9001--032
1.3.7 ActivatinganOMC--Rswitchover indual-server configuration
A switchover canbe:
anautomaticswitchover, inother wordsaprotectionaction
amanual switchover triggeredbyanOMC switchover command
aMMI switchover
Listof switchover procedures
Theproceduresare:
switch back to dual-server operation (Ultra Enterprise 45XX/4XXX or Fire
V880)
manual switchover (UNIX - UltraEnterprise45XX/4XXX or FireV880)
manual switchover (MMI - UltraEnterprise45XX/4XXX or FireV880)
1.3.7.1 Switch back to dual server operation (Ultra Enterprise 45XX / 4XXX or Fire V880)
Introduction
This procedure describes the switch back to dual server operation for an Ultra
Enterprise45XX or 4XXX configurationor aFireV880H/Wconfiguration.
Prerequisites
Ultra Enterprise 45XX/4XXX or Fire V880 dual server configuration with one
A5XXX or T3.
Initial state
Server no. 1isactiveandserver no. 2ispassive.
Actions
Onserver no. 2, whichhasjust becomeactive:
1. Applicationshutdown
1.1 Select theOMC-R object:
GOTO OMC-R Browser
SELECT_OBJ OMC-R
1.2 ShutdowntheOMC-R application:
GOTO OMC-R Browser
SELECT Configuration-- omc -- Shut down
Thefollowingmessageisdisplayed:
TheOMC-R applicationiscompletelystopped.
2. Ontheserver whichhasitsdatauptodate(server no. 2, inthiscase):
Notes:
Whenthemajsecourscommandisinitiated, noother UNIX windows must be
openonthebackupserver.
Afterrunningthemajsecourscommand, itisnecessarytorepeatthecommandif
anexecutionerror occurs.
asanomcuser
cd/CMN/base/shell
cf_majsecours.sh<hostname_out-of-date-server>
example:
cf_majsecours.shserv1
Thisactionupdatesthedataonserver serv1.
3. Restart the passive server by using the background screen menu.
(see Figure 1--2).
4. Restart themainserver byusingthebackgroundscreenmenu.
5. TheUNIX workingenvironment appears.
6. Messagesappear indicatingthat theserversarestartingup.
Final state
Thedual server configurationisrunningoneachmachine.
1--44
PE/DCL/DD/0032
411--9001--032
1.3.7.2 Manual switchover (UNIX - Ultra Enterprise 45XX or 4XXX)
Introduction
Thisproceduredescribesthemanual switchover fromashell. Therequiredaction
istoshutdowntheactiveserver no. 1andtoswitchserver no. 2toactivemode.
Prerequisites
UltraEnterprise45XX / 4XXX or FireV880dual server configuration.
Initial state
Actions
AsanOMCuser, performthefollowingcommandonserver no. 1, whichhasjust
becomepassive:
Switchfromserver no. 1toserver no. 2
cd/CMN/base/shell
cf_bas_man.sh
Theapplicationsoftwareshuts downon server no. 1, whichswitches to UNIX
operation.
Server no. 2restartsinactivemode.
Final state
Theactiveserver switchestoUNIX andthepassiveserver becomesactive.
1.3.7.3 Manual switchover (MMI - Ultra Enterprise 45XX or 4XXX)
Introduction
Thisproceduredescribesthemanual switchoverfromtheMMI.Therequiredaction
istoshutdowntheactiveserver no. 1andtoswitchserver no. 2toactivemode.
Prerequisites
UltraEnterprise45XX / 4XXX or FireV880dual server configuration.
Initial state
Actions
OnanOMC workstation:
1. Logonasadministrator user.
2. Select theMD-R object
GOTO OMC-R Browser
SELECT_OBJ MD-R
3. Switchover
GOTO OMC-R Browser
SELECT Configuration- md- Switchover
MovetotheAction window
SpecifythevaluemdHost =managerServer
Select theApply button
4. Server no. 2restartsinactivemode.
Final state
Themainserver switchestoUNIX andthebackupserver becomesactive.
1--46
PE/DCL/DD/0032
411--9001--032
Ok
Figure1--5 <HaltState>screen
please wait...
<machine name> login:
Figure1--6 UNIXloginscreenfor launchingtheOMC-Rapplication
Figure1--7 Browser screen
Unix Terminal
login: root
password:
#
Figure1--8 Access toUNIXwindow
1--48
PE/DCL/DD/0032
411--9001--032
1.4 Connectionof anXTerminal toanOMC-Rsite
1.4.1 ConnectinganXterminal inastandardconfiguration
Thisproceduredescribestheconnectionof anX terminal toanOMC-R sitefor a
standard configuration: the workstation is an MMI graphics server and an
X terminal server.
1.4.1.2 Prerequisites
TheX terminal isconnectedtotheOMC-R Local AreaNetwork.
TheX terminal isswitchedoff.
1.4.1.4 Actions
1. Power uptheX terminal.
2. Inthewindowthat displaystheUNIX loginmessage, logonusingtheomc
username and select the Start the graphic application option of the
backgroundscreen.
Single-session X terminal
3. ShutdowntheapplicationontheX terminal.
Select the Exit OMC-R option from the Objects menu of the OMC-R
navigationwindow.
OncetheMMI applicationhasbeenshutdown(andtheUNIX loginmessage
isdisplayedagainst awhitebackground), initiatethefollowingactions.
4. SelecttheConnecttoanOMC-Roptionfromthebackgroundscreenmenu.
Enter the reference of the OMC-R site to which the X terminal is to be
connected.
TheOMC-R MMI applicationis restartedautomatically for theX terminal.
Oncethestart-upprocedurehasbeencompleted, theterminal isoperational on
theselectedOMC-R site.
Multi-session X terminal
5. SelecttheConnecttoanOMC-Roptionfromthebackgroundscreenmenu.
Fill in the reference of the OMC-R site to which the X terminal is to be
connected.
TheOMC-R MMI applicationis restartedautomatically for theX terminal.
Oncethestart-upprocedurehasbeencompleted, theterminal isoperational on
theselectedOMC-R site.
1.4.1.5 Final state
TheMMI applicationisstartedontheX terminal.
1--50
PE/DCL/DD/0032
411--9001--032
1.4.2 Connectionof anXterminal (Xterminal server outsideOMC-R)
Thisproceduredescribestheimplementationof theOMC-RMMI graphicsserver,
andassumesthat theX terminal server iscorrectlyconfigured.
TheX terminal isconnectedtotheOMC-R Local AreaNetwork.
TheX terminal isconfigured.
1.4.2.4 Actions
1. Declare the OMC-R workstation concerned as the OMC-R MMI graphics
server.
Inthe/CMN/base/config/cfSup_hosts.cgf file, theconfigurationlinesfor the
workstationandtheserver must beasfollows:
<machineNumber><machineHostName><role>[stationType]
with<role>: STATX
2. Openasessionfromyourterminal XoryourunspecifiedstationontheSTATX.
Redirect thedisplayonyour screen. Type:
cendrillon:/OMC/base/shell <46>(omc)%SETENVDISPLAY IP@:0.0
IP@: IP addressof theterminal X or theunspecifiedstation
Launchtheshell
cendrillon:/OMC/base/shell <46>(omc)%MmiRunGraphic.shcendrillon
wherecendrillonisdefinedasanomcoreserv(SFV880) or StatX
A windowisopenedwiththeallocatedtaskreferenceandinafewsecondsthe
remoteMMI isdisplayedonyour terminal xor onyour unspecifiedstation.
UsethemenuoptionObjects/ExitOMC--Rof MMI tocorrectlyendtheremote
MMI session.
3. ExecutethepsgMmiG commandtolaunchontheOMCRCORESERV or
onSTATX toverifytheMmi taskreferenceallocatedfor thisnewMMI open.
For example:
cendr i l l on: / OMC/ base/ shel l <46>( omc) %psg Mmi G
omc 13678 1 0 13: 45: 10 pt s/ 27 0: 53 / OMC/ exe/ Mmi Gr apahi c. x 462
/ t mp/ di agsuppor t 465 0-
Mcur r ent - T0470 - di spl ay 47. 16
1.4.2.5 Final state
TheMMI applicationisstartedontheX terminal.
1--52
PE/DCL/DD/0032
411--9001--032
1.5 UsingtheXyplexandconfigurationdisplay
ThefollowingtwoXyplexproceduresaredescribedbelow:
connectingtothelocal OMC-R Ethernet network
configurationdisplay
For adetaileddescriptionof theXyplex, seetheNTP <06>.
1.5.1 Connectingto thelocal OMC-REthernetnetwork
This proceduredescribes howto connect to thelocal OMC-R Ethernet network.
ThisprocedureappliestotheXyplex1620.
TheXyplex must beconnected to adistributionpanel equippedwith 20female
SUB-D, 25-pinconnectorswiredasDTE.
TheXyplexisswitchedoff.
1.5.1.4 Actions
TheXyplex1620canbeconnectedtotheEthernet network byusingeither
atransceiver connectedtotheXyplex viaadowncableconnectedontheAUI
plugof theXyplex
or
ahubbyatwistedpair connectedontheRJ45plugof theXyplex.
TheseconnectionsaredescribedinNTP <06>
1.5.1.5 Final state
A connectiontotheOMC-R Ethernet network isestablished.
1.5.2 Configurationdisplay
Thisproceduredescribeshowtodisplaytheconfiguration.
TheXyplexisconnectedtotheEthernet network.
TheXyplexandtheserver arepowered-on.
1.5.2.4 Actions
1. Open an Access to UNIX windowby thebackground screenmenu, ona
workstationandloginasomc user.
2. Connect totheXyplex
t el net NameOf Xypl ex 2000 ( NameOf Xypl ex or TCP/ I P addr ess of
Xypl ex)
Pr ess si mul t aneousl y t he keys Ct r l and /
access not echoed
#ent er user name> c
Xypl ex> set pri v
Passwor d> system
Not e : t he bol d char act er s ar e t o be ent er ed by t he oper at or .
Xypl ex >>
I nf or mat i on on Xypl ex ar e avai l abl e.
All theavailablecommandscanbedisplayedbytypinghelp.
1--54
PE/DCL/DD/0032
411--9001--032
Example:
Xypl ex>> show por t 5
Por t 5: 13 Oct 1997 08: 59: 12
Char act er Si ze: 8 I nput Speed: 9600
Fl ow Cont r ol : XON Out put Speed: 9600
Par i t y: None ModemCont r ol : Enabl ed
Access: Local Local Swi t ch: None
Backwar ds Swi t ch: None Name: XXXX_4
Br eak: Local Sessi on l i mi t : 4
For war ds Swi t ch: None Type: Sof t
Pr ef er r ed Ser vi ce: None
Aut hor i zed Gr oups: 0
( Cur r ent ) Gr oups: 0
Enabl ed Char act er i st i cs:
Aut opr ompt , Br oadcast , I nact i vi t y Logout , I nput Fl ow Con-
t r ol , I nt er net Connect i ons, Li ne Edi t or , Loss not i f i ca-
t i on, Message Codes, Out put Fl ow Cont r ol , Ver i f i cat i on
Xypl ex>>
Exit Xyplex:
Xypl ex>> Qui t
Exit Telnet :
PressthekeysCtrl and]
Tel net > Qui t
ReturntotheUNIX window.
1.5.2.5 Final state
Nostatechange.
1.6 Usingthefloppydrive
Theseproceduresallowyoutousethefloppydriveonworkstationswithfloppies
inDOSformat or inUNIX format.
List of proceduresfor usingthefloppydrive
formattingafloppyinDOSformat
mountingafloppy
1.6.1 FormattingafloppyinDOS format
Thisproceduredescribestheformattingof afloppyinDOSformat
Workstationwithafloppydrive
3.5 Floppy
AccesstotheUNIX commandsavailableontheworkstation
1.6.1.4 Actions
FormattingthefloppyinDOSformat:
fdformat --U--blabel --d
label: floppyname
ThefloppyisformattedinDOSformat.
1.6.1.5 Final state
Thereisnochangeof stateasaresult of thisprocedure.
1--56
PE/DCL/DD/0032
411--9001--032
1.6.2 Mountingafloppy
Thisproceduredescribesthemountingof afloppybythebackgroundscreenmenu.
Workstationwithafloppydrive, connectedtotheOMC-R local network
3.5 Floppy
Backgroundscreenmenuavailableontheworkstation
1.6.2.4 Actions
1. Insert thefloppyinthedrive.
2. Inthebackgroundscreenmenu, select Mount afloppydisk.
3. Thefloppyismounted, accessibleunder thedirectory/floppy/floppy0.
4. Toejectthefloppy, selectEjectafloppydiskinthebackgroundscreenmenu.
If the directory /floppy/floppy0 has been accessed, you must exit fromthe
directorytoeject thefloppy.
1.6.2.5 Final state
1.7 Managingprintjobs
Print jobscanbemanagedbyusingthescreenmenuor UNIX commands.
Theprintingmanagement proceduresdescribedbeloware:
activatingaprintout
listingongoingprint jobs
cancellingaprintout
1.7.1 Additional information
TheUNIX commandslpr, lpq, andcancel provideawiderangeof options.
For more information, consult the UNIX manual available in the UNIX
environment of theOMC-R:
man<commandname>
1.7.2 Activatingaprintout
Therearetwowaystoprint data:
by selecting the data in a text window (notifications, system responses to
commands, for example) anduseanoptionof thebackgroundscreenmenu
byusingtheUNIX commandlp
The systemreturns a request id <identifier> message before the command is
executedineither thesystemwindowor theUNIX windowif thelpcommandis
used.
1--58
PE/DCL/DD/0032
411--9001--032
1.7.2.1 Activating a printout (background screen menu)
Introduction
Thisprocedureusesthebackgroundscreenmenutoprint data.
Prerequisite
Theprinter must beconnectedtotheOMC-R local network
Initial state
Backgroundscreenmenuavailableontheworkstation
Actions
1. Select dataintext window.
2. Usetheoptionsof thebackgroundscreenmenu.
Final state
1.7.2.2 Activating a printout (UNIX)
Introduction
Thisprocedureusesthelp UNIX command toprint data.
Prerequisite
Theprinter must beconnectedtothelocal OMC-R network.
Initial state
UNIX commandsavailableontheworkstation.
Actions
Printout request:
lp<nameof filetoprint>
Final state
1--60
PE/DCL/DD/0032
411--9001--032
1.7.3 Listof ongoingprintjobs
Whenaprintjobisactivated, thesystemrecordstherequestandqueuesthejob. Use
thelpqcommandtodisplaythelist of jobswaitingtobeprinted.
Thelpqcommandreturnsanorderedlistof queuedprint jobsandtheir identifiers.
Thefirst jobonthelist isthenext onetobeprinted.
1.7.3.1 List of ongoing print jobs (procedure)
Introduction
Thisprocedurelistsall print jobsinthequeue.
Prerequisite
Theprinter must beconnectedtotheOMC-R local network.
Initial state
Actions
List theongoingprint jobs:
lpq
Thelist of jobswaitingtobeprintedisdisplayed.
Final state
1.7.3.2 Cancelling a printout
A queuedprint request canbecancelledwiththeUNIX cancel command.
If aprint job is in progress and is still included in thelist displayed by thelpq
command(withactive flag), usethecancel commandtostoptheprintout.
If aprint jobisinprogressbut isnolonger includedinthelist returnedbythelpq
command, it cannot becancelled. Thedataisprintedfromtheprintersmemory.
1.7.3.3 Cancelling a printout (procedure)
Introduction
Thisprocedurecancelsaprintjob. Youmustknowtheidentifier of theprint jobto
becancelled.
Prerequisite
Printer connectedtothelocal OMC-R network.
Initial state
Actions
Cancel aprint job:
cancel <identifier of printjob>
Final state
Thereisnochangeof stateasaresult of thisoperation.
1--62
PE/DCL/DD/0032
411--9001--032
1.8 ConnectinganddisconnectingaDATdrivetoaworkstation
Therearetwoproceduresdescribedinthissection:
connectingaDAT drive
disconnectingaDAT drive
1.8.1 ConnectingaDAT drive
InformationontheworkstationareintheNTP <06>.
Theprocedurebelowdescribeshowtoconnect aDAT drivetoaworkstation.
TheOMC-R applicationmust beoperating.
1.8.1.3 Actions
1. Stoptheworkstation
1.1 ShutdowntheapplicationfromtheMMI
1.1.1 Select theOMC-R object:
GOTO OMC-R Browser
SELECT_OBJ OMC-R
1.1.2 Shutdowntheapplication:
GOTO OMC-R Browser
SELECT Configuration-- omc -- Shut down
1.2 UNIX shutdown
OpenawindowAccesstoUNIX bythebackgroundscreenmenu.
Loginascroot user
UNIX shutdown
#init0
1.3 Power-off theworkstation
Set theON/OFF switchonOFF.
2. Connectionof theDAT drive
ConnecttheDATdrivetotheworkstationbyaSCSI cableconnectingtheSCSI
plugsof theworkstationandtheDAT drive.
Check that thetarget numbers4and5arenot used.
Connect aSCSI busterminationonthesecondSCSI plugof theDAT drive.
3. SwitchontheDAT drive
ON/OFF switchonON
4. Switchontheworkstation
SwitchON/OFF onON.
5. Interrupt theboot.
At thefirst messagedisplayed(Sunbanner),
[STOP],[A]
PresssimultaneouslyonthekeysSTOP andA ontheQwertykeyboard.
or [STOP],[Q]
PresssimultaneouslyonthekeysSTOP andQontheAzertykeyboard.
Thiscommandisof noconsequencefor theworkstation.
6. Relaunchtheboot
OK>boot --r
Optionr sothat theworkstationrecognizestheperipherals(DAT drive).
The application is restarted on the workstation. The main screen appears
(see Figure 1--7).
1.8.1.4 Final state
TheDAT driveisconnected.
1--64
PE/DCL/DD/0032
411--9001--032
1.8.2 DisconnectingaDAT drive
TheprocedurebelowdescribeshowtodisconnectaDAT drivefromaworkstation.
InformationontheworkstationareintheNTP <06>.
A DAT drive must be connected to the workstation. The workstation must be
connectedtothelocal OMC-R network.
1.8.2.3 Actions
1. Stoptheworkstation
1.1 ShutdowntheapplicationfromtheMMI
1.1.1 Select theOMC-R object:
GOTO OMC-R Browser
SELECT_OBJ OMC-R
1.1.2 Shutdowntheapplication:
GOTO OMC-R Browser
SELECT Configuration- omc - Shut down
1.2 UNIX shutdown:
OpenawindowAccesstoUNIX bythebackgroundscreenmenu.
Loginascroot user
UNIX shutdown
#init0
1.3 Power off theworkstation
Set theswitchON/OFF onOFF.
2. Switchoff theDAT drive
Set theON/OFF switchlocatedat theback of theequipment onOFF.
3. Disconnectionof theDAT drive
Disconnect theDAT drivefromtheworkstationbyremovingtheSCSI cable
connectingtheSCSI plugsof theworkstationandtheDAT drive.
Check that thetarget numbers4and5arenot used.
4. Switchontheworkstation
Switch ON/OFF onON
5. Interrupt theboot
At thefirst messagedisplayed(Sunbanner),
[STOP],[A]
PresssimultaneouslyonthekeysSTOP andA ontheQwertykeyboard.
or [STOP],[Q]
PresssimultaneouslyonthekeysSTOP andQontheAzertykeyboard.
Thiscommandisof noconsequencefor theworkstation.
6. Relaunchtheboot
OK>boot --r
The--roptionallowstheworkstationtorecognizetheperipherals(DATdrive
removed).
The application is restarted on the workstation. The main screen appears
(see Figure 1--7).
1.8.2.4 Final State
TheDAT driveisdisconnected.
1--66
PE/DCL/DD/0032
411--9001--032
1.9 ConfiguringtheCiscorouter (V11)
1.9.1 Introduction
TheCiscorouter managementtool, availablefromthebackgroundmenu, provides
thefollowingfunctions:
management of local router (add, updateor removearouter)
management of remote accesses (add, update, or remove a remote access),
includingonOMC-R machine
dynamicandsemi-graphicviewof routersandnetworks: all informationrelated
toOMC-R routingisdisplayedwithinaseparatewindow
automaticdetectionof pre-existingOMC-R routingconfiguration
capability of switching all routes of a faulty router to another router and
restorationof initial configurationwhenfaultyrouter hasbeenfixed
accesstesttoamachineeither local or remote, either router or OMC-Rmachine
(server or workstation)
Theuser must giveapasswordtoaccesstothistool.
Thistool canbeusedeither off-lineor on-line.
1.9.2 Tool details
WhentheCiscorouter configurationtool isrunning, themainmenuisdisplayedin
awindow(seeFigure 1--9).
1.9.2.1 Some operating rules
For eachof theaboveoptions, thefollowingguidelinesaresatisfied:
full helpisprovidedwhenusersreplyincorrectlyor whenusersdonot reply
users can abort thecurrent command andreturn to themainmenu by typing
CTRL C
usersarepromptedtoconfirmeachcommand
Unix Terminal
Exit
Network viewwindowrefresh
Network initial discovery
Add or update a router
Remove a router
Add or update a remote access
Remove a remote access
Switch fromone router to another one
Access test
Skilled mode
Figure1--9 Ciscorouter configurationtool (V11)
1--68
PE/DCL/DD/0032
411--9001--032
1.9.2.2 Details of each choice
The Network viewwindowrefresh choice redraws the network view in the
window.
TheNetworkinitial discoveryoptiondetectspre-existingOMC-R routeswhich
havebeenset upbeforethetool wasused.
TheAddor updatearouter option allows to add a new router or update the
configurationof anexistingrouter locatedonthelocal Ethernet network.
The Removea router option allows to remove an existing router. All remote
accessesusingthisgatewayshouldhavebeenpreviouslyremoved.
TheAddor updatearemoteaccessoptionpermitstoaddanewremoteaccessor
to update an existing one. Associated routes on the related gateway and on the
OMC-R machinesareupdated.
TheRemovearemoteaccessoptionallowstoremoveanexistingremoteaccess.
AssociatedrouteontherelativegatewayandontheOMC-Rmachinesaredeleted.
TheSwitchfromonerouter toanother oneoptionpermitstoswitchtemporarily
all remoteaccessesof afaultyrouter toanother oneandtocomebacktotheinitial
configurationwhenthefaultyrouter hasbeenfixed.
TheAccesstestoptionenablestotesttheaccessibilityof amachine. Thismachine
canbeeither:
alocal OMC-R machine
alocal router
aremoteOMC-R machine
aremoterouter
TheSkilledmodeoptionallowsuserstofetchanddisplaytherouterconfiguration.
Theinterpretationof configurationparametersrequiresgoodknowledgeof Cisco
routersor Ciscodocumentation.
1.9.2.3 Add or update a Cisco router
Introduction
Thisprocedureaddsarouter tothelocal OMC-R network or updatesit.
Prerequisite
A router must beconnectedtothelocal OMC-R network.
Initial state
Therouter configurationtool isavailableontheserver.
Actions
Enter thefollowingmandatoryparameterstodefineanewrouter:
itsname
itsIP address
itsX.25address
theupper limit of theVirtual CircuitsauthorizedbytheX.25subscription
theIP addressassignedtotheX.25interfaceof therouter
Theusercanchoosetocompletelyreconfiguretherouter(theaboveparametersplus
anothersetof parameters). Inthecaseof areplacementrouterthathasjustcomeout
of thefactory, thiscompletereconfigurationoptionismandatory. If theIPaddress
of therouter isnot specifiedinthe/ite/hostsfile, it must beaddedtothelatter.
Final state
Router addedtoor updatedontheLocal AreaNetwork.
1--70
PE/DCL/DD/0032
411--9001--032
1.9.2.4 Add or update a remote access
Introduction
Thisprocedureaddsanewremoteaccessor updatesanexistingone.
Prerequisite
Therouter must beconnectedtothelocal OMC-R network.
Therouter must beconnectedontheremotesite.
Initial state
Therouter configurationtool isavailableontheserver.
Actions
Enter thefollowingparameterstodefineanewremoteaccess:
itsname(for agoodunderstanding, itwouldbeconvenienttoassigntheremote
router nametotherelatedremoteaccess)
thegatewayname(nameof local router usedtoroutetothisremoteaccess)
theremotenetwork Internet addressaccess
theremoterouter X.25address
theremoterouter IP addressassignedtoitsX.25interface
Final state
Theroutingtowardsaremotesiteisaddedor updated.
1.10 Checkingtheaccess rights of softwarecomponents
1.10.1 Introduction
Thisprocedurecheckstheaccessrightsof softwarecomponentsintheMD/OMC
applications. Foreachanomalydetected, thetool displaysamessageontheterminal
window. Thentheadministrator modifies thecomponent withtherecommended
rights.
1.10.2 Prerequisites
Activeserver andback-upserver connectedtotheOMC-R Local AreaNetwork.
1.10.3 Initial state
1.10.4 Actions
1. Loginasomc user
2. Changedirectory: cd/CMN/base/exe
3. Runthetool tocheck accessrightswithfollowinginput parameters:
cf_access.xoption
-cconfigFileName Set thenameof theconfigurationfile
-e Check requiresthesamepermissionsmodes
-m Check isperformedonthemediationfunction
-o Check isperformedonthemanager function
-s Check isperformedonastation
-d Check isperformedontheSDOfunction
-p Check isperformedonthepcuoamservfunction
-h For moreinformationonthistool
1.10.5 Final state
Theaccessrightsof thecomponentshavebeenchecked.
1--72
PE/DCL/DD/0032
411--9001--032
1.11 Archive/restore(OMC-Ragent)
1.11.1 Purpose
TheseproceduresallowauthorizeduserstobackupoperatingdatafromtheOMC-R
agent diskstoamagneticcartridgeandreloadthedatatodiskswhenrequired.
Thearchivecartridgemust beinstalledinthedriveof theactiveOMC-Rmanager
server beforebeginningaprocedure.
All thearchivecartridges must beidentified by a label before use. All thedata
recordedonacartridgearelostwhenthecartridgeislabeled. RefertoNTP<128>.
1.11.2.1 Archiving data
Thenetwork operator must archivedataasandwhennecessary.
The user in charge must execute the archive procedures at regular intervals. A
procedureisusedto archiveall thedataof agiventyperecordedontheOMC-R
agent disksonagivenday.
Several setsof different typesof datacanbebackeduponthesamecartridge.
1.11.2.2 Restoring data
Dataarealwaysrestoredfromanarchivecartridgetosatisfyoneof thefollowing
needs:
Thedatacannot beanalyzedinreal time, but shouldbeinvestigated.
It canbenecessarytoreviewthesystemoperatingconditionsat agiventimeto
comparethemto thepresent days conditions, sincethis information may be
useful toinvestigateanymalfunctionsthat tendtoberepeated.
All thedataof agiventypearchivedonacartridgewithacreationdatematching
thedayspecifiedbytheuser arerestoredtotheOMC-R agent disks.
1.11.3 Archiveprocedure
ON AN OMC-R SERVER
1. LogintotheOMC-R asadministrator user.
2. Install thearchivecartridgeinthedriveof theactiveOMC-R server
GOTO OMC-R Browser
SELECT_OBJ MD-R
SELECT Administration-- Archiving-- Archive
OR Select theoptionArchive inthepop-upmenu
GOTO Actionwindow
SET label label of thecartridgeinstalledinthedrive
SET type typeof datatoback up
SET date dayonwhichthedatatoback upwererecorded
SET Apply
ThefollowingOMC-R agent typesof datacanbearchived:
faults: messagesrecordedinthe/MD/notifpartitionontheOMC-R
agent disks
observations: all observation reports (raw, daily, and busiest day of the
month reports) recorded in the /MD/obs partition on the
OMC-R agent disks
tracedata: tracedatarecordedinthe/MD/trace_function partitionon
theOMC-R agent disks
Thesystemvalidates thedateandlabel, then, archives thedata. Readback the
cartridgetocheckthebackup(seeendof Paragraph).
1--74
PE/DCL/DD/0032
411--9001--032
1.11.4 Restoreprocedure
ON AN OMC-R SERVER
GOTO OMC-R Browser
SELECT_OBJ MD-R
SELECT Administration-- Archiving-- Restore
OR Select theoptionRestore inthepop-upmenu
GOTO Actionwindow
SET type typeof datatorestore
SET date dayonwhichthedatatorestorewererecorded
SET Apply
Thesystemvalidatesthedateandlabel, then, startstorestorethedatatotheOMC-R
agent disksasfollows:
faults: theselectedmessagesarecopiedtothe/MD/restored/notif
partition
observations: theselectedreportsarecopiedtothe/MD/restored/obs
partition
tracedata: theselecteddataarecopiedtothe
/MD/restored/trace_function partition
1.11.5 Procedurefor checkinganarchivecartridge
ON AN OMC-R SERVER
GOTO OMC-R Browser
SELECT_OBJ MD-R
SELECT Administration-- Archiving-- Displayarchivelist
OR Select theoptionDisplayarchivelist inthepop-upmenu
GOTO Actionwindow
SET Apply
For each archive on the cartridge, the following information is recorded in the
sessionlogs:
archiveidentifier
categoryof archiveddata
typeof archiveddata
dateonwhichdatawerearchived
1--76
PE/DCL/DD/0032
411--9001--032
1.12 Archive/ restore(OMC-RManager)
1.12.1 Purpose
TheseproceduresallowauthorizeduserstobackupoperatingfilesfromtheOMC-R
manager diskstoamagneticcartridgeandreloadthedatatodiskswhenrequired.
Thearchivecartridgemust beinstalledinthedriveof theactiveOMC-Rmanager
server beforebeginningaprocedure.
All thearchivecartridges must beidentified by a label before use. All thedata
recordedonacartridgearelostwhenthecartridgeislabeled. RefertoNTP<128>.
1.12.2.1 Archiving data
Thenetwork operator is responsiblefor archivingOMC-R manager dataas and
whennecessary.
The user in charge must execute the archive procedures at regular intervals. A
procedureisusedtoarchiveall thefilescreatedonagivenday.
Several setsof different typesof datacanbebackeduponthesamecartridge.
1.12.2.2 Restoring data
Dataarealwaysrestoredfromanarchivecartridgetosatisfyoneof thefollowing
needs:
Thedatacannot beanalyzedinreal time, but shouldbeinvestigated.
It canbenecessarytoreviewthesystemoperatingconditionsat agiventimeto
comparethemto thepresent days conditions, sincethis information may be
useful toinvestigateanymalfunctionsthat tendtoberepeated.
A major disk problemoccured and damaged the OMC-R manager Sybase
databaseor someoperatingfiles.
All thedataof agiventypearchivedonacartridgewithacreationdatematching
thedayspecifiedbytheuser arerestoredtotheOMC-R manager disks.
1.12.3 Archiveprocedure
ON AN OMC-R SERVER
GOTO OMC-R Browser
SELECT_OBJ OMC-R
SELECT Administration-- Archiving-- Archive
OR Select theoptionArchive inthepop-upmenu
GOTO Actionwindow
SET type typeof datatoback up
SET date dayonwhichthedatatoback upwererecorded
SET Apply
ThefollowingOMC-R manager typesof datacanbearchivedandrestored:
faults: messagesrecordedinthe/CMN/base/save_restpartitionon
theOMC-R manager disks
observations: all observation reports (raw, daily, and busiest day of the
month) recordedinthe/OMC/obs partitionontheOMC-R
manager disks
tracedata: tracedatarecordedinthe/CMN/base/save_restpartitionon
theOMC-R manager
other data: files listed in the /CMN/data partition on the OMC-R
manager disks
backup: BDE backupstoredontheOMC-R Manager disks
Thesystemvalidates thedateandlabel, then, archives thedata. Readback the
cartridgetocheckthebackup(seeendof Paragraph).
1--78
PE/DCL/DD/0032
411--9001--032
1.12.4 Restoreprocedure
ON AN OMC-R SERVER
GOTO OMC-R Browser
SELECT_OBJ OMC-R
SELECT Administration-- Archiving-- Restore
OR Select theoptionRestore inthepop-upmenu
GOTO Actionwindow
SET type typeof datatorestore
SET date dayonwhichthedatatorestorewererecorded
SET Apply
Thesystemvalidatesthedateandlabel, then, startstorestorethedatatotheOMC-R
agent disksasfollows:
faults: theselectedmessagesarecopiedtothe
/CMN/base/save_rest partition
observations: theselectedreportsarecopiedtothe/OMC/obs partition
tracedata: the selected data are copied to the /CMN/base/save_rest
partition
other data: the data files are copied back to their original directory
/CMN/data
1.12.5 Procedurefor checkinganarchivecartridge
ON AN OMC-R SERVER
GOTO OMC-R Browser
SELECT_OBJ OMC-R
SELECT Administration-- Archiving-- Displayarchivelist
OR Select theoptionDisplayarchivelist inthepop-upmenu
GOTO Actionwindow
SET Apply
For each archive on the cartridge, the following information is recorded in the
sessionlogs:
archiveidentifier
categoryof archiveddata
typeof archiveddata
dateonwhichdatawerearchived
1--80
PE/DCL/DD/0032
411--9001--032
1.13 Centralizedarchivingconfiguringprocedure
1.13.1 Purpose
Thisdocumentdescribesthewholeoperationstousecentralizedarchivingfunction.
ThesesoperationsapplyontheNFSserver inpart andonOMC--Rserver inother
part.
This procedureapplies to V12, V13, V14, andV15OMC--R andonSunstation
concerningtheNFSserver.
Thisoperationneed300Mominimumdisk spacefor abackupwithaneft.
Fordiskchoice,largediskcapacityhavetobeused(FYI,afull BDErequiresaround
1Gbytes). Thisdisk spacecouldbeget withinternal andexternal disks.
if diskspaceonNFSserver isnot enough, thisprocedurehelpsyoutoinstall (and
partition) anextradisk.
1.13.4 OMC--Rimpact
Thisprocedureapplyonpartof OMC--Rserver. So, theOMC--Rserver havetobe
stopped. ItapplyalsoonNFSserver. ItisstronglyrecommendedtouseanOMC--R
server asaNFSserver.
1.13.5 NFS server configuration
1.13.5.1 On NFS server
Newdiskinstallation
Thissectionapplyonlyif thereisanewdisktoinstall.Itisrecommendedtoreserve
thisdisk at anexclusivearchivinguse.
First case:
NFsserver isanOMC--R server. OMC--R isrunning. thereisnologgeduser.
1. Logonasadmistrator user.
2. InOMC--Rbrowserwindow, selectconnexiontoOMC--RinSecuritymenu.
3. InConnexionwindow(OMC--R), set administrator inName field, infield
Passwordset theright informationsandclick onConnexionbutton.
4. StopOMC onNFSserver :
InOMC--R Browser window, click toselect omcobject.
Insub--menuof Configuration menu, select Stopstation
1--82
PE/DCL/DD/0032
411--9001--032
5. InActionwindow, click onApplybutton.
Secondcase:
1. Openaroot session.
2. If openwinisrunning, select AccesstoUNIX inbackgroundscreenmenu.
view
3. Logonasroot user toperformthefollowingoperations.
Login: root
Password:
4. If NFSserver isanOMC--R server, desactivateautomaticstart of OMC :
#/usr/local/omcmaint/ds_omcAutoStart.sh--disable
###############################################################
#NORTEL OMC--R TOOLS #
###############################################################
#AutomaticOMC--R startupactivation #
#--------------------------------------------------------------------------------------------------------------------------#
#STARTING: ds_omcAutoStart.sh #
#WITH : --disable #
#LOGIN : /var/local/sysuit/_log/ds_omcAutoStart.log #
#--------------------------------------------------------------------------------------------------------------------------#
#DATE | VERSION | UID| MACHINE #
#--------------------------------------------------------------------------------------------------------------------------#
#04/14/9810:30:21| V10_03.E00| 0| gstat1 #
###############################################################
Disablingautomaticstart....Ok
###############################################################
#ds_omcAutoStart.sh#
#--------------------------------------------------------------------------------------------------------------------------#
#ENDDATE : 04/14/9810:30:28 #
#STATUS: OK #
###############################################################
#
5. Stopthesystem
#init0
6. If systemasks:
Typeb(boot), c(continue), or n(newcommandmode)>,
7. answer n
8. List all periphericalsof theserver
ok probe--scsi--all
/sbus@1f8000000/esp@0,800000
Target 0
Unit 0Disk ...
1--84
PE/DCL/DD/0032
411--9001--032
Target 2
Unit 0Disk ...
Target 4
Unit 0RemovableTape...
Target 6
Unit 0RemovableReadOnlydevice...
ok
9. In SCSI selector of the newdisk, select a figurewhich does not appear in
Targetslistsbyprobe--scsi--all command(inthisexample, 1, 3, 5or 7).
10. Connect physicalythedisk inSCSI chainof theNFSserver.
11. Listagainall theperiphericalstoshowif thenewdiskisknownbytheserver.
ok probe--scsi--all
/sbus@1f8000000/esp@0,800000
Target 0
Unit 0Disk ...
Target 2
Unit 0Disk ...
Target 3
Unit 0Disk ...
Target 4
Unit 0RemovableTape...
Target 6
Unit 0RemovableReadOnlydevice...
12. Reboot thesystem
ok boot --r
13. Logontosystemasroot user
consolelogin: root
password: rootpassword
...
#
14. Format andmakepartitionthenewdisk
#format
Searchingfor disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0<SUN1.05cyl 2036alt 2hd14sec72>
/sbus@1,f8000000/esp@0,800000/sd@0,0
1. c0t2d0<SUN2.1Gcyl 2733alt 2hd19sec80>
/sbus@1,f8000000/esp@0,800000/sd@2,0
2. c0t3d0<SUN1.05cyl 2036alt 2hd14sec72>
/sbus@1,f8000000/esp@0,800000/sd@3,0
Specifydisk (enter itsnumber): disk number topartition
wherepartitiondisk number isaccordingtoSCSI selectionof thenewdisk.
Thisnumber appearsafter theletter t of c0t3d0. Inour example, it must beset
with2
Specifydisk (enter itsnumber): 2
selectingc0t3d0
[disk formated]
FORMAT MENU:
disk -- select adisk
type -- select (define) adisk type
partition -- select (define) apartitiontable
current -- describethecurrent disk
format -- format andanalyzethedisk
repair -- repair adefectivesector
label -- writelabel tothedisk
analyze -- surfaceanalysis
defect -- defect list management
backup -- searchfor backuplabels
verify -- readanddisplaylabels
save -- savenewdisk/partitiondefinitions
inquiry -- showvendor, product andrevision
volname -- set 8--character volumename
quit
format>
15. If thedisk isnot formatted([disk not formatted])
1--86
PE/DCL/DD/0032
411--9001--032
format>format
Readytoformat. Formattingcannot beinterrupted.
andtakes23minutes(estimated). Continue? y
Beginningformat. Thecurrent timeisThuApr 916:23:58
1998
Formatting...
done
Verifyingmedia...
pass0-- pattern=0xc6dec6de
2035/12/18
pass1-- pattern=0x6db6db6d
2035/12/18
Total of 0defectiveblocksrepaired.
format>
16. If disk partitiondefinitionisrequired,
partitiondisk:.
format>partition
PARTITION MENU:
0 -- change0 partition
select -- select apredefinedtable
modify -- modifyapredefinedpartitiontable
name -- namethecurrent table
print -- displaythecurrent table
label -- writepartitionmapandlabel tothedisk
quit
partition>
List actual partitionningof disk.
partition>print
Current partitiontable(original):
Total disk cylindersavailable: 2036+2(reservedcylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0-- 1017 501.05MB (1018/0/0) 1026144
1 unassigned wm 1018-- 2035 501.05MB (1018/0/0) 1026144
2 backup wm 0-- 2035 1002.09MB (2036/0/0) 2052288
3 unassigned wm 0 0 (0/0/0) 0
partition>
Fill disk space beetween different partitions and for each of them, set the
parameters.
WARNING: donot changetheparametersof thepartitionnumber 2!
partition>0
0 unassignedwm 0-- 1017501.05MB (1018/0/0) 1026144
Enter partitionidtag[unassigned]: unassigned
Enter partitionpermissionflags[wm]: wm
Enter newstartingcyl[0]: 0
Enter partitionsize[1026144b, 1018c, 501.05mb]: 500mb
partition>print
Current partitiontable(unnamed):
0 unassignedwm 0-- 1015 500.06MB (1016/0/0) 1024128
1 unassignedwm 1018-- 2035 501.05MB (1018/0/0) 1026144
2 backup wm 0-- 2035 1002.09MB (2036/0/0) 2052288
3 unassignedwm 0 0 (0/0/0) 0
1--88
PE/DCL/DD/0032
411--9001--032
partition>
partition>1
1 unassigned wm 1018-- 2035 501.05MB (1018/0/0) 1026144
Enter partitionidtag[unassigned]: unassigned
Enter partitionpermissionflags[wm]: wm
Enter newstartingcyl[1018]: 1016
Enter partitionsize[1026144b, 1018c, 501.05mb]: 502.03mb
partition>print
Current partitiontable(unnamed):
0 unassignedwm 0-- 1015 500.06MB (1016/0/0) 1024128
1 unassignedwm1016-- 2035 502.03MB (1020/0/0) 1028160
2 backup wm 0-- 2035 1002.09MB (2036/0/0) 2052288
partition>
Appythesesmodifications:
partition>label
Readytolabel disk, continue? y
partition>
Quit thepartionningtool :
partition>quit
FORMAT MENU:
disk -- select adisk
type -- select (define) adisk type
partition -- select (define) apartitiontable
current -- describethecurrent disk
format -- format andanalyzethedisk
repair -- repair adefectivesector
label -- writelabel tothedisk
analyze -- surfaceanalysis
defect -- defect list management
backup -- searchfor backuplabels
verify -- readanddisplaylabels
save -- savenewdisk/partitiondefinitions
inquiry -- showvendor, product andrevision
volname -- set 8--character volumename
quit
format>quit
Builtanewfilesystemoneachof thesespartitions. Number 3insidec0t3d0s0in
previous command is according with SCSI selector of the new disk (to be
customizedinyour case) ands0isaccordingwiththenumber of thepartition. In
our example, thiscommandmust berestart onc0t3d0s1.
#newfs/dev/rdsk/ c0t3d0s0
newfs: construct anewfilesystem/dev/rdsk/ c0t3d0s0: (y/n)? y
/dev/rdsk/c0t3d0s0: 1024128sectorsin1016cylindersof 14tracks, 72sectors
500.1MB in64cyl groups(16c/g, 7.88MB/g, 3776i/g)
super--block backups(for fsck --F ufs --ob=#) at:
32, 16240, 32448, 48656, 64864, 81072, 97280, 113488, 129696, 145904, 162112,
178320, 194528, 210736, 226944, 243152, 258080, 274288, 290496, 306704,
322912, 339120, 355328, 371536, 387744, 403952, 420160, 436368, 452576,
468784, 484992, 501200, 516128, 532336, 548544, 564752, 580960, 597168,
613376, 629584, 645792, 662000, 678208, 694416, 710624, 726832, 743040,
759248, 774176, 790384, 806592, 822800, 839008, 855216, 871424, 887632,
903840, 920048, 936256, 952464, 968672, 984880, 1001088, 1017296,
#
17. Create mounting points of each of theses partitions (two partitions in our
example):
#mkdir /partition1/partition2
#chmod777/partition1/partition2
#
18. Under theeditor of your choice, for examplevi, update /etc/vfstabfile,
1--90
PE/DCL/DD/0032
411--9001--032
19. addalinefor eachpartitiontomount:
/dev/dsk/c0t3d0s0/dev/rdsk/c0t3d0s0/partition1ufs2yes
/dev/dsk/c0t3d0s1/dev/rdsk/c0t3d0s1/partition2ufs2yes
20. If NFSserver isanOMCworkstation, activateautomaticlaunchof theOMC.
#/usr/local/omcmaint/ds_omcAutoStart.sh--enable
###############################################################
#NORTEL OMC--R TOOLS #
###############################################################
#AutomaticOMC--R startupactivation #
#--------------------------------------------------------------------------------------------------------------------------#
#STARTING: ds_omcAutoStart.sh #
#WITH : --enable #
#--------------------------------------------------------------------------------------------------------------------------#
#DATE | VERSION | UID| MACHINE #
#--------------------------------------------------------------------------------------------------------------------------#
#04/14/9810:29:02| V10_03.E00| 0| gstat1 #
###############################################################
Enablingautomaticstart....Ok
###############################################################
#ds_omcAutoStart.sh #
#--------------------------------------------------------------------------------------------------------------------------
#ENDDATE : 04/14/9810:29:09 #
#STATUS: OK #
###############################################################
#
21. Disk installationiscomplete.
Sharingpartition(s)
22. Update /etc/dfs/dfstabfile, addinalinefor eachpartitiontoshare:
share--Fnfs--orw=naxos:glenans:lotus:crocus,anon=0,nosuid/partition1
share--Fnfs--orw=naxos:glenans:lotus:crocus,anon=0,nosuid/partition2
naxos:glenans:lotus:crocusisalist of serverswhichcanbeusedtodosaveson
partitions c0t3d0s0 et c0t3d0s1 mounted respectively on /partition1 and
/partition2(inbi--serverscase, insertinthelist theactiveserver andthepassive
server).
23. Update/etc/hostsfileinaddingalinefor eachpresent server inatleast oneof
thelistsherebelow(eachlineiscomposedwithIP addressandthehostname
of theconcernedserver).
24. Mountnewcreatedpartitions(ignoreerrorsmessagesnotaccordingtothenew
partitions):
#mountall
checkingufsfilesystems
/dev/rdsk/c0t3d0s1: isclean.
/dev/rdsk/c0t2d0s1: isstable.
/dev/rdsk/c0t0d0s3: isstable.
mount: /dev/dsk/c0t0d0s3isalreadymounted, /homeisbusy, ortheallowable
number of mount pointshasbeenexceeded
mount: /dev/dsk/c0t2d0s1 is already mounted, /grande_nfs is busy, or the
allowablenumber of mount pointshasbeenexceeded
mount: /tmpalreadymounted
#
25. Sharenewpartitions:
#shareall
#
26. Check if partitionsarerealyshared:
#share
-- /petite_nfsrw=naxos:glenans:lotus:crocus,anon=0,nosuid
-- /grande_nfsrw=naxos:glenans:lotus:crocus,anon=0,nosuid
-- /partition1rw=naxos:glenans:lotus:crocus,anon=0,nosuid
-- /partition2rw=naxos:glenans:lotus:crocus,anon=0,nosuid
#
27. Reboot thestation.
#init6
The station is now operationnal and if it is an OMC--R station, local
applicationisrestarted.
1.13.5.2 On OMC--R servers
DeclareNFS server
1. Undertheeditorof yourchoise, forexamplevi, update/etc/hostsfileinadding
alinewithyour NFSserver network addressanditshostname.
Createmountingpoints
2. Createpartitionsmountingpointswhichwill beusedfor backup.
1--92
PE/DCL/DD/0032
411--9001--032
#mkdir / point_de_montage1
#chmod777/ point_de_montage1
#cd/
#
OMC--Rconfiguration
3. Edit /CMN/base/config/omc_configure.cfgfile.
4. Besurethat cfInitOMCNameparameter hasadifferent valueoneachOMC,
if not, backupof different OMC couldbemixedandindissociable.
5. Intheparagraphlimitedbythefollowinglines:
BEGIN_LIST_FILESYSTEM_SAVE
END_LIST_FILESYSTEM_SAVE
addalinefor partitiononthat youintendtobackup.
Theseslineshasthefollowingsyntax:
<fileSystemLabel><localMountPoint><hostname><fileSytemDevice>
where<fileSystemLabel>isthelabel of thepartitionwhichbeknownbythe
backuptool,
<localMountPoint>inthemountingpoint ontheOMC server,
<hostname>isthenameonwhichisdefinedNFSserver inthe/etc/hostsfile,
<fileSystemDevice>isthenameonwhichissharethepartitionontheNFS
server.
Inour example, addedlinesinomc_configure.cfgfileswill appear as:
sauvegarde1 /point_de_montage1 gstat1/partition1
sauvegarde2 /point_de_montage2 gstat1/partition2
StoptheOMC--R
6. Onthepassiveserver, under omclogin, typethefollowingcommand:
(omc)%appstopstd
OMC reconfiguration
7. Start omc_configure.shtool
omc% /CMN/base/shell/omc_configure.sh --B nom_du_serveur_actif
nom_du_serveur_passif
Restart theOMC
8. Onpassiveserver thenactiveserver, restart theapplication.
omc%appstart
1.14 Archiving/Restoringviacf_save_tool.x
Thisprocessusisanindependentprocessusthatcanberunon-- oroff-- line. Itisrun
out of thescopeof theomcadministration.
If it isrunningon--line, it allowstheuser to:
accesstoall operationspossiblewith cf_save_mgr.x and cf_save_md.x,
backup/retrievePCUOAM configurationandPCUSN views,
cancel backup/retrieveoperation
If it isrunningoff--line, it allowstheuser to:
backupthewholehost configurationanddatabases,
retrievethehost mainconfiguration
retrievetheOMC global configurationfilesanddatabase,
labeliseatape,
readatapelabel,
list thecontent of amedia
The action to be performed can be chosen using the command line or in an
interactivemode(optionschoice).
1.14.1 Cf_save_tool.x usage
Thefollowingcommandlineissupported:
/ CMN/ exe/ cf _save_tool . x - V - h [ - d <di ag_f i l e>] [ - n <task_number>]
[ - p <part> - o <operati on> - t <date> - l <l abel > - y <data_type>]
[ - f orce]
[ - cancel | - CANCEL]
[ - wi thoutef t]
1.14.1.1 Command line options
Theoptionsare:
- V : returnssoftwareversionandexits
- h : returnssoftwareusageandexits
- d <di ag_f i l e> : wherediag_fileisafilename. Theinternal traceof thetask
will beprintedinthisfile. Thedefault valueis:
/CMN/base/diagnostic/diag_toolsave
- n <t ask_number > : where task number is an integer. The message box
number of thetask isset to<task_number>. Thisparameter isoptionnal.
1--94
PE/DCL/DD/0032
411--9001--032
- p <par t >: setswhichomc --part isconcerned. Thepossiblevaluesare:
md: mediationpart
omc: manager part
Thisvalueisuseful onlywhenon--line. It asnomeaningfor abackup.
- o <oper at i on>: settheoperationthatistobedone. Thepossiblevaluesare:
archive: archivesomedata
restore: restoresomedata
retrieve_cfg: restoreonlymainconfigurationfiles.
labelize: createlabel onatape
consult : consult tapelabel
list : list tapecontent
- t <dat e>: date. Dateformat is:
AAAAMMJJ or d--J for archiving/restoring(not usingfor archiving.
Thetool usethecurrent date)
AAAAMMJ J HHMM for retrieving
- l <l abel >: medialabel. Neededfor backup, retrieve, retrieve_cfg, archive,
restore, labelize.
- y <dat a_t ype> : where data_type is a keyword. It can takes one of the
followingvalues:
fault : fault management data
obs: observationdata
trace: tracedata
other : other data
backup: OMC/MDconfigurationanddatabase
pcuoam: PCUOAM configurationandPCUSN views
- cancel or CANCEL : cancel operationinprogress.
- wi t hout ef t : usableonlywith --oarchive and --ybackup options; not
includetheeft filesinBDE backup
Thisvalueisneededonlyfor archiving/restoringoperation.
Thefollowingtableresumesthevalidactionsandparameters:
A whitevaluemeansthat thisparameter isnot needed
A meansthat thisvalueisneeded
A stringwithin[ ] meansthatthevalueisnotneeded. Thestringisthedefault
value.
A stringwithin( ) meansthatthevalueisnotneeded. Thestringdescribesthe
action
Thestringvaluesdescribesall possiblevalues
On--line(OMC running), thepossibleoperationsare:
OPERATION PART LABEL DATE DATATYPE
archive omc

Ffult
observations
trace
other
[omc]

Backup
pcuoam
md

Fault
Observations
Trace
restore omc

fault
observations
trace
other
[omc]

pcuoam
md

fault
observations
trace
labelize [omc]

consult [omc]
(tape)
list [omc]
(tape)
cancel
1--96
PE/DCL/DD/0032
411--9001--032
WhentheOMC-R applicationisstopped(Off-line), thepossibleoperationsare:
Archive

backup
Restore

backup
retrieve_cfg

Labelize

Consult (tape)
List (tape)
Cancel
1.14.2 OMC--Rdataarchiving/restoringininteractivemode
Thepurposeof thisprocedureistodescribe:
thearchiving/restoringof OMC-R environment databackup(savedinOMC-R
databases)
thearchiving/restoringof OMC-Rdailydata(observations, alarms) collectedon
apreviousspecificday
theretrievial of OMC-Rconfigurationfiles, theOMC-Rapplicationisstopped.
All theoperationsdescribedareperformedviaacommandlineunderUNIXprompt
ontheactiveserver.
Requiredresources:
onelabelledDAT for anarchiving
theDAT withthepreviousdataarchivefor arestoring
Anomc sessionisavailableontheactiveserver.
Theapplicationpart are: omc| md
If actionType=archiveanddataType backup: theOMC-Rapplicationis running.
If actionType=archiveanddataType=backup: theOMC-Rapplication is running
or not.
If actionType=restoreanddataType=backup: theOMC-Rapplicationishalted.
If actionType=retrieve_cfg: theOMC-Rapplicationishalted.
1.14.2.3 Actions in interactive mode
If youneedfurther informationconcerningthevalidactions andtheparameters,
see Notepage1--99at theprocedureend.
1. If not yet done, insert aDAT (without protection) intheDAT drive.
2. If not already done, openaUNIX windowandloginas omc user, onthe
activeserver.
3. If themedialabel name(labelName) isnot known:
. . . ( omc) %/ CMN/ base/ exe/ cf _save_tool . x
Oper at i on t o per f or m:
1 : Ar chi ve dat a
2 : Rest or e dat a
3 : Ret r i eve conf i gur at i on f i l es
4 : Label i ze a t ape
5 : Consul t t ape l abel
6 : Li st medi a cont ent
( 0 : exi t )
>5
l abel : l abel Name
. . . ( omc) %
1--98
PE/DCL/DD/0032
411--9001--032
4. Tolabelizethemedialabel name(labelName):
1 : Ar chi ve dat a
2 : Rest or e dat a
( 0 : exi t )
>4
I nput medi a l abel :
>l abel Name
. . . ( omc) %
5. Toknowavaluefor specificDay:
1 : Ar chi ve dat a
2 : Rest or e dat a
( 0 : exi t )
>6
>l abel Name
par t Name dat aType speci f i cDay. . .
. . . ( omc) %
6. Launchthearchive/restoretool:
CAUTION
Equipmentdamage
Thearchiveactionerases all precious datawhichhavebeensaved
earlier so be sure to have the right DAT.
1 : Ar chi ve dat a
2 : Rest or e dat a
( 0 : exi t )
>(choi ce number: 1 or 2)
Dat a t ype t o ar chi ve/ r est or e :
1 : Faul t
2 : Obser vat i ons ( obs)
3 : Tr ace
4 : Ot her dat a
5 : Backup
6 : Pcuoam( 6 number i s not used f or OMC- R)
( 0 : exi t )
>(choi ce number) ( except 6 number )
OMC- R par t t o use :
1 : Medi at i on Par t ( md)
2 : Manager Par t ( omc)
( 0 : exi t )
>(choi ce number)
I nput ( speci f i c dat e) . . . : ( 0 : exi t )
>(choi ce speci f i cDay) ( except f or t he ar chi ve and backup)
I nput medi a l abel : ( 0 : exi t )
>l abel Name ( except f or t he ar chi ve and backup)
. . . ( omc) %
Note: date (for archiving/restoration and retrieve_cfg operation and pcuoam
backupoperation). Thepossibledateformat are:a)
AAAAMMJJ or d--J for archiving/restoring
AAAAMMJ J HHMM for retrieving
Note: Thecancel operationisnot availableininteractivemode.
1--100
PE/DCL/DD/0032
411--9001--032
7. Wait for theendof tool execution:
act i onType successf ul l y compl et ed
actionType: typeof action(archive| restore| retrieve_cfg| labelize| consult |
list)
8. Eject theDAT fromtheDAT driveandmakeit write-protectedbyslidingthe
tabif thearchiving/restorationisfinished.
1.14.2.4 Troubleshooting
Seethelogfile/ CMN/ base/ di agnost i c/ di ag_savet ool for detailsonerrors.
If theOMC-R applicationisrunning, seealsothelogfiles:
/ OMC/ base/ di agnost i c/ di ag_savemgr
/ MD/ base/ di agnost i c/ di ag_savemd
1.14.2.5 Final status
OMC-R dataisarchivedor restored.
1.14.3 PCU OAMconfigurationbackup/restoringviacommandline
1.14.3.1 ntroduction
Thepurposeof this procedureis to describethebackup/restoringof PCU OAM
configuration.
All theoperationsdescribedareperformedviaacommandlineunderUNIXprompt
ontheactiveserver.
Requiredresources:
onelabelledDAT for anarchiving
theDAT withthepreviousdataarchivefor arestoring
1.14.3.2 Initial status
TheOMC-R applicationis runningonboththeactiveserver andthePCU OAM
workstation.
1.14.3.3 Actions in interactive mode
If youneedfurtherinformationconcerningthevalidactionsandtheparameters, see
Notepage1--104at theendat theprocedure.
1. If not yet done, insert aDAT (without protection) intheDAT drive.
OMC-R activeserver.
3. If themedialabel name(labelName) isnot known:
1 : Ar chi ve dat a
2 : Rest or e dat a
( 0 : exi t )
>5
l abel : l abel Name
. . . ( omc) %
4. Tolabelizethemedialabel name(labelName):
1 : Ar chi ve dat a
2 : Rest or e dat a
( 0 : exi t )
>4
>l abel Name
. . . ( omc) %
1--102
PE/DCL/DD/0032
411--9001--032
5. Toknowavaluefor specificDay:
1 : Ar chi ve dat a
2 : Rest or e dat a
( 0 : exi t )
>6
>l abel Name
. . . ( omc) %
6. Launchthearchive/restoretool:
CAUTION
Equipmentdamage
Thearchiveactionerases all precious datawhichhavebeensaved
earlier so be sure to have the right DAT.
1 : Ar chi ve dat a
2 : Rest or e dat a ( not used f or t he PCU OAM)
3 : Ret r i eve conf i gur at i on f i l es ( not used f or t he
PCU OAM)
( 0 : exi t )
>(choi ce number: 1 or 2)
Dat a t ype t o ar chi ve/ r est or e :
1 : Faul t
2 : Obser vat i ons ( obs)
3 : Tr ace
4 : Ot her dat a
5 : Backup
6 : Pcuoam
( 0 : exi t )
>6
I nput ( speci f i c dat e) . . . : ( 0 : exi t )
>(choi ce speci f i cDay) ( onl y f or r est or e)
I nput medi a l abel : ( 0 : exi t )
>l abel Name
OMC- R par t t o use : ( t he par t Name i s not used f or t he
PCU OAM, i t i s aut omat i cal y omc)
1 : Medi at i on Par t ( md)
2 : Manager Par t ( omc)
( 0 : exi t )
>2 ( i f necessar y)
. . . ( omc) %
7. Wait for theendof tool execution:
act i onType successf ul l y compl et ed
actionType: typeof action(archive | restore | labelize | consult | list)
8. Eject theDAT fromtheDAT driveandmakeit write-protectedbyslidingthe
tabif thearchiving/restorationisfinished.
1--104
PE/DCL/DD/0032
411--9001--032
1.14.3.4 Troubleshooting
Seethelogfile/ CMN/ base/ di agnost i c/ di ag_savet ool for detailsonerrors.
If theOMC-R applicationisrunning, seealsothelogfiles:
/ OMC/ base/ di agnost i c/ di ag_savemgr
/ OMC/ base/ di agnost i c/ di ag_pcuoam
1.14.3.5 Final status
ThePCU OAM configurationisarchivedor restored.
Note: Thefollowingtablesresumethevalidactionsandparameters.
WhentheOMC-R applicationisstopped(Off-line), thepossibleoperationsare:
4 Labelize

5 Consult (tape)
6 List (tape)
Cancel
WhentheOMC-R applicationisrunning(On-line), thepossibleoperationsare:
1 Archive data [ 2 ]

6 Pcuoam
2 Restore [ 2 ]

YYYYMMDDHHMM 6 Pcuoam
4 Labelize [ 2 ]

5 Consult [ 2 ]
(tape)
6 List [ 2 ]
(tape)
A whitevaluemeansthat thisparameter isnot needed.
A meansthat thevalueisneeded.
A valuewithin[ ] meansthat thevalueisnot needed(default value).
A valuewithin( ) meansthat thevalueisnot neededbut themediaispresent.
1.15 RestorePCUSNfilesystem
1.15.1 Introduction
Thepurposeof thisprocedureistodescribetherestoringof PCUSN filesystem.
1.15.2 Initial status
TheOMC-R applicationis runningonboththeactiveserver andthePCU OAM
workstation.
1.15.3 Actions
PCU OAM server.
2. Accesstothefollowingdirectory:
. . . / home/ omc<48>( omc) %cd / SDO/ PCUdata/ PCUOAMBackup
3. List files.
Thedirectoryiscomposedbyonedirectoryandthreelastbackupfilesforeach
PCUSN declaredonPCU OAM server.
. . . / SDO/ PCUdat a/ PCUOAMBackup<49>( omc) %l s - l
t ot al 12100
dr wxr - xr - x 2 omc omc 512 Nov 12 11: 37 PCU_OFST_E1
- r w- r - - r - - 1 omc omc 1157 Nov 12 11: 16 PCU_OFST_E1. t ar
- r w- r - - r - - 1 omc omc 1107 Nov 12 11: 16 PCU_OFST_E1. t ar 1
- r w- r - - r - - 1 omc omc 1106 Nov 12 11: 16 PCU_OFST_E1. t ar 2
dr wxr - xr - x 2 omc omc 512 Nov 12 11: 37 PCU_OFST_T1
- r w- r - - r - - 1 omc omc 1157 Nov 12 11: 16 PCU_OFST_T1. t ar
- r w- r - - r - - 1 omc omc 1107 Nov 12 11: 16 PCU_OFST_T1. t ar 1
- r w- r - - r - - 1 omc omc 1106 Nov 12 11: 16 PCU_OFST_T1. t ar 2
1--106
PE/DCL/DD/0032
411--9001--032
4. Untar thelast filerecordedbythebackup:
PCUSNname isthenameof PCUSN asPCU_OFST_E1.
. . . / SDO/ PCUdat a/ PCUOAMBackup<50>( omc) %tar xvf
PCUSNname. tar
5. AccesstodirectoryPCUSNname:
Check if thebackupfileispresent.
Theformat of thisfileisyear,month, day, hour.FXX.
. . . / SDO/ PCUdat a/ PCUOAMBackup<51>( omc) %cd PCUSNName
. . . / SDO/ PCUdat a/ PCUOAMBackup/ PCUSNname<52>( omc) %l s - l
- r w- r - - - - - 1 omc omc 1107 Nov 12 11: 16 200104051116. F01
6. For therestoringusetheServiceDataRestoretool.
Refer toNTP 241--6001--807.
1.16 Backup/Restorefor PCUOAMof PCUSNconfigurationfiles
1.16.1 Introduction
Thischapter describesthebackup/restoreonPCUOAM of PCUSN configuration
files. This functionality is provided in order to speed up PCUOAM or PCUSN
recoveryincaseof crash.
Thisbackup/restorewill bedoneinfivefunctional steps:
Step1: BackuponPCUOAM of PCUSN configurationfiles.
Step2: PCUOAM systembackup
Step3: PCUOAM configurationbackup
Step4: PCUOAM restore
Step5: PCUSN restore(viaSDR)
In the first step, the PCUSN configuration files save on PCUOAM disk daily
throughacommandinCRONTAB.
Inthestep3, thetool must allowtobackupthefollowingfiles:
PCUSN configurationfilessavedbystep1
PCUOAM configuration(declaredPCUSN, configMDM/MDP)
1.16.2.1 Capacity
The /SDO partition must have enough capacity to hold thebackup files. The
compressedbackupfilesizefor onePCUSN canbeestimatedto1MBytes. That
means100modifiedprovisioningsessionsfromtheoriginal viewfor 30PCUSN.
Oneneeds30MBytesof savedspacedisk. Thus, tobackup30PCUSNbykeeping
thelast threebackups, it isnecessarytohave90MBytesof spacedisk.
Thesizeof thebackupfor 30PCUSNviewwithMDM/MDPconfigurationcan
beestimatedat 11MBytesspacedisk.
Thesizeof thebackupfor1PCUSNviewwithMDM/MDPconfigurationcanbe
estimatedat 82MBytesspacedisk (configuredby default inthecf_save.cfg
configurationfile).
1.16.2.2 Operation
It isnecessarytomodifytheOMC installationfor theshellsandprocedures:
Creationof /CMN/config/cf_crontable_PCUOAM.cfg to declaretheperiod
of backup.
1--108
PE/DCL/DD/0032
411--9001--032
Modification of /CMN/shell/cf_start.sh and /CMN/shell/cf_stop.sh to add
PCUOAM role.
Modification of /CMN/config/cf_tasksInfo.cfg to modify the launch of
cf_start.shandcf_stop.shwiththePCUOAM role.
It is also necessary to create a directory where will be stored the backup files
(/SDO/PCUdata/PCUOAMBackup) andanother for theerror andlogfiles.
1.16.3 Step1
Theprincipleof thebackupistouploadthePCUSNconfigurationfilesthroughthe
MDMtool (if thePCUSNisdeclaredinMDM). OneachPCUSN, all theviewsare
backupedonthePCUSN. Thefiles will bebackupedintar fileformat witha
simplified version management (tar, tar1, tar2) into the PCUOAM workstation
directory, keepingthreelast backups.
It islaunchedperiodicallyviaacommandincrontab.
onsuccessful backupcompletion, thepreviousbackupisrenamed
onbackupfailure, theoldbackupisnotrenamedandanerrorisloggedinaerror
logfile
Thebackup shell usetheSDB (ServiceDataBackup) command of MDM. The
syntaxcommandisgivenin241--6001--807.
Witheachlaunching, thetool will check or create(if necessary) thelink between
the user home directory and the /SDO/PCUdata/PCUOAMBackup directory
because the SDB tool put the views of PCUSN in $HOME directory of the
pds_name onthePCUOAM as: $HOME/passport_name/backupfile.
It uses ftppcu user to uploadthePSCUSN views. Thisuser iscreatedwiththe
cf_make_user_ftppcu.sh shell describedinParagraph1.16.3.1.
ATTENTION
Thebackupshell cannot belaunchedcorrectlyif:
-- theftppcu user isnot created(creationwithcf_make_user_ftppcu.sh
shell inParagraph1.16.3.1)
-- the ftppcu password has been modified with a system command
passwd. (seecf_ftppcu_passwd.x tool inParagraph1.16.3.3)
Theftppcu user hasnoright onthePCUOAM workstationexcept thosegranted
tootherandthewritingrightin/SDS/PCUdata/PCUOAMBackupdirectoryvia
anACL. ThisACL ischeckedandset bythePCUOAM backupshell.
/CMN/base/adm/
cf_ftppcu.dat
PCUSN
/SDO/PCUdata/
PCUOAMBackup
cf_BackupPCUOAM.sh
1
2
3
ATTENTION
Inorder toavoidanabnormal backupoperation, it isimperativetonot:
-- modifythefilecf_ftppcu.dat manually; thisfileismodifiedautomatically
bythecf_ftppcu_passwd.x (SeeParagraph1.16.3.3) tool.
-- updatetheftppcu passwordwiththesystemcommandpasswd. The
cf_ftppcu_passwd.x tool (SeeParagraph1.16.3.3) modifiesit.
1. Readftppcuuser parametersfor theupload(/CMN/base/adm/cf_ftppcu.dat
filecreatedbycf_make_user_ftppcu.shshell)
2. UploadPCUSN views
3. PCUSN viewsstorage(tar format file)
Therestorationof thesefilescanbedoneby SDR (ServiceDataRestore) after to
haveuntarthePSCUNtarfile(seeParagraph1.16.3.4) anditisnotautomaticfor
securitypurpose.
Therestaurationtool usetheSDR syntaxcommandgivenin241--6001--807.
Remark for backupor restoration:
TheSDRusesswapdirectorytoperformsomeof itsfileprocessing. Thisdirectory
needstohavetwicetheamount of spaceastheactual sizeof therestoredfilesfor
restore. Theswapdirectorysizeusedcanbeestimatedto60Mbytesfor30PCUSN.
1--110
PE/DCL/DD/0032
411--9001--032
Note: Thebackupshell canbecarriedout only onceintosimultaneousbecause
withtheServiceDataBackup, only oneuser canbackupthesametarget
Passport nodeat thesametime.
1.16.3.1 cf_make_user_ftppcu.sh
Thepurposeof thisnewshell istocreatetheftppcu(Id=999bydefault) userwith
arandompassword, usedbyPCUOAM backup.
Theshell createalsothegftppcu group(Id=999bydefault) if it doesnot exist.
Theftppcu homedirectoryis/SDO/PCUdata/PCUOAMBackup.
/ CMN/ shel l / cf _make_user_f tppcu. sh - g | - u | - h | - H | - v | - V
Theoptionsare:
u : forceuidnumber
g : forcegidnumber
V or - v : returnssoftwareversionandexits
Hor - h : returnssoftwareusageandexits
Note: It canbelaunchedonlywiththeroot user except withthe--h or --v
parameters.
/CMN/base/adm/
cf_ftppcu.dat
/etc/passwd/etc/group
cf_make_user_ftppcu.sh
1
2
1. Creategftppcu groupwiththegroupadd commandsystem
Createftppcu user withtheuseradd commandsystem
2. UploadPCUSN views
1.16.3.2 cf_del_user_ftppcu.sh
The purpose of this new shell is to remove the ftppcu (Id =999) used by
PCUOAM backup. Theshell removealsothegftppcu group(Id=999) if it do
not usedbyanother user. Thefollowingcommandlineissupported:
/ CMN/ shel l / cf _del _user_f tppcu. sh - h | - H | - v | - V
Theoptionsare:
- V or - v : returnssoftwareversionandexits
- Hor - h : returnssoftwareusageandexits
parameters.
/etc/passwd/etc/group
cf_del_user_ftppcu.sh
1
1. Removegftppcu groupwiththegroupdel commandsystem
2. Removeftppcu user withtheuserdel commandsystem
1--112
PE/DCL/DD/0032
411--9001--032
1.16.3.3 cf_ftppcu_passwd.x
If theftppcuuser doesnotexist, createit. If theftppcuuser exist, beforeanypatch
installation, run/CMN/exe/cf_ftppcu_passwd.xtochangepassword.
/ CMN/ exe/ cf _f tppcu_passwd. x <password> | - h | - H | - v | - V
Theoptionsare:
passwor d : newpasswordfor theftppcuuser
parameters.
/CMN/base/adm/
cf_ftppcu.dat
/etc/passwd
cf_ftppcu_passwd.x
1
2
1. Changetheftppcu passwdwiththepasswd commandsystem.
2. Updatethecf_ftppcu.dat configurationfileusedbythe
cf_BackupPCUOAM.sh shell.
1.16.3.4 cf_untar_PCUSNview.sh
The purpose of this new shell is to untar the PSCUSN views files, created by
cf_BackupPCUOAM.sh shell, intoadirectory (PCUSN Name). It will beused
beforeaPCUSN viewsrestorationviatheSDR tools.
/ CMN/ exe/ cf _untar_PCUSNvi ew. sh - pPSCUSN_Name | - h | - H | - v | - V
Theoptionsare:
- pPCUSN_Name : Nameof tar filewithout extension, or PCUSN name
/SDO/PCUdata/Backup
PCUOAM/PCUSNview
cf_untar_PCUSNview.sh
1
2
/SDO/PCUdata/BackupP
CUOAM/PCUSN_Name
1. Readthetar fileincludingthePCUSN views.
2. WritethePCUSN viewsinto
/SDO/PCUdata/BachkupPCUOAM/PCUSN_Namedirectory.
1--114
PE/DCL/DD/0032
411--9001--032
1.16.4 Step3
Thistool must allow:
tobackupthelast PCUSN viewsfilessavedbystep1in
/SDO/PCUdata/BackupPCUOAM directory(*.tar).
to backup theMDM/MDP configurationfiles from/opt/MagellanNMS/cfg
and/opt/MagellanMDP/cfg directory.
towriteonaremotedevice.
tobeinterrogatedbyMMI viacf_save_mgr.x.
Thepossibledeviceare:
tapedevice(remote)
mountedfilesystem(local or remote(NFS) filesystem)
It canbeperformedby usinggeneral OMC ManMachineInterface(MMI) or by
usingcf_save_tool.x commandline.
cf_BackupPCUOAM_mgr cf_save_mgr
PCUSN
views
FM
PM
OMC--R
MDM/MDP
config MMI
PCUOAM
cf_save_tool
cf_save_md
cf_BackupPCUOAM.sh
PCUSN
2
3
1
Q3
existing
new(step 3)
2
S
t
e
p
1
1. : request fromcf_save_mgr
2. : uploadMDM/MDP configandPCUSN views
3. : backuptoremotemedia
1.16.4.1 cf_BackupPCUOAM_mgr
Itsaimisto:
processall messagesfromcf_save_mgr
logall backupoperation
let themediationdevicetoperformitsownoperations
backupthePCUSN viewfrom/SDO/PCUdata/BackupPCUSN directory
backuptheMDM configurationfrom/opt/MagellanNMS/cfg directory
backuptheMDP configurationfome/opt/MagellanMDP/cfg directory
writetoremotemedia
A newtypeof datawill havetobedeclaredinthefilecf_save.cfg. Thenewtype
will beBACKRET_PCUOAM correspondingtothePCUOAM backup.
Inthisheadingall thedirectoryMDM, MDPconfigurationandPCUSNviewswill
bedeclared. Thisfilewill beusedbythecf_BackupPCUOAM_mgrprocessand
alreadyusedbycf_save_mgr process.
[ BACKET_PCUOAM]
BasePat h = /
Passi veBasePat h = none
SavePat h = .
Rest or ePat h = .
/ opt / Magel l anNMS/ cf g/ *
/ opt / Magel l anMDP/ cf g/ *
/ SDO/ PCUdat a/ BackupPCUOAM/ *. t ar
#/ SDO/ PCUdat a/ BackupPCUOAM/ *. t ar 1
#/ SDO/ PCUdat a/ BackupPCUOAM/ *. t ar 2
1.16.4.2 cf_save_mgr
Thisprocessusispart of theOMC manager function.
Itsaimisto:
processall messagesfromMMI or fromcf_save_tool.x
makeall operationsthat concernmanager data
let themediationdevicetoperformitsownoperations
It candirectlyperformthefollowingoperations:
archive/restorationof themanager data
backupthehost configurationanddatabase
1--116
PE/DCL/DD/0032
411--9001--032
labeliseatape
readatapelabel
list thecontent of amedia
But for thenewfunctionalities of thestep3, it is necessary to sendarequest for
backuponthePCUOAM.
Betweenthesendingof therequesttocf_BackupPCUOAM_mgrtaskandtheend
of thebackupthecf_save_mgr will haveplaceaaccesslock tothebackuptape
or link NFS.
cf_BackupPCUOAM_mgr.x
cf_save_mgr.x
OMC--R
immediate response
PCUOAM
MMI or
cf_save_tool.x
Backup/Retreive
PCUSN views
request backup/restore
ending response
request presence test
with timeout (3mn)
request
immediate response
ending response
Backup/Retreive
MDM/MDP configuration
1.16.4.3 cf_save_md
Thisprocessispart of themediationfunction. It will beabletoreadthisnewtype
of data (BACKRET_PCUOAM) but will not return this information to the
cf_save_mgr processviaQ3, becausetherewill benomodificationonGDMO
interfacetotakeintoaccount thisnewformat.
ThetypeBACKRET informationwill besent.
Description of the OMC-R maintenance Nortel Networks Confidential 2--1
2 DESCRIPTIONOF THE OMC-RMAINTENANCE
2.1 Introduction
Themaintenanceof theOMC-R providesthefollowingfunctions:
OMC-R defenseandmonitoring
OMC-R preventivemaintenance(seeChapter 3)
OMC-R correctivemaintenance(seeChapter 4)
maintenanceproceduresassociatedwithOMC-R notifications(seeChapter 5)
ThemaintenanceprinciplesaredefinedinNTP<39>. ThisNTPalsodescribesthe
variousactionstobetakenwhenafault isdetected.
2.2 OMC-Rdefenseandmonitoring
2.2.1 Defense
2.2.1.1 Defense principles
Thesub-functioncollectsthefaultsdetectedbytheactiveapplicationsandconsults
theconfigurationfilestodeterminetheappropriateaction.
Theseactionsmaybethefollowing:
sendamessage
halt theserver
start theapplication
reboot theserver
inhibit switchover
Defenseisnot activeat start-uptime.
2.2.1.2 Defense thresholds
Thedifferent kindsof faultsareassembledastypesets.
Each type tallies with the fault occurrences during a configurable period and
triggersadefenseactionwhenreachingagivenerror threshold.
For afault of typexx, thenotification 305xx is issuedby theOMC-R. After N
occurrences(N dependsonthefault), anotification306xxisissued. TheOMC-R
actionisdescribedintheFault Number 306xx (ParagraphSYSTEM ACTION in
Chapter 5).
Description of the OMC-R maintenance
2--2
PE/DCL/DD/0032
411--9001--032
Indual-server configuration, thefollowingtableliststhefaultsandcorresponding
actions:
TYPE No FAULT ACTION
0 UNIX functions errors Restartafter 20 occurrences in last
5 minutes
1 Executing process errors Restartafter 20 occurrences in last
5 minutes
2 Semaphore errors Restartafter 20 occurrences in last
5 minutes
3 Shared memory errors Restartafter 20 occurrences in last
5 minutes
4 Memory errors faulton every occurrence
Restartafter 20 occurrences in last
5 minutes
5 TLI errors Restartafter 20 occurrences in last
5 minutes
6 Swap overflowerrors Fault generated and reboot
7 Internal Sybase errors Restartafter 10 occurrences in last
15 minutes
8 Sybase errors on active
server
Fault generated on every occurrence
switchoverafter 10 occurrences in last
15 minutes
9 Sybase errors on backup
server
Fault generated on the md object,
switchover after 10 occurrences in last
15 minutes
10 Result errors fromthe basic
software function
5 minutes
11 Result errors fromthe use of
chained lists
5 minutes
12 Result errors fromthe use
delays
5 minutes
13 Errors resulted fromthe
coding/decoding of the
events
5 minutes
14 A MD/OMC task has
disappeared
Fault generated every time the task is
called
Restartafter 10 occurrences (two if the
task is absent) in last 20 minutes
15 Transaction errors with BSC Restartafter 5 occurrences in last
5 minutes
TYPE No ACTION FAULT
16 Access disk errors on active
server
Fault generated on every read/write
operation
15 minutes
17 Network communication
errors on active server
15 minutes
18 Disk access errors on
backup server
switchoveris forbidden
19 Network communication
errors on backup server
switchoveris forbidden
20 Inter-user mail errors Restartafter 10 occurrences in last
5 minutes
21 Applicative errors Restartafter 50 occurrences in last
15 minutes
22 Oamerrors Restartafter 50 occurrences in last
15 minutes
23 Performance management
errors
15 minutes
24 Configuration management
errors
15 minutes
26 Disk array device errors An alarmindicates the malfunctioning
disk array device
27 CMIS server error Rebootafter 2 occurrences in last
5 minutes
28 Time Function Error An alarmindicates the anomaly
29 MDP data error An alarmindicates the anomaly
30 MDM service error Rebootafter 1 occurrence in last
20 minutes or
Restart after 1 occurrence in last
20 minutes
2--4
PE/DCL/DD/0032
411--9001--032
2.2.2 OMC-Rmonitoring
2.2.2.1 Monitoring principles
Themonitoringfunctiondoesthefollowing:
determines the functional role of each machine fromconfiguration files and
whether theserversarereachable
detects system malfunctions such as absent tasks, Ethernet, X.25 or OSI
problems, andamachinethat stops
executesanactionif necessary(switchover, restart, reboot)
Themonitoringfunctionusesaserial asynchronouslink betweenthetwoservers
(if Ethernet link outageoccurs).
Thefollowingtablesdescribetheactionsof themonitoringfunctionaccordingto
theproblemdetectedandthemachinestatefor several typesof configuration.
2.2.2.2 OMC/MDserver action table in configuration with disk array device
Problemdetected
Passive
state
Active
state
Action
Software problem OK Software
error
The active server acts in
accordance with the
configurable defensive
table.
Start-up problem normal
start-up
start-up
error
The active server halts
(MD/OMC applications)
and does not start. The
passive server starts in
active mode (switchover).
Start-up problem start-up
error
normal
start-up
The passive server halts
(MD/OMC applications)
and does not start. The
active server continues its
start-up. An anomaly is
generated for informing
the passive start-up
failure, the switchover is
inhibited.
A vital task disappears OK missing
task
Both servers start (they
keep their initial role) for
hoping such problem
when re-initializing. If the
start-up sequence fails,
the switchover is
triggered.
Problemdetected Action
Active
state
Passive
state
A supervision task
disappears
OK missing
task
The supervision task on
the passive server tries to
shutdown the active
server by remote
command and it restarts
as active server.
A supervision task
disappears
missing
task
OK An anomaly is generated
to report that the passive
server has disappeared.
If the passive fails in
replying to the active
server, the active server
halts.
Swap problem OK swap full If the total swap space
currently available
crosses an allowed
configurable lowthreshold
then a reboot defensive
action of active and
passive server (they keep
their initial role) is
performed for hoping
such problemdisappears
when re-initializing.
If the start sequence fails,
the switchover is
triggered.
File systemfull OK partition
full
See defence purge.
Local disk problem OK disk error The active server
performs a shutdown
defensive action.
The passive server starts
as active server
(switchover).
Local disk problem disk error disk error The active server
performs a shutdown
defensive action.
as active server
(switchover).
Local disk problem disk error OK The passive server stays
as passive server.
2--6
PE/DCL/DD/0032
411--9001--032
Active
state
Passive
state
External disk problemafter
error occurred when a
running application tries to
access to it.
disk error The active server
performs a shutdown
defensive action.
as active server
(switchover).
Problemwith optical links
connected to disk array
device.
OK disk array
device is
un
reachable
The active server
performs a shutdown
defensive action.
as active server
(switchover).
device.
disk array
device is
un
reachable
OK The switchover
mechanismis temporary
inhibited during the
access problem.
device.
disk array
device is
un
reachable
disk array
device is
un
reachable
The active server stays
as active.
Link problemon BSC
equipments:
X.25
or
Ethernet
OK at least
network
error on
one link
The active server shuts
down. The passive server
starts in active mode
(switchover) even if its
links become failed
between the shutdown
and the start-up
procedure.
Link problemon BSC
equipments:
X.25
or
Ethernet
at least
network
error on
one link
OK The switchover is
temporary prohibited
during the network error.
Link problemon BSC
equipments:
X.25
or
Ethernet
at least
network
error on
one link
at least
network
error on
one link
The active server remains
active.
Ethernet link problem OK ethernet
error
An anomaly reports the
problem.
Ethernet link problem ethernet
error
OK An anomaly reports the
problem.
Active
state
Passive
state
Ethernet link problem ethernet
error
ethernet
error
An anomaly reports the
problem.
Asynchronous link problem broken link broken link An anomaly reports the
problem.
Asynchronous link and
Ethernet link problem
broken
links
broken
links
No more communication
between both servers.
An anomaly is generated
to notify the passive
server unreachable.
Then, the passive server
starts as active server
and takes the ownership
of the set issuing fromthe
disk array device with
force.
The old active server
refuses to start because
disk belonging to disk
array device is physically
reserved by the other
server.
Brutal shutdown of the
server
OK broken There is no
communication between
the two servers. The
passive server starts in
active mode.
Brutal shutdown of the
server
broken OK No more communication
between both servers.
An anomaly is generated
to notify the passive
server unreachable.
Then, the active server
stays active.
Manual restart of the
server, the other server is
already running in active
mode
manual
restart
OK The command fails. The
active server prohibits the
asynchronous passive
server.
Manual restart of the
server, the other server is
already running in active
mode
active manual
restart
The command fails. The
ex-passive server
prohibits asynchronous
starting of the active
server.
2--8
PE/DCL/DD/0032
411--9001--032
2.2.2.3 OMC/MDsingle server action table in configuration with disk array device
Software problem The server acts in accordance with the
configurable defensive table.
Start-up problem The server reboots
(MD/OMC applications). If the next
start-up fails again, then the server
halts (MD/OMC applications) and does
not start.
A vital task disappears Start of the server for hoping such
problemdisappears when re-initializing.
If the start-up sequence fails, a reboot
is attempted.
A supervision task disappears The server keeps on working
(MD/OMC applications) in a degraded
mode. An human action is needed to
stop and start the server.
Swap problem If the total swap space currently
available crosses a allowed
configurable lowthreshold then a
reboot defensive action of server is
performed for hoping such problem
disappears when re-initializing.
If the start sequence fails, another
reboot is attempted.
File systemfull See defence purge.
Local disk problem The server starts. If the start-up
sequence fails, a reboot is attempted.
External disk problemon configuration
with disk array device, after error
occurred when a running application
tries to access to it.
The server starts. If the start-up
sequence fails, a reboot is attempted.
Link problemon BSC equipments:
X.25
or
Ethernet
The server keeps on working
(MD/OMC applications).
2.2.2.4 Actions on a workstation
Software problemon a workstation The workstation acts in accordance
with the defensive action table.
Start-up problemon a workstation The workstation shuts down (OMC
applications) and does not start.
A vital task is absent on a workstation The workstation starts.
Swap problemon a workstation If the total swap space currently
available crosses a allowed
configurable lowthreshold then a
reboot defensive action of the
workstation is performed for hoping
such problemdisappears when
re-initializing.
File systemfull on active server See defence purge
Disk problemon a workstation An anomaly is generated to report the
disk problem
Network problem
The workstation does not communicate
with the manager
An error message is displayed in the
console windowof the workstation.
An anomaly is generated by the
manager.
2--10
PE/DCL/DD/0032
411--9001--032
2.2.2.5 Actions on a disk array device
Disk problem An anomaly is generated to report the
disk error.
Double disk problem
Two associated disks to mirror data are
failed. An error occurs when a running
application tries to access to these
disks.
The MD/OMC applications acts in
accordance to its configuration.
Problemof A5XXX or T3 disk array
device
The components composing
the A5XXX or T3 are duplicated,
consequently when one component is
failed, the A5XXX or T3 stays
operational.
An anomaly reports if the A5XXX or T3
becomes no more operational.
State database replica problem When one of the state database replica
is loss, an anomaly event is generated
to notify the failed database.
OMC-R preventive maintenance Nortel Networks Confidential 3--1
3 OMC-RPREVENTIVE MAINTENANCE
3.1 Introduction
3.1.1 Listof preventivemaintenanceprocedures
Thischapter groupstogether OMC-R preventivemaintenanceprocedures:
OMC-R operational test proceduresandpreventivemaintenancewithOMC-R
units
Sybasedatabasecheck
OMC-R maintenancechecks
OMC-R preventivemaintenancebackup
3.1.2 Schedulingof OMC-Rpreventivemaintenanceoperations
The following table summarizes the scheduling of the preventive maintenance
operations.
Whento perform
theoperations
On--site
maximum
intervention
time(min.)
Operations
Daily 30 to 40 -- LEDs servers, disk array device on
the LCDpanel, tape drive
-- Sybase database check
Last four days 20 to 30 -- OMC-R daily data archiving (after
midnight)
Weekly 20 to 30
10 to 15
-- OMC-R environment data archiving
-- OMC-R maintenance checks
-- Selfs tests for Uninterruptible
Power Supply
Monthly 30 to 40
50 to 70
Between one or eight
weeks
-- Cleaning the heads of the tape
drive
Quarterly 120 to 140 -- OMC-R maintenance checks
Biannual -- Provider maintenance for
Uninterruptible Power Supply
Before and after a BSS
upgrade
30 to 40
20 to 30
OMC-R preventive maintenance
3--2
PE/DCL/DD/0032
411--9001--032
Whento perform
theoperations
Operations
On--site
maximum
intervention
time(min.)
Before and after extending
the network
30 to 40
120 to 140
20 to 30
40 to 50
-- PCU OAM configuration backup
Before and after changing
the frequency plan
30 to 40
20 to 30
Before and after an OMC-R
upgrade
140 to 160
50 to 70
70 or >120
50 to 70
(pre-check)
(post-check)
-- OMC-R file systembackup (server)
-- OMC-R file systembackup
(workstation)
20 to 30
40 to 50
(workstation)
Error detected on a BSS -- Notifications occurrence check
Each time the OMC-R is
shutdown
120 to 140 -- OMC-R maintenance checks
Before and after each major
change in the installation
and configuration of the
OMC-R
70 or >120
50 to 70
40 to 50
(workstation)
Before and after each major
change in the installation
and configuration of the
MDM/MDP
40 to 50 -- PCU OAM configuration backup
Before and after any
hardware or system
operations on OMC-R
machines
120 to 140
70 or >120
50 to 70
40 to 50
(workstation)
250 000 copies for printer -- Replace the printing cartridge and
the maintenance kit of the printer
Attentionlight flashes -- Check the cartridge drive
-- Cleaning the heads of the tape
drive
3.2 OMC-Roperational testprocedures
3.2.1 Introduction
ThisParagraphallowstheoperator todiagnosethestateof theOMC-R (bothfor
softwareandhardwareproblems), andalso to identify andcorrect or replacethe
defectivecomponent on thebasis of the notifications and alarms defined in the
previouschapter.
3.2.2 Hardwareoperational diagnostics
This Paragraphdescribes thediagnostic functions that allowtheoperationof the
OMC-R hardwaresub-assemblies to beassessed. This assessment is visual, and
consistsof interpretingthestatesof light emittingdiodes(LEDs).
3.2.2.1 OMC-R servers
Threetypesof serversareproposedUltraEnterprise45XX or 4XXX or FireV880
withoneA5XXX or twoT3disk arraydevices.
The OMC-R servers are connected to RS449/V35 interface converters for
connectiontotheX.25network.
UltraEnterprise4XXX
Visual operatingindicationsareprovidedonthefollowingcomponents:
UltraEnterpriseserver front panel
internal DAT drive
internal CD-ROM or DVD-ROM drive
SCSI busconnections
RS449/V35interfaceconverters(BlackBoxconverters)
Ultra Enterprise server front panel
TheUltraEnterpriseserver hasthreeLEDsonitsfront panel:
oneat thetopandoneat thebottom, bothof whicharegreen
oneinthemiddle, whichisyellow
3--4
PE/DCL/DD/0032
411--9001--032
Theilluminationof theLEDindicatesthestatusof theserver duringstart-up. The
followingtableprovidesasummaryof theLEDstatesandtheir meanings.
POSITION
OF LED
STATE OF
LED
CONDITION
Top
(green)
ON
OFF
-- the server is powered up
-- No Power
Middle
(yellow)
Flashing
OFF
ON
-- (For the first sixty seconds after power-up), the
self-tests are running
-- (After the tests), no hardware error has been
detected
-- (After the tests), a hardware error has been
detected
Bottom
(green)
OFF
Flashing
OFF
-- (For the first sixty seconds after power-up), the
self-tests are running
-- (After the tests), the systemis running
-- (After the tests), the systemcannot start up --
action must be taken
Theideal condition(after theself tests) isfor thetopandbottomLEDstobelit.
A lesseffectivecondition, inwhichall theLEDsarelit, indicatesthat thesystem
canoperatebut that actionneedstobetaken.
Intheworst case, whenthetopandmiddleLEDsarelit or whennoLEDsarelit,
thesystemcannot bebootedup.
DAT drive
ThegreenLEDonthefront faceof theDAT cartridgedriveindicatestheactivity
of theSCSI bus, whereastheyellowLEDindicatesapossibleerror.
CD-ROM or DVD-ROM drive
TheLEDonthefront faceof thedriveindicatesitsactivity.
SCSI bus connections
TheSCSI bus connection plugs arefitted with aLED, which must be lit under
normal operating conditions. The case of a failure is considered in the Ultra
Enterprise6XXX/5XXX/4XXX SystemsInstallationGuide.
RS449/V35 interface converters
Theseconverters(BlackBoxunits) havesevenLEDsontheir front faces, eachof
whichismarkedwithascreen-printeddesignation:
PWR isapowered-upindicator
DSR: thetwoLEDsdesignatedbythisacronymindicatethestateof theDSR
junctionof eachinterface
CTS: thetwoLEDsdesignatedbythisacronymindicatethestateof theCTS
junctionof eachinterface
DATA: thetwo LEDs designatedby this acronymarerepresentativeof the
trafficoneachinterface
Thelit stateof theLEDsindicatestheactivityof thedesignatedfunction.
A5XXX
The front panel module uses an electroluminescent display panel to display
configuration, statusanddiagnosticinformation(seeFigure 3--1)
The front panel module is equipped with a touch screen which you can use to
monitor andchangeconfigurations.
ThreeLEDsatthetopof thefrontpanel moduleshowtheoverall enclosurestatus.
TheleftLEDisthesystempower status, themiddleLEDisthesystemfaultstatus,
theright LEDisthesystemreadystatus.
POWER FAULT READY INDICATION
ON OFF OFF -- The A5XXX is powered up.
ON OFF ON -- The systemis ready.
ON OFF Flashing -- The systemis active.
N/A ON N/A -- An equipment has failed. Use the front
panel module to determine which the
equipment has failed, if necessary.
OFF OFF OFF -- No power.
3--6
PE/DCL/DD/0032
411--9001--032
63 Gb 81 Gb or 162 Gb
Disk viewscreen
Present disk
Missing disk
Legend:
Disk present and ready
Disk present and not ready
Disk not present
Disk failure
Figure3--1 A5XXXdisplay unit
3.2.2.2 Workstations
Thefour keyboardLEDsdisplay thediagnostic codesof thetestsexecutedwhen
alocal or remoteworkstationisswitchedon.
Thetest runsanddiagnosticsaredescribedindetail intheInstallationGuide.
Thefollowingparagraphsdetail theaspectsof workstationunits.
Processingunit
ThegreenLEDonthefrontpanel indicatesthattheprocessingunitisswitchedon.
CD-ROMdrive
ThereisonlyoneLEDonthefront panel of thedrivethat lightswhenthedriveis
switchedonandaCD-ROM disk isbeingread.
Floppydrive
TheLEDlightswhenafloppywriting/readingisinprogress.
DAT drive
ThegreenLEDonthefrontpanel of theDAT driveindicatesSCSI busactivity. The
yellowLEDlightsif anerror isdetected.
3.2.2.3 Printer
Theprinter hasprinted250000pages, theprinter panel will displayamessage.
It wouldthenbenecessarytochangethecartridge.
Duringthesametimetheuser wouldcleanupthefull printer.
Thecartridgehastobeperiodicallyreplacedinordertokeepagoodprintingquality.
It isimportant yourefer totheUsersGuidefor moredetailedinformation.
3--8
PE/DCL/DD/0032
411--9001--032
3.2.2.4 UPS
Eachweek, runself tests.
Batterieshavearelativelyshort lifetimeandsoneedtobepermanentlychecked.
Tothisend, themaintenanceisbasedaroundtwomainpoles.
It ishighlyrecommendedtoplanamaintenancewiththeretailer twiceayear.
Itisnecessarytocontrol onashorter periodthatthepower supplyworksproperly.
Todoso, thereisadiagnosticmenuwhichallowstotest theUPS.
Itiscrucial torunperiodicallytheself tests. Thiswill ensurethereisnofaultonthe
system.
It isimportant yourefer tothemanual of theUser for moredetailedinformation.
3.2.2.5 Xyplex Maxserver 1620 Terminal server
TheXyplexMaxserver 1620has20front panel LEDs:
CARD ON whenMemoryCardidbeingaccessed
RUN (server state):
slowflashing: normal operatingcondition
fast flashing: theself test result ispositive
LAN (network state):
on: normal operatingcondition
off: network cablenot connectedor nonetwork
flashing: incomingpackets
CONSOLE:
on: indicatesthat asessionisinprogressonalocal or remoteconsole
flashing: apermanent parameter isbeingchanged
LEDs1to10: theseLEDsindicateserver port activity:
off: noconnectionisestablishedontheport
on: aconnectionisestablishedontheport
flashing: trafficontheport
If theself-testdetectsaproblemwhentheequipmentisswitchedonorreset, itreacts
LEDs1to8displayanerror code.
The OMC-R administrator must note the numbers of the LEDs that are lit and
informthemanufacturer torequest maintenanceaction.
3.2.2.6 Multi-tech Modem
TheLEDslocatedonthefront panel of themodemindicatethefollowing:
Datareception(RCV): flashes whenthemodemis receivingdataIt gives the
stateof circuit 104onpin3of theV24interface
Datasending(XMT): flasheswhenthemodemissendingdata. Itgivesthestate
of circuit 103onpin2of theV24interface
Carrier detection (CD): lights when the modem has detected a variable
modulatedsignal.
28800bytes/s(28.8): lightswhenthemodemisconnectedat 28.8kbytes/s
14400bytes/s(14.4): lightswhenthemodemisconnectedat 14.4kbytes/s
Note: If the modemworks at 21.6 -- 26.4 kbytes/s, the two LEDs 28.8 and
24.4 flash
2400bytes/s(24): flasheswhenthemodemisconnectedat 2400bytes/s
Off-Hook(OH): lightswhenthemodemconnectstotheline, itmeanswhenitis
sendingacall, is incommunication, or replies toanincomingcall. ThisLED
flasheswhenthemodemisnumberingbydecimal pulsesintheCommandmode.
Terminal ready (DTR): lights when the modem is allowed to reply to an
incomingcall,switchesoff whenthemodemreleasestheline.
ThisLEDgivesthestateof circuit 108onpin20of theV24interface.
Call indicator (RI): lightswhenthemodemdetectsanincomingcall.
Error(ERR): flasheswhentheleasedlineinoutof orderorthemodemautomatic
testhasfailed. Whenitiscontinuouslylit, itsignalsthatthemodemhasbeenput
out of service(OOS) for incomingcalls.
Thetestsandthemaintenanceof themodemMulti-techMT2834aredescribedin
theUser Manual of thismodem.
3.2.2.7 BayStack AN router
Thefour rear panel LEDsareasfollows:
Power lightsand remainsonwhentherouter ispluggedin.
Runlightsbrieflywhenrouter ispluggedin. Flashesfor onetothreeminutes,
indicatingthatdiagnostictestsarerunning. Whenitlightsagainandremainslit,
therouter isoperational.
Boot lights briefly when the router is plugged in. Flashes for one to three
minutes, indicatingthat diagnostic tests arerunning. Whenit lights againand
remainslit, therouter isbooting.
Diaglightsbrieflywhentherouter ispluggedin. Lightsagainandremainslit,
whendiagnosticfailureoccurs.
3--10
PE/DCL/DD/0032
411--9001--032
3.2.2.8 Control the application state
Theoptioninthebackgroundscreenmenu, chooseControl thelocal application
state, providesinformationontheoperatingstateof theworkstationorserverused.
Theinformationisasfollows:
percentagefillingof thefollowingpartitions:
/
/tmp
/MD/base
/OMC
/OMC/base
/MD/data
/MD/obs
/MD/notif
/MD/trace_function
/MD/restored/notif
/MD/restored/obs
/MD/restored/trace_function
/MD/ssn
/OMC/obs
/OMC/data
swapspacefillinginrelationtoitsmaximumcapacity
indicationof SYBASE server state
softwarerunningstate(correct or not correct)
OSIMCSstate
station/server link state
Note: The /OMC/base, /OMC/obs, /OMC/data partitions and all /OMC
sub-partitionsareonlyindicatedontheactiveserver.
TheinformationispresentedseeFigure 3--2andFigure 3--3.
MmiDisplayMessageBuilder
--------------------------------------------------------------------------------------------------------------
Graphicworkstationstatus(aruba)
--------------------------------------------------------------------------------------------------------------
Partition/ of 288391kbytes( 55%used).
Partition/OMC of 240399kbytes( 57%used).
Partition/tmpof 157760kbytes( 1%used).
Diskswapspace: 148304kkoctetsused, 159940kkoctetsavailable.
Thegraphicworkstationisoperational.
All thetasksarerunning(9task(s)).
--------------------------------------------------------------------------------------------------------------
Manager/MD--R server status(sein)
--------------------------------------------------------------------------------------------------------------
Partition/MD/baseof 96031kbytes( 79%used).
Partition/OMC/baseof 139479kbytes( 90%used).
Partition/MD/dataof 403935kbytes( 38%used).
Partition/MD/obsof 2332108kbytes( 2%used).
Partition/MD/notif of 356687kbytes( 82%used).
Partition/MD/trace_functionof 76967kbytes( 1%used).
Partition/MD/restored/notif of 192807kbytes( 1%used).
Partition/MD/restored/obsof 1099006kbytes( 1%used).
Partition/MD/restored/trace_functionof 38111kbytes( 1%used).
Partition/MD/ssnof 144799kbytes( 1%used).
Partition/OMC/obsof 7043638kbytes( 1%used).
Partition/OMC/dataof 1580669kbytes( 22%used).
SYBASE server isrunningonthisserver.
TheManager/MD--R isoperational.
Osimcstaskisrunning.
TheManager/MD--R server isfittedwithdiskarraydevice.
Figure3--2 Exampleof theworkstationandactiveserver status
3--12
PE/DCL/DD/0032
411--9001--032
----------------------------------------------------------------------------------------------------------
----Passiveserver status(rangiroa)
----------------------------------------------------------------------------------------------------------
----
Partition/MD/baseof 96031kbytes( 72%used).
Partition/OMC/baseof 139479kbytes( 87%used).
TheManager/MD--R isoperational.
Thistest iscompleted.
MmiDisplayMessageBuilder
Figure3--3 Exampleof thepassiveserver status
3.2.3 Preventivemaintenancefor eachOMC-Runit
Preventivemaintenancefor theOMC-R equipment is describedinthefollowing
paragraphsandinthesheetsof external documents:
3.2.3.1 Servers
UltraEnterprise45XX
UltraEnterprise6500/5500/4500SystemsManual
Reference: 805-2632-10
UltraEnterprise4XXX
UltraEnterprise6000/5000/4000SystemsManual
FireV880
FireV880server serviceManual
StorEdgeT3DiskTray
Installation, operationsandServiceManual
Reference: 806-1062
StorEdgeA5000
InstallationandServiceManual
Tapedrive
DDSTapedrive(InstallationandUsersGuide)
SeeSheet 1Cleaningtheheadsof theDDStapedriveandSheet 2Checkof the
DDScartridgedrive.
3--14
PE/DCL/DD/0032
411--9001--032
3.2.3.2 Workstations
DDSTapedrive(InstallationandUsersGuide)
SeeSheet 1Cleaningtheheadsof theDDStapedriveandSheet 2Checkof the
DDScartridgedrive.
3.2.3.3 Uninterruptable Power Supply
APC MATRIX UPS(UsersManual)
Reference: 990-7008-B
3.2.3.4 Printer T612n
Lexmark (UsersGuide) onWWW
Reference: http://www.lexmark.com/publications/pdfs/optrat/usUser.pdf
Preventivemaintenancefor eachOMC-Runit
Sheet 1 Cleaningtheheads of theDDS tapedrive
Productreference
Thisprocedureappliestotheserversandtotheworkstationsequippedof DDSdrive
of theOMC-R.
SUN product reference: aDDSapprovedcleaningtapecartridge.
Schedule
Performthiscontrol:
whentheAttention light flashes.
or thefollowingtable:
Number of DDS cartridge used each day Cleaning interval
1 or less 8 weeks
2 4 weeks
3 3 weeks
4 1 week
Impact
DANGER
Personnel safetyrules
For this procedure:
keep cartridge away fromanything magnetic
store cartridge in a dust-free environment
keep cartridge away fromsource of heat
do not open
do not touch the surface of tape
the cleaning cartridge is good for 24 cleanings
do not rewind the cleaning cartridge
3--16
PE/DCL/DD/0032
411--9001--032
Interventiontime
Theinterventiontimeisapproximately15secondsper cleaning.
TheDAT driveisshowninFigure 3--4.
Tool required
None
Preliminaryoperation
Check that thelightsActivity andAttention areoff.
Cleaning
Insert thecartridgewithwrite-protection.
Pushgentlyonthetapeuntil theunit pullsthecartridgeintothedrive.
Thedriverecognizesthecleaningcartridge.
Wait theendof thecartridgescrolling.
Additional operations
Thedriveeject thecartridge.
Removethecleaningcartridge.
Whenyouarefinishedstorethecartridgeintheprovidecase.
Sheet 2 Checkof theDDS cartridgedrive
Rangeof application
Thisprocedureappliestotheserversandtotheworkstationsequippedof DDSdrive
of theOMC-R.
Product reference: DDS.
Schedule
Performthischeck whentheAttention light flashes.
Impact
Onthecleaningor usedtape.
Interventiontime
Theinterventiontimeisapproximately5seconds.
TheDAT driveisshowninFigure 3--4.
Tool required
A DDSapprovedcleaningtapecartridge.
Preliminaryoperation
Check that thelight Attention flashes.
Action
Cleaningthedriveseesheet: Cleaningtheheadsof theDDStapedrive.
Insert theprevioustape.
If thelight isflashing, copythedataontoanewtapeanddiscardtheoldone.
Otherwisethereisnoneedtoreplacetheprevioustape.
3--18
PE/DCL/DD/0032
411--9001--032
Activity
Write-protect switch Unload button Attention
Figure3--4 DAT drive
3.3 Preventivemaintenanceprocedures
This paragraph lists all the procedures of preventive maintenance in alphabetic
order.
A brief descriptionisgivenfor eachprocedure, aswell asitsreference.
3.3.1 OMC-Rmaintenancechecks
3.3.1.1 Purpose
The series of checks in this procedure allow users to check the sanity of an
operational OMC-R systemandtopurgeall possibleextrafiles.
This procedure does not include actions that may be required to fix anomalies
(see Paragraph4.2.2).
If yourequireassistance, contact themanufacturer.
3.3.1.2 Scope
Thisprocedureisvalidfor:
theV15OMC-R release
thearchitectureof theOMC-R server: E4XXX
themodel of OMC-R server(s): E4XXX withA5000/T3
This procedure is applicable to OMC-R server(s) without graphic screen or
keyboard, but alsotoOMC-R server(s) withagraphicscreenandakeyboard.
Thisproceduredoesnotexplainhowtoaddortoremovethegraphicscreenandthe
keyboardfromanOMC-R server.
3.3.1.3 Reference
Refer toOMC-RmaintenancechecksaccordingtoDS/OMC/APP/0024.
3--20
PE/DCL/DD/0032
411--9001--032
3.3.2 OMC-Rpreventivemaintenancebackup
3.3.2.1 Purpose
Theaimof thisdocument istodescribethedifferent typesof backupthat must be
performedtosavedataor configurationof theOMC-R, theprocedurestoperform
them, andtheschedulingfor eachof them.
Preventivebackupcanbeperformedonfour typesof data, for eachconfiguration
of theOMC--R server:
For E4XXX configuration:
UNIX file systemused to save the content of the applicative and system
partitionsof anOMC-R machine(server or OMC-R workstation)
OMC-R environment data (network or OMC-R configuration or also file
system)
OMC-R dailydata
PCU OAM configuration(MDM/MDP andPCUSN configurationfiles)
TheSDSconfigurationbackupsthediskpartitioning, theconfigurationandthe
applicativetreeonfile-systems
For SFV880configuration:
OMC--R filesystem
OMC-R environment data
OMC-R dailydata
MDM configuration
Eachdatabackupcanberestoredseparatelyfor someparticular uses:
previousdailydataconsultation(notifications, alarms, ...)
specificBDE (i.e. network andOMC-R configuration) restoration
For aglobal restorationprocedure, theoperator will needtofollowtheinstructions
describedinParagraph4.2.1.
3.3.2.2 Scope
ThisprocedureisvalidfromV14(anyeditions) OMC-R release.
Thisprocedureisvalidfor themodel of OMC-R servers(SunE4XXX).
keyboard, butalsotoOMC-Rserver(s) withagraphicscreenandakeyboard. This
proceduredoes not explainhowto add or to removethegraphic screen andthe
3.3.2.3 Reference
Refer to OMC-R preventive maintenance backup according to
DS/OMC/APP/0016.
3--22
PE/DCL/DD/0032
411--9001--032
3.3.3 Sybasedatabasecheck
3.3.3.1 Purpose
Thepurposeof thisprocedureistocheckthelogical andphysical coherenceof the
OMC-R server databases.
If any errors are detected, the tool can also be run to repair them
(see Paragraph 4.2.2).
3.3.3.2 Scope
Thecheck tool managesthemodel of E4XXX/SFV880OMC-R servers.
keyboard, butalsotoOMC-Rserver(s) withagraphicscreenandakeyboard. This
3.3.3.3 Reference
E4XXXserver
Refer toSybasedatabasecheck&fixaccordingtoDS/OMC/APP/0012.
OMC-R corrective maintenance Nortel Networks Confidential 4--1
4 OMC-RCORRECTIVE MAINTENANCE
4.1 Preliminaryinformation
CAUTION
Equipmentdamage
Follow the preliminary tests before the corrective maintenance
procedures.
Thecorrectivemaintenanceproceduresare:
global restorationof theOMC-R system
fixingof theSybasedatabase
disk arraydevicemaintenance
maintenanceproceduresassociatedwithOMC-R notifications(seeChapter 5)
4.1.1 Prerequisite
Onetechnicianmust befamiliar withtheUNIX systemandOMC-R commands.
4.1.2 Preliminarytests
SeeFigure 4--1for aflowchart of thepreliminarytests.
OMC-R corrective maintenance
4--2
PE/DCL/DD/0032
411--9001--032
Check the messages,
check the partitions
check the notification flow,
check the bscMdInterface status
Preliminary tests
NOT START UP
Call the manufacturer
No
OMC--R application is present?
Name -- Role of each machine
Current date/time Check the LEDs
boot
Launch cf_test_appli.sh and
check the availability of memory
Launch zap.sh
OBP is present?
Yes
UNIX is present?
No
Yes
No
Yes
Figure4--1 Flowchartof thepreliminary tests
4.1.3 Checks
4.1.3.1 Take note of the name and the role of each machine and the current date/time.
SiteName, date/time...
4.1.3.2 Check if the machines are powered off or completely blocked.
4.1.3.3 Check the LEDs on the front of the machines.
SeeParagraph3.2.
4.1.3.4 Check the OMC-R application is present.
If theOMC-R applicationisnot present andif OBP is present, seethefollowing
operatingsystembootfromOBPwithout argument:
A consoleterminal onthemachineisavailable. If theserver iswithoutscreen
and keyboard, the deported console is available on the supervisory
workstation.
Boot thesystem:
On t he consol e t er mi nal of t he machi ne:
<#. > ok boot
If the OMC-R application is not present and if OBP is not present, call the
manufacturer.
4.1.3.5 Check the UNIX command is present.
If theUNIX commandisnot present, call themanufacturer withoutstart.
If theUNIXcommandispresent,checkthemessages, thepartitions, thenotification
flow and the bscMdInterface status, launch the application test and check the
availablememory, savethefilesonagigatapeor DAT.
4.1.3.6 Check the messages:
Onthepreferential activeserver consolewindowandtheworkstations:
<- - - Runni ng sequence - dd/ mm/ yy hh: mm: ss - - - >
Andthemessageonthepreferential passiveserver consolewindow:
<- - - Exi t sequence - dd/ mm/ yy hh: mm: ss - - - >
4.1.3.7 Check the partitions
machine.
4--4
PE/DCL/DD/0032
411--9001--032
2. Enter thefollowingcommand:
Under omc l ogi n on t he machi ne:
. . . ( omc) %df - k
Fi l e syst em kbyt es used avai l capaci t y Mount ed on
/ dev/ dsk/ c0t 3d0s0 288855 217234 42736 84% /
/ pr oc 0 0 0 0% / pr oc
f d 0 0 0 0% / dev/ f d
/ dev/ dsk/ c0t 3d0s3 184447 11179 154824 7% / var
/ dev/ dsk/ c0t 3d0s6 253039 3375 224361 2% / home
/ dev/ dsk/ c0t 3d0s4 492351 207485 235631 47% / OMC
/ dev/ dsk/ c0t 3d0s5 480919 9 432819 1% / mi sc
swap 217460 12 217448 1% / t mp
4.1.3.8 Check the flowof the notifications:
GOTO OMC-R Browser
SELECT Fault -- Showalarmsfor all network elements
Control thereceptiondate/timeof thelast receivednotification.
SET Close
4.1.3.9 Check the bscMdInterface object status:
GOTO OMC-R Browser
SELECT_OBJ bscMdInterface
SELECT Object -- Display/Set
Check theadministrativeStatestatus: lockedor unlocked.
SET Close
4.1.3.10 Control the application state:
Choose in the background screen menu, Control the local application state,
providesinformationontheoperatingstateof theworkstationor server used.
OR
machine.
2. Enter the following command on the machine to check if the OMC-R
applicationisrunning:
. . . ( omc) %/ CMN/ base/ shel l / cf _test_appl i . sh
SeeFigure 3--2andFigure 3--3.
4.1.3.11 Check the available memory:
1. Enter the following command on the machine to check if the OMC-R
applicationisrunning:
. . . ( omc) %swap - s
2. The result (used value) / (used value +avilable value) is smaller
than 90%:
84600k x 100 / (84600k +5219516k) =27.8% <90%
t ot al : 71940k byt es al l ocat ed + 12660k r eser ved = 84600k used,
219516k avai l abl e
4.1.3.12 Save the files on a gigatape:
machine.
CAUTION
Do notlaunchthezap.shtool beforethebackupof thefiles.
Enter thefollowingcommandsfor saveonDAT:
. . . ( r oot ) # cd / home/ omc/ zap
. . . ( r oot ) # tar cvf / dev/ rmt/ 0
zap_<host name>_<YYYYMMDD>_<hhmm>.
*

4--6
PE/DCL/DD/0032
411--9001--032
Enter thefollowingcommandfor displaythefilelist ontheDAT:
. . . ( r oot ) # tar tvf
Logout of root, if necessary.
. . . ( r oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
2. After enter thefollowingcommand, if necessary, onthemachinetocheck:
. . . ( omc) %/ CMN/ base/ tool s/ shel l / zap. sh - a
Thewholebackupmaybeverylong.
Without option, thetool executeonthelocal machine.
With--aoption:
fromaserver: thetool isexecutedoneachmachineof theconfiguration
fromastation: thetool isexecutedonserversandthisstation
Enter --hFULL optionfor moreinformation.
Result files
The tool generates a result filein HOME directory of omc user for example
/home/omc/zap:
zap_<hostname>_<YYYYMMDD>_<hhmm>.tar
andafile:
zap_<hostname>_<YYYYMMDD>_<hhmm>.log
Withhostnametheserver nameandYYYYMMDD, hhmmrepresentingrespectively
theyear, thedateandthetimeof execution.
4.1.3.13 Launch the automatic check:
1. If not alreadydone, openaUNIX windowandloginascr oot user, onthe
machine.
CAUTION
Serviceinterruption
The OMC-R application is not running.
2. TheOMC-Rapplicationisnotrunningtheds_check. shtool checksthefile
rightsof thefilesystemmountpointsandrequirestounmountall softwarefile
systems and others. For that reason, ensurethat no other user or process is
loggedin.
3. Enter thefollowingcommandonthemachinetocheck.
4--8
PE/DCL/DD/0032
411--9001--032
##############################################################
OMC- R Conf i gur at i on Check
COMMAND LI NE : / usr / l ocal / oam/ bi n/ ds_check. sh - Dal l
HOSTNAME : t ul i pe
HARDWARE NAME : Sun4u
OPERATI NG SYSTEM : SunOS 5. 5. 1
DATE : 24- 04- YY 18: 07: 30
CHECK RELEASE : Vxx_yy. Ezz
LOG FI LE : / var / l ocal / oam/
ds_check_l og_180729. 19YY0424
##############################################################
**************************************************************
* HARDWARE CONFI GURATI ON *
**************************************************************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Check pr ocessor s_st at e . . done
SUCCESS : check ser ver f ai l ed on t est pr ocessor s_st at e
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
. . .
**************************************************************
* SYSTEM CONFI GURATI ON *
**************************************************************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Check packages . . done
SUCCESS : check ser ver passed on t est packages
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
. . .
**************************************************************
* COMMUNI CATI ON LAYER CONFI GURATI ON *
**************************************************************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Check X25_conf i gur at i on . . done
SUCCESS : check ser ver passed on t est X25_conf i gur at i on
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
. . .
**************************************************************
* APPLI CATI ON LAYER CONFI GURATI ON *
**************************************************************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Check omcr _host s_access . . done
SUCCESS : check ser ver passed on t est omcr _host s_access
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
. . .
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
GLOBAL STATUS
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SUCCESS : check ser ver al l
DATE : 24- 04- YY 16: 08: 36
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
4. Checkthat theglobal statusisSUCCESS. If aproblemisdetected, seewhich
check is in ERROR or WARNING. An error message should help the
investigation.
5. You can take a copy of the ds_check. sh log file
ds_check_l og_<hhmmss. yyyymmdd> inthe/ var / l ocal / oamdirectory.
6. Logout of croot, if necessary.
Under cr oot l ogi n:
. . . ( cr oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
4.1.3.14 Locate the problemdate/time on a diagram:
Thedifferent sequencesof asuccessfull start-upontheOMC-Ractiveserver are:
1 initializationsequence: themachinesareinitializedandthecommon
configurationfilesareread
2 synchronizationsequence: thepartitionsaremountedonthe
meta-devicesandother, thememoryischeckedandtheserversare
synchronized
3 tasksActivationsequence: Sybaseisexecuted, thedatatablesare
controlled, thetasksareactivetedandthedifferentsmanagersare
initialized
4 tasksSynchronisationsequence: sometasksaresynchronizedtogether
5 tasksStartupsequence: thisstepstartstheOMC-R tasks
6 runningsequence: thestart-upisfinished, theOMC-R applicationis
ready
Thedifferentsequencesof asuccessfull start-upontheOMC-Rpassiveserver are:
1 initializationsequence: themachinesareinitializedandthecommon
configurationfilesareread
2 synchronizationsequence: themeta-devicesaremounted, thememory
ischeckedandtheserversaresynchronized
3 tasksActivationsequence: Sybaseisexecuted, thedatatablesare
controlled
4 exit sequence: Thepassiveserver isready, it isonstand-by
Thedifferent sequencesonastopof theOMC-R server are:
1 stopRunningsequence: thisstepstopstheOMC-R tasks
2 exit sequence: thisstepstopstheOMC-R application
4--10
PE/DCL/DD/0032
411--9001--032
machine.
2. Enter thefollowingcommandonthemachinetocheck:
. . . ( omc) %cd / CMN/ base/ di agnosti c
. . . ( omc) %l s - al
. . .
- r w- r - - - - - 1 omc omc 395 J an 25 11: 37 di ag_def ence
- r w- r - - - - - 1 omc omc 395 J an 25 11: 16 di ag_def ence~
. . .
- r w- r - - - - - 1 omc omc 8687 J an 25 17: 55 di ag_i ni t
- r w- r - - - - - 1 omc omc 6199 J an 25 11: 17 di ag_i ni t ~
. . .
- r w- r - - - - - 1 omc omc 80 J an 25 11: 36 di ag_sup
- r w- r - - - - - 1 omc omc 149 J an 25 11: 17 di ag_sup~
. . .
Take down the date/time of files: diag_defence, diag_defence~, diag_init,
diag_init~, diag_supanddiag_sup~.
3. Enter thefollowingcommandonthemachinetocheckandnotethedate/time:
. . . ( omc) %more di ag_i ni t
<- - - 1 - I ni t i al i zat i on sequence - 01/ 25/ 00 11: 36: 04 - - - >
. . .
<- - - 2 - Synchr oni zat i on sequence - 01/ 25/ 00 11: 37: 06 - - - >
. . .
<- - - 3 - TasksAct i vat i on sequence - 01/ 25/ 00 11: 37: 07 - - - >
. . .
<- - - 4 - TasksSynchr oni zat i on sequence - 01/ 25/ 00 11: 38: 54 - - >
. . .
<- - - 5 - TasksSt ar t up sequence - 01/ 25/ 00 11: 38: 57 - - - >
. . .
<- - - 6 - Runni ng sequence - 01/ 25/ 00 11: 39: 02 - - - >
. . .
<- - - 7 - St opRunni ng sequence - 01/ 25/ 00 17: 54: 47 - - - >
. . .
<- - - 8 - Exi t sequence - 01/ 25/ 00 17: 55: 24 - - - >
DrawadiagramseeFigure 4--2.
. . . ( omc) %more di ag_i ni t~
<- - - 1 - I ni t i al i zat i on sequence - 01/ 25/ 00 10: 15: 04 - - - >
. . .
<- - - 2 - Synchr oni zat i on sequence - 01/ 25/ 00 10: 15: 06 - - - >
. . .
<- - - 3 - TasksAct i vat i on sequence - 01/ 25/ 00 10: 15: 06 - - - >
. . .
<- - - 4 - TasksSynchr oni zat i on sequence - 01/ 25/ 00 10: 15: 54 - - - >
. . .
<- - - 5 - TasksSt ar t up sequence - 01/ 25/ 00 10: 15: 57 - - - >
. . .
<- - - 6 - Runni ng sequence - 01/ 25/ 00 10: 16: 02 - - - >
. . .
<- - - 7 - St opRunni ng sequence - 01/ 25/ 00 11: 16: 47 - - - >
. . .
<- - - 8 - Exi t sequence - 01/ 25/ 00 11: 17: 24 - - - >
DrawadiagramseeFigure 4--2.
4--12
PE/DCL/DD/0032
411--9001--032
. . . ( omc) %more di ag_def ence
Tue J an 25 11: 37: 41 2000 Common f unct i on ( sour ce: cf _def . c -
l i ne: 3336) Thr ead Number : 1
War ni ng : MD conf i g f i l e not f ound ( f i l ename: / MD/ base/ conf i g/
cf _def _md. cf g)
The conf i g f i l e / OMC/ base/ conf i g/ cf _def _omc. cf g i s l oaded
VERSI ON: Vxx_yy. zz
cf _def . x : I ni t i al st ep compl et ed
def ence : NORMAL I NI T
Check thedate/timeandinformation.
. . . ( omc) %more di ag_def ence~
War ni ng : MD conf i g f i l e not f ound ( f i l ename: / MD/ base/ conf i g/
cf _def _md. cf g)
The conf i g f i l e / OMC/ base/ conf i g/ cf _def _omc. cf g i s l oaded
cf _def . x : I ni t i al st ep compl et ed
def ence : NORMAL I NI T
Stop
running
1
diag_defence ~
11:16
diag_sup ~
11:17
6 7 6 7
1
10:15 11:17 11:36 11:39 17:55 t
Exit Exit
8 8
Running
diag_defence
11:37
diag_sup
11:36
diag_init ~
jan 25 11:17
diag_init
jan 25 17:55
11:16 10:16 17:54
Initialization
Begin of OMC--R
application start--up
Sequences
Possibly last
reboot
Figure4--2 Date/timediagram
4--14
PE/DCL/DD/0032
411--9001--032
. . . ( omc) %more di ag_sup
St ar t up compl et ed
/ CMN/ base/ exe/ cf _sup. x : NORMAL I NI T
. . . ( omc) %more di ag_sup~
st ar t up compl et ed
/ CMN/ base/ exe/ cf _sup. x : NORMAL I NI T
/ CMN/ base/ exe/ cf _sup. x : Task st opped at Tue J an 25 11: 17: 08 2000
9. Possiblyenter thefollowingcommandonthemachinetocheckthelastUNIX
reboot:
. . . ( omc) %l ast reboot
r eboot syst emboot Thu J an 11 15: 36
r eboot syst emboot Thu J an 11 14: 15
. . .
Thefirst dateisthelast reboot, theseconddateisthenext tolast reboot.
4.1.3.15 Call the manufacturer
4.2 Correctivemaintenanceprocedure
This paragraph lists all the procedures of corrective maintenance in alphabetic
order.
A brief descriptionisgivenfor eachprocedure, aswell asitsreference.
4.2.1 OMC-Rsystemglobal restoration
4.2.1.1 Purpose
Thisproceduredescribestheoperationsperformedto:
restore the complete configuration of an OMC-R system(preferential active
server, preferential passiveserver, or OMC-Rworkstation). Thisprocedurecan
beuseful in caseof major sinister on systems (disk crashfor example). This
restorationprocedureisthecomplement of thebackupproceduredescribedin
OMC-R preventivemaintenancebackup (seeParagraph3.3.2)
re-install the OMC-R database when one or both OMC-R servers detect a
databaseproblemandshutdown. beforemakeare-installationprocedure, repair
thedatabases(seeParagraph4.2.2)
Contact themanufacturer, if necessary.
4.2.1.2 Scope
Thisprocedurecanberuneither onaworkstationor onaserver.
Thisprocedureisvalidforthemodel of OMC-Rserver(s): E4XXXwithA5000/
T3.
Thisprocedureisapplicableto:
OMC-R server(s) without graphicscreenor keyboard
OMC-R server(s) withgraphicscreenandkeyboard
PCU OAM server without graphicscreenor keyboard
PCU OAM server withgraphicscreenandkeyboard
Maximuminterventiontime
Preliminaryoperations: 10min. to15min.
Local filesystemrestorationtotheE4XXX server: 70min. to80min.
Disk arraydevicerestoration: 200min. to220min.
4--16
PE/DCL/DD/0032
411--9001--032
Databasere-installationandenvironment restoration
onbothE4XXX servers: 240min. to260min.
Databasere-installationandenvironment restoration
onapreferential activeE4XXX server: 50min. to60min
OMC-R dailydatarestoration: variable.
OMC-R workstationrestoration: 70min. to80min.
PCU OAM configurationrestoration: 50min. to60min.
Last operation: 10min. to20min.
4.2.1.3 Reference
Refer toOMC-Rsystemglobal restorationaccordingtoDS/OMC/APP/0017.
Refer toOMC-Rdatabasere--installationaccordingtoDS/OMC/APP/0013.
4.2.2 Sybasedatabasefix
4.2.2.1 Purpose
Thepurposeof this procedureis to fix thelogical andphysical coherenceof the
OMC-R server databases.
If anyerrorsaredetected, thetool canalsoberuntorepair them.
4.2.2.2 Scope
Thecheck tool managesthemodel of E4XXX OMC-R servers.
This procedure is applicable to OMC--R server(s) without graphic screen or
keyboard, butalsotoOMC--Rserver(s) withagraphicscreenandakeyboard. This
keyboardfromanOMC--R server.
Maximuminterventiontimeis30minutesto40minutes.
4.2.2.3 Reference
Refer toSybasedatabasecheck&fixaccordingtoDS/OMC/APP/0012.
4.3 A5XXXdiskarraydevicemaintenance
4.3.1 Purpose
This proceduredescribes theoperations to performwhenanA5XXX disk array
deviceisout of service.
CAUTION
EquipmentDamage
Contact the manufacturer, if necessary.
4.3.2 Scope
Thisprocedureisvalidfor theV14andV15OMC--R releases.
4.3.3 Scheduling
Thisprocedureisperformafter:
asystemhardwarefailure
adisk crash
theA5XXX brokenfunction
ThisprocedureisperformonA5XXX disk arraydevicefollowing:
notificationreception
A5XXX displayunit
disconnectedfibre
power off
4--18
PE/DCL/DD/0032
411--9001--032
4.3.4 Prerequisite
Onetechnicianmustbefamiliar withtheUNIX system, OMC--Rcommandandthe
A5XXX hardware.
Youmust knowtheOMC--R root or croot user password.
ThePE_SSA_MAINT product isdownloadontheserver whichownsthediskset.
4.3.5 Systemimpact
CAUTION
Serviceinterruption
An A5XXX disk array device has to be repaired, the OMC--R
applicationmust not be stoppedandrestarted onthe bothservers
or on the server.
4.3.6 Actions
4.3.6.1 Broken disk
Seetheflowchart Figure 4--3.
Check theA5XXX displayunit.
Analyzethe30526 notifications:
String1: Submirror DISKSET1/d(xx+1 or xx+2) of themirror DISKSET1/dxx
hasanunknownstatus
String2:Submirror DISKSET1/d(xx+1 or xx+2) of themirror DISKSET1/dxx
needsmaintenance
String3: Replicas arecorruptedondevice/dev/dsk/cxtydz ; replicas haveto be
deletedandrecreatedonthisdevice.
String4:All thesubmirrorsandreplicasareokay (notificationend)
If anerror isinitiatedwithstring1or 2:
Launchtherebuildmirror.shtool.
If it isOK. Thestepisfinished.
If itisnotOK. ContactthemanufacturerandtheSunmaintenanceforreplacethe
brokendisk. Whenthepersonsarepresent, executetherepair_A5000.shtool.
Check thenotificationendwithstring4.
If theerror isinitiatedwithstring3:
Repair the broken replicas by executing the repair_db.sh tool. Check the
notificationendwithstring4.
If it isOK. Thestepisfinished.
If itisnotOK. ContactthemanufacturerandtheSunmaintenanceforreplacethe
brokendisk. Whenthepersonsarepresent, executetherepair_A5000.shtool.
Check thenotificationendwithstring4.
4--20
PE/DCL/DD/0032
411--9001--032
Check the sub--mirrors
No
Disks are present?
Check the display unit
(sheet 1)
String 1 or 2?
Launch rebuildmirror.sh
(sheet 3)
Yes
Launch repair_db.sh
(sheet 4)
Analyze of the 30526 notification
(sheet 2)
Broken disk
String 3
Check the replicas
Launch repair_A5000.sh
(sheet 5)
CAUTION
No
Yes
OK
No
Yes
End
Figure4--3 Flowchartof theA5XXXbrokendisk
4.3.6.2 The A5XXX broken function
If thepower supply is off, or if afibreis disconnectedor oneproblemonGBIC
interface, restorethepowersupplyorreconnectthefibre. Waitthediskarraydevice
rebootsandchecksthedisplayunit.
Seetheflowchart Figure 4--4.
Analyzethe30526 notifications.
CAUTION
Serviceinterruption
The OMC--R application must not be stopped.
Executetherebuildmirror.shtool for synchronizetheA5XXX disk arraydevice.
CAUTION
EquipmentDamage
The OMC--R application starts or reboots.
IntheA5XXX DISKSET owner, therearethereplicasplusone.
Executethestat_db.shtool for check thereplicasareunknown.
Check format </dev/null for check all disksarepresent.
If all disksarepresent, executerepair_db.shtool for repair thebrokenreplicasand
rebuildmirror.shfor synchronizetheA5XXX disk arraydevice.
If all disksarenot present, call themanufacturer.
4--22
PE/DCL/DD/0032
411--9001--032
The A5XXX broken function
Fibre OK
Analyze of the notification
String 1 or 2
(sheet 2)
Check format </dev/null
(sheet 7)
End Call the manufacturer
Launch stat_db.sh
(sheet 6)
Launch rebuildmirror.sh
(sheet 3)
All disks are present?
Launch repair_db.sh (sheet 4)
and rebuildmirror.sh (sheet 3)
CAUTION Yes
No
Start up or reboot?
CAUTION
CAUTION Yes
No
End
Figure4--4 Flowchartof theA5XXXbrokenfunction
4.3.7 Sequencetables
4.3.7.1 Broken disk string 1 or 2
StepOperationdescription min. Sheet no. OK or
NOK
Input parameters
THE OMC--RAPPLICATIONIS RUNNING
1 Check the A5XXX display unit 2 1
2 Analyze the notifications 2 2
3 String 1 or 2:
launch the rebuildmirror.sh tool
2
3
c<x>= c0 or c1
4 String 3:
launch the repair_db.sh tool
2
4
c<x>t<y>d<z>s<?>
CALL THE MANUFACTURER
5 Repair the A5XXX broken disk:
launch the repair_A5000.sh tool
Removal and reinsertion of the disk (Sun intervention)
5
c<x>t<y>d<z>
6 Check the notifications: string 4 2 2
THE OMC--RAPPLICATIONIS RUNNING
THE A5XXXDISKARRAY DEVICE IS RUNNING
4--24
PE/DCL/DD/0032
411--9001--032
4.3.7.2 The A5XXX broken function
StepOperationdescription min. Sheet no. OK or
NOK
Input parameters
THE OMC--RAPPLICATIONIS RUNNING AND
THE OMC--RAPPLICATIONMUST NOT BE STOPPED
1 Analyze the notifications 2 2
2 String 1 or 2:
launch the rebuildmirror.sh tool
2
3
c<x>= c0 or c1
THE OMC--RAPPLICATIONRESTARTS ORREBOOTS
3 Launch the stat_db.sh tool 2 6
4 Check if the disks are present: format </dev/null 2 7
5 Launch repair_db.sh tool 2 4
c<x>t<y>d<z>s<?>
6 Launch the rebuildmirror.sh tool 2 3
c<x>= c0 or c1
CALL THE MANUFACTURER
THE OMC--RAPPLICATIONIS RUNNING AND
THE A5XXXDISKARRAY DEVICE IS RUNNING
4.3.8 Sheets
1. Check thedisplayunit of theA5XXX disk arraydevice
2. Analyzeof thenotifications
3. rebuildmirror.shtool
4. repair_db.shtool
5. repair_A5000.shtool for A5XXX disk arraydevice
6. stat_db.shtool
7. Check format </dev/null withA5XXX disk arraydevice
4--26
PE/DCL/DD/0032
411--9001--032
A5XXXdiskarraydevicemaintenance
Sheet 1 ChecktheA5XXXdisplayunit
Presentation
Thepurposeof thissheetistoexplainthefunctionsof theA5XXXdiskarraydevice
displayunit.
Initial status
TheA5XXX disk arraydeviceispowered.
Actions
A5XXXdiskarraydevice
The front panel module uses an electroluminescent display panel to display
configuration, status, diagnosticinformation.
Check:
If thedisksarepresent, check thenotification.
If thedisksarenot present, call themanufacturer.
TheenclosureLEDsarelocatedonthefrontpanel moduleof thediskarraydevice:
systempower
systemfault
systemready(seeParagraph3--2)
63 Gb
Disk viewscreen
Present disk
Missing disk
Legend:
Disk present and ready
Disk present and not ready
Disk not present
Disk failure
81 Gb or 162 Gb
Final status
Thefunctionsof theA5XXX displayunit areexplained.
4--28
PE/DCL/DD/0032
411--9001--032
Sheet 2 Analyzeof thenotifications
Presentation
Thepurposeof thissheet istoanalyzetheOMC--Rnotificationsonthediskarray
device.
InputParameters
administrator_password: passwordof theOMC--R administrator user.
Initial status
TheOMC--R applicationisrunningandtheMMI isavailable.
Actions
ONTHE WORKSTATIONORTHE SERVER
1. OpenanUNIX windowandloginas administratoruser if notalreadydone.
2. Check a30526notification:
GOTO OMC-R Browser
SELECT Fault -- Showalarmfor all network elements
GOTO Filter
SET fault number =30526
GOTO Apply
Thefollowingnotificationdisplays:
Al ar m: 164 occur r ed on 10/ 21/ 99 16: 00: 34 - r ecei ved on
10/ 21/ 99 16: 00: 34 Not i f : 976
Type: equi pment Al ar m <Sever i t y: maj or >
I nst ance: md
md: 1 < mdNot i f I d: 6008>
al ar mi st : unacknowl edged al ar mSever i t y: maj or
sour ce : ( 52750) Need mai nt enance, i nt er nal XXX
mi r r or di sk f ai l ed
f aul t Number : ( 30526) SPARC STORAGE ARRAY DEVI CE ERROR
commonAddI nf o :
event r ecept i on MD t i me : 10/ 21/ 99 16: 00: 34
def ence anomal y :
def ence act i on : def ence none
suspect ed t ask : 1405
suspect ed st at i on : 1
manuf act ur er i nf or mat i on : Gr avi t y : 0
St r i ng ( 2) : Submi r r or DI SKSET1/ d47 of t he mi r r or
DI SKSET1/ d45 needs mai nt enance
Othersstringscandisplay:
String1: Submirror DISKSET1/d(xx+1or xx+2) of themirror DISKSET1/dxx
hasanunknownstatus
String3: Replicasarecorruptedondevice/dev/dsk/cxtydz; replicashavetobe
deletedandrecreatedonthisdevice
String4: All thesubmirrorsandreplicasareokay
GOTO Close
Final status
Thenotificationisanalyzed.
4--30
PE/DCL/DD/0032
411--9001--032
Sheet 3 rebuildmirror.shtool
Presentation
Thepurposeof thissheetistoexecutetherebuildmirror.shtool for synchronizethe
disk arraydevice.
InputParameters
c<x>: nameof thecontroller inthenotification,
c0or c1.
Initial status
Indual configuration: bothserversarerunning.
Inmonoconfiguration: theserver isrunning.
Actions
ONTHE ACTIVE SERVER
1. OpenanUNIX windowandloginas croot user if not alreadydone.
2. Executethetool.
. . . ( cr oot ) # cd / usr/ l ocal / ssa_mai nt
. . . ( cr oot ) # rebui l dmi rror. sh c<x>
3. Wait theendof thetool execution.
. . . ( cr oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
Final status
Therebuildmirror.shtool isexecuted.
Sheet 4 repair_db.shtool
Presentation
Thepurposeof this sheet is to executed therepair_db.sh tool which repairs the
replicas.
InputParameters
c<x>t<y>d<z>s<?>: nameof DISKSET1onthenotification.
without parameter, all replicasarerepaired.
Initial status
Actions
ONTHE ACTIVE SERVER
2. Executethetool.
. . . ( cr oot ) # repai r_db. sh [ cxtydzs?]
3. Answer toquestion.
. . . Repai r t he r epl i cas ( y/ n) ? y
4. Check thereisanyfail.
. . . The br oken r epl i cas have been r epai r ed
4--32
PE/DCL/DD/0032
411--9001--032
5. If themessagedisplays.
. . . Cannot r epai r t he br oken r epl i cas
Contact themanufacturer.
. . . ( cr oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
Final status
Therepair_db.shtool isexecuted.
Sheet 5 repair_A5000.shtool for A5XXXdiskarraydevice
Presentation
Thepurposeof thissheet istoexecutetherepair_A5000.shtool for changeadisk
of theA5XXX disk arraydevice.
CAUTION
EquipmentDamage
The presence of Sun maintenance is mandatory before
executethis tool.
Thetool executeduringthreesteps:
executethecommand
changethedisk
pushtheenter keyfor continue
InputParameters
c<x>t<y>d<z>: nameof DISKSET1onthenotification.
Initial status
TheOMC--R applicationisavailable.
Oneor several disksarefailedonA5XXX disk arraydevice.
Oneof thebothserversownstheDISKSET inconfigurationdual--server.
ThePE_SSA_MAINT product isdownloadontheserver whichownsthediskset.
CAUTION
EquipmentDamage
The procedure does not apply if the mirror disk is on service and
without failure.
4--34
PE/DCL/DD/0032
411--9001--032
Actions
ONTHE ACTIVE SERVER
2. Check the SCSI_cont SCSI controller number, the SCSI_tg SCSI target
number, theSCSI_lunSCSI logical unitnumberinthenotificationormetastat.
Thisiscxtydz withSCSI_cont =x, SCSI_tg=y, SCSI_lun=z.
3. Executethetool.
. . . ( cr oot ) # repai r_A5000. sh c<x>t<y>d<z>
Oneexampleif c1t1d0.
4. Removedisk t1d0 . (Thedisk havetobechangebySun).
. . . Remove t 1d0 f r omDI SKSET1
162Gbor 81Gbdisk location:
FRONT VI EW
t0d0 t1d0 t2d0 t3d0 t4d0 t5d0 t6d0 t9d0 t10d0
BACK VI EW
t16d0 t17d0 t18d0 t19d0 t20d0 t21d0 t22d0 t25d0 t26d0
5. Strikeenter key.
. . . St r i ke ent er when t he di sk has been changed
6. Wait.
. . . Pl ease wai t
7. Insert deviceinA5XXX.
. . . I nser t devi ce i n A5000
. . . Pl ease wai t
8. Check theendof repair disk.
. . . Repai r di sk i s f i ni shed
9. Verifythesynchronization.
. . . ( omc) %metastat - s DI SKSET1 | grep Resy
. . .
Thepercentageof thesynchronizationdisplaysto100%. Thesynchronization
takesat least 2hours.
Final status
Therepair_A5000.shtool isexecuted.
4--36
PE/DCL/DD/0032
411--9001--032
Sheet 6 stat_db.shtool
Presentation
Thepurposeof this sheet is to executethestat_db.shtool for display thebroken
replicas.
Initial status
Actions
ONTHE ACTIVE SERVER
2. Executethetool.
. . . ( cr oot ) # stat_db. sh
f l ags f i r st bl k bl ock count
a m pc l uo 16 1034 / dev/ dsk/ c0t 10d0s7
a pc l uo 1050 1034 / dev/ dsk/ c0t 10d0s7
a pc l uo 2084 1034 / dev/ dsk/ c0t 10d0s7
f l ags f i r st bl k bl ock count
a m l uo 16 1034 / dev/ dsk/ c0t 0d0s7
a l uo 16 1034 / dev/ dsk/ c0t 0d1s7
a l uo 16 1034 / dev/ dsk/ c0t 1d0s7
a l uo 150 1034 / dev/ dsk/ c0t 1d0s7
a l uo 16 1034 / dev/ dsk/ c0t 2d0s7
a l uo 16 1034 / dev/ dsk/ c0t 2d1s7
a l uo 16 1034 / dev/ dsk/ c0t 3d0s7
a l uo 1050 1034 / dev/ dsk/ c0t 3d0s7
a l uo 16 1034 / dev/ dsk/ c0t 4d0s7
a l uo 1050 1034 / dev/ dsk/ c0t 4d0s7
a l uo 16 1034 / dev/ dsk/ c0t 5d0s7
a l uo 1050 1034 / dev/ dsk/ c0t 5d0s7
a l uo 16 1034 / dev/ dsk/ c1t 0d0s7
a l uo 16 1034 / dev/ dsk/ c1t 0d1s7
a l uo 16 1034 / dev/ dsk/ c1t 1d0s7
a l uo 1050 1034 / dev/ dsk/ c1t 1d0s7
a l uo 16 1034 / dev/ dsk/ c1t 2d0s7
a l uo 16 1034 / dev/ dsk/ c1t 2d1s7
a l uo 16 1034 / dev/ dsk/ c1t 3d0s7
a l uo 1050 1034 / dev/ dsk/ c1t 3d0s7
a l uo 16 1034 / dev/ dsk/ c1t 4d0s7
a l uo 1050 1034 / dev/ dsk/ c1t 4d0s7
a l uo 16 1034 / dev/ dsk/ c1t 5d0s7
a l uo 1050 1034 / dev/ dsk/ c1t 5d0s7
4--38
PE/DCL/DD/0032
411--9001--032
Fl ags r epr esent t he st at us of r epl i cas :
a - r epl i ca i s act i ve, commi t s ar e occur r i ng t o t hi s r epl i ca
o - r epl i ca act i ve pr i or t o l ast mddb conf i gur at i on change
u - r epl i ca i s up t o dat e
l - l ocat or f or t hi s r epl i ca was r ead successf ul l y
c - r epl i ca s l ocat i on was i n / et c/ opt / SUNWmd/ mddb. cf
p - r epl i ca s l ocat i on was pat ched i n ker nel
m- r epl i ca i s mast er , t hi s i s r epl i ca sel ect ed as i nput
W- r epl i ca has devi ce wr i t e er r or s
M - r epl i ca had pr obl emwi t h mast er bl ocks
D - r epl i ca had pr obl emwi t h dat a bl ocks
F - r epl i ca had f or mat pr obl em
S - r epl i ca i s t oo smal l t o hol d cur r ent dat a base
R - r epl i ca had devi ce r ead er r or s
. . .
3. Anycapital flag isinthereplica, it displays:
Al l t he r epl i cas ar e OK
4. If thereisacapital flag, it displays:
F M unknown unknown / dev/ dsk/ c1t 1d0s7
Br oken r epl i cas :
/ dev/ dsk/ c1t 1d0s7
Repair thereplicas, seeSheet 4.
. . . ( cr oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
Final status
Thestat_db.shtool isexecuted.
Sheet 7 Checkformat</dev/null withA5XXXdiskarraydevice
Presentation
Thepurposeof thissheet istoexecutethecheck if all thedisksarepresent.
Initial status
TheOMC--R applicationisavailable.
Actions
2. Executethecommand.
. . . ( cr oot ) # f ormat < / dev/ nul l
4--40
PE/DCL/DD/0032
411--9001--032
3. Thelist of disksdisplays.
. . . AVAI LABLE DI SK SELECTI ONS:
0. . . c0t 16. . .
1. . . c0t 17. . .
2. . . c0t 18. . .
3. . . c0t 19. . .
4. . . c0t 20. . .
5. . . c0t 21. . .
6. . . c0t 22. . .
7. . . c0t 25. . .
8. . . c0t 26. . .
9. . . c1t 0. . .
10. . . c1t 1. . .
11. . . c1t 2. . .
12. . . c1t 3. . .
13. . . c1t 4. . .
14. . . c1t 5. . .
15. . . c1t 6. . .
16. . . c1t 9. . .
17. . . c1t 10. . .
18. . . c2t 10. . .
19. . . c2t 11. . .
. . .
4. If all disksarepresent, gotoSheet 5andSheet 3.
5. If all disksarenot present, call themanufacturer.
. . . ( cr oot ) # [ Ctrl ] , [ d]
. . . ( omc) %
Final status
Thecheck of thedisksisexecuted.
Procedures associated with OMC-R notifications Nortel Networks Confidential 5--1
5 PROCEDURES ASSOCIATEDWITHOMC-R
NOTIFICATIONS
5.1 Introduction
It explains thefault messages issuedby theOMC-R anddescribes thecorrective
action.
5.2 OMC-Rnotifications
Theevent report messages issuedby theBSS or theOMC-R aretranslatedinto
notificationsfor operator purposes.
OMC-R notificationsaresent toworkstationswheretheOMC-R zoneof interest
isdefinedintheuser or terminal profile.
Therearetwotypesof eventsthattriggernotificationsregardingsolelytheOMC-R:
SOFTWARE (MAJOR or MINOR)
OBSERVATION COUNTER (THRESHOLDCROSSINGor RETURN TO
NORMAL)
A fault messagetext andnumber arepartneredwitheachnotification.
Moreover, whencertaineventsoccur, theOMC-R may decidetoexecutedefense
actionsandissueanalarm.
OMC-Rnotificationformat
Thisformat isdescribedinNTP<39>.
5.3 OMC-Ralarms
OMC-R eventsmaytrigger twotypesof alarms:
fault occurrences
observationthresholdcounter crossing
OMC-Ralarmformat
Thisformat isdescribedinNTP<39>.
5.4 Maintenanceproceduresheetbreakdown
A maintenanceproceduresheet isdividedintothefollowingparagraphs:
IDENTIFICATION/LOCATION. This paragraph contains the information
requiredtoidentifythesourceof thenotification(originof error, for example).
SYSTEM ACTION. This paragraph briefly explains the action taken by the
OMC-R toovercomeoperatingdifficulties.
STEP-BY-STEP REPAIRS. Thisparagraphexplainshowtocorrect thefault.
ADDITIONAL CHECK. Thisparagraphexplainshowtocheckthatthefaulthas
beencleared.
Thesesheetsaregiveninthefollowingpages.
Procedures associated with OMC-R notifications
5--2
PE/DCL/DD/0032
411--9001--032
5.5 Tableof faultnumbers
CAUTION
Equipmentdamage
For 30500to 30527faultnumbers:
The configuration files are not modified. These following fault
numbers are not displayed 30500, 30501, 30502, 30503, 30505,
30510, 30512, 30513, 30520, 30522, 30524 and 30527.
For 30600to 30627faultnumbers:
The configuration files are not modified. These following fault
numbers are not displayed 30609 and 30618.
Thefollowingtableshowstheactionof thefault numbers:
Theasteriskedfault numbersarenot displayedseeCautionParagraph.
OPERATORACTION
CALL THE
MANUFACTURERFOR
ASSISTANCE
WITHOUT ACTION
30052 -- 30060 -- 30061 --
30063 -- 30071 -- 30072 --
30074 -- 30507 -- 30509 --
30511 -- 30514 -- 30515 --
30517 -- 30519 -- 30521 --
30523 -- 30526 -- 30528 --
30529 -- 30530 -- 30605 --
30608 -- 30615 -- 30617 --
31001 -- 31008 -- 31009 --
31010 -- 31100 -- 31200 --
31400 -- 31407 -- 31408 --
31409 -- 31500 -- 31501 --
39500 to 39506 --
39550 to 39556 --
39507 to 39549 --
39557 to 39599
30030 -- 30073 -- 30504 --
30506 -- 30508 -- 30516 --
30614 -- 30616 -- 31401 --
31402 -- 31403 -- 31404 --
31405 -- 31406 -- 31600
30020 -- 30041 -- 30130 --
30131 -- 30600 -- 30601 --
30602 -- 30603 -- 30604 --
30607 -- 30610 -- 30611 --
30612 -- 30613 -- 30620 --
30621 -- 30622 -- 30623 --
30624 -- 30627 -- 31000 --
31006 -- 31007 -- 31201 --
31300 -- 31700 -- 31800 --
31801
30500* -- 30501* --
30505* -- 30510* --
30512* -- 30513* --
30520* -- 30522* --
30524* -- 30527* --
30609*
30502* -- 30503* 30618*
5.5.1 Faultnumber: 30020
iii
Faultnumber:
30020 : Incorrect event received by observation management
Type : processingErrorAlarm
IDENTIFICATION/LOCATION
Thisnotificationisissuedwhenthethresholdof theobservationcounter iscrossed
(rawor synthetic).
Thesources(V12-- V15) or causescanbe:
30200 Unknownobservationtype
30201 Unknownobservationcounter type
30202 Unknownobservationcounter location
30203 Unknownobservationcounter occurrence
30204 Unknowncounter identity
30205 Temporaryobservationcompleted
30208 Receptionof aninconsistent BSC message
SYSTEMACTION
Not applicable.
STEP-BY-STEP REPAIRS
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--4
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30030 : Incorrect event received by fault management
OMC-RissuesthisnotificationwhenaproblemisdetectedintheBSSeventreport.
30210 Unknownobject identifier
30211 Unexpectedanomalytype
30212 WrongASN1structurecontent
30213 Operationcodenot accepted
30214 Missinganomalycode
30215 EVR decodingproblem
30216 DEVR decodingproblem
30217 Object mediationproblem
30218 Stateattributesmediationproblem
30219 Alarmmediationproblem
SYSTEMACTION
Not applicable.
Notethesource(V12-- V15) or thecomplementarycodeor thecause.
Call themanufacturer.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30041 : Late bss event in queue
Type : qualityOfServiceAlarm
Thisnotificationisissuedforeachcircularfile. Itiscreatedwhenthedelaybetween
theemissiondate, setbytheBSCandthereceptiondate, setbytheOMC-Rexceeds
5 minutes.
30042 Softwareanomaliesqueue
30043 Bsceventsqueue
30044 Highprioritystatechangesqueue
30045 Lowprioritystatechangesqueue
30046 Hardwareanomaliesqueue
SYSTEMACTION
Thealarmof the30045sourceor causeisautomaticallystoppedwhentheOMC-R
receivesanotificationof alowprioritystatechange. ThedelaybetweentheBSC
emission and OMC-R reception date of the notification must be lower than 5
minutes.
A warningisdisplayedfor theother sourcesor causes.
Wait for thesynchronizationendof thequeues.
ADDITIONAL CHECK
Not applicable.
5--6
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30052 : Purging alarms on saturation
This notification is issued for knowthe alarms which arepurged after 30 days
without lossof information.
Automatic user-alarmpurge on saturation applies when number of user-alarms
reaches 95%of themaximumnumberof user-alarmsallowedbytheconfiguration.
Oldest user-alarmsarepurgeduntil thisnumber islessor equal than 85%of this
maximumnumber.
Theoperator iswarnedof thispurgeactivationbyaspecificalarm.
The alarmraised on purge activation is not automatically cleared to allow the
operator toseetheproblem.
Thesource(V12-- V15) or causecanbe:
30053 Highthresholdexceeded
SYSTEMACTION
Not applicable.
Clear thealarm. Thepurgedalarmsareinthealarmlogwith
cessationType =purgeonsaturation.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30060 : Association management error (open or abort)
Type : communicationsAlarm
TheOMC-R issues this notification when it detects an association management
error or BSC/OMC-R link outage.
Thefollowingassociationsareconcernedbythistypeof error:
INIT
TRANSAC
FAULT
OBS
Associationscanbeinthefollowingstates:
open
closed
30240 Associationabort problem
30241 Associationopenerror
SYSTEMACTION
WhenthelinkbetweenBSCandOMC-Risoutof service, four notificationsare
output to the notification window (one notification for each association).
Associationsarethenclosed.
When only theINIT association is open, arequest to rebuild theBDA must be
displayedinthenotificationwindow.
Restorethelink betweenOMC andBSC.
Check X.25link cabling.
ADDITIONAL CHECK
Not applicable.
5--8
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30061 : BDA state change
ThisnotificationisissuedwhentheOMC-R detectsaBDA problem.
It isalsoissuedwhentheOMN link towardsthisBSC islockedor at theOMC-R
start-up. Inthiscase, thisnotificationmust not betakenintoaccount.
30289 BDE andreport buildBSC BDA buildnumbersaredifferent
30290 BSC requiresaBDA onlinebuilding
30291 Onlinebuilt BDA associatedEFT requirestobeactivated
30292 Onlinebuilt BDA requirestobeactivated
30293 BSC isinprobativephase
30294 Reset onlinecancelledbyBSC
30295 Reset onlineandbuildonlinecancelledbyBSC
30296 Reset online, buildonlineandEFT changecancelledbyBSC
30297 Reset online, buildonlineandBDA changecancelledbyBSC
30298 Onlinebuilt BDA BSC andMD-R statusareinconsistent
30299 BSC requiresBDA off linebuilding
30400 BDA isinaninconsistent state
SYSTEMACTION
Not applicable.
DeletethenrebuildtheBDA (Refer toNTP<34>).
ADDITIONAL CHECK
Audit theBDA (seepage5--139).
iii
Faultnumber:
30063 : Error on BSC software
Thiswarningindicatesthat aBSChasset asoftwareversiontotheOMC-Rthatis
different fromtheversioninBDE.
Theproblemisprobablydueto:
atypingerror inthesoftwareversionrecordedinBDE
awrongMMU boardinBSC
30284 BDE andreport buildBSC BDA versionnumbersaredifferent
30401 BDE andreport buildBSC softwareversionsaredifferent
30402 BDE andreport buildBSC architecturesaredifferent
30406 BDE andreport buildBSC softwarerunningaredifferent
SYSTEMACTION
Not applicable.
Check theX.25addressesof theBSC.
Makesurethat theBSC softwareversionmatchestheBDE version.
If thereisaversionchange, youmust buildtheBDA.
ADDITIONAL CHECK
Not applicable.
5--10
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30071 : Anomaly in BSC answer
This notification is issued when a BSC sends an RGE to theOMC-R in which
an REE containsnon-interpretableinformation.
It isalsoissuedwhenaReset BDA online commandisexecutedona BSC in
simplexmode.
30260 Messagenot allowed
30261 Negativestatus
30263 Waitingtimer switched
SYSTEMACTION
WhentheResetBDA onlinecommandhasbeenexecuted, theBDA of the BSC
hasnot beenreset.
If theResetBDA onlinecommandhasbeenexecutedonaBSCinsimplexmode,
twoactionsarepossible:
reset theBDA off line(theBSC remainsinsimplexmode)
set theBSC toduplexmodeandreset theBDA online
If thecommandsfail, call themanufacturer.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30072 : Anomaly in command acknowledgement fromBSC
A BSC hasnot acknowledgedtheTGE sent bytheOMC-R.
SYSTEMACTION
Not applicable.
Executeageneral audit if thenotificationisreceivedafter aBDA rebuildrequest
fromaBSC. Dependingontheresultof theaudit, performthefollowingoperation:
ignorethenotificationif theaudit result isOK
if not, archivethedataexcept BDE, reset thenrebuildBDA
If thenotificationisnotissuedafter arebuildcommand, call themanufacturer and
archivethedata(except BDE).
ADDITIONAL CHECK
Not applicable.
5--12
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30073 : Error in spontaneous BSC message
TheOMC-RhasnotdecodedaspontaneousBSCeventmessagebecauseof a BSC
or OMC-R softwarefault.
SYSTEMACTION
Not applicable.
Call themanufacturer andarchivethecontext inwhichthenotificationappeared
(except BDE).
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30074 : Communication problemwith a workstation
TheOMC-RhasacommunicationproblemwithaSDOorPCU OAMworkstation.
30700 SDOWorkstation
30701 PCU OAM Workstation
SYSTEMACTION
Theproblemmaybetemporary.
Ethernet link, link problem
communicationproblemwithaserver
Thefault maybeshort lived.
Not applicable.
ADDITIONAL CHECK
Check thestatusof themachineconnections. For acommunicationproblemwith
aserver, check theserver status.
5--14
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30130 : Begin of BDE save
Type : specific
ThisnotificationisissuedwhentheOMC-Renvironmentdatabackup/restoretool
startsthebackup.
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30131 : End of BDE save
Type : specific
ThisnotificationisissuedwhentheOMC-Renvironmentdatabackup/restoretool
endsthebackup.
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--16
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30500 : OMC-R software error on UNIX primitive invocation
Thisnotificationisissuedwhenataskreceivesanerroronacall toastandard UNIX
primitive(seeParagraph5.5caution).
52408 SIGNAL primitivefailure
52409 KILL primitivefailure
52410 ALARM primitivefailure
52411 TIME primitivefailure
52412 SLEEP primitivefailure
52413 PAUSE primitivefailure
52421 BCOPY primitivefailure
52422 BZEROprimitivefailure
52423 GETHOSTNAME primitivefailure
52424 GETHOSTBYNAME primitivefailure
52428 LSEEK primitivefailure
52430 STRCAT primitivefailure
52431 STRNCAT primitivefailure
52432 STRDUP primitivefailure
52433 STRCMP primitivefailure
52434 STRNCMP primitivefailure
52435 STRCPY primitivefailure
52436 STRNCPY primitivefailure
52437 STRLEN primitivefailure
52438 STRSTR primitivefailure
52439 SETITIMER primitivefailure
52440 GETITIMER primitivefailure
52441 GETTIMEOFDAY primitivefailure
52442 SETTIMEOFDAY primitivefailure
52443 GMTIME primitivefailure
52444 LOCALTIME primitivefailure
52445 RTIME primitivefailure
52446 TIMEGM primitivefailure
52447 TIMELOCAL primitivefailure
52448 STRFTIME primitivefailure
52449 STRPTIME primitivefailure
52453 PERROR primitivefailure
52454 IOCTL primitivefailure
52455 TTYNAME primitivefailure
52461 MEMCMP primitivefailure
52462 MEMCPY primitivefailure
52464 MEMSET primitivefailure
52504 ATOI primitivefailure
52505 ATOL primitivefailure
52506 STRTOL primitivefailure
52507 HTONL primitivefailure
52508 HTONSprimitivefailure
52509 NTOHL primitivefailure
52510 NTOHSprimitivefailure
52511 FTOK primitivefailure
52512 GETUIDprimitivefailure
52513 GETEUIDprimitivefailure
52514 GETGIDprimitivefailure
52515 GETEGIDprimitivefailure
52516 GETPIDprimitivefailure
52517 GETPPIDprimitivefailure
52518 GETHOSTIDprimitivefailure
52519 GETHOSTBYADDR primitivefailure
52532 PRINTF primitivefailure
5--18
PE/DCL/DD/0032
411--9001--032
52533 SPRINTF primitivefailure
52534 SSCANF primitivefailure
52535 SCANF primitivefailure
52536 GETCHAR primitivefailure
52537 FCNTL primitivefailure
52538 STATE primitivefailure
52539 UMASK primitivefailure
SYSTEMACTION
Thefault maybeshort lived. Thedefensetakesnoactionuntil thefault threshold
iscrossed(fault number 30600).
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30501 : Forked process internal error
This notification is issued on a failure to generate a new process UNIX
(see Paragraph5.5caution).
52450 WAIT primitivefailure
52451 FORK primitivefailure
52452 SYSTEM primitivefailure
52456 EXIT primitivefailure
52457 NICE primitivefailure
52458 EXECL primitivefailure
52459 EXECV primitivefailure
52460 EXECLP primitivefailure
52550 THR_CREATE primitivefailure
52551 THR_SETCONCURRENCY primitivefailure
SYSTEMACTION
Thesystemis:
eithertemporarilyunstable, thisprocesscouldnotbegenerated, thecommandin
processfails
or definitelyunstableandthisproblemwill endbyastart of theOMC-R
Not applicable.
5--20
PE/DCL/DD/0032
411--9001--032
ADDITIONAL CHECK
Check theswapzone(UNIX commandswap--s).
Check thenumber of activeprocesses(UNIX commandps --edf).
iii
Faultnumber:
30502 : Semaphore error
This notification is issued for an error in a UNIX semaphore operation
52414 SEMGET primitivefailure
52415 SEMCTL primitivefailure
52416 SEMOP primitivefailure
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Check thenumber of semaphores(UNIX commandipcs --s).
5--22
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30503 : Shared memory error
Thisnotificationisissuedwhenanoperationonthe UNIX sharedmemoriesfails
52417 SHMGET primitivefailure
52418 SHMCTL primitivefailure
52419 SHMAT primitivefailure
52420 SHMDT primitivefailure
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Check thesizeandthenumber of sharedmemories(UNIX commandipcs--m).
iii
Faultnumber:
30504 : Memory allocation error
Thisnotificationisissuedwhenatask failstoallocateanewmemoryzone.
52405 MALLOC primitivefailure
52406 REALLOC primitivefailure
52407 FREE primitivefailure
52465 CALLOC primitivefailure
52466 CFREE primitivefailure
52467 VALLOC primitivefailure
52468 ALLOCA primitivefailure
SYSTEMACTION
Thetask is:
eithertemporarilyunstable, thisprocesscouldnotbegenerated, thecommandin
processfails
or definitelyunstableandthisproblemwill endbyastart of theOMC system
Not applicable.
ADDITIONAL CHECK
Check theswapzone(UNIX commandswap--s).
Check theprocesssize(UNIX commandps --le).
5--24
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30505 : TLI (or socket) error
Thisnotificationisissuedwhenanoperationonthe TLI orsocketconnectionsfails
52479 T_OPEN primitivefailure
52480 T_CLOSE primitivefailure
52481 T_ALLOC primitivefailure
52482 T_FREE primitivefailure
52483 T_BINDprimitivefailure
52484 T_UNBINDprimitivefailure
52485 T_LISTEN primitivefailure
52486 T_ACCEPT primitivefailure
52487 T_CONNECT primitivefailure
52488 T_RCVCONNECT primitivefailure
52489 T_SNDprimitivefailure
52490 T_RCV primitivefailure
52491 T_SNDDISprimitivefailure
52492 T_RCVDISprimitivefailure
52493 T_SNDREL primitivefailure
52494 T_RCVREL primitivefailure
52495 T_GETINFOprimitivefailure
52496 T_GETSTATE primitivefailure
52497 T_LOOK primitivefailure
52498 T_OPTMGMT primitivefailure
52499 T_SYNC primitivefailure
52500 T_ERROR primitivefailure
52501 T_RCVUDATA primitivefailure
52502 T_RCVUDERR primitivefailure
52503 T_SNDUDATA primitivefailure
52469 SOCKET primitivefailure
52470 BINDprimitivefailure
52471 LISTEN primitivefailure
52472 SETSOCKOPT primitivefailure
52473 GETSOCKOPT primitivefailure
52474 GETSOCKNAME primitivefailure
52475 SNDprimitivefailure
52476 RCV primitivefailure
52477 SOCKETPAIR primitivefailure
52478 INET_NTOA primitivefailure
52425 SELECT primitivefailure
52426 CONNECT primitivefailure
52427 ACCEPT primitivefailure
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
5--26
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30506 : Active server swap space overflow
Thisnotificationisissuedfor oneerror swapoverflowto 85%.
52620 UsedSWAP areaMemorythresholdexceededonactiveserver
52622 UsedSWAP areaMemorythresholdexceededonworkstation
SYSTEMACTION
A reboot actionisperformed.
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30507 : Internal database error
Thisnotificationisissuedwhenanoperationonthedatabaseviathe SQL server
fails.
52600 Sybaseerror reportedbyerror handler
52630 Used space threshold exceeded on the Sybase data segment of
the activeserver
52632 SybaseDBLibproblem
52633 SQL-server unreachableontheactiveserver
52635 SQL-server internal error ontheactiveserver
52637 SQL-server isbrokendownontheactiveserver
SYSTEMACTION
Thefault number maybetheresult of incorrect attributelimits.
Not applicable.
ADDITIONAL CHECK
Execute the procedure Sybase database check and fix (see Paragraph 3.3.3
and 4.2.2).
CAUTION
Serviceinterruption
The OMC-R application is stopped.
5--28
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30508 : Active server database error
Suspect databaseonthemainserver.
52610 Sybasemirroringerror onactiveserver
52612 Suspect database
52613 Sybasemirroringerror withredundant disks
52639 Suspect databaseontheactiveserver
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30509 : Backup server database error
Suspect databaseonthebackupserver.
52611 Sybasemirroringerror onstandbyserver
52614 Suspect databaseonstandbyserver
52615 Sybasedatabaseupdatingout of sequencestandbyserver
52631 Used space threshold exceeded on the Sybase data segment of
the passiveserver
52634 SQL-server unreachableonthepassiveserver
52636 SQL-server internal error onthepassiveserver
52638 SQL-server isbrokendownonthepassiveserver
52640 Suspect databaseonthepassiveserver
SYSTEMACTION
Themirroreddataareexpired, theswitchover mechanismisinhibited.
ExecutetheprocedureOMC-R databasere-installation (see Paragraph 4.2.1).
Execute cf_majsecours.sh from the active server to update the backup server
ADDITIONAL CHECK
Not applicable.
5--30
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30510 : OMC common services internal error
This notification is issued on an error from an OMC-R common service
52815 BSF PIPE_BROKEN primitivefailure
52816 BSF RELANCER_MACHINE primitivefailure
52817 BSF INIT_CPT_MSGprimitivefailure
52818 BSF RELEVE_CPT_MSGprimitivefailure
52200 Fileaccesserror
52201 Semaphoreoperationerror
52202 Error detectedontimeout
52203 Reactivationof anexistingtimer
52204 WrongparametersinaBSF primitiveinvocation
52205 Unknownhost
52206 Unexpectedserver type
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30511 : Chained list internal error
Thisnotificationisissuedwhenanoperationonthechainedlistsfails.
52819 BSF CREATION_FILE_ATTENTE primitivefailure
52820 BSF DESTRUCTION_FILE_ATTENTE primitivefailure
52821 BSF ECRITURE_FILE_ATTENTE primitivefailure
52822 BSF LECTURE_FILE_ATTENTE primitivefailure
52823 BSF INTERROGATION_FILE_ATTENTE primitivefailure
52824 BSF AFFICHAGE_FILE_ATTENTE primitivefailure
52825 BSF PARCOURS_FILE_ATTENTE primitivefailure
52826 BSF SUPPRESSION_ELEMENT primitivefailure
52827 BSF AJOUT_ELEMENT primitivefailure
52828 BSF TAILLE_FILE primitivefailure
52829 BSF SUBSTITUTION_ELEMENT primitivefailure
52870 Overflownotificationqueuewaitingtobesent toastation
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
5--32
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30512 : Delay service internal error
This notification is issued when an operation on the delay service fails
52830 BSF ACTIVATION_DELAI primitivefailure
52831 BSF REACTIVATION_DELAI primitivefailure
52832 BSF DEACTIVATION_DELAI primitivefailure
52833 BSF CLEAR_DELAISprimitivefailure
52834 BSF MODIF_DATE primitivefailure
52835 BSF ATTENTE primitivefailure
52836 BSF AFFICHAGE_DELAISprimitivefailure
52837 BSF RELEVE_CPT_DELAISprimitivefailure
52838 BSF ACTIVATION_CHRONOMETRE primitivefailure(notused)
52839 BSF RELEVE_CHRONOMETRE primitivefailure (not used)
52840 BSF CLEAR_CHRONOSprimitivefailure (not used)
52841 BSF AFFICHAGE_CHRONOSprimitivefailure (not used)
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30513 : Coding/decoding event error
Thisnotificationisissuedincaseof aprobleminthecodingordecodingof anevent
crossingtheBSS/MD-R interface (see Paragraph5.5caution).
52842 BSF CODAGE_TEE primitivefailure
52843 BSF CODAGE_TGE primitivefailure
52844 BSF DECODAGE_TEE primitivefailure
52845 BSF DECODAGE_TGE primitivefailure
52846 BSF CODAGE_ATGE primitivefailure
52847 BSF DECODAGE_ATGE primitivefailure
52848 BSF DECODAGE_REE primitivefailure
52849 BSF DECODAGE_RGE primitivefailure
52850 BSF CODAGE_REE primitivefailure
52851 BSF CODAGE_RGE primitivefailure
52852 BSF DECODAGE_DEVR primitivefailure
52853 BSF DECODAGE_EVR primitivefailure
52854 BSF CODAGE_DEVR primitivefailure
52855 BSF CODAGE_EVR primitivefailure
52856 Datedecodingerror
52857 Dateencodingerror
52858 Unconsistant ATGE
52859 Unconsistant RGE header
52860 Unconsistant REE header
52861 UnknownobjectIdinREE
52862 Unconsistant REE
52863 Unconsistant EVR header
5--34
PE/DCL/DD/0032
411--9001--032
52864 Unconsistant DEVR header
52865 UnknownobjectId
52866 Unconsistant data
52867 Wrongattribute
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30514 : Task monitoring failure
A task doesnot replytothemonitoringfor oneof thefollowingcauses:
it hasdisappeared
it istemporarilyinactivityoverload
it loopsindefinitely
it isblocked
52100 Task monitoringfailure
52102 Task disappeared
52103 Disappearedvital task
52104 Task monitoringfailurethresholdexceeded
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
5--36
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30515 : Communication error with BSS
This notification is issued when a BSC communication mechanism fails.
OMC-R detectsthefaultsinmessagesfromoneor moreBSC.
52700 Timeout awaitingreservationacknowledgement
52701 Timeout awaitingsecuredBSC commandacknowledgement
52702 Cannot reserveBSC commandmessage
52714 LoadingBSC commandmessageinmemoryerror
52715 Transmissionfailed: childprocessprobablyKO
52716 TransmittingtransactiontoBSC error
52717 ReceivingtransactionfromBSC error
52718 Parameter error inBSC commandmessage
52719 WrongBSC number
52720 Wrongmessage
SYSTEMACTION
OMC-R resets the X.25 link with the BSC where the communication problem
occurred.
Thisactionmaybeshortlived. Thedefensetakesnoactionuntil thefaultthreshold
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30516 : Active server access disk error
Thisnotificationisissuedincaseof areadingorwritingaccessproblemonanactive
server disk.
52321 First partitionoverflowthreshold
52322 Secondpartitionoverflowthreshold
52323 First thresholdsaturation, partitionor databasespace
52324 Secondthresholdsaturation, partitionor databasespace
52325 Oneor several partitionsor databasesfull
52401 OPEN primitivefailure
52402 READprimitivefailure
52403 WRITE primitivefailure
52404 CLOSE primitivefailure
52463 FFLUSH primitivefailure
52520 FOPEN primitivefailure
52521 FCLOSE primitivefailure
52522 FREADprimitivefailure
52523 FWRITE primitivefailure
52524 FPRINTF primitivefailure
52525 FGETSprimitivefailure
52526 PIPE primitivefailure
52527 DUP primitivefailure
52528 DUP2primitivefailure
52529 LINK primitivefailure
52530 UNLINK primitivefailure
52531 FSCANF primitivefailure
5--38
PE/DCL/DD/0032
411--9001--032
52540 OPENDIR primitivefailure
52544 MKDIR primitivefailure
52545 RMDIR primitivefailure
52710 Writingfileonactiveserver error
52712 Deletingfileonactiveserver error
SYSTEMACTION
When apartition or a databasereaches its second threshold, an alarminitiation
notification(fault number =30516andsourceor cause=52325) isissued. Thena
purgingaction is triggered by OMC-R ontheover-loadedpartition or database.
Whenall partitionsandall databasesgodowntheirthirdthreshold, anend-of-alarm
notification(fault number =30516andsourceor cause=52325) isissued.
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30517 : Active server communication error
Thisnotificationisissuedincaseof acommunicationproblembetweentheactive
server andanoutsidedevice.
52305 Error whileopeningX.25handlingsocket
52306 Error whilebindingX25handler socket
52310 Noanswer fromasynchronouslink
52311 Connectionout withstation
52312 Connectionupfromstation
52313 X.25linksout of service
52314 Ethernet link out of service
52320 Failurefor unmountingapartition
52703 Link failure(HDLC layer) onactiveserver
52970 FailedCMIP onactiveserver
SYSTEMACTION
Theproblemmaybetemporary.
X.25, CMIP, asynchronouslink problem
communicationproblemwithaworkstation
Not applicable.
ADDITIONAL CHECK
Check thestatusof themachineconnections. For acommunicationproblemwith
aworkstation, check theworkstationstatus.
Alarms52311and52312must beclearedmanually.
5--40
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30519 : Backup server communication error
Thisnotificationisissuedeither:
onanasynchronouslink problembetweenmainandbackupserver
or onthemainserver start-upwithout itsbackupserver
or whenthemirroreddataarenolonger valid
or whenpassiveserverdisappearsbrutally(poweredoff or hardwareproblems).
52960 X.25problemonstandbyserver
52961 Problemonasynchronouslink betweenservers
52965 Ethernet problembetweentheactiveserver andthepassiveserver
52966 Failedstandbyserver
52967 Passive server abnormally unreachable, shutdown of active in the
event of aswitchover
52971 FailedCMIP onstandbyserver
SYSTEMACTION
Analarmwithdifferedintervention, of thesamewordingisissued, if not already
existent.
52967sourceor cause: thebackupserver startsandbecomestheactiveserver,
(indual-server configurationonlywithout A5XXX).
52969sourceor cause: theswitchover is prohibited (thepassive server needs
maintenance).
Thestringassociatedtosourceor cause52969canbe:
Passiveserver isunavailable (passiveserver not started)
Passiveserver isunreachable (passiveserver disappearedbrutally)
Invalidmirroringdata (dataareout of dateonthepassiveserver)
Inthecaseof no-longer-validdata(52969sourceorcause),itisnecessarytoexecute
the tool cf_majsecours.sh from the main server to fix the backup server
ADDITIONAL CHECK
5--42
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30520 : Message service error
This notification is issued when an operation with the messaging service fails
52801 BSF AFF_ADRESSESprimitivefailure
52802 BSF AFF_OPERATIONSprimitivefailure
52803 BSF CREATION_BAL primitivefailure
52804 BSF DESTRUCTION_BAL primitivefailure
52805 BSF VIDAGE_BAL primitivefailure
52806 BSF DEL_LAST_MSGprimitivefailure
52807 BSF INFORMATIONS_BAL primitivefailure
52808 BSF RECEPTION_MESSAGE primitivefailure
52809 BSF RECEPTION_SELECTIVE primitivefailure
52810 BSF EMISSION_MESSAGE primitivefailure
52811 BSF IDENTIFIANT_MACHINE primitivefailure
52812 BSF ETAT_MACHINE primitivefailure
52813 BSF VIDAGE_MESSAGERIE primitivefailure
52814 BSF VIDAGE_SELECTIF_MESSAGERIE primitivefailure
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
5--44
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30521 : Application software error
ThisnotificationisissuedwhenaproblemisdetectedbytheOMC-R software.
To identify the problem, more accurately, the complementary code must be
consulted.
52010 UnknownMMI messageparameter
52011 Morethanoneparameter per typeinMMI message
52012 Unknownmessagecode
52013 Unknownmessagetype
52014 timeout onMMI confirmation
52015 Timeout onBSF acknowledgement
52016 Internal error
52017 Computationerror
52018 Unexpectedmessage
52020 Error onMMI messageparameter detectedwhileexecution
52021 UnabletocreateTcl interpreter
52022 BadTcl script
52130 OMC Server start-upcompleted
52641 SybaseDBLibproblem
52990 Thefollowingjobhasnt beenexecutedat thedesiredtime.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
5--46
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30522 : Link error
This notification is issued for a general problem with OMC Administration
52300 NegativeacknowledgementfromSCSEwhencreatingBSC/OMC--R
link
52301 Discrepancydetectedininternal data
52302 SYBASE accesserror
52303 Noanswer fromSCSE
52304 Noanswer fromMMI
52307 UnknownX25port inMMI message
52308 DuplicatedBSSlink inSYBASE table
52309 MaximumBSSlink number exceededinSYBASE table
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30523 : Performance management internal error
Thisnotificationisissuedif aproblemisdetectedbythePerformanceManagement
function(PM). Toidentifytheproblemmoreaccurately, thecomplementarycode
must beconsulted.
52900 Observationreport toolarge
52901 Unknownobservedobject type
52902 Error onwritinganobservationmessage
52903 Readinganobservationmessageerror
52904 Deletinganobservationmessageerror
52905 Readingadaily/monthlymessage(oldversion) error
52906 Storingcountersininternal structureerror
52907 Management internal tablefull
52908 Internal structureinitializationerror
52909 Gettinglist of activetemporaryobservationserror
52910 Gettinglist of messagesfor atemporaryobservationerror
52911 Unknownobject received
52912 OMC-R self observationnot activated
52913 Incoherent observationmessagereceivedfromBSC
52914 SYBASE problem
52917 Anerror isdetectedinauser definedsyntheticobservationcounter
52918 Nopilot access
52919 Observationmessagelost
52920 FTAM error filename
52921 Unknownhost
52922 Syntheticcountersfallback mode
5--48
PE/DCL/DD/0032
411--9001--032
52923 Syntheticcountersinconsistency
52924 YACC internal error
52925 TracedatainsertingprobleminSybase
52926 TracedatapurgingprobleminSybase
52927 Tracedataarchivemakingproblem
52928 Tracedatainsertingproblemwhendatacomefromtracedataarchive
files
52929 Tracefilelost
52930 Insertionintracedatabaseislocked
52931 Insertionintracedatabaseisunlocked
52950 UnexpectedT2timeout
52951 UnexpectedT215timeout
52952 Unknownobservationtype
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30524 : Configuration management internal error
This notification is issued if a problem is detected by the Configuration
Management function (CM). To identify the problem more accurately, the
complementarycodemust beconsulted(see Paragraph5.5caution).
52980 BSC context unblocked
52981 MD/BSC link disconnected
52982 MD/BSC link established
52983 Timecontrol error
52984 Timetransfert error
52985 Timeupdateerror
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
5--50
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30526 : Sparc Storage Array device error
Type : equipmentAlarm
This notification is issued by the OMC-R when an error has been detected on
an A5XXX unit.
Thesource(V12-- V15) or causescanbe:
52750 Needmaintenance, internal SSA mirror disk withstring:
1 Submirror DISKSET1/d(x+1 or x+2) of the mirror
DISKSET1/dxhasanunknownstatus
2 Submirror DISKSET1/d(x+1 or x+2) of the mirror
DISKSET1/dxneedsmaintenance
3 Replicas arecorrupted on devicecxtydz ; replicas haveto be
deletedandrecreatedonthisdevice.
4 All thesubmirrorsandreplicasareokay
52751 Mirror partitionerror ontheSSA
52752 All themirror partitionareokayontheSSA device
SYSTEMACTION
TheOMC-R monitorscyclically(everyminute):
thestateof thesubmirrorsconnectedtoeachmetamirror
andthestateof replicasonlocal disksandonA5XXX
Analarminitiationnotificationisissuedwhen:
asubmirrorchangesfromOKstatetomaintenanceorlastered(seestring
1and 2)
or areplicasgetsbroken(seestring 3)
Inbothcases, thenameof thedefectivesubmirror or thenameof thedevicewhere
thereplicasarefailedisspelt out inthenotification.
Anend-of-alarmnotificationisissuedafter:
amanual replacement of all thedefectivedisksfollowedbystatechangeof the
submirrorsback toOK
andamanual repair of all thebrokenreplicas.
If anerror isinitiatedwithstring 1or 2:
replace the defective A5XXX disk by following the maintenance procedure
definedfor thisproblem
If theerror isinitiatedwithstring 3:
repair thebrokenreplicasbyfollowingthemaintenanceproceduredefinedfor
thisproblem
If theerror hasendedwithstring 4:
noaction, thesubmirrorsandthereplicasarerepaired
ADDITIONAL CHECKS
5--52
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30527 : CMIS service provider error
This notificationis issuedwhentheOSIMCS software(CMIS serviceprovider)
doesnot replytoamonitoringrequest (see Paragraph5.5caution).
TheOMC-Rapplicationsendsamonitoringrequest totheOSIMCSsoftwareina
cyclicway(every 5minutes).
52972 CMIP provider failed
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
30528 : Time function error
Anerror wasencounteredwiththetimefunction.
53001 Manual daemon failure on the OMC-R server (Network Time
Protocol)
53002 Drift threshold exceeded between the OMC-R server and the time
server
53003 Failureonall timeservers
53004 Timeserver unreachable
53005 Manual daemonfailureonthetimeserver (NetworkTimeProtocol)
53006 Radioclock failure
53007 Synchronizationof theradioclock lost
53008 Baddatareceptionfromtheradioclock
53009 Driftthresholdexceededbetweenthetimeserver andtheradioclock
SYSTEMACTION
TheOMC-Rserverperiodically(everyminute) monitorsthetimefunctiononitself
andontimeservers. Problemscanoccur onboth.
When a problemoccurs on a time server (sources or causes from53004 to
53009), a major alarmis raised. Once the problemis resolved, the alarmis
automaticallyreleased.
Whenthereisaproblemonall timeservers, acritical alarmisraised(sourceor
cause53003). So, thetimeof OMC-Rmachinesmightnotbesynchronizedany
more. When at least one time server works again, the critical alarm is
automaticallyreleased.
WhenafailurehappensontheOMC-Rserver, acritical alarmisraised(sourceor
cause 53001or 53002). Thetimeof OMC-Rserver mightnot besynchronized
anymore. When the latter works again, the critical alarm is automatically
released.
5--54
PE/DCL/DD/0032
411--9001--032
Therearetheactionstobeperformedfor agivenfailure.
Whenthedriftthresholdisexceededbetweenthetimeserverandtheradioclock,
(sourceor cause53009) set thetimeserver timemanually.
When thedrift threshold is exceeded between theOMC-R server and atime
server, (sourceor cause53002) comparethetimeonall timeservers. Set the
OMC-R server timemanuallytothemost trustedtimeserver (if thereareonly
twotimeservers) or tothebiggest set of timeserverswhichareinagreement.
Whenthemanual daemon(xntpd)fails(sourceorcause53001or53005) ontime
serversor ontheOMC-R server, restart it.
An unreachabletimeserver (sourceor cause53004) means that thenetwork
connectionfailedor theworkstationwasbrokendown. Theworkstationshould
berestartedinthelatter case.
Incaseof aradioclockfailure(sourceor cause53006), replacetheradioclock.
Whentheradioclockisnomoreornotsynchronized(sourceorcause53007)yet,
movetheradioclocktoahighlocationandnext towindows. Moveit outsideif
necessary. Pleaseavoidmetallicenvironmentsandundergroundplaces.
Incaseof abaddatareception(sourceorcause53008), checktheworkingsof the
serial link andchangeit if needed.
ADDITIONAL CHECK.
CheckthattheOMC-Rserver, timeserversandradioclocksaresynchronizedagain.
iii
Faultnumber:
30529 : MDP data error
ThisnotificationisissuedwhentheMDPhasdetectedmorethan60 errors, during
asummationdurationof onehour.
53100 NomoreobservationdataproceedfromGPRSstatistics
SYSTEMACTION
Thefault maybeshort lived.
Not applicable.
ADDITIONAL CHECK
5--56
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30530 : MDM service error
This notification is issued when the MDM service has detected more than
onemessagingerror, duringasummationdurationof 15 consecutiveminutes.
53200 Fatal error detectedonFM MDM API
53201 Error detectedonFM MDM API
53202 Fatal error detectedonFM MDM software
53204 Error detectedonFM MDM software
SYSTEMACTION
For thesourceor cause 53200:
ThereisaUNIX reboot. TheOMC-Rapplicationmustbestartedonthestation
For thesourceor cause53202:
TheOMC-R applicationmust bestartedonthestation
For thesourceor cause53201or 53204:
Thefault maybeshort lived
Not applicable.
ADDITIONAL CHECK
Not applicable.
5.5.43 Faultnumber 30531
Faultnumber:
30531 : T3 device internal error
ThisnotificationisissuedbytheOMC-Rwhenanerrorhasbeendetectedonan T3
unit. Thesources(V13-- V15) or causescanbe:
53101 T3failure-->diskproblemdetected-- incaseof replacement, thisone
must bedoneinlessthan30mn
53102 T3failure-->diskproblemdetected-- incaseof replacement, thisone
must bedoneinlessthan30mn
53103 T3failure-->power/coolingunit problemdetected
53104 T3failure-->power/coolingunit problemdetected
SYSTEMACTION
TheOMC-R monitorscyclically(every5minutes):
thestateof thedisksonT3
aT3disk changesfromOK statetomaintenanceor lastered
Thenameof thedefectivedeviceisspelt out inthenotification. Anend--of--alarm
notificationisissuedafter:
amanual replacement or repair of all thedefectivedisks.
Replace the defective T3 disk or check power/cooling unit by following the
maintenanceproceduredefinedfor thisproblem
ADDITIONAL CHECKS
Controlethestateof themirroring
5--58
PE/DCL/DD/0032
411--9001--032
Faultnumber:
30532 : T3 device unreachable
ThisnotificationisissuedbytheOMC-RwhentheT3unit isnomoresupervised.
53105 T3failure-->deviceunreachable
53106 T3failure-->deviceunreachable
SYSTEMACTION
TheOMC-R monitorscyclically(every5minutes):
thestateof thesubmirrorsconnectedtoeachmetamirror
andthestateof replicasonlocal disksandonT3
theethernet connectionbetweenserver anditsT3unit isbrocken
Check theethernet link
ADDITIONAL CHECKS
Faultnumber:
30533 : error on passive server
Thisnotificationisissuedby theOMC-R whenanerror hasbeendetectedonthe
passiveserver, andtheswitchover isdisallowed.
53107 BackupServer -->error detectedondisk arrayoptical link
53108 BackupServer -->error detectedonBSC X25link
53109 BackupServer -->error detectedonBSC Ethernet link
SYSTEMACTION
Followingthesourcenumber, checktheoptical diskarraylink, BSCX25linkand
theBSC Ethernet link
ADDITIONAL CHECKS
5--60
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30600 : OMC-R software error on UNIX primitive invocation counter
threshold exceeded
This notification is issued when the MD-R or the manager detects more than
20 software errors in UNIX primitive calls during a counting period of
5 consecutiveminutes, that mayinducetonotificationsof fault number 30500.
Thesource(V12-- V15) or causeis53000Counter out of range.
SYSTEMACTION
Indual-server configuration:
TheOMC-Rapplicationautomaticallyrestartsonbothservers. If thisstartingdoes
not workcorrectlyor it isimpossible, thebackupserver becomesthemainserver.
Insingle-server configuration:
TheOMC-R applicationautomaticallyrestartsontheserver.
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30601 : Forked process internal error counter threshold exceeded
ThisnotificationisissuedwhentheMD-Ror themanager hasdetectedmorethan
20 software errors on process generation, during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--62
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30602 : Semaphore error counter threshold exceeded
20 software semaphore errors, during a summation duration of 5 consecutive
minutes, that mayinducetonotificationsof fault number 30502.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30603 : Shared memory error counter threshold exceeded
20 software errors on shared memory, during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--64
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30604 : Memory allocation error counter threshold exceeded
20 software errors on memory allocation, during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30605 : TLI (or socket) error counter threshold exceeded
20 software errors on TLI (or sockets), during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Check theX.25andEthernet connectionstateof themachine.
5--66
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30607 : Internal database error counter threshold exceeded
10 internal databasesoftwareerrors, duringacountingperiodof 15 consecutive
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30608 : Active server database error counter threshold exceeded
10 softwareerrors onthemainserver database, duringasummationdurationof
SYSTEMACTION
If thebackupserver isoperational, it restartsasactive. If thebackupserver isnot
operational, themainserver remainsactive.
Theserver remainsasactive.
ExecutetheOMC-R databasere-installationprocedure(seeParagraph4.2.1).
ADDITIONAL CHECK
Not applicable.
5--68
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30609 : Backup server database error counter threshold exceeded
10 software errors on the database of the backup server, during a summation
durationof 15consecutiveminutes(see Paragraph5.5caution), that mayinduce
tonotificationsof fault number 30509.
SYSTEMACTION
Thesystemremainsactive.
Call theSybaseadministrator.
Reinstall theOMC-R onthebackupserver (see Paragraph 4.2.1).
Executecf_majsecours.shfromtheactiveserver toupdatethebackupserver
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30610 : OMC common services internal error counter threshold
exceeded
This notification is issued when MD-R or the manager detects more than
10 internal common service errors during a counting period of 5 consecutive
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--70
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30611 : Chained list internal error counter threshold exceeded
10 softwareerrorsonchainedlists, duringasummationdurationof 5 consecutive
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30612 : Delay service internal error counter threshold exceeded
This notificationis issuedwhentheMD or themanager has detectedmorethan
10 software errors on delay service, during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--72
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30613 : Coding/decoding event error counter threshold exceeded
10 software errors on event coding/decoding, during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30614 : Task monitoring failure counter threshold exceeded
This notification is issued when the OMC-R monitoring task detects morethan
5 no-replies or 2 task absences, during a counting period of 20 consecutive
SYSTEMACTION
For aworkstation, thereisalsostarting.
Not applicable.
ADDITIONAL CHECK
5--74
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30615 : Communication error with BSS counter threshold exceeded
This notification is issued when the active OMC-R server detects more than
5 communication management errors with a BSS, during a counting period of
SYSTEMACTION
Repairsdependonthecontext:
if an X.25 link problemoccurred during the ten minutes preceding the first
notification,restoretheX.25linkthencheckthatnonotificationsareissuedforat
least fiveminutes
otherwise (the two active server X.25 links are OK, or 30615 notifications
continuetobeissued) shutdownandstartthemainserverusingtheSHUTTING
DOWNSERVERSandSTARTINGUPSERVERSprocedures(seeChapter 1).
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30616 : Active server access disk error counter threshold exceeded
2 or 10 access disk errors on main server, during a summation duration of
SYSTEMACTION
Call theOMC-R administrator.
ADDITIONAL CHECK
5--76
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30617 : Active server communication error counter threshold
exceeded
10 X.25, CMIP, orEtherneterrors, duringasummationdurationof 15 consecutive
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Accordingtothecomplementarycode, checktheEthernet, X.25andasynchronous
connections:
Ethernet: ping--s
X.25: vcstat IL
CMIP: /CMN/base/exe/com_obsOsimcs.x
For aninaccessibleworkstation, check theworkstationstatus.
iii
Faultnumber:
30618 : Backupserver access diskerror counter thresholdexceeded
Thisnotificationisissuedforerrorsaccessdiskonbackupserver (reading, writing)
SYSTEMACTION
Theswitchover tothebackupserver isforbidden.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--78
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30620 : Message service error counter threshold exceeded
This notificationis issuedwhentheMD or themanager has detectedmorethan
10 messagingerrors, duringasummationdurationof 5 consecutiveminutes, that
mayinducetonotificationsof fault number 30520.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30621 : Application software error counter threshold exceeded
30 softwareerrorsof different kinds, duringacountingperiodof 15 consecutive
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--80
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30622 : Link error counter threshold exceeded
30 softwareerrorsof different kindsduringacountingperiodof 15 consecutive
This notification is issued for errors OAM, general problem with OMC
administration.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30623 : Performance management internal error counter threshold
exceeded
50 internal Performance Management errors, during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--82
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
30624 : Configuration management internal error counter threshold
exceeded
50 internal Configuration Management errors during a summation duration of
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
30627 : CMIS service provider error counter threshold exceeded
Thisnotificationisissuedif inaperiodof 300 seconds, thefunctiondefenseof the
OMC-R sendstwonotifications 30527.
SYSTEMACTION
Thereis aUNIX reboot. TheOMC-R applicationautomatically restarts onboth
serversIf thisstartingdoesnotworkcorrectlyor itisimpossible, thebackupserver
becomesthemainserver.
There is a UNIX reboot. The OMC-R application automatically restarts on the
server.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--84
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31000 : Partition full
Duringawritingoperation, theLOGobjectmanagerof theMD-Rsendsabeginning
of notification 31000 when one of the 3 partitions containing logs (/MD/obs,
/MD/notif, /MD/trace-function) isfull.
Forasaturationof thepartition/MD/notif,thelogmanagerattemptstoreleasespace
bydeletingthelogsof previousthedays.
31001 FAULT partitionfull for /MD/notif
31002 OBSpartitionfull for /MD/obs
31003 TRACE partitionfull for /MD/trace-function
SYSTEMACTION
Not applicable.
Wait for theautomaticanddailypurging(at 3a.m) of theobsoletedatatorelease
spaceonthefull partition.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31001 : BSC clock drift
Thisnotificationisissuedincaseof differencebetweentheBSCtimeandtheMD-R
time.
Thisfault number isrelatedtoBSSclock management.
30403 BSC/OMC-R timedifferencegreater thanTCLOCK4after update
SYSTEMACTION
Analarmwithdeferredinterventionisissued, if not alreadyexistent.
Broadcast thesystemdateandtimetotheBSC inerror:
OnthemainOMC-R screen, intheOMC-R Browser window:
Select theBSC inerror
Select theSynchronizeBSC clock intheConfigurationmenu
ThiscommandisdetailedinNTP <128>.
ADDITIONAL CHECK
Check theOMC/BSC link andre-executethecommand.
5--86
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31006 : Shutdown requested
Thisalarmnotificationispartof thesignalingprotocol betweentheMD-Randthe
manager duringastart-upandshutdownof theOMC-R. WhenaQ3actionof type
start or switchover is requested, a beginning of notification 31006 is sent
before the OMC-R server shuts down. Systematically, at the OMC-R server
start-up, theendof notification31006issent after theendof notification 31007.
30404 MDserviceinterruption
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31007 : Immediate shutdown
Thisalarmnotificationispartof thesignallingprotocol betweentheMD-Randthe
manager duringastart-upandshutdownof theMD-R. WhenaQ3actionof type
start or switchover is requested, a beginning of notification 31007 is sent
beforetheOMC-R server shutsdown.
Byextension, beforeeachshutdownof theOMC-R server (for anytypeof action
requested: start, switchover, shutdown, defense action), a beginning of
notification 31007 is sent just before the OMC-R server shuts down.
Systematically, attheOMC-Rserver start-up, thebeginningof notification 31007
isresent, thentheendof thenotification31007issent.
30405 MDshutdown/switchover
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--88
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31008 : MD-R/Manager time difference has exceeded the threshold
cfDtDiffThreshold
The difference between the MD-R and the time manager has exceeded the
admissiblethresholddefinedbyCF for thetimeshifting(cfDtDiffThreshold).
SYSTEMACTION
Analarmisissuedfurther tothisnotification.
Note: This notification (and the alarm) exists only if the manager and the
mediationdevicearephysicallyseparated(external manager).
Theoperator mustupdatetheMDtimebyachangecommand(M-SET) onthemd
object, byassigningthenewtimetotheattributeexternalTime.
ADDITIONAL CHECK
After thetimesetting, thealarmautomaticallystops.
iii
Faultnumber:
31009 : The MD-R server has switched over
Thisnotificationisissuedwhenthereisaswitchover.
Thepassiveserver isinactivemode.
SYSTEMACTION
Innewdual-server configuration, thealarmautomaticallystops.
Executecf_majsecours.shfromtheactiveserver toupdatethebackupserver.
ADDITIONAL CHECK
Not applicable.
5--90
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31010 : BDE-BDA check-up
Thisnotification isissuedwhenadifferenceisdetectedbetweentheBDE andthe
BDA onanon-Q3attribute.
30270 Fault onattribute
30271 Fault onMD-R/BSC interfaceattribute
SYSTEMACTION
Not applicable.
Reset theBDA (on-line) andrebuildit (on-line).
ADDITIONAL CHECK
iii
Faultnumber:
31100 : Anomalies threshold exceeded
Thisnotification isissuedincasetheMD-R anomalythresholdiscrossed
SYSTEMACTION
Analarmwithdeferredinterventionisissued, if not alreadyexistent.
CheckthecorrectBSSprocessing, accordingtothemdWarningsetbytheoperator.
ADDITIONAL CHECK
5--92
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31200 : Counter exceeding upper threshold
Thisnotificationisissuedwhenthehighthresholdof theMDor manager counters
iscrossed.
Thesethresholdscanbedefinedinthreedifferent ways:
creationof amdWarningat theMMI onobservation counters (Refer to NTP
<128>)
creationof anoperator syntheticcounter
Thistool enablestheuser todefinehisownsyntheticobservationcounter(Refer
toNTP <129>).
definedbydefault inthefiles
/OMC/data/perf/bss_nmc_formulas.dat
Oneof thefollowingdefault countersiswritteninthecounterName fieldof the
alarm:
counter 8569 ratioof SCCP resourcefailure
counter 8628 qualityof Downlink AbisTRAU frame
counter 8707 ratioof TCH resourcefailureinthecell
counter 8714 ratioof thenumberof communicationsabnormallyreleasedin
trafficphaseinthecell
counter 8813 badvirtual timeslot
SYSTEMACTION
Analarmwithdeferredinterventionisissued, if onedoesnot exist already.
Theconfigurationof theattributesof theobjectsdefiningtheobservationcounters,
thehighthresholdsof themanager andtheMD-Rcounters, andthealarmpriorities
dependontheoperator.
5.5.78.1 Counter 8813 Bad virtual timeslot
Forthethresholdcrossingof thesyntheticcounter 8813faultyTrxNoBcch, execute
theprocedurebelow:
HOWTODETERMINE AFAULTYTRANSMISSIONCHAINWHICHDOESNOT
SUPPORT BCCH AND IS NOT DETECTED BY A STANDARD HARDWARE
SUPERVISION.
Purpose
This procedure describes the failure rate supervision mechanism of the
TCH assignment requests.
It describeshowtocustomizethecalculationformulaof thethresholdandhowto
determinethefaultyequipment.
Impact
CAUTION
Serviceinterruption
Loss of communications
Procedure
Description of the supervision mechanism
AnRXfailureisusuallydetectedbytheincreaseof thenumberof TCH assignment
request failures. A supervisionmechanismat theOMCR allowsthedetectionof
theRX failures.
The synthetic counter, faultyTrxNoBcch (8813), has been introduced. Its syntax
allowstheadditionof anewcalculationformulainthedefault syntheticcounters
definitionfiles/OMC/data/perf/bss_nmc_formulas.dat.
As usual, if the synthetic counter threshold is reached an alarmis raised. This
synthetic counter monitors thecells to check if thereis anabnormal assignment
failurerate. Tocalculatetheratio, refer toNTP <125>, Counter 8813.
5--94
PE/DCL/DD/0032
411--9001--032
Modification of the threshold
usetheSyntheticcounter editor describedinNTP <129>
check thefirst calculationformulaandmodifythethreshold
faultyTrxNoBcch[:on,6.9]
Thedefault thresholdvalueis 6.9. It isthenumber of badvirtual timeslots.
If thethresholdissuperior to 6.9, one total TDMA isfaulty.
Looking for the faulty equipment
Thealarmissuedonthecell isrelatedtoanotification 31200
COUNTER EXCEEDINGUPPER THRESHOLD
for thecounter faultyTrxNoBcch.
Exampleof relatednotification:
**** Notification: 173*************************************
occurredon25MarchYYYY23:32:04-- receivedon25MarchYYYY23:32:04
Type: qualityOfServiceAlarm<Severity:major>
Instance: bsc 18 (SW21BSC7) btsSiteManager 0 (BTS165) bts 0 (bsc 18 /
btsSM0/ bts0)
md: 1taskId: 751
Machine: 1
* Additional information: *************************
probableCause: (51)thresholdCrossed
specificProblems: 31200
faultNumber : (31200) COUNTEREXCEEDINGUPPERTHRESHOLD
omcCause: ERROR, idnot found: (30206)
Operator info: highThresholdValue: 6.9
counterValue: 12.083333<-- thisvalueisdefinedper cent
counterName: faultyTrxNoBcch
mdGranularityPeriod: 30
scanInitTime: 19970325230011.0+0900
If the alarmis issued for a cell with only two TRXs, the faulty equipment is
associatedtothe TRX whichdoesnotcarrytheBCCH. If thereisonlyone TRX,
nocommunicationspossible.
For all other cases, asthealarmisissuedfor thecell, it isnecessarytolookfor the
faultyequipment. Youcanproceedbyeliminationinthefollowingway:
1. Check the granularity period (mdGranularityPeriod) of the Fast Statistic
Observations:
intheOMCR Browser (OMC level) select the BSCmanagingthefaulty
cell
select themenuObject -- Display/Set
inthedescriptionwindow: selectthemdScannercorrespondingtothe OFS
andcheck themdGranularityPeriodfield
2. Clear thealarm:
intheOMCR Browser (OMC level) select theBSC managingthefaulty
cell
select themenu: Fault -- List alarms
inthewindowwhichdisplaysthealarms: select theappropriatealarmand
applytheclear command
3. Inthefaulty cell, determinewhichtransceiver equipment (TRX) carries the
BCCH anddrawupalist (L) of theothers:
a) select themenuObject -- Display/Set
b) intheOMCR Browser (Site/Multi-sitelevel) select thefirst transceiver
object (TDMA 0)
c) in the description window : select the object channel 0 and check the
channel type, it shouldbemainBcch, if yes, returnof thechannel object,
select DisplayAll andnotethenumber of the TRX carryingtheTDMA
(valueof thefieldsupportingTransceiverEquipment), if not, startinb) for
thenext transceiver object.
4. Lock oneof theTRXsnot carryingthe BCCH:
a) in the OMCR Browser (OMC level) select the transceiver equipment
object
b) select themenuObject -- Display/Set
c) inthedescriptionwindow: setthefieldMode: toSetadministrativeState
d) inthedescriptionwindow: set thefieldadministrativeStatetolocked
5--96
PE/DCL/DD/0032
411--9001--032
5. Wait for theendof theperiodmdGranularityPeriodandcheck thealarms:
if thealarmisstill raised, thelockedtransceiverequipment(TRX)isnotthe
faultyone.
unlocktheTRXandclear thealarm
6. Repeat Steps 4and 5for all TRXsnot carryingthe BCCHuntil thealarm
isnolonger issued.
Thefaultyequipment isrelatedtothelocked TRX.
5.5.78.2 Counter 8714 Ratio of the number of communications abnormally released in traffic
phase in the cell
For the threshold crossing of thesynthetic counter 8714: callDropTrafficRatio,
executetheprocedurebelow:
HOWTODETERMINE ACELL WITHHIGHCALLDROP THRESHOLD
Purpose
Thisproceduredescribesthecall dropratesupervisionmechanism.
It describeshowtocustomizethecalculationformulaof thethreshold.
Impact
CAUTION
Serviceinterruption
Loss of communications.
Procedure
A failureisusuallydetectedbytheincreaseof communicationsreleasedintraffic
phaseinthecell. A supervisionmechanismat theOMCRallowsthedetectionof
the failures.
Thesyntheticcounter, callDropTrafficRatio(8714), hasbeenintroduced. Itssyntax
As usual, if thesynthetic counter thresholdis reachedan alarmis reached. This
syntheticcounter monitorsthenumber of communicationrelease. Tocalculatethe
ratio, refer toNTP <125>, Counter 8714.
5--98
PE/DCL/DD/0032
411--9001--032
usetheSyntheticcounter editor describedin NTP <129>
callDropTrafficRatio[:on,30]
Thedefaultthresholdvalueis 30%bydefault. Thethresholdrequestisdifferent
operator byoperator.
Thereisanalarmif theratioof thenumberof communicationsreleasedintraffic
phase to the number of communications established in the cell is greater
than 30%duringthemdGranularityPeriod.
The value delivered by the counter 8714 is significant if the number of
successfull TCH assignment (counter 1050) isgreater than 20.
ADDITIONAL CHECK
Optimizethecell: look for interferenceproblemor faultyparameters.
5.5.78.3 Counter 8707 Ratio of TCH resource failure in the cell
For thethresholdcrossingof thesyntheticcounter 8707:
cellTchResourceFailureRatio, executetheprocedurebelow:
HOWTODETERMINE ACELL WITHHIGHTCHBLOCKINGRATE
Purpose
This procedure describes the failure rate supervision mechanism of the
TCH allocation.
Impact
CAUTION
Serviceinterruption
Overload cell. Risk of loss of communications.
Procedure
A failure is usually detected by a high blocking rate of the number of
TCH allocation in a cell. A supervision mechanismat the OMCR allows the
detectionof thefailures.
The synthetic counter, cellTchResourceFailureRatio (8707), is introduced. Its
syntax allows theaddition of anewcalculationformulainthedefault synthetic
countersdefinitionfiles/OMC/data/perf/bss_nmc_formulas.dat.
syntheticcounter monitorstheTCHallocationfailures. Tocalculatetheratio, refer
toNTP <125>, Counter 8707.
5--100
PE/DCL/DD/0032
411--9001--032
cellTchResourceFailureRatio[:on, 0.25]
Thereisanalarmif therateisgreater than 25%.
ADDITIONAL CHECK
Optimizethecell: addresourcesor look for faultyqueueingparameters.
5.5.78.4 Counter 8628 Quality of Downlink Abis TRAU frame
dlMutedAbisTrauFrameRate, executetheprocedurebelow:
HOWTODETERMINE THE QUALITY OF ANABIS PCMLINK
Purpose
Thisprocedureenablestomonitor qualityof thedownlink AbisPCM link.
Impact
CAUTION
Serviceinterruption
Disturbance of phonic or data quality. Risk of loss of
communications.
Procedure
A failureisusually detectedby theincreaseof thenumber of mutedor corrected
DownlinkAbisTRAUframes. A supervisionmechanismattheOMCRallowsthe
detectionof thefailures.
A syntheticcounter, dlMutedAbisTrauFrameRate(8628), isintroduced. Itssyntax
syntheticcountermonitorsthequalityof downlinkAbislink. Tocalculatetheratio,
refer toNTP <125>, Counter 8628.
5--102
PE/DCL/DD/0032
411--9001--032
dlMutedAbisTrauFrameRate[:on,0.005]
Thedefaultthresholdvalueis 0.005(5.10
-3
) bydefault. Thethresholdrequestis
different operator byoperator.
For agoodqualityof radiolink transmission:
theBit Error Rate(BER) <10
-5
without PCM error correction
theBit Error rate<10
-4
withactivePCM error correction
Risk of lost communicationswiththethresholdsuperior to 10
-3
.
ADDITIONAL CHECK
Check thePCM link, together withthetransmissionprovider.
ReplacetheDDTI interfaceboardof theBSC (refer toNTP <41>).
Replace the DTI or PCMI or CPCMI interface board of the BTS (refer to
NTP <46>, <47>, <48>, <49>or <84>).
5.5.78.5 Counter 8569 Ratio of SCCP resource failure
sccpResourceFailureRatio, executetheprocedurebelow:
HOWTODETERMINE ANSCCP CONNECTIONFAILURE
Purpose
This procedure describes the supervision mechanism of the SCCP resource
saturation.
Impact
CAUTION
Serviceinterruption
Risk of loss of communications.
Procedure
An SCCP resourcesaturationisusuallydetectedbytheincreaseof thenumber of
SCCP connectionrefusals. A supervisionmechanismat theOMCR allows the
detectionof thesaturation.
Thesyntheticcounter, sccpResourceFailureRatio(8569), isintroduced. Itssyntax
synthetic counter monitorstheresourcesaturation. Tocalculatetheratio, refer to
NTP <125>, Counter 8569.
5--104
PE/DCL/DD/0032
411--9001--032
sccpResourceFailureRatio[:on,0.2]
Thereisanalarmif theratioof thenumber of SCCP connectionrefusalstothe
number of SCCP connectionsallocatedisgreater than 20%.
ADDITIONAL CHECK
Troubleshoot withtheMSC team.
iii
Faultnumber:
31201 : Counter exceeding lower threshold
Thisnotificationisissuedwhenthelowthresholdof theMDor manager counters
iscrossed.
Thesethresholdsaredefinedintwoways:
creation of an mdWarning at the MMI on observation counters (refer to
NTP <128>)
creationof asyntheticcounter (refer toNTP <129>)
definitioninthefilesOMC/data/perf/bss_nmc_formulas.dat
SYSTEMACTION
Analarmwithdeferredinterventionisissued, if onedoesnot alreadyexist.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--106
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31300 : Filling threshold exceeded
Thisnotification isissuedwhenthefillingthresholdiscrossed.
31303 ThresholdcrossedonFAULT partition
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31400 : Message BSC number different fromlink BSC number
ThisnotificationisissuedwhentheOMC-RreceivesaBSC number inamessage,
different fromthenumber usedinthelink withthis BSC.
SYSTEMACTION
OMN link withthisBSC broken.
Check theX.25addressesof theBSC, ontheOMC-R.
If theseaddressesarecorrect, recustomizethediskof theBSCactivechain, byusing
theTML (refer toNTP <50>).
ADDITIONAL CHECK
Not applicable.
5--108
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31401 : Unknown association identity
Thisnotificationisissuedwhenthe BSCsendsa RGEonanunknownassociation.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31402 : Unknown family identity
Thisnotification isissuedwhena BSCsendsa RGE onanunknownassociation
family
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--110
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31403 : Unknown CODOP
Thisnotification isissuedwhena BSCsendsa RGE withanunknownoperation
code.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31404 : Message of association family not expected
Thisnotificationisissuedwhenthetask managingtheoperatedsystemsreceives
amessageviolatingtheSEPE protocol.
SYSTEMACTION
Not applicable.
Call the manufacturer.
ADDITIONAL CHECK
Not applicable.
5--112
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31405 : Processing of current spontaneous message aborted after
reception of newspontaneous message
This notification is issuedwhen thetask managingtheoperatedsystems of the
OMC-R receives a new BSC event whereas the previous event sent by the
same BSC isnot yet acknowledged.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31406 : Reception of a message on a no-etablished association
Thisnotification isissuedwhenthetaskmanagingthe OMC-Roperatedsystems
receivesa BSC messageviaanon-establishedassociation.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--114
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31407 : Reception of a negative TGE acknowledgement
Thisnotification isissuedincaseof theacknowledgement hasnot beenreceived
intheassignedtime.
SYSTEMACTION
Not applicable.
Modifytheincriminatedattributeor rebuildtheBDA.
ADDITIONAL CHECK
iii
Faultnumber:
31408 : Renunciation of TGE sending attempts
Thisnotification isissuedwhenthe RGE waitingtimeexpires.
SYSTEMACTION
Not applicable.
Modifytheincriminatedattribute.
ADDITIONAL CHECK
5--116
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31409 : Spontaneous messagenotacknowledgedwithinagreedtime
by application
Thisnotification isissuedwhenanacknowledgementhasnotbeenreceivedinthe
assignedtime
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
iii
Faultnumber:
31500 : RGE not expected
Thisnotification isissuedincaseof areceptionof anunexpected RGE.
SYSTEMACTION
Not applicable.
RelaunchthecommandwhentheBSC islessloaded.
ADDITIONAL CHECK
Not applicable.
5--118
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31501 : No BSC response for association supervision
This notificationis issuedwhenaBSC doesnot reply to an OMC-R monitoring
request.
SYSTEMACTION
Not applicable.
Control theBSC stateandcheck itsoperation.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31600 : LAPB down
Thisnotificationisissuedwhenthelevel 2of anX.25linktoa BSCortoamanager
isout-of-service.
The X.25 links are monitored cyclically and fault number 31600 is issued to
indicatetheinitiationof analarmor theendof analarmdependingonthechange
of state.
SYSTEMACTION
Not applicable.
Call themanufacturer of theX.25links.
ADDITIONAL CHECK
Not applicable.
5--120
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31700 : Several unsuccessful logins
Type : Alarm
Thisnotificationisissuedfor threeunsuccessful loginsof MMI session.
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
iii
Faultnumber:
31800 : The followingcounters are not available for the current BSC
release
This warning notification is issued during the creation or modification of the
bscCounterList object when the counters are not available for thecurrent BSC
version. Thenonvalid countersarelistedinthenotification.
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5--122
PE/DCL/DD/0032
411--9001--032
iii
Faultnumber:
31801 : The request did not succeed to the following counters
This notification is issued for the ADD and REMOVE Q3 request in
bscCounterList if countersmust beaddedor arealreadypresent.
Thesources(V12--V15) or causescanbe:
31850 The following counters are already present in the bscCounterList
(ADD)
31851 ThefollowingcountersarealreadymissingfromthebscCounterList
(REMOVE)
SYSTEMACTION
Not applicable.
Not applicable.
ADDITIONAL CHECK
Not applicable.
5.5.97 Faultnumbers: 39500and39550
iii
Faultnumber:
39500 and 39550 : Anomalies threshold exceeded
Themanagementof thealarmcriteriaenablestodefinecriteriainorder togenerate
alarmsforexcessiveanomalyrate. Forthistypeof alarm, theusercanusesynthetic
fault numbers (range between 39500 and 39550). Pre-defined criteria are
availableinthestandardconfiguration.
Thehighthresholdlevel tothealarmisequal totheoccurrencenumber of afault
number.
CONFIGURATION
TYPE
MANUFACTURER OPERATOR MANUFACTURER OPERATOR
Criterion number 500 50000 501 50100
Synthetic fault
number 39550 39500 39550 39500
Object transcoder pcmCircuit
Alarmcondition
Fault number 493
High threshold level
to generate the
alarm
10
Lowthreshold level
to cease the alarm 0
Accounting
reference period (s) 60
AlarmDuration (s) 3600
Example:
thecriterionnumber 500meansthatanalarmof faultnumber 39550isgenerated
if more than 10 fault numbers 493 on the same transcoder object are sent
during 60s. Thealarm 39550 is ceased if thereis no fault number 493 (low
thresholdlevel) after thealarmduration (3600s).
5--124
PE/DCL/DD/0032
411--9001--032
Note: Criteria 50x and 50x00 are associated: the first one belongs to the
Manufacturer configuration, the other one belongs to the Operator
configuration.
A criterion is only processed if its administrative state is unlocked and
accordingtotheactiveconfigurationchosenbytheuser (parameteralarm
criteria intheOMC object):
operator criterionwhenthealarmcriteria parameter isset today
configuration or night configuration or specificconfiguration
manufacturer criterionwhenthealarmcriteria parameter is set to
referenceconfiguration.
SYSTEMACTION
A qualityof service alarmisgeneratedif thereisnoalarmontheparent object.
Thealarmisgeneratedandmaintainedovera3600 secondsperiod(valueof alarm
duration parameter whichcanbeset inalarmcriteriamanagement function) in
order togivetheoperator sometimetoreact.
Thisalarmisclearedif therearenofurther notificationsof thesametype.
Refer to NTP <101>which describes the fault number 493 defined in alarm
condition.
ADDITIONAL CHECK
Rferr to NTP <101>which describes the fault number 493 defined in alarm
condition.
iii
Faultnumber:
number.
CONFIGURATIONTYPE MANUFACTURER OPERATOR
Criterion number 502 50200
Synthetic fault number 39551 39501
Object transceiverEquipment
Alarmcondition Fault
number 1070
High threshold level to
generate the alarm 10
Lowthreshold level to
cease the alarm 0
Accounting reference
period (s) 60
Example:
thecriterionnumber 502meansthat analarmof fault number 39551isgenerated
if morethan10faultnumbers 1070onthesametransceiverEquipmentobjectare
sentduring60s. Thealarm 39551isceasedif thereisnofaultnumber 1070(low
thresholdlevel) after thealarmduration(3600s).
5--126
PE/DCL/DD/0032
411--9001--032
Note: Criteria 502 and 50200 are associated: the first one belongs to the
configuration.
SYSTEMACTION
Refer toNTP<102>, <103>or <104>whichdescribesthefaultnumber 1070
definedinalarmcondition.
ADDITIONAL CHECK
Refer toNTP<102>, <103>or <104>whichdescribesthefaultnumber 1070
definedinalarmcondition.
iii
Faultnumber:
number.
Object transcoderBoard
number 1182
cease the alarm 0
period (s) 60
Example:
thecriterionnumber 503meansthat analarmof fault number 39552isgenerated
if morethan10 faultnumbers 1182onthesametranscoderBoardobjectaresent
during 60s. Thealarm 39552is ceasedif thereis no fault number 1182 (low
5--128
PE/DCL/DD/0032
411--9001--032
configuration.
SYSTEMACTION
Thealarmisgeneratedandmaintainedovera3600secondsperiod(valueof alarm
Refer to NTP <101>which describes thefault number 1182 defined in alarm
condition.
ADDITIONAL CHECK
condition.
iii
Faultnumber:
number.
Object transceiverBoard
number 1183
cease the alarm 0
period (s) 60
Example:
if morethan10 faultnumbers 1183onthesametranscoderBoardobjectaresent
during60s. Thealarm 39553is ceasedif thereis no fault number 1183 (low
5--130
PE/DCL/DD/0032
411--9001--032
configuration.
SYSTEMACTION
condition.
ADDITIONAL CHECK
condition
iii
Faultnumber:
number.
Object pcmCircuit
number 1193
cease the alarm 0
period (s) 60
Example:
if more than 10 fault numbers 1193 on the same pcmCircuit object are sent
5--132
PE/DCL/DD/0032
411--9001--032
configuration.
SYSTEMACTION
condition.
ADDITIONAL CHECK
condition.
iii
Faultnumber:
number.
number 1185
cease the alarm 0
period (s) 60
Example:
if morethan 10faultnumbers 1185onthesametranscoderBoardobjectaresent
5--134
PE/DCL/DD/0032
411--9001--032
configuration.
referenceconfiguration
SYSTEMACTION
condition.
ADDITIONAL CHECK
Refer to NTP <101>whichdescribes thefault number 1185 definedinalarm
condition.
iii
Faultnumber:
number.
number 1186
cease the alarm 0
period (s) 60
Example:
if morethan 10faultnumbers 1186onthesametranscoderBoardobjectaresent
during 60s. Thealarm 39556 is ceased if thereis no fault number 1186 (low
5--136
PE/DCL/DD/0032
411--9001--032
configuration.
SYSTEMACTION
condition.
ADDITIONAL CHECK
condition.
5.5.104 Faultnumbers: 39507to 39549and39557to 39599
iii
Faultnumber:
39507 to 39549 and 39557 to 39599 : Anomalies threshold exceeded
fault numbers 395xx. Pre-defined criteria are available in the standard
configuration.
number.
Criterion number 50x 50x00
Synthetic fault number 39557 to 39599 39507 to 39549
Object ------
number ------
cease the alarm 0
period (s) 60
Example:
thecriterionnumber 50xmeansthatanalarmof faultnumber 395xxisgenerated
if morethan 10faultnumbers------onthesame------objectaresentduring 60s.
Thealarm 395xxisceasedif thereisnofaultnumber ------(lowthresholdlevel)
after thealarmduration(3600s).
5--138
PE/DCL/DD/0032
411--9001--032
configuration.
SYSTEMACTION
Not applicable.
ADDITIONAL CHECK
Not applicable.
5.6 BDAaudit1
Presentation
Thisprocedureallowsuserstocheck theconsistency betweentheBDE (OMC-R
database) andtheBDAs(BSC databases) of oneor all BSCs.
Thefollowingoperationsshouldbeperformedfromaworkstation.
Inputparameters
administratorPassword: passwordof theOMC-R user administrator
bscList: list of bscNumber toprocess
Initial status
TheOMC-RapplicationisrunningandtheUNIX or MMI isaccessibleonthelocal
machine.
ThebscMdInterfaceobject connectedtotheBSC isoperational.
Actions
TheUNIXisaccessibleonthelocal machine.
ONALOCAL OMC-RWORKSTATION
1. If not already done, openaUNIX windowandloginto theOMC-R under
administrator user withadministratorPassword.
2. For eachbscNumber inbscList:
{
Executethetool:
Under omc l ogi n:
. . . ( omc) %/ usr/ l ocal / oam/ bi n/ ds_audi tBDA. sh - BbscNumber
The tool performs a BDA audit and displays the message OK if no
difference, otherwiseKO.
Thistakesawhile. Continuewithanother bscNumber.
}
5--140
PE/DCL/DD/0032
411--9001--032
ORtheMMI isaccessibleonthelocal machine.
1. If not already done, log in to the OMC-R under administrator user with
administratorPassword.
2. For eachbscNumber inbscList:
{
GOTO OMC--R Browser
If thebscMdInterfaceislocked: unlock it.
SELECT_OBJ BSC bscNumber
SELECT Configuration--BDA -- Audit -- Apply
GOTO Sessionlog
Themessagenodifferenceisdisplayed.
}
Troubleshooting
1. Seethelogfile/ var / l ocal / oam/ bscNumber . ds_audi t BDA. l og.
2. Nodatamismatchisaccepted, otherwiseanupdateoperationisnecessary.
Final status
TheOMC-R andBSC databases(BDE andBDAs) areconsistent.
OMC--RPreventiveandCorrectiveMaintenanceManual
Copyright 1999--2004Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL:
The informationcontainedinthis document is the property of Nortel
Networks. Except as specifically authorizedinwritingby Nortel
Networks, the holder of this document shall keepthe information
containedhereinconfidential andshall protect same inwhole or inpart
fromdisclosure anddisseminationto thirdparties anduse for evaluation,
operationandmaintenance purposes only.
Youmay not reproduce, represent, or downloadthroughany means, the
informationcontainedhereininany way or inany formwithout prior
writtenconsent of Nortel Networks.
The followingare trademarks of Nortel Networks: *NORTEL
NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL
Globemark, S2000, S2000E, S2000H, S2000L S4000, S8000, S8002.
GSMis a trademark of FranceTelecom. Sun, Ultrastation, Ultra5, Ultra
Enterprise are registeredtrademarks of SunMicrosystems, Inc.
All SPARC trademarks are usedunder license andare trademarks or
registeredtrademarks of SPARC International, Inc. inthe UnitedStates
andother countries. Sybase is a registeredtrademark of Sybase, Inc.
Lexmark is a registeredtrademark of Lexmark International, Inc.
All other brandandproduct names are trademarks or registered
trademarks of their respective holders.
PublicationReference
PE/DCL/DD/0032 411--9001--032
15.03/EN
March 2004
OriginatedinFrance
For more information, please contact:
For all countries, except USA:
DocumentationDepartment
Parc dactivit de Magny--Chateaufort
CHATEAUFORT
78928YVELINES CEDEX 9
FRANCE
Email : umts--gsm.ntp@nortelnetworks.com
Fax : (33) (1) 39--44--50--29
In the USA:
2221Lakeside Boulevard
RichardsonTX 75082
USA
Tel: 1--800--4NORTEL
1--800--466--7838or (972) 684--5935
Internet Address:
http://www.nortelnetworks.com

OMCR Manual

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OMCR Manual

Загружено:

Авторское право:

Доступные форматы

Wireless Service Provider Solutions

Вам также может понравиться