Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Resolved Issues in CTPOS Release 7.2R1

The following issues have been resolved in CTPOS Release 7.2R1.

  • SNMPv2 traps that are sent from a CTP device do not contain specific bundle descriptor information. In the traps summary, the Bundle Descriptor and Port Descriptor attributes are not sent to the NMS server. [PR/1054258]
  • Data through SAToP bundles is not transmitted from a CTP system to the MICs on MX Series routers because the CTP device does not check the bundle type and sets the "isXorPkt" variable for SATOP bundles. [PR/1060422]
  • Special characters, such as equal sign (=), semicolon (;), and spaces, are not supported in SNMP location strings and are not processed properly. [PR/1060696]
  • A CTP bundle that is set as the data terminal equipment (DTE) with a packet size of 8 bytes does not run and generates a TooFast error (encountered when the bundle is configured for all clocking to be done by the external TT clock). This problem occurs when the port configuration flag is set as HiTTCheck for the CTP bundle, and the packets per second (pps) is shown as 1500 for the bundle in such a scenario. [PR/1074998]
  • After the reboot of a CTP device, the serial card in slot 2 is not visible in the software because the CTPOS software identifies the card and reports IRQ 0 is busy in the log file. In such a scenario, you need to reboot the CTP device again for the card to be operational. [PR/1079714]
  • On a CTP150 device, where eth0 is the default primary interface, eth1 is the Ethernet failover interface, eth0.999 is the VLAN-enabled interface for management traffic, one static route is defined on eth0.999, when eth0 is up normally and eth0.999 is routable for management traffic. If eth0 fails and switches to eth1, the static route does not switch with it and the static route does not display in the routing table. [PR/1080510]
  • The calculation of PPS occurs incorrectly for CTP bundles with Exclusive OR (XOR) packet protector enabled. The PPS value almost doubles from its previous value and the Run State becomes tooFast when you enable XOR packet protector to duplicate and receive packets. [PR/1082106]
  • The direct drive capability (using IP tables instead of direct drive for packet-forwarding) is disabled by default. [PR/1083475]
  • In compliance with the U.S. Department of Defense Joint Interoperability Test Command (JITC) requirements, when the security level of the CTP Series platforms is set as high, the JITC high security mode requires that the CTP device must automatically disable accounts after a 35-day period of account inactivity. A mechanism to unlock and reenable such disabled user accounts is not available. [PR/1085019]
  • With an NMS server that uses SNMP and SSH queries to determine status on a network of CTP devices, SNMP Get operations cause packet loss and starvations in your circuit. [PR/1105651]
  • The display of jitter and latency in the CTP bundle query output for MIB browsers is not supported. [PR/1106063]
  • Both-ended Y-cable redundancy configuration (hardware-based redundancy or software-based Y cable link protocol) does not support loss of signal (LOS) checking for pulled cable failures. [PR/1110021]
  • NTP authentication is not supported on CTP devices to check the authenticity of NTP server before synchronizing local time with the server. [PR/1110250]
  • You cannot associate multiple master nodes with a single backup node in Network node reference (NetRef). [PR/1110275]
  • The FAIL_DELAY value in /etc/login.defs meets the GPOS STIG rule of that requires a minimum of 4 seconds between login failures. The same rule needs to be applied to the /etc/pam.d/system-auth file. [PR/1114496]
  • Support is needed for separate interfaces to be used for the management and circuit networks so that traffic segregation can be achieved at the physical interface level. [PR/1119202]
  • The snmpAcorn.pl script is run in daemon mode because it is observed that snmpAcorn.pl is causing high CPU usage for the complete SNMP walk of Acorn MIB. [PR/1119228]
  • Only full-duplex mode must be supported on the network interface card (NIC) ports of the far-end switch or router connected to the CTP devices. [PR/1125632]
  • The CTP2008 platform is reset intermittently when the Ethernet ports are operating at different speeds and the bundle traffic is flowing though the Ethernet eth0 interface, which is the default interface for the CTP devices, and eth1 (1G autonegotiation) is used to connect to the management network with the CTPView server. [PR/1133527]
  • The 4WE&M interface does not pass audio tone when you configure the interface for a CESoPSN bundle. If you use the same ports and configure for VComp bundles, audio tone passes properly. No audio tone is transmitted even if you delete the bundle and reconfigure as a CESoPSN bundle. [PR/1137814]
  • A memory leak occurs when SNMPV3 is enabled. It is observed that after one and a half days, all of the bundles start generating continuous errors until the CTP2056 platform resets. [PR/1139254]
  • It is necessary to add login information for RADIUS users into the syslog file and address OpenSSL security vulnerabilities. [PR/1144964]
  • BERT counters are not cleared for CESoPSN bundles in the CTP Menu. [PR/1030232]
  • CTP systems that are installed with analog cards enter an unusable state when T1/E1 and VComp cards are not present. [PR/1089541]
  • Disabling the DTE serial port causes RL signal output to go active. [PR/1153461]

Modified: 2016-02-08