VIPTELA-TRAPS.mib missing item 114

[mhuot]

The viptela-traps 2 table ends at 113 but I am seeing 114 traps being sent.

[kyzer-davis]

@mhuot, which file?

[mhuot]

viptela-mibs/20.3/VIPTELA-TRAPS.mib only has 113 and my equipment sends a 114. I can get a tcpdump or any other info if needed. Mike

…

On Tue, May 7, 2024 at 12:48 PM Kyzer Davis ***@***.***> wrote: @mhuot <https://github.com/mhuot>, which file? — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANSY7BHJTOFFDWGTWYJ3RLZBEHVHAVCNFSM6AAAAABHJQ32RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYHE4DMOBQGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mhuot]

There are some other values missing as can be seen in this screen shot.

[kyzer-davis]

Noting that I have the Viptela devs checking.

[mhuot]

Thanks! Let me know what else is needed. I haven't looked at this in a while and I wasn't very clea, the issue is there is no entry in the mib for .1.3.5.1.4.1.41916.100.2.100.2.114

[mamdiall2]

viptela-mibs/20.3/VIPTELA-TRAPS.mib only has 113 and my equipment sends a 114. I can get a tcpdump or any other info if needed. Mike
…
On Tue, May 7, 2024 at 12:48 PM Kyzer Davis @.> wrote: @mhuot https://github.com/mhuot, which file? — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANSY7BHJTOFFDWGTWYJ3RLZBEHVHAVCNFSM6AAAAABHJQ32RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYHE4DMOBQGE . You are receiving this because you were mentioned.Message ID: @.>

Are you sure you were using viptela-mibs/20.3/VIPTELA-TRAPS.mib?
What is the image version on your device?

[mhuot]

Yes, I retrieved the file from https://raw.githubusercontent.com/cisco/cisco-mibs/dc0e8c3ff1454736d041ab70a12357cfd8ad1103/viptela-mibs/20.3/VIPTELA-TRAPS.mib

Here is the end of the file showing it does not have a 114

`viptelaCdbUnlocked NOTIFICATION-TYPE
OBJECTS {
eventTime,
netconfNotificationSeverity,
viptelaSecurityPersonality
}
STATUS current
DESCRIPTION "viptela trap from viptela-security"
::= { traps 112 }

viptelaSecuritySecurityUnclaimedVedgeEntryAdded NOTIFICATION-TYPE
OBJECTS {
eventTime,
netconfNotificationSeverity,
viptelaSecurityUuid,
viptelaSecuritySerial,
viptelaSecuritySubjectSerialNumber,
viptelaSecurityOrganizationName
}
STATUS current
DESCRIPTION "viptela trap from viptela-security"
::= { traps 113 }

END`

The image is version 20.6.3.2 but the issue has been present for earlier version.

[mamdiall2]

Yes, I retrieved the file from https://raw.githubusercontent.com/cisco/cisco-mibs/dc0e8c3ff1454736d041ab70a12357cfd8ad1103/viptela-mibs/20.3/VIPTELA-TRAPS.mib

Here is the end of the file showing it does not have a 114

`viptelaCdbUnlocked NOTIFICATION-TYPE OBJECTS { eventTime, netconfNotificationSeverity, viptelaSecurityPersonality } STATUS current DESCRIPTION "viptela trap from viptela-security" ::= { traps 112 }

viptelaSecuritySecurityUnclaimedVedgeEntryAdded NOTIFICATION-TYPE OBJECTS { eventTime, netconfNotificationSeverity, viptelaSecurityUuid, viptelaSecuritySerial, viptelaSecuritySubjectSerialNumber, viptelaSecurityOrganizationName } STATUS current DESCRIPTION "viptela trap from viptela-security" ::= { traps 113 }

END`

The image is version 20.6.3.2 but the issue has been present for earlier version.

On 20.6, viptela-traps.mib have all the way to 117. And I think this is the reason why you are seeing 114 on your device.

viptelaPolicyAppListUnsupportedAppNotify NOTIFICATION-TYPE
    OBJECTS {
        eventTime,
        netconfNotificationSeverity,
        viptelaPolicyAppListName,
        viptelaPolicyUnsupportedApp
    }
    STATUS current
    DESCRIPTION "viptela trap from viptela-policy"
    ::= { traps 117 }


END

[mhuot]

Where can I get that? I don't see it in https://github.com/cisco/cisco-mibs/tree/main/viptela-mibs Is it elsewhere?

[mamdiall2]

Where can I get that? I don't see it in https://github.com/cisco/cisco-mibs/tree/main/viptela-mibs Is it elsewhere?

This has not yet been published. I will talk to my manager and see if we need to publish that.