Controller E1 down
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2015 06:11 AM - edited 03-17-2019 02:35 AM
Bonjour,
J'ai ce bug pour activer ma carte E1 et continuer les test sur la SDA
E1 0/0/0 is down.
Applique type is Channelized E1 - balanced
Transmitter is sending TS16 LOMF Alarm.
Receiver has loss of multi-frame in TS16.
alarm-trigger is not set
Version info FPGA Rev: 08121917, FPGA Type: PRK4
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 11111
Data in current interval (283 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 283 Unavail Secs
Total Data (last 8 15 minute intervals):
3173 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 5 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 7200 Unavail Secs
Merci pour votre retour
Thanks for your reply to activate the controller
- Labels:
-
Other IP Telephony

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2015 06:13 AM
You will probably get a better response if your post is in English. The best I can do with the output shown is provide this link:
https://supportforums.cisco.com/discussion/9547871/receiver-has-remote-ts16-lomf-alarm-e1-interface-3745
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2015 06:33 AM
Please i have this bug in my E1 controller. I install and configure my E1 card plug in the E1 of my operator to receive signal for SDA.I need help to troubleshoot this error message.
E1 0/0/0 is down.
Applique type is Channelized E1 - balanced
Transmitter is sending TS16 LOMF Alarm.
Receiver has loss of multi-frame in TS16.
alarm-trigger is not set
Version info FPGA Rev: 08121917, FPGA Type: PRK4
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
International Bit: 1, National Bits: 11111
Data in current interval (283 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 283 Unavail Secs
Total Data (last 8 15 minute intervals):
3173 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 5 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 7200 Unavail Secs
Thanks for your reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2015 06:40 AM
Check your framing. The link I provided shows a common set of issues with this alarm. You could try :
framing no-crc4
under your E1 controller and see if it clears up. You might need to contact your provider to see what they have set on their end versus what you have. A mismatch will cause these issues so the command I provided may or may not help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2015 11:13 AM
Thanks Brandon for your reply.
Please, which king of Cable do i use with VWIC3-4MFT-T1/E1 to interconnect with 4E1/E1+100M PDH Multiplexer converter in the client side (my side).
I use E1 cable or strainght cable but the E1 interface is not physically UP and my provider cannot see my cisco gateway.
Please let me know how can i do.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2015 11:32 AM
If the E1 interconnect to the 4E1/E1+100M PDH is another E1 interface you will need a crossover cable much like connecting a T1 card to another T1 card. I'm not familiar with E1 multiplexers since everything I work with is either not multiplexed due to a single T1 or is SIP.
This thread may help if that is indeed the issue:
https://supportforums.cisco.com/discussion/9937446/e1-e1-connection-crossover-cable
Again, that is out of my realm of knowledge. The demarc is where I always stop so beyond the gateway I couldn't tell you much.
