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

No BGP info for Juniper BGP peers #5531

Closed
BradHooper opened this Issue Jan 20, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@BradHooper

BradHooper commented Jan 20, 2017

After recent SQL changes ( #5420 ) all BGP peers have been removed from the bgpPeers_cbgp table for all Juniper devices.

This is happening on 20+ devices. Can provide full debug via email/IRC.

DO NOT DELETE THIS INFORMATION.

Please read this information carefully.

GitHub issues is for feature requests or bugs, please do not post issues asking for help or how to do X, Y or Z.
You can use our irc channel ##librenms on freenode to ask questions or our community site.

Please confirm each of the sections below by putting an x in the box like [x].

  • Is your install up to date? Updating your install
    Please do not submit an issue if your install is not up to date within the last 24 hours or on a stable monthly release.
  • Please include all of the information between the ==================================== section of ./validate.php which you can run from the cli.
  • Unless your issue is for a WebUI fix or feature then please provide ALL info asked for here.
  • Please provide as much detail as possible.
  • Please do NOT post more than 10 lines of debug information here, use a pastebin service or GitHub Gists.
Component Version
LibreNMS d83d08e
DB Schema 156
PHP 7.0.12
MySQL 5.5.50-MariaDB
RRDTool 1.4.8
SNMP NET-SNMP 5.7.2

-bash-4.2$ cat bgpdebug | grep 1.1.1.1
Found peer 1.1.1.1 (AS666)
[7.ipv4.210.9.30.254.1.1.1.1.1] => Array
peerindex for ipv4 1.1.1.1 is 2
SQL[SELECT COUNT() from bgpPeers WHERE device_id = '63' AND bgpPeerIdentifier = '1.1.1.1']
SQL[UPDATE bgpPeers set bgpPeerRemoteAs ='666',astext ='' WHERE device_id='63' AND bgpPeerIdentifier='1.1.1.1']
.SQL[SELECT COUNT(
) from bgpPeers_cbgp WHERE device_id = '63' AND bgpPeerIdentifier = '1.1.1.1' AND afi='ipv4' AND safi='unicast']
SQL[INSERT INTO bgpPeers_cbgp (device_id,bgpPeerIdentifier,afi,safi) VALUES ('63','1.1.1.1','ipv4','unicast')]
SQL[SELECT * FROM bgpPeers_cbgp WHERE device_id = '63' AND bgpPeerIdentifier = '1.1.1.1']
SQL[DELETE FROM bgpPeers_cbgp WHERE device_id = '63' AND bgpPeerIdentifier = '1.1.1.1' AND afi='ipv4' AND safi='unicast']

@laf

This comment has been minimized.

Show comment
Hide comment
@laf

laf Jan 20, 2017

Member

Can you try reverting to this commit pls:

9fa8485

If that works I think what's happened is that this has always been broken but the data could not be deleted before, now that's fixed it is :)

Member

laf commented Jan 20, 2017

Can you try reverting to this commit pls:

9fa8485

If that works I think what's happened is that this has always been broken but the data could not be deleted before, now that's fixed it is :)

@BradHooper

This comment has been minimized.

Show comment
Hide comment
@BradHooper

BradHooper Jan 20, 2017

Yeah understand the delete now works correctly. I've just rolled back and now bgpPeers_cbgp is populating.

BradHooper commented Jan 20, 2017

Yeah understand the delete now works correctly. I've just rolled back and now bgpPeers_cbgp is populating.

@laf

This comment has been minimized.

Show comment
Hide comment
@laf

laf Jan 20, 2017

Member

Can you post a debug output for this, an snmpwalk would be ace as well.

Member

laf commented Jan 20, 2017

Can you post a debug output for this, an snmpwalk would be ace as well.

laf added a commit to laf/librenms that referenced this issue Jan 21, 2017

@laf laf removed the Needs-Info label Jan 21, 2017

@laf laf closed this in #5536 Jan 22, 2017

laf added a commit that referenced this issue Jan 22, 2017

@lock

This comment has been minimized.

Show comment
Hide comment
@lock

lock bot May 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

lock bot commented May 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@lock lock bot locked as resolved and limited conversation to collaborators May 18, 2018

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