Chapter 11 Using System Diagnostics

Rebooting PSAX Hardware Components

11-14 255-700-686R10.0.0
PacketStar

PSAX Multiservice Media Gateway User Guide, Issue 1 Release 10.0.0

Rebooting PSAX Hardware Components
Specific hardware components may need to be restarted for several reasons,
including:
When you want to revert back to a saved configuration
When a module is not adhering to its configuration
When timing problems cannot be resolved automatically
When firmware changes on a module
After turning on system-wide features (such as the GR-303 Interface)
To reboot (initialize) one or more components in a PSAX system, perform the
following procedure.
Perform the following procedure to reboot the system and apply the configu-
ration changes performed in the previous procedures.
Begin
1 Select the Console Interface Main Menu window by pressing Ctrl+G.
The Console Interface Main Menu window is displayed.
2 Select the Save Configuration [Modified] option (Ctrl+A) to save the
modifications. [Modified] is removed from the window when Save Con-
figuration is selected.
3 Select the Diagnostics option.
The Diagnostics Menu window is displayed.
[Test Status] Default: Not-run-
ning
Range: N/A
Format: Predefined
Displays the status of the cell test.
Not-running Indicates the test is not running.
Running Indicates the test is running.
[Packets Transmit-
ted]
Default: 0
Range: N/A
Format: Numeric
Displays the number of packets transmitted.
[Packets Received] Default: 0
Range: N/A
Format: Numeric
Displays the number of packets received.
[Packets Mis-
matched]
Default: 0
Range: N/A
Format: Numeric
Displays the number of packets that are not asso-
ciated with the number transmitted/number
received pairs.
Table 11-9. Cell Test Payload Configuration Window Field Descriptions (Continued)
Field Name Field Value Description
255-700-686R10.0.0 11-15
PacketStar

PSAX Multiservice Media Gateway User Guide, Issue 1 Release 10.0.0

Chapter 11 Using System Diagnostics
Rebooting PSAX Hardware Components
4 Select the Reboot Hardware Components option.
The Remote Reboot Configuration window is displayed (see
Figure 11-7). The commands on this window are described in
Table 11-10.
5 Select the appropriate command as needed.
For the options preceding the Primary Switchover option, you will be
prompted twice from the following table to confirm whether you want to
proceed with the operation. For the Primary Switchover option, you will
have the opportunity to save you configuration if you did not already do
so (see step 1). The system displays a prompt in the status line, asking
whether you are sure you want to reboot.
!
CAUTION:
Selecting any option on the Remote Reboot Configuration window will
interrupt all traffic running on the chassis and/or the selected I/O mod-
ule(s).
6 Press Y (yes) to proceed with the reboot operation, or press N to cancel
the request.
The VxWorks shell is restarted in a process called the auto-boot. If you
press a key during the auto-boot process, the auto-boot process will stop.
You can resume the auto-boot process by pressing Shift+2 (the @ sym-
bol). The system reboot takes 510 minutes, depending on the system
configuration.
7 After the Press RETURN to log in... message is displayed, log back
into the system, if necessary.
End
Figure 11-7. Remote Reboot Configuration Window
Chapter 11 Using System Diagnostics
Rebooting PSAX Hardware Components
11-16 255-700-686R10.0.0
PacketStar

PSAX Multiservice Media Gateway User Guide, Issue 1 Release 10.0.0

Table 11-10. Remote Reboot Configuration Window Commands
Command Function
Note: If you have just upgraded your PSAX system software, make sure that all module firmware
drivers are completely and successfully downloaded before using the commands on this window.
Reboot the I/O Module in
Slot:__
Reboots the I/O or server module in the slot you designate. This
command is the equivalent to physically removing the module from
and then reinserting it into the chassis.
Reboot All I/O Modules Reboots all I/O and server modules in the chassis, without affecting
the primary CPU module or backup (standby) CPU module (if one is
present). This command is the equivalent to physically removing the
modules from and then reinserting them into the chassis.
Reboot Primary CPU
WARNING:
!
Rebooting the PSAX system with a single (nonredundant) CPU
module or component will interrupt all traffic running through
the PSAX chassis.
Reboots (reinitializes) the primary CPU module. If a backup
(standby) CPU module is present in the system, traffic running
through the PSAX chassis is not interrupted. This command also
reboots all I/O and server modules in the chassis, as instructed by
the system software initialization process. In a system with redun-
dant (two) CPU modules, the primary CPU module remains the pri-
mary one.
Reboot Backup CPU Reboots (reinitializes) the backup (standby) CPU module, without
affecting the primary CPU module. Used only in redundant PSAX
systems.
Reboot Chassis
WARNING:
!
Rebooting the PSAX system with the Reboot Chassis command
will interrupt all traffic running through the PSAX chassis.
Reboots the primary CPU module, the backup (standby) CPU mod-
ule (if one is present), and all I/O and server modules in the chassis;
purges trap log.
This command is equivalent to a system cold start, that is, removing
the power from the chassis and then reapplying the power.
Use this command:
After enabling the GR-303 interface feature.
After changing the call control resource allocation setting for
H.248 protocol feature.
255-700-686R10.0.0 11-17
PacketStar

PSAX Multiservice Media Gateway User Guide, Issue 1 Release 10.0.0

Chapter 11 Using System Diagnostics
Removing Configuration Files
Removing Configuration Files
To remove configuration files, perform the following procedure.
WARNING:
!
The following procedure removes all configuration files from the CPU
and restores the CPU to its factory default settings. All data will be
removed except the CPU IP address, gateway IP address, and SNMP trap
destinations.
Begin
1 On the Console Interface Main Menu window, select the Diagnostics
option.
The Diagnostics Menu window is displayed (see Figure 11-2).
2 On the Diagnostics Menu window, select the Remove Configuration Files
option. The following prompt is displayed.
Are you sure that you want to remove all the configuration
files? (y/n)
3 Answer y to remove the files or n to cancel.
End
Unlocking a Telnet Session
If you are in a telnet session to connect to an PSAX system and a lockup con-
dition occurs, you must use another PSAX system in the network to remotely
access and unlock the PSAX system with the telnet lock-up problem. To
unlock the telnet session of a PSAX system, or to check the connectivity of a
PSAX system, perform the following procedure.
Primary Switchover Switches processing control from the primary CPU module to the
backup (standby module) and immediately begins rebooting the
original primary CPU module. As this process proceeds, the new pri-
mary CPU module (originally the standby CPU) synchronizes the
management information base (MIB) data with the new standby
CPU module (originally the primary CPU). The green LED ACTIVE is
illuminated on the primary CPU module. Used only in redundant
PSAX systems.
Note: Using this command does not interrupt traffic running
through the PSAX chassis.
Go Back to Diagnostics
Menu
Redisplays the Diagnostics Menu window.
Table 11-10. Remote Reboot Configuration Window Commands (Continued)
Command Function
Chapter 11 Using System Diagnostics
Unlocking a Telnet Session
11-18 255-700-686R10.0.0
PacketStar

PSAX Multiservice Media Gateway User Guide, Issue 1 Release 10.0.0

Begin
1 From another PSAX system, log onto the PSAX system console interface.
2 On the Console Interface Main Menu window (see Figure 11-1), select
the Diagnostics option.
The Diagnostics Menu window is displayed (see Figure 11-2).
3 On the Diagnostics Menu window, select the Unlock Shell / Ping option.
The Unlock Shell / Ping window is displayed (see Figure 11-8).
4 Type the IP address of the PSAX system that is connected to the locked-
up telnet session in the IP Address field,.
5 Select the Unlock Remote Shell command.
This command corrects a telnet lock-up condition, and enables you to
access the specified PSAX system.
6 To verify that access has been restored to the specified PSAX system,
select the Ping Remote Machine command.
This command sends a ping command to the remote PSAX system speci-
fied in the IP Address field or to another switching device to indicate
whether or not you can connect to that remote device.
End
Figure 11-8. Unlock Shell / Ping Window
255-700-686R10.0.0 11-19
PacketStar

PSAX Multiservice Media Gateway User Guide, Issue 1 Release 10.0.0

Chapter 11 Using System Diagnostics
Operations Administration and Maintenance (OAM)
Operations Administration and Maintenance (OAM)
OAM is supported for end-to-end and end-segment-point connections. In
order to support OAM functionality, you must have already configured one
I/O module for circuit emulation and one I/O module for ATM as follows:
The first port is assigned to the near-end user.
The second port is assigned to the far-end user, using the same configura-
tion as the first port.
For further information about OAM, see Chapter 3. To enable OAM connec-
tions, see the PacketStar

PSAX Connections Provisioning Guide.

Enabling OAM Loopback Functions
To enable OAM loopback functionality, perform the following procedure.
Begin
1 On the Diagnostics Menu window, select the OAM Loopback option.
The OAM Loopback Table window is displayed (see Figure 11-9).
2 Select the OAM Add a loopback command.
The OAM Loopback window is displayed (see Figure 11-10).
3 Enter values in the fields on this window according to the information
provided in Table 11-13.
4 To apply the desired OAM Loopback configuration, select the Apply
Action command.
End