Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Understanding T1 and E1 Options Exceptions on Circuit Emulation PICs

• bert-algorithm, bert-error-rate, and bert-period options are supported for CT1 or CE1 configurations only.
• framing is supported for CT1 or CE1 configurations only. It is not applicable in SAToP configurations.
• buildout is supported in CT1 configurations only.
• line-encoding is supported in CT1 configurations only.
• loopback local and loopback remote are supported in CE1 and CT1 configurations only.
• loopback payload is not supported. It is not applicable in SAToP configurations.
• idle-cycle-flag is not supported. It is not applicable in SAToP or ATM configurations.
• start-end-flag is not supported. It is not applicable in SAToP or ATM configurations.
• invert-data is not supported. It is not applicable in SAToP configurations.
• fcs32 is not supported. fcs is not applicable in SAToP or ATM configurations.
• timeslots is not supported. It is not applicable in SAToP configurations.
• byte-encoding nx56 is not supported. It is not applicable in SAToP or ATM configurations.
• crc-major-alarm-threshold and crc-minor-alarm-threshold are not supported.
• remote-loopback-respond is not supported. It is not applicable in SAToP configurations.

• bert-algorithm, bert-error-rate, and bert-period options are supported for CT1 or CE1 configurations only.
• framing is supported for CT1 or CE1 configurations only. It is not applicable in SAToP configurations.
• buildout is supported in CT1 configurations only.
• line-encoding is supported in CT1 configurations only.
• loopback local and loopback remote are supported in CE1 and CT1 configurations only. By default, no loopback is configured.
• loopback payload is not supported. It is not applicable in SAToP configurations.
• idle-cycle-flag is not supported. It is not applicable in SAToP configurations.
• start-end-flag is not supported. It is not applicable in SAToP configurations.
• invert-data is not supported. It is not applicable in SAToP configurations.
• fcs16 is not supported in E1 and T1 configurations only.
• fcs32 is not supported in E1 and T1 configurations only. It is not applicable in SAToP configurations.
• timeslots is not supported. It is not applicable in SAToP or ATM configurations.
• byte-encoding is not supported in T1 configurations only. It is not applicable in SAToP configurations. nx56 byte encoding is not supported.
• crc-major-alarm-threshold and crc-minor-alarm-threshold are T1 options supported in SAToP configurations only.
• remote-loopback-respond is not supported. It is not applicable in SAToP configurations.
• If you attempt to configure the local loopback capability on an AT interface (ATM1 or ATM2 intelligent queuing (IQ) interface or a virtual ATM interface on a Circuit Emulation (CE) interface) by including the loopback local statement at the [edit interfaces at-fpc/pic/port e1-options], [edit interfaces at-fpc/pic/port e3-options], [edit interfaces at-fpc/pic/port t1-options], or the [edit interfaces at-fpc/pic/port t3-options] hierarchy level (to define the E1, E3, T1, or T3 physical interface properties) and commit the configuration, the commit is successful. However, local loopback on AT interfaces does not take effect and a system log message is generated stating that local loopback is not supported. You must not configure local loopback because it is not supported on AT interfaces.