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 | 184
Image Files
Image files (.img) are loaded into the terminal and either contains code that is executed by the system
processor, or contain instructions to configure the various programmable logic elements. The image
file types that can be uploaded are:
• Kernel image files
• Software image files
• Firmware image files
Note: The Bootloader image file C-CC-B-(version number).srec and Flash File System image file C-
CC-F-(version number).img can only be changed in the factory.
Uploading of image files can only be performed to the local terminal (not via the link to the remote
terminal).
To upload and activate an image file:
1. Upload the required image file.
If the Upload Status page show ‘executing’, then ‘writing to flash’, then ‘Succeeded’, then the file
has been written into the image table correctly.
If the Upload Status is ‘Failed’, there may not be enough free space in the image table to write the
file. Inactive images can be deleted (and the terminal rebooted) to free up space for the new
image (see “
Changing the status of an image file” on page 188).
2. Set the status of the image to ‘activate’ (see “Changing the status of an image ” on page 188).
This actually sets the status to ‘Selected’ until after a terminal reboot.
3. Reboot the terminal using a ‘Hard Reboot’ (see “Rebooting the terminal” on page 189).
This activates the selected image. The image table status will now show ‘Active’.
The previous image file status will now show as ‘Inactive’.