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
Configuring the terminal | 67
SNMP (Simple Network Management Protocol)
In addition to web-based management (SuperVisor), the terminal can also be managed using the
Simple Network Management Protocol (SNMP). MIB files are supplied, and these can be used by a
dedicated SNMP Manager, such as Castle Rock's SNMPc (
www.castlerock.com), to access most of
the terminal's configurable parameters.
However, it is recommended that SNMP is only used for status and alarm monitoring of your entire
network. SuperVisor is the best means to configure individual terminals.
For communication between the SNMP manager and the terminal, Access Controls, Trap
Destinations, and Community strings must be set up as described in the following sections.
A SNMP Access Control is the IP address of the terminal used by an SNMP manager or any other
SNMP device to access the terminal. Entering an IP address of ‘Any’ (not case sensitive) or
*
will
allow any IP address access to the terminal. A community string is sent with the IP address for
security.
Commands are sent from the SNMP manager to the terminal to read or configure parameters of the
terminal e.g. setting of interface parameters.
A SNMP Trap Destination is the IP address of a station running an SNMP manager. A community
string is sent with the IP address for security.
Events are sent from the terminal to the SNMP manager e.g. alarm events.
A SNMP Community String is used to protect against unauthorized access (similar to a password).
The SNMP agent (terminal or SNMP manager) will check the community string before performing the
task requested in the SNMP message . Trap Destinations and Access Controls both use community
strings for protection.
To configure Trap Destinations and Access Controls:
Select Local > Maintenance > SNMP > SNMP Settings
Note: SNMP Settings can only be setup on the local terminal.