Running and testing the probe

Run the probe and ensure it is communicating with the NMS or EMS correctly.

To run and test the probe:

  1. Start the probe from the command line, specifying the minimum message level of debug and that an initial resynchronization is to occur. For example:

    $OMNIHOME/probes/nco_p_generic_3gpp -messagelog stdout -messagelevel debug -initialresync true

  2. Ensure that the probe connects to the target system successfully. Look for the following message in the probe's log file:
    Information: I-JPR-000-000: Probe connected
    If the probe fails to connect:
    • Check and adjust the properties related to setting up a connection. See Device connections through the CORBA interface for information on the connection properties and how to set them.
    • Ensure that any firewall between the probe host and the NMS or EMS is configured to allow traffic to pass from one end to the other in both directions.
  3. Check that the probe successfully synchronizes with the NMS or EMS. Look for messages similar to the following in the probe's log file:
    Information: I-UNK-000-000: Probewatch: START SYNCHRONIZATION
    Debug: D-JPR-000-000: Filter value is : sadsadsa
    Debug: D-JPR-000-000: Calling get_alarm_list()
    Debug: D-JPR-000-000: Statistic of alarms received in one batch
    Debug: D-JPR-000-000: ResyncAlarmData [isAllAlarm=true, criticalCount=0,
     majorCount=0, minorCount=0, warningCount=0, indeterminateCount=0,
    Debug: D-JPR-000-000: Parsing alarm
    Information: I-UNK-000-000: Probewatch: END SYNCHRONIZATION

    Troubleshoot any synchronization errors, including the values of the synchronization properties. See Properties and command line options provided by the Java Probe Integration Library (probe-sdk-java) version 4.0 for information on synchronization.

  4. Check that the probe correctly parses alarms with the Event Processor. Check for any unsupported types for event parsing. For example:
    Debug: D-UNK-000-000: [Event Processor] Reason:	SOME REASON
    Debug: D-UNK-000-000: [Event Processor] EventName:	x2
    Debug: D-UNK-000-000: [Event Processor] NotificationID:	997169651
    Debug: D-UNK-000-000: [Event Processor] AckState:	1
    Debug: D-UNK-000-000: [Event Processor] AlarmId:	676512950
    Debug: D-UNK-000-000: [Event Processor] SpecificProblem:
                                     supervision inhibited by operator
    Debug: D-UNK-000-000: [Event Processor] BackupUpStatus:	false
    Debug: D-UNK-000-000: [Event Processor] AdditionalText_LineCount:	1
    Debug: D-UNK-000-000: [Event Processor] AckSystemId:	ack_system_id
    Debug: D-UNK-000-000: [Event Processor] TrendIndication:	MoreSevere
    Debug: D-UNK-000-000: [Event Processor] FullDN:	(NW, UTRAN) 
                               (BTSEquipment.userLabel, BTSM2_413_005)
    Debug: D-UNK-000-000: 
             [Event Processor] ManagedObjectClass:	managed_object_class
  5. Check the log file for errors that occur from parsing unsupported types of event. For example:
    Cannot parse event attribute 'X.733:CorrelatedNotifications' with type [19] 
    and content description: Sequence

    Check also for attributes having a null value or one that shows as 'UNKNOWN'.

  6. Check that events appear in the Event List and that they contain the expected elements and values.

    Modify the rules file if the values in the Event List do not meet your requirements.