D02654GS A0 RC1 OMC Server Guide

AllIPCDMA2000|GSM
12
SonataCoreVoiceNetwork
UG
IS41R4.5.3|GSMR4.5.4|SRANR4.5.3
OperationsandMaintenanceCenter
ServerGuide 2A
1 _2
_ RC
PartNumberD02654GSRevA0RC1
A0
AllIPCDMA2000|GSM
12
UG
IS41R4.5.3|GSMR4.5.4|SRANR4.5.3
OperationsandMaintenanceCenter
GSMR4.5.4|IS41R4.5.3|SRAN 2A
R4.5.3
_2
C1
_R
A0
Copyright2012,StarSolutionsInternationalULC.Allrightsreserved.Nopartofthisdocumentationmaybereproducedinany
formorbyanymeansorusedtomakeanyderivativework(suchastranslation,transformation,oradaptation)withoutprior
writtenpermissionfromStarSolutionsInternationalULC.
StarSolutionsInternationalULCreservestherighttorevisethisdocumentationandtomakechangesincontentfromtimeto
timewithoutobligationonthepartofStarSolutionsInternationalULCtoprovidenotificationofsuchrevisionorchange.
StarSolutionsInternationalULCprovidesthisdocumentationwithoutwarrantyofanykind,eitherimpliedorexpressed,
including,butnotlimitedto,theimpliedwarrantiesofmerchantabilityandfitnessforaparticularpurpose.StarSolutions
InternationalULCmaymakeimprovementsorchangesintheproduct(s)and/ortheprogram(s)describedinthisdocumentation
atanytime.
UNITEDSTATESGOVERNMENTLEGENDS:
IfyouareaUnitedStatesgovernmentagency,thenthisdocumentationandthesoftwaredescribedhereinareprovidedtoyou
subjecttothefollowing:
12
UnitedStatesGovernmentLegend:Alltechnicaldataandcomputersoftwareiscommercialinnatureanddevelopedsolelyat
privateexpense.SoftwareisdeliveredasCommercialComputerSoftwareasdefinedinDFARS252.2277014(June1995)orasa
commercialitemasdefinedinFAR2.101(a)andassuchisprovidedwithonlysuchrightsasareprovidedinStarSolutions's
standardcommerciallicensefortheSoftware.TechnicaldataisprovidedwithlimitedrightsonlyasprovidedinDFAR
252.2277015(Nov1995)orFAR52.22714(June1987),whicheverisapplicable.Youagreenottoremoveordefaceanyportion
ofanylegendprovidedonanylicensedprogramordocumentationcontainedin,ordeliveredtoyouinconjunctionwith,this
UG
UserGuide.
StarSolutions,theStarSolutionslogo,iCell,Softexchange,Sonata,SonataAccessTandem,SonataHLR,SonataIP,SonataMSC,
SonataWLL,andTelosareregisteredtrademarksortrademarksofStarSolutionsInternationalULCanditssubsidiaries.
CDMA2000isaregisteredtrademarkoftheTelecommunicationsIndustryAssociation(TIAUSA).
IntelandPentiumareregisteredtrademarksoftheIntelCorporationoritssubsidiariesintheUnitedStatesandothercountries.
2A
Microsoft,Windows,WindowsNT,andNetMeetingareregisteredtrademarksofMicrosoftCorporation.Sun,Java,andSolaris
aretrademarksorregisteredtrademarksofSunMicrosystems,Inc.OracleisaregisteredtrademarkofOracleCorporation.HP,
HPUX,andHPOpenviewaretrademarksorregisteredtrademarksoftheHewlettPackardCompany.UTStarcom,theUTStarcom
logo,MovingMedia,mSwitch,andTotalControlareregisteredtrademarksortrademarksofUTStarcom,Inc.anditssubsidiaries.
Otherbrandandproductnamesmayberegisteredtrademarksortrademarksoftheirrespectiveholders.
_2
C1
_R
A0
CONTENTS
ABOUTTHISGUIDE
Conventions 10
Notices 10
12
FiguresandScreenCaptures 10
Text 10
RelatedDocumentation 11
UG
TechnicalSupport 14
ObtainingTechnicalAssistance 14
ServiceCentersOperationalHours 14
WarrantySupport 15
ContactingTechnicalDocumentation 15
PARTI OMCOVERVIEW
2A
1 OMCOVERVIEW
_2
OperationsandMaintenanceCenterOverview 19
OMCFeatures 20
ManagementFeatures 20
1
SystemArchitecture 21
LDAP 21
RC
NetworkElementFramework 22
DRUMontheNE 22
RCPontheNE 22
Multihoming 23
_
Active/StandbyConfiguration 23
AutomaticNEDiscovery 23
A0
SNMP 24
SNMPTrapForwarder 24
MultipleSNMPAgents 24
BSCandBTSStateInformation 24
PerformanceTables 24
Performance(Subsystem)Upgrade 24
ArchiveManagement 24
UpdatestoSummarizedPeformanceFiles 24
ACM2SupportfortheBSS 25
AutomatedBSSUpgrade 25
PARTII OMCCONFIGURATION ANDOPERATION
STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|SRAN

R4.5.3OperationsandMaintenanceCenterServerGuide
6 Contents
2 OMCSERVERCONFIGURATION
SNMPEventForwarding 29
Active/StandbyConfiguration 29
DRUMPassword 29
OMCProxyConfiguration 30
ConfiguringtheOMCtoSupporttheNEs 31
RetrievingtheNodespecificNEFFiles 31
MergingtheNEFFilesontheOMCServer 31
MergingtheCONXandNENEFFiles 32
12
NonstandardNEAccountPasswords 33
ConfiguringBSC/BTSReachthroughforSRANOMC 33
HourlyPerformanceFiles 34
PerformanceFilesontheSonataNEs 35
UG
BSSPerformanceReports 35
CallDetailRecords 35
3 OMCOPERATIONS ANDTROUBLESHOOTING
2A
OMCOperations 37
StoppingandStartingtheOMC 37
QueryingtheOMCStatus 37
StartingandStoppingDRUM/SNMPForwarder 38
_2
QueryingDRUM/SNMPForwarderStatus 38
CreatingandDeletingRCPs 38
NEStateInformation 38
RealTimePerformanceData 38
1
RemotePackageInstallation 39
OMCTroubleshooting 40
RC
OMCServerTroubleshooting 40
CheckOMCServerConnections 41
OMCConsoleCPU,Memory,DiskI/O,NetworkI/O 41
PostinstallTroubleshooting 42
_
DRUMandSNMPForwarderTroubleshooting 42
CheckingtheDRUMorSNMPForwarderOMCServerConnection 42
A0
RCPTroubleshooting 43
OMCBSSTroubleshooting 44
IncorrectTrapOID 44
NoBSSFaultsorPerformanceReportsontheOMC 44
AutomatedBSSUpgrade 44
PARTIII APPENDIXES
A ACRONYMS
INDEX

ListofTables 7
LISTOFTABLES
Table 1 NoticeIconDescriptions 10
Table 2 TextConventionDescriptions 10
Table3 AccounttoProductMappingforDRUMconfiguration 30
Table 4 ListofAcronyms 47
12
UG
2A
1 _2
_ RC
A0

8 ListofFigures
LISTOFFIGURES
Figure 1 CoreVoiceNetworkDocumentMap 12
12
UG
2A
1 _2
_ RC
A0

ABOUTTHISGUIDE
Thisguidedescribeshowtoconfigure,operate,maintain,andtroubleshootthe
12
OMCServer.Thisguideisintendedfornetworkoperations,support,IPtelephony
systemsplanningpersonnel,andsystemadministrators.Priorexperiencewith
SunSolarisoperatingsystems,telecommunications,IPtelephony,and
networkingisrecommended.
UG
TheAboutthisGuidesectionincludes:
Conventions
RelatedDocumentation

2A
TechnicalSupport
WarrantySupport
ContactingTechnicalDocumentation
_2
ThisguidecoversthebasereleaseoftheOMCServerfortheIS41Release4.5.3,
GSMRelease4.5.4,andSRANMobilityServerRelease4.5.3.Releasenotesare
availablefortheOMCServerforpatchlevelsafterthebaserelease.Ifthe
informationinthereleasenotesdiffersfromtheinformationinthisguide,follow
1
theinstructionsinthereleasenotes.
_ RC
A0
STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

ServerGuide
10 AboutThisGuide
Conventions Thisguidemaycontainnotices,figures,screencaptures,andcertaintext
conventions.
Notices Table 1listsnoticeiconsusedinthisguide.
Table 1NoticeIconDescriptions
Icon NoticeType Description

InformationNote Informationthatcontainsimportantfeaturesor
instructionsbutisnothazardrelated.
12
Cautionor CautionsareprecededwiththewordCaution.This
Warning typeofcautionindicatesapotentiallyhazardous
situationwhich,ifnotavoided,mayresultinminor
ormoderateinjury.Itmayalsoalertagainstunsafe
UG
Cautionor
Warningdueto practicesandpotentialprogram,data,system,or
potential devicedamage.
electricalhazard WarningsareprecededwiththewordWarning.This
typeofwarningindicatesapotentiallyhazardous
situationwhich,ifnotavoided,couldresultindeath
orseriousinjury.
2A Warningsduetopotentialelectricalhazardsare
precededwiththewordWarning.Thistypeof
warningindicatesapotentialelectricalhazard.This
hazard,ifnotavoided,couldresultindeathor
seriousinjury.
_2
ESD Informationthatindicatespropergrounding
precautionsarerequiredbeforehandlingaproduct.
1
FiguresandScreenCaptures Thisguideprovidesfiguresandscreencapturesasexamples.Theseexamples
containsampledata.Thisdatamayvaryfromtheactualdataonaninstalled
RC
system.
Text Table 2liststextconventionsinthisguide.

Table 2TextConventionDescriptions
_
Convention Description
A0
Textrepresentedasscreen Thistypefacerepresentstextthatappearsona
display terminalscreen,forexample:login:.
Textrepresentedasuser Thistypefacerepresentscommandsenteredbythe
entry. user,forexample,cd$HOME.
Textrepresentedasmenus, Thistypefacerepresentsallmenus,submenus,buttons,
submenus,buttons,tabs, tabs,directories,andfieldnameswithinprocedures,for
directories,andfieldnames example:
OntheFilemenu,clickNew.
Textrepresentedby Thistypefacerepresentsarequiredvariable,for
<variable> example:<filename>

ServerGuide
RelatedDocumentation Figure 1mapstherelationsamongthedocumentsintheStarSolutionsSonata

CoreVoiceNetworkdocumentationsetandsuggestsanorderinwhichtoread
them.Forexample,tooperateandmaintaintheSignalingServer(SSVR),the
documentmapsuggestsreadingthedocumentsinthefollowingorder:
1 IS41orGSMSystemOverviewGuide
2 IS41orGSM,andOMCReleaseNotes(BaseLevelandanyPatchLevel)
3 CoreVoiceNetworkInstallationandInitialConfigurationGuideorcPCISystem
InstallationandInitialConfigurationGuide(initialinstallonly)
12
4 OMCServerGuide(initialinstallonly)
5 OMCUserInterfaceGuide
6 CoreVoiceNetworkOperations,Maintenance,andProvisioningGuide
UG
7 MSCServerProvisioningGuideandMSCServerOperationsandMaintenance
Guide,orHLR/AuthenticationCenterGuide
8 SignalingServerGuide
2A
1 _2
_ RC
A0

ServerGuide
12 AboutThisGuide
Figure 1CoreVoiceNetworkDocumentMap
IS41R4.5.4SystemOverviewGuide
GSMR4.5.4SystemOverviewGuide
SonataCoreVoiceNetwork SonataCoreVoiceNetwork
IS41R4.5.4BaseLevelReleaseNotes
SonataCoreVoiceNetwork IS41R4.5.4PatchLevelReleaseNotes
GSMR4.5.4BaseLevelReleaseNotes GSMR4.5.4PatchLevelReleaseNotes
SonataOperationsandMaintenanceCenter SonataOperationsandMaintenanceCenter
OMCR4.5.4BaseLevelReleaseNotes OMCR4.5.4PatchLevelReleaseNotes
12
InstallationandInitialConfigurationGuide
cPCISystemInstallationandInitCfgGuide
UG
SonataOperationsandMaintenanceCenter
OMCR4.5.4ServerGuide
SonataOperationsandMaintenanceCenter
2A
OMCR4.5.4UserInterfaceGuide
IS41/GSMR4.5.4Ops,Maint&ProvisioningGuide
_2
SonataSoftExchange
IS41R4.5.4MSCServerProvisioningGuide
SonataSoftExchange
GSMR4.5.4MSCServerProvisioningGuide SonataFeatureServer
IS41R4.5.4HLR/ACGuide
1
SonataFeatureServer
SonataSoftExchange GSMR4.5.4HLR/AuCGuide
IS41R4.5.4MSCServerOps&MaintGuide
RC
SonataSoftExchange
GSMR4.5.4MSCServerOps&MaintGuide
SonataSoftExchange SonataFeatureServer
IS41/GSMR4.5.4MediaResourceFunctionGuide IS41/GSMR4.5.4SignalingServerGuide
_
SonataSoftExchange
A0
IS41/GSMR4.5.4LawfulInterceptGuide
GuidesforIS41systems
SonataSoftExchange
IS41/GSMR4.5.4CallConferenceServGuide GuidesforGSMsystems
GuidesforIS41andGSMsystems
SonataSoftExchange
IS41/GSMR4.5.4Media/SignalingGwGuide Thisguide

ServerGuide
TheCoreVoiceNetworkOperations,Maintenance,andProvisioningGuideand
theOMCUserInterfaceGuidecontaincommonproceduresandinformationfor
allCoreVoiceNetworknodesexcepttheCallConferenceServerand
Media/SignalingGateway.ReadtheCoreOMPGuidepriortoreadingthe
nodespecificguides.
Theothernodespecificguidesare:
MSCServerProvisioningGuide,whichcontainstheMSCspecifictablesand
howtoprovisionthem.
12
MSCServerOperationsandMaintenanceGuide,whichcontainsthe
MSCspecificproceduresforoperatingandmaintainingtheMSCServer,such
asproceduresrelatedtoupperlayercallprocessingprotocols,CallDetail
Records(CDR),andMSCspecificalarms.
UG
HLRandAuthenticationCenterGuide,whichcontainsallHLRspecific
provisioning,operationsandmaintenanceprocedures,andHLRspecific
alarmsetc.
MRFGuide,whichcontainsadescriptionofthetonesandannouncements
2A
availabletotheMSC,adescriptionoftheMediaResourceFunction(MRF),
andoperations,maintenance,andprovisioningproceduresspecifictothe
AccessServer.
LawfulInterceptGuide,whichcontainsadescriptionoftheLawfulIntercept
_2
service,thecomponentsthatareinvolvedtheservice,andtheoperations,
maintenance,andprovisioningspecifictotheLawfulInterceptServerand
service.
CallConferenceServerGuide,whichcontainsadescriptionoftheCall
1
ConferenceServer,adescriptionofthethreewaycallfunctionality,and
operations,maintenance,andprovisioningproceduresspecifictotheCall
RC
ConferenceServer.
_
A0

ServerGuide
14 AboutThisGuide
TechnicalSupport TheStarSolutionsProductSupportTeamdeliversthesupportservicesrequired
forbusinessandprofessionalneeds.OurproductexpertsdeliverTier1,2and3
technicalsupportdirectlytonewandcontractentitledcustomersincludingthe
followingservices:
BasicSupportPackage:Nonemergencytechnicalsupport
PremiumSupportPackage:24hoursaday,7daysaweek,and365daysayear
Emergencytechnicalsupport
12
TheStarSolutionsServiceGuideoutlinesthespecificdetailsforobtaining
technicalsupport.Theguideisavailablefromasalesaccountmanager.Referto
theServiceGuideforservicesandoptionsspecifictoindividualsupportplans,
includingguidelinesforproblemseverityandthetechnicalresolutionescalation
UG
process.
ObtainingTechnical StarSolutionsmaintainsaglobalpresencethroughitsTechnicalResponseand
Assistance ServiceCenters.Thesecentersareavailablefortechnicaltelephonesupportto
entitledcustomersduringnormalbusinesshours.

2A
Beforecontactingtechnicalsupport,havethisinformationavailable:
Productinformation
Softwareandhardwarerevisions
_2
Serialnumbers
Problemdescription
Symptoms
1
Knowncauses
RC
Troublelocatingandclearingattempts.
Forinformationaboutcustomerservice,includingsupport,training,code
releasesandupdates,contracts,anddocumentation,contactusat:
_
http://www.starsolutions.com/support
A0
ServiceCentersOperationalHours
NorthAmerica/CALARegion:
09:0018:00PacificTime(UTC8:00)
EMEA/AsiaPacificRegion:
09:3018:30IndianStandardTime(UTC+5:30)

ServerGuide
WarrantySupport 15
WarrantySupport StarSolutionsprovidesitscustomerswarrantysupportperthetermsoftheStar
SolutionsWarrantyStatementfortheirequipment.Customerswhorequire
warrantysupportshouldcontacttheStarSolutionsCustomerServiceCenteras
specifiedinthecustomerserviceguideorat:
http://www.starsolutions.com/servicesupport
ContactingTechnical Toprovidecommentsonthisdocumentation,sendanemailto:
Documentation
12
techcom@starsolutions.com
Pleaseincludethenameandpartnumberoftheguidebeingreferenced.If
applicable,providethechapterandpagenumber.
UG
2A
1 _2
_ RC
A0

ServerGuide
A0
_ RC
1 _2
2A
UG
12
OMCOVERVIEW
I
Chapter 1 OMCOverview
12
UG
2A
1 _2
_RC
A0
A0
_ RC
1 _2
2A
UG
12
OMCOVERVIEW
1
ThischapterprovidesanoverviewoftheStarSolutionsSonataOperationsand
MaintenanceCenter(OMC)featuresandoperation.
Thischapterincludes:
OperationsandMaintenanceCenterOverview
OMCFeatures
SystemArchitecture
AutomaticNEDiscovery
SNMP
PerformanceTables
Performance(Subsystem)Upgrade
ArchiveManagement
ACM2SupportfortheBSS
AutomatedBSSUpgrade
Operationsand TheOperationsandMaintenanceCenter(OMC)isascalableElement
MaintenanceCenter ManagementsolutionforStarSolutionsSonataCoreVoiceNetworkandiCell
Overview AccessNetworkproducts.ItprovidescentralizedElementManagementfor
distributedsystemsandcomponentsthroughawebbaseduserinterface.
TheOMCrunsinaclientserverconfiguration.TheserverrunsontheSun
MicrosystemsSolaris8operatingsystem;theclient(alsoknownastheOMC
Console)isaJavabasedapplicationlaunchedfromawebserverandrunsin
MicrosoftWindows2000orXP,oronaUNIXworkstation,usinganInternet
browser.
TheOMCoperatorusestheOMCConsoletoviewnetworkalarms,performance
statistics,andaccountinginformation,andtoperformnetworkandsecurity
configurationforthefollowingCoreVoiceNetworkelements:
MSC
HLR
SignalingServer(SSVR)
AccessServer(MRF)
LawfulInterceptServer

GSMR4.5.4|IS41R4.5.3|SRANR4.5.3ServerGuide
20 Chapter1:OMCOverview
TheOMCConsoleallowsforalarmandperformancestatisticsmonitoringforthe
followingAccessNetworkelements:
iCellBaseStationController(BSC)
iCellBaseTransceiverStation(BTS)
SRAN
ProvisioningServer
TheCallConferenceServerandMedia/SignalingGateway(MG/SG)donotuse
theOMCServer.
ToinstallandruntheOMCConsoleusethefollowingURL:
http://hostname:6688/omc/omc.html
wherehostnameisthewebserver'shostname.
RefertotheOMCUserInterfaceGuideforhowtousetheOMCConsole.
OMCFeatures ThisguidecoversthebasereleaseoftheOMCServerfortheIS41Release4.5.3,
GSMRelease4.5.4,andSRANMobilityServerRelease4.5.3.Releasenotesare
availablefortheOMCServerforpatchlevelsafterthebaserelease.
ThisreleaseoftheOMCServersupportsthefollowingfeatures:
Webbaseduserinterface(refertotheOMCUserInterfaceGuide)
AutomaticOMCclientsoftwareinstallation(refertotheOMCUserInterface
Guide)
Supportforupto10simultaneoususers
Configurationmanagementinterfaceforprovisioningnetworkelements
(refertotheOMCUserInterfaceGuide)
Comprehensiveelementandnetworkmanagementfeatures(referto
ManagementFeatures)
SNMPtrapforwardingdirectlyfromtheNEstoOSSs(refertoSNMPTrap
Forwarder)fortheGSMreleaseonly
MultipleSNMPagents(refertoMultipleSNMPAgents)
RemotesoftwarepackageinstallationtomanagedNetworkElements(NE)
(refertoRemotePackageInstallationonpage 39)
ACM2faultmanagementsupportfortheBaseStationsubsystem(referto
ACM2SupportfortheBSS)
Active/Standbyconfiguration(refertoActive/StandbyConfiguration)
ManagementFeatures TheOMCConsoleprovidesaccesstothefollowingmanagementfeatures:
NetworkManagementTheOMCmanagesalldevicesandnetworkresources
ontheSonatanetwork.OMCusersseeaunifiednetworkwideviewofall
systemobjects.

SystemArchitecture 21
LogicalgroupingofnetworkelementsNetworkElementscanbegrouped
andsubgroupedontheOMCdisplaytoprovideforeasiermanagement.
PerformanceManagementvisualinterfacesTheOMCcollectsanddisplays
statisticswitheasytouseintuitiveanddatasensitiveinterfaces.Thebasic
OMCperformancemanagementincludesstatisticgraphingandreportsthat
enableoperatorstooptimizenetworkresourceusageandqualityofservice.
TheOMCprovidesbasicperformancestatisticssuchassystemhealth,call
processingandmobilitymanagementstatusfortheMSCServer,HLR,
SignalingServer,andBaseStations.
RealtimealarmsandeventstheOMCFaultManagementInterfacedisplays
realtimealarmsandevents;itprovidesmethodsforacknowledgingand
manuallyclearingalarms,creatingaudiblealarms,andfilteringthedisplayof
alarms.
AccessControlandSecuritymanagementstrategyUserRoleandDomain
Managementprovidesaccesscontrolviaflexibleprivilegemanagement
functionsforusers.Itofferscustomizableauthorityspecificand
domainspecificmanagement.
SecuritymanagementincludespasswordcontrolledaccesstotheOMC
consoleandoperationsandsessionloggingwhichtracksalluseractionson
theOMC.UseractionsincludelogginginandoutoftheOMCconsole,
NetworkElement(NE)operations,andtablechanges.
OMCLogManagementTheOMCincludesOMCServersystemerrorsand
warnings,operationsloggingtotrackuseractivities,andsessionlogging.
SystemArchitecture TheOMCsystemconsistsof:
LayeredarchitectureTheOMCusesnetworkmanagementandNetwork
Element(NE)managementlayers.Thisarchitectureenablesallocationof
resourcesandmanagementtasksaccordingtothemanagementobjectivesof
eachlayer,andassistsdistributedmanagementandcustomsystems.
ScalablesystemconfigurationTheOMCadoptstheadvanced
Intranet/InternetBrowser/Servermode,centeredontheapplicationserver
andprovidessuperiorsystemscalability.
IntegratedopenstandardsUtilizingSNMPandCORBAprotocols,theOMC
usesastandardManager/Agentmodel.Thisfeaturestandardizesthe
collectionandconfigurationofsystemmanagementinformation,providesa
JavaRemoteMethodInvocation(RMI)basedopenmanagementinterface,
andsupportsintegrationwiththirdpartyapplicationsystems,contributingto
minimumaccesscostsandtheminimalcomplexityofthenetwork
managementcenter.
MultiplatformapplicationsTheobjectorientedprogramminglanguage,
Java,ensuresplatformindependence.TheOMCConsolerunsonvarious
software/hardwareplatformssuchasWindows2000,WindowsXP,andSolaris
workstations.
LDAP TheOMCusestheLightweightDirectoryAccessProtocol(LDAP)tostore
configurationdata.TheimplementationisOpenldap.OpenldapisboththeLDAP

serverandstoragecontainer.
NetworkElementFramework TheSonataOMCisaframework.ItcanbeusedtomanageanySonataproduct,
forexampletheIS41andGSMMSCsandHLRs.
AtthecoreoftheOMCoperationistheNetworkElementFramework(NEF)file.
TheNEFfileisaframeworkfilewhichcapturesallfault,performance,
configuration,accounting,security,policy,auditing,licensing,diagnostic,and
otherinformation(FCAPS+)relatingaparticularNEtypeontoXSDschemafiles.
AnXSDfileisaW3CcompliantXMLschemathatdefinesstructures,
relationships,andvalidationsforanXMLinstancedocument.
InformationcontainedintheNEFfileincludes:
Faultinformation:Alarms,events,andSNMPtrapsfromthenetwork
elementsrepresentedinXMLschemadefinitionformat.
Performanceinformation:Performancemetricsfromthenetworkelements
representedinXMLschemadefinitionformat.Themetricsarespecifictoeach
individualNE.
Accountinginformation:CDRinformationrelatingtonetworkelementusage.
Configurationinformation:AllNEconfigurableinformationdescribedasXML
schemaandthirdpartyconfigurationconvertedtoXMLschemaformat.
Securityinformation:Accessinformationrelatingtoaparticulartable,node,
object,orelementdefinedintheNEF.Basedontheaccessinformation,
accessrestrictionisachieved.
Licensinginformation:SoftwarelicensecontrolfortheNEisembeddedinthe
NEF.
Referentialintegrityinformation:Dependenciesandreferencesare
embeddedintheNEF.ThisallowsrelationshipstobedescribedintheNEFso
businesslogiccanenforcetheintegrityoftheNEF.
RefertoConfiguringtheOMCtoSupporttheNEsonpage 31formore
information.
DRUMontheNE DRUMistheproxybetweentheNEandtheOMC.DRUMrunsontheNEand
receivesconfiguration,control,andstatusqueriesfromtheOMCServerand
distributesthemtotheNE.Italsoreceivesconfiguration,control,andstatus
queryreplies,andalarmnotificationsfromNEs.
RCPontheNE DRUMusestheReliableCommunicationPath(RCP)ontheNE,whichis
implementedassharedmemory,tocommunicatewiththeNE.

AutomaticNEDiscovery 23
Multihoming TheOMCServerisintheuniquepositionwhereitneedstomanagetheNEsin
thebearernetworkandalsosupportexternalOSSsinthemanagementnetwork.
Thebearernetworkmustbeseparatedfromthemanagementnetwork,
thereforetheOMCServerismultihomedwithatleasttwophysicalinterfaces.
Theitemsthatinteractwithexternalentitiesaredividedintotwocategories:
Southbound(thosethatdealwiththebearernetwork)theseitemsinclude
alarmcollection,performancereportcollection,configurationandcontrol.
Northbound(thosethatdealwiththemanagementnetwork)theseitems
includeSNMPcollectorsandanyRCPs.
Active/StandbyConfiguration Theactive/standbyconfigurationallowstwoOMCserverstoworkintandem.If
onefails,theotheroneservesallclients.ThisincludesallFTP,OMCConsolesand
DRUMclients.
Therearetwoactive/standbyconfigurations.Inbothscenarios,commonIPsare
sharedbetweenthetandemservers:
1 ThefirstscenariohasbothserverssharingasinglecommonIP.Typically,thisis
thesouthboundinterface.
2 Inthesecondscenario,bothserverssharetwocommonIPs.OnecommonIPis
sharedforthenorthboundinterface;theothercommonIPissharedforthe
southboundinterface.TheserversmusthaveaphysicalinterfaceforeachIP
address.
AutomaticNEDiscovery WhentheOMCProxy(DRUM)startsontheNE,itdetectswhichproductsare
installedonthemachineandreportsittotheOMCserver.
TherearethreepossibilitiesforthereportedNEs:
First,thereportedNEisnewtotheOMC(NEdiscovery).Inthiscase,theOMC
requeststheproxytouploadallconfigurationsfromtheNEtotheOMC
server.
Second,thereportedNEexistsintheOMCserverandhasanunassociated
state(apreconfiguredNE).Inthiscase,theOMCwillrequesttheproxyto
downloadallconfigurationsfromtheOMCservertotheNE.
Third,thereportedNEexistsintheOMCserverandhasanassociatedstate.
Thismayhappeniftheproxyisrestarts.Inthiscase,theOMCwillignorethe
reporteventandsendoutstandingconfigurationrequeststotheNE
applications.

SNMP SNMPtrapsaresentfromNEappplicationstotheOMCfordisplayontheOMC
Console.
SNMPTrapForwarder AnSNMPforwarderagentcanexistonGSM(onlyinthisrelease)NEstoforward
trapsdirectlyfromtheNEtotheOSStoavoidtoomanymessages,inparticular
keepalivemessages,betweentheNEandtheOMCServer.
TheOMCServerstillconnectstotheSNMPForwarderagentforconfiguration
changesontheNE.
MultipleSNMPAgents TheOMCand/ortheSNMPForwardercansendalarmstomorethanoneNMS/
OSSviaSNMP.UsethepostinstalltooltosetupmultipleSNMPreceivers.
BSCandBTSState SNMPGETfunctionsontheOMCserverpullstateandotherinformation
Information periodicallyfromSNMPagentsrunningontheBSC,BTSandBTSsectors.The
resultsfromtheSNMPpullsareusedtoupdatetheNEinstancesontheGUI.
StateattributesaredisplayedgraphicallyontheOMCConsole.
PerformanceTables Theperformancedatabasetableshavebeenalteredtoenhancetheperformance
subsystem.Realtimedatahasbeenpartitionedintotablesbasedononehour.
Theyarelabeledstatisticnwherenis0to24.Thetablestatistic_tables
storesallinformationregardingthecontentofthestatisticntablesbasedon
time.
Thesummarizeddataispartitionedintotablesbasedononeday.Theyare
labeledsummarizedstatisticnwherenis0to30.Thetable
summarizedstatistic_tablesstoresinformationregardingthecontentofthe
summarizedstatisticntablesbasedontime.
TheOMCstores30daysofsummarizedperformancedata.
Performance(Subsystem) IfupgradingtheOMC,theOMCusestheexistingstatisticand
Upgrade summarizedstatistictablesuntilalldataisbeyondtheretentionperiods(24
hoursand30daysrespectively).
ArchiveManagement Theproductionofdaily,weeklyormonthlylogsofsystemoruseractionsis
integratedintotheOMC.Userswithrootprivilegescanconfiguretheproduction
ofarchivelogs.Logtimeistimesinceepoch,inseconds.
Limitations:
Logsproducedmaynotbetimestampedexactlyatmidnight.
Dailylogsareproducedfortheprevious24to48hoursandnottheprevious
24hours.
UpdatestoSummarizedPeformanceFiles
SARisalwaysthelastNetworkElementTypelisted.
TheorderoftheSARelementsisthesameasfortheothernetworkelements.
ACM2SupportfortheBSS 25
TheorderoftheperformancestatisticsisthesameasintheNEF.
ACM2SupportfortheBSS ACM2hasalarmsandalarmhierarchyspecificallyfortheBSSMIBs.
TheOMCsupportsalarmsfromtheACM2device.ACM2devicesareACMswitha
softwareversion1.2.0andhigher.ACMdeviceswithsoftwareversionof1.1.13
arepartiallysupported.Whilemostfieldsofthealarmsaretranslatedcorrectly,
thespecificproblemmaynotbetranslated.ChecktheAdditionalTextfieldfor
moreinformationregardinganalarm.
AutomatedBSSUpgrade AnautomatedBSSUpgradeutilityexistsfortheIS41productonly.
TheautomatedBSSUpgradeenablesupgradingBSCNEsandtheirassociatedBTS
NEs.Theupgradecanbeperformedeitheratascheduledtimeorimmediately,
andcanbedoneasawholeorinparts.Thedownloadingofthesoftwareonto
theBSCcanbeseparatedfromtheactualrestartofthenetworkelement.
Limitations:
ItispossibletoperformaDeleteSubtreeforaBSCthatisundergoingan
upgrade.Doingsocauseserrorsintheupgrade.
Itispossibletoaddmultipletaskstooneschedulewiththesametarget
(networkelementID).Doingsomaynotupgradethenetworkelement.

OMCCONFIGURATION ANDOPERATION
II
Chapter 2 OMCServerConfiguration
12
Chapter 3 OMCOperationsandTroubleshooting
UG
2A
1 _2
_ RC
A0
A0
_ RC
1 _2
2A
UG
12
OMCSERVERCONFIGURATION
2
ThischaptercoverstheconfigurationoftheOMCServeraftertheOMCServer
hasbeeninstalledbyStarSolutions.
SNMPEventForwarding
Active/StandbyConfiguration
DRUMPassword
OMCProxyConfiguration
ConfiguringtheOMCtoSupporttheNEs
HourlyPerformanceFiles
CallDetailRecords
SNMPEventForwarding SNMPEventForwardingcanbeenabledordisabledandeventscanbeforwarded
tomultipletargets.Thisiscontrolledbythepostinstallprocedure.ContactStar
SolutionstechnicalsupporttorerunthepostinstalltoenableordisableSNMP
EventForwardingandaddordeletetargets.
TheServerPluginDef.xmlfileshouldNOTbeeditedasinpreviousreleases.
Active/Standby Active/Standbycapabilitiesareenabledordisabledduringpostinstall.Contact
Configuration StarSolutionstechnicalsupporttoconfigureactive/standbycapabilities.
DRUMPassword Ifthedrumuseraccounthasadifferentpasswordthanthedefault(drum),
changetheconfigurationoftheSar_user_accountparameterinthe
~/CONF/trans.conffileintheomcaccount.TheOMCusesthepasswordinthis
filetologintoDRUMtogetSARperformancedata.

30 Chapter2:OMCServerConfiguration
OMCProxyConfiguration DRUMistheOMCproxyprocesswhichrunsontheSonataNEs.TheDRUM
configurationisfoundinthe/etc/drum.conffileontheSonataNEs.
ToconfigureDRUM:
1 LogintotheSonataNEasroot.
2 Createoreditthe/etc/drum.conffiletolistalltheproductsinstalledonthe
SonataNE.
Aproductislistedas:<NECLASS><path>{<VERSION>}
Blanklinesandlinesstartingwith'#'areignored.
Table3showstheaccounttoPRODUCTmappingusedtofigureoutthe
<NECLASS>and<VERSION>fortheDRUMconfigurationparameters.
Table3AccounttoProductMappingforDRUMconfiguration
Protocol Account Product

GSM pro CONX
IS41 pro CONX
GSM msc GSMMSC
IS41 msc IS41MSC
GSM fsv GSMHLR
IS41 fsv GSMHLR
<NECLASS>iscomposedofPRODUCTandVERSIONconcatenatedtogether.
<VERSION>iscomposedofthemajorversionandminorversionconcatenated
by"_".
Forexample,thedrum.conffilemightcontain:
#<NECLASS><path>{<VERSION>}
GSMMSC4_5/telos/msc4_5
CONX4_5/telos/pro4_5
GSMHLR4_5/telos/fsv4_5
3 Changethepermissionsonthedrum.conffilebyexecuting:
chmoda=r/etc/drum.conf
4 Logout.

ConfiguringtheOMCto InorderfortheOMCtounderstandeachnode,eachnodesNEFfilemustbe
SupporttheNEs mergedontotheOMC.TheOMConlyneedstobepopulatedonceforeach
particularnodetypeandversion.
Thisisdonebyrunningthe~/DATA/postinstall/postinstallscriptwiththe
supportofStarSolutionstechnicalsupport.
RetrievingtheNodespecific ThenodespecificNEFfilesareshippedwitheachNEandarelocatedinthe
NEFFiles $HOME/CONF/nef/<NEtype>directoryontheNE.Thefollowingpreparation
instructionsareusedtomergenodespecificNEFsontotheOMCserver.
1 LogintotheNEastheappropriateuser.
2 Changedirectoryto$HOME/CONF/nef/<product>
Forexample,ontheMSC,thiswillbe$HOME/CONF/nef/msc
3 FTPtheNEFfilefromtheNEtotheOMCServer.Thefilenameisintheformof
<NECLASS>.xsd.Examplesare:Conx5.1.0.xsd,IS41HLR4_5.xsd
MergingtheNEFFilesonthe FortheOMCtobeabletoadministerbothCONX(theSignalingServer
OMCServer application)andtheNEapplicationfortheNE,theCONXandNENEFfilesneedto
bemerged.RefertoMergingtheCONXandNENEFFiles.
ToMergetheNEFFilesontotheOMCServer:
1 LoginontotheOMCServerasomc.
2 StoptheOMCServer(refertoStoppingandStartingtheOMC).
3 ContactStarSolutionstoexecute~/DATA/postinstall/postinstalland
selecttheNEFfilesetsthattheOMCServerrequires.TheIP/portspecifiesthe
addressoftheexternalOSSreceivingtheSNMPtraps.Theversionspecifies
whichSNMPversiontheexternalOSSsupports.Thecommunityidentifiersare
usedbySNMPforsimpleauthenticationandauthorizationpurposes.For
example:
postinstall:start
===currentNEFsetting===
indexused<prod>/<nef>

1.msc/GSMMSC4_4.xsd
2.pro/CONX4_4.xsd
command

toattachansubNEF,enter'a<index>'
todeattachansubNEF,enter'd<index>'
toendtheNEFconfig,enter'e'
command[e]:a2

1.msc/GSMMSC4_4.xsd
2.Ypro/CONX4_4.xsd
command

command[e]:e
ldapproviderchooseiplanetoropenldap[openldap]:
AllowActive/Standbycapabilities(true|false)[false]:
DisablestandbyNEinteraction{true|false)[false]:

32 Chapter2:OMCServerConfiguration
DisablerolestandbyNEinteraction{true|false)[false]:
UseexternalLDAPauthentication(true|false)[true]:
TheexternalLDAPhost[unknown]:
TheexternalLDAPport[389]:
IsexternalLDAPportusingTLS/SSL(true|false)[false]:
Fullpathofkeystore/certificate(IgnoreifnotusingTLS/SSL)
[/export/home/telos/omc/CONF/keystore]:
Passwordtoaccesskeystore/certificate(IgnoreifnotusingTLS/SSL)
[unknown]:
TheexternalLDAPuserbaseDN[ou=People,dc=teloseng,dc=com]:
===currentSNMPsettings===

SNMP_FORWARDING.0=true
SNMP_MANAGER_IP.0=172.25.128.22
SNMP_MANAGER_PORT.0=162
SNMP_MANAGER_VERSION.0=2
SNMP_READ_COMMUNITY.0=public
SNMP_WRITE_COMMUNITY.0=public
command

toaddanewSNMPmanager,enter'a'
toremoveaSNMPmanager,enter'r<index>'
tochangeanexistingSNMPmanager,enter'c<index>'
toendtheSNMPmanagerconfig,enter'e'
pleasewait(thismaytakeafewminutes)...

postinstall:done
4 StarttheOMC(refertoStoppingandStartingtheOMC).
5 Logout.
MergingtheCONXandNE FortheOMCtobeabletoadministerbothCONX(theSignalingServer
NEFFiles application)andtheNEapplicationfortheNE,theCONXandNENEFfilesneedto
bemerged.
TomergetheCONXNEFfileandtheNENEFfile:
1 LogintotheOMCServerasomc.
2 FTPtheNEFfile(eg./telos/fsv/CONF/IS41HLR4_5.xsdfortheHLR)fromthe
NEtothe/telos/omc/CONF/nef/<NE>directoryontheOMC(eg.
/telos/omc/CONF/nef/fsvfortheHLR).
3 FTPthe/opt/telos/Conx5.1.0/share/ConxR5.1.0.xsdfilefromtheNEto
the/telos/omc/CONF/nef/prodirectoryontheOMC.
4 StartuptheOMCConsoleanddeletetheNE'ssubtreefromtheOMC:
a RightclicktheNEandselectDeletesubtree
5 StoptheOMC:
cpu_stop
6 Runthenef_mergetool:
nef_merge</full_path/name_of_application.xsd>
</full_path/name_of_CONX.xsd></full_path/name_of_merged.xsd>

Forexample:
nef_merge/telos/omc/CONF/nef/fsv/IS41HLR4_5.xsd
/telos/omc/CONF/nef/pro/ConxR5.1.0.xsd
/telos/omc/CONF/nef/fsv/IS41HLRCONX4_5.xsd
7 RunthepostinstallscriptusingthemergedNEFfile(s):
$HOME/DATA/postinstall
Thefollowingshowsthepromptsfromthepostinstallscript:
postinstall:start
===currentNEFsetting===

command

command[e]:e
TheIPaddressoftheSNMPManagertowhichOMCwillsend
TRAPnotificationsofnewalarmsandmanualclearevents
[unknown]:
ThePortNumbertowhichOMCwillsendTRAPnotifcationsfor
newOMCalarmsandmanualclearevents[162]:
TheSNMPversionthatoutgoingTRAPnotificationswillbe
sentoutin[1or2][2]:
TheSNMPreadcommunityidentity[public]:
TheSNMPwritecommunityidentity[public]:
pleasewait(thismaytakeafewminutes)...
8 StarttheOMC.
cpu_start
TheOMCresynchronizestheNEwhentheNE'sDRUMconnectstoit.
9 LogoutoftheOMCServer.
NonstandardNEAccount WhennonstandardNEaccountpasswordsareused,makesurethefollowing
Passwords stepsareexecuted:
1 LogintotheOMCServerasomc.
2 Editthe$HOME/CONF/trans.confconfigurationfiletochangeallthepassword
componentsofthePerf_user_account,Sar_user_account,and
Acc_user_accountkeywordssothattheappropriatecredentialswillbeusedto
transfertheperformance,SAR,andaccountingfilesfromvariousaccounts
respectively.Thechangewilltakeeffectthenexttimethecollectionscriptsare
invoked.
ConfiguringBSC/BTS ReachthroughfromtheOMCConsoleallowshttpaccesstotheNEs.http
ReachthroughforSRANOMC ReachthroughtotheNEsusesport80bydefault.However,theSRANOMC,
whichmanagestheSRANBSCandBTS,usesport8888forhttpaccess.
ThehttpReachthroughportconfigurationisinthe
$HOME/CONF/ApplicationDef.xmlfileintheomcaccountontheOMCServer.

TochangethehttpReachthroughport:
1 LogintotheSRANOMCServerasomc
2 Editthe$HOME/CONF/ApplicationDef.xmlfile:
vi$HOME/CONF/ApplicationDef.xml
3 Changethefollowing(bold)linesinthefiletochangethedefaulthttpportto
8888:
from:
<CommandDefname="ReachthroughtoiCellBTS"type="URL">
<Condition>
objectClassName=iCellBTS
</Condition>
<Command>
http://<hostname/>
</Command>
</CommandDef>
<CommandDefname="ReachthroughtoiCellBSC"type="URL">
<Condition>
objectClassName=iCellBSC
</Condition>
<Command>
http://<hostname/>
</Command>
</CommandDef>
to:
<CommandDefname="ReachthroughtoiCellBTS"type="URL">
<Condition>
objectClassName=iCellBTS
</Condition>
<Command>
http://<hostname/>:8888
</Command>
</CommandDef>
<CommandDefname="ReachthroughtoiCellBSC"type="URL">
<Condition>
objectClassName=iCellBSC
</Condition>
<Command>
http://<hostname/>:8888
</Command>
</CommandDef>
4 Saveandquitthefileeditor.
HourlyPerformanceFiles Hourlyperformancefilesareenabledbydefaultandareputintothe
~/DATA/SAR_PERF/storedirectoryundertheomcaccount.Thehourly
performancefilesusethestandardETSIXMLformatbydefault.
Thefilenameformatisamixtureofstandards(ETSITS132104v3.5.0)and
proprietaryrequirements:
B<start_timestamp><end_timestamp>_<unique_id><version>
Bindicatesthatthefilecontainsstatisticsformultiplenetworkelementsfor
onegranularity(onehour).
CallDetailRecords 35
Forexample:
B20090316.150020090316.1600_CoreNetwork1.0
B20090316.150020090316.1600_BSS1.0
Realtimeperformancesummarizationparametersareconfiguredinthe
$HOME/CONF/config.propfileintheomcaccount.
Someparametersofinterestinthisconfigurationfileare:
HistoricPerfProcessedLocationthischangesthestoragelocationforthe
hourlyperformancefiles.ChangingthisparameterrequiresanOMCServer
restart.
UseNonXMLFormatchangesthefileformattoASCIIifsettotrue
WhenthePerfSummarizationHalfHourparameterinthe
$HOME/CONF/config.propfileischanged,expectthesummarizedperformance
reportstobeincorrectormissingfortwosummarizedperiods.
PerformanceFilesonthe PerformancefilesontheSonataNEsaregeneratedintheDATAdirectoryinthe
SonataNEs drumaccount.
ThefilenameformatisthesameasontheOMCServer:
B<start_timestamp><end_timestamp>_<unique_id><version>
Forexample:
B20090316.150020090316.1600_CoreNetwork1.0
B20090316.150020090316.1600_BSS1.0
Theconfigurationfilewhichcontrolsthegenerationandnumberofperformance
filesisCONF/sar_gen.propwiththefollowingcontents:
sar_gen_in_xmlindicateswhethertheperformance(SAR)fileistobe
generatedinxmlformat(valuesaretrueorfalse)
xml_to_keepindicatesthenumberofxmlfilestokeep
BSSPerformanceReports TheOMCcangenerateperformancetrendsgraphsfortheBSCandBTS.
ThepredefinedOMCperformancereportsmustbeenabledasperformancejobs
oneachBSSNEbeforetheOMCcangenerateperformancegraphsandstatistics.
RefertotheiCellProvisioningGuideformoreinformationonwhichperformance
jobstoenablewhentheBSSNEswillbemanagedbyanOMC.
CallDetailRecords ACallDetailRecord(CDR)isasetofinformationthatrecordsthedetailsofacall.
Eachvoicecallthatusessystemresourcesproducesoneormorerecords
describingeventsthatoccurredduringthelifeofacall.TheSonataMSC
generatesCDRsinbinaryformat.

TheOMCperiodicallyretrievesCDRfilesfromtheMSC.TheOMCcanbe
configuredtoeitheruploadthefilesperiodicallytoabillingserverormakethe
filesavailablefordownloadbyabillingserver.
RefertotheConfiguingCallDetailRecordschapteroftheMSCOperationsand
MaintenanceGuideforcompletedetailsonconfiguringtheMSCandOMCfor
CDRgenerationandcollection.
OMCOPERATIONSANDTROUBLESHOOTING
3
ThischapterprovidesanoverviewoftheStarSolutionsSonataOperationsand
MaintenanceCenter(OMC)operationsandtroubleshooting.
OMCOperations
NEStateInformation
RealTimePerformanceData
RemotePackageInstallation
OMCTroubleshooting
OMCOperations ThissectioncovershowtostopandstarttheOMCandquerythestatusofthe
OMCprocesses.ThissectionalsocovershowtostopandstartDRUMandthe
ReliableCommunicationPaths(RCP)ontheNEs.
EithertheOMCProxy(DRUM)ortheSNMPForwarder,andtheRCPcomponents
arerequiredoneachmanagedNE.
StoppingandStartingthe TostarttheOMC:
OMC
1 Loginasomc.
2 Enter:
cpu_start
TostoptheOMC:
1 Loginasomc.
2 Enter:
cpu_stop
QueryingtheOMCStatus ToquerytheOMCstatus:
1 Loginasomc.
2 Enter:
cpu_status

38 Chapter3:OMCOperationsandTroubleshooting
StartingandStopping TostartDRUMorSNMPForwarderontheNE:
DRUM/SNMPForwarder
1 Loginasdrum.
2 Enter:
cpu_start
TostopDRUMorSNMPForwarderontheNE:
1 Loginasdrum.
2 Enter:
cpu_stop
QueryingDRUM/SNMP ToqueryDRUMorSNMPForwarderstatusontheNE:
ForwarderStatus
1 Loginasdrum.
2 Enter:
cpu_status
CreatingandDeletingRCPs TocreateRCPsontheNE(onlyunderStarSolutionstechnicalsupport
supervision):
1 Loginasdrum
2 Executeinitrcpcreate
TodeleteallRCPsontheNE:
1 Loginasdrum
2 Executeinitrcpdelete
NEStateInformation TheinitialstateofallSNMPmanagedNEs(exceptthosewithnoSNMPmapping
setupintheirNEF)shouldbeUNKNOWN.Afteraheartbeatinterval,the
correspondingNEs'actualvalueisretrievedbySNMPGETfunctionsandare
assignedtotheattributesoftheNEinstancesinOMC.IftheOMCcannotgeta
replytoanSNMPGET,afteraheartbeatintervalplusthetimespentonretries
andtimeouts,theNEsstatechangestoUNKNOWN.
TheinitialstatesofcorenetworkNEssuchastheMSCreflecttheactualstateof
theNEifDRUMisrunningontheNE.IfDRUMisdownontheNE,thestateofthe
NEissettoUNKNOWNontheOMC.
RealTimePerformance Realtimeperformancesummarizationparametersareconfiguredinthe
Data $HOME/CONF/config.propfile.
WhenthePerfSummarizationHalfHourparameterinthe
$HOME/CONF/config.propfileischanged,expectthesummarizedperformance
reportstobeincorrectormissingfortwosummarizedperiods.

RemotePackageInstallation 39
RealtimeperformancedatafromSNMPdevicesthataremorethananhourold
arenotprocessed.Anydataaheadoftimeisnotprocessed.Olderfilesare
automaticallymovedto$HOME/DATA/SAR_PERF/store.Newerfilesareleftin
the$HOME/DATA/SAR_PERF/readuntiltheyareprocessed.
Summarizationoccursonlyforthelastfullhourbeforethelastkickofftime.For
example:
Normalsummarization,kickofftimeis15minutesafterthehour:Itis02:15.
Summarizationoccursfor01:00to02:00.
Systemstartupat04:13:Summarizationoccursfor02:00to03:00.Thelast
kickofftimefor04:13was03:15.
Systemstartupat05:35.
OntheOMCConsolethetabularsummarizedperformancedatamaydisplaythe
timemarkedwitha*.Thisindicatesthatthedatafortheperiodaresummarized
overanhourthatisshiftedforwardby30minutes.Forexample,14H/Aug21*
meansthatthedataissummarizedfrom13:30to14:30localtime.
UnregisteredNEsareremovedautomatically.PreviousversionsoftheOMCdid
notremovethenetworkelementwhentheNEwasnolongersupplying
performancedata.NowtheOMCremovestheNEfromtheperformancedata.
RemotePackage Softwarepackages(suchaspatches)canbeinstalledremotelyfromtheOMC.A
Installation packageinstallationtaskcorrespondstoajobscheduledatadesiredtimeforthe
targetedNEs.Multipletaskscanbearrangedtoexecuteinserialorparallel
mode.
RemotepackageinstallationcanbeperformedfromtheOMCConsoleorfrom
thecommandline.
Thereare5packageinstallationrelatedjobscripts:
download_epdownloadsanyrequestedpackageanditsdependent
packagesontotargetedNEs.
requires<hostname>and<netype>parametersfromthecommandline
Thecommandlinefoptiondownloadsonlytherequestedpackage
install_epinstallsthedownloadedpackagewhilekeepingtheapplication
stateintactonthetargetedNEs.Afterexecutioninstall_epwillreturna
newCPUversioninformationifsuccessfuloranerrormessageifnot
successful.
foptioninstallsonlytherequestedpackage.
roptionremovestherequestedpackage.

<mode>installstherequestedpackageonlywhentheapplicationsare
underthespecifiedmode.
download_install_epdownloadsandinstallstherequestedpackagein
onestep.download_install_epreturnsanewCPUversioninformationif
successfuloranerrormessageifnotsuccessful.
<mode>installstherequestedpackageonlywhentheapplicationsare
underthespecifiedmode.
commandlinefoptioninstallsonlytherequestedpackage.
commandlineroptionremovestherequestedpackage.
get_cpu_versionandget_cpu_statusprovideassistanceinobtaining
systemversionandstatusinformation.Theoperatorcanapplythescriptsto
anytargetsandentertheapplicationasthescriptparameter.Thescripts
returnqueriedinformationviaadialogwindowactivatedthroughabuttonin
thetaskpanel.
requires<hostname>and<netype>parametersfromthecommandline.
OMCTroubleshooting
OMCServerTroubleshooting TheOMCserverdoesnothaveaprocessmanagementfunction.Therefore,to
checkwhethertheOMCserverisrunningproperly,checktheOMCstatus(refer
toQueryingtheOMCStatus).
Also,checkindividualcomponentsbyexecutingthefollowingcommand:
psef|grepomc
Atleastthefollowingprocessesshouldberunning:
java
httpd(manyinstances)
rmiregistry
slapd
safe_mysqld
tnameserv
Tofixanyproblems,restarttheOMCserver(refertoStoppingandStartingthe
OMC).
Checkifthereareanyerrorsinthe/telos/omc/RUN/log.omcserver.errfile.
ThefileshouldendwithAllpluginshavebeeninitializedand
started
Checkifthereareanyerrorsinthe/telos/omc/RUN/log.tnameserv.errfile.
ThisfileshouldbeemptyiftheOMCisrunningcorrectly.

ContactStarSolutionstechnicalsupportifthereareanyerrorsinthefiles.
CheckOMCServerConnections
CheckwhethertheOMCserverislisteningforconnectionsfromtheOMCproxy:
1 LogintotheOMCServerasomc
1 Switchusertoroot
2 Execute:
lsofn|grep24243
3 Iftheoutputofthiscommandisnull,contactStarSolutionstechnicalsupport.
CheckwhethertheOMCGUIcanconnecttotheOMCserver:
1 Fromtheomcuseraccount,execute:
cfgclientu<user>p<password>getobject<dn>object
where<dn>istheNEobjectdistinguishednamee.g.CONX4_4:NEID=platinum
2 IftheNEismanagedbytheOMCthenthiscommandwilldisplaytheobject.
3 IftheOMCServerisnotrunning,theOMCConsolewillreconnecttotheOMC
Serverautomaticallywhenitcomesbackupandresynchronizedata
automatically.
OMCConsoleCPU,Memory, CPU,Memory,DiskIO,NetworkIOarecalledSARdata.Thisdataisgeneratedby
DiskI/O,NetworkI/O DRUMoneachNE.TheOMCserverperiodicallyftpsthisdatafromDRUMtothe
OMC.
IfthisdataisnotbeingftpdtotheOMCServer,itmaybeduetoanincorrect
configurationontheOMCServer.ChecktheSar_user_accountparameterin
thetrans.conffileinthe/telos/omc/CONFdirectoryontheOMCServer.
MakesuretheDRUMpasswordiscorrect.Ifnot,correcterrorsandwaitforat
leastfiveminutes.ChecktheOMCConsoleagain.
Iftheaboveisnotthecauseoftheproblem,followthestepsbelowtodiagnose
theproblem:
1 LoginasdrumtotheNE.Runcrontabl.Makesurethatsa3isinvokedevery5
minutes.Ifnot,DRUMhasnotbeeninstalledproperly.ContactStarSolutions
technicalsupport.
2 SARdataaretemporarilystoredin/var/adm/saontheNE.Checkwhetherthere
arefilesinthisdirectory.Ifnot,checkwhetherthediskisfull.Ifthediskisfine,
checktheerrorsin/telos/drum/RUN/sa3.log.Ifthereareerrors,contactStar
Solutionstechnicalsupport.
3 OntheOMCServer,checkwhetherthereissardatainthe
/telos/omc/DATA/readdirectory.Thereshouldbeonlyonefileinthisdirectory.
Iftherearemanyfiles,theOMCserverisnotfunctioningproperly.Restartthe
OMCServer.

PostinstallTroubleshooting Thepostinstallprocessproducesalogfile:/tmp/postinstall.logIferrorsare
foundinthisfile,contactStarSolutionstechnicalsupport.Warningsinthisfile
arenormal.
Duringthepostinstallprocess,errorsmayappearwhentheNEFsarechecked.
ThishappensforolderNEFsforMSC,CONX,HLR,MRF,andLIS.Tocorrectthis,
replaceallinstancesofthefollowing,withsupportfromStarSolutionstechnical
support:
com.telostech.omcP.commonP.verifyP.VerifyPcC
with:
com.utstar.mm2k.omcP.commonP.verifyP.VerifyPcC
DRUMandSNMPForwarder TocheckDRUMorSNMPForwarderstatusrefertoQueryingDRUM/SNMP
Troubleshooting ForwarderStatus.RestartDRUMorSNMPForwarderifitdoesnotshowall
processesrunning(refertoStartingandStoppingDRUM/SNMPForwarder).
LogsforDRUMandtheSNMPForwarderagentarestoredin
/telos/drum/RUN/System.logThisfileisrotatedandrenamedeachdayto
System.log.<YYYYMMDD>
Checktheappropriatereleasenotesformoreinformation.Checkifthereareany
errorsinthe/telos/drum/RUN/log.System.logfile.Ifthereareerrors,
contactStarSolutionstechnicalsupport.
CheckingtheDRUMorSNMPForwarderOMCServerConnection
CheckwhetherDRUMortheSNMPForwarderagenthasconnectedtotheOMC
Server'sport24243byexecuting:
lsofn|grepdrum|grep24243
Ifthereisnoconnection,checkwhethertheOMCserverisrunningandlistening
onport24243(refertoOMCServerTroubleshooting).IftheOMCServeris
listeningonport24243andDRUM/SNMPForwarderdidnotconnecttothe
OMCServer,theproxymanager_hostparameterinthe$HOME/CONF/drum.prop
filemaybewrong.ContactStarSolutionstechnicalsupport.

RCPTroubleshooting TheReliableCommunicationPath(RCP)isimplementedassharedmemory.
Whensharedmemoryiscreated,thereshouldbeacorrespondingfilein
/tmp/.SHMD
TocheckwhetherRCPisworkingproperly,usethefollowingsteps(themsc
accountisusedasanexample):
1 LogintotheMSCasmsc
2 Checkwhetherthefollowingthreefilesexistin/telos/msc/RUN:
config.proxy2app.rcp
config.app2proxy.rcp
fault.app2proxy.rcp
3 Checkwhetherthecorrespondingmapfilesexistin/tmp/.SHMD
4 Switchtothedrumuser.Checkwhethermessagesarebeingpassedbetween
DRUMandtheNEusingRCPbyexecutingthercp_peekertoolwhichscans
messagesoverRCPwithoutdisturbingRCPusers.Youmayhavetowaitafew
minutesbeforemessagesareseen:
~/TOOL/rcp_peeker<filename>
where<filename>isoneofthefilesfromstep2
Ifthetoolexitswithanerrormessage,RCPisnotworkingcorrectly
UseCtrlctoquitthetool
Forexample:
rcp_peeker/telos/msc/RUN/config.proxy2app.rcp
rcp_peeker/telos/msc/RUN/fault.app2proxy.rcp
5 CheckifDRUMandtheNEareusingthesameRCPsbyexecutingthelsof
command:
lsof<mapfilename>
Forexample:
lsof/tmp/.SHMD/telos_msc_RUN_config.proxy2app.rcp
Ifnot,restarttheprocess(DRUMortheNE)thatisnotusingtheRCP(referto
StartingandStoppingDRUM/SNMPForwarder).
6 Ifsteps2,3or4reporterrors,RCPhasnotbeencreatedproperly.Torecreate
theRCPs,contactStarSolutionstechnicalsupportforhelpwithrecreatingthe
RCPsusingthefollowingprocedure:
a LogintotheNEasdrum.
b RuninitrcpdeletetodeleteallRCPsontheNE.
c RuninitrcpcreatetocreateallRCPsontheNE.
d RestarttheNEbyexecuting:
hwd_clik
e RestartDRUM(refertoStartingandStoppingDRUM/SNMPForwarder).

OMCBSSTroubleshooting ThereareafewareastocheckiftheOMCdoesnotappeartobereportingBSS
informationcorrectly.
IncorrectTrapOID
TheOMCsupportsmultipleversionsofthesameNEtype(forexample,BSC4_7
andBSC4_5).However,theOIDforeachtrapmustuniquelyidentifytheNEtype.
Ifitdoesnot,theOMCwillnotbeabletoidentifytheNEtypeforNEsnotalready
addedtothesystemviatheOMCConsole.TheOMCdropsthesetraps.This
affectstheiCellBSCsandBTSsversion4_5and4_7,whichusethesametrapOID
forperformanceandfaulttraps.IftheNEhasnotbeenregistered,theOMC
ServerattemptstoidentifythetypebasedontrapOID.IfthetrapOIDdoesnot
uniquelyidentifyanNEType,thetrapisrejected.
NoBSSFaultsorPerformanceReportsontheOMC
IfBSSperformancereportsarenotbeinggenerated:
1 CheckthetimeontheBSCandBTStoensurethattheyaresettothecurrentdate
andtime.Alsocheckthesystem.logfileitwillindicateiftimestampsarefrom
1980insteadofthecurrentdateandtime.
2 CheckthatSNMPtrapsarebeingsenttotheOMCbyrunningsnoopontheOMC:
a LogintotheOMCasroot.
b Execute:
snoopo<snoopfilename>host<ipofBSSdevice>port2162
c Ifsnoopdoesnotreceiveanytrapsovera5minuteinterval,theBSShasnot
beenconfiguredtosendtrapstotheOMC.
AutomatedBSSUpgrade FortheAutomatedBSSUpgrade,ensurethattheOMCandBSCsareconfigured
tocommunicatewithoneanother.RefertotheiCellCDMA20001Xv4.7Upgrade
documentforinstructions.
Runssh_setupforeachBSCtheOMCmanages.ThisensuresthattheBSS
upgradescancomplete.
UnpackpackagesfortheBSSUpgradetothe~/software_upgradedirectory.If
thedirectorydoesnotexist,createit.

APPENDIXES
III
Appendix A Acronyms
12
UG
2A
1 _2
_ RC
A0
ACRONYMS
A
Thisappendixdefinesacronymsusedinthisguide.
Table 4ListofAcronyms
Acronym Definition
ACM AlarmControlModule
ASCII AmericanStandardCodeforInformationInterchange
BSC BaseStationController
BSS BaseStationSystem
BTS BaseTransceiverStation
CALA CentralAmerica,LatinAmerica
CDR CallDetailRecord
CORBA CommonObjectRequestBrokerArchitecture
CPU CentralProcessingUnit
DN DirectoryNumber
EMEA Europe,MiddleEast,andAfrica
ESD ElectrostaticDischarge
ETSI EuropeanTelecommunicationsStandardsInstitute
FCAPS Fault,Configuration,Accounting,Performance,andSecurity
Management
FTP FileTransferProtocol
GSM GlobalSystemforMobileCommunications
GUI GraphicalUserInterface
HLR HomeLocationRegister
IO InputOutput
IP InternetProtocol
LDAP LightweightDirectoryAccessProtocol
MG MediaGateway
MGW MediaGateway
MRF MediaResourceFunction
MSC MobileSwitchingCenter
NE NetworkElement
NEF NetworkElementFramework
OMC OperationandMaintenanceCenter
OSS OperationSupportSystem
RCP RemoteCopyProgram

ServerGuide
48 AppendixA:Acronyms
Table 4ListofAcronyms
Acronym Definition
SAR SystemActivityReport
SE SwitchingElements
SG SignalingGateway
SGW SignalingGateway
SNMP SimpleNetworkManagementProtocol
SS7 SignalingSystemNumberSeven
SSVR SignalingServer
TLS TransparentLANService
URL UniformResourceLocator
UTC UniversalCoordinatedTime
XML ExtensibleMarkupLanguage

ServerGuide
INDEX
12
A
alarms 21
UG
C
comprehensivemanagementfunctions 20
contacting
technicaldocumentationdepartment 15
conventions,text 10
customerservice
contacting 14
2A
I
icons 10
_2
N
notices 10
1
P
RC
performancemanagement 21
ProvisioningServer 20
S
securitymanagement 21
_
SRAN 20
A0
T
technicalsupport
hours 14
services 14
website 14
W
warrantysupport 15
STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|

SRANR4.5.3OperationsandMaintenanceCenterServerGuide
A0
_ RC
1 _2
2A
UG
12
A0
_ RC
1 _2
2A
UG
12
12
UG
2A
1 _2
_ RC
A0
Copyright2012 StarSolutionsInternationalInc.
1204600JacombsRoad
Richmond,BritishColumbia V6V3B1 Canada
www.starsolutions.com

D02654GS A0 RC1 OMC Server Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

D02654GS A0 RC1 OMC Server Guide

Enviado por

Direitos autorais:

Formatos disponíveis

AllIPCDMA2000|GSM

PARTII OMCCONFIGURATION ANDOPERATION

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|SRAN

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|SRAN

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|SRAN

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|SRAN

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

Notices Table 1listsnoticeiconsusedinthisguide.

Icon NoticeType Description

Text Table 2liststextconventionsinthisguide.

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

RelatedDocumentation Figure 1mapstherelationsamongthedocumentsintheStarSolutionsSonata

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

Protocol Account Product

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3OperationsandMaintenanceCenter

STA R SO LU TIONS CO N FI DE N TI A L SonataCoreVoiceNetworkIS41R4.5.3|GSMR4.5.4|SRANR4.5.3GSMR4.5.4|IS41R4.5.3|

Você também pode gostar