The CA Spectrum Secure Domain Connector (SDC) shows a Null varbind value in traps and/or the SdmConnectorService uses 100% cpu.

Document ID : KB000006706
Last Modified Date : 14/02/2018
Show Technical Document Details

This document outlines 2 issues that are fixed in the same patch:

1.  When traps are sent through the SDC to the SS, the varbind values are not correctly processed and show a Null value.

2.  The Sdmconnectorservice utilizes 100% CPU when IP Version 6 Linux Kernel Module is disabled

Spectrum 10.2

Both problems are due to internal code flaws.




Both problems are resolved with 10.02.00.PTF_10.2.036a. Please open a ticket with Spectrum Support if this fix is needed.  


The release notes also show other fixes as this is a bundled patch.  These are described by the technical documents linked here:


Symptom: SDC traps contain incorrect varbind values for unsigned 32bit data types.

        Resolution: Resolved issue causing incorrect varbind values for unsigned 32bit data types.

        (DE286012, 00717832)


        Symptom: Rare but consistent SpectroSERVER hangs due to multiple problems with the SNMP subsystem. 

        Symptoms can include failed online backups, failed shutdowns and invalid management agent lost alarms.


        Resolution: Major overhaul of SNMP subsystem, designed to improve efficiency and stability. 

(DE198464, 00502085)


        Symptom: Secure Domain Connector( SDC ) always listens for SNMP traps 

and SDM connections on all interfaces.


Resolution: Extended Secure Domain Connector( SDC ) functionality to 

allow IP-specific binding for SNMP traps and SDM connections.

(DE263283, 00627431)


        Symptom: SpectroSERVER not establishing connection to Secure Domain Connector.


        Resolution: Resolved deadlock preventing SDC connections from being established.

(DE277727, 00679511)


        Symptom: Unknown log-entries in Spectrum Control Panel(VNM.OUT).


        Resolution:  Unknown log-entries  are not seen in SCP/VNM.OUT, after the fix.

        (DE266961, 00640407)

Additional Information:

This PTF 10.02.00.PTF_10.2.036a does include 10.02.00.PTF_10.2.031