- Preface
- Command-Line Interface Command Surmmary
- Cisco VDS Internet Streamer 4.2.1 Software Commands, aaa through line
- Cisco VDS Internet Streamer 4.3.1 Software Commands, lls through show statistics content-mgr
- Cisco VDS Internet Streamer 4.3.1 Software Commands, show statistic distribution through write
- Acronyms
- Standard Time Zones
Cisco Videoscape Distribution Suite, Internet Streamer 4.4.1 Command Reference Guide
- Updated:
- April 24, 2018
Chapter: Cisco VDS Internet Streamer 4.2.1 Software Commands, aaa through line
- aaa
- access-lists
- acquirer (EXEC)
- acquirer (Global configuration)
- acquisition-distribution
- alarm
- area nssa
- area stub
- asset
- authsvr
- bandwidth (Global configuration)
- bandwidth (interface configuration)
- banner
- bitrate
- blink
- bootstrap-node
- cache
- capability
- cd
- cdn-select
- cdnfs
- cdsm
- clear cache
- clear content
- clear ip
- clear ipv6
- clear isis
- clear logging
- clear service-router
- clear srp database offline
- clear srp descriptor
- clear srp neighbor
- clear srp resource
- clear srp route
- clear statistics
- clear transaction-logs
- clear users
- clear wmt
- clock (EXEC)
- clock (Global configuration)
- cms (EXEC)
- cms (Global configuration)
- configure
- contentmgr
- content-mgr disk-info force-reset
- content-origin
- copy
- cpfile
- debug
- debug ip bgp
- debug ip ospf
- debug ip proximity
- debug ip rib
- debug isis
- debug srp
- delfile
- deltree
- device
- dir
- direct-server-return
- disable
- disk (EXEC)
- disk (Global configuration)
- distribution
- dnslookup
- domain
- enable
- enable password
- end
- eviction-watermark
- exec-timeout
- exit
- expert-mode password
- external-ip
- find-pattern
- flash-media-streaming
- flooding
- geo-cache-size set
- geo-location-server
- gulp
- help
- hostname
- http-options
- install
- interface
- ip (Global configuration)
- ip (Interface configuration)
- ip access-list
- ip ospf priority
- ip rib route
- ip router isis
- ipv6
- isis
- is-type
- kernel
- key
- key-string
- key chain
- lacp
- line
Cisco Videoscape Distribution Suite, Internet Streamer Software Commands
This chapter contains an alphabetical listing of all the commands in Cisco Videoscape Distribution Suite, Internet Streamer (VDS-IS) software. The software CLI is organized into the following command modes:
- EXEC mode—For setting, viewing, and testing system operations. It is divided into two access levels, user and privileged. To use the privileged access level, enter the enable command at the user access level prompt and then enter the privileged EXEC password when you see the password prompt.
- Global configuration (config) mode—For setting, viewing, and testing the configuration of Internet Streamer VDS-IS software features for the entire device. To use this mode, enter the configure command from privileged EXEC mode.
- Interface configuration (config-if) mode—For setting, viewing, and testing the configuration of a specific interface. To use this mode, enter the interface command from Global configuration mode.
- Other configuration modes—Several configuration modes are available from the Global configuration mode for managing specific features. The commands used to access these modes are marked with a footnote in Table 2-1 .
See “Using Command Modes,” for a complete discussion of using CLI command modes.
Table 2-1 summarizes the commands and indicates the command mode for each command. The same command may have different effects when entered in a different command mode, and for this reason, they are listed and documented separately. In Table 2-1 , when the first occurrence is entered in EXEC mode, the second occurrence is entered in Global configuration mode. When the first occurrence is entered in Global configuration mode, the second occurrence is entered in interface configuration mode.
The VDS-IS software device mode determines whether the VDS-IS device is functioning as a Service Engine (SE), Content Delivery System Manager (CDSM), or Service Router (SR). The commands available from a specific CLI mode are determined by the VDS-IS device mode in effect. Table 2-1 also indicates the device mode for each command. All indicates that the command is available for every device mode.
Note
When viewing this guide online, click the name of the command in the left column of the table to jump to the command page, which provides the command syntax, examples, and usage guidelines.
Note See Appendix A, “Acronyms” for an expansion of all acronyms used in this publication.
|
|
|
|
|
|---|---|---|---|
Specifies accounting, authentication and authorization methods. |
|||
Enables authentication when the acquirer obtains content through a proxy server. |
|||
Starts and stops the acquisition and distribution database cleanup process and the content acquisition and distribution process. |
|||
Configures an area as an NSSA1. |
|||
Sets the allowable bandwidth usage and its duration for the Movie Streamer and WMT2 streaming media. |
|||
Sets the specified interface bandwidth to 10, 100, or 1000 Mbps. |
|||
Configures the EXEC, login, and MOTD3 banners. |
|||
Configures the maximum pacing bit rate for the Movie Streamer and configures WMT bit-rate settings. |
|||
Manages the Internet Streamer CDNFS4. |
|||
Configures the CDSM IP address and primary or standby role settings. |
|||
Deletes a single descriptor or all descriptors from the service routing layer. |
|||
Removes a neighbor Proximity Engine from the neighbor list of the local Proximity Engine. |
|||
Deletes a resource from a descriptor in the service routing layer. |
|||
Deletes a single route entry from the DHT routing table of the local Proximity Engine. |
|||
Configures the CMS5-embedded database parameters. |
|||
Schedules the maintenance and enables the Centralized Management System on a given node. |
|||
Forces the Content Manager to reset the disk share memory information. |
|||
Copies the configuration or image files to and from the CD-ROM, flash memory, disk, or remote hosts. |
|||
Reschedules and refreshes the content redistribution through multicast for all delivery services or a specified delivery service ID or name. |
|||
enable 6 |
|||
Deletes some of the cached objects and make available for the new object, using configuring eviction-watermark. |
|||
Exits from interface, Global configuration, or privileged EXEC modes. |
|||
Redirects requests to different CDNs based on the geographic location of the client. |
|||
Configures a Gigabit Ethernet or port channel interface. Provides access to interface configuration mode. |
|||
Creates and modifies the access lists for controlling access to interfaces or applications. Provides access to ACL configuration mode. |
|||
Sets the router priority, which helps determine the designated router for this network. |
|||
Configures a Proximity Engine to act as a Level 1 (intra-area) router, as both a Level 1 router and a Level 2 (interarea) router, or as an inter-area router only. |
|||
Creates a key ID and enters into key ID configuration submode. |
|||
Creates a key chain and enters into key chain configuration submode. |
|||
Configures the memory limit that is associated with a content manager, flash media streaming server, movie streamer, web engine, or the service-router, |
|||
Configures the community values that are associated with a Proximity Engine. |
|||
Configures the router to send a syslog message when an IS-IS neighbor goes up or down. |
|||
Configures syslog8. |
|||
Sets the maximum transmission unit MTU9 size of IS-IS LSPs. |
|||
Changes the CDE250 platform model number after a remanufacturing or rescue process. |
|||
Generate multicast packets and tests connectivity through multicast routers. |
|||
Defines the interfaces on which OSPF runs and defines the area ID for those interfaces. |
|||
Negates a Global configuration command or sets its defaults. |
|||
Configures a primary interface for the VDS-IS network to be a Gigabit Ethernet or port channel interface. |
|||
Enables a BGP proximity algorithm option for the Proximity Engine. |
|||
Enables the IS-IS routing protocol and specifies an IS-IS process. |
|||
Enables the OSPF12 routing process. |
|||
Configures the Real-Time Streaming Protocol-related parameters. |
|||
Sets the rules by which the SE filters HTTP, HTTPS, and RTSP traffic. |
|||
Configures the basic configuration settings and a set of commonly used caching services. |
|||
Displays the accounting, authentication, and authorization configuration. |
|||
Displays the acquirer delivery service information and progress for a specified delivery service number or name. |
|||
Displays information on various types of alarms, their status, and history. |
|||
Displays cache-route information for various Protocol Engines. |
|||
Displays the Centralized Management System protocol, embedded database content, maintenance status, and other information. |
|||
Displays information about the NAS13 mount. |
|||
Displays the configured or current mode of a CDSM, SE, or SR device. |
|||
Displays the distribution information for a specified delivery service. |
|||
Displays the caching configuration of the FTP14. |
|||
Displays the IP domain name, name servers, IP addresses, and host table. |
|||
Displays the information about access lists that are defined and applied to specific interfaces or applications. |
|||
Displays the contents of a particular host in the BGP routing table. |
|||
Displays BGP routes that match a specified BGP community string. |
|||
Displays information relating to all IPV4 unicast routes in the BGP routing table. |
|||
Displays memory usage information of the running BGP daemon. |
|||
Displays information about the TCP and BGP connections to neighbors. |
|||
Displays the next-hop database information in the BGP routing table. |
|||
Displays the IP interface state and its address and mask for all interfaces. |
|||
Displays information specific to the OSPF database for a specific router. |
|||
Displays a list of all LSAs15 requested by a router. |
|||
Displays OSPF RSPF16 from specific routers. |
|||
Displays the proximity algorithm options currently in use by this Proximity Engine. |
|||
Displays the proximity interface information currently in use by this Proximity Engine. |
|||
Displays the interface addresses and hostnames of the proximity servers currently in use by this Proximity Engine. |
|||
Displays details of all the routing protocol instances that are clients of the RIB. |
|||
Displays one or all the destinations to which the router knows how to route CLNS packets. |
|||
Displays the router-name-to-system-ID mapping table entries for an IS-IS router. |
|||
Displays the Intermediate IS-IS RSPF route for IS-IS learned routes. |
|||
Displays the Intermediate IS-IS RSPF route for IS-IS learned routes. |
|||
Displays IS-IS RRM17 information. |
|||
Displays how often and why the router has run a full SPF18 calculation. |
|||
Displays SRM19 information for an IS-IS process. |
|||
Displays SSN20 information for an IS-IS process. |
|||
Displays whether or not the multicast sender and receiver are enabled. |
|||
Displays the descriptor-related information saved in the descriptor database. |
|||
Displays the replica-set information for a Proximity Engine. |
|||
Displays route information for a Proximity Engine to its neighbor nodes on the same DHT network. |
|||
Displays accounting, authentication, and authorization statistics. |
|||
Displays the SE Internet Streamer VDS-IS network file system statistics. |
|||
Displays the simplified statistics for content distribution components. |
|||
Displays the delivery service replication status and related statistical data. |
|||
Displays the Service Engine TACACS+ authentication and authorization statistics. |
|||
Displays TACACS+ authentication protocol configuration information. |
|||
Displays the system information for Cisco technical support. |
|||
Displays the user identification number and username information. |
|||
Shuts down the device (stops all applications and operating system). |
|||
Configures the community access string to permit access to the SNMP. |
|||
Defines an SNMPv221 MIB view. |
|||
Forces archiving of the working log file to make a transaction log file. |
|||
Configures the Web Engine caching parameters and disables revalidation. |
|||
Writes or erases the startup configurations to NVRAM or to a terminal session, or writes the MIB persistence configuration to disk. |
|
|
aaa
To specify accounting, authentication, and authorization methods, use the aaa command in global configuration mode. To selectively disable options, use the no form of this command.
aaa {accounting {commands {0 {start-stop tacacs + | stop-only tacacs+} | 15 {start-stop tacacs + | stop-only tacacs+}} | exec {start-stop tacacs + | stop-only tacacs+} | system {start-stop tacacs + | stop-only tacacs+}} | authentication {enable {primary | secondary | tertiary} | radius {primary | secondary | tertiary} | tacacs+ {primary | secondary | tertiary}} | login {fail-over server-unreachable | local {primary | secondary | tertiary} | radius {primary | secondary | tertiary} | tacacs+ {primary | secondary | tertiary}} | authorization {commands {0 tacacs+ [if-authenticated] | 15 tacacs+ [if-authenticated]} | config-commands | console | exec {local {primary | secondary | tertiary} | radius {primary | secondary | tertiary} | tacacs+ {primary | secondary | tertiary}}}}
no aaa {accounting {commands {0 {start-stop tacacs + | stop-only tacacs+} | 15 {start-stop tacacs + | stop-only tacacs+}} | exec {start-stop tacacs + | stop-only tacacs+} | system {start-stop tacacs + | stop-only tacacs+}} | authentication {enable {enable {primary | secondary | tertiary} | radius {primary | secondary | tertiary} | tacacs+ {primary | secondary | tertiary}} | login {fail-over server-unreachable | local {primary | secondary | tertiary} | radius {primary | secondary | tertiary} | tacacs+ {primary | secondary | tertiary}} | authorization {commands {0 tacacs+ [if-authenticated] | 15 tacacs+ [if-authenticated]} | config-commands | console | exec {local {primary | secondary | tertiary} | radius {primary | secondary | tertiary} | tacacs+ {primary | secondary | tertiary}}}}
Syntax Description
Specifies a condition to switch to a local authentication scheme. |
|
Uses Tacacs+ hosts for authorization Tacacs+ hosts for authorization. |
Defaults
Command Modes
Usage Guidelines
The aaa accounting commands command enables accounting using TACACS+ for normal and supper users.
The aaa accounting exec command enables accounting records for user EXEC terminal sessions on the Tacacs+ server, including username, date, start, and stop times.
The aaa accounting system command enables accounting of the system events, such as system reboot, NIC interface up or down, accounting configuration enabled or disabled, and using TACACS+.
The aaa authentication login command enables authentication using TACACS+ or the RADIUS server to determine if the user has access permission on the SE. The local authentication uses the local database for authentication, if configured. This can be enabled to provide a fallback in case of TACACS+ or Radius server failure.
If there are multi-authentication methods configured, the SE tries to authenticating the user through all configured methods, one by one, until one of them succeeds. The authentication order complies with the priority specified (primary, secondary, then tertiary). If the primary is empty, the secondary is considered as primary, and so on.
If the configured TACACS+ or Radius server is unreachable, use the aaa authentication login fail-over server-unreachable command to switch off the TACACS+ or Radius server, and enable fail-over to use the local password file for authentication.
The aaa authentication enable command enables authentication using TACACS+ or the RADIUS server to determine if the normal user can enter the privileged exec mode. Alternatively, the enable authentication method uses the local database (the enable password) for authentication.
The aaa authorization command enables authorization using the TACACS+ server to determine if the specified user can execute commands or not. In case the configured TACACS+ server is unreachable, the if-authenticated option can switch off the TACACS+ server and authorization is granted to anyone who is authenticated.
Note The following commands bypass authorization and accounting:
CTRL+C, CTRL+Z, exit, end, and all of configuration commands for entering submode, for example, interface GigabitEthernet 1/0.
The aaa authorization config-commands command reestablishes the default created when the aaa authorization commands command was issued.
If the aaa authorization commands level method command is enabled, all commands, including configuration commands, are authorized using the method specified for the specified user. To bypass the configuration commands, using the no aaa authorization config-commands command stops the network access server from attempting configuration command authorization.
After the no form of this command is entered, AAA authorization of configuration commands is completely disabled. Take care before entering the no form of this command because it potentially reduces the amount of administrative control on configuration commands.
Use the aaa authorization config-commands command if, after using the no form of this command, you need to reestablish the default set by the aaa authorization commands level method command.
Note This command is disabled by default. You get the same result if you (1) do not configure this command, or (2) configure the no aaa authorization config-commands.
The aaa authorization console command applies authorization to a console. To disable the authorization, use the no form of this command.
The no aaa authorization console command is the default, and the authorization that is configured on the console line always succeeds. If you do not want the default, you need to configure the aaa authorization console command.
The aaa authorization exec command enables authorization using the TACACS+ or RADIUS server to determine if the user can startup an exec (shell). The local authentication uses the local database for authorization, if configured. This can be enabled to provide a fallback in case the TACACS+ or Radius server fails.
If you are trying to disable the aaa authorization exec command, at least one authorization method must be selected (local is the default). At least one authentication method must be selected for login.
Note As long as the login authentication fail-over is enabled, it is applied to the exec authorization as well. In other words, the local database is used for authorization as well if the remote severs is unreachable.
Examples
The following configures accounting commands for a normal user using Tacacs+ hosts:
The following example enables/disables authentication for login:
The following example applies authorization to a console:
Related Commands
|
|
|
access-lists
To configure access control list (ACL) entries, use the access-lists command in Global configuration mode. To remove access control list entries, use the no form of this command.
access-lists {300 {deny groupname {any [position number ] | groupname [ position number ]}} | { permit groupname {any [position number ] | groupname [ position number ]}} | enable }
no access-lists {300 {deny groupname {any [position number ] | groupname [ position number }} | { permit groupname {any [position number ] | groupname [ position number ]}} | enable }
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
You can configure group authorization using an ACL only after a user has been authenticated against an LDAP HTTP-request Authentication Server. The use of this list configures group privileges when members of the group are accessing content provided by an SE. You can use the ACL to allow the users who belong to certain groups or to prevent them from viewing specific content. This authorization feature offers more granular access control by specifying that access is only allowed to specific groups.
Use the access-lists enable Global configuration command to enable the use of the ACL.
Use the access-lists 300 command to permit or deny a group from accessing the Internet using an SE. For instance, use the access-lists 300 deny groupname marketing command to prevent any user from the marketing group from accessing content through an SE.
At least one login authentication method, such as local, TACACS+, or RADIUS, must be enabled.
Note We recommend that you configure the local login authentication method as the primary method.
The ACL contains the following feature enhancements and limitations:
- A user can belong to several groups.
- A user can belong to an unlimited number of groups within group name strings.
- A group name string is a case-sensitive string with mixed-case alphanumeric characters.
- Each unique group name string cannot exceed 128 characters.
Note If the unique group name string is longer than 128 characters, the group is ignored.
- Group names in a group name string are separated by a comma.
- Total string of individual group names cannot exceed 750 characters.
For Windows-based user groups, append the domain name in front of the group name in the form domain or group as follows:
For Windows NT-based user groups, use the domain NetBIOS name.
The access-list command does not use a netmask; it uses a wildcard bitmask. The source and destination IP and wildcard usage is as follows:
- source_ip—Number of the network or host from which the packet is being sent. There are three alternative ways to specify the source:
– Use a 32-bit quantity in four-part dotted decimal format.
– Use the any keyword => source and source-wildcard of 0.0.0.0 255.255.255.255.
– Use the host keyword => specific source and source_wildcard equal 0.0.0.0.
- source-wildcard—Wildcard bits to be applied to source. Each wildcard bit set to 0 indicates the corresponding bit position in the source. Each wildcard bit set to 1 indicates that both a 0 bit and a 1 bit in the corresponding position of the IP address of the packet is considered a match to this access list entry.
To specify the source wildcard, use a 32-bit quantity in four-part dotted decimal format. Place 1s in the bit positions you want to ignore.
Note Wildcard bits set to 1 need not be contiguous in the source wildcard. For example, a source wildcard of 0.255.0.64 would be valid.
Examples
The following example shows how to display the configuration of the ACL by using the show access-lists 300 command:
The following example shows how to display statistical information for the ACL by using the show statistics access-lists 300 command:
The following example shows how to reset the statistical information for the ACL by using the clear statistics access-lists 300 command:
Related Commands
|
|
|
acquirer (EXEC)
To start or stop content acquisition on a specified acquirer delivery service, use the acquirer command in EXEC configuration mode. You can also use this command to verify and correct the Last-Modified-Time attribute in content acquired using the VDS-IS software.
acquirer { check-time-for-old-content [ delivery-service-id delivery-service-num | delivery-service-name delivery-service-name ] | [ correct [ delivery-service-id delivery-service-num | delivery-service-name delivery-service-name ]] | start-delivery-service {delivery-service-id delivery-service-num | delivery-service-name delivery-service-name } | stop-delivery-service {delivery-service-id delivery-service-num | delivery-service-name delivery-service-name } | test-url url [ use-http-proxy url | use-smb-options smb-options ]}
Syntax Description
Defaults
If you do not specify the delivery service, this command applies to all delivery services assigned to the Content Acquirer.
Command Modes
Usage Guidelines
The acquirer is a software agent that gathers delivery service content before it is distributed to the receiver SEs in an VDS-IS network. The acquirer maintains a task list, which it updates after receiving a notification of changes in its delivery service configuration.
The acquirer stores the Last-Modified-Time attribute in the local time format. Content acquired using earlier software releases has a Last-Modified-Time attribute that is incorrect if used with later versions of the VDS-IS software, which use GMT format.
Correct the Last-Modified-Time attributes for content acquired with earlier releases by entering the following command from the privileged EXEC prompt:
acquirer check-time-for-old-content correct [delivery-service-id delivery-service-num delivery-service-name delivery-service-name ]
This command changes the Last-Modified-Time attributes for content in all delivery services assigned to the Content Acquirer unless you specify the delivery service ID or name.
SEs identify changes in the Last-Modified-Time attribute and download content only when changes have occurred.
Use the acquirer start-delivery-service command to immediately start acquisition tasks for the selected delivery service. Use the acquirer stop-delivery-service command to immediately stop all acquisition tasks for the selected delivery service.
Use the acquirer test-url url command in EXEC configuration mode to test whether a URL is accessible or not. The actual content is dumped into the /dev/null path.
Examples
The following example shows how the acquirer starts acquiring content on delivery service 86:
The following example shows how the acquirer stops acquiring content on delivery service 86:
The following example shows how the acquirer test-url command is used to test a URL:
Related Commands
|
|
|
Displays the acquirer delivery service information and progress for a specified delivery service number or name. |
|
acquirer (Global configuration)
To provide authentication when the acquirer obtains content through a proxy server, use the acquirer command in Global configuration mode. To disable acquirer proxy authentication, use the no form of this command.
acquirer proxy authentication {outgoing { hostname | ip-address } port-num} username | password password }
no acquirer proxy authentication {outgoing { hostname | ip-address } port-num} username | password password }
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
Use the acquirer proxy authentication outgoing Global configuration command to configure authentication when you enable content acquisition through a proxy server. First configure the proxy host and the port using the http proxy outgoing host Global configuration command. The maximum number of outgoing proxies allowed is eight. When you remove an outgoing proxy using the no http outgoing proxy command, the authentication information associated with that proxy is automatically removed.
Use the acquirer proxy authentication transparent command for transparent caches in the VDS-IS network that require authentication.
The acquirer supports a proxy with basic authentication. Content acquisition through a proxy server is supported only for HTTP and not for HTTPS or FTP. Also, authentication is only supported for a single proxy server in a chain, so if multiple proxy servers in a chain require authentication, the request fails.
Acquisition through a proxy server can be configured when the Content Acquirer cannot directly access the origin server because the origin server is set up to allow access only by a specified proxy server. When a proxy server is configured for Content Acquirer content acquisition, the acquirer contacts the proxy server instead of the origin server, and all requests to that origin server go through the proxy server.
Note Content acquisition through a proxy server is only supported for HTTP requests. It is not supported for HTTPS, FTP, MMS, or MMS-over-HTTP requests.
There are three ways to configure the proxy server: through the CDSM GUI. If you need to configure the SE to use the proxy for both caching and prepositioned content, use the CLI to configure the proxy. The CLI command is a Global configuration command that configures the entire SE to use the proxy. If only the acquirer portion of the SE needs to use the proxy for acquiring the prepositioned content, use the manifest file or specify the outgoing proxy. When you configure the proxy server in the manifest file, you are configuring the acquirer to use the proxy to fetch the content for a particular delivery service.
Note Proxy configurations in the manifest file take precedence over proxy configurations in the CLI. A noProxy attribute configuration in the manifest file takes precedence over the other proxy server configurations in the manifest file.
You can also configure a proxy for fetching the manifest file by using the CDSM GUI (the Creating New Delivery Service or Modifying Delivery Service window). When you configure a proxy server in the CDSM GUI, the proxy configuration is valid only for acquiring the manifest file and not for acquiring the delivery service content. Requests for the manifest file go through the proxy server, and requests for the content go directly to the origin server.
Tip Before configuring a proxy server, verify that the Content Acquirer is able to ping the proxy server. To check whether the proxy server is accepting incoming HTTP traffic at the configured port, use the acquirer test-url http://proxyIP:proxyport command in Global configuration mode in the Content Acquirer CLI, where the URL in the command is the URL of the proxy server being tested. If the proxy is not servicing the configured port, the message “failed: Connection refused.”
Examples
The following example shows the authentication configuration for a transparent proxy server with basic authentication:
Related Commands
acquisition-distribution
To start or stop the content acquisition and distribution process, use the acquisition-distribution command in EXEC configuration mode.
acquisition-distribution {database-cleanup { start | stop } | start | stop }
Syntax Description
Defaults
Command Modes
Usage Guidelines
When you use the acquisition-distribution database-cleanup command, the acquisition and distribution database is checked to ensure that all prepositioned content is available in Cisco Network File System (CDNFS). If any prepositioned content is found to be missing from CDNFS, the content is replicated to all SEs in the VDS-IS network. Content Acquirers assigned to a delivery service acquire the content directly from the origin server and replicate the content through the delivery service either by unicast or multicast transmission to other SEs in the delivery service. Receiver SEs obtain the content from forwarder SEs either by unicast or multicast. In the case of a disk00 failure, when the database is stored on disk00 in an internal file system (/state), the recovery of the acquisition and distribution database is done automatically. You should run the acquisition and distribution database cleanup if a failure occurs or if you have to replace a disk drive other than disk00.
Examples
The following example shows how to start the acquisition and distribution database cleanup process:
The following example shows how to start the acquisition and distribution process:
The following example shows how to stop the acquisition and distribution process:
Related Commands
alarm
To configure alarms, use the alarm command in Global configuration mode. To disable alarms, use the no form of this command.
alarm {admin-shutdown-alarm enable | overload-detect {clear 1-999 [ raise 10-1000 ] | enable | raise 10-1000 [ clear 1-999 ]}}
no alarm {admin-shutdown-alarm enable | overload-detect {clear 1-999 [ raise 10-1000 ] | enable | raise 10-1000 [ clear 1-999 ]}}
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
The alarm admin-shutdown-alarm command must be enabled for an admin-shutdown alarm to take effect. If an admin-shutdown alarm occurs, disabling this option does not clear the outstanding alarm properly. There are two ways to avoid this situation:
- Clear the outstanding admin-shutdown alarm first before disabling this option.
- Disable this option and reboot, which clears this alarm.
When multiple applications running on an SE experience problems at the same time, numerous alarms are set off simultaneously, and an SE may stop responding. Use the alarm overload-detect command to set an overload limit for the incoming alarms from the node Health Manager. If the number of alarms exceeds the maximum number of alarms allowed, an SE enters an alarm overload state until the number of alarms drops down to the number defined in the clear.
When an SE is in the alarm overload state, the following events occur:
- Alarm overload notification is sent to SNMP and the CMS. The clear and raise values are also communicated to SNMP and the CMS.
- SNMP traps and CMS notifications for subsequent alarm raise and clear operations are suspended.
- Alarm overload clear notification is sent.
- SE remains in the alarm overload state until the rate of incoming alarms decreases to the clear value.
Note In the alarm overload state, applications continue to raise alarms and the alarms are recorded within an SE. The show alarms and show alarms history command in EXEC configuration modes display all the alarms even in the alarm overload state.
Examples
The following example shows how to generate a linkdown alarm when an interface shuts down:
The following example shows how to enable the detection of alarm overload:
The following example shows how to set the threshold for triggering the alarm overload at 100 alarms per second:
The following example shows how to set the level for clearing the alarm overload at 10 alarms per second:
Related Commands
|
|
|
Displays information on various types of alarms, their status, and history. |
|
Displays the status of various alarms and alarm overload settings. |
area nssa
To configure an area as a not-so-stubby area (NSSA), use the area nssa router configuration command. To remove the NSSA distinction from the area, use the no form of this command.
Syntax Description
Identifier of the area for which authentication is to be enabled. The identifier can be specified as either a decimal value or an IP address (ID range is from 0 to 4294967295). |
Command Default
Command Modes
OSPF configuration (config-ospf) mode.
Usage Guidelines
This command is used to configure an area as a NSSA. The area ID range is given as 0 to 4294967295, but area 0 cannot be configured as an NSSA area.
Examples
In the following example area 1 is configured as an NSSA area:
area stub
To define an area as a stub area, use the area stub router configuration command. To disable this function, use the no form of this command
Syntax Description
Identifier for the stub area. The identifier can be specified as either a decimal value or an IP address (ID range is from 0 to 4294967295). |
Command Default
Command Modes
OSPF configuration (config-ospf) mode.
Usage Guidelines
This command is used to define an area as a stub area. The area ID range is given as 0 to 4294967295, but area 0 cannot be configured as a stub area.
Examples
The following example shows how to configure area 1 as a stub area:
asset
To configure the CISCO-ENTITY-ASSET-MIB, use the asset command in Global configuration mode. To remove the asset tag name, use the no form of this command.
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Examples
The following example shows how to configure a tag name for the asset tag string:
authsvr
To enable and configure the Authorization server, use the authsvr command in Global configuration mode. To disable the Authorization server, use the no form of this command.
authsvr {enable | geo-cache-size set num | location-server {cache-timeout num | enable | primary ip addr port num [ service-name name ] [ retry num ] [ timeout num ] | secondary ip addr port num [ service-name name ] [ retry num ] [ timeout num ] | server-type [ maxmind-restful-hosted [ http | https ] service name | quova-restful-gds | quova-restful-hosted [ http [ api-key key | shared-secret secret ] ] ]} | unknown-server allow}
no authsvr {enable | geo-cache-size set num | location-server {cache-timeout num | enable | primary ip addr port num [ service-name name ] [ retry num ] [ timeout num ] | secondary ip addr port num [ service-name name ] [ retry num ] [ timeout num ] | server-type [ maxmind-restful-hosted [ http | https ] service name | quova-restful-gds | quova-restful-hosted [ http [ api-key key | shared-secret secret ] ] ]} | unknown-server allow}
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
Changing the primary or secondary Geo-Location server configuration requires a restart of the authsvr for the configuration change to take effect. To restart the authsvr, disable it by entering the no authsvr enable and then re-enable it by entering the authsvr enable command.
The no authsvr unknown-server allow command causes all blocked requests to increment the authsvr block statistic.
Examples
The following example shows how to enable the Authorization server:
Related Commands
|
|
|
bandwidth (Global configuration)
To set an allowable bandwidth usage limit and its duration for Cisco Streaming Engine Windows Media Technology (WMT) streaming media, use the bandwidth command in Global configuration mode. To remove individual options, use the no form of this command.
bandwidth {{movie-streamer {incoming bandwidth | outgoing bandwidth}{default | max-bandwidth | start-time day hour end-time day hour}} | wmt {{incoming bandwidth | outgoing bandwidth}{default | max-bandwidth | start-time day hour end-time day hour} }}
no bandwidth {{movie-streamer {incoming bandwidth | outgoing bandwidth}{default | max-bandwidth | start-time day hour end-time day hour}} | wmt {{incoming bandwidth | outgoing bandwidth}{default | max-bandwidth | start-time day hour end-time day hour} }}
Syntax Description
Configures the maximum pacing bit rate, in kilobits per second (kbps), for the Movie Streamer. |
|
Configures the duration of allowable incoming bandwidth settings for WMT. |
|
Bandwidth size for the Movie Streamer, in kbps. The range is from 0 to 2147483647. |
|
Configures the duration of allowable outgoing bandwidth settings for WMT. |
|
Specifies the default value for bandwidth if the scheduled bandwidth is not configured. |
|
Configures the duration of allowable bandwidth settings for WMT. For more information, see the “Configuring Incoming and Outgoing WMT Bandwidth” section. |
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
With the various types of traffic originating from a device, every type of traffic, such as streaming media, HTTP, and metadata, consumes network resources. Use the bandwidth command to limit the amount of network bandwidth used by the WMT streaming media.
The content services bandwidth includes the bandwidth allocation for WMT. WMT bandwidth settings apply to WMT streaming of live, cached, and prepositioned content.
For each type of bandwidth, you can specify the amount of bandwidth to be used for a particular time period. This type is called scheduled bandwidth. The default bandwidth is the amount of bandwidth associated with each content service type when there is no scheduled bandwidth. In centrally managed deployments (the SEs are registered with a CDSM), if the SE is assigned to a device group and no default bandwidth has been configured for the SE itself, the device group default bandwidth settings are applied. However, if the default bandwidth has been configured for the SE, then that setting overrides the device group settings. If the SE is a member of multiple device groups, the most recently updated default bandwidth settings are applied.
The maximum bandwidth specifies the upper limit for the allowable bandwidth. The total bandwidth configured for all content services must not exceed the bandwidth limits specified for any SE platform model in the VDS-IS network. In addition, the license keys configured for WMT further restrict the maximum bandwidth available for each SE model.
Configuring Incoming and Outgoing WMT Bandwidth
The bandwidth between the WMT proxy server (the SE) and the WMT client is called the WMT outgoing bandwidth.
The bandwidth between the WMT proxy and the origin streaming server is called the incoming bandwidth. Because the bandwidth from the edge to the outside IP WAN is limited, you must specify a per session limit (the maximum bit rate per request) for each service that is running on the SE and that consumes the incoming bandwidth (for example, the WMT streaming service), and an aggregate limit (the maximum incoming bandwidth.) You need to control the outgoing bandwidth based on the WMT license that is configured on the SE.
The bandwidth wmt outgoing and bandwidth incoming commands enable you to specify a WMT incoming and an outgoing bandwidth as follows:
- Use the bandwidth wmt outgoing kbits command in Global configuration mode to specify the outgoing WMT bandwidth in kbps. This command sets the maximum bandwidth for the WMT content that can delivered to a client that is requesting WMT content. The range of values is between 0 and 2,147,483,647 kbps.
If the specified outgoing bandwidth is above the limit specified by the WMT license, then a warning message is displayed. However, the specified outgoing bandwidth setting is applied to the SE because the outgoing bandwidth may be configured before the WMT licenses are enabled or an enabled WMT license may be changed to a higher value at a later time.
- Use the bandwidth wmt incoming kbits command in Global configuration mode to specify the incoming WMT bandwidth in kbps. This command sets the maximum bandwidth for the WMT content that can delivered to the SE from the origin streaming server or another SE in the case of a cache miss. The specified bit rate is the maximum incoming WMT per session bit rate. The range of values is between 0 and 2,147,483,647 kbps. The incoming bandwidth applies to VoD content from the origin server for a cache miss.
Related Commands
|
|
|
Sets the specified interface bandwidth to 10, 100, or 1000 Mbps. |
|
Configures a Gigabit Ethernet or port channel interface. Provides access to interface configuration mode. |
|
bandwidth (interface configuration)
To configure an interface bandwidth, use the bandwidth command in interface configuration mode. To restore default values, use the no form of this command.
no bandwidth { 10 | 100 | 1000 }
Syntax Description
Sets the bandwidth to 1000 Mbps. This option is not available on all ports. |
Defaults
Command Modes
Interface configuration (config-if) mode.
Usage Guidelines
The bandwidth is specified in Mbps. The 1000 Mbps option is not available on all ports. On an SE model that has an optical Gigabit Ethernet interface, you cannot change the bandwidth of this interface. Therefore, Gigabit Ethernet interfaces run only at 1000 Mbps. For newer models of the SE that have a Gigabit Ethernet interface over copper, this restriction does not apply; you can configure these Gigabit Ethernet interfaces to run at 10, 100, or 1000 Mbps.
You can configure the Gigabit Ethernet interface settings (bandwidth, and duplex settings) if the Gigabit-over-copper-interface is up or down. If the interface is up, it applies the specific interface settings. If the interface is down, the specified settings are stored and then applied when the interface is brought up. For example, you can specify any of the following commands for a Gigabit-over-copper-interface, which is currently down, and have these settings automatically applied when the interface is brought up:
ServiceEngine(config-if)# bandwidth 10
ServiceEngine(config-if)# bandwidth 100
ServiceEngine(config-if)# bandwidth 1000
You cannot configure the Gigabit Ethernet interface settings on an optical Gigabit Ethernet interface.
Examples
The following example shows how to set an interface bandwidth to 10 Mbps:
The following example shows how to restore default bandwidth values on an interface:
Related Commands
|
|
|
Configures a Gigabit Ethernet or port channel interface. Provides access to interface configuration mode. |
banner
To configure the EXEC, login, and message-of-the-day (MOTD) banners, use the banner command in Global configuration mode. To disable the banner feature, use the no form of this command.
banner {enable | exec {message line | message_text } | login {message line | message_text } | motd {message line | message_text }}
no banner {enable | exec [message ] | login [message ] | motd [message ]}
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
You can configure the following three types of banners in any VDS-IS software device mode:
- MOTD banner sets the message of the day. This message is the first message that is displayed when a login is attempted.
- Login banner is displayed after the MOTD banner but before the actual login prompt appears.
- EXEC banner is displayed after the EXEC CLI shell has started.
Note All these banners are effective on a console, Telnet, or a Secure Shell (SSH) Version 2 session.
After you configure the banners, enter the banner enable command to enable banner support on the SE. Enter the show banner command in EXEC configuration mode to display information about the configured banners.
Note When you run an SSH Version 1 client and log in to the SE, the MOTD and login banners are not displayed. You need to use SSH Version 2 to display the banners when you log in to the SE.
Examples
The following example shows how to enable banner support on the SE:
ServiceEngine(config)# banner enable
The following example shows how to use the banner motd message command to configure the MOTD banner. In this example, the MOTD message consists of a single line of text.
ServiceEngine(config)# banner motd message This is an Internet Streamer CDS 2.3 device
The following example shows how to use the banner motd message global command to configure a MOTD message that is longer than a single line. In this case, the SE translates the \n portion of the message to a new line when the MOTD message is displayed to the user.
ServiceEngine(config)# banner motd message "This is the motd message.\nThis is an Internet Streamer CDS 2.3 device\n"
The following example shows how to use the banner login message command to configure a MOTD message that is longer than a single line. In this case, SE A translates the \n portion of the message to a new line in the login message that is displayed to the user.
ServiceEngine(config)# banner login message "This is login banner.\nUse your password to login\n"
The following example shows how to use the banner exec command to configure an interactive banner. The banner exec command is similar to the banner motd message commands except that for the banner exec command, the banner content is obtained from the command-line input that the user enters after being prompted for the input.
Assume that the SE has been configured with the MOTD, login, and EXEC banners as shown in the previous examples. When a user uses an SSH session to log in to the SE, the user sees a login session that includes a MOTD banner and a login banner that asks the user to enter a login password as follows:
This is the motd banner.
This is an Internet Streamer CDS 2.3 device
This is login banner.
Cisco SE
admin@ce's password:
After the user enters a valid login password, the EXEC banner is displayed, and the user is asked to enter the VDS-IS username and password as follows:
Last login: Fri Oct 1 14:54:03 2004 from client
System Initialization Finished.
This is the EXEC banner.
After the user enters a valid VDS-IS username and password, the SE CLI is displayed. The CLI prompt varies depending on the privilege level of the login account. In the following example, because the user entered a username and password that had administrative privileges (privilege level of 15), the EXEC configuration mode CLI prompt is displayed:
ServiceEngine#
Related Commands
|
|
|
bitrate
To configure the maximum pacing bit rate for large files for the Movie Streamer and to separately configure WMT bit-rate settings, use the bitrate command in Global configuration mode. To remove the bit-rate settings, use the no form of this command.
bitrate {movie-streamer {incoming bitrate | outgoing bitrate} | wmt {incoming bitrate | outgoing bitrate}}
no bitrate {movie-streamer {incoming bitrate | outgoing bitrate} | wmt {incoming bitrate | outgoing bitrate}}
Syntax Description
Defaults
movie-streamer bitrate : 1500 kbps
Command Modes
Global configuration (config) mode.
Usage Guidelines
The WMT proxy has the ability to cache on-demand media files when the user requests these files for the first time. All subsequent requests for the same file are served by the WMT proxy using the RTSP protocol. The WMT proxy can also live-split a broadcast, which causes only a single unicast stream to be requested from the origin server in response to multiple client requests for the stream.
The bit rate between the proxy and the origin server is called the incoming bit rate. Use the bitrate command to limit the maximum bit rate per session for large files. The bitrate wmt incoming and bitrate wmt outgoing commands enable you to specify a WMT incoming and outgoing per session bit rate as follows:
- Use the bitrate wmt incoming bitrate command to specify the maximum incoming streaming bit rate per session that can be delivered to the WMT proxy server (the SE) from the origin streaming server or another SE in the case of a cache miss. The specified bit rate is the maximum incoming WMT per session bit rate. The range of values is between 0 and 2,147,483,647 kbps. The default value is 0 (no bit-rate limit).
- Use the bitrate wmt outgoing bitrate command to set the maximum outgoing streaming bit rate per session that can delivered to a client requesting WMT content. The specified bit rate is the maximum outgoing WMT per session bit rate). The range of values is between 0 and 2,147,483,647 kbps. The default value is 0 (no bit-rate limit). The outgoing bandwidth applies to VoD content from the WMT proxy server on the SE in the case of a cache miss.
Note The aggregate bandwidth used by all concurrent users is still limited by the default device bandwidth or by the limit configured using the bandwidth command.
A content provider can create streaming media files at different bit rates to ensure that different clients who have different connections—for example, modem, DSL, or LAN—can choose a particular bit rate. The WMT caching proxy can cache multiple bit-rate files or variable bit-rate (VBR) files, and based on the bit rate specified by the client, it serves the appropriate stream. Another advantage of creating variable bit-rate files is that you only need to specify a single URL for the delivery of streaming media.
Note In the case of multiple bit-rate files, the SE that is acting as the WMT proxy server retrieves only the bit rate that the client has requested.
Examples
The following example shows how to configure an incoming bit rate for the Movie Streamer:
The following example shows how to configure an incoming bit rate for a file sent using WMT. Use the show wmt command to verify that the incoming bit rate has been modified.
Related Commands
|
|
|
blink
To identify physical devices by blinking their LED(s), use the blink command in EXEC configuration mode.
blink {disk name | interface {GigabitEthernet slot/port_num | TenGigabitEthernet slot/port_num}}
Syntax Description
Slot and port number for the selected interface. The slot range is from 1 to 14; the port range is from 0 to 0. The slot number and port number are separated with a forward slash character (/). |
|
Command Default
Command Modes
Usage Guidelines
The blink disk command submits IO to a disk, do not use this command in systems with live traffic.
Examples
The following example shows how to blink a disk:
The following example shows how to blink a GigabitEthernet interface:
bootstrap-node
To configure a bootstrap node IP address, use the bootstrap-node Service Routing Protocol (SRP) configuration command. To remove a bootstrap node address, use the no or default form of the command.
[ no | default ] bootstrap-node ip-address
Syntax Description
Valid IP address for the bootstrap node. IP addresses 0.0.0.0 and 255.255.255.255 are not valid addresses for a bootstrap node. |
Command Default
Command Modes
SRP configuration (config-srp) mode.
Usage Guidelines
This command is used to set bootstrap nodes for an SRP. A Proximity Engine specifies one or more bootstrap nodes to join a DHT network. In a DHT network, the domain ID of the bootstrap nodes and the Proximity Engine must the same.
The first Proximity Engine in the network, which acts as the bootstrap node for others, does not have to configure the bootstrap node address itself. This is the only exception to configuring bootstrap nodes. All other nodes need to configure a bootstrap node address before they can join any network.
The no and default forms of the command remove a given bootstrap node from the list of available bootstrap nodes of a Proximity Engine. The port number for bootstrap node is 9000. The show srp process command lists configured bootstrap nodes.
A Proximity Engine cannot be its own bootstrap node. A maximum 25 bootstrap nodes are allowed.
Examples
The following example shows how to configure a bootstrap node address with the bootstrap-node command :
The following example shows how the show srp process command displays configured bootstrap nodes:
Related Commands
|
|
|
cache
To restrict the maximum number of contents in the VDS-IS, use the cache command in Global configuration mode.
cache content {eviction-preferred-size {small | large} | eviction-protection {min-size-100MB {min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr} | min-size-1GB {min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr} | min-size-4GB {min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr} | min-size-500MB {min-duration-1hr | min-duration-2hr | min-duration-3hr| min-duration-4hr}} | small-file-eviction-protection {max-size-10MB {min-duration-10min | min-duration-15min | min-duration-30min | min-duration-5min} | max-size-1MB {min-duration-10min | min-duration-15min | min-duration-30min | min-duration-5min} | max-size-20MB {min-duration-10min | min-duration-15min | min-duration-30min | min-duration-5min} | max-size-2MB {min-duration-10min | min-duration-15min | min-duration-30min | min-duration-5min} | max-size-4MB {min-duration-10min | min-duration-15min | min-duration-30min | min-duration-5min} | max-size-500KB {min-duration-10min | min-duration-15min | min-duration-30min | min-duration-5min}} | max-cached-entries num | max-cached-dirs num }
cache content {eviction-preferred-size {small | large} | eviction-protection { min-size-100MB { min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr }| min-size-1GB { min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr } | min-size-4GB { min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr } | min-size-500MB { min-duration-1hr | min-duration-2hr | min-duration-3hr | min-duration-4hr }}| max-cached-entries num | max-cached-dirs num }
Syntax Description
Selects cache content eviction preferred size (Retain smaller objects). |
|
Selects cache content eviction preferred size (Retain larger objects). |
|
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
The Content Manager manages the caching, storage, and deletion of content.
Current priority favors small objects. The cache content eviction-preferred size command allows users to configure a preference for small or large objects in the Content Manager. Once a preference is specified, it only applies on contents made after the configurative; contents prior to configuration remain unchanged.
Addition and Deletion Processes
Previously, the VDS-IS software did not restrict adding new content to CDNFS as long as there was enough disk space for the asset. The cache content max-cached-entries command restricted the number of assets, but it was not a hard limit. New content was always added and the CDS would delete old content in an attempt to keep within the limits configured. The CDS could actually have more content than the configured limit, because the process to delete content is slower than the process to add content. The same situation applies to disk-usage based deletion, where deletion occurs when 90 percent of the CDNFS is used.
Content addition stops at 105 percent of the maximum object count or 95 percent of the CDNFS capacity (disk usage). For example, if the maximum number of objects has been configured as 50 million, the VDS-IS starts deleting content if the object count reaches 50 million, but adding content is still allowed. Adding content stops when the maximum number of content objects reaches 52.5 million (105 percent of 50 million), which allows time for the content deletion process to reduce the number of objects in the VDS-IS to the configured limit. Adding content resumes only after the number of objects is 50 million or less. The same logic applies to disk usage. The deletion process starts when disk usage reaches 93 percent, adding content stops when disk usage reaches 98 percent, and adding content resumes only after the disk usage percentage reaches 95 percent or less.
Note We recommend that any CDE model that has hard-disk drives (HDDs) (instead of solid-state drives [SDDs]), and is used to stream ABR content, be configured with a maximum of 5 million objects instead of the default value. This is because HDD-based hardware requires more seek time to access content. The software can handle 50 million objects, but the hard-drive access time impacts the ABR streaming performance. ABR content consists of a large number of small files, which results in a lot of overhead.
For long-tail content (Windows Media Streaming, Flash Media Streaming, Movie Streamer, and progressive download), the maximum number of content objects can be configured with the default of 20 million on the HDD-based hardware models. Two of the HDD-based hardware models are the CDE220-2G2 and CDE250-2M0.
If adding content has been stopped because either the content count reached 105 percent of the limit or the disk usage reached 98 percent of capacity, the un-writable flag is set in the share memory and when the protocol engine calls create, FastCAL library looks into the share memory and denies the creation request. The protocol engine performs a bypass or cut-through operation.
The show cdnfs usage command shows the current status of whether the content is able to be cached or not. Following is an example of the output:
If the maximum object count is reached, the following is displayed:
If the disk usage reaches more than 98 percent, the following is displayed:
The Content Manager provides configurable eviction protection for some content. The Content Manager eviction algorithm is triggered when the disk usage reaches 93 percent or when the cached object count reaches the configured maximum object count. The eviction algorithm assigns a priority number to each content object based on an algorithm similar to the greedy-dual-size-frequency (GDSF) algorithm. The priority number is based on the size and usage of the object. Small objects are given preference over large objects; that is, they are less likely to be deleted.
To protect incoming large objects from getting a low priority and being deleted, use the cache content eviction-protection global configure command. The cache content eviction-protection command allows you to set the minimum content size (100 MB, 500 MB, 1 GB, and 4 GB) and the minimum age (1-4 hours for 100 MB size, 1, 4, 8, or 24 hours for all other sizes) of the content object to be protected from deletion. For example, to set the eviction protection for content objects larger than 100 MB that were ingested in the last two hours, you would enter the following command:
If the content object being cached is larger than the configured size, it is inserted into a protection table along with the current time stamp. If the difference between the object’s time stamp and the current time is greater than the configured time duration, the object is removed from the protection table. If the eviction algorithm is triggered, before it selects an object for deletion, it first looks at the protection table, and if the object is found, it is skipped for that iteration. The clear-cache-content command also checks the protection table before deleting an object. The clear-cache-all command does not check the eviction protection table; cache content is just deleted. As for relative cache content, content in the protection table might still be deleted if the relative content that is not protected is deleted. The eviction protection is disabled by default.
If the Content Manager eviction algorithm is not able to find any content to delete, a syslog message is sent to notify the administrator to revisit the configuration. Changing the settings of the cache content eviction-protection command only affect the content that are currently in the protection table and any new content that is added. Any object that is removed from the protection table prior to the configuration change is not brought back into the protection table.
Reloading the SE or entering the no cache content eviction-protection min-size-xx duration-xx command removes all entries in the eviction protection table.
Note Changing the time on the SE affects the Content Manager eviction process. If the time is set forward, content is deleted sooner than expected. If the time is set back, content is protected longer.
The show cache content command displays the eviction protection status and the number of elements in the eviction protection table.
Examples
The following example shows how to configure the cache content:
The show cdnfs usage command shows the current status of whether the content is able to be cached or not. Following is an example of the output:
If the maximum object count is reached, the following is displayed:
If the disk usage reaches more than 95 percent, the following is displayed:
Note When the VDS-IS is started or the cache Content Manager is restarted, it performs a scan of the entire CDNFS. During this period, the deletion starts at 94 percent (not 90 percent) and adding content stops at 95 percent.
Related Commands
|
|
|
capability
To modify the capability configuration, use the capability command in Global configuration mode. To disable capability, use the no form of this command.
capability config profile number [add attrib {capability-url url | user-agent name} | description]
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Related Commands
|
|
|
cd
To change from one directory to another directory, use the cd command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
Use this command to maneuver between directories and for file management. The directory name becomes the default prefix for all relative paths. Relative paths do not begin with a slash (/). Absolute paths begin with a slash (/).
Examples
The following example shows how to use a relative path:
The following example shows how to use an absolute path:
Related Commands
|
|
|
cdn-select
To enable the CDN Selector for third-party service selection, use the cdn-select command in Global configuration mode. To disable the CDN Selector, use the no form of this command.
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
The cdn-select command enables the CDN Selector, which provides a method to do third-party service selection based on parameters like content type and geographic location.
Examples
The following example shows how to enable the CDN Selector:
The following example shows how to disable the CDN Selector:
Related Commands
|
|
|
Redirects requests to different Content Delivery Networks based on the geographic location of the client. |
|
cdnfs
To browse the VDS-IS network file system (CDNFS), use the cdnfs browse command in EXEC configuration mode.
cdnfs { browse | cleanup {info | start force | stop}}
Syntax Description
Defaults
Command Modes
Usage Guidelines
The VDS-IS CDNFS stores the prepositioned VDS-IS network content to be delivered by all supported protocols.
Use the cdnfs browse command to browse the CDNFS directories and files. It does not display cached content for the Web Engine or Flash Media Streaming. It only caches content for Windows Media Streaming and Movie Streamer, and displays prefetched content. To display cached content, use the show cache content command.
Because the CDNFS is empty in this example, the ls command does not show any results. Typically, if the CDNFS contains information, it lists the websites as directories, and file attributes and content could be viewed using these subcommands.
The cdnfs cleanup command, which is used to cleanup unwanted entries in CDNFS, is deprecated in Release 2.6. in the following manner. When an SE is removed from a delivery service, the Content Manager removes all cache content for that delivery service. All prefetched content for that delivery service is removed by the Acquisition and Distribution process. However, if the Acquisition and Distribution process fails because of an SE being offline or for any other reason, then the cdnfs cleanup command is still required to remove the prefetched content.
In certain cases, the Acquirer is not notified by the Centralized Management System (CMS) about deleted channels, and it fails to clear all unified name space (UNS) content. In such cases, the cdnfs cleanup command can be used to clean up all UNS content associated with deleted channels.
Note You can use the cdnfs cleanup start command to clean up the orphan content. The orphan content is content that is not associated with any channel to which the SE is subscribed.
The cdnfs database recover command must be run when the cdnfs_db_corrupt alarm is raised. This alarm is raised when the Total Cached entries is more than Total CDNFS entries in the output for the show cdnfs usage command:
This occurs generally when an internal bookkeeping file is corrupted. With the server in the offloading status, enter the cdnfs database recover command to remove this inconsistency, then reload the server.
Examples
The following example shows the output of the cdnfs cleanup info command:
The following example shows the output for the cdnfs database recover command:
Related Commands
|
|
|
cdsm
To configure the Content Delivery System (CDSM) IP address to be used for the SEs or SRs, or to configure the role and GUI parameters on a CDSM device, use the cdsm command in Global configuration mode. To negate these actions, use the no form of this command.
cdsm {ip { hostname | ip-address | role { primary | standby } | ui port port-num }}
no cdsm {ip | role { primary | standby } | ui port }
Syntax Description
Configures the CDSM role to either primary or standby (available only from the CDSM CLI). |
|
Configures the CDSM GUI port address (available only from the CDSM CLI). |
|
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
You can use the cdsm ui port command to change the CDSM GUI port from the standard number 8443 as follows:
Note The role and ui options are only available on CDSM devices. Changing the CDSM GUI port number automatically restarts the Centralized Management System (CMS) service if this has been enabled.
The cdsm ip command associates the device with the CDSM so that the device can be approved as a part of the network.
After the device is configured with the CDSM IP address, it presents a self-signed security certificate and other essential information, such as its IP address or hostname, disk space allocation, and so forth, to the CDSM.
Configuring Devices Inside a NAT
In an VDS-IS network, there are two methods for a device registered with the CDSM (SEs, SRs, or standby CDSM) to obtain configuration information from the primary CDSM. The primary method is for the device to periodically poll the primary CDSM on port 443 to request a configuration update. You cannot configure this port number. The backup method is when the CDSM pushes configuration updates to a registered device as soon as possible by issuing a notification to the registered device on port 443. This method allows changes to take effect in a timelier manner. You cannot configure this port number even when the backup method is being used. VDS-IS networks do not work reliably if devices registered with the CDSM are unable to poll the CDSM for configuration updates. Similarly, when a receiver SE requests content and content metadata from a forwarder SE, it contacts the forwarder SE on port 443.
All the above methods become complex in the presence of Network Address Translation (NAT) firewalls. When a device (SEs at the edge of the network, SRs, and primary or standby CDSMs) is inside a NAT firewall, those devices that are inside the same NAT use one IP address (the inside local IP address) to access the device and those devices that are outside the NAT use a different IP address (the inside global IP address) to access the device. A centrally managed device advertises only its inside local IP address to the CDSM. All other devices inside the NAT use the inside local IP address to contact the centrally managed device that resides inside the NAT. A device that is not inside the same NAT as the centrally managed device is not able to contact it without special configuration.
If the primary CDSM is inside a NAT, you can allow a device outside the NAT to poll it for getUpdate requests by configuring a static translation (inside global IP address) for the CDSM’s inside local IP address on its NAT, and using this address, rather than the CDSM’s inside local IP address, in the cdsm ip ip-address command when you register the device to the CDSM. If the SE or SR is inside a NAT and the CDSM is outside the NAT, you can allow the SE or SR to poll for getUpdate requests by configuring a static translation (inside global IP address) for the SE or SIR’s inside local address on its NAT and specifying this address in the Use IP Address field under the NAT Configuration heading in the Device Activation window.
Note Static translation establishes a one-to-one mapping between your inside local address and an inside global address. Static translation is useful when a host on the inside must be accessible by a fixed address from the outside.
The VDS-IS software implements a standby CDSM. This process allows you to maintain a copy of the VDS-IS network configuration. If the primary CDSM fails, the standby can be used to replace the primary.
For interoperability, when a standby CDSM is used, it must be at the same software version as the primary CDSM to maintain the full CDSM configuration. Otherwise, the standby CDSM detects this status and does not process any configuration updates that it receives from the primary CDSM until the problem is corrected.
Note We recommend that you upgrade your standby CDSM first and then upgrade your primary CDSM. We also recommend that you create a database backup on your primary CDSM and copy the database backup file to a safe place before you upgrade the software.
Switching a CDSM from Warm Standby to Primary
If your primary CDSM becomes inoperable for some reason, you can manually reconfigure one of your warm standby CDSMs to be the primary CDSM. Configure the new role by using the Global configuration cdsm role primary command as follows:
This command changes the role from standby to primary and restarts the management service to recognize the change.
Note Check the status of recent updates from the primary CDSM. Use the show cms info command in EXEC configuration mode and check the time of the last update. To be current, the update time should be between 1 and 5 minutes old. You are verifying that the standby CDSM has fully replicated the primary CDSM configuration. If the update time is not current, check whether there is a connectivity problem or if the primary CDSM is down. Fix the problem, if necessary, and wait until the configuration has replicated as indicated by the time of the last update. Make sure that both CDSMs have the same Coordinated Universal Time (UTC) configured.
If you switch a warm standby CDSM to primary while your primary CDSM is still online and active, both CDSMs detect each other, automatically shut themselves down, and disable management services. The CDSMs are switched to halted, which is automatically saved in flash memory.
Examples
The following example shows how to configure an IP address and a primary role for a CDSM:
The following example shows how to configure a new GUI port to access the CDSM GUI:
The following example shows how to configure the CDSM as the standby CDSM:
The following example shows how to configure the standby CDSM with the IP address of the primary CDSM by using the cdsm ip ip-address command. This command associates the device with the primary CDSM so that it can be approved as a part of the network.
clear cache
To clear the HTTP object cache use the clear command in EXEC configuration mode.
clear cache [all | content <1-1000000> disk-volume word | flash-media-streaming | url word rate num]
Syntax Description
Clears the Flash Media Streaming edge server cached content and DVR cached content. |
|
The original URL(s) (grouped by wildcard) for content object(s) to delete. |
|
Defaults
Command Modes
Usage Guidelines
The clear cache command removes all cached contents from the currently mounted cache volumes. Objects being read or written are removed when they stop being busy.
The clear cache all command requests the Content Manager to delete all cache contents. Only one clear cache all command can be executed at a time, and the Control-C option is not allowed with this command. During the clear cache all operation, the show cache content and show cdnfs usage outputs display a line about running the clear cache all command, and the progress is displayed in the output of these commands.
The clear cache all command is irreversible, and all cached content is erased. Cisco does not recommend using this command on production systems.
When the clear cache content command is executed, by default, the command evicts 1000MB of content from all disks in the SE. For example, if the SE has 12 disks, then 1000MB/12 = ~83MB content is evicted from each disk. In this case, all content in the SE is 450MB content; therefore, each disk results in a minimum content of 450MB. This causes 450MB * 12 = 5400MB to be evicted. Each disk maintains its own eviction tree, so to avoid this issue, evict each disk separately.
Examples
The following example shows how to clear all cached contents:
Related Commands
|
|
|
|---|---|
clear content
To clear the content of a Uniform Resource Locator (URL), use the clear content command in EXEC configuration mode.
clear content {last-folder-url url | url url}
Syntax Description
Clears all content with a relative diskpath from the given URL without a filename. |
|
Defaults
Command Modes
Usage Guidelines
The clear content url command requests the Fast Content Abstraction Layer (FastCAL) API to delete the content of the specified URL and inform the Content Manager to remove it from its internal data structure.
Examples
The following example shows how to clear the content URL:
1. Verify the URL that is to be deleted from the SE.
2. Clear the URL content from that SE:
3. Verify the content is removed from SE:
This example shows how to delete all the contents matching the last-folder-url:
clear ip
To clear the IP configuration, use the clear ip command in EXEC configuration mode.
clear ip access-list counters [standard_acl-num | extended_acl_num | acl-name ]
clear ip { access-list counters [standard_acl-num | extended_acl_num | acl-name] | bgp {ip address | all} | ospf {neighbor {all | GigabitEthernet slot/port num | PortChannel num} | rspf route [router-id} | traffic} {SR-Mode}
Syntax Description
(Optional) Counters for the specified access list, identified using a numeric identifier. The range is from 1 to 99. |
|
(Optional) Counters for the specified access list, identified using a numeric identifier. The range is from 100 to 199 |
|
(Optional) Counters for the specified access list, identified using an alphanumeric identifier up to 30 characters, beginning with a letter. |
|
Clears the BGP22 neighbors. |
|
Clears the OSPF23 tables. |
|
Slot and port number for the selected interface. The slot range is 1 to 14, and the port is 0. The slot number and port number are separated with a forward slash character (/). |
|
Specifies the Ethernet Channel interface number. The range is from 1 to 4. |
|
(Optional) Specifies the ID of a router for clear routing information. |
|
|
|
Defaults
Command Modes
Usage Guidelines
Use the clear ip bgp command whenever any of the following changes occur:
Examples
The clear ip bgp all command is used to clear all routes in the local routing table. In the following example, the Proximity Engine has only one neighbor, 192.168.86.3:
The following example shows how to clear OSPF of all neighbors:
The following example shows how to clear OSPF of all neighbors in the GigabitEthernet 1/0 interface:
The following example shows how to clear OSPF RSPF information for all routers:
The following example shows how to clear OSPF RSPF information for the router with the ID 172. 20.168.41:
Related Commands
|
|
|
|---|---|
clear ipv6
To clear the IPv6 ACL counters, use the clear ipv6 command in EXEC configuration mode.
clear ipv6 access-list counters [standard_acl-num | extended_acl_num | acl_name ]
Syntax Description
Defaults
Command Modes
Examples
The following example shows how to clear IPv6 ACL counters:
Related Commands
|
|
|
|---|---|
clear isis
To clear IS-IS Routing for an IP, use the clear isis command in EXEC configuration mode.
clear isis {adjacency { all | GigabitEthernet slot/port num | PortChannel num } | ip rspf route [ LSP-ID ]}
Syntax Description
Slot and port number for the selected interface. The slot range is 1 to 14; the port is 0. The slot number and port number are separated with a forward slash character (/). |
|
Specifies the Ethernet Channel interface number. The range is from 1 to 4. |
|
IS-IS Reverse SPF24 routing information. |
|
(Optional) Clears information for LSPs25 ID in the form of xxxx.xxxx.xxxx.xxxx or name. |
|
|
Defaults
If no LSP ID is specified in the clear isis ip rspf route command, IS-IS RSPF information is cleared for all LSP IDs.
Command Modes
Usage Guidelines
The clear isis ip rspf route command is used to clear IS-IS RSPF routing information. IS-IS RSPF routing information is displayed only with the s how isis ip rspf route command when a new proximity request has been received.
Examples
The following is sample output from the show isis adjacency command before and after running the clear isis adjacency command:
The following is a sample from the s how isis ip rspf route command before and after running the show isis ip rspf route command:
Related Commands
|
|
|
|---|---|
Displays the Intermediate IS-IS RSPF route for IS-IS learned routes. |
clear logging
To clear the syslog messages saved in the disk file, use the clear logging command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
The clear logging command removes all current entries from the syslog.txt file, but does not make an archive of the file. It puts a “Syslog cleared” message in the syslog.txt file to indicate that the syslog has been cleared, as shown in the following example:
Examples
The following example shows how to clear the syslogs:
clear service-router
To clear the proximity-based routing proximity cache, use the clear service-router command in EXEC configuration mode.
clear service-router proximity-based-routing proximity-cache
Syntax Description
Defaults
Command Modes
Usage Guidelines
When an SR receives a redirect request from a client network 1 with proximity-based routing enabled, the SR queries the proximity server for the proximity rating of the SEs. The ratings returned from the proximity server are cached, and the default timeout for the cache is 1800 seconds. If there is any network or proximity rating change within this period, the SR does not know as it redirects based on the ratings cached for that network. The clear service-router command is used to force clear cache.
Examples
The following example shows how to clear the Service Router.
Related Commands
|
|
|
|---|---|
clear srp database offline
To clear the SRP database while it is offline, use the clear srp database offline command in privileged EXEC mode.
Syntax Description
Command Defaults
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
The clear srp database offline command is used to clear the SRP database while it is offline.
Note You must turn off SRP before executing this command by entering the no router srp command.
Examples
The following example shows how to clear the SRP database offline:
Related Commands
|
|
|
|---|---|
Displays the descriptor-related information saved in the descriptor database. |
|
clear srp descriptor
To delete either a single descriptor or all descriptors from the service routing layer, use the clear srp descriptor command in privileged EXEC mode.
Syntax Description
The DHT key in hexadecimal format for the descriptor to be deleted. A valid DHT key has 1 to 64 hexadecimal digits. |
Command Defaults
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
The clear srp descriptor command is used to delete a single descriptor in the descriptor database. The delete operation deletes the descriptor at the descriptor root node (which may not necessarily be the local Proximity Engine). Therefore, the descriptor is deleted from the entire network.
Note Deleting a group descriptor also causes the deletion of the group from the network (not just the group’s descriptor).
A valid DHT key must be specified in key to identify the descriptor that is deleted. Keys with less than 64 hexadecimal characters are appended with zeroes.
Deleting a nonexistent descriptor or a descriptor that does not appear in the descriptor database of the Proximity Engine results in an error message stating that the DHT key does not exist.
Examples
The following example shows how use the clear srp descriptor command to delete a descriptor with key 123. After the deletion, the show srp database command is used to verify that the descriptor has been deleted.
1230000000000000000000000000000000000000000000000000000000000000
Entity was DELETED on (47b4269b599afa86) Thu Feb 14 11:31:39 2008
Related Commands
|
|
|
|---|---|
Displays the descriptor-related information saved in the descriptor database. |
|
clear srp neighbor
To remove a neighbor Proximity Engine from the neighbor list of the local Proximity Engine, use the clear srp neighbor command in privileged EXEC mode.
Syntax Description
The DHT key in hexadecimal format for the node to be removed from the neighbor list. A valid DHT key has 1 to 64 hexadecimal digits. |
Command Defaults
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
The clear srp neighbor command is used to delete a single neighbor in the service routing layer from the local Proximity Engine neighbor list. After a small interval, the neighbor list is refreshed and the deleted neighbor may be included in the neighbor list again if it is still a neighbor of the local Proximity Engine in the service routing layer.
A valid DHT key should be specified in key to identify the neighbor. Keys with less than 64 hexadecimal characters are appended with zeroes.
If you attempt to delete a neighbor that does not appear in the neighbor list of the local Proximity Engine, clear srp neighbor displays an error message stating that the neighbor could not be found.
Examples
The following example shows how to use Proximity Engine sn-sj85 with one neighbor sn-sj81 as seen in the following show srp neighbor command output. The neighbor sn-sj81 is also in the leafset of sn-sj85 as can be seen in the show srp leafset output. All commands are issued from Proximity Engine sn-sj85.
The clear srp neighbor command is used to remove sn-sj81 from the neighbor list.
Finally, the show srp neighbor and show srp leafset commands are issued again and show the following:
- Output from show srp neighbor s hows that the neighbor sn-sj81 is in the intransitive state (I). The intransitive state means node sn-sj85 cannot reach node sn-sj81.
- Output from show srp leafset s ho ws that there are no leafset entries (PL or WPL) for the Proximity Engine sn-sj85.
The following example shows how to use the clear srp resource command to delete a resource having resource ID 456 from a descriptor with the key 123. The sh ow srp database command is used to verify that the resource exists before the delete operation and that it has been deleted after the delete operation.
Related Commands
|
|
|
|---|---|
clear srp resource
To delete a resource from a descriptor in the service routing layer, use the clear srp resource command in privileged EXEC mode.
Syntax Description
The DHT key in hexadecimal format for the descriptor from which the resource are deleted. A valid DHT key has 1 to 64 hexadecimal digits. |
Command Defaults
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
The clear srp resource command is used to delete a resource from a descriptor in the service routing layer. Resources can be added to and deleted from any descriptor that exists in the descriptor database.
A valid DHT key must be specified in key to identify the descriptor from which a resource is deleted. Keys with less than 64 hexadecimal characters are appended with zeroes. If you attempt to delete a resource from a nonexistent descriptor, clear srp resource displays an error stating that the DHT key does not exist. Deleting a nonexistent resource has no impact, and no error warning is generated.
Examples
The following example shows how to use clear srp resource to delete a resource, newResource, having resource ID 456 from a descriptor with the key 123. The sh ow srp database command is used to verify that the resource exists before the delete operation and that it has been deleted after the delete operation.
Related Commands
|
|
|
|---|---|
Deletes a single descriptor or all descriptors from the service routing layer |
|
Displays the descriptor-related information saved in the descriptor database. |
clear srp route
To delete a single route entry from the DHT routing table of the local Proximity Engine, use the clear srp route command in privileged EXEC mode.
clear srp route prefix / length
Syntax Description
Command Defaults
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
The clear srp route command deletes a single routing table entry from the local DHT routing table. Similar to other routing protocols, the DHT routing table entries consist of a prefix and length that index the DHT ID of the next-hop Proximity Engine. A valid DHT key prefix (1 to 64 hexadecimal characters) and valid prefix length (multiples of four) must be supplied to identify the neighbor to be deleted.
The clear srp route command provides a manual way to delete routing table entries. After a small interval, the DHT routing table is refreshed and the deleted next-hop Proximity Engine may be included in the DHT routing table again if it is still a viable neighbor.
The clear srp route command can be used to test the presence and persistence of neighbors. Deleting a routing entry that does not exist results in an error message.
Examples
In the following example, Proximity Engine sn-sj85 has four routing table entries. The example shows how to use the clear srp route command to clear the routing table entry that has 8/4 as its prefix / length . The show srp route command is used to verify the deletion of the route.
Related Commands
|
|
|
|---|---|
Displays route information for a Proximity Engine to its neighbor nodes on the same DHT network. |
clear statistics
To clear the statistics, use the clear s tatistics command in EXEC configuration mode.
clear statistics {aaa | access-lists 300 | all | authentication | authsvr {all | delivery-service-id | global} | distribution { all | mcast-data-receiver | mcast-data-sender | mcast-fx-receiver | mcast-fx-sender| metadata-receiver | metadata-sender | unicast-data-receiver | unicast-data-sender } | flash-media-streaming | history | icap | icmp | ip | movie-streamer | radius | rule {action action-type | all | pattern {1-512 | all} | rtsp } | running | snmp | tacacs | tcp | transaction-logs | udp | web-engine [force] | wmt }
clear statistics {aaa | all | authentication | history | http requests | icmp | ip [ospf | proximity { rib | server}] | isis [ GigabitEthernet slot/port num | PortChannel num ] | radius | running | service-registry | service-router | snmp | srp | tacacs | tcp | udp}
Syntax Description
Clears Authentication Server statistics for the delivery service |
|
Clears the distribution statistics for the mcast receiver. Note This command is only available on VDS-IS Release 3.1.1. |
|
Clears the distribution statistics for the mcast sender. Note This command is only available on VDS-IS Release 3.1.1. |
|
Clear statistics for Multicast Fx Receiver. Note The clear mcast-fx-receiver command restarts the receiver server. |
|
Clear statistics for Multicast Fx Sender. Note The clear mcast-fx-sender command restarts the sender server. |
|
Clears the distribution statistics for the metadata receiver. Note This command is only available on VDS-IS Release 3.1.1. |
|
Clears the distribution statistics for the metadata sender. Note This command is only available on VDS-IS Release 3.1.1. |
|
Clears the distribution statistics for the unicast data receiver. Note This command is only available on VDS-IS Release 3.1.1. |
|
Clears the distribution statistics for the unicast data sender. |
|
Clears the ICAP26 statistics. |
|
Slot and port number for the selected interface. The slot range is 0 to 14; the port is 0. The slot number and port number are separated with a forward slash character (/). |
|
Specifies the Ethernet Channel interface number. The range is from 1 to 4. |
|
Clears the statistics of all the rules with the same action. |
|
Specifies one of the following actions: allow |
|
Clears the statistics for the configured RTSP rules (rules configured for RTSP requests from RealMedia players [the RTSP rules] and rules configured for RTSP requests from Windows Media 9 players [the WMT-RTSP rules]). |
|
Resets to zero all statistics counters kept by the local DHT service |
|
|
|
Defaults
Command Modes
Usage Guidelines
The clear statistics command clears all statistical counters from the parameters given. Use this command to monitor fresh statistical data for some or all features without losing cached objects or configurations.
This command is used to reset to zero proximity statistics related to the Proximity Engine components that are used for the proximity function. Use the show statistics ip proximity command to display proximity statistics.
The DHT service keeps several counters, such as the number of requests and responses for DHT lookups. These counters can be displayed using the show statistics srp command.
The clear statistics web-engine and clear statistics all commands clear only normal statistics, not the Web Engine statistics details. To clear all Web Engine statistics, use the clear statistics web-engine force command.
The clear stats authsvr delivery-service-id command only clears the authsvr delivery-service specific statistics. It does not clear global statistics. If you want to clear the global statistics, you must use the clear statistics authsvr all or clear statistics authsvr global commands.
Note The clear statistics web-engine and clear statistics all commands clear only 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.
Examples
The following example shows how to clear proximity statistics with the clear statistics ip proximity command:
The following is sample output from the s how statistics isis command before and after running clear statistics isis command:
The following example shows the use of the clear statistics srp command . The show statistics srp command is used to verify that the SRP counters have been reset to zero:
Related Commands
|
|
|
clear transaction-logs
To clear and archive the working transaction log files, use the clear transaction-log command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
The clear transaction-log command causes the transaction log to be archived immediately to the SE hard disk. This command has the same effect as the transaction-log force archive command.
Examples
The following example shows that the clear transaction-log command forces the working transaction log file to be archived:
clear users
To clear the connections (login) of authenticated users, use the clear users command in EXEC configuration mode.
Syntax Description
Clears the connections of administrative users who have been authenticated through a remote login service. |
Defaults
Command Modes
Usage Guidelines
The clear users administrative command clears the connections for all administrative users who are authenticated through a remote login service, such as TACACS. This command does not affect an administrative user who is authenticated through the local database.
Examples
The following example shows how to clear the connections of the authenticated users:
clear wmt
To clear the WMT streams, use the clear wmt command in EXEC configuration mode.
clear wmt {encoder-alarm-msg msg | stream-id num [stale-stat]}
Syntax Description
Clears the WMT streams that have the specified WMT stream ID. Also stops the SE’s WMT process that is associated with the specified stream ID. |
|
Defaults
Command Modes
Examples
The following example shows how to clear a WMT stream for a stream ID of 22689:
Related Commands
|
|
|
clock (EXEC)
To set or clear clock functions or update the calendar, use the clock command in EXEC configuration mode.
clock {read-calendar | set time day month year | update-calendar }
Syntax Description
Current time in hh:mm:ss format (hh: 00 to 23; mm: 00 to 59; ss: 00 to 59). |
|
Month of the year (January, February, March, April, May, June, July, August, September, October, November, December). |
|
Defaults
Command Modes
Usage Guidelines
If you have an outside source on your network that provides time services (such as a Network Time Protocol [NTP ] server), you do not have to set the system clock manually. Enter the local time when setting the clock. The SE calculates the Coordinated Universal Time (UTC) based on the time zone set by the clock timezone command.
Note We strongly recommend that you configure the SE for the NTP by using the ntp command. See the “ntp” section for more details.
Note If you change the local time on the device, you must change the BIOS clock time as well; otherwise, the timestamps on the error logs are not synchronized. Changing the BIOS clock is required because the kernel does not handle time zones.
Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock. The calendar clock is the same as the hardware clock that runs continuously on the system, even if the system is powered off or rebooted. This clock is separate from the software clock settings that are erased when the system is powered cycled or rebooted.
The set keyword sets the software clock. If the system is synchronized by a valid outside timing mechanism, such as a NTP clock source, you do not have to set the system clock. Use this command if no other time sources are available. The time specified in this command is relative to the configured time zone.
To perform a one-time update of the hardware clock (calendar) from the software clock or to copy the software clock settings to the hardware clock (calendar), use the clock update-calendar command.
Examples
The following example shows how to set the software clock on the SE:
Related Commands
|
|
|
clock (Global configuration)
To set the summer daylight saving time and time zone for display purposes, use the clock command in Global configuration mode. To disable this function, use the no form of this command.
clock {summertime timezone {date startday startmonth startyear starthour endday endmonth endyear offset | recurring {1-4 startweekday startmonth starthour endweekday endmonth endhour offset | first startweekday startmonth starthour endweekday endmonth endhour
offset | last startweekday startmonth starthour endweekday endmonth endhour offset }} | timezone { timezone hoursoffset minutesoffset }}
no clock {summertime timezone {date startday startmonth startyear starthour endday endmonth endyear offset | recurring {1-4 startweekday startmonth starthour endweekday endmonth endhour offset | first startweekday startmonth starthour endweekday endmonth endhour
offset | last startweekday startmonth starthour endweekday endmonth endhour offset }} | timezone { timezone hoursoffset minutesoffset }}
Syntax Description
Minutes offset (see Table B-1 ) from Coordinated Universal Time (UTC) The range is from 0 to 59. |
|
Configures the starting week number. The range is from 1 to 4. |
|
Configures the summer time to recur beginning the first week of the month. |
|
Configures the summer time to recur beginning the last week of the month. |
|
Day of the week to start. The range is from Monday to Friday. |
|
Hour to end in hour:minute (hh:mm) format. The range is from 0 to 23. |
|
Minutes offset (see Table B-1 ) from UTC. The range is from 0 to 59. |
|
Hours offset (see Table B-1 ) from UTC. The range is from –23 to +23. |
|
Minutes offset (see Table B-1 ) from UTC. The range is from 0 to 59. |
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
To set and display the local and UTC current time of day without an NTP server, use the clock timezone command with the clock set command. The clock timezone parameter specifies the difference between UTC and local time, which is set with the clock set command in EXEC configuration mode. The UTC and local time are displayed with the show clock detail command in EXEC configuration mode.
Use the clock timezone offset command to specify a time zone, where timezone is the desired time zone entry from Table B-1 and 0 0 is the offset (ahead or behind) Coordinated Universal Time (UTC) in hours and minutes. UTC was formerly known as Greenwich Mean Time (GMT).
Note The time zone entry is case sensitive and must be specified in the exact notation listed in the time zone table as shown in Appendix B, “Standard Time Zones.” When you use a time zone entry from Table B-1, the system is automatically adjusted for daylight saving time.
Note If you change the local time on the device, you must change the BIOS clock time as well; otherwise, the timestamps on the error logs are not synchronized. Changing the BIOS clock is required because the kernel does not handle time zones.
The offset (ahead or behind) UTC in hours, as displayed in Table B-1 , is in effect during winter time. During summer time or daylight saving time, the offset may be different from the values in the table and are calculated and displayed accordingly by the system clock.
Note An accurate clock and timezone setting is required for the correct operation of the HTTP proxy caches.
Examples
The following example shows how to specify the local time zone as Pacific Standard Time with an offset of 8 hours behind UTC:
The following example shows how to configure a standard time zone on the SE:
The following example negates the time zone setting on the SE:
The following example shows how to configure daylight saving time:
Related Commands
|
|
|
To set the summer daylight saving time and time zone for display purposes. |
|
cms (EXEC)
To configure the Centralized Management System (CMS) embedded database parameters, use the cms command in EXEC configuration mode.
cms { config-sync | database { backup | create | delete | downgrade [ script filename ] | maintenance { full | regular } | restore filename | validate } | deregister [ force ] | recover {identity word }}
Syntax Description
Defaults
Command Modes
Usage Guidelines
The VDS-IS network is a collection of SR, SE, and CDSM nodes. One primary CDSM retains the VDS-IS network settings and provides other VDS-IS network nodes with updates. Communication between nodes occurs over secure channels using the Secure Shell Layer (SSL) protocol, where each node on the VDS-IS network uses a Rivest, Shamir, Adelman (RSA) certificate-key pair to communicate with other nodes.
Use the cms config-sync command to enable registered SRs, SEs, and standby CDSM to contact the primary CDSM immediately for a getUpdate (get configuration poll) request before the default polling interval of 5 minutes. For example, when a node is registered with the primary CDSM and activated, it appears as Pending in the CDSM GUI until it sends a getUpdate request. The cms config-sync command causes the registered node to send a getUpdate request at once, and the status of the node changes as Online.
Use the cms database create command to initialize the CMS database. Before a node can join a VDS-IS network, it must first be registered and then activated. The cms enable command automatically registers the node in the database management tables and enables the CMS. The node sends its attribute information to the CDSM over the SSL protocol and then stores the new node information. The CDSM accepts these node registration requests without admission control and replies with registration confirmation and other pertinent security information required for getting updates. Activate the node using the CDSM GUI.
Once the node is activated, it automatically receives configuration updates and the necessary security RSA certificate-key pair from the CDSM. This security key allows the node to communicate with any other node in the VDS-IS network. The cms deregister command removes the node from the VDS-IS network by deleting registration information and database tables.
Note The cms deregister command cleans up the database automatically. You do not need to use the cms database delete command. If the deregistration fails, the best practice is to resolve any issues that caused the deregistration failure; for example, the Service Engine is the Content Acquirer of a delivery service and cannot be deleted or deactivated. Assign a different SE as the Content Acquirer in each delivery service where this SE is assigned as the Content Acquirer and try the cms deregister command again.
To back up the existing management database for the CDSM, use the cms database backup command. For database backups, specify the following items:
The naming convention for backup files includes the time stamp.
When you use the cms recover identity word command when recovering lost registration information, or replacing a failed node with a new node that has the same registration information, specify the device recovery key that you configured in the Modifying Config Property, System.device.recovery.key window of the CDSM GUI.
Use the lcm command to configure local or central management (LCM) on an VDS-IS network device. The LCM feature allows settings configured using the device CLI or GUI to be stored as part of the VDS-IS network-wide configuration data (enable or disable).
When you enter the cms lcm enable command, the CMS process running on SEs, SRs, and the standby CDSM detects the configuration changes that you made on these devices using CLIs and sends the changes to the primary CDSM.
When you enter the cms lcm disable command, the CMS process running on SEs, SRs, and the standby CDSM does not send the CLI changes to the primary CDSM. Settings configured using the device CLIs are not sent to the primary CDSM.
If LCM is disabled, the settings configured through the CDSM GUI overwrite the settings configured from the SE or SR; however, this rule applies only to those local device settings that have been overwritten by the CDSM when you have configured the local device settings. If you (as the local CLI user) change the local device settings after the particular configuration has been overwritten by the CDSM, the local device configuration is applicable until the CDSM requests a full-device statistics update from the SE or SR (clicking the Force full database update button from the Device Home window of the CDSM GUI triggers a full update). When the CDSM requests a full update from the device, the CDSM settings overwrite the local device settings.
The cms deregister force command should be used only as the last option, because the CDSM does not know about the device being removed. When executing the cms deregister force command, take note of any messages stating that the deregistration failed and make sure to resolve them before reregistering the device with the same CDSM or registering the device to another CDSM. The cms deregister force command forces the deregistration to continue.
Examples
The following example shows how to back up the database management tables:
The following example shows how to validate the database management tables:
In the following example, the CMS deregistration process has problems deregistering the SE, but it proceeds to deregister it from the CMS database when the force option is used:
The following example shows the use of the cms recover identity command when the recovery request matches the SE record, and the CDSM updates the existing record and sends a registration response to the requesting SE:
The following example shows the use of the cms recover identity command when the hostname of the SE does not match the hostname configured in the CDSM GUI:
Related Commands
|
|
|
Displays the CMS protocol, embedded database content, maintenance status, and other information. |
cms (Global configuration)
To schedule maintenance and enable the Centralized Management System (CMS) on a given node, use the cms command in Global configuration mode. To negate these actions, use the no form of this command.
cms { database maintenance { full { enable | schedule weekday at time } | regular { enable | schedule weekday at time }} | enable | rpc timeout {connection 5-1800 | incoming-wait 10-600 | transfer 10-7200 }}
no cms { database maintenance { full { enable | schedule weekday at time } | regular { enable | schedule weekday at time }} | enable | rpc timeout {connection 5-1800 | incoming-wait 10-600 | transfer 10-7200 }}
Syntax Description
Defaults
database maintenance regular : enabled
database maintenance full : enabled
connection: 30 seconds for CDSM; 180 seconds for the SE and the SR
Command Modes
Global configuration (config) mode.
Usage Guidelines
Use the cms database maintenance command to schedule routine, full-maintenance cleaning (vacuuming) or a regular maintenance reindexing of the embedded database. The full maintenance routine runs only when the disk is more than 90 percent full and runs only once a week. Cleaning the tables returns reusable space to the database system.
The cms enable command automatically registers the node in the database management tables and enables the CMS process. The no cms enable command stops only the management services on the device and does not disable a primary sender. You can use the cms deregister command to remove a primary or backup sender SE from the VDS-IS network and to disable communication between two multicast senders.
Examples
The following example shows how to schedule a regular (reindexing) maintenance routine to start every Friday at 11:00 p.m.:
The following example shows how to enable the CMS process on an SE:
Related Commands
configure
To enter Global configuration mode, use the configure command in EXEC configuration mode.
To exit Global configuration mode, use the end or exit commands. In addition, you can press Ctrl-Z to exit from Global configuration mode.
Syntax Description
Defaults
Command Modes
Examples
The following example shows how to enable Global configuration mode:
Related Commands
|
|
|
Exits configuration and privileged EXEC configuration modes. |
|
Exits from interface, Global configuration, or privileged EXEC configuration modes. |
|
contentmgr
To configure the Content Manager, use the contentmgr command in Global configuration mode. To remove the configuration, use the no form of this command.
contentmgr {delivery-service cache-content purge-on-delete num | disk-bucket-fail-threshold num | hitcnt-decay-half-life num | slowscan-time time | slowscan-rate num | transaction-logs-disable | rollback}
no contentmgr {delivery-service cache-content purge-on-delete num | disk-bucket-fail-threshold num | hitcnt-decay-half-life num | slowscan-time time | slowscan-rate num | transaction-logs-disable | rollback}
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
As part of FastCAL, the Content Manager module replaces the Ucache process in VDS-IS 2.6 Release software. The Content Manager keeps track of all the files in CDNFS, and maintains all content popularity information and stores it in a snapshot file.
The contentmgr disk-bucket-fail-threshold command monitors the percentage of disks failed in a particular disk bucket. A minor alarm would be raised if the percentage disk failure crosses the configured threshold value.
A disk bucket is a logical unit in FastCAL module, where all the disks on an SE are distributed equally among each disk bucket. The number of disk buckets can be 1, 3, or 4 depending on the platform.
– This hardware has 3 disk-buckets.
– Each disk-bucket has 4 disks in it (sequentially allocated).
– The allocation of disks is as follows:
disk-bucket00 | disk-bucket01 | disk-bucket02
--------------|-----------------|---------------
– The Number of Disk buckets for each platform type is as as follows:
Use the contentmgr hitcnt-decay-half-life command to configure the time period after which cache hit count is decayed.
The Content Manager transaction logs help identify whether a content is being added, updated, deleted, or evicted. The format for Content Manager transaction logging is as follows:
Use the content-mgr rollback command to downgrade the Service Engine from 4.2.1 image to the previous release image. This command evicts the cached disk content till the maxcached files count below 20,000,000 and max cached directories count below 950,000. Without executing this command before downgrading the Service Engine, all disk cached files will be lost after downgrade reload. This command could take minutes to hours depends on how many cached files are in the disk before downgrade.
Examples
The following example shows how to configure the Content Manager delivery service cache content purge on delete after 10 minutes:
The following example shows how to configure the cache hit count half life to 10 days:
The following example shows how to configure the percentage of disk failures to 20 percent:
The following example shows the disk bucket alarm:
Related Commands
|
|
|
Forces the Content Manager to reset the disk share memory information |
|
content-mgr disk-info force-reset
To force the Content Manager to reset the disk share memory information, use the copy command in EXEC configuration mode.
content-mgr disk-info-force-reset
Syntax Description
Defaults
Command Modes
Examples
The following example shows how to force the Content Manager to reset the disk share memory information:
Related Commands
|
|
|
content-origin
To support multiple origin servers within a content origin, use the content-origin command in Global configuration mode. To remove configured content origin, use the no form of this command.
content-origin request-fqdn domain config-url url [username username password password]
no content-origin request-fqdn domain config-url url [username username password password]
Syntax Description
Configures the request FQDN27. |
|
Domain of the request FQDN. Domain size range should be between 1to 255 characters. |
|
|
|
Defaults
Command Modes
Usage Guidelines
Previously, only one origin server per content origin was allowed and the same origin server could not be shared across multiple content origins. Users had to create delivery services or content origins and different content origin domain names resolving to same IP addresses of the origin server. This created much overhead during deployment. The content-origin command supports multiple origin servers within a content origin and allows users to share single origin servers across multiple delivery service or content origins.
Examples
The following example shows how to create a
Related Commands
|
|
|
copy
To copy the configuration or image data from a source to a destination, use the copy command in EXEC configuration mode.
copy cdnfs disk url sysfs-filename
copy disk {ftp { hostname | ip-address } remotefiledir remotefilename localfilename | startup-config filename }
copy ftp {disk { hostname | ip-address } remotefiledir remotefilename localfilename | install { hostname | ip-address } remotefiledir remotefilename }
copy http install {{ hostname | ip-address } remotefiledir remotefilename } [ port port-num [ proxy { hostname | ip-address } | username username password [ proxy { hostname | ip-address } proxy_portnum ]] | proxy { hostname | ip-address } proxy_portnum | username username password [ proxy { hostname | ip-address } proxy_portnum ]]
copy running-config {disk filename | startup-config }
copy startup-config {disk filename | running-config }
copy system-status disk filename
copy tech-support {disk filename | remotefilename }
Syntax Description
Defaults
Command Modes
Usage Guidelines
The copy cdnfs command in EXEC configuration mode copies data files from of the CDNFS to the sysfs for further processing. For example, you can use the install imagefilename command in EXEC configuration mode to provide the copied files to the command.
The copy disk ftp command copies files from a sysfs partition to an FTP server. The copy disk startup-config command copies a startup configuration file to NVRAM.
The copy ftp disk command copies a file from an FTP server to a sysfs partition.
Use the copy ftp install command to install an image file from an FTP server. Part of the image goes to the disk and part goes to the flash memory.
Use the copy http install command to install an image file from an HTTP server and install it on a local device. It transfers the image from an HTTP server to the SE using HTTP as the transport protocol and installs the software on the device. Part of the image goes to the disk and part goes to the flash memory. You can also use this command to redirect your transfer to a different location or HTTP proxy server, by specifying the proxy hostname | ip-address option. A username and a password have to be authenticated with the remote HTTP server if the server is password protected and requires authentication before the transfer of the software release file to the SE is allowed.
Use the copy running-config command to copy the running system configuration to a sysfs partition or flash memory. The copy running-config startup-config command is equivalent to the write memory command.
The copy startup-config command copies the startup configuration file to a sysfs partition.
The copy system-status command creates a file on a sysfs partition containing hardware and software status information.
The copy tech-support tftp command copies technical support information to a a sysfs partition.
Related Commands
|
|
|
Writes or erases the startup configurations to NVRAM or to a terminal session, or writes the MIB persistence configuration to disk. |
cpfile
To make a copy of a file, use the cpfile command in EXEC configuration mode.
cpfile oldfilename newfilename
Syntax Description
Defaults
Command Modes
Usage Guidelines
Use this command to create a copy of a file. Only sysfs files can be copied.
Examples
The following example shows how to create a copy of a file:
Related Commands
|
|
|
Copies the configuration or image files to and from the CD-ROM, flash memory, disk, or remote hosts. |
|
debug
To monitor and record caching application functions, use the debug command in EXEC configuration mode. To disable these functions, use the no form of this command.
Syntax Description
Specifies the debugger type; see the section for valid values. |
Defaults
Command Modes
Usage Guidelines
We recommend that you use the debug command only at the direction of Cisco TAC because the SE performance is affected when you enter the debug command.
You can use the logging disk priority debug command with the debug command. This configuration causes the debugging messages to be logged in the syslog file, which is available in the /local1 directory by default. You can then download the messages from the SE, copy them to a local disk file (for example, using the copy disk ftp command), and forward the logs to Cisco TAC for further investigation.
By default, system log messages are logged to the console and you need to copy and paste the output to a file. However, this method of obtaining logs is more prone to errors than capturing all messages in the syslog.txt file. When you use system logging to a disk file instead of system logging to a console, there is no immediate feedback that debug logging is occurring, except that the syslog.txt file gets larger (you can track the lines added to the syslog.txt file by entering the type-tail syslog.txt follow command). When you have completed downloading the system logs to a local disk, disable the debugging functions by using the undebug command (see the “undebug” section section for more details), and reset the level of logging disk priority to any other setting that you want (for example, notice priority).
Table 2-2 shows valid values for the debug command options.
| Queries the ACL configuration. Queries the ACL group name or names of groups of which the user is a member. Each group name must be separated by a comma. |
|
Debugs the Autnentication Server. |
|
| Advanced bandwidth controller debug commands. |
|
| Debugs all buffer manager functions. |
|
| (Optional) Sets the debug level to all. |
|
Debugs the Cds Origin Manager. |
|
| Debuts all data server functions. |
|
| Debugs the DFS application API. Debugs the DFS in-memory disk-directory cache management. |
|
| Debugs the distribution components. Debugs Distribution FXD Receiver components. Distribution FXD Sender component debug commands Debugs all distribution components. Debugs all distribution components to error level 1 (show error). Debugs all distribution components to trace level 2 (show error and trace). Debugs the multicast receiver distribution component. Debugs the multicast receiver distribution component to error level 1. Debugs the multicast receiver distribution component to trace level 2. Debugs the metadata receiver distribution component. Debugs the metadata receiver distribution component to error level 1. Debugs the metadata receiver distribution component to trace level 2. Debugs the metadata sender distribution component. Debugs the metadata sender distribution component to error level 1. Debugs the metadata sender distribution component to trace level 2. Debugs the unicast receiver distribution component. Debugs the unicast receiver distribution component to error level 1. Debugs the unicast receiver distribution component to trace level 2. Debugs the unicast sender distribution component. Debugs the unicast sender distribution component to error level 1. Debugs the unicast sender distribution component to trace level 2. |
|
Debugs the HTTPS Configuration Manager. |
|
Debugs Live-routing component. |
|
| Debugs both ICAP client and ICAP daemon processing. |
|
| Debugs Border Gateway Protocol. |
|
| Debugs IS-IS adjacency information. Debugs IS-IS Complete Sequence Number PDU (CSNP) information. Debugs IS-IS DIS election information. Debugs IS-IS ESIS information. Debugs IS-IS event information. Debugs IS-IS hello information. Debugs IS-IS timer LSP information. Debugs IS-IS MPLS information. |
|
Debug commands for memory allocation. Debugging commands for cache application memory allocation. Collects statistics for every distinct allocation call-stack. Alerts if application attempts to release the same memory twice. Checks boundary over and under run scribble. Checks if free chunks are over-written after release. Ensures all allocations are zero-cleared. Allocator use statistical summary. DNS Caching Service memory allocation debugging. Collects statistics for every distinct allocation call-stack. Alerts if application attempts to release the same memory twice. Checks boundary over and under run scribble. Check if free chunks are overwritten after release (when possible) Ensure ALL allocations are zero-cleared General allocator use statistical summary ICAP Service memory allocation debugging. Collects statistics for every distinct allocation call-stack. Alerts if application attempts to release the same memory twice. Checks boundary over and under run scribble. |
|
Debug commands for the Movie Streamer. |
|
Debug commands for the QoS component. Debug commands for the policy service. |
|
Debugs the RBCP (Router Blade Configuration Protocol) functions. |
|
| Displays the remote procedure call (RPC) logs. |
|
Session manager debug commands. Sets the debug level to critical. |
|
Debugs the Service Routing Protocols. Debug SRP frag defragmentation. Debugs the SRP ippc (inter process command). |
|
| Debugs all statistics functions. Debugs the statistics collection. |
|
Debugs the Service Registration Daemon and Descriptor Interpreter. Debugs all SVCREG and Descriptor Interpreter Library (DESCI). Debugs DESCI ippc (inter process comm). Service Registry Daemon (SVCREG) debug commands. |
|
| Debugs the transaction logging. Debugs all transaction logging. Debugs the transaction log archive. |
|
Unified naming service debug commands. (Optional) Sets the debug level to all. |
|
| Debugs the WMT level 1 functionality. For more information, see the “Using WMT Error Logging” section. (Optional) Debugs the request from a specific client IP address to level 1 (show error). (Optional) Debugs the request to a specific server IP address to level 1 (show error). Debugs the WMT level 2 functionality. (Optional) Debugs the request from a specific client IP address to level 2 (show error and trace). (Optional) Debugs the request to a specific server IP address to level 2 (show error and trace). |
|
All modules have debug error as the default level if they support the error keyword; however, when you execute the show debug command, the error does not display.
Some modules have two debugging keywords (error and trace), but you cannot enable both at the same time. See the table above to identify commands with only the error and trace keywords.
Some modules have the all keyword through which you can enable both the error and trace keywords at the same time. This results in debug set to everything. See Table 2-2 to identify commands with the all keyword.
Note When debugging is set to trace level, it uses a lot of the CPU on the SE to handle error log writing. When writing the trace-level error logs reaches 100 percent of the CPU usage, 504 timeout error messages start to occur. Therefore, trace-level error logging should not be enabled in production systems.
Table 2-3 shows the authsvr debugging commands and provides the corresponding log and error display information.
|
|
|
|
|---|---|---|
You can use the debug cdnfs command to monitor the lookup and serving of prepositioned files. If prepositioned files are available in CDNFS but are not served properly, you can use the debug cdnfs command.
Error logs are in the same format and location as syslogs. The WMT log messages are logged to /local1/errorlog/wmt_errorlog.current.
You can configure the SE for WMT error logging by using the debug wmt error command in EXEC configuration mode. This command debugs WMT level 1 functionality.
Logging WMT Client Disconnects
When a WMT client is disconnected abruptly, the reasons for the client disconnect (for example, the request was blocked by the rules, the maximum incoming or outgoing bit-rate limit was reached, the maximum incoming or outgoing bandwidth limit was reached) are logged in VDS-IS software error logs.
The client information includes the client IP address, the server IP address, the requested URL, the client protocol, the version of the client media player, the number of packets that the client received, and the number of packets that the server sent.
Related Commands
|
|
|
debug ip bgp
To display information relating to the BGP process, use the debug ip bgp command in privileged EXEC configuration mode. To disable the display of BGP information, use the undebug form of this command.
debug ip bgp {A.B.C.D. | all | brib | dampening |events | internal | io | keepalives | list | packets | rib | updates}
undebug ip bgp {A.B.C.D. | all | brib | dampening |events | internal | io | keepalives | list | packets | rib | updates}
Syntax Description
Command Default
Debugging of the keepalives is turned on upon the start of the BGP daemon.
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command turns on BGP debugging information. When debug ip bgp is turned on, the performance of the Proximity Engine may be impacted slightly.
Examples
The following example shows sample output displayed before and after running the debug ip bgp all command:
When the undebug ip bgp all command is run, the following output is displayed:
Related Commands
|
|
|
debug ip ospf
To display information related to OSPF process, use the debug ip ospf command in privileged EXEC configuration mode. To disable the display of OSPF information, use the undebug form of this command.
debug ip ospf { adjacency [detail | terse] | all [detail | terse] | database [ detail | terse] | database-timers | events [ detail | terse] | flooding [ detail | terse] | hello | lsa-generation [ detail | terse] | packets | retransmission | spf [ detail | terse] | spf-trigger [detail]}
undebug ip ospf { adjacency [detail | terse] | all [detail | terse] | database [ detail | terse] | database-timers | events [ detail | terse] | flooding [ detail | terse] | hello | lsa-generation [ detail | terse] | packets | retransmission | spf [ detail | terse] | spf-trigger [detail]}
Syntax Description
OSPF LSDB28 changes. |
|
LSAs29 flooding. |
|
|
|
Command Default
Display of information related to the OSPF process is disabled.
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
When debug ip ospf is turned on, the performance of the Proximity Engine may be impacted slightly.
Examples
Add the detail or terse keywords to each of the following commands to enable detailed or major events respectively.
The following example shows how to enable neighbor adjacency events:
The following example shows how to enable all OSPF debugging:
The following example shows how to enable debugging for OSPF LSDB changes:
The following example shows how to enable debugging for OSPF LSDB timers:
The following example shows how to enable debugging for OSPF-related events:
The following example shows how to enable debugging for LSA flooding events:
The following example shows how to enable debugging for hello packets and DR elections:
The following example shows how to enable debugging for local OSPF LSA generation events:
The following example shows how to enable debugging for of OSPF packets:
The following example shows how to enable debugging for OSPF retransmission events:
The following example shows how to enable debugging for SPF calculations:
The following example shows how to enable debugging for SPF triggers:
Related Commands
|
|
|
Displays the state of each debugging option for the OSPF process. |
debug ip proximity
To debug the transport layer of proximity process in an SR, use the debug ip proximity command in privileged EXEC mode. To disable the display of RIB information, use the no form of this command.
debug ip proximity {all | ippc {connection | execute | message | response | send}}
no debug ip proximity {all | ippc {connection | execute | message | response | send}}
Syntax Description
Command Default
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
The debug ip proximity command enables debugging of the transport layer of the proximity process in an SR to troubleshoot problems with proximity request and response.
Examples
The following example shows how to :
Related Commands
|
|
|
Displays the debug options that are enabled for the proximity process. |
debug ip rib
To display RIB information, use the debug ip rib command in privileged EXEC mode. To disable the display of RIB information, use the no form of this command.
debug ip rib [add-route | all | delete-route | detail | mod-route | proximity | rnh | summary]
no debug ip rib [add-route | all | delete-route | detail | mod-route | proximity | rnh | summary]
Syntax Description
Command Default
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command is used to display debug information related to the routing information base (RIB).
Examples
The following example shows how to display the RIB information:
The following example shows how to add routes:
The following example shows how to turn on all IP routing table events:
The following example shows how to remove routes:
The following example shows how to enable detailed debugging for IP routing:
The following example shows how to modify IP routing events:
The following example shows how to turn on proximity debugging information:
The following example shows how to enable recursive next hop events:
The following example shows how to display a one-line summary or URIB I/O events:
Related Commands
|
|
|
Displays the debug options that are enabled for the RIB process. |
debug isis
To display information related to IS-IS process, use the debug isis command in privileged EXEC configuration mode. To disable the display of IS-IS information, use the undebug form of this command.
debug isis [ adjacency | all | csnp | dis | esis | event | hello | lsp | mpls | psnp | route-map | spf | timer ]
undebug isis [ adjacency | all | csnp | dis | esis | event | hello | lsp | mpls | psnp | route-map | spf | timer ]
Syntax Description
Command Default
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
When debug isis is turned on, the performance of the Proximity Engine may be impacted slightly.
Examples
The following example shows how to turn on the debug information for the interaction between IS-IS and the RPM API library:
Related Commands
|
|
|
Displays the debug options that are enabled for the IS-IS process. |
debug srp
To turn on SRP debugging information, use the debug srp command in Privileged EXEC configuration mode. To turn off the debugging information, use the no form of this command.
Syntax Description
Specifies the category of SRP debugging information to turn on. See Table 2-4 for a list of option values. |
Command Default
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command turns on SRP debugging information logging either in the trace file or log file.
The log file for SRP is /local/local1/errorlog/srp_log.current. The option argument to the debug srp command specifies a keyword indicating the category of SRP debugging information logging to turn on. Table 2-4 lists the values that can be specified in the option argument.
Each debugging information message includes a tag that indicates the debugging category. For example, the SRP API debug messages include the tag SRP_DEBUG_API. Table 2-4 lists the tags that are used for each category of debugging information.
To turn off SRP debugging information, use the undebug srp command in privileged EXEC configuration mode.
Examples
The following example shows how to use the debug srp command to turn on SRP host and neighbor debugging information logging:
Related Commands
|
|
|
delfile
To delete a file, use the delfile command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
Examples
The following example shows how to delete a file:
Related Commands
|
|
|
deltree
To remove a directory with its subdirectories and files, use the deltree command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
Use this command to remove a directory and all files within the directory from the SE sysfs file system. Do not remove files or directories required for proper SE functioning.
Examples
The following example shows how to delete a directory from the /local1 directory:
Related Commands
|
|
|
device
To configure the mode of operation on a device as a CDSM, SE or SR, use the device command in Global configuration mode. To reset the mode of operation on a device, use the no form of this command.
device mode {content-delivery-system-manager | service-engine | service-router}
no device mode {content-delivery-system-manager | service-engine | service-router}
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
A CDSM is the content management and device management station of an VDS-IS network that allows you to specify what content is to be distributed, and where the content should be distributed. If an SR is deployed in the VDS-IS network, the SR redirects the client based on redirecting policy. An SE is the device that serves content to the clients. There are typically many SEs deployed in an VDS-IS network, each serving a local set of clients. IP/TV brings movie-quality video over enterprise networks to the desktop of the VDS-IS network user.
Because different device modes require disk space to be used in different ways, disk space must also be configured when the device mode changes from being an SE or SR to CDSM (or the other way around). You must reboot the device before the configuration changes to the device mode take effect.
Disks must be configured before device configuration is changed. Use the disk configure command to configure the disk before reconfiguring the device to the SE or SR mode. Disk configuration changes using the disk configure command takes effect after the next device reboot.
To enable VDS-IS network-related applications and services, use the cms enable command. Use the no form of this command to disable the VDS-IS network.
All VDS-IS devices ship from the factory as SEs. Before configuring network settings for CDSMs and SRs using the CLI, change the device from an SE to the proper device mode.
Configuring the device mode is not a supported option on all hardware models. However, you can configure some hardware models to operate as any one of the four content networking device types. Devices that can be reconfigured using the device mode command are shipped from the factory by default as SEs.
To change the device mode of your SE, you must also configure the disk space allocations, as required by the different device modes, and reboot the device for the new configuration to take effect.
When you change the device mode of an SE to an SR or CDSM, you may need to reconfigure the system file system (sysfs). However, SRs and CDSMs do not require any disk space other than sysfs. When you change the device mode to an SR or a CDSM, disk configuration changes are not required because the device already has some space allotted for sysfs. sysfs disk space is always preconfigured on a factory-fresh VDS-IS network device.
If you are changing the device mode of an SR or a CDSM back to an SE, configure disk space allocations for the caching, pre-positioning (CDNFS) and system use (sysfs) file systems that are used on the SE. You can configure disk space allocations either before or after you change the device mode to an SE.
Examples
The following examples show the configuration from the default mode, SE, to the CDSM, SR, and SE modes:
Related Commands
|
|
|
Displays the configured or current mode of a CDSM, SE, or SR device. |
dir
To view a long list of files in a directory, use the dir command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
Use this command to view a detailed list of files contained within the working directory, including names, sizes, and time created. The equivalent command is lls.
Examples
The following example shows how to view a list of files in a directory:
Related Commands
|
|
|
direct-server-return
To enable a VIP for direct server return, use the direct-server-return command in Global configuration mode. To disable direct server return, use the no form of this command.
direct-server-return vip ip_address
no direct-server-return vip ip_address
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
Direct Server Return (DSR) is a method used by load balancer servers in a load balancing configuration. DSR responds directly to the client, bypassing the load balancer in the response path. Table 2-5 shows the Direct Server Return flow.
|
|
|
|
|
|
|---|---|---|---|---|
Note When issuing the direct-server-return vip command on an SE, the DSR VIP IP address cannot be the same as the Origin Server FQDN (OFQDN).
Examples
The following example shows how to enable direct server return:
Related Commands
|
|
|
disable
To turn off privileged command in EXEC configuration mode, use the disable command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
The disable command places you in the user-level EXEC shell. To turn privileged EXEC configuration mode back on, use the enable command.
Examples
The following example shows how to enter the user-level EXEC configuration mode:
Related Commands
|
|
|
disk (EXEC)
To configure disks and allocate disk space for devices that are using the CDS software, use the disk command in EXEC configuration mode.
disk {erase diskname | mark diskname { bad | good } | policy apply | recover-cdnfs-volumes | recover-system-volumes | repair diskname sector sector_address_in_decimal | unuse diskname}
Syntax Description
Name of the disk to be repaired (disk00, disk01, and so on). |
|
Name of the disk to be stopped for application use (disk01, disk02, and so on). |
Defaults
Command Modes
Usage Guidelines
The disk space in the CDS software is allocated on a per-file system basis, rather than on a per-disk basis.
Note For details on the VDS-IS software disk storage and configuration requirements for SEs, see the Cisco Videoscape Distribution Suite, Internet Streamer 4.2.1 Software Configuration Guide.
The CDNFS amounts are reported by the actual usable amounts of storage for applications. Because of the internal file system overhead of approximately 3 percent, the reported amounts may be smaller than what you configured.
To view disk details, use the show disk details command.
Note The show disk details command shows the amount of disk space that is allocated to system use. This detail is not shown by using the show disk current command.
To show the space allocation in each individual file system type, use the show statistics cdnfs command.
After upgrading, the disk space allocation remains the same as previously configured.
Remapping of Bad Sectors on Disk Drives
The disk erase command in EXEC configuration mode performs a low-level format of the SCSI or SATA disks. This command erases all the content on the disk.
If a disk drive continues to report a failure after you have used the disk erase command, you must replace the disk drive.
Note SCSI and SATA drives can be reformatted.
The disk erase command replaced the disk reformat command. This command erases all the content on the disk. The sequence to erase a disk with the disk erase and then use the disk policy apply commands. If a disk drive continues to report a failure after you have used the disk erase command, you must replace the disk drive.
Be careful when using the
disk erase command because this command causes all content on the specified disk to be deleted.
A new disk is recognized and the RAID is rebuilt when the device is rebooted. After inserting the new disk, enter the disk policy apply command to force the VDS-IS software to detect the new disk and rebuild the RAID.
Note RAID is not supported for generic hardware (UCS servers). These systems have a single un-RAIDed system disk. Any disk replacement requires that the system first be taken off-line.
The disk policy's design, when adding new disks, is to always favor safety. If when a new disk is added, the disk manager detects “degraded” or “bad” system volumes, the new disk is used to repair the system volumes. Thus, the disk manager always strives to have two disks allocated to the system volumes. If when a new disk is added, the system volumes are “normal” or “syncing,” the new disk is added to the cdnfs volume.
Note ● For the CDE220-2S3i,and the CDE220-2S3, because the system disks are internal drives, if the system disk is “bad,” the CDE should be replaced.
- For CDE280, if the system disk disk24 is bad, replace the CDE, and do not use the "disk mark disk24 good". However, if you use the same, the system will erase the boot partition and will not boot up the CDE.
The disk repair command re pairs the bad sector, including the proximal sectors. All data on the drive is lost, but the sectors are repaired and available for data storage again. This command provides equivalent functionality as the repair-disk utility. The disk repair command takes approximately three hours to complete per disk; after the repair disk command completes, reboot the SE to ensure all VDS-IS software services are functioning correctly.
The device should be offline before running the disk repair command. Because this command involves complex steps, we recommend you contact Cisco Technical Support before running this command.
The disk repair command not only repairs the bad sectors, but reformats the entire drive, so all data on the drive is lost. The difference between the disk repair command and the disk erase command is that the disk erase command only re-initializes the file system and does not repair bad sectors.
For CDE280, do not use this command on disk24 because it contains a very important partition.
A minor alarm is set when an LSE is detected. After the sector is repaired with the disk repair command, the alarm is turned off.
Stopping Applications from Using a Disk Drive
The disk unuse command in EXEC configuration mode allows you to stop applications from using a specific disk drive (for example, disk01) without having to reboot the device.
Note When executing the disk unuse command, any applications using the disk will be terminated. Take the devie off-line before executing this command.
Examples
The following example shows how to repair the sector 4660 on disk 02:
Note A system disk cannot be unused in a non-RAID system (generic/ucs). For CDE280, running the disk unuse command on disk24 will cause other commands not to run.
The following examples show usage of the disk unuse command and the resultant actions:
The following example shows how to view disk details:
The following example shows how to display the current disk space configuration:
The following examples show how to view space allocation in each file system type:
The following example shows how to erase all CDNFS volumes and reboot the SE:
Related Commands
|
|
|
disk (Global configuration)
To configure how disk errors should be handled and to define a disk device error-handling threshold, use the disk command in Global configuration mode. To remove the device error-handling options, use the no form of this command.
disk error-handling {bad-sectors-mon-period minutes | reload | threshold {alarm-bad-sectors bad-sectors | alarm-remapped-sectors remapped-sectors | bad-sectors bad-sectors | errors errors} }
no disk error-handling {bad-sectors-mon-period minutes | reload | threshold {alarm-bad-sectors bad-sectors | alarm-remapped-sectors remapped-sectors | bad-sectors bad-sectors | errors errors}}
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
To operate properly, the SE must have critical disk drives. A critical disk drive is the first disk drive that also contains the first sysfs (system file system) partition. It is referred to as disk00. Disk00 is not guaranteed to be the system drive or the 'key' CDNFS drive. For example, the system drives on a 2S6 are internal (disk24 and disk25), and the 'key' CDNSF disk is typically disk00, although it can move to other disks as a result of a missing or bad disk00.
The sysfs partition is used to store log files, including transaction logs, system logs (syslogs), and internal debugging logs. It can also be used to store image files and configuration files on an SE.
Note A critical drive is a disk drive that is either disk00 or a disk drive that contains the first sysfs partition. Smaller single disk drive SEs have only one critical disk drive. Higher-end SEs that have more than one disk drive may have more than one critical disk drive.
When an SE is booted and a critical disk drive is not detected at system startup time, the VDS-IS system on the SE runs at a degraded state. On a generic UCS system the boot partition resides on the system disk (single disk, no RAID). In the event that this disk dies, the system is unbootable. If one of the critical disk drives goes bad at run time, the VDS-IS system applications can malfunction, hang, or crash, or the VDS-IS system can hang or crash. Monitor the critical disk drives on an SE and report any disk drive errors to Cisco TAC.
In a RAIDed system, if a single system disk fails, the system handles the failure seamlessly (apart from any would be CDNFS partitions). If the 'key' CDNFS disk, typically the lowest numbered disk containing CDNFS, fails the system enters an bad state and must be rebooted. In a non-RAID system, if the system disk fails, the system is no longer boots.
With a VDS-IS system, a disk device error is defined as any of the following events:
- Small Computer Systems Interface (SCSI) or Integrated Drive Electronics (IDE) device error is printed by a Linux kernel.
- Disk device access by an application (for example, an open(2), read(2), or write(2) system call) fails with an EIO error code.
- Disk device that existed at startup time is not accessible at run time.
The disk status is recorded in flash (nonvolatile storage). When an error on an SE disk device occurs, a message is written to the system log (syslog) if the sysfs partition is still intact, and an SNMP trap is generated if SNMP is configured on the SE.
In addition to tracking the state of critical disk drives, you can define a disk device error-handling threshold on the SE. If the number of disk device errors reaches the specified threshold, the corresponding disk device is automatically marked as bad.
If the specified threshold is exceeded, the SE either records this event or reboots. If the automatic reload feature is enabled and this threshold is exceeded, then the VDS-IS system automatically reboots the SE. For more information about specifying this threshold, see the “Specifying the Disk Error-Handling Threshold” section.
You can remap bad (but unused) sectors on a SCSI drive and SATA drives using the disk repair command.
Disk Latent Sector Error Handling
Latent Sector Errors (LSE) are when a particular disk sector cannot be read from or written to, or when there is an uncorrectable ECC error. Any data previously stored in the sector is lost. There is also a high probability that sectors in close proximity to the known bad sector have as yet undetected errors, and therefore are included in the repair process.
The syslog file shows the following disk I/O error message and smartd error message when there are disk sector errors:
Apr 28 21:00:26 U11-CDE220-2 kernel: %SE-SYS-4-900000: end_request: I/O error, dev sdd, sector 4660
Apr 28 21:00:26 U11-CDE220-2 kernel: %SE-SYS-3-900000: Buffer I/O error on device sdd, logical block 582
Apr 28 21:04:54 U11-CDE220-2 smartd[7396]: %SE-UNKNOWN-6-899999: Device: /dev/sdd, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 75 to 73
Apr 28 21:04:54 U11-CDE220-2 smartd[7396]: %SE-UNKNOWN-6-899999: Device: /dev/sdd, SMART Usage Attribute: 187 Reported_Uncorrect changed from 99 to 97
Apr 28 21:04:54 U11-CDE220-2 smartd[7396]: %SE-UNKNOWN-2-899999: Device: /dev/sdd, ATA error count increased from 1 to 3
Specifying the Disk Error-Handling Threshold
You can configure a disk error-handling threshold to determine how many disk errors or bad sectors can be detected before the disk drive is automatically marked as bad.
The disk error-handling threshold bad-sectors command determines how many bad sectors can be detected before the disk drive is automatically marked as bad. By default, this threshold is set to 15. To change the default threshold, use the disk error-handling threshold bad-sectors command. Specify 0 if you never want the disk drive to be marked as bad.
If the bad disk drive is a critical disk drive, and the automatic reload feature (disk error-handling reload command) is enabled, then the VDS-IS software marks the disk drive as bad and the SE is automatically reloaded. After the SE is reloaded, a syslog message and an SNMP trap are generated.
The disk error-handling threshold errors command determines how many disk errors can be detected before the disk drive is automatically marked as bad. By default, this threshold is set to 500. To change the default threshold, use the disk error-handling threshold errors command. Specify 0 if you never want the disk drive to be marked as bad.
By default, the automatic reload feature is disabled on an SE. To enable the automatic reload feature, use the disk error-handling reload command. After enabling the automatic reload feature, use the no disk error-handling reload command to disable it.
Examples
The following example shows that five disk drive errors for a particular disk drive (for example, disk00) are allowed before the disk drive is automatically marked as bad:
ServiceEngine(config)# disk error-handling threshold errors 5
Related Commands
|
|
|
Displays currently effective configurations with more details. |
distribution
To reschedule and refresh content redistribution for a specified delivery service ID or name, use the distribution command in EXEC configuration mode.
distribution {failover {delivery-service-id delivery_service_num | delivery-service-name delivery_service_ name } [ force ] | fallback {delivery-service-id delivery_service_num | delivery-service-name delivery_service_ name } | multicast {resend {all [on-demand-only]| delivery-service-id delivery_service_num [object url | on-demand-only]| delivery-service-name delivery_service_ name [object url | on-demand-only] | send-nack-now | stop {all | delivery-service-id delivery_service_num [object url] | delivery-service-name delivery_service_ name [object url]} | primary-ip-fallback {forwarder-id forwarder_num | forwarder-name forwarder_name } | refresh {meta-data delivery-service-id delivery_service_num | object object_url }}
Syntax Description
Triggers the root or forwarder SE to fail over and make this SE the temporary Content Acquirer. |
|
(Optional) Forces a failover regardless of whether the root or forwarder SE is active. |
|
Forces the temporary Content Acquirer to become a receiver SE. |
|
(Optional) Triggers a resend only on demand of content NAK for the delivery service. |
|
Generates a NACK for uncompleted objects and sends it to the multicast sender immediately. |
|
Triggers the downstream receiver SEs to contact a forwarder using the forwarder’s primary IP address. For more information, see the “distribution primary-ip-fallback Command” section. |
|
Specifies the forwarder SE ID that is contacted by the receiver SE. |
|
Specifies the name of the forwarder SE that is contacted by the receiver SE. |
|
Forces the redistribution of content to be refreshed on every SE. |
|
Forces the redistribution of metadata to be refreshed on every SE. |
|
Specifies the delivery service ID to be used in the distribution. |
|
Forces the distribution of objects to be refreshed on every SE. |
|
Specifies the object URL that needs to be refreshed on every SE. |
Defaults
Command Modes
Usage Guidelines
Note This command is only available on VDS-IS Release 3.1.1.
When the Content Acquirer fails, use the distribution failover command in EXEC configuration mode on an SE that is going to be the temporary Content Acquirer to trigger an immediate failover to the temporary Content Acquirer if you do not want to wait for the automatic failover process to occur. When you enter this command, the current SE becomes the temporary Content Acquirer if its forwarder is an inactive Content Acquirer. If the Content Acquirer has not failed, a failover to the temporary Content Acquirer does not occur if you use the distribution failover command in EXEC configuration mode. Use the distribution failover force command to force a failover even if the Content Acquirer is active.
Use the distribution fallback command on an SE that is currently the temporary Content Acquirer to cause it to become a receiver SE.
Use the distribution refresh meta-data {delivery-service-id delivery_service_num } command to request that the metadata receiver repeat a previous request for all the content metadata for the specified delivery service from its forwarder SE. This method allows you to start over if the metadata receiver fails to replicate some metadata properly. The content metadata (machine-readable information that describes the characteristics of the content) must be distributed to a receiver first before the content can be replicated. The content metadata helps to define what content to retrieve, how content is retrieved, how recently the content has been updated, how the content is to be prepositioned (for example, expiration time), and so forth. The metadata is always distributed using unicast. The content can also be replicated using unicast.
Use the distribution refresh object object_url command to reissue a request for unicast distribution of the specified object. This command lets you obtain a new copy of an object if there is a corrupted copy on the SE. After you enter this command, if the distribution is unicast, the unicast receiver reissues the request to its forwarder SE. The old content on the SE is removed and a new copy is replicated.
To identify missing content and trigger a resend of a file, receiver SEs send a negative acknowledgement (NACK) message to the sender SE. NACK messages generated by many receiver SEs could generate more traffic than the sender can handle. You can adjust the average interval between NACKs by configuring a NACK interval multiplier for an individual receiver SE. This value (an integer between 0.1 to 10) adjusts the default average NACK interval (the default is 20 minutes) by the value configured as the interval multiplier. For example, if you set the NACK interval multiplier to 3, the interval between NACKs becomes 20 minutes x 3, or 60 minutes. This adjustment can be made as needed by choosing Devices > Devices > Prepositioning > Distribution in the CDSM GUI.
distribution primary-ip-fallback Command
When downstream receiver SEs at the edge of the network try to access a forwarder SE that is inside a NAT firewall, those receiver SEs that are inside the same NAT use one IP address (called the inside local IP address) to access the forwarder, but other receiver SEs that are outside the NAT need to use a different forwarder’s IP address (called the inside global IP address or NAT address) to access the forwarder. A forwarder SE registers the IP address configured on its primary interface with the CDSM, and the CDSM uses the primary IP address for communication with devices in the VDS-IS network. If the registered primary IP address is the inside local IP address and the forwarder is behind a NAT firewall, a receiver that is not inside the same NAT as the forwarder cannot contact it without special configuration. All other receivers inside the NAT use the inside local IP address to contact the forwarder that resides inside the NAT.
VDS-IS supports NAT for unicast distribution (see the “NAT Firewall” section for more information). When the receiver SE polls its forwarder from an upstream location for the content metadata or content, the receiver first connects to the forwarder using the forwarder’s primary IP address. If it fails and the NAT address of the forwarder has been configured, then the unicast receiver tries to poll the forwarder using the forwarder’s NAT address. If the receiver polls the forwarder successfully using the NAT address, the receiver continues to use the forwarder’s NAT address during the subsequent polling intervals with the same forwarder. The unicast receiver retries to connect to the forwarder using the forwarder’s primary IP address only after one hour. Even if the unicast receiver is able to poll the forwarder using the forwarder’s primary IP address, it would take one hour for the receiver to fall back to the forwarder's primary IP address automatically. You can use the distribution primary-ip-fallback command to enable the receiver that is using the NAT address of the forwarder to fall back to the primary IP address immediately, if you are certain that the forwarder’s primary IP address is working.
NAT enables private IP internetworks that use nonregistered IP addresses to connect to the Internet. NAT is configured on the firewall at the border of a stub domain (referred to as the inside network) and a public network such as the Internet (referred to as the outside network). NAT translates the internal local addresses to globally unique IP addresses before sending packets to the outside network. You can configure NAT to advertise only one address for the entire network to the outside world. This configuration provides additional security, effectively hiding the entire internal network from the world behind that address. NAT has the dual functionality of security and address conservation and is typically implemented in remote access environments.
In the inside network’s domain, hosts have addresses in the one address space. While on the outside, they appear to have addresses in another address space when NAT is configured. The first address space is referred to as the local address space while the second is referred to as the global address space.
Hosts in outside networks can be subject to translation and can have local and global addresses.
NAT uses the following definitions:
- Inside local address—The IP address that is assigned to a host on the inside network. The address is probably not a legitimate IP address assigned by the Network Information Center (NIC) or service provider.
- Inside global address—A legitimate IP address (assigned by the NIC or service provider) that represents one or more inside local IP addresses to the outside world.
- Outside local address—The IP address of an outside host as it appears to the inside network. Not necessarily a legitimate address, it was allocated from an address space routable on the inside.
- Outside global address—The IP address assigned to a host on the outside network by the host’s owner. The address was allocated from a globally routable address or network space.
Use the distribution multicast command to resend or stop metadata transfer. It is important to note that content metadata must be distributed to a receiver before the content itself can be replicated via either multicast or unicast. The meta data is sent to receiver only by unicast. Content metadata specifies what content to distribute, how the content will be distributed, how the content has been updated, how the content is to be pre-positioned. A multicast receiver rejects a multicast sender’s advertisement of a file if the proper content metadata has not arrived yet.
Multicast transmission happens on an SE if the following conditions are met:
- The SE is capable of sending multicast.
- The SE belongs to a multicast-enabled delivery service.
- The SE has an IP multicast address assigned to that delivery service.
Then, the multicast replicator on the SE multicasts out every file of that delivery service to the assigned addresses.
Related Commands
dnslookup
To resolve a host or domain name to an IP address, use the dnslookup command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
The dnslookup command accepts IPv6 address. If an IPv6 address is specified in the dnslookup command, the server replies to a query including the IPv6 address and the IPv6 address displays in the output of the and tcpdump and netstat commands and all logs.
Examples
The following examples show that the dnslookup command is used to resolve the hostname myhost to IP address 172.31.69.11, cisco.com to IP address 192.168.219.25, and an IP address used as a hostname to 10.0.11.0:
domain
To set the domain ID for the SRP, use the domain SRP configuration command. To remove a domain ID, use the no or default form of the command.
[ no | default ] domain [ id ]
Syntax Description
Command Default
Command Modes
SRP configuration (config-srp) mode.
Usage Guidelines
This command is used to set the domain ID for an SRP. All Proximity Engines running SRP routing with the same domain ID form a single network if the nodes are found through a bootstrap node. By changing a Proximity Engine’s domain, the Proximity Engine leaves its current network.
The no and default forms of the command replace current domain ID with the default domain ID, which is 0.
Examples
The following example shows how to configure a domain ID with domain .
The following example illustrates how show srp process command displays the configured domain ID.
Related Commands
|
|
|
enable
To access privileged commands in EXEC configuration modes, use the enable command in EXEC configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
To access privileged EXEC configuration mode from EXEC configuration mode, use the enable command. The disable command takes you from privileged EXEC configuration mode to user EXEC configuration mode.
Examples
The following example shows how to access privileged EXEC configuration mode:
Related Commands
|
|
|
Exits from interface, Global configuration, or privileged EXEC configuration modes. |
enable password
To change the enable password, which is used if aaa authentication enable enable is configured, use the enable password command in Global configuration mode.
Syntax Description
Defaults
Command Modes
Usage Guidelines
The enable password changes the enable password, which is used if aaa authentication enable enable is configured.
Examples
The following example shows how to access privileged EXEC configuration mode:
Related Commands
|
|
|
end
To exit Global configuration mode, use the end command in Global configuration mode.
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
Use the end command to exit Global configuration mode after completing any changes to the running configuration. To save new configurations to NVRAM, use the write command.
In addition, you can press Ctrl-Z to exit Global configuration mode.
Examples
The following example shows how to exit Global configuration mode:
Related Commands
|
|
|
Exits from interface, Global configuration, or privileged EXEC configuration modes. |
eviction-watermark
To configure the content eviction-watermark, use the folowing command in Global configuration mode. To revert to the default value, use the no form of this command.
eviction-watermark high <value> low <value>
no eviction-watermark high <value> low <value>
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
Examples
The following example shows how to configure a content eviction-watermark:
The following example negates the configured content eviction-watermark:
The content eviction-watermark contains the following limitations:
exec-timeout
To configure the length of time that an inactive Telnet or Secure Shell (SSH) session remains open, use the exec-timeout command in Global configuration mode. To revert to the default value, use the no form of this command.
Syntax Description
Timeout in minutes. The range is from 0–44640. The default is 15. |
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
A Telnet or SSH session with the SE can remain open and inactive for the interval of time specified by the exec-timeout command. When the exec-timeout interval elapses, the SE automatically closes the Telnet or SSH session.
Configuring a timeout interval of 0 minutes by entering the exec-timeout 0 command is equivalent to disabling the session-timeout feature.
Examples
The following example shows how to configure a timeout of 100 minutes:
The following example negates the configured timeout of 100 minutes and reverts to the default value of 15 minutes:
Related Commands
|
|
|
exit
To access commands in EXEC configuration mode shell from the global, interface, and debug configuration command shells, use the exit command.
Syntax Description
Defaults
Command Modes
EXEC, Global configuration (config), and interface configuration (config-if) modes.
Usage Guidelines
Use the exit command in any configuration mode to return to EXEC configuration mode. Using this command is equivalent to pressing the Ctrl-Z key or entering the end command.
The exit command issued in the user-level EXEC shell terminates the console or Telnet session. You can also use the exit command to exit other configuration modes that are available from the Global configuration mode for managing specific features (see the commands marked with a footnote in Table 2-1 ).
Examples
The following example shows how to exit the Global configuration mode and return to the privileged-level EXEC configuration mode:
The following example shows how to exit the privileged-level EXEC configuration mode and return to the user-level EXEC configuration mode:
Related Commands
|
|
|
Exits configuration and privileged EXEC configuration modes. |
expert-mode password
To set the customer configurable password, use the expert-mode password command in Global configuration mode.
expert-mode password [encrypted] password
Syntax Description
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
This is a customer configurable password for allowing to enter engineering mode for troubleshooting purposes. The function prompts the user for the current admin password to verify that the user attempting to set the expert-mode password is authorized to do so. If the user is authenticated, the user is prompted twice to enter the new expert-mode password. The new expert-mode password is encrypted prior to being persisted.
Examples
The following example shows how to configure four external NAT IP addresses:
external-ip
To configure up to eight external Network Address Translation (NAT) IP addresses, use the external-ip command in Global configuration mode. To remove the NAT IP addresses, use the no form of this command.
Syntax Description
A maximum of eight external or NAT IP addresses can be configured. |
Defaults
Command Modes
Global configuration (config) mode.
Usage Guidelines
Use this command to configure up to eight Network Address Translation IP addresses to allow the router to translate up to eight internal addresses to registered unique addresses and translate external registered addresses to addresses that are unique to the private network. If the IP address of the RTSP gateway has not been configured on the SE, then the external IP address is configured as the IP address of the RTSP gateway.
In a VDS-IS network, there are two methods for a device registered with the CDSM (SEs, SRs, or the standby CDSM) to obtain configuration information from the primary CDSM. The primary method is for the device to periodically poll the primary CDSM on port 443 to request a configuration update. You cannot configure this port number. The backup method is when the CDSM pushes configuration updates to a registered device as soon as possible by issuing a notification to the registered device on port 443. This method allows changes to take effect in a timelier manner. You cannot configure this port number even when the backup method is being used. VDS-IS networks do not work reliably if devices registered with the CDSM are unable to poll the CDSM for configuration updates. When a receiver SE requests the content and content metadata from a forwarder SE, it contacts the forwarder SE on port 443.
When a device (SEs at the edge of the network, SRs, and primary or standby CDSMs) is inside a NAT firewall, those devices that are inside the same NAT use one IP address (the inside local IP address) to access the device and those devices that are outside the NAT use a different IP address (the NAT IP address or inside global IP address) to access the device. A centrally managed device advertises only its inside local IP address to the CDSM. All other devices inside the NAT use the inside local IP address to contact the centrally managed device that resides inside the NAT. A device that is not inside the same NAT as the centrally managed device cannot contact it without a special configuration.
If the primary CDSM is inside a NAT, you can allow a device outside the NAT to poll it for getUpdate requests by configuring a static translation (NAT IP address or inside global IP address) for the CDSM’s inside local IP address on its NAT, and using this address, rather than the CDSM’s inside local IP address in the cdsm ip ip_address command when you register the device to the CDSM. If an SE or SR is inside a NAT and the CDSM is outside the NAT, you can allow the SE or SR to poll for getUpdate requests by configuring a static translation (NAT IP address or inside global IP address) for the SE or SR’s inside local address on its NAT.
Note Static translation establishes a one-to-one mapping between your inside local address and an inside global address. Static translation is useful when a host on the inside must be accessible by a fixed address from the outside.
Examples
The following example shows how to configure four external NAT IP addresses:
find-pattern
To search for a particular pattern in a file, use the find-pattern command in EXEC configuration mode.
find-pattern {binary filename | case {binary filename | count filename | lineno filename | match filename | nomatch filename | recursive filename } | count filename | lineno filename | match filename | nomatch filename | recursive filename }
Syntax Description
Defaults
Command Modes
Usage Guidelines
Use this command to search for a particular regular expression pattern in a file.
Examples
The following example shows how to search a file recursively for a case-sensitive pattern:
The following example searches a file for a pattern and prints the matching lines:
The following example searches a file for a pattern and prints the number of matching lines:
Related Commands
|
|
|
flash-media-streaming
To enable and configure Flash Media Streaming, use the flash-media-streaming command in Global configuration mode. To disable Flash Media Streaming, use the no form of this command.