Table of Contents
Release Notes for Cisco Video Surveillance Manager , Release 7.11.1
Support for new H.265 Cisco cameras
Operator Password Must Be Set By an Admin
Cisco Connected Safety and Security UCS Platform Series Servers
Upgrading from Previous Cisco VSM Releases
Supported Devices: Generic IP Cameras
Supported Devices: Analog Cameras
Device Models Validated in Cisco VSM as Generic IP Cameras
Clipping Support By Application
Obtaining and Installing Licenses
Understanding the Cisco VSM Software Types
Using the Software Bug Search Tool
Release Notes for Cisco Video Surveillance Manager, Release 7.11.1
Note Always refer to the latest online version of these Release Notes for up to date information.
This document provides important information for Release 7.11.1 of the Cisco Video Surveillance Manager (Cisco VSM).
What’s New In This Release
Cisco VSM Release 7.11.1 is a maintenance release that includes bug fixes and the following new features and enhancements:
- Support for new H.265 Cisco cameras
- Operator Password Must Be Set By an Admin
- Dewarping Improvements
Support for new H.265 Cisco cameras
The following cameras that support the H.265 video codec are now supported.
See Table 8 : Cisco 8000 Series for more information.
Getting Started
Cisco VSM Release 7.11.1 is pre-installed on new servers, can be installed as a virtual machine, or used to upgrade an existing deployment.
Release 7.11.1 is pre-installed in new installations on the Cisco Connected Safety and Security UCS Platform Series servers:
See Cisco Connected Safety and Security UCS Platform Series Servers for more information.
Direct upgrades can be performed from the previous 2 releases. Older releases require alternative methods.
Upgrades can be performed on Cisco VSM virtual machines (VMs) and on Cisco Video Surveillance servers.
An .OVA template file is used to install a new virtual machine (VM) instance of the server.
After an .OVA virtual machine is installed, you can use the Cisco VSM Management Console to perform future upgrades of the system software.
See Cisco Video Surveillance Virtual Machine Deployment and Recovery Guide for UCS Platforms for more information.
See the following for more information:
- Cisco Video Surveillance Manager: Install and Upgrade Guide
- Cisco Connected Safety and Security UCS Platform Series Servers
- Upgrading from Previous Cisco VSM Releases
- Recovery/Factory Image
Cisco Connected Safety and Security UCS Platform Series Servers
Cisco VSM Release 7.11.1 is pre-installed on new installations of the Cisco Connected Safety and Security UCS Platform Series when ordered with the Cisco VSM software installed.
- Cisco CSS UCS Server User Guide — supported features, physical installation and setup instructions
- Release Notes for the Cisco CSS UCS Servers
- After the server appliance is installed, see the Cisco Video Surveillance Manager: Install and Upgrade Guide to perform the initial Cisco VSM setup.
- For additional server hardware documentation, see the Cisco UCS C-Series Server Documentation (Roadmap) .
Upgrading from Previous Cisco VSM Releases
For complete instructions, see the Cisco Video Surveillance Manager: Install and Upgrade Guide .
The following table describes the upgrade methods based on how old your server’s current release is.
Directly upgrade the system software on the server using a
.zip
upgrade file that includes all required software packages.Upgrades can be performed on Cisco VSM virtual machines (VMs) and on Cisco Video Surveillance servers.
Backup and restore to a new server
For example, backup the configuration and data from a release 7.8 server and restore it to a new release 7.11 server.
Cisco Video Surveillance Manager: Install and Upgrade Guide
For older releases, first upgrade to 7.6 then upgrade to latest version.
- Release 7.0 was pre-installed on the Cisco Multiservices Platform (Cisco MSP) servers, including the CPS-MSP-1RU-K9 and CPS-MSP-2RU-K9.
- Release 7.2 to Release 7.7 was pre-installed on the CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9 Cisco CSS UCS series servers.
– The CIVS platform is not supported and cannot be upgraded to VSM 7.7 or later.
– CPS-UCSM4-1RU-K9 / Cisco CPS UCSM4 2RU
Note Virtual Machine (VM) installations can also be upgraded using the Cisco VSM Management Console. Upgrades are supported from release 7.8 or higher on the RHEL6 operating system. See Cisco Video Surveillance Virtual Machine Deployment and Recovery Guide for UCS Platforms for more information.
Recovery/Factory Image
You can also create a bootable USB flash drive that can be used to recover an installation or perform a a factory installation of Cisco VSM Release 7.11.1 on a supported physical server that shipped with Cisco VSM Release 7.11.1 pre-installed. This includes CPS-UCSM4-1RU-K9 and Cisco CPS UCSM4 2RU.
For more information, see Cisco Video Surveillance Manager: Install and Upgrade Guide
Released Versions
Cisco VSM Release 7.11.1 is released with 7.11.1-20i. The component package versions are:
- Cisco_VSBase-7.11.1-012d.i686
- Cisco_SASD-7.11.1-5.noarch
- Cisco_VSMUpgrade-7.11.1-012d.i686
- Cisco_AMQBroker-7.11.1-1.noarch
- Cisco_VSDrivers-7.11.1-012d.i686
- Cisco_DashCast-7.11.1-012d.i686
- Cisco_VSF-7.11.1-8.noarch
- Cisco_Tomcat-7.0.82-3.el6.noarch
- Cisco_MetaDataService-7.11.1-012d.i686
- Cisco_VSTools-7.11.1-012d.i686
- Cisco_GeoServer-7.8.0-1.noarch
- Cisco_VSRecorder-7.11.1-012d.i686
- Cisco_MPClient-7.11.1-67.noarch
- Cisco_CDAF-7.11.1-8.noarch
- Cisco_VSMS-7.11.1-012d.i686
Supported Devices
The following sections provide information about the devices that this version of Cisco VSM supports:
- Supported Devices: Cisco
- Supported Devices: Arecont
- Supported Devices: Axis
- Supported Devices: IQinVision
- Supported Devices: Mobotix
- Supported Devices: Panasonic
- Supported Devices: Pelco
- Supported Devices: Sony
- Supported Devices: Vivotek
- Supported Devices: Generic IP Cameras
- Supported Devices: Analog Cameras
- Device Models Validated in Cisco VSM as Generic IP Cameras
Supported Devices: Cisco
Table 3 through Table 9 provide information about Cisco devices supported in this release:
- Cisco 2400/2500, 2600, 2800, and 2900 Series Basic functionality such as streaming and recording is supported. Any features that require a firmware upgrade are not supported.
- Cisco 3000 Series
- Cisco 4000 Series and 5000 Series Basic functionality such as streaming and recording is supported. Any features that require a firmware upgrade are not supported.
- Cisco 6000 Series
- Cisco 7000 Series
- Cisco 8000 Series
- Cisco CIVS-SENC-4P and CIVS-SENC-8P
Table 3 Cisco 2400/2500, 2600, 2800, and 2900 Series
Basic functionality such as streaming and recording is supported. Any features that require a firmware upgrade are not supported. FW Version for Release 7.11.1 Compatibility1
FW Version for Release 7.11.1 Compatibility2
Table 5 Cisco 4000 Series and 5000 Series
Basic functionality such as streaming and recording is supported. Any features that require a firmware upgrade are not supported. FW Version for Release 7.11.1 Compatibility3
FW Version for Release 7.11.1 Compatibility4
FW Version for Release 7.11.1 Compatibility5
FW Version for Release 7.11.1 Compatibility9Additional Notes on Cisco Devices
- Cisco 4500 and 4500E support video analytics.
- Redundancy is supported for all Cisco devices some exceptions for the 2400, 2500, 2900 and 5000 series. The 2400, 2500, 2900 and 5000 series do not support sending events to the redundant server such motion detection and contact closure events.
- Cisco 5000 series does not support motion detection at video bit-rates above 4,000 (4 Mbps). The “H” video preset in Templates has been chosen to not exceed this, so motion detection will work.
- The Cisco 5000 and 2900 camera series do not allow changes to the authentication settings (username/password) or networking settings (DHCP/Static, DNS, etc.) through Cisco VSM. These values can only be changed using the camera web interfaces.
- Focus, Auto Focus and Zoom support are not available for Cisco 6000P, 3421V, 3520, 3530, 3535, and 3050 camera models.
- When Cisco VSM manages a Cisco 6930, 2830, or 2835 camera, it automatically enables the HTTP protocol on the camera and uses this protocol to send PTZ commands to the camera. Other configuration commands continue to use the HTTPS protocol.
- The Cisco 2830, 2835, 3000 series, 6000 series and 7030 cameras now support MJPEG primary streams.
- Cisco 3421V and 6050 cameras do not support Contact Closure, Cisco 7030 camera supports 3 input ports. All other Cisco 3000, 6000, 8000 series cameras support 1 input port.
- In PTZ Tour Configuration, the configured transition time configured includes the time that it takes the camera to move from the one preset position to the next preset position in addition to the time that the camera is expected to stay in the preset position. If the transition time is configured to a value that is less than the time that it takes the camera to move from one preset position to the next, the camera moves between the first and second presets positions only, instead of touring between all preset positions that are configured in the tour.
- The minimum firmware version required to support camera applications is 2.5.0-10.
- The minimum firmware version required to support connected edge storage is 2.0.
Supported Devices: Arecont
Table 10 provides information about Arecont devices that this Cisco VSM release supports.
Additional Notes on Arecont Devices
- AV20185, AV20365, AV12186, AV8365 and AV8185 are 4-channel IP cameras. In order to support multiple video channels from a single device, Cisco VSM 7 models these devices as “Encoders”.
- Arecont devices have not yet been qualified to support redundancy in Cisco VSM 7.
- Secondary streams are not supported in H, M, L template settings for Arecont Devices. However secondary stream can be configured using Custom templates.
- Arecont cameras divide the Maximum FPS the camera supports by the number of streams. This could result in lower FPS when both primary and secondary streams are configured for these cameras.
- Arecont AV10XX5, AV5115, AV2115 support VBR and multicast streaming.
- There is a restriction with motion detection for Arecont multi-sensor cameras. False motion events are generated if both half and full resolution size images are requested simultaneously using Cisco VSM or Arecont Camera Web Interface or a third party Media Player.
Supported Devices: Axis
Table 11 , Table 12 , and Table 13 provide information about Axis devices supported in this release.
Version10
Version11Table 13 provides information about additional Axis devices that this Cisco VSM release supports.
Additional Notes on Axis Devices
- Axis P3301 IP camera and Q7401, Q7404, and Q7406 encoders have been qualified to support redundancy in Cisco VSM 7.0.1.
- Axis 233D supports contact closure configuration and events.
- Support for 0.1fps MJPEG stream for all supported Axis models.
The following table documents the various Field-Of-Views supported for the Axis M3007 panoramic cameras and support for PTZ and Motion Detection for these Field-Of-Views.
The Axis M3007 camera allows the user to configure various mounting options directly in the camera web interface that affects the possible values for Field-Of-Views that can be configured on the camera. The table below provides this mapping:
Supported Devices: IQinVision
Table 16 provides information about IQinVision devices that this Cisco VSM release supports.
Supported Devices: Mobotix
Table 17 provides information about Mobotix devices that this Cisco VSM release supports.
Supported Devices: Panasonic
Table 18 provides information about Panasonic devices that this Cisco VSM release supports.
Additional Notes on Panasonic Devices
- Panasonic devices have not yet been qualified to support redundancy in Cisco VSM 7.
- Only same field of views can be configured on primary and secondary streams on Panasonic cameras SW458/SF438.
- The following table documents the various Field-Of-Views supported for the Panasonic SF 458 and SF 438 panoramic cameras and support for PTZ and Motion Detection for these Field-Of-Views.
Supported Devices: Pelco
Table 20 provides information about Pelco devices that this release supports.
Additional Notes on Pelco Devices
- Pelco devices have not yet been qualified to support Redundancy in Cisco VSM 7.
- Audio volume controls are not supported for NET540XT
- For Pelco NET540xT PTZ to work, the analog camera should be chosen as Pelco Analog Camera (pelco_sarix) in Operations Manager and not as Pelco D.
- The user needs to directly configure the Serial protocol on the Pelco NET540XT encoder outside of Cisco VSM.
- The Pelco Spectra IV TXB-N (H.264 capable model) run Pelco Sarix firmware and can be supported in Cisco VSM as a Pelco Sarix Generic IP camera (additional details in the Generic IP camera section).
Supported Devices: Sony
Table 21 provides information about Sony devices that this release supports.
Additional Notes on Sony Devices
- Sony devices have not yet been qualified to support redundancy in Cisco VSM 7.
- These Sony devices do not support motion detection with the H.264 media type.
- The Sony SNC-RX5x0 cameras stop streaming video when the Object Detection window is opened in the camera’s web interface.
- For Sony HM662 Panoramic camera, only the 360 degree view is supported. De-warped views are not supported.
Supported Devices: Vivotek
Table 22 provides information about Vivotek devices that this release supports.
Supported Devices: Generic IP Cameras
Cisco VSM Release 7.11.1 provides the following device drivers to support IP cameras from various vendors. The functionality they support will depend on the particular device that they are used with. They are intended to provide a quick and easy way to support devices for which there isn’t yet a specific driver available for Cisco VSM. Since these drivers may not be tested with a specific device, some issues may be encountered. When using these drivers with a device, failover and redundancy are not supported.
Note The vendor specific generic driver should always be used before a non-vendor specific driver such as ONVIF.
Motion Detection14
- Supports only IP Cameras, no support for Encoders
- No contact closure support
- Multicast streaming is supported only for the primary stream
- Multicast port must be an even number within the range 16000:19999
- Audio Multicast issues are observed on most of the ONVIF cameras. Hence do not enable audio when multicast is enabled for video.
- Capture Mode on the camera cannot be changed using ONVIF APIs. So, it is assumed that the camera is in the desired capture mode before adding it to VSOM using ONVIF
- This ONVIF driver has been tested with a limited number of camera models from Axis, Sony, Panasonic, Bosch, Pelco, Samsung, J2000IP, Hikvision and Cohu. We have found that these cameras have some variations in how they have implemented the ONVIF specification. Hence there may be compatibility issues when using this ONVIF driver with a particular device that is ONVIF compliant.
- Some of the known caveats are listed below:
- ONVIF user account—Some Axis cameras require a special ONVIF user account, which can be created on the camera's web interface before adding an AXIS ONVIF camera to the VSOM. This page is at Setup --> System Options --> Security --> ONVIF --> Add
- Camera and VSMS (Media Server) Time Synchronization—ONVIF camera and VSMS server to which ONVIF camera is being added should have their time synchronized ideally using NTP.
- Codec Change through VSOM—Hikvision camera requires a reboot after the codec is changed from VSOM.
- The Minimum Firmware Version of Hikvision cameras supported is V5.3.0, to be added as ONVIF camera in Cisco VSM.
- Megapixel Mode setting on the camera SND-7080
- To support the resolutions (1600*1200) and (2048*1536), change the Megapixel Mode to 3-Megapixel in the following page on the camera browser: Settings -> Audio & Video -> video profile -> Megapixel mode
- Enable Authentication on the camera before adding it to VSOM In the camera browser, go to Camera Setup -> Configuration -> User Settings. Select User and enable “Require Password” field.
- Media Transport Type— Only UDP is supported. Streaming fails if TCP is selected.
- Unsupported Resolutions —Streaming fails for the resolutions 176*144, 176*120, 160*120
- Codec Change through VSOM— Switching from H264 to JPEG or vice-versa requires a camera reboot. And camera needs to be deleted and added in VSOM after camera is up.
- Support for Audio— Camera does not support ONVIF Audio
- Frame rate— Only Framerate 30 is supported
- Dual Streaming— Secondary configuration overwrites the primary configuration. So, dual streaming is not supported on Bosch cameras using ONVIF.
- Capture Mode Setting— If the camera is added in VSOM using Multicast, changing the capture mode on the camera browser manually causes the streaming to fail. After this, only the unicast streaming works
- User Authentication— User Authentication should be enabled in the camera browser as follows - Setup -> User mng -> User auth. Choose ON for User auth.
- Media Transport Type— Only UDP is supported. Streaming fails if TCP is selected
- Support for Audio— Camera does not support ONVIF Audio
- Set Configuration Issues — Camera returns success even if one or more of the parameters are not valid for that camera/video stream. ONVIF profile gets updated with values but Camera still uses the previous correct value. Recommend to configure only the values as allowed in the camera browser.
- Support for Password change on the camera— Camera does not support password change for the administrator users using ONVIF API.
Supported Devices: Analog Cameras
This Cisco VSM release provides support for the following analog cameras.
Device Models Validated in Cisco VSM as Generic IP Cameras
The camera models listed in Table 25 have been tested with VSM Release 7.11.1 as generic IP cameras.
Clipping Support By Application
You can create and view video clips using the following Cisco VSM applications:
Note When converting a virtual clip to an MP4 file, only the entire duration of the virtual clip can be saved, not a segment.
Obtaining and Installing Licenses
To install a license, purchase the license and obtain the license file, then upload the file to the Operations Manager.
Table 27 lists the part numbers for the Cisco VSM licenses. Multiple camera and VSMS licenses can be included in a single license file. For example, a single license file might include support for 25 additional cameras and two additional VSMS devices.
- A license for 10,000 Cisco cameras is included by default (you do not need to purchase and install an additional license for Cisco cameras).
- You can add 1 Media Server and 10 non-Cisco cameras without a license for initial setup purposes only. This feature is removed when you add any permanent license.
Step 1 Purchase additional licenses:
a. Determine the part number for the license you want to purchase (see Table 27 ).
b. Purchase the license by contacting your Cisco sales representative or any Cisco reseller. For more information, visit http://www.cisco.com/en/US/ordering/index.shtml .
c. When the purchase is complete, you are issued a Product Authorization Key (PAK) in paper form, or in an e-mail message.
Step 2 Obtain the license file:
a. Locate the Product Authorization Key (PAK) that was created with the purchase.
b. In a web browser, open the Cisco Product License Registration web page.
http://www.cisco.com/go/license/
c. Follow the on-screen instructions to complete the form and enter the Product Authorization Key (PAK). When you are done, a license file with the extension
.lic
is sent to your e-mail address.d. Transfer the file to the drive of the PC used for the configuration.
Step 3 Install the license file in Cisco VSM:
a. Log in to the Operations Manager.
b. Select System Settings > Software Licensing .
c. Click Add and select the license file located on your local drive.
d. Click Save to install the file and activate the additional capacity.
The additional capacity is available immediately. You do not need to restart the server or take additional steps.
See the Cisco Video Surveillance Operations Manager User Guide for more information.
Understanding the Cisco VSM Software Types
Table 28 describes the different types of software and firmware that are installed on servers, cameras, and encoders.
System software denotes the Cisco VSM software, including Media Server, Operations Manager, Cisco VSM Management Console, Safety and Security Desktop and Multipane clients. All servers running the Operations Manager and associated Media Server services must run the same software version.
Use the Operations Manager to update the System Software on all servers (such as Media Servers) associated with the Operations Manager. See the Cisco Video Surveillance Operations Manager User Guide for instructions.
- The Operations Manager and all associated servers must run the same system software version.
- To update a Federator server, log in to the Federator server Management Console. See the Cisco Video Surveillance Operations Manager User Guide for instructions.
- To repair or restore the Cisco VSM system software, see the Cisco Video Surveillance Manager: Install and Upgrade Guide for your hardware platform. For VM installations, see the Cisco Video Surveillance Virtual Machine Deployment and Recovery Guide for UCS Platforms ).
OVF template files are used to install the system software as a virtual machine (VM) on a supported Cisco Unified Computing System (UCS) platform.
- OVA template files are downloaded from the Cisco website.
- The file format is
.ova.
For example:Cisco_VSM-7.11-331d_ucs-bc.ova
- See the Cisco Video Surveillance Virtual Machine Deployment and Recovery Guide for UCS Platforms for instructions to install the .ova image and perform the initial VM setup.
- After the VM setup is complete, use the Management Console to complete the configuration.
Use the USB Recovery Disk image to create a Cisco VSM 7 Recovery Flash Drive (for example, on a USB stick). The recovery disk can be used do the following:
- Repair: reinstalls the Operating System files and partitions without erasing video files stored on the server. You must backup the Cisco VSM database before using the recovery image, and then restore the database after the recovery process is complete. This action also preserves the RAID configuration.
- Factory Restore: Restores the server to its factory default settings, reinstalls the operating system, and clears and reconfigures the RAID. This action deletes all data, configurations, software and video files from the appliance, and then reinstalls the operating system and Cisco VSM software. Perform this procedure only if necessary.
See the Cisco CSS UCS Server User Guide for more information.
Device firmware is provided by the device manufacturer. The firmware for Cisco devices can be upgraded using Operations Manager. Firmware for other manufacturers is upgraded using a direct connection.
See the “Upgrading Camera and Encoder Driver Firmware” section of the Cisco Video Surveillance Operations Manager User Guide for instructions to upgrade Cisco device firmware, or refer to the device documentation.
Device driver packs are the software packages used by Media Servers and the Operations Manager to interoperate with video devices, such as cameras. Driver packs are included with the Cisco VSM software, or may be added to a server at a later time to add support for new devices or features.
- Install new driver packs to add support for additional devices.
- Upgrade existing driver packs to enable support for new features.
- When updating or installing a driver pack, you first install the file on the Operations Manager, and then on the Media Servers that support the cameras or encoders. You can install the new version on all Media Servers, or only the Media Server(s) that support the affected devices. If the driver pack version is different on the Media Servers in your deployment, a driver pack mismatch error can occur.
– A warning message is informational only and the cameras and encoders can be configured normally.
– A critical message appears if the driver pack mismatch will impact the functionality or compatibility between the Operations Manager, Media Servers, and the video device. The upgrade is not allowed. Camera and encoder templates cannot be revised until the same driver pack version is installed on all Media Servers.
Note We strongly recommend upgrading driver packs using the Operations Manager interface (see the “Driver Pack Management” section of the Cisco Video Surveillance Operations Manager User Guide). This allows you to upgrade multiple servers at once.
Language packs can be added to display the Cisco VSM user interfaces in non-English languages.
Language packs are added using the Operations Manager (release 7.6 and higher). See the Cisco Video Surveillance Operations Manager User Guide for instructions.
Obtaining Cisco VSM Software
Complete the following procedure to obtain software and other information for the Cisco VSM products and components:
Step 1 Go to the Cisco Video Surveillance Manager product page .
Step 2 Click Download Software .
Step 3 Select a product category. For example:
- Video Surveillance Device Driver
- Video Surveillance Manager Stand-alone Tools
- Video Surveillance Media Server Software (including system software)
Step 4 Select the release for your server, device, or deployment (Figure 1).
Step 5 Click Download or Add to Cart and follow the onscreen instructions.
Figure 1 Download Software Page
You can also navigate the Cisco Physical Security product pages to download software updates and other information:
Step 1 Go to the following URL.
http://www.cisco.com/go/physicalsecurity
Step 2 Click View All Physical Security Products.
Step 3 Click IP Video Surveillance.
Step 4 Click Cisco Video Surveillance Manager.
Step 5 Click Download Software for this Product .
Step 6 Click a Software Type and follow the onscreen instructions.
For example: Video Surveillance Media Server Software (Figure 1).
Step 7 Select the release for your server, device, or deployment.
Step 8 Click Download or Add to Cart and follow the onscreen instructions.
Caveats
This section includes the following topics:
Using the Software Bug Search Tool
You can use the Bug Search Tool to find information about most caveats for Cisco VSM releases, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.
To access Bug Search Tool, you need the following items:
To use the Software Bug Search Tool, follow these steps:
Step 1 To access the Bug Search Tool, go to https://tools.cisco.com/bugsearch/
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the Search for field.
Step 4 For more information, go to the Bug Search interactive tour .
Open Caveats
Table 29 lists caveats that are open in this release.
Resolved Caveats
Table 30 lists caveats that are resolved in this release.
Related Documentation
See the following locations for the most current information and documentation:
Cisco Video Surveillance 7 Documentation Roadmap
Descriptions and links to Cisco Video Surveillance documentation, server and storage platform documentation, and other related documentation.
http://www.cisco.com/go/physicalsecurity/vsm/roadmap
Cisco Physical Security Product Information:
www.cisco.com/go/physicalsecurity/
Cisco Video Surveillance Manager Documentation Website
www.cisco.com/go/physicalsecurity/vsm/docs
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.