Cisco Cisco Expressway Maintenance Manual
2.
Upload the software image using SCP/PSCP.
—
For the System platform component:
Upload to the /tmp folder on the system. The target name must be /tmp/tandberg-image.tar.gz, for
example:
example:
scp s42700x8_1_0.tar.gz root@10.0.0.1:/tmp/tandberg-image.tar.gz
—
For other components:
Upload to the /tmp/pkgs/new/ folder on the system, preserving the file name and extension, for example:
scp root@10.0.0.1:/tmp/pkgs/new/vcs-lang-es-es_8.1_amd64.tlp
3.
Enter the root password when prompted.
The software installation begins automatically. Wait until the software has installed completely. This should
not take more than five minutes.
The software installation begins automatically. Wait until the software has installed completely. This should
not take more than five minutes.
4.
If you have upgraded the System platform component, log in to the Expressway, either using the web
interface or CLI, and reboot the Expressway. After about five minutes the system will be ready to use.
interface or CLI, and reboot the Expressway. After about five minutes the system will be ready to use.
Note:
if you make any further configuration changes before rebooting, those changes will be lost when the system
restarts, so you are recommended to reboot your system immediately.
Configuring Logging
The Expressway provides syslogging features for troubleshooting and auditing purposes.
The Event Log is a rotating local log that records information about such things as calls and messages sent and
received.
received.
The Expressway's logging options are configured on the Logging page (Maintenance > Logging) where you can:
■
to change the depth of event information recorded locally
■
■
toggle
Call Detail Records
■
addresses
■
filter the events sent to each remote syslog server by severity
■
Changing Event Log Verbosity
Control the local log verbosity by setting the Local event log verbosity between 1 and 4.
All events have an associated level in the range 1-4, with Level 1 Events considered the most important. The table
below gives an overview of the levels assigned to different events.
below gives an overview of the levels assigned to different events.
Level Assigned events
1
High-level events such as registration requests and call attempts. Easily human readable. For example:
■
call attempt/connected/disconnected
■
registration attempt/rejected
Note that endpoints or other devices cannot register to the Expressway. Registration requests will be
rejected and will be logged with 'License limit exceeded' messages.
rejected and will be logged with 'License limit exceeded' messages.
2
All Level 1 events, plus:
■
logs of protocol messages sent and received (SIP, H.323, LDAP and so on) excluding noisy
messages such as H.460.18 keepalives and H.245 video fast-updates
messages such as H.460.18 keepalives and H.245 video fast-updates
184
Cisco Expressway Administrator Guide