McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 24

↗ View in doc context
page
24
source
uc-solutions/virtualization/cisco-uc-virtualization-guide/cisco-uc-virtualization-guide.md
chunk_id
uc-solutions::virtualization::cisco-uc-virtualization-guide::cisco-uc-virtualization-guide::23

© 2026 Cisco and/or its affiliates. All rights reserved. Page 24 of 34 Virtualization Requirements for Cisco NFVIS-for-UC Overview For an overview of Cisco NFVIS-for-UC as a supported virtualization environment, see the Introduction to Supported Virtualization Environments. ● Cisco NFVIS-for-UC is only supported on the following hardware: o Cisco calling appliances: Business Edition 6000/7000 M5, M6, M7 generations and Cisco Expressway CE1400V M7. ● You must also follow any compatibility instructions in Supported Platforms from NFVIS Release Notes (for example, Link). ● You must also follow the application rules for CPU, Memory, Storage, and Network in this chapter. Application / Hypervisor Compatibility The minimum supported releases are 15 SU4 / X15.4 with NFVIS-for-UC 4.18. Supported NFVIS-for-UC releases can be classified as Major and Minor. Within a Major/Minor, there are various Maintenance releases. For compatibility of application releases with NFVIS-for-UC Major/Minor releases (for example, “4.18”), see each application’s Installation Guide.

  1. Cisco Unified Communications Manager and the IM and Presence Service
  2. Cisco Expressway Installation Guide
  3. Cisco Emergency Responder Administration Guide ● Compatible releases will be explicitly listed. Newer hardware generations may require a newer minimum Major/Minor release. ● Unlisted releases are not supported and not tested. ● See Cisco EOL Bulletins for when compatible releases enter Cisco’s release end-of-life and implications for support. Within a supported NFVIS-for-UC Major/Minor release, ● A minimum Maintenance release may be required for application compatibility (for example, “4.18.2a” not “4.18.1” is the minimum requirement for “4.18” compatibility). ● Subsequent Maintenance releases (for example, “4.18.2a” as the minimum compatible release vs. future “4.18.3”) are compatible unless explicitly indicated otherwise. ● There are no other versioned components that need to be tracked/managed.