RBS-RNC IP Transmission CheckPurpose In order to see transmission status between RNC-RBS, I prepared these guidelines. None of these parameters are configurable, they only tells the current status. Procedure In node B: 1. Look the operationalState of IpAccessHostEt and IpSyncRef: should be "ENABLED" 2. syncStatus: should be in "OK". Possible values: NOT_REACHABLE 0 No reply from the NTP server. 1 NOT_RELIABLE Unreliable clock information received from the NTP server. 2 OK 3. syncRefStatus: should be in "OK". Possible values: FAILED 0 Synchronization reference cannot perform its required tasks. 1 DEGRADED Capability of the synchronization reference to perform its required tasks is degraded, for example, because of high bit error rate. This value is applicable only for synchronization references that carry traffic, that is, for ET physical path terminations. 2 LOSS_OF_TRACKING The algorithm for system clock regulation cannot follow the synchronization reference signal either because of the poor quality of the signal or because of a HW fault. 3 OK Synchronization reference is capable of performing its required tasks. 4 REF_PATH_FAILED_A Synchronization reference cannot be distributed on plane A. 5 REF_PATH_FAILED_B Synchronization reference cannot be distributed on plane B. 6 NOT_RELIABLE No NTP packets are received from the server. This value is only used for IP synchronization references. 7 LOW_QUALITY The time stamp packets received from the NTP server are not reliable and the synchronization algorithm cannot lock to IP reference. This value is only used for IP synchronization references. 4. nodeSystemClock: should be in "LOCKED_MODE". Possible values: UNKNOWN_MODE 0 1 STARTUP_MODE The system clock is starting up. 2 LOCKED_MODE The system clock signal on the Timing Unit is locked: a synchronization reference is used to generate the system clock, the clock accuracy is 50 ppb or better. 3 HOLD_OVER_MODE The system clock signal on the Timing Unit has holdover quality: no synchronization reference is used to generate the system clock, the clock accuracy is 50 ppb or better. 4 FREE_RUNNING_MODE The system clock signal on the Timing Unit is free-running: no synchronization reference is used to generate the system clock, the clock accuracy is 4.6 ppm or better. 5 FAILED_MODE The system clock signal on the Timing Unit is failed: there is fault in generating the system clock, no guarantee of clock accuracy level. 6 LOSS_OF_TRACKING_MODE The frequency of the system clock is at its upper or lower limit. 7 NOT_APPLICABLE The system clock signal on Timing Unit is not applicable: the TUB or the CBU is not present. 5. Action: ping On IpAccessHostEt MO, use the action "ping" to check the availability of IpSyncRef IP addresses. Calls a host or router to find out if it is present in the network. The following parameter is returned: Ping result: The IP address - is alive or no answer. 6. Node Logs: Alarm & Event Logs: Alarm list and events will always tell any disruption in a certain time. In RNC: 7. staticDelay: below Latest calculated one way static delay. Special values: 40960000 indicates no value available Unit: microsecond Resolution: 125 8. For a deep analysis, below counters can be activated and checked periodically. RBS Synchronization: pmHDelayVarBest10Pct pmHDelayVarBest1Pct pmHDelayVarBest50Pct pmMaxDelayVariation RNC NodeSynch: pmIubLinkDynamicDelayMax pmIubLinkStaticDelay The following delay values are suggested for IP-based transport network solutions: Delay for real-time traffic on Iub Propagation delay, target: 5 ms Propagation delay, maximum: 30 ms Delay variation, maximum: 10 ms Packet Loss, recommended maximum: 10e-6, maximum: 10e-3. Exceeding the recommended packet loss rate will results in a somewhat impaired service. Delay for best effort traffic on HSPA on Iub Propagation delay, target: 10 ms Propagation delay, maximum: 100 ms Delay variation, maximum: - Packet Loss, recommended maximum: 10e-6, maximum: 10e-3. Exceeding the recommended packet loss rate will results in a somewhat impaired service. Delay for best effort traffic on DCH Propagation delay, target: 10 ms Propagation delay, maximum: 50 ms Delay variation, maximum: 12 ms Packet Loss, recommended maximum: 10e-6, maximum: 10e-3. Exceeding the recommended packet loss rate will results in a somewhat impaired service.