- Introduction to Cisco BAMS
- Setup and Installation
- Provisioning BAMS
- Using MML Commands
- Using BAMS Tag IDs
- Configuring BAMS for BAF Output
- Configuring BAMS for ASCII Output and Measurements
- Configuring BAMS for P01 Output
- Configuring BAMS for NICS Output
- Configuring BAMS for 1110 Binary Output
- Configuring BAMS for QoS Output
- Obtaining Measurements
- Troubleshooting Cisco BAMS
- Upgrading to BAMS Release 3.30
- Backing up and Restoring BAMS
- Installing Solaris 10 Version 0708-V02 on Sun Netra T5220
- Introduction
- Starting and Stopping BAMS
- MML Commands
- chgno—Change Number
- clr-alm—Clear Alarm
- dialog—Dialog
- get-nodenames—Get Node Names
- h—History
- prov-add—Provision Add
- prov-cpy—Provision Copy
- prov-diff—Provision Compare
- prov-dlt—Provision Delete
- prov-dply—Provision Deploy
- prov-ed—Provision Edit
- prov-exp—Provision Export
- prov-rtrv—Provision Retrieve
- prov-sta—Provision Start
- prov-stp—Provision Stop
- prov-sync—Provision Synchronize
- quit—Quit
- r—Repeat
- rtrv-alms—Retrieve Alarms
- rtrv-circuit—Retrieve Circuits
- rtrv-configs—Retrieve Configuration
- rtrv-file—Retrieve File
- rtrv-ne—Retrieve Network
- rtrv-session—Retrieve Session
- rtrv-softw—Retrieve Software
- rtrv-syslog—Retrieve Syslog
- set-alm—Set Alarm
- set-node—Set Node
- set-nodename—Set Node Name
- sta-softw—Start Software
- stp-softw—Stop Software
- sw-ovr—Switch Over
Using MML Commands
Introduction
This chapter provides general reference information to help you understand how to operate the Cisco Billing and Measurements Server (BAMS) using Man-Machine Language (MML) commands. See Chapter 5 "Using BAMS Tag IDs" for the information about the tag IDs that you use in conjunction with MML commands to modify BAMS tables.
Note MML commands are differentiated from the surrounding text by being set in a Courier typeface. This makes them appear as they would on a computer screen. User input is shown in a bold font, and system responses are shown in a plain font. Text strings that you enter with MML commands are enclosed in quotes. Integers are shown without quotes. |
Command Notation
The command notation follows the Backus-Naur conventions.
Command Syntax
The command syntax follows the Bellcore TL1 conventions.
Starting and Stopping BAMS
The following sections describe the system-level MML commands that you use to start and stop BAMS.
Starting the System
To start the system from the MML system prompt, use the sta-softw (start software) command.
Example:
sta-softw
or start_system (from UNIX)
Stopping the System or OOS
To stop the system or bring it out-of-service (OOS), use the stp-softw (stop software) command.
Example:
stp-softw::confirm
or
stop_system (from UNIX)
Starting an MML Session
To start an MML session, and to get information about MML commands, perform the following steps:
Step 1 Log in to BAMS using your user ID and password.
When MML is started, the system prompt changes to mml:sys>.
The system is now ready to accept command-line instructions.
Note This is an alternate method for starting the command-line interface: In the BAMS bin directory, type mml in lowercase letters at the UNIX system prompt. Certain environment variables must be defined before MML can run. To define these variables, run . sym_defs in the profile of authorized users. The UNIX prompts and scripts follow the conventions for the UNIX Korn shell. |
Step 2 Type help.
The system displays a list of available MML commands. One screen of information is presented. Press Enter to display additional information.
These MML commands are discussed in more detail in the following sections.
Help—Help Command
Note Variables such as tag ID, field name, and so on, are shown in brackets. |
Note Strings must be enclosed in quotes, for example "string". Anything enclosed in brackets, for example [:command name] is an option. Colons are used to separate major command components, for example the command name from the tag ID, and the tag ID from the field name. Fields are separated by commas. When modifying field name values, do not enter spaces before or after the equal sign (=) or commas. |
command name:?:—Help on Tag IDs
Note In the preceding example, the specified command displays three valid tag IDs at the system level prompt. When a node is set, the tag IDs are displayed, as shown in the example below: mml:1:boston>prov-add:?: Billing and Measurements Server - BAMS-00 2004-09-22 11:26:35 B COMPLD ZONE-INFO TRUNKGRP ALM-PARMS BIN1110 COUNTRY MAPTYPE NODEPARMS NPANXX P01FILTER POLL RATING-TYPE RATE-EXC SIGPATH SKIPCDB SKIPCDE SWITCHINFO TCA-TBL TOLLFREE TKGPREFIX ; |
command name:tagID:?—Help on Field Names
Note In the example above, the specified command and tag ID display the field names for the MSC-THRES table. See the "Tag IDs and Field Names" section for a description of the fields in each BAMS table. |
MML Session Logs
The /opt/CiscoBAMS/data/logs directory contains daily MML session logs.
The log contains the time stamp of all user activity on BAMS and can be used for audits and troubleshooting.
MML Commands
To use the Man-Machine Language (MML) commands, define your user profile by typing .sym_defs in the /opt/CiscoBAMS/bin directory. Next, type mml to start the MML program. The UNIX system prompt changes to mml:sys>
and allows you to enter MML commands, which are listed in the following sections.
chgno—Change Number
clr-alm—Clear Alarm
Purpose |
Clears a previously set alarm that was written to the alarm history file. These alarms are generally set for test purposes, for example, to test the alarm trapping. This command sends an alarm trap clear to the SNMP agent. (For details about setting alarms, see the "set-alm—Set Alarm" section.) |
Format |
clr-alm:taskname:msgnumber="nnn"[,msgtext="message_text"] |
Description |
The value of taskname is any valid BAMS task name. The value of msgnumber can be any three-digit number. This number corresponds to the number of the message to be cleared. For ACC227 and POL402 alarms, you need to specify the full msgtext value to clear the alarm, because the message text for these alarms can vary. For ACC227, the msgtext includes the timestamp. |
Example |
mml:3>clr-alm:MSC:msgnumber="030" mml:3>clr-alm:POL:msgnumber="402",msgtext="Cannot connect to unit bams0-a" mml:3>clr-alm:ACC:msgnumber="227",msgtext="TTL CALL ROUTING III, TG1, 0 is equal to 0 @ 20021102220000 UTC" Billing and Measurements Server - BAMS-00 2004-09-08 14:11:09 B COMPLD ; |
Note For more information on the field names, refer to the "Updating the Poll Table" section. |
dialog—Dialog
get-nodenames—Get Node Names
h—History
prov-add—Provision Add
prov-cpy—Provision Copy
prov-diff—Provision Compare
Note If two (or more) tables are not identical across units, you will receive a message similar to the following: /* Table <table name> DOES NOT MATCH across BAMS units. Examine this table on both BAMS units. Execute prov-sync from correct unit. */ After you determine which BAMS unit has the correctly configured table, execute the prov-sync command for the appropriate node of the correctly configured BAMS unit. For more information, see "prov-sync—Provision Synchronize" section. |
prov-dlt—Provision Delete
prov-dply—Provision Deploy
Purpose |
Implements changes specified during an active provisioning session. |
Format |
prov-dply::[srcver=dirname] |
Description |
The value of dirname is the directory name; if you are in a provisioning session, you can deploy another session from within the active directory. prov-dply:: copies the changes in the current provisioning session to the active session (directory). If a directory name is specified with the prov-dply command, the files in that directory are copied to the active session. Note When you execute a prov-dply command in a redundant BAMS configuration, all the tables at the same level (node or system) are synchronized with the remote unit (i.e., they are transferred to that unit). This is the same behavior as when you execute the prov-sync command. The following message indicates that an MML table has been successfully transferred to the remote BAMS unit: |
Example |
mml:2>prov-dply::srcver=test Billing and Measurements Server - BAMS-00 2004-09-08 11:29:15 B COMPLD ; |
Note When you execute prov-dply at the node level, if the values to be provisioned for the NODEPARMS parameters nailed-cfg and interval-minutes are different from those in the current active configuration, the processing tasks for this node automatically restart so that these parameter changes can take effect. The restart of the node tasks generates MGR801 alarms, which indicate that certain processes are being terminated and restarted. Since changing these parameters has a significant effect on how the data is processed, the measurements data produced might show some incongruities with previously generated measurements data. |
prov-ed—Provision Edit
prov-exp—Provision Export
prov-rtrv—Provision Retrieve
prov-sta—Provision Start
prov-stp—Provision Stop
prov-sync—Provision Synchronize
quit—Quit
Purpose |
Quits the MML session. |
Format |
quit |
Description |
none |
Example |
mml:sys>quit Billing and Measurements Server - BAMS-00 2004-09-22 14:12:03 |
r—Repeat
rtrv-alms—Retrieve Alarms
rtrv-circuit—Retrieve Circuits
This command is only available at node level, and only on systems that have been configured in PGW Dynamic Mode (i.e., where PGW_DYNAMIC_UPDATE=TRUE). For more information, see the "Setting the PGW Dynamic Update Mode" section.
rtrv-configs—Retrieve Configuration
rtrv-file—Retrieve File
rtrv-ne—Retrieve Network
rtrv-session—Retrieve Session
rtrv-softw—Retrieve Software
rtrv-syslog—Retrieve Syslog
set-alm—Set Alarm
Purpose |
Generates an alarm message. Use this command to set a test alarm that is written to the syslog. (For details about clearing alarms, see the "clr-alm—Clear Alarm" section.) |
Format |
set-alm:taskname:msgnumber=nnn,level=n |
Description |
The value of taskname is any valid BAMS task name. The value of nnn is a three-character message number. The value of n is a valid single-character threshold level (0, 1, or 2). Note This command works only for alarms maintained in the alarmslist.CTL file in the /opt/CiscoBAMS/files directory. |
Example |
mml:3>set-alm:MSC:msgnumber="030",level=0 Billing and Measurements Server - BAMS-00 2004-09-08 14:13:13 B COMPLD ; |
set-node—Set Node
set-nodename—Set Node Name
sta-softw—Start Software
stp-softw—Stop Software
sw-ovr—Switch Over
Purpose |
Forces a manual rotation of the BAMS unit designated to poll the VSC. (You can execute this command only on the active polling unit.) |
||
Format |
sw-ovr |
||
Description |
You can use the sw-ovr command to rotate polling from the active BAMS unit to the standby unit in the event of a switch failover. The command is executed immediately on the local BAMS unit. On the remote BAMS unit, the rotation takes effect at the next poll attempt. Poll attempts are typically set at 5-minute intervals. |
||
|
|||
No tag IDs are required, just the command verb. Note Successful execution of this command causes a POL105 message to be written to the syslog (see "Troubleshooting Cisco BAMS"). |
|||
Example |
mml:sys>sw-ovr Billing and Measurements Server - BAMS-00 2004-09-22 13:26:19 B COMPLD ; |