|
|
The DPA 7630 includes several built-in troubleshooting and diagnostic features. Use these sections for details about troubleshooting:
The DPA 7630 includes several LED status indicators on the front panel (see Figure 5-1). Table 5-1 includes descriptions of these LEDs.
| LED | On | Flashing | Off |
|---|---|---|---|
Power | Power connected and operating normally | N/A | Power not connected |
Status | Operating normally | Potential hardware error detected. Check the event log for details. | Not operating normally |
TX | N/A | Packet transmitted. | Nothing transmitted |
RX | N/A | Packet received. | Nothing received |
100 MBPS | Connected at 100 Mbps | N/A | Connected at 10 Mbps |
Ethernet Link | Ethernet link connected | N/A | Not connected |
Console Link | Console link connected | N/A | Console link not connected |
24 Port | Connected and operating normally | Not configured or error on port | Not connected |
Use these sections to obtain information about the current status and settings of the DPA 7630 and its connections:
The system status provides an overview of the current network settings on the DPA 7630. Use this procedure to quickly check your network settings and connectivity information.
To display system status, perform these steps:
Step 2 Select System status.
The system status displays:
Use the network statistics to observe the network traffic and packet errors through the IP connection on the DPA 7630.
To display network statistics, perform these steps:
Step 2 Select Network statistics.
These statistics display:
The port status provides detailed information about each port on the DPA 7630. This is useful when determining the current state and activity on a particular port.
To display port status, perform these steps:
Step 2 Select Port status.
Step 3 Use the information in Table 5-2 and Table 5-3 to interpret the port status.
| Type | Description |
|---|---|
Call | This port is used for general call processing. |
Oct MWI | This port is used to receive MWI commands from the Octel system. |
PBX MWI | This port is used to set MWI commands on the Lucent PBX system. |
Virtual | This "port" is an IP phone used for setting MWI commands on Cisco CallManager. |
Down | The link to the Octel or PBX port is not connected. Unused ports display as "down." |
| Status | Description | Used By Port Type |
|---|---|---|
Octel registering | This indicates an intermediate state when the DPA 7630 is starting up a port's connection to the Octel system. |
|
Octel link down | The port previously had a connection to the Octel system, but the connection is down. |
|
CM link registering | This indicates an intermediate state when the DPA 7630 is registering an IP phone with Cisco CallManager. |
|
CM link down | This indicates an intermediate state when the DPA 7630 has successfully started the port connected to the Octel system but cannot establish a connection to Cisco CallManager. |
|
DN=xxxx <substate> | This is the normal status for the ports. The Octel port has started, and the IP phone associated with the port has registered and has a directory number assigned to it, where DN=xxxx indicates the directory number, and <substate> indicates current port activity:
|
|
DN=xxxx, Q=yyy | IP phone is up with assigned directory number, and there are MWI messages queued for Cisco CallManager. | Virtual |
PBX down | The PBX port is down. | PBX MWI |
PBX registering | The PBX port is starting up. | PBX MWI |
Q=xxxx | The PBX port is up, and there are MWI messages queued. | PBX MWI |
O=xxxx | DPA is dialing out the MWI command xxx to the PBX. | PBX MWI |
You can obtain detailed information about the connection to the Cisco CallManager system.
To display Cisco CallManager status, perform these steps:
Step 2 Select Port status.
Step 3 Select a port and press Enter.
Step 4 Refer to Table 5-4 for a description of the fields.
To obtain detailed information about the Octel integration, perform these steps:
Step 2 Select Octel integration status.
Step 3 The system displays the following information:
 |
Tips In hybrid mode, the MWI status options display as separate settings for the Lucent and Cisco CallManager systems. |
You can quickly display all the settings you have configured on the DPA 7630.
To display the configured settings, perform these steps:
Step 2 Select Show configuration.
The event log enables you to capture errors, warnings, and other informational messages from the DPA 7630. Typically, you use these options only when troubleshooting a complex issue, perhaps while working with a Cisco technical representative.
However, using the default settings and these options, you can resolve many errors on your own:
You can identify a syslog server to automatically capture and receive event logs for remote network management by performing these steps:
Step 2 Select Event log.
Step 3 Select Syslog server.
Step 4 Enter the IP address of the network management system you want to designate as the syslog server.
You can set the DPA 7630 to log progressively more detail (information, errors, or warnings), or you can restrict logging to specific ports.
Usually, configure these options when working with a Cisco technical representative because the nature of the problem determines the amount of information required to resolve it.
To set logging levels or select ports, perform these steps:
Step 2 Select Event log.
Step 3 Select Set logging levels or Set logged ports.
Step 4 Work with a Cisco technical representative to determine the best options to select and enter.
You can obtain a list of recent messages from the DPA 7630 to help you resolve some configuration issues.
To display recent messages, perform these steps:
Step 2 Select Event log.
Step 3 Select View recent to display recent messages.
Step 4 See "Resolving Error Messages" section for information on resolving these errors.
|
Tips You can also select View all to display all errors, or View new to display new errors only. |
You can use the event log to identify errors on the DPA 7630. Use Table 5-5 to interpret and resolve these errors.
| System | Error | Explanation | Action |
|---|---|---|---|
Octel/CM | Lucent MWI On dial string not set | You have not configured the dialing sequence options for setting MWI on the Lucent/Octel systems. | 1. From the DPA 7630 main menu, select Configure. 2. Select Octel/Lucent integration configuration. 3. Select Lucent MWI ON pre-extension dial string. 4. Enter the appropriate values obtained from the Octel and Lucent systems. |
Octel/CM | Lucent MWI Off dial string not set | You have not configured the dialing sequence options for turning off MWI on the Lucent/Octel systems. | 1. From the DPA 7630 main menu, select Configure. 2. Select Octel/Lucent integration configuration. 3. Select Lucent MWI OFF pre-extension dial string. 4. Enter the appropriate values obtained from the Octel and Lucent systems. |
Octel/CM | CM MWI On DN not set | You have not configured the options for enabling MWI on the Cisco CallManager system. | 1. From the DPA 7630 main menu, select Configure. 2. Select CallManager. 3. Select CallManager MWI ON directory number. 4. Enter the appropriate values obtained from the Cisco CallManager system. |
Octel/CM | CM MWI Off DN not set | You have not configured the options for disabling MWI on the Cisco CallManager system. | 1. From the DPA 7630 main menu, select Configure. 2. Select CallManager. 3. Select CallManager MWI OFF directory number. 4. Enter the appropriate values obtained from the Cisco CallManager system. |
Octel/CM | Octel/Lucent integration mode not set | You have not configured the integration mode. | 1. From the DPA 730 main menu, select Configure. 2. Select Octel/Lucent integration. 3. Select Mode. 4. Select the appropriate configuration type:
|
Octel/CM | CM register reject | The port attempted to register with Cisco CallManager but was rejected. | Verify that Cisco CallManager and the settings for this port in Cisco CallManager are properly configured. Refer to the documentation and online help included with Cisco CallManager for additional assistance. |
Octel/CM | <port> Lucent MWI controller <port> not up | A request to set or clear a Lucent MWI light was received from the Octel system, but the corresponding port connected to the PBX is not responding. | Verify that the cabling between the DPA 7630 and the Lucent and Octel systems is set up properly. Refer to the "Connecting to the Telco Connectors" section for instructions on configuring these connections. |
DHCP | IP address refused | The DHCP server rejected the DPA 7630's request for an IP address. | Check configuration of DHCP server. If errors persist, assign a static IP address. |
DHCP | IP address cannot be allocated | No DHCP server responded to the request. | Check configuration of DHCP server. If errors persist, assign a static IP address. |
DHCP | Server address not configured | DHCP is not being used so you must assign a static IP address. | Refer to "Configuring Network Settings" section for details on assigning a static IP address. |
Ethernet | Ethernet failed to start | The Ethernet cable is not properly connected to the DPA 7630 or to the hub or switch. | Check the Ethernet cable and reconnect it to the DPA 7630 and the hub or switch. If error persists, replace cable. |
OS | Incorrect password entered | A user attempted to use a telnet or console connection to the DPA but entered an incorrect password. | Check the passwords and verify that you are using the correct one. Change the password if you suspect an unauthorized login attempt. Refer to the "Configuring Passwords" section for details. |
SNMP | Attempt to use Get with invalid community name "<name>" | The DPA was sent an SNMP request with an invalid read-only community name (password). | Check the community string setting on the DPA and ensure that your network management system has the correct password. Refer to the "Configuring SNMP Settings" section for details. |
SNMP | Attempt to use Set with invalid community name "<name>" | The DPA was sent an SNMP request with an invalid read-write community name (password). | Check the community string setting on the DPA and ensure that your network management system has the correct password. Refer to the "Configuring SNMP Settings" section for details. |
Posted: Thu Dec 14 09:31:08 PST 2000
Copyright 1989-2000©Cisco Systems Inc.
