Extracted Ticket


Ticket Number  : SUNETTICKET-6476
Ticket Type    : Unscheduled
Ticket Status  : Closed
Ticket Summary : Loss of connectivity - ki-r2
Ticket Scope   : Hardware

Ticket Opened  : 20200710 2:28 UTC
Ticket Closed  : 20200727 14:55 UTC

Problem Start  : 20200710 1:48 UTC
Problem End    : 20200715 15:14 UTC

Affected organisations:

      * SUNET, KI
        ----

Description:

      * FPC0 on router ki-r2 restarted.
        ----

Impact:

      * The following services is affected:
        SU-S002149 	IP - Backbone 	patch tug-r1 <-> tug-r2 	
        SU-S002384 	IP - Backbone 	Backbone ki-r2 - ki-r1 	
        SU-S002385 	IP - Backbone 	Backbone ki-r2 - tug-r1 	
        SU-S003035 	IP - Customer Connection 	IP to KI2 	
        SU-S003569 	MPLS - L2C 	KI sth <-> KI Hongkong MDVPN
        
        Loss of redundancy for KI.
        ----

Update:

      * 20200710 3:08 UTC
        Escalated to provider.
        ----
        
      * 20200710 3:24 UTC
        Router is no longer reachable.
        ----
        
      * 20200710 10:40 UTC
        Router is reachable again after a power cycle of the
        chassis.
        ----
        
      * 20200713 7:12 UTC
        The alarms disappeared after we moved FPC to slot1.
        This points to CB0 being the issue and not the FPC.
        We sent new logs and output to NN/Juniper to analyze.
        ----
        
      * 20200714 7:33 UTC
        Juniper wants us to move back the FPC to slot 0 as they
        think there might be issues with that slot. We asked the
        customer if they can help us again with the move.
        ----
        
      * 20200714 9:04 UTC
        The customer will do the switch at 11:00 UTC today.
        ----
        
      * 20200714 11:24 UTC
        FPC swiched back to slot 0. No alarm observed right now.
        Monitoring.
        ----
        
      * 20200715 15:15 UTC
        Traffic activated back to the router. Monitoring.
        ----
        
        
Final ticket report:

      * FPC had restarted after a transient issue and the issue
        recovered after a re-seat. 
        ----