Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Support for Display of Jitter and Latency in the CTP Bundle Query Output on MIB Browser

    Until CTPOS Release 7.1, the CTP bundle query does not provide statistics for jitter and latency. Starting with CTPOS and CTPView Release 7.2R1, jitter and latency values are displayed in the command used to query the CTP bundles. Latency is computed as follows:

    Latency = RoundTripDelay / 2

    where:

    RoundTripDelay is the sum of the amount of time taken for a signal to be sent and the amount of time taken for an acknowledgment of that signal to be received.

    Jitter is calculated as follows:

    Jitter = (double) Span/ CTP_OSC_FREQ

    where:

    CTP_OSC_FREQ = 0x8000 or 32MHz

    Span = Largest Buffer – Smallest Buffer

    Two additional values are appended at the end of the following command to support bundle jitter and bundle latency.

    [root@ctp_87 ctp_cmd 3]# cmd bndl 0 qry snmp v1;B;0;1;this is ctp bundle description of maximum length on te-0.0 port.;te-0/0;1;-1;10.216.118.88;0;0;0;10.0.0.1;1024;16.000;12.000;8.000;0;255;0x40;-1;- 1;3;20206060;20208183;0;24;88;86;0;1;10189;10089;6045;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;4.145;150;

    Similarly, MIB objects for bundleJitter and bundleLatency are added in ACORN-MIB used by the MIB Browser.

    Jitter and latency fields are added for the CTP, SAToP, CESoPSN, and VComp bundles. However, for VComp bundles, this value is always –1, and for SAToP and CESoPSN bundles, the latency field is always –1.

    Enhanced snmpAcorn.pl to Support the Daemon Model

    Until CTPOS Release 7.1, all SNMP requests for the Acorn MIB are rendered to the snmpAcorn.pl script, which computes the results and returns them to the requestor. It is observed that snmpAcorn.pl is causing high CPU usage for the complete SNMP walk of Acorn MIB. Starting with CTPOS and CTPView Release 7.2R1, the snmpAcorn.pl script is run in daemon mode. All the SNMP requests arrive first at the snmpAcorn client, which in turn sends an interprocess communication message (IPC) to the daemon. The daemon processes the request and sends it back to the snmpAcorn client. To enable this functionality of the daemon processing the SNMP requests, the snmpAcorn.pl has been enhanced to support the daemon model.

    Modified: 2016-01-29