Cisco GoQAM Información técnica descargar pdf (Pagina 41)

Command Syntax

4025561 Rev

*/* MODULE> chassis 20 slot *

20/* MODULE> show monitor outpwr

MODID NAME VALUE UNITS

20/05 OutPwr -5.33429 dBm

20/07 OutPwr 10.086 dBm

20/13 OutPwr -6.15736 dBm

SUCCESS!

20/* MODULE>

 In the first line above, the operator changes from CLI command mode to Module

command mode and specifies chassis 20, any (*) slot.

 In the next line, the prompt (20/* MODULE>) has changed to reflect the new

command mode and chassis specification.

 At this prompt, the operator enters the show command followed by monitor and

outpwr. These parameters specify that the response should include only

modules for which OutPwr is a monitored parameter.

 In the next four lines, the response identifies each module by its chassis and slot

location (e.g., 20/05) and displays the current output power level in dBm.

In the following example, a craft operator uses the wildcard character to check all

monitored parameters whose name contained pwr:

CLI> module chassis 20 slot *

20/* MODULE> show monitor *pwr*

MODID NAME VALUE UNITS

20/05 OutPwr 8.3 dBm

20/07 OutPwr 5.91542 dBm

20/14 OutPwrA 18.9057 dBm

20/14 OutPwrB 18.8904 dBm

SUCCESS!

20/* MODULE>

The pattern matching is caseless, so the parameters OutPwr, InPwr, and InPwr2 are

included in the response even though a lowercase P was used in the command line.

Wildcards default to MS Windows filename pattern matching format, where ?, *,

and [x-y] have special meaning. This format can be adjusted using the Terminal

command Pattern to use POSIX regex wildcards. See Terminal Mode Commands (on

page

157) for additional information.

Note: Wildcards are never allowed anywhere in a Set command.

1 2 ... 36 37 38 39 40 41 42 43 44 45 46 ... 307 308

Sin comentarios

Cisco GoQAM Información técnica Pagina 41