ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SpectroSERVER crashed accessing VIPTELA_POLICY mib attributes in Spectrum

book

Article ID: 186982

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

SpectroSERVER crashed accessing VIPTELA_POLICY mib attributes in Spectrum.

Specifically, the policerRate attribute.

 

Cause

There is a datatype mismatch between the VIPTELA_POLICY mib file used to create these attributes in Spectrum and the datatype of the attribute in the mib database on the device.

For example, VIPTELA_POLICY mib file used to create the policerRate attribute in Spectrum used the ConfdString datatype as follows:

-- tagpath /policer/rate
policerRate OBJECT-TYPE
    SYNTAX      ConfdString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION "Bandwidth, in bps"
    ::= { policerEntry 4 }


However, in the mib database on the device, the datatype is Counter 64.

When Spectrum reads the value of the policerRate attribute on the device, it is expecting one datatype but the value returned is a totally different datatype.

Environment

Release : Any

Component : Spectrum Core / SpectroSERVER

Resolution

There is no out of the box functionality in Spectrum that reads any attributes from the VIPTELA_POLICY mib. This only occurred after the user manually read the value of this attribute using the Attributes tab.

The only solution at this time is to avoid reading these attributes.

The Spectrum development team has received new version of the Viptela mibs that have corrected this datatype mismatch and is in the process of certifying them for a future release of Spectrum.