Hello,
I'm tring to get nocol bgpmon to tell me the status of my BGP peers. All my
BGP peers are working as I do my testing. I'm running ONLY with
Ciscorouters version 11.3. Where I run the bgpmon it tells me, that my
bgppeers are down? Can anybosy tell me why? Bellow is the debug output from
bgpmon and my configuration fil. I did of course change the passwords to
<PASSWD>. Could it be because bgpmon dosen't talk to my Cisco equipment
right? What should I do?
su-2.03# bin/bgpmon
bin/bgpmon: new object (ASCEND_GRF_1.3.8) = 616, %PASS%:sho bgp sum:exit
bin/bgpmon: new object (ASCEND_GRF_1.3.11) = 616, %PASS%:sho bgp sum:exit
bin/bgpmon: new object (ASCEND_GRF_1.4.6) = 616, %PASS%:sho bgp sum:exit
bin/bgpmon: new object (CISCO_11.x) = 23, %PASS%:sh ip bgp sum:exit
bin/bgpmon: new object (BAY_1.27) = 23, %USER%:%PASS%:sho bgp peer:exit
bin/bgpmon: new router (I_NUK-1) is a CISCO_11.x (192.168.8.1)
bin/bgpmon: new router (I_TVBY-1) is a CISCO_11.x (192.168.10.2)
bin/bgpmon: new router (I_KAN-GE-USA) is a CISCO_11.x (192.168.12.2)
bin/bgpmon: added severity for as008818 - E_CRITICAL
bin/bgpmon: added severity for as005492 - E_CRITICAL
bin/bgpmon: added severity for as004969 - E_CRITICAL
bin/bgpmon: -, I_NUK-1, 192.168.10.2
bin/bgpmon: initializing: 192.168.10.2 BGP/I_NUK-1 (I_NUK-1:192.168.10.2)
bin/bgpmon: -, I_NUK-1, 192.168.12.2
bin/bgpmon: initializing: 192.168.12.2 BGP/I_NUK-1 (I_NUK-1:192.168.12.2)
bin/bgpmon: -, I_TVBY-1, 192.168.10.1
bin/bgpmon: initializing: 192.168.10.1 BGP/I_TVBY-1 (I_TVBY-1:192.168.10.1)
bin/bgpmon: -, I_TVBY-1, 130.227.0.153
bin/bgpmon: initializing: ser8-1-0.val2-core BGP/I_TVBY-1
(I_TVBY-1:130.227.0.153)
bin/bgpmon: -, I_KAN-GE-USA, 192.168.12.1
bin/bgpmon: initializing: 192.168.12.1 BGP/I_KAN-GE-USA
(I_KAN-GE-USA:192.168.12.1)
bin/bgpmon: -, I_KAN-GE-USA, 207.8.136.5
bin/bgpmon: initializing: ge-greenland BGP/I_KAN-GE-USA
(I_KAN-GE-USA:207.8.136.5)
bin/bgpmon: connecting to 192.168.8.1:23
bin/bgpmon: sending command: <PASSWD>
bin/bgpmon: sending command: sh ip bgp sum
bin/bgpmon: sending command: exit
bin/bgpmon: socket closed, 15 lines captured.
bin/bgpmon: item already exists: I_NUK-1:192.168.10.2
bin/bgpmon: item already exists: I_NUK-1:192.168.12.2
bin/bgpmon: connecting to 192.168.10.2:23
bin/bgpmon: sending command: <PASSWD>
bin/bgpmon: sending command: sh ip bgp sum
bin/bgpmon: sending command: exit
bin/bgpmon: socket closed, 15 lines captured.
bin/bgpmon: item already exists: I_TVBY-1:130.227.0.153
bin/bgpmon: item already exists: I_TVBY-1:192.168.10.1
bin/bgpmon: connecting to 192.168.12.2:23
bin/bgpmon: sending command: <PASSWD>
bin/bgpmon: sending command: sh ip bgp sum
bin/bgpmon: sending command: exit
bin/bgpmon: socket closed, 15 lines captured.
bin/bgpmon: item already exists: I_KAN-GE-USA:192.168.12.1
bin/bgpmon: item already exists: I_KAN-GE-USA:207.8.136.5
bin/bgpmon: connecting to 192.168.12.2:23
bin/bgpmon: sending command: <PASSWD>
bin/bgpmon: sending command: sh ip bgp sum
bin/bgpmon: sending command: exit
bin/bgpmon: socket closed, 15 lines captured.
bin/bgpmon: status of 192.168.12.1:
Unknown host (no address)- nocol.navya.com
eventlog- could not connect to nocol.navya.com
bin/bgpmon: update_event: I_KAN-GE-USA:192.168.12.1, 0, 0, 1 (008818)
bin/bgpmon: status of 207.8.136.5:
bin/bgpmon: update_event: I_KAN-GE-USA:207.8.136.5, 0, 0, 1 (004969)
bin/bgpmon: status of 192.168.12.1:
bin/bgpmon: update_event: I_KAN-GE-USA:192.168.12.1, 0, 0, 1 (008818)
bin/bgpmon: status of 207.8.136.5:
bin/bgpmon: update_event: I_KAN-GE-USA:207.8.136.5, 0, 0, 1 (004969)
bin/bgpmon: connecting to 192.168.10.2:23
bin/bgpmon: sending command: <PASSWD>
bin/bgpmon: sending command: sh ip bgp sum
bin/bgpmon: sending command: exit
bin/bgpmon: socket closed, 15 lines captured.
bin/bgpmon: status of 130.227.0.153:
bin/bgpmon: update_event: I_TVBY-1:130.227.0.153, 0, 0, 1 (005492)
bin/bgpmon: status of 192.168.10.1:
bin/bgpmon: update_event: I_TVBY-1:192.168.10.1, 0, 0, 1 (008818)
bin/bgpmon: status of 130.227.0.153:
bin/bgpmon: update_event: I_TVBY-1:130.227.0.153, 0, 0, 1 (005492)
bin/bgpmon: status of 192.168.10.1:
bin/bgpmon: update_event: I_TVBY-1:192.168.10.1, 0, 0, 1 (008818)
bin/bgpmon: connecting to 192.168.8.1:23
bin/bgpmon: sending command: <PASSWD>
bin/bgpmon: sending command: sh ip bgp sum
bin/bgpmon: sending command: exit
bin/bgpmon: socket closed, 15 lines captured.
bin/bgpmon: status of 192.168.10.2:
bin/bgpmon: update_event: I_NUK-1:192.168.10.2, 0, 0, 1 (008818)
bin/bgpmon: status of 192.168.12.2:
bin/bgpmon: update_event: I_NUK-1:192.168.12.2, 0, 0, 1 (008818)
bin/bgpmon: status of 192.168.10.2:
bin/bgpmon: update_event: I_NUK-1:192.168.10.2, 0, 0, 1 (008818)
bin/bgpmon: status of 192.168.12.2:
bin/bgpmon: update_event: I_NUK-1:192.168.12.2, 0, 0, 1 (008818)
bin/bgpmon: opening /usr/local/nocol/data/bgpmon-output for writing
_________________________________________________________
su-2.03# cat etc/bgpmon-confg
# bgpmon-confg - bgpmon master configuration
#
## Use this file with bgpmon v2.0 and above.
#
###
# - You define router types (objects).
# - Then, for each of your router, specify its type and login password.
# - Finally, define which routers you want to monitor and optionally, the
# peers and max severity based on the AS number.
###
#
# Set a different polling interval - default 5 mins
pollinterval 300
## THIS SECTION DOES NOT REQUIRE EDITING NORMALLY
# OBJECT DEFINITIONS - how to obtain and parse the bgp summary
#
# IMPORTANT NOTE: the version numbers linked with each object are the
# versions of firmware that the configuration was
# tested with. It could very well work with other (especially
# newer) versions of the firmware, and possibly older versions
# as well. YOU DO NOT NEED TO ADD A NEW CONFIGURATION FOR YOUR
# FIRMWARE REVISION UNLESS NONE OF THE EXISTING ONES WORK.
#
# TYPE PORT ARYREF UPVAL COMMAND SEQUENCE
object ASCEND_GRF_1.3.8 616 8,1,3 Established %PASS%:sho bgp sum:exit
object ASCEND_GRF_1.3.11 616 10,1,3 Established %PASS%:sho bgp sum:exit
object ASCEND_GRF_1.4.6 616 10,0,2 Established %PASS%:sho bgp sum:exit
object CISCO_11.x 23 9,0,2 \d+ %PASS%:sh ip bgp sum:exit
object BAY_1.27 23 4,0,2 Estab %USER%:%PASS%:sho bgp peer:exit
### EDIT THIS FOLLOWING SECTIONS ###
## ROUTER DEFINITIONS - used in conjunction with peer/router statements
#
# NAME TYPE IP ADDRESS PASS USER (opt)
#router_def sfo-rtr ASCEND_GRF_1.3.8 205.215.xx.xx password
#router_def pdl-bay BAY_1.27 205.215.xx.xx password netadmin
router_def I_NUK-1 CISCO_11.x 192.168.8.1 <PASSWD>
router_def I_TVBY-1 CISCO_11.x 192.168.10.2 <PASSWD>
router_def I_KAN-GE-USA CISCO_11.x 192.168.12.2 <PASSWD>
## ROUTERS TO MONITOR - will monitor all bgp peers/sessions on a router
#
# NAME
router I_NUK-1
router I_TVBY-1
router I_KAN-GE-USA
#router pdl-bay
## SINGLE PEERS TO MONITOR - will monitor only this peer on a router
# NOTE: you can put a - for the peer name if you wish the name to be
# determined by DNS.
#
# ROUTER NAME PEER NAME PEER IP
#peer I_NUK-1 I_TVBY-1 192.168.10.2
#peer I_NUK-1 I_Kan-GE-USA 192.168.12.2
#peer I_TVBY-1 I_NUK-1 192.168.10.1
#peer I_TVBY-1 UNI2 130.227.0.153
#peer I_KAN-GE-USA I_NUK-1 192.168.12.1
#peer I_KAN-GE-USA NETAXS 207.8.136.5
peer I_NUK-1 - 192.168.10.2
peer I_NUK-1 - 192.168.12.2
peer I_TVBY-1 - 192.168.10.1
peer I_TVBY-1 - 130.227.0.153
peer I_KAN-GE-USA - 192.168.12.1
peer I_KAN-GE-USA - 207.8.136.5
## SEVERITY - defines severity levels based on AS number
#severity DEFAULT E_ERROR
#severity 4006 E_CRITICAL # Netrail (very important)
#severity 3491 E_WARNING # CAIS (so used to seeing it in alarm)
severity 8818 E_CRITICAL # Netrail (very important)
severity 5492 E_CRITICAL # Netrail (very important)
severity 4969 E_CRITICAL # Netrail (very important)
## Assume all peers on a router are unchanged from their last known status in
# the event that a router cannot be reached. If you wish to assume that all
# peers would be down in this event, use 'down' as an assumption
# assume <unchanged | down>
ASSUME unchanged
# EOF
_____________________________________________________________________
Thank you for taking the time to read my mail.
Best Regards
Lasse
|