Tristan
Tristan
Sorry for the late reply. I think it would sort of work. The only potential issue is if two instances are trying to write to the database at the same...
I notice the same issue
@emilyHere6 o/ It seemed to me that the maintainer didn't manage to find time to work on this project anymore... So I gave up and started using another tool (Cryptgeon).
I agree, I'm too used to copy-pasting with just a simple selection.
Hi! First, thank you for all the work you've done and for sharing that @lausser To follow up on this, I noticed the same issue when setting the "junos" servertype...
Hello! > Well, no answer after a week. Then fix that yourself. Thank you for taking the time to look into that, and sorry for the late answer, I didn't...
It is clearly the BGP4-MIB which is used instead of the JUNOS-BGP4V2-MIB. ``` ./check_nwc_health-new-juniper '--community' 'XXXXXXXX' '--hostname' '198.51.100.10' '--mode' 'bgp-peer-status' '--name' '2001:0db8:0000:0000:0000:0000:0000:0010' '--servertype' 'junos' '--timeout' '60' -vvvvvvvvvvvvvvv […] [PEERSUBSYSTEM] BGP4-MIB_bgpPeerTable_bgpPeerRemoteAddr_cache:...