1 Monitoring the VDS-OS

1 Monitoring the VDS-OS
CH AP TE R
1
Monitoring the VDS-OS
The VOSM provides tools that can be used for system monitoring and system diagnostics. The topics
covered in this chapter include:
•
System Monitoring, page 1-1
•
Device Monitoring, page 1-8
•
Origin Service Monitoring, page 1-18
•
Viewing Statistics, page 1-20
•
Log Files, page 1-22
•
Transaction Logs, page 1-23
System Monitoring
System monitoring consists of the following:
•
System Status
•
System Home Page
•
System Audit Logs
•
System Port Numbers
System Status
The VOSM displays the system status in the System Status bar that is located above the navigation tabs
in every window. The System Status bar presents the overall device and service health of the system. You
can use this feature to monitor devices and services in your VDS-OS network. The System Status bar
helps you immediately identify any problems on the network, allowing you to act and respond to
problems quickly.
The system status reporting mechanism uses four alarm lights to identify problems that need to be
resolved. Each light represents a different alarm level, as follows:
•
Green—No alarms (the system is in excellent health)
•
Yellow—Minor alarms
•
Orange—Major alarms
•
Red—Critical alarms
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-1
Chapter 1
Monitoring the VDS-OS
System Monitoring
When you roll your mouse over an alarm light in the System Status bar, a pop-up message provides
further details about the device, origin service, or license status. See Figure 1-1.
The icon next to the System Status either displays a yellow triangle with an exclamation mark or a green
circle with a check mark. The yellow triangle indicates the alarms and alerts count includes only the
unacknowledged alarms and alerts. The green circle with a check mark indicates all alarms and alerts
are counted, whether they are acknowledged or unacknowledged.
Figure 1-1
System Status Bar
When you click the alarm light or the link next to the alarm light, a new window opens (Troubleshooting
Devices or Troubleshooting Services), listing the individual devices or origin services that need
attention.
Figure 1-2
Troubleshooting Device Window
Troubleshooting Window Pop-Up Menus
When you roll your mouse over an item under the Alarm Information column in the Troubleshooting
window, the Troubleshooting Tools menu is displayed. The Troubleshooting Tools menu provides links
to all the diagnostic tools, troubleshooting tools, and monitoring applications for troubleshooting and
resolving the problem. Figure 1-2 shows the Troubleshooting Tools menu for device alarms.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-2
OL-28084-04
Chapter 1
Monitoring the VDS-OS
System Monitoring
-Table 1-1 describes the icons for the Troubleshooting window.
Table 1-1
Icon
Troubleshooting Window Icons
Function
Create a filtered table. Filter the alarms by severity or device type.
View all alarms. Click this icon to view all alarms after you have
created a filtered table.
Refresh the table
Print the current window.
View acknowledged alarms.
You can sort the Troubleshooting table by clicking any column heading displayed in blue. The first time
the column heading is clicked, the table is sorted by that column in increasing order. If the column
heading is clicked again, the table is sorted by that column in decreasing order.
Note
If there is more than one alarm for a device, and the Troubleshooting window is sorted by device, then
the device is only listed once for multiple alarms associated with it. The same is true for service alarms.
Troubleshooting Window Acknowledge and Unacknowledge Alarms Function
The following procedure describes acknowledging and unacknowledging an alarm:
Step 1
To remove an alarm from the Troubleshooting window, check the check box for the alarm. The alarm is
moved to the Acknowledged Alarm window.
Step 2
To view the acknowledged alarms, click the View acknowledged alarms icon. The Acknowledged
Alarm window is displayed (Figure 1-3).
Figure 1-3
Step 3
Acknowledged Alarms Window
To unacknowledge an alarm, check the check box for the alarm. The alarm is returned to the
Troubleshooting window.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-3
Chapter 1
Monitoring the VDS-OS
System Monitoring
Step 4
To view the Troubleshooting window again, click the Back (blue left arrow) icon.
Device Alarms
Device alarms are associated with device objects and pertain to applications and services running on
SEs, SRs, and VOSMs. Device alarms are defined by the reporting application or service. For example,
the SR raises an alarm for an SE (the keepalive time-out alarm) if the SE has a Layer 3 failure. Device
alarms can also reflect reporting problems between the device and the VOSM. (See Table 1-2.)
Alarm thresholds are configured for each device. For more information, see the “Setting Service Monitor
Thresholds” section on page 1-52.
Table 1-2
Device Alarms for Reporting Problems
Alarm
Alarm
Severity
Device Status
Description
Device is offline
Critical
Offline
The device has failed to communicate with the
VOSM.
Device is pending
Major
Pending
The device status cannot be determined.
Device is inactive
Minor
Inactive
The device has not yet been activated or
accepted by the VOSM.
Device has lower
software version
Minor
Online
The device is not interoperable with the VOSM
because it has an earlier software version.
To troubleshoot a device from the System Status bar, do the following:
Step 1
In the System Status bar, click the Devices alarm light or click the Device link. The Troubleshooting
Devices window is displayed.
Step 2
In the Alarm Information column, hold your mouse over the alarm message until the Troubleshooting
Tools menu is displayed. See Figure 1-2.
Step 3
Click the troubleshooting tool you want to use. The link takes you to the corresponding page in the
VOSM. Table 1-3 describes the tools available for all device alarms.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-4
OL-28084-04
Chapter 1
Monitoring the VDS-OS
System Monitoring
Table 1-3
Troubleshooting Tools for Device Alarms
Item
Navigation
Description
Edit/Monitor Device
Devices home page
Displays Devices home page
Telnet to Device
Opens a Telnet window
Initiates a Telnet session using the
device IP address
Run Show Commands
Devices > Device > Monitoring >
Show/Clear Commands > Show
Commands
Displays device show command tool
Core Dump File
Devices > Device > Monitoring >
Core Dump Files
Displays a list of core dump files on
the device.
Update Software
Devices > Devices > Device Home > Displays a list of software files that
Update Software
have been uploaded to the VDS-OS.
Remote Storage Alarms
Storage alarms have two levels: major and minor. A minor alarm transits to a major alarm if it persists
for more than 60 seconds. All alarms are viewable by using the show alarm command and through the
Device alarms in the System Status bar.
Storage alarms are generated at two levels from each SE:
•
Storage server—Single alarm is generated for each storage server, and indicates that the SE could
not connect to the storage server within the timeout period (that is, the mount command timed out).
•
Origin service—Alarm is generated when an origin service fails to access one or more shares. A
different alarm is generated for each share. The storage server alarms also trigger origin service
alarms.
Service Alarms
Service alarms pertain to content problems and are associated with origin services. Service alarms are
raised by the VOSM based on content status reports, or by the SE health manager based on acquisition
and distribution errors.
If the same fault is reported by the content status and by the SE health manager, the VOSM reports both;
one appears as the true alarm and the other as an error. The VOSM does not correlate nor attempt to
consolidate the errors generated by the content status and by the SE health manager.
To troubleshoot service content issues from the System Status bar, do the following:
Step 1
In the System Status bar, click the Services alarm light or click the Service link. The Troubleshooting
Services window is displayed.
Step 2
In the Alarm Information column, hold your mouse over the alarm message until the Troubleshooting
Tools menu is displayed.
Step 3
Click the troubleshooting tool that you want to use. The link takes you to the corresponding page in the
VOSM.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-5
Chapter 1
Monitoring the VDS-OS
System Monitoring
System Home Page
The System Home page (Figure 1-4) provides overall system information on configuration and software
versions running on the VDS-OS devices. Clicking the links for devices and origin services and live
channels takes you to the corresponding table pages.
Note
The number of devices that have a lower version of software than the VOSM only compares the major
and minor release numbers (X.Y) of the software release number. The software release number consists
of X.Y.Z-b#, where X is the major release number, Y is the minor release number, Z is the maintenance
release number, and b# is the build number. Devices with a lower X.Y version than the VOSM do not
interoperate with the VOSM, and the VOSM does not send configuration updates to those devices. A
minor alarm is generated for the devices with a lower version of software.
Figure 1-4
System Home Page
System Audit Logs
The VOSM logs user activity in the system. The only activities that are logged are those that change the
VDS-OS network. This feature provides accountability for users actions (for example, which user did
what and when). Logged activities include the following:
•
Creation of VDS-OS network entities
•
Modification and deletion of VDS-OS network entities
•
System configurations
To view audit trail logs, do the following:
Step 1
Choose System > Logs > Audit Trail Logs. The Audit Log page is displayed. All logged transactions
in the VOSM are listed by date and time, user, actual transaction that was logged, and the IP address of
the machine that was used.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-6
OL-28084-04
Chapter 1
Monitoring the VDS-OS
System Monitoring
To determine the number of rows that you want to display, choose a number from the Rows
drop-down list.
Step 2
System Port Numbers
Information on all the protocols and ports used by the VDS-OS can be viewed on the Well Known Ports
page.
To view ports used by the VDS-OS, choose System > Well Known Ports. The Well Known Ports page
is displayed. Table 1-4 lists all ports listed on the Well Known Ports page.
To view all ports on one page, from the Rows drop-down list, choose All.
Table 1-4
Well Known Ports
Source Group
Destination Group
Source Destination
Protocol Port
Port
Purpose
Administrator
(PC)
VOSM
TCP
ANY
8443
Access to VOSM GUI from administrator PC
All Devices
All Devices
TCP
ANY
22
SSH
All Devices
All Devices
TCP
ANY
23
Telnet (disabled by default)
All Devices
NTP Servers
UDP
ANY
123
Query time servers
All Devices
NMS Servers
TCP
ANY
161
SNMP query or polling
All Devices
NMS Servers
UDP
ANY
162
SNMP trap
All Devices
Syslog Server
UDP
ANY
514
Syslog
Client
DNS Server/Proxy
UDP
ANY
53
DNS query for Service Router Fully-Qualified
Domain Name (SRFQDN) from client
Client
SR
TCP
ANY
80
HTTP request to Service Router from client
Client
SE
TCP
ANY
80
HTTP request to Service Engine from client
DNS
Server/Proxy
SR
UDP
ANY
53
DNS query for RRFQDN from DNS
server/proxy used by client
DNS
Server/Proxy
All Devices
UDP
ANY
1023-65535
DNS server responses to DNS query requests
SE
VOSM
TCP
ANY
443
VDS-OS management (notifications, updates,
queries)
SE
SE
TCP
ANY
80
HTTP request between Service Engines
SE
VOSM
UDP
ANY
2000
Service Engine to VOSM keepalives
SE
SR
UDP
ANY
2323
Service Engine to Service Router keepalives
SE
NFS NAS Server
TCP
ANY
2049
Mounting NFS shares
SR
VOSM
TCP
ANY
443
VDS-OS management (notifications, updates,
queries)
SR
VOSM
UDP
ANY
2000
Service Router to VOSM keepalives
VOSM
SE
TCP
ANY
443
VDS-OS management (notifications, updates,
queries)
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-7
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Table 1-4
Well Known Ports (continued)
Source Group
Destination Group
Source Destination
Protocol Port
Port
VOSM
SR
TCP
ANY
443
VDS-OS management (notifications, updates,
queries)
VOSM
VOSM
TCP
ANY
443
VDS-OS management (notifications, updates,
queries)
VOSM
VOSM
UDP
ANY
2000
VOSM to VOSM keepalives
Note
Purpose
The Destination Ports that have a port range indicate the possible ports that the Source Group could be
expecting to send traffic to and receive traffic from. The specific ports required to be open to receive and
send data depends on the Source Group configuration.
Device Monitoring
This section covers the following topics:
•
Devices Table
•
Devices Home Page
•
Using show, clear, and alarm Commands
•
Core Dump Files
•
CPU Utilization
For more detailed statistics on HTTP traffic, see the “Viewing Statistics” section on page 1-20.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-8
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Devices Table
The Devices Table page displays all devices registered in the VDS-OS network (Figure 1-5).
Figure 1-5
Devices Table Page
Table 1-5 describes the Device Table columns. You can sort the information in the table by clicking on
any column title. The table can be sorted in ascending or descending order for each column.
The table defaults to listing ten rows. You can change the number of rows by clicking the Rows
drop-down list. The bottom of the table lists the page number and the total number of pages, as well as
how many items are showing out of the total number of items.
Table 1-5
Device Table Columns
Column Heading
Description
Device Name
Host name of the device.
Type
Device type: SE, SR, VOSM (Primary), VOSM (Secondary).
IP Address
Primary IP address of the device.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-9
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Table 1-5
Device Table Columns (continued)
Column Heading
Description
Status
Status is one of the following:
Location
•
Online—Device has been activated through the VOSM and is able to send and
receive data and control traffic.
•
Offline—Device has failed to communicate with the VOSM.
•
Pending—Device status cannot be determined. The device could be in the
process of being activated by the VOSM
•
Offloading—Device is in the Server Offload state. See the Server Offload field
in Table 1-6 on page 1-10 for more information. To monitor the current traffic
on an SE during the Server Offload state, view the statistics for HTTP (see
Table 1-15 on page 1-21). After all HTTP traffic has finished, you can perform
maintenance or upgrade the software on the device. For information about
upgrading the software, see the “Upgrading the Software” section on page 1-4.
•
Online [Waiting for datafeed]—In some situations, the VOSM may receive
regular heartbeat messages, but not receive a datafeed message for a long time.
The Online [Waiting for datafeed] state indicates that the VOSM has not
received a datafeed message from this online device in the last 2.25 * polling
rate seconds. When the datafeed message is received, the state changes to
Online.
Location the device is assigned to.
Software Version Device software version.
Table 1-6 describes the icons for the device table. To view or modify the configuration of a device, click
the Edit icon next to the device name.
Table 1-6
Icon
Device Table Icons
Function
Activate all inactive Service Engines.
Edit the device.
Export a table to a comma-separated value (CSV) file.
Create a filtered table. Filter the devices by the device name, device
type, and device status.
View all devices. Click this icon to view all devices after you have
created a filtered table.
Refresh the table
Print the current window.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-10
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Device Monitoring
For more information, see the “Devices, Services, and Other Tables” section on page 1-7.
Devices Home Page
The Devices home page (Figure 1-6) provides alarm status and information on the device. Only basic
information is displayed for the SR and VOSM.
By clicking the Origin Services and Device Groups links in the Assignments area on the home page for
an SE a table is displayed listing all the origin services or device groups in the VDS-OS, and which ones
the SE is assigned to. Through this page, you can assign the device to additional origin services or device
groups by clicking the icon next to the applicable origin services or device groups and submitting your
selection.
You can update the device software, and telnet to the device from the Devices home page. For more
information about updating the software, see the “Software Upgrade” section on page 1-1.
Figure 1-6
SE Devices Home Page
The Devices home page for an SE or an SR provides several icons. Table 1-7 describes these icons. The
VOSM home page has a subset of the icons.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-11
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Table 1-7
SE Devices Home Page Icons
Icon
Description
Displays all devices. Clicking this icon displays a list of the Service Engines. To view
or configure another Service Engine, click the Service Engine name. The configuration
page for that device is displayed and the left-panel menu displays. This feature allows
you to compare the configuration on different Service Engines. To return to the
left-panel menu, click the Display Menu icon.
Displays the left-panel menu for the device.
Refreshes the page.
Deletes the device. See the “Deleting a Device” section on page 1-9.
Updates application statistics. The device statistics are updated at a configurable time
interval, which is set in the System Configuration page
(System.monitoring.collectRate). See the “Configuring System Settings” section on
page 1-8. To see the latest statistics immediately, without waiting for the time interval
to elapse, click this icon.
Forces a full database update from the VOSM to the SE. If the VOSM and SE databases
are not synchronized because of network errors or other errors, you can synchronize
them by clicking this icon.
Reboots the device. See the “Rebooting Devices” section on page 1-8.
Prints the home page.
For more information about the Devices home page, see the “Devices Home Page” section on page 1-8.
Using show, clear, and alarm Commands
The show, clear, and alarm commands offer more detailed monitoring of the device.
•
Table 1-8 lists only the show command parameters where arguments are required or are optional.
•
Table 1-9 lists only the clear command parameters where arguments are required.
•
Table 1-10 lists only the alarm command parameters where arguments are required.
A full list of the show, clear, and alarm commands is available from the drop-down list on the respective
page.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-12
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Using the VOSM show, clear, or alarm Command Tool
To use the VOSM show, clear, or alarm command tool, do the following:
Step 1
Choose Devices > Devices > Monitoring > Show/Clear/Alarm Commands and then click either Show
Commands, Clear Commands, or Alarm Commands.
Step 2
From the drop-down list, choose a command.
Step 3
Enter arguments for the command, if any.
Step 4
Click Submit to display the command output. The results of the command are displayed in a new
window.
Table 1-8
show Command Arguments
show Command
Arguments
Device
aaa
{commands [accounting | authorization] | enable
[authentication] | exec [accounting | authorization] | login
[authentication] | system [accounting | authorization]}
SE, SR,
VOSM
access-list
{300}
SE
alarms
[critical | detail | history | major | minor | status]
SE, SR,
VOSM
authentication
{user}
SE, SR,
VOSM
cdn-statistics
http {service-engines | device-group-name groupname |
device-groups}
VOSM
cdnfs
{usage | volumes}
SE
clock
[detail | standard-timezones {all | details timezone | regions |
zones region-name}]
SE, SR,
VOSM
cms
{database {content {dump filename | text | xml} |
maintenance [detail]} | info | processes}
SE, SR,
VOSM
content
{all | diskpath diskpath| last-folder-url url | url url}
SE
content-origin
[request-fqdn domain_name]
SE
device-mode
{configured | current}
SE, SR,
VOSM
disks
[current | details | error-handling [details] | raid-state |
SMART-info [details]]
SE, SR,
VOSM
interface
{GigabitEthernet slot/port | PortChannel port-num | Standby SE, SR,
group_num | TenGigabitEthernet slot/port}
VOSM
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-13
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Table 1-8
show Command Arguments (continued)
show Command
Arguments
Device
ip
On SE or VOSM: {access-list [acl-name | acl-num] | routes}
SE, SR,
VOSM
On SR: {access-list [acl-name | acl-num] | bgp {ip-prefix |
network-ip-address | all | community [location-community] |
ipv4 unicast | memory | neighbors [neighbor-ip-address] |
nexthop-database | summary} | interface brief | opsf
[border-routers | database [adv-router
ip-address-advertising-router | asbr-summary
[ip-address-link-state-id | detail] | database-summary | detail |
external [ip-address-link-state-id | detail] | network
[ip-address-link-state-id | detail] | nssa-external
[ip-address-link-state-id | detail] | router
[ip-address-link-state-id | detail] | self-originated [detail] |
summary [ip-address-link-state-id | detail]] | interface |
memory | neighbor [ip-address-neighbor [detail] |detail |
summary] | request-list ip-address-neighbor-router
{GigabitEthernet slot/port | PortChannel channel-number} |
retransmission-list {GigabitEthernet slot/port | PortChannel
channel-number} | route [single-ip-route] | rspf route
[ip-address-advertising-router] | traffic] | proximity
{algorithm | server} | rib {clients [single-client] | memory |
recursive-next-hop [ip-address-next-virtual-hop] | route
[ip-address-single-route | bgp | direct | isis | ospf | summary] |
unresolved-next-hop [ip-address-unresolved-next-hop]} | route
| static route}
lacp
{counters | internal}
SE, SR,
VOSM
ntp
{status}
SE, SR,
VOSM
processes
[cpu | debug pid | memory | system [delay 1-60 | count 1-100]] SE, SR,
VOSM
service-registry
{process | service}
SR
service-router
On SE: {keepalive-interval | service-monitor}
SE, SR,
VOSM
On SR: {vos-monitor | lastresort [domain domain-name] | load
{all | sename sename} | memory | redirect-burst-control |
routes | service-monitor | services {all | sename sename] | |
summary}| unified-routing-table}
On VOSM: {service-monitor}
services
{ports [port-num] | summary}
SE, SR,
VOSM
snmp
{alarm-history | engine ID | group | stats | user}
SE, SR,
VOSM
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-14
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Table 1-8
show Command Arguments (continued)
show Command
Arguments
Device
statistics
On all devices: aaa | fd | icmp | icmpv6 | ip | lsof | netstat |
radius | services | snmp | tacacs | tcp | udp
SE, SR,
VOSM
On SR only: {cdn-select summary | ip [ospf | proximity {rib |
server}] | isis [GigabitEthernet slot/port | PortChannel
channel-number] | service-router {all | dns | history | keepalive
| routing se se-name | summary} | transaction-logs}
On VOSM only: content-distribution-network device status
device-name or device-group-name or device-ID
On SE only:
access-lists 300 | admission | cdnfs | content-mgr |
transaction-logs | vos [errors | rm-interface |
VOSM-interface | we-interface]
vos [errors | rm-interface | VOSM-interface | we-interface]
web-engine [abr {dash-media-app [detail | fragment-file |
manifest-file | representation-index-file | server-manifest-file
| summary] | hls-media-app [detail | fragment-file |
manifest-file | meta-file | session | summary] |
smoothhd-media-app [detail | fragment-file | manifest-file |
meta-file | session | summary] | zeri-media-app [detail |
fragment-file | manifest-file | meta-file | summary]| detail |
error | key-client | performance | usage]
tech-support
[list-files list-file-directory | page | service {authentication | cms | SE, SR,
| kernel | web-engine}]
VOSM
user
{uid number | username name}
SE, SR,
VOSM
users
{administrative}
SE, SR,
VOSM
version
[pending]
SE, SR,
VOSM
vos
{asset | capture-src-manager {channels | statistics} | channel SE
{all | channelURI [config [outfile filename]] | schedule [all
[outfile filename] | [pub-resourceURI]] |
origin-service [all | srdn]}}
web-engine
{all | admission-control | health | mediaapp}
SE
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-15
Chapter 1
Monitoring the VDS-OS
Device Monitoring
Table 1-9
clear Command Arguments
clear Command Arguments
Device
ip
SE, SR, VOSM
On all devices: {access-list counters 1-99 (standard IP) or
100-199 (extended IP) or access-list-name}
On SR only: bgp {neighbor-ip-address | all} | ospf {neighbor {all
| GigabitEthernet slot/port | PortChannel channel-number} |
traffic}
statistics
On all devices: aaa | all | history | icmp | ip | radius | running |
snmp | tacacs | tcp | udp
SE, SR, VOSM
On SR only: http requests | ip | service-registry |
On SE only: {access-lists 300 | admission | transaction-logs | vos
| web-engine [force] |}
users
Table 1-10
Note
{administrative}
SE, SR, VOSM
alarm Command Arguments
clear Command
Arguments
Device
admin-shutdown-alarm
{enable}
SE, SR
overload-detect
{clear 1-999 [raise 10-1000] | enable | raise 10-1000 [clear
1-999]}
SE, SR
The clear statistics web-engine and clear statistics all commands only clear normal statistics, not the
Web Engine statistics details. To clear all Web Engine statistics, use the clear statistics web-engine
force command. We do not recommend using the clear statistics web-engine force command, but if it
is used, restart the Web Engine service by entering the web-engine stop and web-engine start
commands.
Core Dump Files
The Core Dump Files page lists any core dump files for the device. To view a list of core dump files for
the device, choose Devices > Devices > Monitoring > Core Dump Files. The Core Dump File page is
displayed and lists any core dump files that have occurred on the device.
To delete a core dump file, check the check box next to the filename and click the Delete icon in the task
bar.
To delete all core dump files, check the check box in the heading of the check box column, and click the
Delete icon in the task bar.
To refresh the table, click the Refresh Table icon in the task bar.
To print the table, click the Print icon in the task bar.
The core dump files are located in the /local1/local1/core_dir directory.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-16
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Device Monitoring
CPU Utilization
The CPU Utilization report displays the CPU usage for the SE.
To view the CPU Utilization report for an SE, do the following:
Step 1
Choose Devices > Devices > Monitoring > Statistics > CPU Utilization. The CPU Utilization Report
page is displayed.
Step 2
Enter the settings as appropriate. Table 1-11 describes the report settings.
Table 1-11
Step 3
CPU Utilization Report Settings
Field
Description
Chart Size
The chart display size choices are small, medium, or large.
Time Frame
The time frame options are last hour, last day, last week, last month, or
custom. There is a difference in the meaning of the graphs based on the time
frame chosen:
•
Last Hour—Shows raw data collected from the SEs. Real-time values are
reported.
•
Last Day—Shows hourly data, which consolidates the raw data.
Consolidation is done by averaging the raw data for each hour. So the
value reported in the Last Day graph are average values per hour.
•
Last Week, Last Month, and Custom—Shows daily data, which
consolidates hourly data. Consolidation is done by averaging the hourly
data for each day. So these are average values per day.
Time Zone
The time zone choices are SE local time, VOSM local time, or UTC.
Custom Date Range
The custom date range is used when Time Frame is set to custom. Enter the
dates, beginning and end, for the chart in the mm/dd/yyyy format, or choose
the dates by using the calendar icons.
Click Update to see the report.
To export the report to a CSV (comma-separated value) file, click the Export icon in the task bar. A
dialog box is displayed. Choose either Open or Save.
If you choose Open, the tabular report is displayed in the same browser window or a new browser
window, depending on your browser.
If you choose Save, you are prompted to choose a location where to save the file. The file can be opened
with any spreadsheet program.
To print the report, click the Print icon in the task bar.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-17
Chapter 1
Monitoring the VDS-OS
Origin Service Monitoring
Origin Service Monitoring
This section covers the Virtual Origin Service Table.
Virtual Origin Services Table
The Virtual Origin Services Table page lists all origin services on the system and displays the Service
Routing Domain Name (SRDN) for each origin service.
Table 1-12 describes the icons for the Virtual Origin Services Table. To view or modify the configuration
of an origin service, click the Edit icon next to the origin service name. To create a new origin service,
click the Create New icon in the task bar.
Table 1-12
Icon
Virtual Origin Service Table Icons
Function
Creates a new origin service.
Edits an origin service.
Creates a filtered table. Filter the origin service by the origin service
name and content origin.
Views all origin services. Click this icon to view all origin services
after you have created a filtered table.
Refreshes the table.
Prints the current window.
For more information, see the “Devices, Services, and Other Tables” section on page 1-7.
Monitoring Live Channels
Live channels can be managed through the Live Channel, Capture Resource, and Publish Resource
tables. The Control Command column in each table provides a way to start and stop each channel and
resource. The operational state of the channels and resources are displayed as well. This section
describes the control and status monitoring functions of the following tables:
•
Live Channel Table
•
Capture Resource Table
•
Publish Resource Table
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-18
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Monitoring Live Channels
Live Channel Table
Table 6-11Table 1-12 for more information. To view or modify the configuration of a live channel, click
the Edit icon next to the live channel name. To create a new live channel, click the Create New icon in
the task bar.
Channel States
•
Table 6-12Table 1-13 for more information.
•
Stopped—Channel is not capturing content; therefore, content is not being published
•
Not Available—Channel configuration is incomplete (for example, there are no Acquisition nodes
assigned, or the resources have not been defined)
Table 1-13 describes the state of a live channel based on the states of the Acquisition nodes. The
Aggregated Channel State column shows the state that is displayed for the Live Channel Status based on
the state of the Acquisition nodes assigned to the channel.
Table 1-13
Live Channel States
Aggregated Channel State
State of Acquisition node 1 State of Acquisition node 2
Ready
Ready
Ready
Ready
Ready
Stopped
Ready
Ready
Updating
Partial Failure
Ready
Failed
Partial Failure
Ready
Partial Failure
Partial Failure
Failed
Partial Failure
Partial Failure
Partial Failure
Partial Failure
Partial Failure
Partial Failure
Stopped
Failed
Failed
Failed
Failed
Failed
Stopped
Failed
Failed
Updating
Channel Control
Stop icon displayed in the Control column. All channels that are currently stopped have the Start icon
displayed. To start or stop a live channel, click the Stop or Start icon.
Capture Resource Table
Table 6-11Table 1-12 for more information. To view or modify the configuration of a capture resource,
click the Edit icon next to the capture resource, name. To create a new capture resource, click the Create
New icon in the task bar.
The Capture Resources Status includes the state of each Acquisition node. Following are the possible
states of the Acquisition node Resource Status column:
•
Ready—Acquisition node is ready to capture resources
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-19
Chapter 1
Monitoring the VDS-OS
Viewing Statistics
•
Failed—Acquisition node has a failure in the capturing of resources
•
Partial Failure—Acquisition node has a partial failure means that the capture resource is still
functional, but there is a partial failure.
•
Stopped—Acquisition node is not capturing content; therefore, content is not being published
•
Not Available—Acquisition node configuration is incomplete (for example, the encapsulator is not
pushing content)
The Capture Resources Table provides a way to start or stop a capture with the Control column. All
capture resources that are currently started have the Stop icon displayed in the Control column. All
capture resources that are currently stopped have the Start icon displayed. To start or stop a capture
resources, click the Stop or Start icon.
Publish Resource Table
Table 6-11Table 1-12 for more information. To view or modify the configuration of a publish resource,
click the Edit icon next to the publish resource name. To create a new publish resource, click the Create
New icon in the task bar.
The Publish Resources Status includes the state of each Acquisition node. Following are the possible
states of the Acquisition node Resource Status column:
•
Ready—SE is ready to publish resources
•
Failed—SE has a failure in the publishing of resources
•
Partial Failure—SE has a partial failure means that the publish resource is still functional, but there
is a partial failure.
•
Stopped—SE is not publishing content
•
Not Available—SE configuration is incomplete (for example, the encapsulator is not pushing
content)
•
Init—SE has not scheduled the resource yet, one reason could be there is an issue with setting up
the channel
The Capture Resources Table provides a way to start or stop a capture with the Control column. All
capture resources that are currently started have the Stop icon displayed in the Control column. All
capture resources that are currently stopped have the Start icon displayed. To start or stop a capture
resources, click the Stop or Start icon.
Viewing Statistics
The Statistics pages track system-wide playout and routing traffic in the VDS-OS. You can view
statistics on playout traffic listed by SE or device group. The Routing Statistics page lists client requests
and redirects.
This section contains the following procedures:
•
Viewing Service Engines and Device Group Statistics
•
Viewing Routing Statistics
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-20
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Viewing Statistics
Viewing Service Engines and Device Group Statistics
To view the statistics for all SEs or all device groups, do the following:
Step 1
Choose Devices > Statistics. The Statistics page is displayed.
Step 2
Choose Service Engines or Device Groups, and then choose HTTP.
Table 1-14 describes the icons provided on the Statistics pages.
Table 1-14
Icon
Statistics Icons
Function
Update application statistics. The statistics are updated at a configurable time
interval, which is set in the System Configuration page
(System.monitoring.collectRate). See the “Configuring System Settings” section on
page 1-8. To see the latest statistics immediately, without waiting for the time interval
to elapse, click this icon.
Export a table to a comma-separated value (CSV) file.
Refresh the table
Print the current window.
Table 1-15 describes the statistic for HTTP.
Table 1-15
Statistic
Service Engine and Device Group Statistics
Description
HTTP
Requests/Sec
Number of requests per second.
Bytes/Sec
Number of bytes per second.
Hit Rate
Average number (as a percentage) of content items successfully served per
minute from the cache of the SE or from all the SEs in the device group.
Updated
Timestamp indicating when the statistics were updated.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-21
Chapter 1
Monitoring the VDS-OS
Log Files
Viewing Routing Statistics
Step 1
Devices > Statistics > Routing Statistics.
Step 2
Choose one of the following options:
•
Routing Requests
•
Routing Redirects
See Table 1-14 for descriptions of the icons provided on the Routing Statistics pages. Table 1-16
describes each routing statistic.
Table 1-16
Service Router Statistics
Statistic
Description
Routing Requests
Total Requests
Total number of content requests received from clients.
HTTP Requests
Number of ASX and traditional HTTP web requests received.
Updated
Timestamp indicating when the statistics were updated.
Routing Redirects
Total Requests
Total number of content requests received from clients.
Reqs Redirected
Total number of redirected client requests.
Reqs Not Redirected
Total number of client requests not redirected.
Updated
Timestamp indicating when the statistics were updated.
Log Files
Log files can be generally categorized in three main classes:
1.
Transaction logs
2.
Error and debug logs
3.
General system logs and core files
Transaction Logs
Transaction logs are stored under the /local/local1/logs/ directory. They are disabled by default; to enable
transaction logging either enter the transaction-logs enable command or check the Transaction Log
Enable check box on the Transaction Log Settings page. See the “Configuring Transaction Logs”
section on page 1-15 for more information.
Transaction log archiving is configured by using the transaction-logs archive command or by entering
the settings on the Transaction Log Settings page.
To allow the Service Monitor module to collect threshold information enter the service-router
service-monitor transaction-log enable command or check the Enable check box for each setting on
the Service Monitor page. See the “Setting Service Monitor Thresholds” section on page 1-52 for more
information. To configure the Service Monitor thresholds, use the Service Monitor page.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-22
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
For more information about transaction logs, see the “Transaction Logs” section.
Error and Debug Logs
Error and debug logs are stored under the /local/local1/errorlog/ directory. By default, all software
modules only log error related information. Debug logging levels can be controlled (on a per software
module basis) through the debug command.
There is a background cron job that periodically (every hour) monitors and trims the overall size of
SYSFS (including the errorlog/ directory).
General System Logs and Core Files
General system logs primarily consist of /local/local1/syslog.txt. In addition, any core files generated
are stored to the /local/local1/core_dir/ directory. The same background cron job used for the error and
debug logs also monitors and trims the growth of syslog.txt and core_dir/ directory. If the overall space
usage of SYSFS exceeds 80 percent, this cron job raises an alarm indicating that.
When the overall SYSFS space usage exceeds 90 percent, this cron job starts freeing up space by
removing the oldest files first. The algorithm used basically removes files based on their age. Initially,
all files that are older than 30 days are removed (from the core_dir/, errorlog/, and logs/ directories). If
this does not free up enough space (that is less than 90 percent of capacity), then all files having an age
of 10 days are removed.
Transaction Logs
Transaction logs allow administrators to view the traffic that has passed through the SE. Typical fields
in the transaction log are the date and time when a request was made, the URL that was requested,
whether it was a cache hit or a cache miss, the type of request, the number of bytes transferred, and the
source IP address. For more information about configuring transaction log settings for SEs, see the
“Configuring Transaction Logs” section on page 1-15.
This section discusses the following topics:
Note
•
Transaction Log Formats for Web Engine
•
Usage Guidelines for Log Files
•
Service Router Transaction Log Fields
•
Service Monitor Transaction Logs
•
Content Manager Transaction Log Fields
•
Capture Controller Transaction Log Fields
Each transaction log includes a header line that provides the VDS-OS software version and a summary
line as the last line in the transaction log, which includes a summary of all the requests that appear in the
transaction log.
Transaction Log Formats for Web Engine
The transaction logs for Web Engine consist of the following:
•
Extended Squid
•
Apache
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-23
Chapter 1
Monitoring the VDS-OS
Transaction Logs
•
Custom Format
Note
Changing the time zone on an SE does not affect the log entry nor the log filename. Both the log entries
and the log filename always use UTC.
Note
The timestamp for Web Engine transaction log entry has no space between the date and the time. An
example follows:
[19/Oct/2010:11:20:09.133-0705] 4821 172.22.71.155 TCP_MISS/404 235 GET
http://172.22.71.155/hello application/octet-stream
Extended Squid
The Extended Squid format logs the same fields logged by the Squid-1.1 access log file format. The
Extended Squid transaction logs are located in the logs/webengine_extsquid/ directory.
For details on the Squid-1.1 native log file format, see the Squid documentation “Frequently Asked
Questions,” “Squid Log” section, access.log heading at:
http://wiki.squid-cache.org/SquidFaq/FaqIndex
The Extended Squid-style log file format is as follows:
Current-Time Time-to-Serve Client-IP Request-Desc/Status-Returned Bytes-Xferred Method URL
MIME-Type
An Extended Squid-style log format example looks like this:
[21/May/2009:00:29:12 +0530] 952195 171.71.50.197 TCP_REFRESH_MISS/200 11120239 GET
http://7.9.0.3/1mbs_ai/1mbs1-100.wmv video/x-ms-wmv
Table 1-17 describes the fields for the Extended-Squid transaction log.
Table 1-17
Extended-Squid Transaction Log Fields
Field
Description
Current-Time
Time (milliseconds), in common log time format, the request was
received.
Time-to-Serve
Time, in microseconds, taken to complete the request.
This field could be zero if the transaction complete time is greater
than the transaction start time, which could occur if NTP is not
synchronized.
Client-IP
IP address of the requesting client.
Request-Desc/Status-Returned
Combination of Squid result codes and the response code returned
to the client.
The Request-Desc/Status-Returned field includes the error status
code for both TCP_MISS and TCP_HIT. A TCP_HIT with an
error status code means the HTTP response was served from
cache. The meaning of a TCP_MISS with an error status code has
not changed.
Bytes-Xferred
Bytes sent to the client, including the headers.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-24
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Table 1-17
Extended-Squid Transaction Log Fields (continued)
Field
Description
Method
Request method.
URL
Requested URL, including the query string.
MIME-Type
MIME type.
Table 1-18 describes the Squid codes currently supported. The TCP_ codes refer to the cache status of
the object when the request was handled by the Web Engine. In addition to the cache statistics listed in
Table 1-18, the client or server error statistics could get incremented as well depending on the response
code.
Table 1-18
Squid Code Request Descriptions
Valid Response
(Status) Code
Squid Result Code
Description
TCP_MISS
Requested object was not in
cache.
0–5xx
Cache miss
Cache bypass
Partial hit
TCP_MEM_HIT
Valid copy of the requested
object was in memory.
Currently
supports only
2xx response
code
Cache hit and memory hit
TCP_HIT
Valid copy of the requested
object was in cache.
0, 2xx, 3xx, 406, Cache hit
412, 416, 500
TCP_REFRESH_
MISS
Requested object was cached
0–-5xx
but is stale. The query returned
the new content.
TCP_REFRESH_
HIT
Requested object was cached,
but expired. The query for the
object resulted in a “304 not
modified” message.
0, 2xx, 406, 412, Cache hit
416, 500
TCP_IMS_HIT
Client issued an IMS request
for an object, which was in
cache and was not stale.
0, 2xx, 3xx, 500
Cache hit
TCP_DENIED
Access was denied for this
request.
403
—
000
—
NONE
See Request
NONE_ABORTED Description—None and
None_Aborted, for the
description.
Mapping to Cache Statistics
(show statistics web-engine
detail)
Cache miss
Request Description—None and None_Aborted
Normally, when a transaction completes, if the cache status is unknown (before the content lookup
completes, the cache status is unknown), and the request was not denied by the Authorization Server, the
request description that is written to the transaction log is “NONE.”
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-25
Chapter 1
Monitoring the VDS-OS
Transaction Logs
If a transaction completes because the client aborted the connection, “_ABORTED” is appended to
“NONE.”
If a transaction completes because the of an internal Web Engine failure, and there are no more
transactions waiting for the process within the session, then the transaction was not aborted; therefore,
the “_ABORTED” is not appended to “NONE.”
Under the conditions described above, because this occurs before the origin service is contacted and
there is no Authorization Server failure or redirect, the response status code that is written to the
transaction log is 000.
Apache
The Apache format is the Common Log File (CLF) format defined by the World Wide Web Consortium
(W3C) working group. This format is compatible with many industry-standard log tools. The
Apache-style transaction log files are located in the /webengine_apache/ directory.
The Apache-style log file format is as follows:
client-IP-address URI bytes-sent object-size bytes-received method status time-received time-to-serve
An Apache-style log file format example looks like this:
171.71.50.197 http://spcdn-se612-5.sanity.spcdn.net/gmedia-0.4gb.wmv 363704065 137
363710748 GET 200 [06/Nov/2007:00:25:32 +0530] 325033158
Table 1-19 describes the fields for the Apache-style transaction log.
Table 1-19
Apache-Style Transaction Log Fields
Field
Description
client-IP-address
IP address of the requesting client
URI
Requested URL, including the query string.
bytes-sent
Bytes sent to client, including the headers.
object-size
Bytes sent to client, excluding the HTTP headers.
bytes-received
Bytes received from client.
method
Request method.
status
HTTP response code for the request.
time-received
Time, in common log time format, the request was received.
time-to-serve
Time, in microseconds, taken to complete the request.
Custom Format
The transaction-logs format custom command allows you to use a log format string to log additional
fields that are not included in the predefined Extended Squid format or Apache CLF format. The log
format string is a string that can contain the tokens listed in Table 1-20 and that mimics the Apache log
format string.
The log format string can contain literal characters that are copied into the log file. Double backslashes
(\\) can be used to represent a literal backslash, and a backslash followed by a single quote (\’) can be
used to represent a literal single quote. A literal double quote cannot be represented as part of the log
format string. The control characters \t and \n can be used to represent a tab and a new line character,
respectively. The custom transaction logs are located in the /webengine_clf/ directory.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-26
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
The following command can be entered to generate the well-known Apache Combined Log Format:
transaction-logs format custom “%t%r %>s %b”
The following transaction log entry example is configured by using the preceding custom format string:
[11/Jan/2003:02:12:44 -0800] “GET http://www.cisco.com/swa/i/site_tour_link.gif HTTP/1.1” 200
3436
Apache and Squid can be represented by the following custom log format patterns:
Apache-style logging with custom patterns: %a %U %O %b I %m %>s %t %D
Squid-style logging with custom patterns:- %Z %D %a %R/%>s %O %m %U %M
Table 1-20
Custom Log Format String Values
Format Token
Value
%a
IP address of the requesting client.
%A
IP address of the SE.
%b
Bytes sent, excluding HTTP headers.
%B
Bit rate in bits per second (bps). Only for HSS session tracking.
%c
Time, in common log time format, that the log entry was generated.
%C
Records AuthLOOKupTime | CALLOOKuptime | CacheRouterTime |
OSDownloadTime in microseconds granularity.
CacheRouterTime displays only on the revalidation scenario. In normal
cache-miss use case, the CALLOOKuptime| includes the time taken by cache
route lookup as well.
%D
Time consumed to serve the request in microseconds
%h
Remote host (IP address of the requesting client is logged).
%H
Request protocol.
%I
Bytes received from the client.
%k
Method of session tracking (cookie, URL query)
%m
Request method.
%M
MIME type of the requested asset.
%O
Bytes sent to client, including the headers.
%p
Client that set up the transport session for the request. The value is one of the
following:
•
Local—Request is from this SE.
•
Internal—Request is from other SE
•
External—Request is from end user
%q
Query string (which is preceded by a question mark (?) if a query string exists;
otherwise, it is an empty string).
%r
First line of the request. The space in the first line of the request is replaced with
a vertical bar (|) delimiter (for example, Get|/index.html|HTTP/1.1)
%R
Request description (Squid description codes).
%>s
Status. The translog code always returns the HTTP response code for the request.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-27
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Table 1-20
Custom Log Format String Values (continued)
Format Token
Value
%t
Time in common log time format (or standard English format).
%T
Time consumed to serve the request in seconds (a floating point number with 3
decimal places).
%u
URL path requested, including query strings.
%U
URL path requested, not including query strings.
%V
Value of the host request header field reported if the host appeared in the request.
If the host did not appear in the host request header, the IP address of the server
specified in the URL is reported.
%X
Connection status when the response is completed. The %X field has the
following possible values:
•
X—Connection aborted before the response completed.
•
+ —Connection may be kept alive after the response is sent.
•
- —Connection is closed after the response is sent.
%Z
Print the request received time stamp in milliseconds; otherwise, the request
received time stamp is in seconds.
%{Header-Field}i
Any request header. Replace the Header-Field with the actual header field you
want to log; for example, %{Cache-Control}i.
Note
All client request headers are only logged on the edge SE.
Usage Guidelines for Log Files
This section provides some guidelines for working with log files, and includes the following topics:
Note
•
Working Logs
•
Archive Working Log
•
Exporting Log Files
The time stamp in the filename is always in UTC, but the time stamp for the log entries in the transaction
logs depends on the transaction log.
Working Logs
Transaction logs are located in the /local/loca1/logs directory. Each component has one or more
directories, depending on its configuration.
There is a working log file in each directory, which is a symbol link, linking to the current working log
file.
The log files are logged to a working log on the local disk as follows:
•
Service Router logs are logged to a working log on the local disk in the
/local1/logs/service_router/working.log
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-28
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
•
Web Engine client transaction logs are located in the /local1/logs/webengine_apache, the
/local1/logs/webengine_clf, and the /local1/logs/webengine_extsquid directories
•
Service Router transaction logs are located in the /local1/logs/service_router directory
•
Service Monitor transaction logs are located in the /local1/logs/service_monitor directory
•
Content Manager transaction logs are located in the /local1/logs/content_mgr directory
Archive Working Log
You can specify the interval at which the working log should be cleared, when the interval occurs the
data is moved to an archive log. The archive log files are located on the local disk in the /local1/logs/
directory.
The archiving of working logs can be configured to occur at a specified time interval and when the
working log file reaches a specified size. If one of the criteria is met and at least one new message has
been written to the working log, a log rotation occurs. If one of the criteria is met and no new messages
have been written to the working log, a log rotation does not occur. You can specify the maximum
number of old logs kept on disk.
Because multiple archive files are saved, the filename includes the timestamp when the file was created.
The time stamp in the filename is always in UTC, but the time stamp for the log entries in the transaction
logs depends on the transaction log. Because the files can be exported to an FTP/SFTP server, the
filename also contains the IP address of the SE.
The archive filenames use this format:
modulename_IPADDRESS_YYYYMMDD_HHMMSS_file-generation-number.
Note
The IP address used in the archived filename is not necessarily the primary interface of the SE. The
transaction log function decides on which IP address to use in creating the archive name.
Exporting Log Files
To facilitate the post-processing of cache log files, you can export transaction logs to an external host.
This feature allows log files to be automatically exported by FTP to an external host at configurable
intervals. The username and password used for FTP are configurable, as is the directory to which the log
files are uploaded.
The log files automatically have a filename that uses the
<type>_<ipaddr>_yyyymmdd_hhmmss_<file_generation_number> format, where:
•
<type> represents the type of log file, with selog for cache logs such as HTTP, HTTPS, and FTP.
•
<ipaddr> represents the SE IP address.
•
yyyymmdd_hhmmss represents the date and time when the log was archived for export.
•
<file_generation_number> represents the File Generation Number, which has a range from 00001
to 99999.
Exporting Transaction Logs to External FTP Servers
To export transaction logs to an FTP server, you must first enable exporting of transaction logs and then
configure the FTP or secure FTP (SFTP) server parameters. This feature can support up to four FTP
servers. The following information is required for each target FTP server:
•
Server IP address or the hostname
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-29
Chapter 1
Monitoring the VDS-OS
Transaction Logs
The SE translates the hostname with a DNS lookup and then stores the IP address in the
configuration.
•
FTP user login and user password
•
Path of the directory where transferred files are written
Use a fully qualified path or a relative path for the user login. The user must have write permission
to the directory.
You can also compress archived log files into gzip format before exporting them to external FTP servers.
The compressed filename has a .gz extension. This compression feature uses less disk space than that
required for uncompressed archived files on both the SE and the FTP export server and also requires less
bandwidth during export because of the smaller size of the files to be exported.
For more information about exporting and archiving transaction logs, see the “Configuring Transaction
Logs” section on page 1-15 for SEs, and the “Configuring Transaction Logs for the Service Router”
section on page 1-71 for SRs.
To immediately have the transaction logs archived and exported following the next transaction, use the
following commands:
SE# transaction-log force archive
SE# transaction-log force export
The transaction-log force archive command causes the transaction log to be archived to the SE hard
disk following the next transaction. The transaction-log force export command causes the transaction
log to be exported to the configured FTP server. The transaction-log force commands do not change the
configured or default schedule for an archive or export of the transaction logs. The archive or export
interval is restarted after the forced operation. If a scheduled archive or export job is in progress when
the transaction-log force command is entered, the command has no effect.
Restarting Export After Receiving a Permanent Error from the External FTP Server
When an FTP server returns a permanent error to the SE, the export is retried at 10-minute intervals or
sooner if the configured export interval is sooner. If the error is a result of a misconfiguration, the archive
transaction logs are no longer exported to that server. You must re-enter the SE transaction log export
parameters for the misconfigured server to clear the error condition.
A permanent error (Permanent Negative Completion Reply, RFC 959) occurs when the FTP command
to the server cannot be accepted, and the action does not take place. Permanent errors can be caused by
invalid user logins, invalid user passwords, and attempts to access directories with insufficient
permissions or directories that do not exist.
Exporting Transaction Logs to External SFTP Servers
You can also export transaction logs to a Secure File Transfer Protocol (SFTP) server. You must first
enable the feature and configure the SFTP server parameters. The following information is required for
each target SFTP server:
•
SFTP server IP address or the hostname
The SE translates the hostname with a DNS lookup and then stores the IP address in the
configuration.
•
SFTP user login and user password
•
Path of the directory where transferred files are written
Use a fully qualified path or a relative path for the user login. The user must have write permission
to the directory.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-30
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
To enable this feature, enter the sshd allow-non-admin-users command on the SE. If this feature is
enabled, the output of the show running-config EXEC command shows that this feature is enabled on
the SE.
Service Router Transaction Log Fields
Table 8-19Table 1-21 describes the fields for the Service Router transaction log.
Table 1-21
Service Router Transaction Log Fields
Field
Description
c-ip
Source Internet Protocol (IP) address of the connected socket. This may be the
IP address of a proxy server or firewall.
user-agent
Browser type used if the player was embedded in a browser. If the player was
not embedded, this field refers to the user agent of the client that generated the
log. The user-agent value is enclosed in double quotes (“ “).
date
Date, in international date format, when a client is connected.
time
Time when the client is connected. The time format is either in Coordinated
Universal Time (UTC) or local time, depending on how the logging plug-in is
configured.
url
URL requested by the client.
protocol
Protocol used to access the content.
server-picked
Service Engine selected by the Service Router.
routed-path
Path of the redirected URL that is used for last-resort error-domain redirects
and last-resort translator API requests.
status
Status code.
routing-method
Routing method chosen. The routing-method field has the following possible
values:
•
Last-Resort
•
Network
•
Proximity
•
Zero-Network
•
Geo-Location
Service Monitor Transaction Logs
Service Monitor transaction logs provide a tool for analyzing the health history of a device to ensure the
device is within the configured capacity limits.
The device and service health information are periodically logged on the device in transaction log files.
Transaction logs provide a useful mechanism to monitor and debug the system. The transaction log fields
include device information applicable to Service Engines and Service Routers that are useful for
capacity monitoring. Additionally, when a device threshold is exceeded, detailed information is sent to
a file (threshold_exceeded.log) to capture the processes that triggered the threshold alarm. To configure
threshold settings, see the “Setting Service Monitor Thresholds” section on page 1-52.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-31
Chapter 1
Monitoring the VDS-OS
Transaction Logs
The Service Monitor transaction log filename has the following format:
service_monitor_<ipaddr>_yyyymmdd_hhmmss_<>, where:
•
<ipaddr> represents the IP address of the SE, SR, or VOSM.
•
yyyymmdd_hhmmss represents the date and time when the log was created.
For example, service_monitor_192.168.1.52_20110630_230001_00336 is the filename for the log file
on the device with the IP address of 192.168.1.52 and a time stamp of June 30, 2011 at 3:36 AM.
The Service Monitor transaction log file is located in the /local1/logs/service_monitor directory.
An entry to the Service Monitor transaction log is made every two seconds.
Note
The following rules apply to Service Monitor transaction logs:
•
A transaction log value is only logged if the Service Monitor is enabled for that component on the
device. For example if CPU monitoring is not enabled, the transaction log value “–” is displayed.
•
If a log field can have more than one value, the values are delimited by the pipe (|) character.
•
If a value can have sub-values, the sub-values are delimited by the carrot (^) character.
•
Some of the fields display aggregate values. If the statistics are cleared using the clear statistics
command, the value after clearing the statistics may be less than the previous values, or may be zero
(0).
Table 1-22 describes the fields for the Service Monitor transaction log on an SE.
Table 1-22
SE Service Monitor Transaction Log Fields
Field
Sample Output
Description
Corresponding CLI Command
date
2011-06-30
Date of log.
–
time
22:52:02
Time of log.
–
cpu_avg
21
Moving average value in percentage of show service-router service-monitor
CPU usage.
Device status—CPU—Average load
mem_avg
44
Moving average value in percentage of show service-router service-monitor
memory usage.
Device status—Mem—Average used
memory
kernel-mem-avg
11
Moving average value in percentage of show service-router service-monitor
kernel memory.
Device status—KMEM—Average
kernel memory
disk_avg
2
Moving average value in percentage of show service-router service-monitor
disk usage.
Device status—Disk—Average load
disk_fail_count_
threshold
Y
Boolean value to indicate if disk fail
count threshold has been reached.
per_disk_load
disk03-01^2|
disk04-02^5
Current load per disk, as a percentage. –
The sample output indicates that
disk03–partition01 has a 2 percent load
and disk04–partition02 have a 5 percent
load.
show service-router service-monitor
Device status—Device
Status—Disk—Status
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-32
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Table 1-22
SE Service Monitor Transaction Log Fields (continued)
Field
Sample Output
Description
Corresponding CLI Command
bandwidth_avg
Port_Channel_
1^2^4|
Port_Channel_
2^0^0
Moving average bandwidth used, as a show service-router service-monitor
Device status—NIC—Average BW
percentage, of bandwidth in and
In/ Average BW Out
bandwidth out per interface. The
sample output indicates that port
channel 1 has an average bandwidth of
2 percent for receiving and 4 percent for
transmitting, and port channel 2
average bandwidth usage is 0.
file-desc-count
1023
Total count of file descriptors open on show statistics lsof
the device. File descriptors are internal
data structures maintained by the Linux
kernel for each open file.
tcp_server_connections
35
Number of TCP server connections
open.
show statistics tcp
TCP Statistics—Server connection
openings
tcp_client_connections
24
Number of TCP client connections
open.
show statistics tcp
TCP Statistics—Client connection
openings
processes_count
42
Number of processes running on the
device.
show processes
dataserver-cpu-
percentage
1
Percentage of the CPU used for the
dataserver process.
–
web_ engine_
threshold_exceeded
Y
Boolean value to indicate if the Web
Engine threshold has been exceeded.
show service-router service-monitor
Services status—Web—Threshold
web-engine-augment-
threshold-exceeded
Y
Boolean value to indicate if Web
Engine augmentation alarm threshold
has been exceeded.
–
web_ engine_stopped
N
Boolean value to indicate if Web
Engine has stopped.
show service-router service-monitor
Services status—Web—Stopped
web-engine-cpu-
percentage
3
Percentage of the CPU used by the Web –
Engine.
web_engine_mem
3500
Memory (in bytes) used by the Web
Engine.
show web-engine health
Total memory usage
web_engine_get_
requests
250
Count of get requests received by the
Web Engine (Aggregate value)
show statistics web-engine detail
HTTP Request Type Statistics—Get
requests
web_engine_sessions
5
Count of HTTP connections.
show statistics web-engine detail
Web-Engine Detail Statistics—Total
HTTP Connection + Active Session
web_engine_upstream_
connections
2
Count of HTTP connections to
upstream SE or origin service.
show statistics web-engine detail
Web-Engine Detail Statistics—Total
HTTP Connection
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-33
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Table 1-22
SE Service Monitor Transaction Log Fields (continued)
Field
Sample Output
Description
Corresponding CLI Command
uns-cpu-percentage
3
Percentage of CPU used by the Unified –
Namespace (UNS) process.
uns_mem
3500
Memory used by the UNS process.
–
Table 1-23 describes the fields for the Service Monitor transaction log on a SR.
Table 1-23
SR Service Monitor Transaction Log Fields
Field
Sample Output Description
Corresponding CLI Command
date
2011-06-30
Date of log.
–
time
22:52:02
Time of log.
–
cpu_avg
21
Moving average value in percentage of show service-router service-monitor
CPU usage.
Device status—CPU—Average load
mem_avg
44
Moving average value in percentage of show service-router service-monitor
memory usage.
Device status—Mem—Average used
memory
kernel-mem-avg
11
Moving average value in percentage of show service-router service-monitor
kernel memory.
Device status—KMEM—Average
kernel memory
disk_avg
2
Moving average value in percentage of show service-router service-monitor
disk usage.
Device status—Disk—Average load
disk_fail_count_
threshold
Y
Boolean value to indicate if disk fail
count threshold has been reached.
file-desc-count
1023
Total count of file descriptors open on –
the device. File descriptors are internal
data structures maintained by the Linux
kernel for each open file.
tcp_server_connections
35
Number of TCP server connections
open.
show statistics tcp
TCP Statistics—Server connection
openings
tcp_client_connections
24
Number of TCP client connections
open.
show statistics tcp
TCP Statistics—Client connection
openings
processes_count
42
Number of processes running on the
device.
show processes
dataserver-cpu-
percentage
1
Percentage of the CPU used for the
dataserver process.
–
sr-cpu-percentage
12
Cpu percentage used by SR.
–
sr_mem
750000
Memory (in bytes) used by SR.
show processes memory and search
for service_router
show service-router service-monitor
Device status—Device
Status—Disk—Status
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-34
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Table 1-23
SR Service Monitor Transaction Log Fields (continued)
Field
Sample Output Description
Corresponding CLI Command
requests_received
34
Total count of requests received by SR
(aggregate value)
show statistics service-router
summary
Requests Received
http_normal_requests_
received
5
Not applicable in VDS-OS.
–
http_asx_requests_
received
5
Not applicable in VDS-OS.
–
rtsp_requests_received
5
Not applicable in VDS-OS.
–
rtmp_requests_received
5
Not applicable in VDS-OS.
–
dns_requests_received
6
Total count of DNS requests received
by SR (aggregate value).
show statistics service-router dns
Total DNS queries
Content Manager Transaction Log Fields
The Content Manager transaction log filename has the following format:
content_mgr__<ipaddr>_yyyymmdd_hhmmss_<>, where:
•
<ipaddr> represents the IP address of the SE, SR, or VOSM.
•
yyyymmdd_hhmmss represents the date and time when the log was created.
The Content Manager transaction log file is located in the /local1/logs/content_mgr directory.
Table 1-24 describes the fields for the Content Manager transaction log on an SE.
Table 1-24
Content Manager Transaction Log Fields
Field
Description
Date
Date of log entry.
Time
Time of log entry.
ContentType
Type of content, which is either cached or prepos-content (prefetched).
Operation
Content Manager operation, which is addition, deletion, update, or eviction.
Priority
Prefetched content always has a priority of 0, which means ignore. The lower the
number, the lower the priority.
CreationDate
Date the content object was created.
CreationTime
Time the content object was created.
FileSize
File size, in bytes, of the content object.
HitCount
Number of times the content object was accessed.
URL
URL of the content object. If Content Manager cannot retrieve the URL by using the
FastCAL lookup of the disk path, then the ContentType field has a value of
“unknown-content” and the URL field displays “-.”
Path
Disk path of the content object.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-35
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Capture Controller Transaction Log Fields
<ipaddr>_yyyymmdd_hhmmss_<>, where:
•
<ipaddr> represents the IP address of the SE or SR.
•
yyyymmdd_hhmmss represents the date and time when the log was created.
The Capture Controller transaction log file is located in the /local1/logs/capturecontroller directory.
Table 1-25 describes the fields for the Capture Controller transaction log on an SE or SR.
Table 1-25
Capture Controller Transaction Log Fields
Field
Description
Timestamp
Time (in UTC) this particular record is logged.
PublishURI
URI used to publish the recorded asset to the client. This is the live channel URI
followed by the publish resource base URI configured on the VOSM; for
example, http://vos.demo.net/abchd_west/live/hls/index.m3u8.
Channel URI
Uniquely identifies the channel across the system. It is a combination of the
origin service and the live channel name; for example,
http://vos.demo.net/abchd_west.
Event
Event has the following values:
•
Linear—Live publish resource
•
Scheduled—Live-to-VOD publish resource configured using the Capture
Schedule XML or through the Recorder Manager.
MediaType
Indicates the Media Encapsulation Format (hss/smooth/hls/dash/c2)
StartTime
Time the recording started for the publish resource. This is the configured start
time.
StopTime
Time the recording stopped/completed for the publish resource. this is the
configured stop time.
Status
Status of the publish resource when it completed or stopped. Status has the
following values:
•
Complete,
•
Partial Complete
•
Failed
•
Partial Failed
•
Stopped
•
Playout Only
CaptureResource
Capture resource is a collection of source profiles defined on the Cisco Media
Encapsulator (CME). A live channel can have multiple capture resources. This
field (relative to the Channel ID) indicates which of the configured capture
resources is used by this publish resource.
TimeShiftDuration
Time (in minutes) the user can seek back to while playing a live stream.
StartOverURI
Currently not supported.
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-36
OL-28084-04
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Table 1-25
Capture Controller Transaction Log Fields (continued)
Field
Description
ActionOnCompletion The VDS-OS provides an option to notify an external entity, by using the
Capture Schedule XML file, after the recording of a VOD publish resource is
complete. This field indicates the action as “Notify” if configured and the
Notify URL.
PublishStreamInfo
(Stream | BitRate |
State)
The list of source profiles configured for this publish resource on the VOSM,
their corresponding configured bit rate, and the recording status for this profile
(Playout Only, Stopped, Failed, or Complete)
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
OL-28084-04
1-37
Chapter 1
Monitoring the VDS-OS
Transaction Logs
Cisco Videoscape Distribution Suite Origin Server Release 2.1.1 Software Installation and Configuration Guide
1-38
OL-28084-04
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising