Troubleshooting guide
Table Of Contents
- Chapter 1 Getting Started
- Chapter 2 Initial Setup
- Connect PC to Controller
- Establish Communication with Controller
- Enable Licenses and Options
- MCD Software Installer Tool Requirements for AMC
- 3300 ICP System Requirements for AMC
- Automatic Sync with AMC via MCD Software Installer Tool (Rel 6.0 or later)
- Automatic Sync via System Administration Tool
- Manual License and Options Entry via MCD Software Installer Tool
- Manual License and Options Entry via System Administration Tool
- Install the Online Help (Optional)
- Verify the Operation of the Controller
- Chapter 3 Installation and Programming
- Install Hardware
- Determine Controller Module Configuration
- Identify Controller Component Options
- Remove Controller Cover
- Install Controller Modules
- Install Controller Stratum 3 Clock Module
- Install Controller Hardware
- Rack Mount the Controller
- Wall Mount the CX/CXi and CX II/CXi II Controller
- Install Service Units and Cabinets
- Installing SX-200 Bays
- Install Telephones
- Install and Configure Music on Hold
- Program 5485 IP Paging Unit
- Register IP Devices from the Telephone
- Program System
- Install Hardware
- Chapter 4 Software Installation
- About Installing and Upgrading Software
- Install System Software Manually
- The MCD Software Installer Tool
- Upgrade System Software
- System Software Installation Details
- Installing MSL Software on APC (CX/CXi) or APC-CX(i) II (CX II/CXi II)
- Installing MSL Software on an MXe Server
- Installing System Software on the FTP Server
- Upgrade to MCD 5.0 and Group Licensing
- Upgrade the 3300 ICP Software on the MXe Server
- Upgrading/Installing with Maximum Elements Change
- Upgrade to Rel 6.0 or later with Flexed Dimensions
- Apply a Software Patch
- Distributing New Firmware to IP Phones
- Load IP Phone Software Remotely
- Downgrading to a Previous Software Release
- Chapter 5 Maintenance
- Check System
- View Logs
- Detect Device Moves for E911
- Analyze IP Phone Issues
- Power Down the Controller
- Perform a System Reset
- Back Up a Database
- Restore a Database
- Migrate SX-2000 Database Across Platforms
- Converting a PRI Database on a Universal NSU
- Export Configuration Data
- Import Configuration Data
- Restoring Default Addresses on MXe Server
- Assign Static IP Addresses to IP Phones
- Providing Power Over Ethernet to Devices (CXi/CXi II)
- Recover MXe Server
- Chapter 6 Install and Replace Units
- Component Replacement Notes
- Add or Replace Controller FRUs
- Controller Modules
- Stratum 3 Clock Module
- System i-Button/System ID Module
- Analog Main Board
- Analog Option Board
- Application Processor Card
- E2T or RTC Processor
- Hard Drives
- Fan Complex
- Power Supply Unit
- Redundant Power Supply
- RAID Controllers
- Line Cards
- Controller Card (AX)
- Flash Cards (AX)
- Memory Module (CX, CXi, AX)
- Install Cabinet FRUs
- Appendix A Hardware Reference
- Appendix B Installation Planner
- Reserved IP Addresses
- MXe Server/MXe/AX/CXi/CXi II Requirements for IP Networking
- Controller Configuration Settings (RTC)
- DHCP Configuration Settings
- Programming E2T via Debug Cable or Secure Telnet
- Configuring External DHCP Settings for E2T
- Configuring a Windows 2000 or Windows 2003 DHCP Server (Rel 7.0 and later)
- System Administration Tool Settings
- IP Phone Settings
- Telephone Programming Guide
- Increasing DSP Resources
- Appendix C Typical Network Configurations
- Network Configuration Examples
- Cisco Discovery Protocol (CDP)
- CXi/CXi II/MXe/MXe Server Configuration
- AX Configuration Procedures
- CXi, CXi II, MXe and AX-Specific Guidelines
- Windows 2000 FTP Server
- Appendix D Status LEDs
- Controller LEDs
- Network Services Unit LEDs
- Analog Services Unit LEDs
- ASU II Card LEDs
- IP Device LEDs
- Peripheral Cabinet LEDs
- SX-200 Bay LEDs
- Digital Services Unit LEDs
- In-Line Power Unit LEDs
- Appendix E FRU Part Numbers
- Appendix F System Capacity and Parameters
- Appendix G Older Hardware and Software
- Procedures for Older Controllers
- Programming the Controller DHCP Server Settings (prior to Rel 7.0)
- To use an alternative DHCP server (prior to Rel 7.0)
- Configuring a Windows 2000 DHCP Server (prior to Release 7.0)
- Program DHCP for VLAN (prior to Rel 7.0):
- Connect a Windows 95/98 PC to the NSU via Dial-Up
- Physically Connecting the PC to an NSU
- Creating a Dial-Up Network Connection on Windows 95/98
- Migrate SX-2000 PBX Hardware
- Collecting System Logs Manually
- Collecting System Lockup Logs Manually
- Peripheral Cabinet
- Digital Service Unit (DSU)
- Index
- Procedures for Older Controllers
59
Installation and Programming
You can double the number of Universal and R2 NSUs in a system by
chaining a secondary NSU to each primary NSU connected to the
controller. BRI NSUs cannot be chained.
Some NSUs must be programmed with the ISDN Maintenance and
Administration Tool (IMAT) (see “ISDN Maintenance and Administration
Tool” on page 72).
Universal or R2 Network Services Unit
1. Mount and secure the NSU in the desired location.
2. Set the L0/L1 port DIP switches to the appropriate termination mode
and impedance (see Table 31 on page 255 and Table 36 on
page 257). The default is network termination mode. See “Network
Services Units” on page 254 for the location of these switches.
3. Set the Message Link DIP switch to the appropriate position. See
Figure 111 on page 254 for the location of the Message Link switch
and Table 30 on page 255 for settings.
4. Connect a fiber optic cable between the NSU and the controller FIMs.
5. If you are installing a secondary NSU, connect a crossover CAT 5
cable between CIM 1 of the secondary NSU and CIM 2 of the primary
NSU (see Table 33 on page 256 for CIM pinout, and Table 30 on
page 255 for message link dip switch settings).
6. Connect the NSU L0 and/or L1 port to the remote system (the PSTN
or another system). See Table 36 on page 257 for the pinout.
7. For the PRI and R2 protocols, program the NSU using IMAT (see “To
install IMAT on the PC:” on page 72 and “Program NSU from IMAT” on
page 75). Refer to the IMAT Online Help for more information.
8. Connect power to the NSU.
9. Using the System Administration Tool, program the NSU settings on
the controller. In the View Alphabetically list, click Network Services
Unit Configuration. Refer to the Online Help for more information.
CAUTION: To connect your NSU to the LAN, you must change
the default IP and gateway addresses to match an available
address on the LAN. The default address is
192.168.1.1:ffffff00. See "Program an IP Address into the NSU"
on page 74.
Tip: The NSU software will not load until the NSU programming is complete
(see Step 9 below).