|
|
The Cisco Media Gateway Controller (MGC), is a Sun host running Cisco MGC Software Release 7. The Cisco MGC, in conjunction with other elements of the telephony solution, provides public switched telephone network (PSTN) access services using several different Cisco Media Gateways (MGWs) or trunking gateways.
You can manage the Cisco MGC by using the Cisco MGC software and Man-Machine Language (MML) commands to stop and start the system; retrieve the status of the software, signaling, and traffic channels; and command signaling and bearer channels in or out of service.
You might need to perform these tasks if you:
The following paragraphs contain the startup procedures for each component of the solution.
The procedures in this section are performed using MML or UNIX commands. You should be familiar with these commands before attempting these procedures.
For more information about MML commands, see the chapter titled "MML Commands" in the Cisco Media Gateway Controller Software Release 7 Reference Guide.
For more information about UNIX commands, see the Appendix titled "UNIX System Operation," also located in the Cisco Media Gateway Controller Software Release 7 Reference Guide.
 |
Note This section assumes that the Cisco Media Gateway Controller Software Release 7 has been correctly installed, configured, and provisioned on the host server and that you have the appropriate packages, or applications, for your system. If the Cisco MGC Software Release 7 has been installed, configured, or provisioned incorrectly, or you are having other problems, see "Troubleshooting the Cisco MGC," for more information. |
To perform the procedures in this section, you must have a user ID that is part of the Cisco MGC group (mgcgrp) if you are using version 7.4 or up of the MGC software, or the Transpath group if you are using version 7.3 software, you must have the proper group privileges, and you need to source $BASEDIR/local/.cshrc.
|
Note If you are using version 7.3 software, you must substitute "TransPath" in place of "CiscoMGC" wherever it appears in this manual. Consult your system administrator. |
To verify that your user ID is part of the Cisco MGC group (or the TransPath group) and that you have the necessary privileges, see "Setting Up the CiscoMGC Group and Users" in the Cisco Media Gateway Controller Software Release 7 Reference Guide for more information.
|
Note For some startup procedures, you must log in as root; this is noted in the applicable locations. In other procedures, you must not log in as root and that also is noted. |
When a procedure requires that you start an MML session, you must perform the following steps:
|
Note We recommend that you run your MML sessions from the active Cisco MGC. |
|
Note You do not need to change to a subdirectory under $BASEDIR if you are using version 7.4 and up of the MGC software. |
Step 2 Enter the following command:
mml
If you receive an error message that sessions are already in use, enter the following command:
mml -s session number
Use any session number from 2 through 12 and repeat until you find a vacant session. After successfully entering MML, the prompt changes to:
machine_name mml>
The system defaults to automatic startup. Under normal conditions, simply powering up the system automatically launches the Cisco MGC software and the Simple Network Management Protocol (SNMP) daemon. See the "Configuring SNMP" section in the Cisco Media Gateway Controller Software Release 7 Installation and Upgrade Guide for more information about SNMP.
For all configurations the Process Manager (procM) starts first. The Process Manager controls and starts all of the processes and process groups listed in Table 2-1.
The system switch of the Cisco MGC is a rocker, momentary contact switch that functions as a standby device only, controlling the logic circuits that enable power module output.
To power on the system, complete the following steps:
|
Note Peripheral power is activated prior to system power so that the system can recognize the peripherals when it is activated. |
Step 2 Apply power to the system inlet.
Step 3 Momentarily set the front panel ON/STBY system switch to the ON position and hold it until the system starts to power up.
 |
Caution Do not use the following commands unless specifically instructed to do so by Cisco Technical Assistance Center (TAC) personnel. |
To manually start the system, log in to the Cisco MGC as root and enter the command:
/etc/init.d/[ CiscoMGC | TransPath ] start
This restores execution permission and enables the startup script.
To manually stop the system, enter the command:
/etc/init.d/[ CiscoMGC | TransPath ] stop
This disables the startup script and allows you to start individual processes or process groups.
The Cisco MGC software contains processes and process groups that perform various software functions. These functions include managing the I/O channels; generating alarms, call detail records, and logs; and performing signal conversion. All these processes are managed by the Process Manager (procM) component of the software.
The processes.dat file contains information about every process on the system that the Cisco MGC is responsible for monitoring. Three different monitoring levels are offered:
Additionally, the processes.dat file holds information related to how often to check a process's health and about how to restart the process.
The file procGroups.dat contains an entry for each Cisco MGC component-managed process group on the system. Information is included indicating whether procM must automatically start a process group and what delay must be involved.
Using MML commands to control procM, you can monitor the health of managed processes running on the call processor.
Table 2-1 shows the system processes and process groups controlled by the Process Manager for
version 7.4 and up of the MGC software.
Table 2-2 shows the system processes and process groups controlled by the Process Manager for
version 7.3 of the MGC software.
| Group | Process | Description |
|---|---|---|
| ENGG-01 | Engine Group | |
| Replic-01 | Replicator Controller |
| ENG-01 | Engine |
| LOGG-01 | Logging Group | |
| LOG-01 | Log Server |
| IOSG-01 | I/O Subsystem Group | |
| IOCM-01 | IOS Channel Manager |
| TCAP-01 | TCAP and SCCP protocol handler |
| XEG-01 | Execution Environment Group | |
| CFM-01 | Config Manager |
| ALM-01 | Alarm Manager |
| MM-01 | Measurement Manager |
| CDRDMPR-01 | CDR Dumper |
| MMDB-01 | TimesTen DataBase Process |
| POM-01 | Provisioning Object Manager |
| FTG-01 | Failover Group | |
| FOD-01 | Failover Controller |
| PFMG-01 | Platform Monitoring Group | |
| DSKM-01 | Disk Space Monitor |
| SNMPG-01 | SNMP Group | |
| MEASAGT | Measurements SNMP Agent |
| PROVSAGT | Provisioning SNMP Agent |
| OPERSAGT | Operational SNMP Agent |
| Group | Process | Description |
| ENGG-01 | Engine Group | |
| Replic-01 | Replicator Controller |
| ENG-01 | Engine |
| IOSG-01 | IO Subsystem Group | |
| IOCM-01 | IOS Channel Manager |
| TCAP-01 | TCAP and SCCP protocol handler |
| IOCC-ASP | IOS Channel Controller - ASP |
| XEG-01 | Execution Environment Group | |
| CFM-01 | Config Manager |
| ALM-01 | Alarm Manager |
| MM-01 | Measurement Manager |
| AMDMPR-01 | Alarm and Measurement Dumper |
| CDRDMPR-01 | CDR Dumper |
| MMDB-01 | TimesTen DataBase Process |
| POM-01 | Provisioning Object Manager |
| FTG-01 | Failover Group | |
| FOD-01 | Failover Controller |
| PFMG-01 | Platform Monitoring Group | |
| DSKM-01 | Disk Space Monitor |
| SNMPG-01 | SNMP Group | |
| MEASAGT | Measurements SNMP Agent |
You can retrieve the status of an individual process, a process group, or all processes using MML commands. You might want to retrieve the status of all of the processes to see which ones are active.
To retrieve the status of all processes, perform the following steps:
|
Note You do not need to change to a subdirectory under $BASEDIR in version 7.4 and up of the MGC software. |
Step 2 Enter the following command at the MML prompt:
rtrv-softw:all
The system returns different sets of messages depending on which version of the MGC software you are running.
For version 7.3 of the MGC software, the system returns a message similar to the following:
Media Gateway Controller - MGC-01 2000-04-05 08:11:02 M RTRV "CFM-01:RUNNING" "ALM-01:RUNNING" "MM-01:RUNNING" "AMDMPR-01:RUNNING" "CDRDMPR-01:RUNNING" "DSKM-01:RUNNING" "MMDB-01:RUNNING" "POM-01:RUNNING" "MEASAGT:RUNNING" "OPERSAGT:RUNNING" "PROVSAGT:RUNNING" "MGCP-1:RUNNING " "Replic-01:RUNNING " "ENG-01:RUNNING " "IOCM-01:RUNNING " "TCAP-01:RUNNING " "FOD-01:RUNNING " "EISUP-1:RUNNING " "SS7-A-1:RUNNING " "LOG-01:RUNNING "
This message shows the status of all processes.
For version 7.4 and up of the MGC software, the system returns a message similar to the following:
Media Gateway Controller - MGC-04 2000-04-05 08:06:03 M RTRV "CFM-01:RUNNING ACTIVE" "ALM-01:RUNNING ACTIVE" "MM-01:RUNNING ACTIVE" "AMDMPR-01:RUNNING ACTIVE" "CDRDMPR-01:RUNNING ACTIVE" "DSKM-01:RUNNING IN N/A STATE" "MMDB-01:RUNNING IN N/A STATE" "POM-01:RUNNING ACTIVE" "MEASAGT:RUNNING ACTIVE" "OPERSAGT:RUNNING ACTIVE" "PROVSAGT:RUNNING ACTIVE" "MGCP-1:RUNNING IN N/A STATE" "Replic-01:RUNNING ACTIVE" "ENG-01:RUNNING ACTIVE" "IOCM-01:RUNNING ACTIVE" "TCAP-01:RUNNING IN N/A STATE" "FOD-01:RUNNING IN N/A STATE" "EISUP-1:RUNNING IN N/A STATE" "SS7-A-1:RUNNING IN N/A STATE" "LOG-01:RUNNING IN N/A STATE" ;
This message shows the status of all processes.
This section contains the recommended startup procedure for the Cisco Signaling Link Terminal (SLT).
|
Note In this section, it is assumed that the Cisco SLT has been correctly installed and configured and that the correct software version is installed. If you are experiencing problems, see "Troubleshooting Cisco SLT Signaling," for detailed information. |
After you have installed the Cisco SLT, connect the power cable to the rear panel power connector and the power source, and set the power switch to the ON (|) position. The Power LED on the front panel should be on and the fan should be operating.
This section contains the recommended startup procedure for the Catalyst 5500 LAN switches.
|
Note In this section, it is assumed that the Catalyst 5500 has been correctly installed and configured and that the correct software version is installed. If you are experiencing problems, see "Troubleshooting MSR Signaling," for detailed information. |
To start the Catalyst 5500, complete the following steps:
Step 2 Turn the power supplies on (|). During the boot process, observe the following:
Step 3 Press Return at the Enter Password prompt to access the console command line.
The following sections contain the recommended shutdown procedures for each component of the solution. These procedures assume that the component has been correctly installed, configured, and provisioned in accordance with the instructions provided in the relevant documentation.
To shut down the Cisco MGC, simply power off the system. The system switch of the Cisco MGC is a rocker, momentary contact switch that functions as a standby device only, controlling logic circuits that enable power module output.
|
Caution Prior to turning off system power, exit from the operating system. Failure to do so might result in data loss. |
To power off the system, complete the following steps:
Step 2 Back up system files and data prior to shutdown.
Step 3 Halt the operating system.
Step 4 Momentarily set the front panel power switch to the STBY position until the system powers down.
Step 5 Verify that the POWER LED is off.
Step 6 Remove the input power connector from the power inlet.
|
Caution Regardless of the position of the ON/STBY switch, where an AC or DC power cord remains connected to the system, voltage is always present within the power supply. |
To shut down the Cisco SLTs, simply set the power switches to the OFF (0) position.
When the power switches are in the OFF (0) position, the power LEDs on the front panels should be off and the fans should not be operating.
To shut down the Catalyst 5500, simply set the power switches to the OFF (0) position.
When the power switches are in the OFF (0) position, the LEDs on the power supplies should be off and the fan assembly should not be operating.
Posted: Mon Aug 28 10:31:29 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.