User's 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
Maintenance | 185
Kernel image files
Kernel image files contain code that forms the basis of the microprocessor’s operating system. There
can only ever be two kernel image files in the image table, the active and the inactive.
Kernel filenames have the following format:
C-CC-K-(version number).img
e.g. C-CC-K-7_1_4.img
To upload a kernel image file;
1. Select Local > Maintenance > Upload > Kernel
2. Browse to the location of the file required to be uploaded into the terminal *.img.
3. Click on Upload.
4. Activate the image (see “Changing the status of an image file” on page 188).
5. Reboot the terminal using a ‘Hard Reboot’ (see “Rebooting the terminal” on page 189).
Software image files
Software image files contain code that forms the basis of the terminal’s application and management
software (including the Web-based GUI). There can only ever be two software image files in the image
table, the active and the inactive.
Software image filenames have the following format:
C-CC-R-(version number).img
e.g. C-CC-R-7_1_4.img
To upload a software image file;
1. Select Local > Maintenance > Upload > Software
2. Browse to the location of the file required to be uploaded into the terminal *.img.
3. Click on Upload.
Software image files may take one or two minutes to upload as they can be quite large (≈ 2 Mbytes).
The size of this file has caused some Microsoft Internet Explorer proxy server setups to abort during
the software update process. To avoid this problem, either set the proxy file size limit to 'unlimited' or
avoid the use of the proxy altogether.
4. Activate the image (see “Changing the status of an image file” on page 188).
5. Reboot the terminal using a ‘Hard Reboot’ (see “Rebooting the terminal” on page 189).