User Manual
Table Of Contents
- 1. Getting started
- 2. Introduction
- 3. Preparation
- 4. About the terminal
- 5. Mounting and installing the terminal
- 6. Connecting to the terminal
- 7. Managing the terminal
- 8. Configuring the terminal
- 9. Configuring the traffic interfaces
- 10. Cross Connections
- Embedded cross connect switch
- The Cross Connections application
- The Cross Connections system requirements
- Installing the Cross Connections application
- Opening the Cross Connections application
- The Cross Connections page
- Setting the terminal's address
- Management and user ethernet capacity
- Setting card types
- Getting cross connection configuration from the terminals
- Creating cross connections
- Sending cross connection configuration to the terminals
- Saving cross connection configurations
- Using existing cross connection configurations
- Printing the cross connection configuration
- Deleting cross connections
- Configuring the traffic cross connections
- Cross connection example
- Symmetrical Connection Wizard
- 11. Protected terminals
- 12. In-service commissioning
- What you will need
- Checking the antenna polarization
- Visually aligning antennas
- Accurately aligning the antennas
- Synchronizing the terminals
- Checking performance
- Checking the receive input level
- Checking the fade margin
- Checking long-term BER
- Bit Error Rate tests
- Additional tests
- Checking the link performance
- Viewing a summary of the link performance
- What you will need
- 13. Maintenance
- 14. Troubleshooting
- 15. Interface connections
- 16. Alarm types and sources
- 17. Country specific settings
- 18. Specifications
- Ethernet interface
- QJET Quad E1 / T1 interface
- Q4EM Quad 4 wire E&M interface
- DFXO Dual foreign exchange office interface
- DFXS Dual foreign exchange subscriber interface
- QV24 Quad V.24 asynchronous data interface
- HSS Single high speed synchronous data interface
- External alarm interfaces
- Auxiliary interfaces
- AC Power supply
- DC Power supply
- Power consumption
- MHSB protection
- Ethernet interface
- 19. Product end of life
- 20. Abbreviations
- 21. Acknowledgments and licensing
- 22. Commissioning Forms
- 23. Index
Connecting to the terminal | 42
Connecting to the terminal's ethernet interface
The main access to a terminal for management is with the ethernet interface using standard IP
networking. There should be only one ethernet connection from the terminal to the management
network.
The terminals are pre-configured to use IP addressing in one of the common 'non-routable' IP address
ranges. This means the terminals are usually recognized by your operating system without any
reconfiguration.
However, you should change these default addresses (see “
Changing the terminal’s IP address” on
page
56) to comply with your IP addressing scheme.
In the example below, the active management PC must only have one connection to the link as shown
by path c. There should not be any alternate path that the active management PC can use via an
alternate router or alternate LAN that would allow the management traffic to be looped as shown by
path d.