1、Page 1,Q3 training,1. B7/B8/B9 Q3IM Configuration 2. NMC Configuration 3. Efd & Log 4. Alarm Clearing 5. Alarm Synchronization Action 6. Alarm format 7. Trace Analyzing,Page 2,B7 Q3IM Configuration,=Current OMC side configuration =OMC ADDRESS : PSEL = OVDMSSEL = ses0TSEL = tp0NSAP = 0xac180c48OMC SY
2、STEM IDENTIFIER = “sbardx48“ OMC NETWORK IDENTIFIER = 48 Q3 AGENT AETITLE = NONE ASN TIMER INTERVAL = seconds,Page 3,B8 Q3IM Configuration,=Current OMC side configuration =OMC ADDRESS : PSEL = q3SSEL = PrsTSEL = CMIPNSAP = 0xac180c48OMC SYSTEM IDENTIFIER = “sbardx48“ OMC NETWORK IDENTIFIER = 48 Q3 A
3、GENT AETITLE = NONE ASN TIMER INTERVAL = seconds,Page 4,B9 Q3IM Configuration,我方OMC3需要NMC的相关参数IPaddress- NMC的ip地址 APTITLE- 1.3.9999.1 ip AEQUALIFIER- netPSAP- SSAP- TSAP- NetworkID-(用来标示我方的OMCR是该NMC下第几个设备)我方OMC3提供给NMC的相关参数：林武坑13802430040 ,Page 5,B9 Q3IM Configuration,开启Q3时，通常使用method(3BK 17422 4041
4、RJZZA)中的PI01/03/06。当执行declareNmc.pl时，请统 一使用”-form2” 和”-rfc1006”参数。NMCAeTitle = APTITLE+AEQUALIFIER例如：Current OMC side configuration OMC ADDRESS : PSEL = q3SSEL = PrsTSEL = CMIPNSAP = 0xac18fc0bOMC SYSTEM IDENTIFIER = “omc3h01“ OMC NETWORK IDENTIFIER = 11 Q3 AGENT AETITLE = NONE ASN TIMER INTERVAL =
5、seconds,Page 6,NMC Configuration,=Current NMC configuration =AE TITLE NMC TYPE FORM TYPE LINK TYPE PSEL SSEL TSEL NSAP-1) 1.2.3.4.5.1 Primary form2 RFC1006 pres ses 172.24.12.40,Page 7,Efd & Log,Q3IM has 1 default efd and 3 default Logs. The default efd only filters 4 alarms, they are cTelHeartbeatR
6、eport cTelRequestCMSynchronization cTelTransferUpReady processingErrorAlarm The default Log1 saves alarms for FM, they are communicationAlarm, communicationAlarm, qualityofServiceAlarm, equipmentAlarm, environmentalAlarm The default Log2 saves alarms for CM, they are stateChange, attributeValueChang
7、e, cTelObjectCreation, cTelObjectDeletion, cTelRequestCMSynchronization The default Log3 saves alarms for COM, they are cTelTransferUpReady,Page 8,Efd & Log (Cont),/alcatel/omc3/q3im/conf/efdLogInEPIM xnumber 1 0 xnumber 1 1 xnumber 2 1 xnumber 3 1 /alcatel/omc3/q3im/conf/fwkmo.autostart /alcatel/ba
8、se/q3im/db/efd_1.mo /alcatel/base/q3im/db/log_1/log_1.mo /alcatel/base/q3im/db/log_2/log_2.mo /alcatel/base/q3im/db/log_3/log_3.mo /alcatel/base/q3im/db/log_q3imc_sbardx48/log_q3imc_sbardx48.mo /alcatel/base/q3im/db efd_1.mo log_2 log_q3imc_sbardx48 log_1 log_3,Page 9,Efd & Log (Cont),According to s
9、pecification, when Q3im start up on OMCR, only default elog and EFD was created, then only default alarms were sent to NMC; When OMCR association to NMC was established, NMC should create EFD to OMCR to get all alarms and/or some special alarms.,Page 10,Efd & Log (Cont),Problem list and check point:
10、 NMC can not receive and alarms from OMCR Check point: OMCR connection to NMC is OK, check ftp/telnet on bi-direction NMC only get some alarms from OMCR; Check point: Check /alcatel/omc3/q3im/conf/efdLogInEPIM, if only default EFD exists, ask NMC to check /create EFD on OMCR; NMC get alarms from OMC
11、R with abnormal status, such as time flag was abnormal. Check point: Check those alarms was normal on OMCR or not.,Page 11,Efd & Log (Cont),Solution for reset default efd & logs 1. stop Q3IM process2. delete /alcatel/omc3/q3im/conf/efdLogInEPIM and /alcatel/omc3/q3im/conf/fwkmo.autostart.3. empty di
12、rectory /alcatel/base/q3im/db/.4. restart Q3IM process,Page 12,Alarm Clearing,According to ITU X.733 8.1.2.3 Perceived severity. cleared: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the sa
13、me Alarm type, Probable cause and Specific problems (if given). Multiple associated notifications may be cleared by using the Correlated notifications parameter (defined below).In B9 CDE, The cleared alarm has the same notificationIdentifier with one or more corresponding BEGIN alarm.,Page 13,Alarm
14、synchronization Action,Current active alarms synchronization after link restore in network level Initial state NMC and 1353-RA communication link restored after broken Operating Mode Send an M-ACTION request from NMC: BOC = cTelPlmnSubnetwork BOI = ACTION Type = cTelRetrieveCurrentAlarmsData ACTION
15、Info =BaseManagedObjectIdBOC = cTelPlmnSubnetworkBOI = Final state NMC successfully retrieve current active alarms from 1353-RA in network level,Page 14,Alarm synchronization Action (Cont),Current active alarms synchronization after link restore in managedElement level Initial state NMC and 1353-RA
16、communication link restored after broken Operating Mode Send an M-ACTION request from NMC: BOC = cTelPlmnSubnetwork BOI = ACTION Type = cTelRetrieveCurrentAlarmsData ACTION Info =BaseManagedObjectIdBOC = managedElement BOI = Final state NMC successfully retrieve current active alarms from 1353-RA in
17、 managedElement level,Page 15,Trace Analyzing,1. Change trace level to 1+ 2. Check q3im.chld.trace, whether reporting cTelHeartbeat alarm every minute. 3. Check q3im.chld.trace, whether reporting communicationAlarm, qualityofServiceAlarm, equipmentAlarm, environmentAlarm etc. 4. If the above steps normal, that is to say that Q3IM works well.,
