This command displays the Cisco VVB versions on the active partition and the inactive partition. The inactive version is displayed only if the inactive partition is available.

Command syntax

show vvb version

Requirements

Level privilege: 0

Command privilege level: 0

Allowed during upgrade: Yes

Example

admin:show vvb version 
 Active VVB Version: 11.0.0.95000-245
 Inactive VVB Version: NA
Command successful. 

This command displays the various components in Cisco VVB for which tracing can be turned on or off from CLI commands. This command is useful when you need the list of components to modify the trace settings of Cisco VVB.

Command syntax

show vvb components

Requirements

Level privilege: 0

Command privilege level: 0

Allowed during upgrade: Yes

Example

admin:show vvb components
Various components are as follows -

 AppAdmin
 Engine

This command displays the various subcomponents in specific Cisco VVB component. This command is useful when you need the list of subcomponents to modify the trace settings of Cisco VVB.

Command syntax

show vvb subcomponents component [options]

Options

• component—(Mandatory) Component such as Engine. For example, some of the VVB subcomponents for 'Engine' component are:

  • APP_MGR

  • ARCHIVE_MGR

  • BOOTSTRAP_MGR

  • CFG_MGR

  • CHANNEL_MGR and so on

• page—Displays the output one page at a time

Requirements

Level privilege: 0

Command privilege level: 0

Allowed during upgrade: Yes

Example

admin:show vvb subcomponents Engine

This command displays the names and trace levels of the various Cisco VVB components and subcomponents. If the optional component is specified, then the trace settings of all the subcomponents of the specified component are displayed. If both the optional component and subcomponent are specified, then the trace settings of the specified subcomponent of the specified component are displayed.

Command syntax

show vvb trace levels [options]

Options

• Component—Displays the trace levels of all the subcomponents of this component

• Sub-component—Displays the trace levels of this subcomponent for the specified component. The trace levels can be displayed only if the component was specified

• page—Displays the output one page at a time

• file—Stores the output to a file instead of showing it on the console. The name of the file is displayed after the completion of the command

  Requirements

Level privilege: 0

Command privilege level: 0

Allowed during upgrade: Yes

Example

admin:show vvb trace levels Engine SS_VB 
 Trace settings for component "Engine" and module 'SS_VB' are
  ALARM = true
  DEBUGGING = false
  XDEBUGGING1 = false
  XDEBUGGING2 = false
  XDEBUGGING3 = false
  XDEBUGGING4 = false
  XDEBUGGING5 = false

 Command successful.

This command shows the trace file size for the specified component.

Command syntax

show vvb trace file size [component]

Options

component—(Mandatory) Component such as Engine

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: Yes

Example

admin: show vvb trace file size Engine
Trace file size for Engine is 3000000 bytes.

Command Successful.

This commands shows the trace file count for the specified component, which is the maximum number of trace files. The new file overwrites the older files.

Command syntax

show vvb trace file count [component]

Options

component—(Mandatory) Component such as Engine

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: Yes

Example

admin: show vvb trace file count Engine
Trace file count for Engine is 300.

Command Successful.

This command shows the currently allocated browser cache size in KB.

Command syntax

show vvb cache browser_cache_size

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:show vvb cache browser_cache_size   
  1000 KB
 Command successful.

This command shows the DOM cache capacity.

Command syntax

show vvb cache dom_cache_capacity

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:show vvb cache dom_cache_capacity  
  64 entries
 Command successful.

This command shows if the browser cache is enabled where True is enabled and False is disabled.

Command syntax

show vvb cache enable_browser_cache

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:show vvb cache enable_browser_cache  
  true
 Command successful.

This command shows if the browser cache trace is enabled.

Command syntax

show vvb cache enable_browser_cache_trace

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:show vvb cache enable_browser_cache_trace  
  false
 Command successful.

This command shows the extensions used for Cisco VVB.

Command syntax

show vvb cache extensions

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:show vvb cache extensions
  jsp
  ircgi
  nohead
  testingExt
 Command successful.

This command shows the maximum cache size of a resource. If the size of the resource is more than this limit, resource will not be added to the cache.

Command syntax

show vvb cache max_file_size

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:show vvb cache max_file_size
 1000 KB

 Command successful.

This command sets the default trace levels for all components and subcomponents in Cisco VVB. If the optional component is specified, it sets the default trace levels only for all the subcomponents of the specified component. If both the optional component and subcomponent are specified, it sets the default trace levels only for the specified subcomponent under the component.

Command syntax

set vvb trace defaults [component] [subcomponent]

Options

• Component—(Mandatory) Sets the default trace levels for all the subcomponents of this component. The various components are Engine and AppAdmin.

• Sub-component—(Optional) Sets the default trace levels for this subcomponent for the specified component. This trace level can be specified only if the component was specified preceding it.

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb trace defaults Engine 
SS_HTTP
Default traces restored successfully for the module.

This command sets the trace file size for the specified component.

Command syntax

set vvb trace file size [component] [size]

Parameters

component—(Mandatory) The component such as Engine

size—(Mandatory) Specifies the file size in bytes

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb trace file size engine 3145728
Trace file size for engine is set to 3145728 bytes.

This command sets the trace file count for the specified component, that is the maximum number of trace files after which older files will start getting overwritten.

Command syntax

set vvb trace file count [component] [no-of-files]

Arguments

• component—(Mandatory) The component such as Engine.

• no-of-files—(Mandatory) Specifies the number of files after which older files will get overwritten.

Requirements

Level privilege—1

Command privilege level—1

Allowed during upgrade—No

Example

admin:set vvb trace file count engine 300
Trace file count for engine is set to 300

Enables the specified logging level for the sub-component in the component mentioned in the command. The user can enter multiple levels of logging by separating them by commas.

After the completion of the command, a message is displayed showing the current log trace settings enabled.

Restart the Cisco VVB services for the trace changes to take effect.

Command syntax

set vvb trace enable [component] [sub-component] [level]

Options

component—(Mandatory) The component such as Engine

sub-component—(Mandatory) The subcomponent within the component such as SS_SIP within the Engine component.

Level—(Mandatory) The logging level which will be enabled. Tracing levels are Debugging, XDebugging1, XDebugging2, XDebugging2, XDebugging3, XDebugging4 and XDebugging5.

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example 1

admin:set vvb trace enable engine SS_VB debugging
 Trace for engine:SS_VB:debugging is enabled.
 Command successful.

Example 2

admin:set vvb trace enable engine SS_SIP XDEBUGGING1,XDEBUGGING2
Trace for engine:SS_SIP:XDEBUGGING1 is enabled
Trace for engine:SS_SIP:XDEBUGGING2 is enabled
Command successful.

Disables the specified logging level for the subcomponent in the component mentioned in the command. The user can enter multiple levels of logging by separating them by commas. You cannot use this command to turn off Alarm tracing.

After the completion of the command, a message is displayed showing the current log trace settings enabled.

Restart the Cisco VVB services for the trace changes to take effect.

Command syntax

set vvb trace disable [component] [sub-component] [level]

Options

Component—The component such as Engine.

Sub-component—The subcomponent within the component such as SS_SIP within the Engine component.

Level—(Mandatory) The logging level which will be disabled. Tracing levels are Debugging, XDebugging1, XDebugging2, XDebugging2, XDebugging3, XDebugging4 and XDebugging5. The tracing levels will also be available as part of the help of the command.

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example 1

admin:set vvb trace disable engine SS_VB debugging
 Trace for engine:SS_VB:debugging is disabled.
 Command successful.

Example 2

set vvb trace disable engine SS_SIP XDEBUGGING1,XDEBUGGING2
Trace for engine:SS_SIP:XDEBUGGING1 is disabled
Trace for engine:SS_SIP:XDEBUGGING2 is disabled
Command successful.

This command changes the security/SFTP password on Cisco VVB. In addition to changing the security password, it also changes the passwords of the internal Cisco VVB users.

Command syntax

set password user security

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set password user security   
Please enter the old password: ******
Please enter the new password: ******
Reenter new password to confirm: ******
WARNING:
Please make sure that the security password on the publisher is changed first.
The security password needs to be the same on all cluster nodes,
including the application server, therefore the security password on all nodes
need to be changed.

After changing the security password on a cluster node, please restart that node.

Continue (y/n)?y

Please wait...

Command successful.

This command enables or disables the browser cache where True is enabled and False is disabled.

Command syntax

set vvb cache enable_browser_cache [Option]

Parameters

Boolean—(Mandatory) Enter boolean value true or false.

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb cache enable_browser_cache false 
 Command successful.

This command sets the cache size in KB. Setting cache size to 0 disables the cache. Disabling cache does not add new entries to the cache. However, existing cache entries can be reused until they are expired.

Command syntax

set vvb cache browser_cache_size [size_in_KB]

Requirements

• size_in_KB —Cache Size in KB

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb cache browser_cache_size 1000

 Command successful.

Note	If this command is issued while browser cache is disabled (enable_browser_cache = false), a warning message like this will be shown on console: 'Please note that browser cache is currently disabled, so this operation will take effect once caching is enabled again.'

This command enables or disables the browser cache trace.

Command syntax

set vvb cache enable_browser_cache_trace [Option]

Parameters

Boolean—(Mandatory) Enter boolean value true or false.

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb cache enable_browser_cache_trace true
  Command successful.

Note	If this command is issued while browser cache is disabled (enable_browser_cache = false), a warning message like this will be shown on console: 'Please note that browser cache is currently disabled, so this operation will take effect once caching is enabled again.'

This command is used to create new extensions.

Command syntax

set vvb cache extensions [Name]

Parameters

Name—(Mandatory) Enter the extension name.

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb cache extensions newExtension
 Command successful.

Note	If this command is issued while browser cache is disabled (enable_browser_cache = false), a warning message like this will be shown on console: 'Please note that browser cache is currently disabled, so this operation will take effect once caching is enabled again.'

This command sets the cache size in KB. Setting cache size to 0 disables the cache. That means that new entries will not be added to the cache; however, existing cache entries will be reused until they are expired.

Command syntax

set vvb cache browser_cache_size [size_in_KB]

Options

• size_in_KB —Cache Size in KB

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:set vvb cache browser_cache_size 1000

 Command successful.

Note	If this command is issued while browser cache is disabled (enable_browser_cache = false), a warning message like this will be shown on console: 'Please note that browser cache is currently disabled, so this operation will take effect once caching is enabled again.'

This command allows you to enable, disable, create, and check the status of a remote account.

Command Syntax

• utils remote_account status

• utils remote_account enable

• utils remote_account disable

• utils remote_account create username life

Arguments

• username—Specifies the name of the remote account. The username can contain only lowercase characters and must be more than six characters long.

• life—Specifies the life of the account in days. After the specified number of days, the account expires.

Usage Guidelines

A remote account generates a pass phrase that allows Cisco support personnel to access the system for the specified life of the account. You can have only one remote account that is enabled at a time.

Example

admin:utils remote_account status
Remote Support
Status         : disabled
Decode Version : 2

This command allows you to install upgrades and Cisco Option Package (COP) files from both local and remote directories.

Command syntax

utils system upgrade [Options]

Options

initiate—Starts a new upgrade wizard or assumes control of an existing upgrade wizard. The wizard prompts you for the location of the upgrade file for Cisco VVB.

status—Displays status of the upgrade

cancel—Stops the upgrade process

Example

admin:utils system upgrade initiate

Warning: Do not close this window without first canceling the upgrade.

Source:

 1) Remote Filesystem via SFTP
 2) Remote Filesystem via FTP
 3) Local DVD/CD
 q) quit

Please select an option (1 - 3 or "q" ):

This command allows you to check whether the database was corrupted after an unsuccessful switch version due to a restart in the middle of a switch version attempt. The command displays the status of last switch version. If there is a database backup available that can be restored, it prints the time stamp of the backup and display the CLI command utils vvb switch-version db-recover to recover from this backup.

Command Syntax

utils vvb switch-version db-check

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:utils vvb switch-version db-check
vvb DB was found to be corrupted.
Last switch version was aborted at 05/29/2012 16:18:07
05/29/2012 16:18:07|root:Switch Version 9.0.1.10000-41 to 9.0.10000-42
Aborted
There is a VVB backup with timestamp 2012-05-29 16:16:19.000000000 +0530
that was taken during a prior switch version.
!!!WARNING!!! IF YOU CHOOSE TO RECOVER FROM THIS BACKUP, ANY CHANGES DONE
TO THE DATABASE AFTER THE TIMESTAMP OF THIS BACKUP WILL BE LOST.
You can run the CLI command "utils vvb switch-version db-recover" to
restore the DB from this backup.

This command first checks whether the database was corrupted after an unsuccessful switch version due to the restart in the middle of a switch version attempt. The command displays the status of the last switch version. If there is a database backup available that can be restored, it prints the time stamp of the backup and offer an option to restore the database from this backup. If the restore option is chosen, the command completes after restoring the database from this backup and bringing up all the services.

Command Syntax

utils vvb switch-version db-recover

Requirements

Level privilege: 1

Command privilege:1

Allowed during upgrade: No

Example

admin:utils vvb switch-version db-recover
VVB DB was found to be corrupted.
Last switch version was aborted at 05/29/2012 16:18:07
05/29/2012 16:18:07|root:Switch Version 9.0.1.10000-42 Aborted
There is a VVB DB backup with timestamp 2012-05-29 16:16:19:000000000
+530 that was taken during a prior switch version.
!!!WARNING!!! IF YOU CHOOSE TO RECOVER FROM THIS BACKUP, ANY CHANGES DONE
TO THE DATABASE AFTER THE TIMESTAMP OF THIS BACKUP WILL BE LOST.
Are you sure you want to continue?
Continue (y/n)?y
This operation may take a few minutes to complete. Please wait

Run this command to enable Cisco VVB administration security filter settings.

Command syntax

utils vvb security_filter enable

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

utils vvb security_filter enable

admin:utils vvb security_filter enable
The status of security filter is: enabled
Please restart Cisco VVB service using
'utils service restart Cisco Tomcat' for changes to take effect.

Run this command to disable Cisco VVB administration security filter settings.

Command syntax

utils vvb security_filter disable

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:utils vvb security_filter disable
The status of security filter is: disabled
Please restart Cisco VVB service using
'utils service restart Cisco Tomcat' for changes to take effect.

Run this command to check the status of Cisco VVB administration security filter flag.

Command syntax

utils vvb security_filter status

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:utils vvb security_filter status
vvb security filter is :enabled

This command shows all the services running on Cisco VVB server.

Command syntax

utils service list

Requirements

Level privilege: 1

Command privilege level: 1

Allowed during upgrade: No

Example

admin:utils service list
Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STARTED]
Cisco SCSI Watchdog [STARTED]
Service Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
Cisco AMC Service[STARTED]
Cisco Audit Event Service[STARTED]
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco Certificate Change Notification[STARTED]
Cisco Certificate Expiry Monitor[STARTED]
Cisco RIS Data Collector[STARTED]
Cisco RTMT Reporter Servlet[STARTED]
Cisco Syslog Agent[STARTED]
Cisco Tomcat[STARTED]
Cisco Tomcat Stats Servlet[STARTED]
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STARTED]
Administration[STARTED]
CVD Dependent Webapp[STARTED]
Cluster View Daemon[STARTED]
Configuration API[STARTED]
Database[STARTED]
Engine[STARTED]
Perfmon Counter Service[STARTED]
SNMP Java Adapter[STARTED]
Serviceability[STARTED]
Voice Subagent[STARTED]
WebServices[STARTED]
Cisco Unified Serviceability RTMT[STARTED]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
Platform Administrative Web Service[STARTED]
SNMP Master Agent[STARTED]
SOAP -Log Collection APIs[STARTED]
SOAP -Performance Monitoring APIs[STARTED]
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Cisco Serviceability Reporter[STOPPED] Service Not Activated
Primary Node =true
Command successful.

This command lists prompt files created for various locales.

Command syntax

file vvb list prompt_file file_spec [options]

Arguments

file-spec—(Mandatory) The file to view. File-spec can contain asterisks (*) as wildcard.

Options

page—Pauses output

detail—Shows detailed listing

reverse—Reverses sort order

date—Sorts by date

size—Sorts by size

Requirements

Level privilege: 0

Command privilege level: 1

Allowed during upgrade: No

Example

admin:file vvb list prompt_file system/default/vb detail
no such file or directory can be found
admin:file vvb list prompt_file system/G711_ULAW/default/vb detail
09 May,2017 22:07:43       32,110  ringback.wav
dir count = 0, file count = 1

The platform show commands supported by Cisco VVB are:

• show account

• show accountlocking

• show cli

• show date

• show diskusage

• show hardware

• show login

• show media stream

• show myself

• show network *

• show open *

• show password *

• show process *

• show registry *

• show risdb

• show sessions max limit

• show stats io

• show status

• show tech

• show timezone

• show tls client min-version

• show tls server min-version

The platform set commands supported by Cisco VVB are:

• set cli

• set commandcount

• set date

• set logging

• set password user admin

• set timezone

• set webapp session timeout

• set tls client min-version

• set tls server min-version

• set network hostname

• set network ip eth0 <ip_address> <netmask> <default gateway>

The platform utils commands supported by Cisco VVB are:

• utils auditd *

• utils iostat

• utils iothrottle

• utils network capture

• utils network ping

• utils reset_application_ui_administrator_password

• utils service *

The platform file commands supported by Cisco VVB are:

• file delete *

• file dump *

• file get *

• file list *

• file search *

• file tail

• file view

• unset network *

• delete process