•
Use to place a remote device, connected at the T1 over T3 layer, in loopback.
•
Specify one of the following options:
•
line fdl ansi
—Sends a repeating 16-bit ESF data link code word (00001110 11111111)
to the remote end requesting that it enter into a network line loopback. Specify the
ansi keyword to enable the remote line FDL ANSI bit loopback on the T1 line, according
to the ANSI T1.403 specification.
•
line fdl bellcore
—Sends a repeating 16-bit ESF data link code word (00010010
11111111) to the remote end requesting that it enter into a network line loopback. Specify
the bellcore keyword to enable the remote line FDL Bellcore bit loopback on the T1
line, according to the Bellcore TR-TSY-000312 specification.
•
payload
[
fdl
] [
ansi
]—Sends a repeating 16-bit ESF data link code word (00010100
11111111) to the remote end requesting that it enter into a network payload loopback.
Enables the remote payload FDL ANSI bit loopback on the T1 line. You can specify
fdl
or
ansi
.
•
Example
host1(config-controll)#
path 12 ds3 2 t1 14 loopback remote payload
•
Use the
no
version to send the 16-bit ESF data link code word to deactivate the loopback
at the remote end, depending on the last activate request sent to the remote end.
•
See path ds3 t1 loopback.
path ds3 t1 remote-loopback
•
Use to enable the router to accept remote loopback requests from a remote device
connected at the T1 over T3 layer.
•
Example
host1(config-controll)#
path 12 ds3 2 t1 14 remote-loopback
•
Use the
no
version to restore the default, which is to reject remote loopback requests.
•
See path ds3 t1 remote-loopback.
Testing Connectivity
Use the
path overhead j1
command to check for connectivity between the router and a
SONET/SDH device at the other end of the line. This command defines:
•
A message that the router sends from the specified interface to the SONET/SDH device
at the other end of the line.
•
A message that the router expects to receive on the specified interface from the
SONET/SDH device at the other end of the line.
When you define a message that the interface sends, you must monitor receipt of that
message at the remote end.
Copyright © 2010, Juniper Networks, Inc.
146
JunosE 11.2.x Physical Layer Configuration Guide
Summary of Contents for JUNOSE 11.2.X MULTICAST ROUTING
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x Physical Layer Configuration Guide...
Page 16: ...Copyright 2010 Juniper Networks Inc xvi JunosE 11 2 x Physical Layer Configuration Guide...
Page 24: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x Physical Layer Configuration Guide...
Page 66: ...Copyright 2010 Juniper Networks Inc 44 JunosE 11 2 x Physical Layer Configuration Guide...
Page 228: ...Copyright 2010 Juniper Networks Inc 206 JunosE 11 2 x Physical Layer Configuration Guide...
Page 247: ...PART 2 Index Index on page 227 225 Copyright 2010 Juniper Networks Inc...
Page 248: ...Copyright 2010 Juniper Networks Inc 226 JunosE 11 2 x Physical Layer Configuration Guide...