INDEX OF CONTENTS
1. INTRODUCTION.......................................................................... 1
1.1. CrossLink Description .................................................................................................... 1
1.2. Technical Features .......................................................................................................... 1
1.3. CrossLink Applications .................................................................................................. 1
1.3.1. Digital Cross Connect (DXC) ................................................................................................. 1
1.3.2. E1 Groomer .................................................................................................................................... 2
1.4. Local and Remote Management ..................................................................................... 2
2. INSTALLATION............................................................................. 3
2.1. Package Contents............................................................................................................ 3
2.2. Cables for Connection .................................................................................................... 3
2.3. Installing the Equipment................................................................................................. 3
2.3.1. Ports and Leds Description of Front and Rear Panel .................................................. 3
2.3.1.1. Front Panel....................................................................................................................3
2.3.1.2. Rear Panel.....................................................................................................................4
2.3.2. Connecting to AC or DC Power .......................................................................................... 4
2.3.2.1. AC Power .....................................................................................................................4
2.3.2.2. DC Power .....................................................................................................................4
2.3.2.3. Redundant Power..........................................................................................................5
3. OPERATION ................................................................................ 6
3.1. E1 Link Interface Characteristics ................................................................................... 6
3.2. Transmission clock options ............................................................................................ 6
3.3. Time Slots Routing ......................................................................................................... 6
3.3.1. Time Slot 0 ....................................................................................................................................... 6
3.3.2. Insertion of Management Traffic (NMS) ........................................................................... 6
3.3.3. Content of Output Time Slots ................................................................................................ 7
3.4. Backup Function............................................................................................................. 7
4. CONFIGURATION ...................................................................... 8
4.1. Console Port ................................................................................................................... 8
4.1.1. Terminal Configuration ............................................................................................................. 8
4.1.2. Syntax ............................................................................................................................................... 8
4.1.2.1. SELECT command.......................................................................................................8
4.1.2.2. DIR or LS command.....................................................................................................9
4.1.2.3. GET and SET commands .............................................................................................9
4.1.2.4. SHOW command........................................................................................................13
4.1.2.5. VALIDATE command ...............................................................................................14
4.1.2.6. CLEAR command ......................................................................................................14
4.1.2.7. HELP command .........................................................................................................14
4.2. ViewLink Lite............................................................................................................... 15
4.2.1. Software Installation ................................................................................................................ 15
4.2.1.1. System Requirements .................................................................................................15
4.2.1.2. Installation ..................................................................................................................15
4.2.2. Device Configuration ............................................................................................................. 15
4.2.2.1. CrossLink Main Window............................................................................................16
4.2.2.2. General Management Window ...................................................................................17
6. DIAGNOSTICS .......................................................................... 36
6.1. Loops in E1 Ports.......................................................................................................... 36
6.1.1. Local Loopback 3..................................................................................................................... 36
6.1.2. Local Loopback 2..................................................................................................................... 36
6.1.3. Remote Loopback 2 ............................................................................................................... 36
6.2. PRBS Generation.......................................................................................................... 37
7. TROUBLESHOOTING................................................................. 38
7.1. Frequently Asked Questions......................................................................................... 38
7.2. Return Material Authorization (RMA) ......................................................................... 39
LIST OF FIGURES
LIST OF TABLES
Table 2.1. Indicator leds in front panel .................................................................................................... 4
Table 5.1. System parameters description.............................................................................................. 32
Table 5.2. Temperature parameters description ..................................................................................... 33
Table 5.3. IP parameters description ..................................................................................................... 34
Table C.1. E1 ports connector PIN assignment ....................................................................................... 42
Table C.2. Console port connector PIN assignment ................................................................................ 42
1. INTRODUCTION
1.1. CrossLink Description
CrossLink can be used in different ways and covering multiple applications. The main
ones are detailed on the device application section (see section 1.3).
System is highly scalable by just connecting a new CrossLink in cascade to any FE1
port. In this way, new customers can be added easily from a NOC (Network Operator
Centre).
Based on a host processor running Linux operating system, CrossLink is delivered with an
embedded SNMP Agent and Telnet server for remote management as well as with an
FTP application for software upgrading. Configuration can be done from a text based
interface (local port console or remote Telnet session) or from an intuitive and
comprehensive GUI (locally with Universal Local Manager or via IP with ViewLink
applications).
CrossLink is designed as a standalone unit that can also be rack mounted. Universal
110/230 VAC as well as 24/48 VDC (on demand) power supplies can be supported.
There are also DC versions with redundant power supply availability.
CrossLink can be used as an 8 port digital cross connect system (DXC). By just defining 2
blocks of 4 E1 links, CrossLink can cross connect any 64 Kb/s PCM time slot coming from
one block to any other time slot going out on the other block and vice versa. Flexible
time slot allocation can be remotely arranged as well as any other configuration
parameters using system capabilities.
In figure 1.1 there is an example of traffic cross connection coming from different Base
Stations, in a single E1 frame.
1.3.2. E1 Groomer
CrossLink can be used as a headend or distribution system for a Multi Tenant Unit/Multi
Dwelling Unit (MTU/MDU) application based on E1 transmission technology.
In these type of applications, traffic on single or multiple complete E1 lines coming from
the access provider (LMDS operator, CLECs or cable operator) can be distributed on
the rest of available FE1 ports at rates of nx64 Kb/s as per user’s requirements. HDB3
transmission and coding technology as per ITU G.703 will cover typical distances inside
apartment or office buildings using 4 unconditioned copper wires (regular telephone
cables) without need for additional repeaters. Thus, by just adding an InterLink
interface converter as CPE (Customer Premises Equipment) data services (Frame Relay,
PPP, ...) can be delivered with different interfaces (V.35, X.21, 10BaseT) in a cost
effective way. Like in DXC application, bandwidth allocation per port can be done
remotely from a Telnet session or from ViewLink SNMP Manager application.
CrossLink access device can be locally managed by its serial port using VT100
emulation or higher using GUI (local configuration software), and remotely managed
by Telnet or SNMP using the VAYRIS ViewLink manager. This device is also able to
manage using in-band protocols all the equipment of VAYRIS Link family connected to
its E1/FE1 ports (see chapters 3 and 4).
2. INSTALLATION
2.1. Package Contents
Before installing the CrossLink check the shipping package encloses the following
provided accessories:
• Power cable.
• Serial cable null modem with sub-D9 pin connector for local
configuration.
• CD-Rom containing the Universal Local Manager software.
• CrossLink User Manual.
CrossLink front panel has 10 indicator leds and a turn-on switch as it is shown in the next
figure.
CrossLink
1 2 3 4 5 6 7 8
RT OR T O RT O RT O RT O R T O RT O R T R
PO P P P P P P P ER ON
TURN ON SWITCH
100-240 VAC DC 48V PORT 1 PORT 2 PORT 3 PORT 4 PORT 5 PORT 6 PORT 7 PORT 8
CONSOLE
ETHERNET
E1 Ports
Power Supply Connections
Console Port Ethernet Ports
2.3.2.1. AC Power
Connect the power cable provided to the power supply network and to the device.
Once the switch is turned on, the ON led from the front panel will be lighted.
2.3.2.2. DC Power
DC powered devices have an internal DC/AC converter. The external power supply
connection must be done using the provided cable ended in electrical terminals. The
device internally has a rectifier bridge to avoid polarity troubles. Once this cable is
connected, led ON in frontal panel will be lighted.
This version is available only on demand.
This version is available only on demand. Ask your VAYRIS distributor for more
information.
3. OPERATION
CrossLink is a time slot digital cross connect system that allows cross connection of any
64 kb/s DS0 time slot between any incoming and outgoing E1/FE1 port.
CrossLink E1 link interface meets the requirements of ITU-T Rec. G.703 and G.704 and
supports the CRC-4 option.
The CrossLink E1 link has the 120 ohm balanced line interface terminated in standard
RJ-45 connectors. Line coding is selectable between AMI and HDB3 codes, and jitter
performance complies with the requirements of ITU-T Rec. G.823.
Different clock sources selection provides maximum flexibility in system integration (see
section 4.2.2.1. and 4.2.2.3 to configure it):
• Master Clock: the clock received from the port considered as Master is
considered the system clock. This port is used as a clock source to
transmit the data to all the output ports. In this option, another port can
be configured as a Secondary port in case the Master fails.
• Internal Clock: the device incorporates an internal oscillator that can be
used as the system clock source for all the outgoing E1 links at 2048 KHz
+/- 50 ppm.
CrossLink allows the user to program the connection of each 64 kb/s time slot to any
time slot of the other link. Configuration can be done following the instructions in
chapter 4.
In the output data streams where Time Slot 0 (TS0) is configured as NMS for
management traffic transport, a valid TS0 will be generated inserting NMS traffic in the
spare bits.
If TS0 from one incoming E1 port is mapped into TS0 of an outgoing port, CrossLink will
be transparent, not generating or changing any bit information in this time-slot.
CrossLink will keep a ‘dialog’ with its remote device for each E1 port which has a Time
Slot configured as NMS. This option will only be valid when the remote device has a
compatible in band management, and it is configured with the same NMS Time Slot.
NMS traffic can be inserted into spare bits in TS0 allowing data throughput up to 1984
Kb/s, or mapped directly into any other TS.
Following information can be inserted into the time slots of the outgoing E1/FE1 lines:
• A Time Slot coming from another input port (cross-connection).
• General IDLE pattern (common to all 8 ports).
• Specific IDLE pattern to this Time Slot.
• NMS, in band management traffic.
• A pseudo-random sequence (PRBS) generated internally by the device
to check the quality on the ports when used with some loopbacks.
In the grooming applications where there is one port concentrating all the traffic
coming from different links, a secondary port can also be configured as a backup port
in the device. Then, in case of signal failure in the grooming port, all the traffic in this
port will be redirected to the backup port (see section 4.2.2 to configure it), using the
same cross connection mapping .
Besides, since the backup port is also configured as secondary port, clock reference for
whole system will also be taken from this port, replacing all the original functionality.
4. CONFIGURATION
There are two possibilities to configure CrossLink : via console port (RS 232) or via
Ethernet port. The first possibility, described in section 4.1, needs a terminal emulator
(like HyperTerminal or similar). The second possiblity (described in section 4.2) uses a
friendly GUI that allows an easy configuration by means of ViewLink Lite software,
provided with CrossLink device.
Crosslink device can be locally managed using the serial port located in the rear panel
using a null-modem cable.
4.1.2. Syntax
The console allows to access the device information. This information is saved in a
management database in the device, which is named MIB (Management Information
Base) according to SNMP standards. The MIB has a tree structure and each branch or
node in the tree is identified with a number.
• SELECT
• DIR or LS
• GET
• SET
• SHOW
• VALIDATE
• HELP
By default crosslink is selected. To configure the SNMP Agent, the following command
should be entered:
DIR or LS command shows a list of objects that can be modified for the actual device
selected.
The objects are grouped to clarify their meaning. For example, in Crosslink, DIR
command returns:
SYSTEM:
NAME LOCATION LOCAL_ADDRESS
PORTS:
IDLE G703_CODE(1:8) G703_FRAMING(1:8)
CROSS:
MASTERPORT SECONDARYPORT ISBACKUP REF_CLOCK
P1TS(0:31) P2TS(0:31) P3TS(0:31) P4TS(0:31)
P5TS(0:31) P6TS(0:31) P7TS(0:31) P8TS(0:31)
GET command returns the value for a specified object. The command syntax is as
follows:
SET command assigns a value to the specified object. The command syntax is as follow:
Every object has a set of possible values that can be accessed by get command.
For SET and GET command, the specified object (object_name) must be accessible
from the selected device.
The table below shows the configurable objects for Crosslink, SNMP Agent, Muxlink and
Interlink and their possible values.
- Cosslink:
interval of time-slots with character ‘:’ between first and last time-slot
*** PnTS(a:b) indicates de time-slot source where ‘n’ indicates the port number and ‘a’
- SNMP Agent:
- Interlink:
- Muxlink:
SHOW command shows a group of objects of the device. The syntax command is as
follows:
The show_options are different depending if the device is already selected or not.
SHOW STATE: shows if device is linked, looped, and system information and value of
circuits and leds.
SHOW PORTS: shows the values of the objects related to the ports of the device.
SHOW STATS: shows the total statistics objects.
SHOW PROFILES: shows the nine possible default values that can be set.
SHOW PARAMETERS: shows the ip parameters of SNMP Agent. The same information is
displayed if only SHOW is entered.
VALIDATE command allows to set default values, recovery the last values saved or
validate the changes.
For Interlink there are different options for the default values :
VALIDATE DEFAULT1
VALIDATE DEFAULT2
...
VALIDATE DEFAULT9
The profiles set with these commands are showed with the command SHOW PROFILES
If Agent is selected VALIDATE has no parameter and it saves the configuration and
restart de agent, so the communication with the console ends until the agent inits
again.
CLEAR command allows to set to zero all the ports statistics counters. The syntax
command is as follow:
CLEAR PORT1
CLEAR PORT2
…
CLEAR PORT8
CLEAR ALL
‘Clear all’ sets to zero all 8 ports statistics counters also the time on object. Therefore,
clear port1 to port 8 set to zero the specific port statistics counters but the time on
object is not set to zero.
If Interlink either Muxlink is selected CLEAR command does not need any parameter, so
the command syntax is as follow:
HELP command shows information about configurable objects and commands. With no
parameter it shows all commands that can be executed.
ViewLink Lite is a GUI application running on Windows or UNIX OS. It can be used to
configure and manage CrossLink device through the Ethernet port located in the rear
panel.
Connect the PC where the software is going to be installed to the Ethernet port of the
CrossLink using a null-Ethernet cable (with the pinout 1-3, 2-6, 3-1, 6-2). The CrossLink has
the following default IP address: 192.168.46.232. Configure the PC with an IP address in
the range of 192.168.46.X (for example 192.168.46.10) different than the CrossLink IP
address.
To check that the connection has been done correctly, open a MS-DOS session in the
PC and ping the CrossLink with the following command:
ping 192.168.46.232 –t
If the CrossLink doesn’t reply, please check the null-Ethernet cable and the IP
parameters of the PC.
4.2.1.2. Installation
Launch the ViewLink Lite application. Click with the right-button of the mouse on the
“Manager” icon located on the left side of the window. Select the option “Add SNMP
session”, and enter the IP address of the CrossLink (the first time, it should be the
default one, 192.168.46.232) and click on “Apply” button. A window similar to the shown
in Figure 4.1 should be displayed.
In the figure above there is a graphical representation of the CrossLink device, its eight
E1 ports, and also the remote devices connected to the ports.
In next paragraphs there are all the options and elements available in this window.
• CrossLink: Central rectangle in the screen represents CrossLink device. Inside the
rectangle you can see information related to the name and location of the device
(both parameters can be modified clicking with the mouse over each of the text fields).
There are also two buttons inside the CrossLink box: one for the CrossLink configuration
slots and the other for the CrossLink SNMP Agent parameters. Finally, with a mouse click
over the device image, the main window of management information will be
displayed. With the mouse right button over the CrossLink image you can also get a
popup menu with links to the windows and options of the device.
• E1 ports: The ports of the device are represented by 8 connections numbered from
1 to 8. The colour of each connection indicates the port state, according to the next
codification:
If you put the mouse over the line representing each port and press mouse right
button, you will see a popup menu to configure the next port parameters:
1. Master: defines which E1 port is considered as Master, and from which the
reference clock is taken. Once assigned, a "Master" label appears close to the
corresponding port.
2. Secondary: defines the E1 port from which the reference clock is taken in case
that E1 Master is lost. Once assigned, a "Secondary" label appears beside the
corresponding port.
3. Backup: defines if the secondary E1 port is also working as backup. In this case,
this E1 is going to take the role of Master for reference clock and Time-Slots.
Once assigned, a "Backup" label appears beside the corresponding port.
4. Active / Not active: defines if you want to use or not the selected port. If the E1
port is disabled, the device will generate AIS in the output port, to inform
possible remote devices.
5. Configuration / Alarms / Statistics: Opens the corresponding windows for the
selected E1 port.
6. Config slots E1: Opens the slots configuration window showing only the
connections for the selected port.
• Remote devices: In the end of each port, it is represented the remote device
connected to the ports in the CrossLink. If the remote device is a VAYRIS device, an
icon will be displayed indicating what kind of device it is. If it is not a VAYRIS one, an
unknown device icon will be displayed. For VAYRIS devices, if you click with the mouse
over the device icon, the specific main window for that device will be displayed, and
you will be able to manage and configure it from the CrossLink using in band NMS
protocol.
In this window you can see all the different aspects of CrossLink management and E1
port management. The left side of the window shows specific information about
CrossLink device, while the right side shows E1 ports information buttons and a selection
box with the 8 E1 ports.
The specific management objects for the CrossLink can be divided in next categories:
1. Validate changes: all the changes made during the session will be
validated in the CrossLink, and all the previous values will be deleted.
2. Last values: gets the values stored previously to the last change.
3. Default values: gets the values by default set by the manufacturer.
Besides these port buttons, in the left, there is a port selection box. If you select more
than one port, the changes you make in the next window will be applied for all
selected ports.
In this window you can get general information about the system and other
parameters. The window is divided in four parts:
4.2.2.4. Alarms
In this window the alarms of CrossLink can be programmed; the configuration for port
specific alarms can be made in another window. The window is divided into two parts:
• In the upper part, you can set the type of alarms that the CrossLink will send:
Fault&Progress, Major Alarms, All of them, None; that is to say the priority to give to
those alarms. For example, if the priority is “Fault&Progress”, the agent will exclusively
send the alarm set as “Minor Alarm”, not taking in account the rest of the alarms.
• In the lower part of the window, you can set up each alarm individually. Permission
to sent alarm, Alarm priority, and threshold upon which the alarm is activated. You will
also find here the following information: whether an alarm is activated or not, and how
long it has been activated. The Time Reset button initialises the time counter of the
selected alarm and initialises its counter of events. That is to say that if 45 error seconds
have been counted since the last time the error seconds counter was initialised, and
the alarm gets activated, the usual procedure is to attend it and click on the Time Reset
button to initialise the counter again.
• Temperature Out: Alarm gets activated when the number of times that the
temperature of the Converter overpasses the limit is detected is higher than the
established one, which is 0 per defect so that the first time that the temperature of the
unit overpasses this limit, the alarm gets activated.
• Possible configuration loss: Alarm gets activated when the number of times that a
possible configuration loss is detected is higher than the threshold, which is 0 per defect
so that the first time that a possible configuration loss is detected, the alarm gets
activated.
• Application Error: Alarm gets activated when device is executing from BOOT (only
for those devices with firmware download option activated).
• Remote_Loopback_2: Alarm gets activated when the number of times that a
remote loopback 2 is detected is higher than the established one, which is 0 per defect
so that the first time that a remote loopback is detected, the alarm gets activated. For
loopback alarms, the source is not specified.
• Local_Loopback_2: Alarm gets activated when the number of times that a local
loopback 2 is detected is higher than the established one, which is 0 per defect so that
the first time that a local loopback is detected, the alarm gets activated. For loopback
alarms, the source is not specified.
• Local_Loopback_3: Alarm gets activated when the number of times that a local
loopback 2 is detected is higher than the established one, which is 0 per defect so that
the first time that a local loopback is detected, the alarm gets activated. For loopback
alarms, the source is not specified.
4.2.2.5. Diagnostics
In this screen you can activate loopbacks and BERT measures for the CrossLink.
Loopbacks have no memory, they are activated in real time. When a reset is made in
the device, it loses all loopbacks. For more information about Loops, see chapter 6 of
Diagnostics.
In this window you can check and configure the parameters that define each of the
eight E1 ports in the CrossLink.
• Line Code. It specifies the line code for data transmitted and received: AMI or
HDB3.
• Frame Format. Frame format as per ITU G.704. Possible values are: PCM31, PCM31C
& FAS/NFAS.
• Impedance. Fixed to 120 Ohm balanced.
• Protocol bits. Number of management bits in a NMS slot (Fixed to 8 bits).
• Bit position. The position of the least significant bit of the management protocol
(NMS) inside a frame interval.
In this window, you can configure those alarms specific for each of the 8 ports in
CrossLink. All changes made will be applied on ports previously selected for this
window. The available alarms are as follows:
• Signal Loss: Alarm gets activated when the signal in the E1 port is lost more times
than the threshold. Default threshold is o, so first time that the signal drops the alarm
is activated.
• CRC Error: Alarm gets activated when the number of times that CRC Errors are
detected is higher than the threshold.
• LCV (Line Code Violations) Error: Alarm gets activated when the number of times
that Line Code Violations are detected is higher than the threshold.
This window shows the statistics in selected E1 port as per ITU G.821. It is divided in two
parts. In the left one the total accumulated statistics are shown, and in the right part
you will find the statistics of the current time interval. The time intervals are 15 minutes
long (900 seconds).
• Time ON: Measures the time the CrossLink has been switched ON (in seconds).
• Time interval: Current time (in seconds) from current interval (maximum of 900
seconds for 15”).
• LL (Lost Links): Number of lost links.
In this window you can configure time slot mapping for the 8 E1 ports in the CrossLink
using mouse options (as drag&drop, right button,...). In the next paragraphs several
configuration procedures are described.
1. Drag mouse from source slot and drop in destination slot. The connection made is
bidirectional, so if you assign slot 1-1 to slot 2-2, automatically is also assigned slot 2-
2 to slot 1-1.
2. To verify the connection, you can roll the mouse over one of the slots and you will
see a line drawn between them. The text of the slot button must change from "n/a"
(not assigned) to the identifier ("E1-slot") of the source/destination slot.
or
1. With the mouse situated besides (not over) the E1, click mouse and roll over E1 until
desired slots are selected.
2. Drag mouse (from initial slot) and drop to its sink position.
• Activate/deactivate an E1
1. Put the mouse over the upper button for the E1 you want to activate/deactivate.
2. Press mouse right button. A menu with four options will appear.
3. Press "Activate" button from menu in order to E1 change its state.
4. If you want to activate all E1s at the same time, repeat the previous steps but
opening the menu, directly over the window foreground instead of over any E1
upper button.
• View/hide an E1.
1. Put the mouse over the upper button for the E1 you want to view/hide.
2. Press mouse right button. A menu with four options will appear.
3. Press "View" button from menu in order to E1 appears (if it is hidden) or to E1 hides (if
it is viewed)
4. If you want to activate all E1s at the same time, repeat the previous steps but
opening the menu, directly over the window foreground instead of over any E1
upper button.
• Show E1 connections.
1. Put the mouse over the upper button for the E1.
2. Press mouse right button. A menu with four options will appear.
3. Press "Connections" button from menu. You will see slot connections for that E1, so
E1s with no slots assigned to that one won't be shown in the screen.
4. If you want to activate all E1s at the same time, repeat the previous steps but
opening the menu, directly over the window foreground instead of over any E1
upper button.
• Delete E1 connections.
1. Put the mouse over the upper button for the E1.
2. Press mouse right button. A menu with four options will appear.
3. Press "Disconnect" button from menu in order to delete all connections for that E1.
4. If you want to activate all E1s at the same time, repeat the previous steps but
opening the menu, directly over the window foreground instead of over any E1
upper button.
IMPORTANT : The configuration changes made in this window are not loaded in the
device until you press the option File->Save in the window menu bar. If you want to
save the changes as permanent in the device, you must validate them in the device
(from CrossLink main management window or from the device popup menu in main
window for the CrossLink).
The items in the menu bar for this window are described below:
• File menu
• Edit menu
Undo: undo the last action applied on slots for this window.
Redo: redo the last action applied on slots for this window.
• Help menu
5. REMOTE MANAGEMENT
5.1. SNMP Management
CrossLink device includes an embedded SNMP agent. This agent enables the remote
management via SNMP protocol for the own device parameters and also for the xLink
(VAYRIS) devices connected to the E1 ports of CrossLink. The ViewLink SNMP manager
provides an easy and intuitive way to manage CrosLink and its ports with the same GUI
as ViewLink Lite application (see section 4.1.2.)
CrossLink SNMP Agent is delivered with the factory default IP Address 192.168.46.232. In
order to configure IP parameters of the agent with the ViewLink Lite software or
following the next steps:
1) Open a telnet session to the agent: telnet 192.168.46.232
2) You will be asked for login and password. Enter the following:
login: root
password: vayris
3) Type: telnet localhost 23000
4) Now you should see the message : Connected to 192.168.46.232 and the operating
system prompt (CROSSLINK>)
5) You must type the following commands:
> select agent
6) In order to change any parameter in the table (type ‘DIR’ to see them), you have to
type:
> set parameter_name value
For example, to set the SNMP Agent IP address to 10.0.1.25, you should type:
> set agentip 10.0.1.25
For syntax information on the different objects please refers to 4.12.3 section.
ViewLink management application enables managing more than one SNMP Agent at
the same time, because it provides a set of tools to add several SNMP sessions with the
IP addresses corresponding to Vayris agents. This set of tools are available from the
application control panel (or session manager) located in the left side of the screen. All
options for this panel are described in next paragraphs.
On the left side of the application you can see a control panel. This panel is tree
structured with all the managed elements in the network as branches. With this panel
you can add and delete SNMP agents, also open and close a serial session. Moreover
the tree structure enables to view in an easy way the elements managed by each
agent and also provides tools to go directly into device management windows.
We are going now to describe each level that integrates the tree, and also each one
of the available actions for them (accessible from popup menus with mouse right
button).
Manager
This is the tree root node, and all agents and manageable devices depend on it. The
menu associated with the root node contains the next options:
SNMP Session
It is represented with a VAYRIS SNMP Agent icon and its release number. On the right
hand of this icon the agent IP address is specified. If the SNMP Agent belongs to a
CrossLink device, the next tree level will represent a CrossLink with sub-levels
corresponding to its ports and different windows. If it is not a CrossLink Agent, the next
tree level will represent a rack with sub-levels corresponding to rack positions. The menu
options for this tree level are listed next:
Serial Session
It is represented with a serial COM port icon, specifying the session port (COM1, COM2,
COM3, COM4). If you are managing both a CrossLink device or any other VAYRIS
device or set of devices, the next tree level for this type of node is represented by a
rack structure. The menu options for this tree level are listed next (these options are also
accesible with the ULM software):
• Automatic polling.
• Timeouts.
• Timeout.
• Window refresh time.
• Refresh windows.
• Serial port.
• Expand racks with devices.
• Delete empty racks.
• Number of racks.
• Close session.
CrossLink SNMP management using ViewLink has the same GUI as described with local
serial management using ULM. Therefore, all parameters explained in section 4.2.2 can
be configured in ViewLink application. The only difference is the agent configuration
window, which does not appear in serial management. Access to this window can be
done in two ways:
1. Using “Config Agent” button of the CrossLink main window (figure 4.1). This button is
inside the icon which represents the device.
2. Using the option “Open management window” of the popup menu in the left control
panel (figure 5.1). These menus appear by clicking right button of the mouse located
on the SNMP agent icon which has to be configured.
5.1.2.2.2. Temperature
The SNMP has a sensor to monitor the temperature of the device. In this window we can
see the following elements:
5.1.2.2.3. IP Addresses
or
• telnet x.x.x.x
(where x.x.x.x is the CrossLink SNMP Agent IP address)
Once you have opened the console session, the way to manage the device is the
same than the one described in port console paragraph (see 4.1 to learn about the
syntax and list of manageable objects).
6. DIAGNOSTICS
6.1. Loops in E1 Ports
The loops of CrossLink don’t have memory. In other words, Once the device is turned
off, it loses the memory of the configured loops, and it always starts-up with no loops
programmed.
The device will execute the loops when these are programmed and one each time. It is
not necessary to validate the changes to activate a loop.
In the following sections there are the descriptions of the different types of loops. All the
loops must be activated using local management software (see Diagnostics part in
Device Configuration section, 4.2.2.5).
When this loop is being done, as it its shown in figure 6.1, all data transmitted out
through the selected port is routed again inside the CrossLink.
In this case, CrossLink returns to the selected E1 port all the data coming into the same
port.
This loopback function can be activated using another option: If the device is
connected to a remote CrossLink, the first one will do the loopback 2 if the remote one
is configured with Remote Loopback 2 option, explained below.
the remote device will return all the data sent by the first CrossLink using the selected E1
port.
The device is able to generate and measure a pseudo-random binary sequence. The
BERT must be configured using management software (see Diagnostics section of the
Device Configuration part, 4.2.2.5). There is the possibility to configure both port and
Time Slot. Once the option is activated, CrossLink will start generating a known
sequence, and ‘listening to’ the port searching for this sequence. Once synchronized,
CrossLink is able to count the errors detected in the incoming sequence in order to
measure the quality of the E1 links.
7. TROUBLESHOOTING
Question 1- I have configured the CrossLink but after a reset the configuration was lost.
How can I avoid this?
Answer 1- After making any change in the configuration of the device, it is necessary to
validate it (see section 4.2.2.2 General Management Window).
Question 4- I have several fractional E1 links with PCM30 frame format and signalling in
time-slot 16. Is it possible to join them in a single E1 with CrossLink?
Answer 4- No. CrossLink performs a time-slot cross-connection, , so any bit-level
multiplexing feature is not implemented.
Question 6- How can I configure the IP address of the SNMP agent in order to manage
via IP the CrossLink?
Answer 6- Please refer to section 5.1.1 SNMP Agent Configuration.
Question 7- I haven’t any data analyser to test the link. Is there any functionality to do
it?
Answer 7- Yes. CrossLink has an in-built PRBS (pseudo random binary sequence)
generator (see section 4.2.2.5 Diagnostics for configuration). You just have to select the
E1 port that you want to test and one time-slot to carry the PRBS. After this, you should
make a loopback in the remote site to take the PRBS back to the CrossLink (see
chapter 6. Diagnostics).
Please refer to our web site for the latest FAQs version.
When returning the device for warranty work, a return material authorization (RMA)
number must be obtained from VAYRIS S.A. technical support service at e-mail address
/ fax / phone below:
E-mail: support@vayris.es
Phone: +34 93 582 02 01
Fax: +34 93 582 02 52
E1 interface
Physical: as per ITU G.703
Frame format: FAS/NFAS, PCM31, PCM31C
Jitter: as per ITU G.823
Line code: AMI or HDB3
Rates: 2048 Kb/s ± 50 ppm
Transmission clock: a single master clock for all E1/FE1 ports must be provided. Internal
or slave.
Connector: RJ-45
Impedance: 120 ohm
Diagnostics
Local (LAL) and remote (RDL) loops on each individual port, PRBS at DS0 Time Slot level
Management
Local: Console port: RS-232 (9600 8N1)
Universal Local Manager (Windows)
Connector: sub-d, 9 pin
Remote: Embedded SNMP Agent (MIB available)
Telnet Server
Connector: RJ-45, Ethernet 10/100 Base-T
Power supply
Internal: 230 VAC, (5/12/24/48 VDC on demand)
Dimensions: 340 mm x 274 mm x 60 mm
Weight: 2900 g
Temperature
0 ° a 60 °C (non condensing)
E1 Configuration
All the Time-Slots from port 1 to 5 and vice-versa
All the Time-Slots from port 2 to 6 and vice-versa
All the Time-Slots from port 3 to 7 and vice-versa
All the Time-Slots from port 4 to 8 and vice-versa
RS485 Configuration
Time between polling: 500 ms
Polling ratio: 3
RS485 bus statistics: Enabled
Local timeout: 200 ms
Remote timeout: 500 ms
Retries= 1
General Parameters
Number of racks: 1
Number of devices: 16
Communication type: VIEW
Agent type: 3 (standalone)
Memory: 0
Timeout : 10
Version : 3
Modifiable : 1
IP Configuration
SNMP Agent IP Address: 192.168.46.232
Subnetmask: 255.255.255.0
Nms1 IP Address: 10.0.1.152
Nms2 IP Address: 10.0.1.41
PIN SIGNAL
1 TTIP(OUT)
2 TRING(OUT)
4 RTIP(IN)
5 RRING(IN)
Table C.1. E1 ports connector PIN assignment
PIN SIGNAL
1 DCD(109)
2 RXD(104)
3 TXD(103)
4 DTR(108)
5 GND
6 DSR(107)
7 RTS(105)
8 CTS(106)
9 ---
Table C.2. Console port connector PIN assignment
PIN SIGNAL
1 TX+(OUT)
2 TX-(OUT)
3 RX+(IN)
4
5
6 RX-(IN)
7
8
Table C.3. Ethernet port connector PIN assignment