Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

E1 Configuration with Clock Source Internal

Today I have faced very strange problem when configuring the E1 link between my central site and remote site.

On central site I was continuously getting the Link UP and Link Down message on one configured E1. I tried to configure everything like framing, linecode etc but behaviour was same.

At the time when i was getting this message on my Central Site Router,no message was occured on Remote Site Router. Lateron somehow i changed the Clock Source of Remote Router from Line to Internal. The Link UP and Link Down message disappears and I got the IP Connectivity as well.From this it looks like that somehow there was problem in Remote Site E1 Connection that he was not getting the Clock from Line but strange thing was that no message appears on Router Console for such problem.

Now even the links are configured and I have the IP Connectivity as well but the still I am getting the Link UP and Link DOWN messages on my central site Router on E1 Controller Interface. Also the ping results are not always the 100%.

Is this can be the problem from the Telco Provider as well?

7 REPLIES
Community Member

Re: E1 Configuration with Clock Source Internal

This sounds like the Telco has not set the Clock on its NTU. double check with them on this point.

Clock source internal should really only be used for back to back connections.

Cheers/

Community Member

Re: E1 Configuration with Clock Source Internal

I am checking with the Telco provider, In the mean time, is there any why to run debug on e1 controllers..

thanks

Community Member

Re: E1 Configuration with Clock Source Internal

Following is the message i received whenever connect the cable to E1 interface of the Router.

*Mar 1 00:18:52.163: E1T1 0/0 FW: alm1:02 p:00 LOF

*Mar 1 00:18:52.163: E1T1 0/0 FW: e1_state_up going to e1_state_rlof_integ p:0

0

*Mar 1 00:18:52.163: E1T1 0/0 FW: cfg: clock: int/line

*Mar 1 00:18:52.163: E1T1 0/0 FW: set clocking E1, TE, Internal

*Mar 1 00:18:52.163: E1T1 0/0 FW: set clocking E1, TE, Looped-Timed

*Mar 1 00:18:52.163: E1T1 0/0 FW: Clocking change: MASTER PORT:01

*Mar 1 00:18:52.163: E1T1 0/0 FW: alm1:12 p:00 AIS LOF

*Mar 1 00:18:52.187: E1T1 0/0 FW: alm1:52 p:00 YEL AIS LOF

*Mar 1 00:18:52.275: E1T1 0/0 FW: CERR: 00

*Mar 1 00:18:52.275: E1T1 0/0 FW: MERR: 00

*Mar 1 00:18:52.275: E1T1 0/0 FW: FERR: 00

*Mar 1 00:18:52.275: E1T1 0/0 FW: dsx1[00] --UP-- RAIS

*Mar 1 00:18:53.275: E1T1 0/0 FW: JERR: 00

*Mar 1 00:18:53.275: E1T1 0/0 FW: MERR: 00

*Mar 1 00:18:53.275: E1T1 0/0 FW: FERR: 00

*Mar 1 00:18:53.275: E1T1 0/0 FW: Port: 00 RENEG_SHORT_HAUL: 13

*Mar 1 00:18:53.275: E1T1 0/0 FW: dsx1[00] --UP-- RAIS RLOS

*Mar 1 00:18:53.275: E1T1 0/0 FW: cfg: clock: line/line

*Mar 1 00:18:53.275: E1T1 0/0 FW: set clocking E1, TE, Looped-Timed

*Mar 1 00:18:53.275: E1T1 0/0 FW: set clocking E1, TE, Looped-Timed

*Mar 1 00:18:53.275: E1T1 0/0 FW: Clocking change: MASTER PORT:00

*Mar 1 00:18:53.275: E1T1 0/0 FW: cfg: clock: line/line

*Mar 1 00:18:53.279: E1T1 0/0 FW: set clocking E1, TE, Looped-Timed

*Mar 1 00:18:53.279: E1T1 0/0 FW: set clocking E1, TE, Looped-Timed

*Mar 1 00:18:53.279: E1T1 0/0 FW: cfg: clock: int/line

*Mar 1 00:18:53.279: E1T1 0/0 FW: set clocking E1, TE, Internal

*Mar 1 00:18:53.279: E1T1 0/0 FW: set clocking E1, TE, Looped-Timed

*Mar 1 00:18:53.279: E1T1 0/0 FW: Clocking change: MASTER PORT:01

*Mar 1 00:18:53.291: E1T1 0/0 FW: alm1:12 p:00 AIS LOF

*Mar 1 00:18:53.315: E1T1 0/0 FW: alm1:52 p:00 YEL AIS LOF

*Mar 1 00:18:54.275: E1T1 0/0 FW: JERR: 00

*Mar 1 00:18:54.275: E1T1 0/0 FW: MERR: 00

*Mar 1 00:18:54.275: E1T1 0/0 FW: FERR: 00

*Mar 1 00:18:54.275: E1T1 0/0 FW: dsx1[00] --UP-- RAIS

*Mar 1 00:18:54.627: E1T1 0/0 FW: rlof timer expired p:00

*Mar 1 00:18:54.627: E1T1 0/0 FW: e1_goto_rlof p:00

*Mar 1 00:18:54.627: E1T1 0/0 FW: Controller_DOWN p:00

*Mar 1 00:18:55.275: E1T1 0/0 FW: dsx1[00] -DOWN- RAIS RLOF

*Mar 1 00:18:55.519: %CONTROLLER-5-UPDOWN: Controller E1 0/0, changed state to

down (AIS detected)

*Mar 1 00:18:57.519: %LINK-3-UPDOWN: Interface Serial0/0:1, changed state to do

wn

The link is continuously going up and down. The quick response will be highly appreciable.

Community Member

Re: E1 Configuration with Clock Source Internal

What i can see:-

*Mar 1 00:18:52.163: E1T1 0/0 FW: Clocking change: MASTER PORT:01

*Mar 1 00:18:53.275: E1T1 0/0 FW: Clocking change: MASTER PORT:00

Please go through

http://www.cisco.com/en/US/docs/ios/12_2/dial/command/reference/drfchcp.html#wp1056117

For clock source line

Check and revert

***************************************

RATE USERFUL POST

***************************************

Community Member

Re: E1 Configuration with Clock Source Internal

I already have checked this thing. In my setup, the E1 is used primarily for Data Network and it is not configured as PRI.

Somehow now the E1 controller is up but the path code violations are generated a lot as well as if i see the corresponding Serial Interface the CRC errors are increasing very rapidly.

Hall of Fame Super Gold

Re: E1 Configuration with Clock Source Internal

Usually these are symptoms of faulty circuit. Post "show controllers e1".

Community Member

Re: E1 Configuration with Clock Source Internal

the problem has been resolved. At the end on the remote site, the problem was the grounding of Cisco router with transmission equipment.

Thanks all for your comments and help.

671
Views
0
Helpful
7
Replies
CreatePlease to create content