Carrier Access Access Navigator Manual De Usuario
18-48
August 2003
Access Navigator - Release 1.8
CLI Language Reference
CLI Command List
Read Remote Connections
Purpose:
Displays crossconnections between interfaces inside the remote Access Bank II,
including the T1 connection to the Access Navigator DS1. This command permits the
operator to remotely read the actual Access Bank II crossconnect settings through the
DS1’s CAC FDL management channel.
including the T1 connection to the Access Navigator DS1. This command permits the
operator to remotely read the actual Access Bank II crossconnect settings through the
DS1’s CAC FDL management channel.
NOTE:
All read remote commands require that the remote Access Bank II
is operational and connected to an Access Navigator drop DS1 using Carrier
Access FDL management protocol. If configuration downloading is enabled,
the read remote and show remote settings should be the same.
Access FDL management protocol. If configuration downloading is enabled,
the read remote and show remote settings should be the same.
NOTE:
The read remote commands show the actual settings of the remote
device, while the show remote commands display the settings stored in the
Access Navigator’s data base. Both commands should display the same
settings when remote configuration is enabled so the Access Navigator can
provision the remote Access Bank II.
Access Navigator’s data base. Both commands should display the same
settings when remote configuration is enabled so the Access Navigator can
provision the remote Access Bank II.
Security:
Level 3 (monitor)
Syntax:
read remote <n> connections
Example:
read remote 9 connections
This command produces a message similar to the following. The message shows static
connections between each span and channel as a table, where the span is the interface
and the channel is the DS0.
connections between each span and channel as a table, where the span is the interface
and the channel is the DS0.
NOTE:
An Access Navigator DS1 may connect to either T1 port of the
Access Bank II. The following message example shows that the Access
Navigator DS1 is connected to T1#2 of the Access Bank II, so that T1#1
becomes the T1Drop port. No DS0 channels are currently connected to T1#1.
Navigator DS1 is connected to T1#2 of the Access Bank II, so that T1#1
becomes the T1Drop port. No DS0 channels are currently connected to T1#1.
NOTE:
In the Access Bank II/SDSL, the SDSL port replaces T1#2.
Each row and column represents one end of the connection (row is span, column is
channel). Note that some spans have two rows of channels, with channels 1 to 12 in the
first row and channels 13 to 24 in the second row.
channel). Note that some spans have two rows of channels, with channels 1 to 12 in the
first row and channels 13 to 24 in the second row.
The table entry at the row-column intersection represents the other end of the
connection (span:channel). Each interface name in the first column has a span number
shown in parentheses. For example, FX#2 (4) means the FX#2 is span number 4, so the
entry “4:2” means span 4 channel 2. Table entries with the letters “n/c” have “no
connection.”
connection (span:channel). Each interface name in the first column has a span number
shown in parentheses. For example, FX#2 (4) means the FX#2 is span number 4, so the
entry “4:2” means span 4 channel 2. Table entries with the letters “n/c” have “no
connection.”
In the message example below, row T1#2 (2) and column CH 13 represent span 2
channel 13. The corresponding table entry is “4:1”, which represents span 4 channel 1.
channel 13. The corresponding table entry is “4:1”, which represents span 4 channel 1.
Field
Description
n
DS1 number, 1 to 32.