Spectrum Server Crash open Checkpoint VSX table on an un-certified device.
At the time of crash in the VNM.OUT you may see this error message
Nov 18 16:49:08 ERROR TRACE at CsOIDValL.cc(235): CsOIDValueList buf length 125468707 is exceeding 8MB limit : aborting unpacking
Release : 10.3.x, 10.4.0, 10.4.1, 10.4.2.0, 10.4.2.1
Component : Spectrum Core / SpectroSERVER
This is fully resolved in 10.4.2.2
Symptom: SpectroSERVER crashes while reading the external attributes from the device for the SNMP mib mismatched datatypes.
Resolution: SpectroSERVER not crashes while reading the external attributes from device for the snmp mib mismatched datatypes. (DE477168, 32215136, 10.4.2.1)
Symptom: SpectroSERVER crashes while expanding the checkpoint VSX view table.
Resolution: Code changes are made to stop SpectroSERVER from crashing while expanding the checkpoint VSX view table. (DE467946, 32065353, 10.4.2.2)
Temporary workaround:
I have checked spectrum code base and its certified with old CHECKPOINT-MIB file (64000_R76SP_50_chkpnt_mib)
Please see below spectrum vs CHECKPOINT-MIB vsx OID information as follows,
vsxCountersTable OBJECT-TYPE
SYNTAX SEQUENCE OF VsxCountersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table with accumulated VSX data such as connection and packet count"
::= { vsxCounters 1 }
vsxCountersEntry OBJECT-TYPE
SYNTAX VsxCountersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
""
INDEX { vsxStatusVSId }
::= { vsxCountersTable 1 }
VsxCountersEntry ::=
SEQUENCE {
vsxCountersVSId
INTEGER,
vsxCountersConnNum
INTEGER,
vsxCountersConnPeakNum
INTEGER,
vsxCountersConnTableLimit
INTEGER,
vsxCountersPackets
DisplayString,
vsxCountersDroppedTotal
DisplayString,
vsxCountersAcceptedTotal
DisplayString,
vsxCountersRejectedTotal
DisplayString,
vsxCountersBytesAcceptedTotal
DisplayString,
vsxCountersBytesDroppedTotal
DisplayString,
vsxCountersBytesRejectedTotal
DisplayString,
vsxCountersLoggedTotal
DisplayString,
vsxCountersIsDataValid
INTEGER
}
vsxCountersPackets(1.3.6.1.4.1.2620.1.16.23.1.1.5) attribute certified its datatype as "Text String" in Spectrum but the same OID defined as "Counter64" as per the customer provided walk file( same applicable for other VsxTable attributes).
1.3.6.1.4.1.2620.1.16.23.1.1.5.1.0, Counter64 , 6496124
For workaround to avoid the SpectroSERVER crash, please follow below steps( Spectrum not reads the VSX counter values from device while expanding VSXTable)
Shutdown the OneClick Server.
Take a backup of $(SPECROOT)/tomcat/webapps/spectrum/WEB-INF/topo/config/table-checkpoint-vsx-counters.xml file
Copy the attached file to $(SPECROOT)/tomcat/webapps/spectrum/WEB-INF/topo/config/table-checkpoint-vsx-counters.xml location
Start the oneClick Server
Check the SpectroSERVER behavior by expanding the VsxTable information via oneClient application.
We will certify the device with the new mib which has the corrected data type.
A certification request has been opened and is tentatively scheduled to be included in the NetOps 20.4 release due out in Q4 of 2020.