-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VIPTELA-TRAPS.mib missing item 114 #81
Comments
@mhuot, which file? |
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:
***@***.***>
|
Noting that I have the Viptela devs checking. |
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 |
Are you sure you were using viptela-mibs/20.3/VIPTELA-TRAPS.mib? |
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 viptelaSecuritySecurityUnclaimedVedgeEntryAdded NOTIFICATION-TYPE 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.
|
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. |
@mhuot, in case you missed it. @mamdiall2 and co published 20.12 MIB files which have 114-123 in traps. https://github.com/cisco/cisco-mibs/blob/main/viptela-mibs/20.12/VIPTELA-TRAPS.mib#L3110-L3121 I believe that should address this issue tracker item. Let me know. |
The viptela-traps 2 table ends at 113 but I am seeing 114 traps being sent.
The text was updated successfully, but these errors were encountered: