Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement handling of Juniper BGP traps (jnxBgpM2BackwardTransition and jnxBgpM2Established from BGP4-V2-MIB-JUNIPER) #288

Closed
Tracked by #173
lunkwill42 opened this issue Jul 4, 2024 · 1 comment
Closed
Tracked by #173

Implement handling of Juniper BGP traps (jnxBgpM2BackwardTransition and jnxBgpM2Established from BGP4-V2-MIB-JUNIPER) #288

lunkwill42 opened this issue Jul 4, 2024 · 1 comment
Assignees
@lunkwill42
Labels
enhancement New feature or request

Comments

@lunkwill42
Copy link
Member

lunkwill42 commented Jul 4, 2024 •
edited
Loading

Zino 1 appears to ignore traps from the regular IETF BGP4-MIB, and only handles traps from the Juniper-specific BGP MIB BGP4-V2-MIB-JUNIPER.

Mainly two traps are handled:

  • jnxBgpM2BackwardTransition - indicates that a BGP peer was lost.
  • jnxBgpM2Established - indicates that a BGP peer came back up.
@lunkwill42 lunkwill42 mentioned this issue Jul 4, 2024
Closed
14 tasks
@lunkwill42 lunkwill42 changed the title BGP4-V2-MIB-JUNIPER::jnxBgpM2BackwardTransition and BGP4-V2-MIB-JUNIPER::jnxBgpM2Established Implement handling of Juniper BGP traps (jnxBgpM2BackwardTransition and jnxBgpM2Established from BGP4-V2-MIB-JUNIPER) Jul 4, 2024
@lunkwill42 lunkwill42 self-assigned this Jul 4, 2024
@lunkwill42 lunkwill42 added the enhancement New feature or request label Jul 4, 2024
This was referenced Jul 4, 2024
Merged
Merged
Merged
@lunkwill42
Copy link
Member Author

Closed by #291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lunkwill42 lunkwill42

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lunkwill42