Displaying Hardware Status

If potential hardware failures are detected, warning messages appear on the main interface window. However, you can also proactively monitor the current operating environment on the VG248. To do this, follow these steps:

Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Show environment.

The following information about the VG248 displays:

•Internal temperature

•1.8 volts supply

•3.3 volts supply

•5.0 volts supply

•12.0 volts supply

•48.0 volts supply

•96.0 volts supply

•Chassis fan state

The voltages and temperatures are indicated with the actual values and "okay", "too high", or "too low" annotating the values. The fan status is identified as "okay" or "faulty".

Identifying Fan Faults

If a fan fault is reported, it indicates that one (or more) of the fans is not functioning. You should verify that nothing is lodged in the holes in the rear of the device, but do not make any attempt to open the device or move the fans. You should contact a technical support representative from Cisco Systems for assistance.

Identifying Power Supply Faults

The 1.8v and 3.3v voltages must be within +/- 6% of nominal, and the others must be within +/- 10%. If any of these values are outside this range, then the VG248 reports a power supply fault.

If the phone power supplies (-48v and -96v) fail, it might indicate that the VG248 is overloaded. Verify that you have not exceeded the maximum ringer equivalency number (REN) load for each line. You should only have a maximum of three (3) phones per line.

If one of the other power supplies fails, you should contact a Cisco technical representative for assistance.

Monitoring Internal Operating Temperature

The VG248 monitors its internal temperature to ensure that it is operating within the specified limits (the ambient operating environment should be 0° to 40° C or 32° to 104° F). If the VG248 identifies internal temperatures too low or too high, it generates warning messages. Continuing to operate at ranges exceeding these limits (either too low or too high) can damage the VG248.

If the operating temperature of the VG248 is too low, there is a risk of condensation forming inside the device. You should move the device to a warmer location to prevent this.

If the operating temperature of the VG248 is too high, you should move the device to a cooler location with improved ventilation. The internal fans on the VG248 maintain the internal temperature consistent with the ambient environment. Therefore, if the device is in a location that is too warm, its internal temperature is more likely to exceed the limits. There are two levels of high temperature alert:

•yellow alert—generates and logs an error, but enables the device to continue functioning

•red alert—causes all the phones to be immediately shut down, causing calls to drop and preventing calls from being made. You must manually restart the VG248 either by selecting Configure > Restart or by disconnecting power to the device.

Connecting Too Many Phones to the VG248

The VG248 has a maximum ringer equivalency number (REN) load of three (3) analog devices per line (using a shared directory number), and only two of these devices can be off-hook at any one time. If these requirements are ignored, you might experience reduced quality on these analog phones, including:

•Difficulty hearing caller—Users have too many phones off-hook. Do not have more than two phones per line off-hook simultaneously.

•Dialing or caller ID are not working properly—Users have too many phones off-hook. Do not have more than two phones per line off-hook simultaneously.

•Phones not ringing properly or at all—REN load has been exceeded. Do not connect more than three analog devices per line.

Resolving Additional Hardware Errors

Table 5-1 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log) which are caused by a hardware fault. Use this information to resolve these errors.

Table 5-1 Hardware Errors and Warnings Explanation

System

Error

Explanation

Action

DSP

DSP X on SIM Y has failed

One of the Digital Signal Processor (DSP) chips inside the VG248 has failed.

Contact a Cisco technical representative for assistance.

DSP

DSP X, SIM Y failed to boot

OS

Ethernet has gone down

Ethernet has gone down at the physical level.

Verify that the Ethernet cable is properly connected to the VG248 and that the hub or switch to which it is connected is up and running properly.

SCCP

Failed to update real-time clock

The on-board real-time clock in the VG248 has failed to set the time from Cisco CallManager.

Contact a Cisco technical representative for assistance.

SLIC

EDSP failure warning received

A transient fault has been detected in the SLICs (the hardware that drives the analog telephony interfaces).

If these messages persist, contact a Cisco technical representative for assistance.

SLIC

over-temperature warning received

Troubleshooting Software Errors

The VG248 displays informational messages and errors on-screen or in the event log ((see the "Working with the Event Log" section for details on accessing the event log), which indicate potential software problems, such as misconfiguration, time-outs, unreachable servers, and so on.

Resolving Network and System Errors

Table 5-2 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which are caused by a misconfiguration or miscommunication with the network or system settings. Use this information to resolve these errors.

These errors might occur if the network is busy. The errors should resolve themselves when the network load reduces.

TFTP

TFTP: Rx error

Resolving Analog Errors

Table 5-3 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which are caused by a misconfiguration or miscommunication with the analog phones or features. Use this information to resolve these errors.

Table 5-3 Analog Errors and Warnings Explanation

System

Error

Explanation

Action

POTS

Feature codes: X same as Y

You have configured the telephone feature codes such that the code for one operation (such as speed dial) is the same as for another (such as call forward).

Users will not be able to use one of these operations. You must set unique feature codes for each operation.

Resolving Cisco CallManager Errors

Table 5-4 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which are caused by a misconfiguration or miscommunication with the Cisco CallManager system. Use this information to resolve these errors.

Table 5-4 Cisco CallManager Errors and Warnings Explanation

System

Error

Explanation

Action

SCCP

Registration failed: X

This message, associated with a particular port (1 - 48), indicates that the port had difficulty registering itself with Cisco CallManager.

If a port is not properly registered, then you cannot make phone calls using it.

The reason that registration with Cisco CallManager failed is indicated in the message.

If the port cannot successfully register, verify that the port is properly configured in Cisco CallManager.

Verify the name of the TFTP server the VG248 is attempting to locate using Display > System Status.

•If using DHCP, check the configuration on the DHCP server to verify that it is returning a valid TFTP server name to the VG248.

•If you are using a fixed TFTP server, verify the configured server name using Configure -> Telephony > CallManager TFTP server.

Upgrading Software Images

The VG248 has two software images: a main software image and a boot loader. If necessary, you can upgrade these software images.

Upgrading the Main Image

The main software image might need to be updated if a new release is available on CCO as a bug update or feature enhancement.

Caution When you send a new software image to the VG248 using FTP, the current image is automatically deleted. If the FTP transfer terminates before the new file is copied to the VG248, the VG248 might not be able to start up. See the
"Resolving an Incomplete Upgrade" section to resolve this problem.

To upgrade the main software image, perform these steps:

Step 1 Obtain a configuration file whose name is in the following format: vgc-main.<version>.tar, where <version> indicates the release number, such as 1-0-1.

Step 2 Connect to the VG248 using FTP.

Step 3 Send the configuration file to the VG248 using FTP.

Step 4 Restart the VG248 for the new image to take effect.

Step 5 From the main menu on the VG248, choose Display.

Step 6 Choose Version to verify the updated version has been installed.

Upgrading the Boot Loader

The boot loader is the initial startup image. You should not upgrade this image unless instructed to do so by a Cisco technical representative.

Caution Only upgrade the boot loader if you are instructed to do so by a Cisco technical representative. If you encounter difficulties during this upgrade, such as a loss of power, the VG248 might not be able to start up.

To upgrade the boot loader image, perform these steps:

Step 1 Obtain a configuration file whose name is in the following format: vgc-load.<version>.bin, where <version> indicates the release number, such as 1-0-1.

Step 2 Connect to the VG248 using FTP.

Step 3 Send the configuration file to the VG248 using FTP.

You must use a destination name that begins with "boot:". For example:

put vgc-load.<version>.bin boot:loader

Caution If the VG248 loses power or experiences a failure at this step, the VG248 might not start up. If this occurs, contact a Cisco technical representative for assistance.

Step 4 After the FTP command has completed successfully, restart the VG248 for the changes to take effect.

Step 5 Once the VG248 has restarted, choose Display > Version to verify that the updated version has been installed.

Resolving an Incomplete Upgrade

If you initiated an upgrade to the main software image, but terminated it before the FTP transfer of the new image completed, the VG248 might not start up properly.

If this occurred, the next time the VG248 starts up, one of the following occurs:

•The boot loader loads, but the VG248 waits indefinitely at the Pausing for FTP prompt.

•The VG248 partially loads the main image, pauses, and then restarts.

To resolve either of these errors (while connected to the VG248 boot loader), use the console port to establish an FTP session and transfer the main image file again, following the steps in the "Upgrading the Main Image" section.

Verifying Network Connectivity

To verify that the VG248 is connected to and communicating with your network, you can attempt to ping another device on the network. Follow these steps to ping another device from the VG248:

Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Ping network host.

Step 3 Enter the IP address or host name of the device.

The VG248 makes an attempt to reach the device once every second.

Step 4 Press Esc to exit.

Displaying Status and Configuration Settings

Use these sections to obtain information about the current status and settings of the VG248 and its connections:

•Active—connected to this Cisco CallManager and using this connection for SCCP communication.

•Connecting—in the process of connecting to this Cisco CallManager

•Idle—this Cisco CallManager is not being used

•Standby—connected to this Cisco CallManager but not currently using the connection. Can use connection if active connection fails.

•Pending—attempting to make this Cisco CallManager the active connection as soon as possible.

CallManager type

Type of Cisco CallManager system:

•Normal—typical Cisco CallManager system

•Failover—Cisco CallManager system reserved for failover situations

Displaying Port Statistics

Step 1 From the main screen, choose Display.

Step 2 Choose Port status.

Step 3 Use the arrow keys to select one of the ports and press Enter.

Step 4 Press the space bar.

These statistics display for the current call:

•Tx packets

•Rx packets

•Call time

•Rx bad sequence

•Rx bad headers

•Rx packets late

•Rx packets early

These statistics display for the call history:

•Incoming calls

•Outgoing calls

•Connected calls

Displaying Current Configuration

You can quickly display all the settings you have configured on the VG248.

To display the configured settings, perform these steps:

Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Show configuration.

Displaying Software Version

Step 1 From the main screen, choose Display.

Step 2 Choose Version.

Monitoring System Status Remotely

The VG248 includes a web server allowing you to monitor system status remotely using a web browser application. These options are identical to the settings accessible via the VG248 user interface directly.

Follow these steps to monitor the system status remotely:

Step 1 From a web browser window, enter the IP address or host name of the VG248.

Working with the Event Log

The event log enables you to capture errors, warnings, and other informational messages from the VG248. 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:

Tips You can also select View all to display all errors, or View new to display new errors only.

Understanding Sub-Systems on the VG248

The VG248 generates informational and warning messages and errors from different sub-systems in its software. Many of these messages do not require any intervention on your part; the device simply notifies you of changes or update. Other errors and warnings require additional troubleshooting or configuration.

Table 5-7 provides an overview of the different sub-systems on the VG248 that might generate informational or warning messages.

Table 5-7 VG248 Sub-Systems

System

Description

DHCP

Communicates with DHCP server.

Ethernet

Concerned with low-level network link integrity.

OS

Runs the low-level services of the VG248.

FTP

Used to send new software images to the VG248.

DNS

Resolves host names to IP addresses.

TFTP

Handles retrieval of Cisco CallManager port configuration.

SLIC

Detects events from analog handsets.

DSP

Provides digital signal processing.

POTS

Bridges between analog and IP telephony.

SCCP

Transmits and receives telephony events over the IP network; communicates with Cisco CallManager.

SNMP

Coordinates SNMP communication.

Resolving Incorrect Date and Time in Event Log

The VG248 has a built-in real time clock that synchronizes itself periodically with Cisco CallManager to obtain the correct date and time.

The VG248 must have at least one port enabled and registered with Cisco CallManager. You should also verify that the time settings on the Cisco CallManager system are correct.