SRX

 View Only
last person joined: 4 days ago 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  srx340 : problem with peer bgp

    Posted 30 days ago

    Hello

    i have srx340 , have a problem with neigbor bgp 

    show bgp neighbor 192.168.78.4 
    Peer: 192.168.78.4 AS 65426    Local: 192.168.78.3 AS 65011
      Group: eBGP-VPN-Internet     Routing-Instance: VPN-Internet
      Forwarding routing-instance: VPN-Internet  
      Type: External    State: Active         Flags: <>***************************************************
      Last State: Idle          Last Event: Start
      Last Error: Cease********************************************************************************************
      Export: [ EXPORT-eBGP-VPN-Internet ] Import: [ IMPORT-eBGP-VPN-Internet ]
      Options: <Preference AddressFamily PeerAS Refresh>
      Options: <BfdEnabled>
      Options: <GracefulShutdownRcv>
      Address families configured: inet-unicast
      Holdtime: 90 Preference: 170
      Graceful Shutdown Receiver local-preference: 0
      Number of flaps: 2
      Last flap event: Stop
      Error: 'Cease' Sent: 2 Recv: 0

    what is problem exact and  what is other command show can help expert to check more with me ?

    i wait a reply from expert security and newtork

    best regards



    ------------------------------
    Dhikra Marghli
    ------------------------------


  • 2.  RE: srx340 : problem with peer bgp

    Posted 27 days ago

    Check the syslog for messages mentioning BGP. Usually where 'Cease' is mentioned there will be a little more details explaining why that error was encountered.



    ------------------------------
    Nikolay Semov
    ------------------------------



  • 3.  RE: srx340 : problem with peer bgp

    Posted 20 days ago
    In the absence of any fatal errors (that are indicated in this
       section), a BGP peer MAY choose, at any given time, to close its BGP
       connection by sending the NOTIFICATION message with the Error Code
       Cease.  However, the Cease NOTIFICATION message MUST NOT be used when
       a fatal error indicated by this section does exist.
    
       A BGP speaker MAY support the ability to impose a locally-configured,
       upper bound on the number of address prefixes the speaker is willing
       to accept from a neighbor.  When the upper bound is reached, the
       speaker, under control of local configuration, either (a) discards
       new address prefixes from the neighbor (while maintaining the BGP
       connection with the neighbor), or (b) terminates the BGP connection
       with the neighbor.  If the BGP speaker decides to terminate its BGP
       connection with a neighbor because the number of address prefixes
       received from the neighbor exceeds the locally-configured, upper
       bound, then the speaker MUST send the neighbor a NOTIFICATION message
       with the Error Code Cease.  The speaker MAY also log this locally


    https://www.rfc-editor.org/rfc/rfc4271.html#section-6.7



    this document offciel that i find about Code Cease



    show bgp neighbor 192.168.78.4
    Peer: 192.168.78.4+179 AS 65427 Local: 192.168.78.3 AS 65011
    Group: eBGP-VPN-Internet Routing-Instance: VPN-Internet
    Forwarding routing-instance: VPN-Internet
    Type: External State: Connect Flags: <>
    Last State: Active Last Event: ConnectRetry
    Last Error: Cease
    Export: [ EXPORT-eBGP-VPN-Internet ] Import: [ IMPORT-eBGP-VPN-Internet ]
    Options: <Preference AddressFamily PeerAS Refresh>
    Options: <BfdEnabled>
    Options: <GracefulShutdownRcv>
    Address families configured: inet-unicast
    Holdtime: 90 Preference: 170
    Graceful Shutdown Receiver local-preference: 0
    Number of flaps: 4
    Last flap event: Stop
    Error: 'Cease' Sent: 3 Recv: 0

    what is mean !!


    ------------------------------
    Dhikra Marghli
    ------------------------------



  • 4.  RE: srx340 : problem with peer bgp

    Posted 20 days ago

    If you want to know what actually happened in your case, you must check the SRX logs.

    You can try show log messages but if that doesn't show enough information, you may need to configure more detailed logging.

    Reference: https://supportportal.juniper.net/s/article/SRX-Getting-Started-Configure-System-Logging?language=en_US



    ------------------------------
    Nikolay Semov
    ------------------------------