cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5948
Views
5
Helpful
1
Replies

Error log on CISCO2921

Anyone know ? I found error log on CISCO2921 15.5(1)T2 module on router this below:

- VWIC2-2MFT-T1/E1
- PVDM3-192      

Sep 12 16:50:33: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:50:38.963 BKK: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Sep 12 16:50:43: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:50:49.211 BKK: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/0/0
Sep 12 16:50:49.211 BKK: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 2
Sep 12 16:50:51.471 BKK: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/1
Sep 12 16:50:52: ISDN Se0/0/0:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 1067804184, datasize = 0
Sep 12 16:50:53: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:51:01.719 BKK: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 2 to priority 1
Sep 12 16:51:02: ISDN Se0/0/0:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 1067804184, datasize = 0
Sep 12 16:51:03: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:51:03.979 BKK: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0
Sep 12 16:51:07.731 BKK: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/0
Sep 12 16:51:12: ISDN Se0/0/0:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 1067804184, datasize = 0
Sep 12 16:51:13: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:51:23: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:51:33: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0
Sep 12 16:51:42: ISDN Se0/0/1:15 SERROR: L2_Go: at bailout DLCB is NULL
        L2: sapi 42 tei 102 ces 255 ev 0xFFF
Sep 12 16:51:42: ISDN Se0/0/1:15 SERROR: L2_Go: at bailout DLCB is NULL
        L2: sapi 42 tei 102 ces 255 ev 0xFFF
Sep 12 16:51:43: ISDN Se0/0/1:15 BACKHAUL: handle_mail: received (DL_EST_REQ):
        dest_id = 0, source_id = 3, prim = 200
        priv_ln = 4, int_id = 554158384, datasize = 0

 

  Anyone can suggest?

 

1 Accepted Solution

Accepted Solutions

Manish Gogna
Cisco Employee
Cisco Employee

Hi Jirasak,

The error %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0 basically
means that the IOS placed the primary clock of the router on hold cause the controller E1 0/0/0 went down and that the current clock source signal is out of range, therefore this messages appear when your link goes down but is re-established when the link come up.

The first thing we have to be sure about is that the controller receives a valid clock source signal from your Telco and that you have the correct setting on your controller which must come also from you Telco.

 

Manish

- Do rate helpful posts -

View solution in original post

1 Reply 1

Manish Gogna
Cisco Employee
Cisco Employee

Hi Jirasak,

The error %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0 basically
means that the IOS placed the primary clock of the router on hold cause the controller E1 0/0/0 went down and that the current clock source signal is out of range, therefore this messages appear when your link goes down but is re-established when the link come up.

The first thing we have to be sure about is that the controller receives a valid clock source signal from your Telco and that you have the correct setting on your controller which must come also from you Telco.

 

Manish

- Do rate helpful posts -