Release Notes for Cisco UCS Software, Release 2.0
This document describes system requirements, new features, catalog and bundle images information, resolved caveats, known caveats and workarounds for Cisco UCS Manager Release 2.0(1m), Release 2.0(1q), Release 2.0(1s), Release 2.0(1t), Release 2.0(1w), Release 2.0(1x), 2.0(2m), 2.0(2q), 2.0(2r), 2.0(3a), 2.0(3b), 2.0(3c), 2.0(4a), 2.0(4b), 2.0(4d), 2.0(5a), 2.0(5b), 2.0(5c), 2.0(5d), 2.0(5e), 2.0(5f), 2.0(5g). This document also includes the following:
- Current information that became available after the technical documentation was published
- Related firmware and BIOS versions on blade and rack servers and other Cisco Unified Computing System (UCS) components associated with the releases
.
Make sure to review other available documentation on Cisco.com to obtain current information on Cisco UCS Manager.
Contents
This document includes the following sections:
- Revision History
- Introduction
- Internal Dependencies
- Capability Catalog
- New Hardware Features in Release 2.0
- New Software Features in Release 2.0
- Resolved Caveats
- Open Caveats
- Known Limitations and Behaviors
- Open Caveats from Prior Releases
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
Revision History
shows the revision history for this document.
Created release notes for Release 2.0(1m). 1
Added ‘The following caveats are common across Release 2.0’ section under Open Caveats.
Removed CSCua02797 from Resolved Caveats; applies only to VIC Driver release notes.
Updated release notes for Catalog Release 2.0.5l.T and removed a PID for ucs-catalog.2.0.1m.T.bin.
Removed a PID from catalog Release 2.0.5l.T that is already listed for a previous release.
1.This release was removed from the download area due to CSCts96949 and CSCts86890. See the software deferral notice.
1.This release was removed from the download area due to CSCts96949 and CSCts86890. See the software deferral notice.
Introduction
Cisco UCS™ Manager provides unified, embedded management of all software and hardware components of the Cisco Unified Computing System™ (Cisco UCS) across multiple chassis, rack-mount servers, and thousands of virtual machines. Cisco UCS Manager manages Cisco UCS as a single entity through an intuitive GUI, a command-line interface (CLI), or an XML API for comprehensive access to all Cisco UCS Manager functions.
System Requirements
To install Cisco UCS Manager your computer must meet or exceed the following system requirements:
- The Cisco UCS Manager GUI is a Java-based application. Starting with Release 2.0(3a), Cisco UCS Manager supports both Sun JRE 1.6 and JRE 1.7. Versions earlier than Cisco UCS Manager Release 2.0(3a) require Sun JRE 1.6. (Sun JRE must be 32-bit version due to the lack of 64-bit native libraries for the KVM/VMedia; the 32-bit JRE can be executed in both Win32 and Win64, as well as Linux 32 and 64).
- Cisco UCS Manager uses web start and supports the following web browsers:
–
Microsoft Internet Explorer 6.0 or higher
–
Mozilla Firefox 3.0 or higher
Adobe Flash Player 10 or higher is required for some features
Internal Dependencies
shows interdependencies between the hardware and versions of Cisco UCS Manager. Server FRU items such as DIMMs are dependent on their server type, and chassis items such as fans and power supplies work with all versions of Cisco UCS Manager.
![]()
Caution You cannot mix component software versions (for example, you cannot have a B200 using the 1.0(1) BIOS with a UCS M81KR adapter running 1.0(2) firmware managed by Cisco UCS Manager 1.3(1)). Compare the minimum software version for all your components and use at least the latest of all the versions, or use the most current version of software for all components. Mixing M1 and M2 hardware versions is not an issue if they are running software at a version matching the other system components.
C220 M32
UCS M71KR-Q
UCS CNA M72KR-E
UCSB-MLOM-PT-01
Cisco Nexus 22484
N10-E0080
SFP-H10GB-CU5M
SFP-H10GB-ACU10M
SFP-H10GB-ACU10M=
DS-SFP-FC8G-LW
DS-SFP-FC4G-LW
GLC-LH-SM
2.See the Software Advisory for the minimum firmware level required on the Cisco UCS C220 M3 and Cisco UCS C240 M3.
2.See the Software Advisory for the minimum firmware level required on the Cisco UCS C220 M3 and Cisco UCS C240 M3.
3.N20-AI0002, the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter, is not supported on the B440 server but is still available for other models. We suggest you use the Cisco UCS CNA M61KR-I Intel Converged Network Adapter in place of the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter.
3.N20-AI0002, the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter, is not supported on the B440 server but is still available for other models. We suggest you use the Cisco UCS CNA M61KR-I Intel Converged Network Adapter in place of the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter.
4.The C-series integration using the Cisco Nexus 2248 Fabric Extender is no longer supported as of Release 2.0(2). See the UCS C-Series hardware documentation for details.
4.The C-series integration using the Cisco Nexus 2248 Fabric Extender is no longer supported as of Release 2.0(2). See the UCS C-Series hardware documentation for details.
Capability Catalog
for details on the mapping of versions to bundles.
New Hardware Features in Release 2.0
Release 2.0(5b) adds support for the following:
This patch release provides support for UCS B200 M3 blade server configurations with a single CPU, in addition to the previously supported dual CPU configurations.
Release 2.0(2m) adds support for the following:
- Integration of Cisco C200 M2 SFF, C460 M2, C220 M3, C260 M2, and C240 M3 rack-mount servers
- Nexus 2232 Fabric Extender (replaces Nexus 2248 in this and following releases, see the Cisco UCS C-Series hardware documentation for details)
- Cisco UCS B200 M3 blade server
- Cisco VIC 1240 mLOM
- Port Expander Card for VIC 1240
- Cisco UCS 6296 fabric interconnect
- Cisco 2204 IO module
- Cisco VIC 1280 adapter card
Release 2.0(1w) adds support for the following:
- Version 2 of UCS B440 M1 and M2 Blade Servers. This new hardware version is part of a proactive replacement program. See Field Notice 63430 for further details.
New Software Features in Release 2.0
Release 2.0(5d) adds support for the following:
![]()
Note The changes are documented in the Intel public Specification Updates for August 2013.
Release 2.0(5a) adds support for the following:
- BIOS Policy Settings—Provides the ability to select refresh interval rate for internal memory.
- Memory Speed—Enables 1333 MHz memory speed for 8GB/16GB 1600-MHz RDIMMs populated with 3 DIMMs Per Channel/1.5v on the Cisco UCS B200 M3 blade server and Cisco UCS C240 M3 rack server.
- Call Home—Enables you to configure call home for CMOS battery voltage low alert.
Release 2.0(1m) adds support for the following:
- Licensing—Updated information for new UCS hardware.
- Firmware Bundle Option—Enables you to select a bundle instead of a version when updating firmware using the Cisco UCS Manager GUI.
- Disk Drive Monitoring Support—Support for disk drive monitoring on certain blade servers and a specific LSI storage controller firmware level.
- iSCSI Boot—iSCSI boot enables a server to boot its operating system from an iSCSI target machine located remotely over a network.
- Pre-login Banner—Displays user-defined banner text prior to login when a user logs into Cisco UCS Manager using the GUI or CLI.
- Unified Ports—Unified ports are ports on the 6200 series fabric interconnect that can be configured to carry either Ethernet or Fibre Channel traffic.
- Upstream Disjoint Layer-2 Networks—Enables you to configure Cisco UCS to communicate with upstream disjoint layer-2 networks.
- Virtual Interfaces—The number of vNICs and vHBAs configurable for a service profile is determined by adapter capability and the amount of virtual interface (VIF) namespace available on the adapter.
- VM-FEX Integration for VMware—Cisco Virtual Machine Fabric Extender (VM-FEX) for VMware provides management integration and network communication between Cisco UCS Manager and VMware vCenter. In previous releases, this functionality was known as VN-Link in Hardware.
- VM-FEX Integration for KVM (Red Hat Linux)—Cisco Virtual Machine Fabric Extender (VM-FEX) for KVM provides external switching for virtual machines running on a KVM Linux-based hypervisor in a Cisco UCS instance.
Resolved Caveats
This section contains resolved caveats for the following releases:
Release 2.0(5)
- “Resolved Caveats in Release 2.0(5g)” section
- “Resolved Caveats in Release 2.0(5f)” section
- “Resolved Caveats in Release 2.0(5e)” section
- “Resolved Caveats in Release 2.0(5d)” section
- “Resolved Caveats in Release 2.0(5c)” section
- “Resolved Caveats in Release 2.0(5b)” section
- “Resolved Caveats in Release 2.0(5a)” section
The following caveats are resolved in the 2.0(5g) release:
The following caveats are resolved in the 2.0(5f) release:
The following caveats are resolved in the 2.0(5e) release:
The following caveats are resolved in the 2.0(5d) release:
The following caveats are resolved in the 2.0(5c) release:
The following caveats are resolved in the 2.0(5b) release:
The following caveats are resolved in the 2.0(5a) release:
The following caveats are resolved in the 2.0(4d) release:
The following caveats are resolved in the 2.0(4b) release:
The following caveats are resolved in the 2.0(4a) release:
The following caveats are resolved in the 2.0(3c) release:
The following caveats are resolved in the 2.0(3b) release:
The following caveats are resolved in the 2.0(3a) release:
The following caveats are resolved in the 2.0(2r) release:
The following caveats are resolved in the 2.0(2q) release:
The following caveats are resolved in the 2.0(2m) release:
The following caveats are resolved in the 2.0(1x) release:
The following caveats are resolved in the 2.0(1w) release:
The following caveats are resolved in the 2.0(1t) release:
The following caveats are resolved in the 2.0(1s) release:
The following caveats are resolved in the 2.0(1q) release:
PAA for a SPAN session now works with 8Gb transceivers and Fibre Channel expansion modules on the fabric interconnect.
Using the Cisco UCS Manager GUI, you are now able to disassociate a service profile that is currently bound to a template.
When you assign an organization to a locale in the Cisco UCS Manager GUI, the operation sometimes fails due to an internal error. This error is now corrected.
The PCI Device address of a vNIC will not change after an upgrade of Cisco UCS Manager from Release 1.x to Release 2.0(1q).
When the DHCP server is using an option 67 (RFC 2132) to report the bootfile name to the gPXE client, gPXE will receive the boot parameters and the boot will function normally.
When the BIOS is upgraded on a B230-M1 blade from Cisco UCS Release 1.x to Release 2.0, the PCI address is preserved.
Note In the New Hardware Features in Release 2.0, see the BIOS section for issues when upgrading the B230-M1 BIOS from Release 2.0(1m) to Release 2.0(1q) or later.A B230-M1 blade discovered while running a Cisco UCS 1.4 BIOS Release image and now running a Cisco UCS 2.0 Release BIOS image will associate and disassociate normally.
command or running an SNMP agent querying this SNMP object will no longer cause an unexpected reboot.
If the hostname is configured for the vCenter in Cisco UCS Manager and the DNS server does not reply with the hostname to IP mapping within 30 seconds, the VMS process will no longer crash unexpectedly.
A Blade with a service profile with a 22 character or longer name will boot as expected from the local disk after upgrading the BIOS from a 1.x release to the BIOS in the 2.0(1q) release.
The following caveats are resolved in the 2.0(1m) release:
Open Caveats
This section contains open caveats for the following releases:
- Common Across Release 2.0
- Release 2.0(5)
- Release 2.0(4)
- Release 2.0(3)
- Release 2.0(2)
- Release 2.0(1)
The following caveats are common across Release 2.0:
The following caveats were found in Release 2.0(5g)
The following caveats were found in Release 2.0(5f)
The following caveats were found in Release 2.0(5d)
The following caveats were found in Release 2.0(5c)
The following caveats were found in Release 2.0(5a)
The following caveats were found in Release 2.0(4d)
The following caveats were found in Release 2.0(4b)
The following caveats were found in Release 2.0(4a)
The following caveats were found in Release 2.0(3c)
The following caveats were found in Release 2.0(3b)
The following caveats were found in Release 2.0(3a)
The following caveats were found in Release 2.0(2r)
The following caveats were found in Release 2.0(2q)
The following caveats were found in Release 2.0(2m)
The following caveats were found in Release 2.0(1x):
The following caveats were found in Release 2.0(1t):
The following caveats were found in Release 2.0(1s):
The following caveats were found in Release 2.0(1q):
The following caveats were found in Release 2.0(1m):
Known Limitations and Behaviors
The following known limitations found in Release 2.0(5f) are not otherwise documented:
- On platforms with 00B storage controller, Cisco UCS Manager displays usable (coerced) value in disk inventory section, which is different than the raw 'NumberOfBlocks' value displayed in catalog section. This is a non-issue; Cisco UCS Manager is designed to report the coerced, or usable, size as reported by the LSI controller. Both the host and OOB interfaces report this same value.
- While upgrading from Release 2.0(2q) to 2.0(5a) or higher, the hosts cannot login to storage due to a conflict in the FCoE VLAN ID with one of the regular VLANs. The VLAN conflict is not a supported configuration and it should be fixed prior to the upgrade.
- After the firmware upgrade from Release 1.4(3m) to any later release, vMotion fails due to AES-NI bit difference. As a workaround, disable the OEM AESNI control in BIOS for the blade that is upgraded. Once this feature is disabled and the blade is booted to ESXi, vMotion is allowed to proceed between the two hosts without any issues.
The following known limitations found in Release 2.0(5a) are not otherwise documented:
- Single chassis set up might generate an error with a warning message on accessing shared storage. This might have an impact on system’s service when the fabric interconnect fails. In a multiple chassis set up, this might not cause an issue, except in IOM firmware upgrade. If this error does not clear or re occurs, do one of the following: (CSCtu17144)
–
Remove and re-seat the IO module, making sure module is firmly in contact with the backplane.
![]()
Note Do not upgrade IOM firmware until this error is cleared.
The following known limitations found in Release 2.0(3a) are not otherwise documented:
- The 2.0(3d).T catalog is not backward compatible with Release 2.0(2) or Release 2.0(1).
- The IOM reset CMC process does not complete due to an inoperable IOM. Replacing the IOM with a new IOM does not clear the state for a long time and the new IOM does not come up. This issue occurs when the reset CMC process is issued to an IOM that the Cisco UCS Manager cannot communicate with.
- The PLOGI frames can get dropped in the fabric interconnect and as a result, the hosts do not have a path to the LUNs. This issue was observed only once while adding the additional chassis to the fabric interconnect.
- When an Ethernet border port failure occurs, the host ports are repinned to a new border port. This issue could cause a few FCoE frames to be dropped. This issue is observed on a failover from one Ethernet border port to another and it can be noticed only when there is a high rate of the FCoE traffic. This is a transient issue and it recovers immediately.
- While downgrading Cisco UCS Manager from Release 2.0(x) to Release 1.4(x) with CLI commands being issued, an svc_sam_dme core dump may occur along with a CLI command failure. This issue could occur due to the following conditions:
–
When an image is activated through the GUI, CLI commands are issued.
–
When an image is activated through the CLI, CLI commands are issued from another CLI session.
To avoid this issue, do not issue CLI commands during the process of image activation.
The following known limitations found in Release 2.0(2) are not otherwise documented:
- If upgrading from build 2.0(2m) to 2.0(2q), if you check the AES-NI control on B200 M2 and B250 M2 blades, the AES-NI setting value polarity reverses. The BIOS in build 2m defines the AES-NI NVRAM with 0 = disabled and 1 = enabled. The BIOS in build 2q defines the AES-NI NVRAM value with 0 = enabled and 1 = disabled.
- Whenever a 2232 FEX is decommissioned and re-commissioned, all the servers that are connected to that FEX must be re-acknowledged.
- During an upgrade from 2.0(1) to 2.0(2), duplicate IQNs are not allowed. Any duplicate IQNs statically entered will raise an alarm. This is seen in service profiles with duplicate IQNs assigned to multiple iSCSI vNICs. There are two fixes. One corrects the issue before the upgrade. The second fixes the issue assuming the upgrade has already been performed. Either fix will correct the issue.
Modify any service profiles or service profile templates with iSCSI vNICs to have unique IQNs. Remove any duplicates. If necessary, use the PowerShell script provided in the upgrade notes to find out which iSCSI vNICs reuse the same iSCSI name.
a.
Cisco UCS Manager will throw faults on iSCSI vNICs which have the shared IQN name.
command to find which iSCSI vNIC has the IQN registered.
c.
Modify the iSCSI vNIC which is using the same IQN name but is not registered, and then edit the IQN name (manual or pooled).
d.
Make any change to the SP (ex:- Fw upgrade or modify description and so on.)
command and make sure that the IQNs are registered in Cisco UCS Manager.
The details of the PowerShell script are provided in the troubleshooting and upgrade guide. (CSCty29247)
- At the end of installing ESXi 5.0 to an iSCSI LUN, an error message appears “expecting 2 boot bank, found 0". This message is not critical and a reboot of the system will start a normal boot of ESXi without any issues.
- Power-related BIOS options for C1E are disabled by default on a B200 M3.
- If the desired power state for a service profile associated with a blade server or an integrated rack-mount server is set to off, using the power button or Cisco UCS Manager to reset the server will cause the desired power state of the server to become out of sync with the actual power state and the server may unexpectedly shut down at a later time. To safely reboot a server from a power-down state, use the Boot Server action in the Cisco UCS Manager GUI.
The following known limitations found in Release 2.0(1) are not otherwise documented:
- When using the Windows VIRTIO driver in a virtual machine, Ethernet performance is low when compared to Linux based VMs in a Red Hat KVM environment. Windows does not currently support the LRO feature. To minimize performance impacts, disable GRO using the ethtool -K interface gro command. Disabling GRO may cause higher CPU utilization with TCP traffic.
- A bonded interface will not start as a slave if the MASTER value is in double quotes. You will not be able to create NIC teaming (channel bonding) with third-party adapters.
- The HDD fault monitoring feature cannot detect failures in all possible circumstances. The disk controller may report the disk as operable even though some blocks are marked Unknown. In this circumstance, RAID creation will fail. There is no workaround. ()
- When trying to configure an FC uplink or VSAN as an FC traffic monitoring source, an error message appears stating “Error creating mon-src-mysession. FC Port (1/29) cannot be configured as ingress SPAN source due to hardware limitation.” This only happens on Cisco UCS 6200 Fabric Interconnects. ASICs in these fabric interconnects do not allow a FC port or VSAN to be added as a SPAN (traffic monitoring session) source. There is no workaround. You can still can add a VFC as a source for an Ethernet traffic monitoring session. (
- When Cisco UCS Manager and fabric interconnect activation are done together, the switch upgrade can take longer than usual. This may happen when not following the published upgrade procedure. ()
- On an adapter configured with two iSCSI VNICs, only the iSCSI VNIC designated as primary in the boot order will post the discovered iSCSI LUN to the BIOS and write an iBFT entry to the host memory during boot. There is no workaround. (CSCtr51704)
- After an upgrade from a prior release to 2.0(1), a critical fault may be raised about an overlapping or matching FCoE VLAN ID used for a vSAN and an Ethernet VLAN ID under the same fabric as the FCoE VLAN. Raising a fault is the correct behavior under this circumstance. The fault can be avoided by changing either the FCoE VLAN ID or the Ethernet VLAN ID so that they have two different IDs prior to the upgrade. Resolving the problem after the upgrade may lead to down time for the system. See the Software Advisory . (
- When using Release 2.0, BIOS versions from the 1.4 software versions may be listed. If these versions are selected when attempting a BIOS recovery, the result is a system boot failure in B440 and B200 blades, the recovery may not complete, and the system may be permanently damaged or unrecoverable. You must choose to recover the BIOS to a BIOS version from the 2.0 software release. (
- Before you delete a VLAN from a fabric interconnect, ensure that the VLAN has been removed from all vNICs and vNIC templates. If you delete a VLAN that is assigned to a vNIC or vNIC template, the vNIC could allow that VLAN to flap.
- If during RHEL 5.x installation to an iSCSI LUN on a blade with a Broadcom M51KR-B adapter RHEL 5.x does not detect the iSCSI LUN during OS installation, select the Broadcom M51KR-B port during the install and manually assign the initiator IP address, subnet mask, and gateway with the values from the service profile. ()
- When UCS is connected to an upstream Cisco Nexus 7000 Series switch (running 4.2.4 version) using port-channels, and if the port channel is configured as LACP passive on the Cisco Nexus 7000 Series switch side, it is possible that under high system stress situation, LACP may not be able to converge for the port channel. The workaround is to avoid native VLAN configuration change while system instability is in place or CPU utilization is high. Using LACP active on Cisco Nexus 7000 Series switch also reduces the likelihood of the problem occurring.
- Per- packet Veth statistics for the UCS M81KR adapter are no longer supported, and will display as 0. Supported statistics are now packets, packets mcast, packets bcast, Bytes, and packets dropped.
- When SAN port channel or a HIF port channel has FC traffic flowing through them, any link flap in the port channel can cause the FC traffic to be impacted or lost. Even multipathing does not help the FC traffic to continue as the VFC is operationally up via the other links of the port channel. Traffic will recover after a short while, but increasing SCSI timer settings can help. ()
- When the BIOS is upgraded on a B230-M1 blade from Release 2.0(1m) to Release 2.0(1q) or later, the PCI bus enumeration will shift by one bus number. This renumbering can cause certain operating systems such as VMware ESX or Windows to see the old vNICs and vHBAs with the new PCI address and could result in those interfaces being inoperable unless the configuration is changed in the OS. In case of ESX, a workaround is to edit the esx.conf with the new PCI address and to modify the vswitch configuration. This issue results from the resolution of Caveat CSCts86890, and affects only the upgrade of this specific server between these two specific releases. See the Software Advisory .
- After downgrading from Cisco UCS Manager 2.0 to 1.4(1) or 1.4(2), the fabric interconnect can become unstable and fail to boot. This is usually due to having enabled features specific to release 2.0 that are not available in the earlier release and neglecting to disable those features before attempting the downgrade. In general, it is best to contact TAC and have them walk through a downgrade with you rather than attempt it unassisted.
- After upgrading from a 1.3.x to a 1.4.x or a later release, you might see the service profile configuration disappears from an organization. To confirm that this problem has occurred, use a CLI command that begins with show service-profile . A NULL CLI output confirms the problem. This problem is most likely to occur if you created an organization with a space in its name while running a Cisco UCS Manager 1.0 release and then later upgraded Cisco UCS Manager to a 1.3.x release. In the 1.3.x release, spaces are not allowed in organization names and are automatically replaced with an underscore. If the system is subsequently upgraded to a 1.4.x or later release, the old organization name with a space reappears without the space to underscore conversion and all of its children (which includes service profiles, policies, and templates) are deleted. Note: An organization that was created in a Cisco UCS 1.3.x release or with a name that does not contain a space character will not have this problem.
To avoid this problem, do the following before upgrading from a 1.3.x release to a 1.4.x or a later release:
1. Change the description field of the organizations that have underscores in their names by removing the underscores and any spaces to help keep the organizations in the database.
2. Create a backup using the All Configuration option before upgrading. If a problem occurs after the upgrade, restore the configuration using the backup file. After importing the configuration file, reacknowledge all blades to restore their VIF status.
Open Caveats from Prior Releases
This section contains open caveats for the following releases:
- Release 1.4(3)
- Release 1.4(2)
- Release 1.4(1)
- Release 1.3(1)
- Release 1.2(1)
- Release 1.1(1)
- Release 1.0(2)
- Release 1.0(1)
The following caveats were found in Release 1.4(3):
The following caveats were found in Release 1.4(2b):
The following caveats were found in Release 1.4(1i):
Release 1.3(1)
The following caveats were opened in Release 1.3(1c):
The following caveats were opened in Release 1.2(1):
This section lists the open caveats in release 1.1(1j).
This section lists the open caveats in release 1.0(2).
This section lists the open caveats in release 1.0(1).
Related Documentation
For more information, you can access related documents from the following links:
Obtaining Documentation and Submitting a Service Request
.
, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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. (1110R)
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.