Junos OS

last person joined: 2 days ago 

Ask questions and share experiences about Junos OS.
  • 1.  show log message, where only can see SNMP_TRAP_LINK_DOWN, nothing indicating circuit up time.

    Posted 03-01-2012 18:07

    Hi

     

    Our customer using M40e router, on alarm log it is only showing time circuit when down, but none of the log showing is up.

     

    It is important to us to know the down time and up time especially for circuit flapping issue.

    Currently sh log can’t show us how frequent it’s flapped, how long each flap occurs

     

    Here by I attached show log message, where only can see SNMP_TRAP_LINK_DOWN, nothing indicating circuit up time

     

    Feb 23 18:30:01  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:30:10  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:32:04  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:33:00  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:34:17  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:34:22  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:35:42  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:36:26  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:36:32  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:39:28  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

    Feb 23 18:41:34  M40eMY_1_RE0 mib2d[992]: SNMP_TRAP_LINK_DOWN: ifIndex 172, ifAdminStatus up(1), ifOperStatus down(2), ifName t3-0/2/1.0

     

    *only down time shows, then when it is up before it going down again?



  • 2.  RE: show log message, where only can see SNMP_TRAP_LINK_DOWN, nothing indicating circuit up time.

     
    Posted 03-02-2012 08:23

    Hi,

     

    JUNOS has the notion of severity when it comes to log messages, where a link-down is a "bad" thing (more severe) and a "link-up" a good thing (less severe). So a link-down has the severity of "warning" and a link-up has the severity of "info". The default severity level is somewhere inbetween, so that you see the downs but not the ups. To be able to see the ups also you need to add something like "set system syslog <destination> daemon info" to your config.

     

    Best Regards

     

    Ulf



  • 3.  RE: show log message, where only can see SNMP_TRAP_LINK_DOWN, nothing indicating circuit up time.

    Posted 03-04-2012 18:27

    Hi,

     

    Please try the command show interface ..... extensive.   U can see the last flap. Thanks



  • 4.  RE: show log message, where only can see SNMP_TRAP_LINK_DOWN, nothing indicating circuit up time.
    Best Answer

    Posted 03-08-2012 11:59

    Try damon info.  Notice test results below.  I hope this helps.  Regards, Johnny

     

    [edit system syslog file messages]
    juniper@SRX240-5# show
    any notice;
    authorization info;
    daemon info;

    [edit system syslog file messages]
    juniper@SRX240-5# commit
    commit complete

    [edit system syslog file messages]
    juniper@SRX240-5# run show log messages
    Mar 8 19:50:01 SRX240-5 clear-log[1510]: logfile cleared
    Mar  8 19:51:33  SRX240-5 mgd[1219]: UI_COMMIT: User 'juniper' requested 'commit' operation (comment: none)

    [edit system syslog file messages]
    juniper@SRX240-5# run show log messages
    Mar 8 19:50:01 SRX240-5 clear-log[1510]: logfile cleared
    Mar  8 19:51:33  SRX240-5 mgd[1219]: UI_COMMIT: User 'juniper' requested 'commit' operation (comment: none)
    Mar  8 19:52:43  SRX240-5 mib2d[1092]: SNMP_TRAP_LINK_DOWN: ifIndex 515, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/0/6
    Mar  8 19:52:43  SRX240-5 eventd: sendto: Network is down
    Mar  8 19:52:43  SRX240-5 rpd[1093]: EVENT <UpDown> ge-0/0/6.0 index 71 <Broadcast Multicast> address #0 0.26.88.eb.51.86
    Mar  8 19:52:43  SRX240-5 rpd[1093]: EVENT UpDown ge-0/0/6.0 index 71 10.7.122.3/24 -> 10.7.122.255 <Broadcast Multicast Localup>
    Mar  8 19:52:43  SRX240-5 rpd[1093]: EVENT UpDown ge-0/0/6.0 index 71 2001:1890:8400:122::3/64 -> (null) <Broadcast Multicast Localup>
    Mar  8 19:52:43  SRX240-5 rpd[1093]: EVENT UpDown ge-0/0/6.0 index 71 fe80::226:88ff:feeb:5186/64 -> (null) <Broadcast Multicast Localup>
    Mar  8 19:52:43  SRX240-5 rpd[1093]: EVENT <UpDown> index 139 <Broadcast Multicast> address #0 0.26.88.eb.51.86
    Mar  8 19:52:43  SRX240-5 rpd[1093]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.7.122.2 (realm ospf-v2 ge-0/0/6.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)
    Mar  8 19:52:43  SRX240-5 rpd[1093]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.7.122.1 (realm ospf-v2 ge-0/0/6.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)
    Mar  8 19:52:43  SRX240-5 rpd[1093]: RPD_OSPF_NBRDOWN: OSPF neighbor fe80::8271:1fff:fec3:9881 (realm ipv6-unicast ge-0/0/6.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)
    Mar  8 19:52:43  SRX240-5 rpd[1093]: RPD_OSPF_NBRDOWN: OSPF neighbor fe80::8271:1fff:fec0:3c81 (realm ipv6-unicast ge-0/0/6.0 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)
    Mar  8 19:52:51  SRX240-5 rpd[1093]: EVENT <UpDown> ge-0/0/6.0 index 71 <Up Broadcast Multicast> address #0 0.26.88.eb.51.86
    Mar  8 19:52:51  SRX240-5 mib2d[1092]: SNMP_TRAP_LINK_UP: ifIndex 515, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/0/6
    Mar  8 19:52:51  SRX240-5 mib2d[1092]: SNMP_TRAP_LINK_UP: ifIndex 545, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/0/6.0
    Mar  8 19:52:51  SRX240-5 rpd[1093]: EVENT UpDown ge-0/0/6.0 index 71 10.7.122.3/24 -> 10.7.122.255 <Up Broadcast Multicast>
    Mar  8 19:52:51  SRX240-5 rpd[1093]: EVENT UpDown ge-0/0/6.0 index 71 2001:1890:8400:122::3/64 -> (null) <Up Broadcast Multicast>
    Mar  8 19:52:51  SRX240-5 rpd[1093]: EVENT UpDown ge-0/0/6.0 index 71 fe80::226:88ff:feeb:5186/64 -> (null) <Up Broadcast Multicast>
    Mar  8 19:52:51  SRX240-5 rpd[1093]: EVENT <UpDown> index 139 <Up Broadcast Multicast> address #0 0.26.88.eb.51.86
    Mar  8 19:52:51  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor fe80::8271:1fff:fec0:3c81 (realm ipv6-unicast ge-0/0/6.0 area 0.0.0.0) state changed from Init to 2Way due to 2WayRcvd (event reason: neighbor detected this router)
    Mar  8 19:52:51  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor 10.7.122.2 (realm ospf-v2 ge-0/0/6.0 area 0.0.0.0) state changed from Init to 2Way due to 2WayRcvd (event reason: neighbor detected this router)
    Mar  8 19:52:51  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor fe80::8271:1fff:fec3:9881 (realm ipv6-unicast ge-0/0/6.0 area 0.0.0.0) state changed from Init to 2Way due to 2WayRcvd (event reason: neighbor detected this router)
    Mar  8 19:52:51  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor 10.7.122.1 (realm ospf-v2 ge-0/0/6.0 area 0.0.0.0) state changed from Init to 2Way due to 2WayRcvd (event reason: neighbor detected this router)
    Mar  8 19:52:51  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor fe80::8271:1fff:fec0:3c81 (realm ipv6-unicast ge-0/0/6.0 area 0.0.0.0) state changed from Exchange to Full due to ExchangeDone (event reason: DBD exchange of master completed)
    Mar  8 19:52:51  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor 10.7.122.1 (realm ospf-v2 ge-0/0/6.0 area 0.0.0.0) state changed from Exchange to Full due to ExchangeDone (event reason: DBD exchange of master completed)
    Mar  8 19:52:55  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor fe80::8271:1fff:fec3:9881 (realm ipv6-unicast ge-0/0/6.0 area 0.0.0.0) state changed from Loading to Full due to LoadDone (event reason: OSPF loading completed)
    Mar  8 19:52:55  SRX240-5 rpd[1093]: RPD_OSPF_NBRUP: OSPF neighbor 10.7.122.2 (realm ospf-v2 ge-0/0/6.0 area 0.0.0.0) state changed from Loading to Full due to LoadDone (event reason: OSPF loading completed)