DocWiki - User contributions [en]

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2012-07-16T20:48:57Z

Jkratky: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

= Supported Virtual Machine OVA Templates =

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications '''must''' use one of the supported virtual machine configurations in the tables below in order to be supported. The OVAs contain virtual hard disks with pre-aligned disk partitions. Using the OVA is the only way to deploy the UC applications on aligned disks. Using the OVA also guarantees that all configuration of the virtual machine is correct and supported.

In the tables below '''users''' refers to the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

 See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Template Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder 8.5 and 8.6'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|}
 
{| border="1" style="width: 1077px; height: 416px"
|+ '''Supported OVA Templates: Cisco Emergency Responder 8.7 and 9.0'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
Emergency Responder 12,000 users Only for C200M2 TRC#1

| 2 (with 800 MHz reservation) 
| E5506 2.13 GHz
| 4 GB (with all 4 GB reserved)
| 1x 80 GB disk
| 1
| For use only on UCS C200M2 TRC#1. Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
!
Emergency Responder 20,000 users Not for C200M2 TRC#1

| 1 (with 800 MHz reservation) 
| E5540 2.53 GHz
| 4 GB (with all 4 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use on C200 M2 TRC#1. Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
!
Emergency Responder 30,000 users Not for C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GH
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk
| 1
| Not for use on C200 M2 TRC#1. Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|-
!
Emergency Responder 40,000 users Not for C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk
| 1
| Not for use on C200 M2 TRC#1. Limits:

:*40,000 IP phones
:*12,500 analog phones
:*4,000 roaming phones (per Emergency Responder cluster)
:*2,500 LAN switches
:*150,000 switch ports
:*12,500 ERLs

 

|}

 

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|}

 

== Cisco Intercompany Media Engine ==

{| border="1" style="width: 712px; height: 416px"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 5000 users
| 2 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*48 ports
:*36 text-to-speech ports

|-
! 15,000 users
| 4 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*144 ports
:*36 text-to-speech ports

|}

 

== Cisco Unified Presence (referred to as IM and Presence from Release 9.0(1) and later) ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 
*[[OVA Template Details for Unified Presence Release 8.6(4)]] 
*[[OVA Template Details for IM and Presence Release 9.0(1)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: {{Note| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 8.5 (1))
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
| rowspan="3" | See [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/uccx851ig.pdf Installing Cisco Unified Contact Center Express Release 8.5(1) guide]for more information on vDisk space.
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 9.0 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
| rowspan="3" | See [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/uccx851ig.pdf Installing Cisco Unified Contact Center Express Release 9.0(1) guide]for more information on vDisk space.
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording
:*'''Virtualizing''' the Monitor server for Server (SPAN) recording is '''not '''supported on the UCS platform

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|
|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283884662&flowid=28561&softwareid=282773197&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest OM, SM, SSM OVAs] CPU/Memory in table above.
|
|
|
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*[http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]
*[[OVA Template Details for Unified Contact Center Enterprise Release 8.x]]
*[[OVA Template Details for Unified Contact Center Enterprise Release 9.x]]

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense Virtualization for Cisco MediaSense]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense Release 8.5'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" |
Release 8.5(2)

Release 8.5(3)

Release 8.5(4)

|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

 

To promote ease of use, MediaSense Release 9.0 has only one template. This template contains a list of deployment options as shown in the following table.  

{| width="812" cellspacing="1" cellpadding="1" border="1"
|+ '''Supported OVA Template: Cisco MediaSense Release 9.0'''
|-
! valign="baseline" align="center" scope="col" | Deployment  
! valign="baseline" align="center" scope="col" |   vCPU   
! valign="baseline" align="center" scope="col" |
CPU      reservation  

! valign="baseline" align="center" scope="col" |  vRAM 
! valign="baseline" align="center" scope="col" |    vDisk    
! valign="baseline" align="center" scope="col" | Notes            
|-
! valign="baseline" align="center" | SRE 
| valign="baseline" align="center" |
 2

| valign="baseline" align="center" |
  2200 MHz

| valign="baseline" align="center" |
 6 GB

| valign="top" align="left" |
Disk 1: 80 GB for OS Disk 2: 80 GB for DB  Disk 3: 200 GB for media               

| valign="top" align="left" |
Includes a fixed 200 GB disk for media storage. No expansion nodes supported. No additional media storage supported. 

|-
! valign="baseline" align="center" |  Primary/Secondary    
| valign="baseline" align="center" |    7 
| valign="baseline" align="center" |   15000 MHz 
| valign="baseline" align="center" |  8 GB 
| valign="top" align="left" |
Disk 1: 80 GB for OS  Disk 2: 600 GB for DB 

| valign="top" align="left" |
User must add media disks prior to installation. 

|-
! valign="baseline" align="center" | Expansion
| valign="baseline" align="center" |    7
| valign="baseline" align="center" | 10000 MHz 
| valign="baseline" align="center" | 8 GB 
| valign="top" align="left" |
Disk 1: 80 GB for OS Disk 2: 80 GB

| valign="top" align="left" |
User must add media disks prior to installation.

|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&release=9.0.1&relind=AVAILABLE&softwareid=283733464&rellifecycle=&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
|-
! Large deployment option
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
|-
! Small deployment option
| 2
| 8 GB
| 2x 80GB
| 1
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

{| cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
|
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_1_v2.0] 

Deployment Option:

100 agents - Email Only 

| Application, Services Server ,File server Messaging Server ,Web Server and Database server
| 1
| 2 
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_2_v2.0] 

Deployment Option:

140 agents - Email Only

 

| Application, Services Server ,File server Messaging Server and Web server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_3_v2.0] 

Deployment Option:

100 agents - Chat only or

100 agents - Email and Chat  

| Application, Services Server ,File server Messaging Server and Database server
| 1
| 2
| 1 x 80GB
| 4
|-
| Web Server
| 1
| 1
| 1 x 80GB
| 2 
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_4_v2.0] 

Deployment Option:

250 Agents - Email and Chat or 120 Agents - BC and CallBack

 

 

| Web Server
| 1
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2 
| 1 x 80 GB for OS, 1 x 150 GB for DB
| 4
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_5_v2.0] 

Deployment Option:

500 Agents - Email and Chat or 240 Agents - BC and CallBack 

 

| Web Server
| 2 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 8
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 1
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_6_v2.0] 

Deployment Option:

750 Agents - Email and Chat or 360 Agents - BC and CallBack 

| Web Server
| 3
| 1
| 1 x 80GB
| 1
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16 
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_7_v2.0] 

Deployment Option:

1000 Agents - Email and Chat or 480 Agents - BC and CallBack 

| Web Server
| 4
| 1
| 1 x 80GB
| 1
|-
| Application server
| 4 
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_8_v2.0] 

Deployment Option:

1250 Agents - Email and Chat or 600 Agents - BC and CallBack 

| Web Server
| 5 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 5
| 2
| 1 x 80GB
| 2 
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|}

 

== Cisco Media Blender ==

{| width="1054" cellspacing="1" cellpadding="1" border="1" align="center" style="width: 1054px; height: 102px"
|-
|
 '''Application, OVA Capacity and Notes+Download Link'''

|         '''Contents    '''  
| '''No of VM's to deploy of each component'''
| '''vCPU'''
| '''vDisk'''
| '''vRAM/Memory'''
|-
|
 [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all Cisco Media Blender]

|
 

Cisco Media Blender

|
 1

|
 2

|
 1 x 80GB

|
 2

|}

 

== Cisco Finesse ==

See also:

*[[Virtualization for Cisco Finesse|Cisco Finesse]]
*[http://www.cisco.com/cisco/software/type.html?mdfid=283613135&flowid=30701 Cisco Finesse OVA Templates] 

{| border="1"
|+ '''Supported OVA Templates: Cisco Finesse'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Finesse_2000_agents_v9.0.1_vm8
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 9.0(1)
|-
! Finesse_2000_agents_v1.0_vmv7 
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 8.5(3)
|}

  

== TelePresence Applications ==

{| border="1"
|+ '''Supported OVA Templates: TelePresence Applications'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores 
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
!  [http://www.cisco.com/cisco/software/release.html?mdfid=284132721&flowid=29922&softwareid=280887004&release=1.8.0%28582%29 Cisco TelePresence Manager] 
| align="center" | 2
| align="center" | 8 GB (4 GB reserved)
| align="center" | 1 x 200 GB
| align="center" | 1
|
1.9.0 Supported Co-residency Configurations:

*Up to 4 CTS-Manager instances can be installed on a single server, for service provider deployments with no more than 50 endpoints under management per instance of CTS-Manager. 
*1 CTS-Manager and 1 CTMS can be installed on a single UCS server. 

 

|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=281043620&flowid=20525&softwareid=281149680&release=1.8.0%281026%29 Cisco TelePresence Multipoint Switch] 
| align="center" | 4
| align="center" | 6 GB (2.304 GB reserved)
| align="center" | 1 x 100 GB
| align="center" | 1
|
1.9.0 Supported Co-residency Configurations:

:*2 CTMS instances can be installed on a single UCS server.
:*1 CTMS and 1 CTS-Manager can be installed on a single UCS server.

 

|}

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Virtualization for Unified CCE 9.x

2012-07-16T20:31:43Z

Jkratky: 1 revision

== Updates to this Page ==

The following is a list of significant updates to this page:

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| June 18, 2012
| New virtualization page for 9.x
|-
| June 19, 2012
| Overall Edits for 9.x release
|-
| 
| 
|}

== Information for Partners about Unified CCE on UCS Deployment Certification and Ordering ==

'''It is important that partners who are planning to sell UCS products on Unified Contact Center Enterprise read the DocWiki page''' [http://docwiki.cisco.com/wiki/UCCE_on_UCS_Deployment_Certification_Requirements_and_Ordering_Information UCCE on UCS Deployment Certification Requirements and Ordering Information.]

This page contains essential information for partners about the following:

:*Partner Certification Requirements
:*UCS Server Ordering Information
:*Important Notes on Cisco UCS Service and Support

 

== Unified CCE 9.x Support for Virtualization on the ESXi/UCS Platform ==

Starting with Release 8.0(2), virtualization of the following deployments and Unified CCE components on Cisco Unified Computing Systems (UCS) B200 Series and C210 Series hardware is supported:

:*Router
:*Logger
:*Agent PG
:*MR PG
:*VRU PG
:*Unified Contact Center Gateway
:*Avaya ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2)
:*TDM ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2)
:*Cisco Agent Desktop (CAD) Server
:*Administration and Data Server with one of the following roles:
::*Administration Server and Real-time Data Server (AW)
::*Configuration-only Administration Server (AW-CONFIG)
::*Administration Server and Real-time and Historical Data Server (AW-HDS)
::*Administration Server, Real-time and Historical Data Server, and Detail Data Server (AW-HDS-DDS)
::*Historical Data Server and Detail Data Server (HDS-DDS)
:*Administration Client
:*Outbound Option with SIP Dialer (collocate SIP Dialer and MR PG with Agent PG in the same VM guest. Generic PG can also be collocated with the Agent PG in the same VM guest. Published agent capacity formula with Outbound Option applies.)
:*Support Tools
:*Rogger (a Router and a Logger in the same VM)
:*The Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE is supported; see the section [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Support_for_UCM_Clustering_Over_the_WAN_with_Unified_CCE_on_UCS_Hardware Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware]for important information.
:*Unified IP-IVR is supported with Unified CCE on UCS B-Series solution and on UCS C-Series with the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] only. Please refer to the IPIVR product specific pages for detail.
:*CVP is supported with CCE on UCS solution. Please refer to the [[Virtualization for Unified CVP]] wiki page for details.
:*Contact Center Management Portal (CCMP). See the [http://docwiki.cisco.com/wiki/Virtualization_for_CCMP_with_Unified_CCE_on_UCS_Hardware Virtualization for CCMP with Unified CCE on UCS Hardware] wiki page for details.
:*Cisco Unified Intelligence Center (Unified IC). Please refer to the [http://docwiki.cisco.com/wiki/Cisco_Unified_Intelligence_Center Cisco Unified Intelligence Center] wiki page for details.
:*Cisco E-mail Interaction Manager (EIM)/Web Interaction Manager (WIM). See the Virtualization for EIM-WIM wiki page for details

 

The following deployments and Unified CCE components have not been qualified and '''are not supported''' in virtualization:

:*Progger (a Router, a Logger, and a Peripheral Gateway); this all-in-one deployment configuration is not scalable in a virtualization environment. Instead, use the Rogger or Router/Logger VM deployment configuration.
:*Unified CCH
:*Unified ICMH
:*Unified ICME with more than 12,000 agents and/or the use of NIC, SIGTRAN
:*Outbound Option with SCCP Dialer
:*WebView Server
:*Expert Advisor
:*Remote Silent Monitoring (RSM)
:*Span based Silent Monitoring on UCS B-series chassis
:*Cisco Unified CRM Connector
:*IPsec. UCS does not support IPsec off-board processing, therefore IPsec is not supported in virtualization.

{{note|The hybrid (virtual and non-virtual server) deployment model is supported. Components that are not yet virtualized can continue to be on MCS in the UCCE on UCS deployment. See the [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Hybrid_Deployment_Options Hybrid Deployment Options] section for more information.}}

 

The following VMware features are not supported with Unified CCE:

:*VMware Physical to Virtual migration
:*VMware snapshots
:*VMware Consolidated Backup
:*VMware High Availability (HA)
:*VMware Site Recovery Manager
:*VMware vCenter Update Manager
:*VMware vCenter Converter

 

== Hardware Requirements for Unified CCE Virtualized Systems ==

Requirements for Cisco Unified CCE systems using UCS B200 or C210 hardware are located in the [http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware Unified Computing System Hardware]. These are the UC on UCS '''TRC (Test Reference Configuration)''' models. For UCS C210, Unified CCE supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] with a specific HDS Virtual Machine (VM) coresidence/population rule. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments].

=== Cisco SmartPlay Solution Packs for UC/Hardware Bundles Support ===

[http://www.cisco.com/web/partners/incentives_and_promotions/cisco_smartplay_promo.html Cisco SmartPlay Solution Packs for UC], which are the pre-configured bundles (value UC bundles) based on '''UCS B200M2 or C210M2''' as an alternative ordering to UC on UCS TRCs above are '''supported with caveats''':

:*For '''B200M2 and C210M2 Solution Packs (''Value UC Bundles'')''' that have better specification than the UC on UCS B200M2/C210M2 TRC models (e.g., 6 cores per same cpu family, etc.), the UC on UCS spec-based HW support policy needs to be followed and these bundles are supported by UCCE/CVP as an exception providing the same UCCE VM co-residency rules are compliant and the number of CVP Call Server VMs cannot be more than two on the same server/host.
:*For ''other Spec-based Servers'' according to UC on UCS Spec-based Hardware Policy that have specification equal to or better than the UC on UCS B200M2/C210M2 TRCs, they '''may''' be used for UCCE/CVP once validated in the Customer Collaboration DMS/A2Q (Design Mentoring Session/Assessment To Quality) process. This also means a particular desired spec-based server model may '''not be approved''' for use after the server design review in the DMS/A2Q session.

 Unified CCE supports MCS-7845-I3-CCE2 with virtualization. For a list of supported virtualized components on MCS servers, see the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted.]Unified CCE does not support UCS C200.

== VMware and Application Software Requirements ==

The following software requirements apply specifically to Unified Contact Center Enterprise:

:VMWare ESXi 5.0 is the only supported hypervisor for Unified Contact Center Enterprise release 9.x.
:*If you are upgrading ESXi software, see the section [http://docwiki.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance Upgrade ESXi].
:*The Windows, SQL, and other third party software requirements for the Unified CCE applications in the ESXi/UCS platform are the same as in the physical server. For more information see the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted].

 

=== ESXi 5.0 Software Requirements ===

When Cisco Unified CCE is running on ESXi 5.0, you must perform the following steps:

:*You must install or upgrade VMware Tools for ESXi 5.0 on each of the VMs and use all of the VMware Tools default settings. For more information, see the section [http://docwiki.cisco.com/wiki/VMware_Tools VMware Tools].
:*You must disable Large Receive Offload (LRO). For details, see the section [http://docwiki.cisco.com/wiki/Disable_LRO Disable LRO].

 

= Unified CCE Component Capacities and VM Configuration Requirements =

For supported Unified CCE component capacities and VM computing resource requirements, see the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise List of Unified CCE OVA Templates].

{{note| You must use the OVA VM templates to create the Unified CCE component VMs.}}

 For instructions on how to obtain the OVA templates, see [http://docwiki.cisco.com/wiki/Downloading_OVA_Templates_for_UC_Applications Downloading OVA Templates for UC Applications].

== Unified CCE Scalability Impacts ==

The [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information] is based on the operating conditions published in the ''Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 9.x'', Chapter 10, ''Operating Conditions'' and the ''Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted'''','''''Release 9.x, Section 5. Both documents are available at [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco.com]'''.'''

The following features reduce the scalability of certain components below the agent count of the respective OVA [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information].

*CTI OS Security - CTI OS Server capacity is impacted when CTI OS Security is enabled; capacity is decreased by 25%.
*Mobile Agents - Refer to the SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Mobile Agents.
*Outbound Option – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Outbound Option.
*Agent Greeting – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with the Agent Greeting feature enabled.
*Whisper Announcement - Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with the Whisper Announcement feature enabled.
*Precision Queues – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with precision queues.
*Extended Call Context (ECC) usage greater than the level noted in the Operating Conditions will have a performance and scalability impact on critical components of the Unified CCE solution. As noted in the SRND, the capacity impact will vary based on ECC configuration, therefore, guidance must be provided on a case-by-case basis.

= UCS Network Configuration =

:*'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (UCCE) on UCS servers, see [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE.]
:*'''QoS must be enabled''' for the Private network connections only (between Side A and B) of PGs using PG Setup and set to enabled on Router nodes using Unified CCE Setup. Refer to Chapter 12 of the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND)] for more details.

 

== Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware ==

You can deploy the Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE on UCS hardware.

When you implement this deployment model, be sure to follow the best practices outlined in the section "IPT: Clustering Over the WAN" in the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND).]

In addition, note the following expectations for UCS hardware points of failure:

*For communication path single point of failure performed by Cisco on the Unified CCE UCS B-series High Availability (HA) deployment, system call handling was observed to be degraded for up to 45 seconds while the system recovered from the fault, depending upon the subsystem faulted. Single points of failure will not cause the built-in ICM software failover to occur. Single points of failure include, but are not limited to, a single fabric interconnect failure, a single fabric extender failure, and single link failures.

*Multiple points of failure on the Unified CCE UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.

=== B-Series Considerations ===

Cisco recommends use of the M81KR Virtual Interface Card (VIC) for Unified CCE deployments, though the M71KR(-E/Q) and M72KR(-E/Q) may also be used as per reference design 2 detailed at the dedicated networking page linked below. M51KR, M61KR and 82598KR are not supported for Contact Center use in UCS B series blades.

New B Series deployments are recommended to use Nexus 5000/7000 series data center switches with vPC PortChannels. This technology has been shown to add considerable advantageous to Contact Center applications in fault recovery scenarios.

See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#UCCE_on_UCS_B-Series_Network_Configuration UCCE on UCS B-Series Network Configuration].

=== C-Series Considerations ===

If deploying Clustering Over the WAN with C-Series hardware, '''do not''' trunk public and private networks. You '''must''' use separate physical interfaces off of the C-Series servers to create the public and private connections. See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#UCCE_on_UCS_C-Series_Network_Configuration UCCE on UCS C Series Network Configuration].

 

= Notes for Deploying Unified CCE Applications on UCS B Series Hardware with SAN =

In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays.

In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore.

Keep the following considerations in mind when deploying UCCE applications on UCS B Series hardware with SAN.

*This deployment must comply with the conditions listed in Section 3.1.6 of the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware & System Software Specification (Bill of Materials) for Cisco Unified Contact Center Enterprise.] In particular, SAN disk arrays must be configured as RAID 5 or RAID 10. 
**Note: RAID 6/ADG is also supported as an extension of RAID 5.
*Historical Data Server (HDS) requires a 2 MB datastore block size to accommodate the 500 GB OVA disk size, which exceeds the 256 GB file size supported by the default 1 MB block size for datastores (in ESXi 4.0U1, this may change in later versions). The HDS block size is configured in vSphere at datastore creation.
*To help keep your system running most efficiently, schedule automatic database purging to run when your system is least busy.
*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines:
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.
*The SAN design and configuration must meet the following Windows performance counters on UCCE VMs:
**AverageDiskQueueLength must remain less than (1.5 ∗ (the total number of disks in the array)).
** %Disktime must remain less than 60%. 
*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CCE applications should be designed for the 95th percentile IOPS values published in this wiki. For other UC applications, please follow their respective IOPS requirements & guidelines.
*vSphere will alarm when disk free space is less than 20% free on any datastore. Recommendation is to provision at least 20% free space overhead, with 10% overhead '''required'''.
*Recommend deploying from 4-8 VMs per LUN/datastore so long as IOPS and space requirements can be met, with supported range from 1-10.

 

See below for an example of SAN configuration for Rogger 2000 agent deployment. This example corresponds to the 2000 agent Sample CCE Deployment for UCS B-Series described in: [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCE_9.x#Unified_CCE_Component_VM_Coresidency_and_Sample_Deployments Unified CCE Component Coresidency and Sample Deployments.]

== Example of SAN Configuration for Unified CCE ROGGER Deployment up to 2000 Agents ==

The following SAN configuration was a tested design, though generalized here for illustration. It is not the only possible way in which to provision SAN arrays, LUNs, and datastores to UC applications. However, you must adhere to the guidance given earlier in this section (above).

=== Rogger Side A ===

[[Image:RoggerSideA.jpg]]

=== Rogger Side B ===

[[Image:RoggerSideB.jpg]]

= Steps for Installing/Migrating Unified CCE Components on Virtual Machines =

Follow the steps and references below to install the Unified CCE components on virtual machines. You can use these instructions to install or upgrade systems running with Unified CCE 8.0(2) and later. You can also use these instructions to migrate virtualized systems from Unified CCE 8.0(X) to Unified CCE 9.0(X) or later, including the Avaya PG and other selected TDM PGs that were supported on Unified CCE 8.5(X). Not all TDM PGs supported in Unified CCE 8.5(X) are supported in Unified CCE 9.0(x). For more information, see the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted.]

#Acquire the supported servers for Unified CCE 9.0(X) or later release.
#*Cisco UCS servers are specified in the [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Hardware_Requirements_for_Unified_CCE_Virtualized_Systems Hardware Requirements for Unified CCE Virtualized Systems] section.
#*MCS-7845-I3-CCE2 is specified in the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted].
#*If there are PG VMs that are running on the following older MCS servers, MCS-7845-H2 or MCS-7845-I2, replace these servers with supported servers.
#Install, setup, and configure the servers.
#Configure the network. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#UCS_Network_Configuration UCS Network Configuration]. {{note |Configuring the network for the MCS servers is the same as configuring the network for the UCS C-Series servers.}}
#If VMware VirtualCenter is used for virtualization management, install or update to VMware vCenter Server 5.0 or later.
#Install and Boot VMWare ESXi. See the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide] or the [http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/os/vmware/install/vmware_install_c.html Cisco UCS C-Series Servers VMware Installation Guide]. On C-Series servers or MCS servers, you must configure the ESXi datastore block size for the Administration & Data Server. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Configuring_the_ESXi_Data_Store_Block_Size_for_Administration_and_Data_Server Configuring the ESXi Data Store Block Size for Administration and Data Server] for instructions.
#Create the Unified CCE virtual machines from the OVA templates. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Creating_Virtual_Machines_from_OVA_VM_Templates Creating Virtual Machines from OVA VM Templates].
#Install VMware Tools with the ESXi version on the virtual machines. Install the same version of VMware Tools as the ESXi software on the virtual machines.
#Install Windows OS and SQL Server (for Logger and HDS components) on the created virtual machines. {{note| Microsoft Windows Server 2008 ''Standard Edition'' and Microsoft SQL Server 2008 ''R2 Edition'' should be used for virtual machine guests. See related information in the links below.}}
#Install or migrate the Unified CCE Software components on the configured virtual machines, using Fresh Install or Tech Refresh Upgrade, as described in [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Installing_Unified_CCE_Components_on_Virtual_Machines Installing Unified CCE components on virtual machines] and [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Migrating_Unified_CCE_Components_to_Virtual_Machines Migrating Unified CCE components].

= Unified CCE Component VM Coresidency =

You can have one or more Unified CCE VMs coresident on the same ESXi server (for example, B200M2 blade or C210M2 rack mount server).  However, you must follow the rules described below:

:*You can have any number of Unified CCE virtual machines and combination of coresidency of Unified CCE virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation does not over commit the available ESXi server computing resources. 
:*You must not have CPU overcommit on the ESXi server that is running Unified CCE realtime application components.  The total number of vCPUs among all the virtual machines on an ESXi host must not be greater than the total number of CPUs available on the ESXi server.  In the case of the Cisco UCS B-200 and C-210, the total number of CPUs available is 8.
:*You must not have memory overcommit on the ESXi host running UC realtime applications.  You must allocate a minimum 2GB of memory for the ESXi kernel.  For example, if an ESXi server on B-200 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel you have 34GB available for the virtual machines.  The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.
:*VM coresidency with Unified Communications '''and''' third party applications (for example, WFM) is '''not''' supported unless it is described in the following subsection.

 

The following table shows how Unified CCE components can be coresident on the same ESXi server. '''A diamond indicates that coresidency is allowed'''. For example, the first row shows that Unified Communications Applications can not be colocated with Contact Center Tier 1 Applicaitons. The third row shows that Third Party Applications can only be colocated with Contact Center Tier 3 Applications.

{| class="wikitable FCK__ShowTableBorders"
|-
! Unified CCE Component Coresidency
! Contact Center Tier 1 Applications
! Contact Center Tier 2 Applications
! Contact Center Tier 3 Applications
! Unified Communications Applications
! Third Party Applications
|-
| '''Contact Center Tier 1 Applications: Router, Logger, Peripheral Gateway, ADS-HDS'''
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|
|
|-
| '''Contact Center Tier 2 Applications: CVP Call + VXML Server, CVP Reporting Server, CUIC, CCMP''' 
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" |
|-
| '''Contact Center Tier 3 Applications: ADS/AW (any non-HDS), Admin Client, Support Tools, Windows AD DC, CVP Ops/OAMP Server, CVP Media Server, SocialMiner''' 
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|-
| '''Unified Communications Applications: Communications Manager, Contact Center Express, IPIVR, CUP, Unity, Unity Connection, MediaSense''' 
| align="center" |
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|
|}

{{note|'''EXCEPTIONS''' to the above VM co-residency table:}}

:*On a '''C-Series''' server, the HDS '''cannot''' co-reside with a Router, Logger, or a PG.
:*'''PG''' (in CCE solutions up to 1000 CTIOS agents or 500 CAD agents) VMs '''can''' be co-resident with UCM/CUP/IPIVR VMs on the same ESXi host/server.

 

{{note|If Cisco Support determines that a third party application deployed coresident with a Contact Center Tier 3 application causes that application to fail in performance or function, the customer must address the issue by moving the applications to other servers as necessary to alleviate the failure.}}

For coresidency restrictions specific to individual Unified Communications applications that run on VMs, see the Unified Communications Virtualization Sizing Guideline docwiki.

= Hybrid Deployment Options =

Some Unified Contact Center deployments are supported in a "hybrid" fashion whereby certain components must be deployed on (bare-metal) Media Convergence Servers (MCS) or generic servers, and other components are deployed in virtual machine guests on Unified Computing System (UCS) or MCS servers. The following sub-sections provide further details on these hybrid deployment options.

== Cisco Unified Contact Center Hosted ==

*NAM Rogger is deployed on a (bare-metal) quad CPU server as specified in the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted.]
*Each customer instance central controller (CICM) connecting to the NAM may be deployed in its own virtual machine as a Rogger or separate Router/Logger pair on UCS hardware. Multiple CICM instances are not supported collocated in one VM. Existing published rules and capacities apply to CICM Rogger and Router/Logger VMs. (Note: CICMs are not supported on bare-metal UCS.)
*As in Enterprise deployments, each Agent PG is deployed in its own virtual machine. Multi-instance Agent PGs are not supported in a single VM. Existing published rules and capacities apply to PGs in Hosted deployments.

== Parent/Child Deployments ==

*The parent ICM is deployed on (bare-metal) servers as specified in the appropriate [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted.]
*The Unified Contact Center Enterprise (or Express) child may be deployed virtualized according to existing published VM requirements.
*The Unified Contact Center Enterprise Gateway PG and System PG are each deployed in its own virtual machine; agent capacity (and resources allocated to the VM) are the same as the Unified CCE Agent PG @ 2,000 agent capacity. Use the same virtual machine OVA template to create the CCE Gateway or System PG VM.

= Cisco Unified CCE-Specific Information for OVA Templates =

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/OVA_Template_Details_for_Unified_Contact_Center_Enterprise_Release_9.x OVA Template Details for Unified Contact Center Enterprise Release 9.x]
*[http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Unified CCE OVA Templates]

 

== Creating Virtual Machines by Deploying the OVA Templates ==

In the vSphere client, perform the following steps to deploy the Virtual machines.

#Highlight the host or cluster to which you wish the VM to be deployed.
#Select '''File''' > '''Deploy OVF Template'''.
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''OR '''click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''.
#Verify the details of the template, and click '''Next'''.
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''.
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''.
#Choose a virtual network for the VM, then click '''Next'''.
#Verify the deployment settings, then click '''Finish'''.

== Notes ==

:*VM CPU affinity is not supported. You may not set CPU affinity for Unified CCE application VMs on vSphere.
:*VM Resource Reservation - For Unified CCE 9.0(1) and later, VM resource reservation is supported for Unified CCE application VMs on vSphere. The VM computing resources have a default reservation setting when deployed from the OVA.
:*You must not change the computing resource configuration of your VM at any time.
:*You must never go below the minimum VM computing resource requirements as defined in the OVA templates.
:*ESXi Server hyperthreading is enabled by default.

 

== Preparing for Windows Installation ==

In the vSphere client, perform the following steps to prepare for operating system installation.

#Right click on the virtual machine you want to edit and select '''Edit Settings'''. A Virtual Machine Properties dialog appears.
#On the Hardware tab, select '''CD/DVD Drive 1'''. Under Device Type, select '''Datastore ISO File''' and enter the location of the operating system ISO.
#Click '''OK''' to save setting changes.
#Power up your VM and continue with operating system installation.

 

= Remote Control of the Virtual Machines =

For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. The contact center supervisor can access the ClientAW VM using Windows Remote Desktop.

= Installing VMware Tools =

The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to VMware documentation for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

= Installing Unified CCE Components on Virtual Machines =

Install the Unified CCE components after you create and configure the virtual machine. Installation of the Unified CCE components on a virtual machine is the same as the installation of the components on physical hardware.

Refer to the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Unified CCE documentation] for the steps to install Unified CCE components. You can install the supported Virus Scan software, the Cisco Security Agent(CSA), or any other software in the same way as on physical hardware.

= Migrating Unified CCE Components to Virtual Machines =

Migrate the Unified CCE components from physical hardware or another virtual machine after you create and configure the virtual machine. Migration of these Unified CCE software components to a VM is the same as the migration of the components to new physical hardware and follows existing policies. It requires a Tech Refresh as described in the [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_installation_guides_list.html Upgrade Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted.]

= Configuring the ESXi Data Store Block Size for Administration and Data Server =

This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks (3-10) are RAID 5.

The creation of the virtual machine for the Unified CCE Administration and Data Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store block size to 2MB for it to handle the Unified CCE Administration and Data Server virtual disk size requirement before you deploy the OVAs for the following Unified CCE components:

:*AW-HDS
:*AW-HDS-DDS
:*HDS-DDS

 Steps to configure the ESXi data store block size to 2MB:

#After you install ESXi on the first disk array group (RAID 1 with disk 1 and disk 2), boot ESXi 4.0 and use VMware vSphere Client to connect to the ESXi host.
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB.
#Right-click on this data store and delete it. We will add the data store back in the following steps.
#Click on the “Add Storage…” and select the Disk/LUN.
#The data store that was just deleted will now be available to add, select it.
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.

= Timekeeping Best Practices for Windows =

You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1318 VMware KB: Timekeeping best practices for Windows].

*ESXi hosts and domain controllers should synchronize the time from the same NTP source.
*When Unified CCE virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time.
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.

= System Performance Monitoring Using ESXi Counters =

:*Make sure that you follow VMware's ESXi best practices and SAN vendor's best practices for optimal system performance. 
:*VMware provides a set of system monitoring tools for the ESXi platform and the VMs. These tools are accessible through the VMware Infrastructure Client or through VirtualCenter.
:*You can use Windows Performance Monitor to monitor the performance of the VMs. Be aware that the CPU counters may not reflect the physical CPU usage since the Windows Operating System has no direct access to the physical CPU.
:*You can use Unified CCE Serviceability Tools and Unified CCE reports to monitor the operation and performance of the Unified CCE system.
:*The ESXi Server and the virtual machines must operate within the limit of the following ESXi performance counters.

 

You can use the following ESXi counters as performance indicators.

{| class="wikitable FCK__ShowTableBorders"
|-
! Category
! Object
! Measurement
! Units
! Description
! Performance Indication and Threshold
|-
| CPU
|
:*ESXi Server
:*VM

 

| CPU Usage (Average)
| Percent
| CPU Usage Average in percentage for:
:*ESXi server
:*Virtual machine

 

| Less than 60%.
|-
| CPU
|
:*ESXi Server Processor#
:*VM_vCPU#

 

| CPU Usage 0 - 7 (Average)
| Percent
| CPU Usage Average for:
:*ESXi server for processors 0 to 7
:*Virtual machine vCPUs

 

| Less than 60%
|-
| CPU
| VM
| CPU Ready
| mSec
| The time a virtual machine or other process waits in the queue in a ready-to-run state before it can be scheduled on a CPU.
| Less than 150 mSec. If it is greater than 150 mSec doing system failure, you should investigate and understand why the machine is so busy.
|-
| Memory
|
:*ESXi Server
:*VM

 

| Memory Usage (Average)
| Percent
| Memory Usage = Active/ Granted * 100
| Less than 80%
|-
| Memory
|
:*ESXi Server
:*VM

 

| Memory Active (Average)
| KB
| Memory that is actively used or being referenced by the guest OS and its applications. When it exceeds the amound of memory on the host, the server starts swap.
| Less than 80% of the Granted memory
|-
| Memory
|
:*ESXi Server
:*VM

 

| Memory Balloon (Average)
| KB
| ESXi use balloon driver to recover memory from less memory-intensive VMs so it can be used by those with larger active sets of memory.
| Since we do not over commit the memory, this should be 0 or very low. Note: ESXi performs memory ballooning before memory swap.
|-
| Memory
|
:*ESXi Server
:*VM

 

| Memory Swap used (Average)
| KB
| ESXi Server swap usage. Use the disk for RAM swap
| Since we do not over commit the memory, this should be 0 or very low
|-
| Disk
|
:*ESXi Server
:*VM

 

| Disk Usage (Average)
| KBps
| Disk Usage = Disk Read rate + Disk Write rate
| Ensure that your SAN is configured to handle this amount of disk I/O.
|-
| Disk
|
:*ESXi Server vmhba ID
:*VMbha ID

 

| Disk Usage Read rate 
| KBps
| Rate of reading data from the disk
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

 

| Disk Usage Write rate
| KBps
| Rate of writing data to the disk
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

 

| Disk Commands Issued
| Number
| Number of disk commands issued on this disk in the period.
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

 

| Disk Command Aborts
| Number
| Number of disk commands aborted on this disk in the period. Disk command aborts when the disk array is taking too long to respond to the command. (Command timeout)
'''This counter should be zero. A non-zero value indicates storage performance issue.'''

|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

 

| Disk Command Latency
| mSec
| The average amount of time taken for a command from the perspective of a Gust OS. Disk Command Latency = Kernel Command Latency + Physical Device Command Latency.
| '''15ms latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.'''
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

 

| Kernel Disk Command Latency
| mSec
| The average time spent in ESXi Server VMKernel per command
| '''Kernel Command Latency should be very small in comparison to the Physical Device Command Latency, and it should be close to zero.  Kernel Command Latency can be high, or even higher than the Physical Device Command Latency if there is a lot of queuing in the ESXi kernel.'''
|-
| Network
|
:*ESXi Server
:*VM

 

| Network Usage (Average)
| KBps
| Network Usage = Data receive rate + Data transmit rate
| Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.
|-
| Network
|
:*ESXi Server vmnic ID
:*VM vmnic ID

 

| Network Data Receive Rate
| KBps
| Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.
|-
| Network
|
:*ESXi Server vmnic ID
:*VM vmnic ID

 

| Network Data Transmit Rate
| KBps
| The average rate at which data is transmitted on this Ethernet port
| Less than 30% of the available network bandwidth.  For example, it should be less than 300Mps for 1G network.
|}

= System Performance Monitoring Using Windows Perfmon Counters =

You must comply with the best practices described in the [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco Unified Contact Center Enterprise Solution Reference Network Design(SRND)] section System Performance Monitoring, and in Chapter 8 Performance Counters in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ippcenterprise9_0_1/configuration/guide/ICM-CC_Serviceability_Best_Practices_Guide_for_Release_9.0.pdf Serviceability Best Practices Guide for Cisco Unified ICM/Unified CCE & Unified CCH Release 9.0].

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

[[Category:Unified_Contact_Center_Enterprise]]

Talk:Internetworking Terms and Acronyms (ITA) Guide

2012-07-13T03:02:01Z

Jkratky:

When you create a PDF, you get 37 pages only and a fraction of the necessary (and previously available) terms in the ITA. Can you provide better instructions on accessing these?

Hi,
Thanks for your comment! When you create the PDF, all ITA terms from the wiki are in the PDF in the 37 pages. The ITA used to be on Cisco.com years ago and when the content was migrated only the unique terms and definitions were kept. This is primarily because the common terms found on wikipedia were more up-to-date. Hope this helps!

Compatibility Matrix for Unified CCE

2012-06-26T20:32:39Z

Jkratky: Undo revision 46468 by Jkratky (talk)

'''Go to:''' [[:Category:Unified Contact Center Enterprise|'''Category:Unified Contact Center Enterprise''']]

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,255,204); color: green" |
'''Introduction'''

|-
|
If you want to '''ask a question''', '''post a comment''', or '''discuss an issue''' regarding content on this wiki space:

::#Log in.
::#Navigate to the article in question.
::#Click the '''Discussion''' tab at the top of the page.
::#Edit the Discussion page as described above under Editing.
::#To start a different thread under a new subheading on the Discussion page, click the '''+''' tab at the top of the page instead of the Edit tab.

 

|-
|
If you want to '''be notified of changes to this wiki space''':

::#Log in.
::#Click the '''watch''' tab at the top of the page.

 

|-
|
'''Information will be added and updated on a regular basis, with an emphasis on applying, expanding, and clarifying the content. '''

|-
! style="background-color: rgb(255,255,204); color: green" |
'''Navigation'''

|-
| '''The following list contains compatibility information for specific versions of Cisco Unified Contact Center Enterprise (Unified CCE or CCE). Click the required link. For general compatibility information that applies across all versions of CCE, see additional information later in this page.'''
|-
|
 

:*[[Unified CCE Software Compatibility Matrix for 8.5(x)|'''Unified CCE Software Compatibility Matrix for 8.5(x)''']]

:*[[Unified CCE Software Compatibility Matrix for 8.0(x)|'''Unified CCE Software Compatibility Matrix for 8.0(x)''']] 

:*[[Unified CCE Software Compatibility Matrix for ALL 7.x Releases|'''Unified CCE Software Compatibility Matrix for ALL 7.x Releases''']]

 

|}

 

= General Compatibility information for CCE =

The following sections contain compatibility information that applies to all versions of CCE. 

{| cellspacing="1" cellpadding="1" border="1" style="width: 1043px; height: 310px"
|-
! style="background-color: rgb(255,255,204); color: green" | For Information on 
! style="background-color: rgb(255,255,204); color: green" | Scope/Further Reading 
|-
| valign="top" | Unified CCE Compatibility with Service/Maintenance Releases
| valign="top" | Except where specifically noted otherwise (in the tables below), Unified CCE supports all service/maintenance releases for compatible component versions. Cisco recommends that you run the latest available service/maintenance releases for Unified CCE components. For more information on the Unified CCE software maintenance strategy, see the [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_bulletins_list.html Software Release and Support Methodology: ICM/IPCC].
|-
| valign="top" | Component Versions Supported During Upgrade
| valign="top" | This document lists component versions supported for new installs and full upgrades. It does not list component versions that may be temporarily supported during an upgrade period. Consult the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Upgrade Guide for ICM and CTI OS for Cisco Unified Contact Center Enterprise] for your Unified CCE version for a list of any additional component versions supported during upgrade.
|-
| valign="top" | OS and Third-Party Software Compatibility 
| valign="top" | To verify operating system, database, and third-party software (that is, anti-virus, Web browser, remote administration) compatibility, consult the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Hardware & System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted] specific to your Unified CCE version. 
*The [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html Cisco Unified Communications Manager Compatibility Matrix] and related support information. 
*See also the [http://www.cisco.com/en/US/partner/prod/collateral/voicesw/custcosw/ps5694/ps3651/prod_bulletin09186a0080207fb9_ps1844_Products_Bulletin.html Third Pary Support Policy Bulletin ].

|-
| valign="top" | Unified CCE Component End of Life Notices 
| valign="top" | Find out when a Cisco product has reached its [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_eol_notices_list.html End of Life] and what product upgrade and substitution options.
Because this guide lists component versions until they reach last-date-of-support (the final stage in the end-of-life process) some of the component versions listed herein may have reached end-of-sale or end-of-software-maintenance-release.

|}

 

== General Compatibility Notes and Limitations ==

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" style="background-color: rgb(255,255,204); color: green" | Component
! scope="col" style="background-color: rgb(255,255,204); color: green" | Notes
|-
| valign="top" | Phones
| valign="top" | The following general limitations pertain to IP phones used with Unified CCE Enterprise deployments:
*Third-party SIP phones are not supported as contact center agent phones. The SIP standard does not include the necessary messaging for third-party Call Control (3PCC). Unified CCE relies on CTI capabilities on the SIP phones that third-party phones do not have. As an alternative, you may choose to deploy the Mobile Agent solution to enable Cisco Unified CCE and Contact Center Hosted (CCH) to use any phone as an agent phone. Please consult with your Cisco Sales Engineer for additional detail on this configuration.
*IP Communicator is not supported with Cisco Agent Desktop (CAD) IP Phone Agent.
*See the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html Cisco Unified Communications Manager Compatibility Guide ]for SIP and other phone protocol support.

|-
| valign="top" | System Peripheral Gateway (PG) Deployments
| valign="top" | The following general limitations pertain to Unified CCE deployments that use the System PG:
*E-Mail Manager Option, Web Collaboration Option (both end-of-life products), as well as E-Mail Interaction Manager and Web Interaction Manager (Unified EIM/WIM) are not supported with deployments that use the System PG. For Unified EIM/WIM documentation, see:[http://www.cisco.com/en/US/products/ps7233/tsd_products_support_series_home.html Cisco Unified E-Mail Interaction Manager ]and [http://www.cisco.com/en/US/products/ps7233/tsd_products_support_series_home.html Cisco Unified Web Interaction Manager].

|}

 

= Unified CCE Parent / Child Compatibility =

{| width="644" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" | Release 
! style="background-color: rgb(255,255,204); color: green" | Parent 7.0(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.1(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.2(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.5(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 8.0(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 8.5(x)
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.0(x)'''
| align="center" | Yes 
| align="center" | Yes 
| align="center" | No 
| align="center" | No 
| align="center" | No 
| align="center" | No
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.1(x)'''
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | No 
| align="center" | No 
| align="center" | No 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.2(x)'''
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" |  No 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.5(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 8.0(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 8.5(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|}

 

= Central Controller Backward Compatibility =

{| width="600" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | CentralController
! style="background-color: rgb(255,255,204); color: green" scope="col" | PG
! style="background-color: rgb(255,255,204); color: green" scope="col" | PG + CAD
|-
| align="center" | 8.5
| align="center" | 8.0
| align="center" | 8.0
|-
| align="center" | 8.5
| align="center" | 7.5
| align="center" | 7.5
|-
| align="center" | 8.0
| align="center" | 7.5
| align="center" | 7.5
|-
| align="center" | 8.0
| align="center" | 7.2
| align="center" | 7.2
|-
| align="center" | 8.0
| align="center" | 7.1
| 
|-
| align="center" | 7.5
| align="center" | 7.2
| align="center" | 7.2
|-
| align="center" | 7.5
| align="center" | 7.1
| 
|}

 

'''Note:''' Backward compatible PGs are intended to be supported during the transition when you upgrade the Central Controller and PGs to the same version.

'''Note''': For Outbound deployments, the dialer PG and the Central Controller must be at the same version. 

= VXI Support =

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" style="background-color: rgb(255,255,204); color: green" | Cisco Client Type
! scope="col" style="background-color: rgb(255,255,204); color: green" | Version
! scope="col" style="background-color: rgb(255,255,204); color: green" | Virtual Desktop Infrastructure
! scope="col" style="background-color: rgb(255,255,204); color: green" | OS Compatibility
! scope="col" style="background-color: rgb(255,255,204); color: green" | Cisco VXI Clients
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(1)
| valign="top" | VMWare View 3.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Unsupported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - N/A VXC 2200 - N/A VXC 2111 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2211 - Supported
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(1)
| valign="top" | Citrix XenDesktop 5.0 or 6.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Unsupported Win XP 32 Bit - Supported
| valign="top" | VXC 2100 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2200 - Supported VXC 2111 - N/A VXC 2211 - N/A
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.5(2)
| valign="top" | VMWare View 3.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Supported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - N/A VXC 2200 - N/A VXC 2111 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2211 - Supported
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.5(2)
| valign="top" | Citrix XenDesktop 5.0 or 6.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Supported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2200 - Supported VXC 2111 - N/A VXC 2211 - N/A
|-
| valign="top" | Cisco Agent Desktop (CAD)
| valign="top" | All
| valign="top" | Not Supported
| valign="top" | Not Supported
| valign="top" | Not Supported
|}

 

= Application Virtualization =

Windows Server 2008 R2 (SP1)

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Cisco Client Version
! style="background-color: rgb(255,255,204); color: green" scope="col" | Version
! style="background-color: rgb(255,255,204); color: green" scope="col" | Citrix/XenApp
! style="background-color: rgb(255,255,204); color: green" scope="col" | Remote Desktop Services platform
|-
| valign="top" | CTI-OS Clients (All CILs) 
| valign="top" | 8.5(3) and up 
| valign="top" | XenApp 6.0 
| valign="top" | Windows Server 2008 R2 (SP1) 
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(x)
| valign="top" | XenApp 5.0
| valign="top" | Windows Server 2008 R2 (SP1) 
|}

'''Note:'''

*UCM Silent Monitoring is the only type of Silent Monitoring that is supported with VXI/VDI.
*Desktop solutions are supported on PC-like devices only that utilize a keyboard and mouse (no tablets or mobile devices supported at this time).
*For information about CAD wih thin client and virtual desktop environments, see the Integrating CAD with Thin Client and Virtual Desktop Environments document.

 

= Siebel Compatibility =

{{note| The Siebel Driver and CTIOS Server versions should be the same.}}

 

{| width="298" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" | Cisco Siebel Driver 
! style="background-color: rgb(255,255,204); color: green" | Siebel Release 
|-
| align="center" | 8.5(x)
| align="center" | 8.1(x)
|-
| align="center" | 8.0(x)
| align="center" | 8.1(x)
|-
| align="center" | 7.5(x)
| align="center" | 8.1(x)
|-
| align="center" | 8.5(x)
| align="center" | 8.0(x)
|-
| align="center" | 8.0(x)
| align="center" | 8.0(x)
|-
| align="center" | 7.5(x)
| align="center" | 8.0(x)
|-
| align="center" | 7.5(10)
| align="center" | 7.7(x)
|-
| align="center" | 7.2(x)
| align="center" | 7.8(x)
|-
| align="center" | 7.1(x)
| align="center" | 7.8(x)
|-
| align="center" | 7.0(x)
| align="center" | 7.8(x)
|-
| align="center" | 6.0(x)
| align="center" | 7.7(x)
|}

 

= ICM-to-ICM Gateway Requirements =

 The following are system requirements for ICM-to-ICM Gateway.

*Both Client ICM and Server ICM must be supported releases of Unified ICME, and must bewithin one major version. If two connected ICMs are running with different releases ofUnified ICME, only the ICM-to-ICM Gateway features supported by the lowest release areavailable.
*Refer to the ICM-to-ICM Gateway Client and Server Release Requirements table below for additional information.

'''Note:''' A supported release includes “extended support releases”. For example, as of June2008, 7.1 (5) and 7.2(7) are considered as “extended support releases” that are within a minorversion of each other.

*An ICM communication network configuration that can support ICM-to-ICM Gateway. TheSignaling Access Network (SAN)/Public network is strongly recommended.

'''Note:''' Refer to the Pre-installation Planning Guide for Cisco Unified ICM Enterprise andHosted for information about the Signaling Access Network and ICM communicationsnetwork configurations. 

== ICM-to-ICM Gateway Client and Server Release Requirements ==

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" style="background-color: rgb(255,255,204); color: green" | Client/Server 1
! scope="col" style="background-color: rgb(255,255,204); color: green" | Client/Server 2
! scope="col" style="background-color: rgb(255,255,204); color: green" | Comments
|-
| valign="top" | 6.0
| valign="top" | 7.0, 7.1, 7.2
| valign="top" | ICM 6.0 has reached End of Life and End of Support. ICM6.0 is mentioned here only to provide the available upgradepaths.
|-
| valign="top" | 7.0, 7.1, 7.2
| valign="top" | 7.5
| valign="top" | ICM 7.0, 7.1 and 7.2 are End of Life and End of Support.They are mentioned here only to provide the available upgradepaths.
|-
| valign="top" | 7.5, 8.0
| valign="top" | 7.5, 8.0
| valign="top" | UCCE 8.0(1) is a major release.
|}

 

 

----

----

 

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,255,204); color: green" | '''Back to:''' [[:Category:Unified Contact Center Enterprise|Category:Unified Contact Center Enterprise]]
|}

 

[[Category:Unified_Contact_Center_Enterprise]]

Compatibility Matrix for Unified CCE

2012-06-26T20:31:51Z

Jkratky: Undo revision 46470 by Jkratky (talk)

'''Go to:''' [[Guidelines to Edit the Compatibility Matrix for Unified CCE|'''Guidelines to Edit the Compatibility Matrix for Unified CCE''']]

'''Go to:''' [[:Category:Unified Contact Center Enterprise|'''Category:Unified Contact Center Enterprise''']]

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,255,204); color: green" |
'''Introduction'''

|-
|
If you want to '''ask a question''', '''post a comment''', or '''discuss an issue''' regarding content on this wiki space:

::#Log in.
::#Navigate to the article in question.
::#Click the '''Discussion''' tab at the top of the page.
::#Edit the Discussion page as described above under Editing.
::#To start a different thread under a new subheading on the Discussion page, click the '''+''' tab at the top of the page instead of the Edit tab.

 

|-
|
If you want to '''be notified of changes to this wiki space''':

::#Log in.
::#Click the '''watch''' tab at the top of the page.

 

|-
|
'''Information will be added and updated on a regular basis, with an emphasis on applying, expanding, and clarifying the content. '''

|-
! style="background-color: rgb(255,255,204); color: green" |
'''Navigation'''

|-
| '''The following list contains compatibility information for specific versions of Cisco Unified Contact Center Enterprise (Unified CCE or CCE). Click the required link. For general compatibility information that applies across all versions of CCE, see additional information later in this page.'''
|-
|
 

:*[[Unified CCE Software Compatibility Matrix for 9.0(x)|'''Unified CCE Software Compatibility Matrix for 9.0(x)''']]

:*[[Unified CCE Software Compatibility Matrix for 8.5(x)|'''Unified CCE Software Compatibility Matrix for 8.5(x)''']]

:*[[Unified CCE Software Compatibility Matrix for 8.0(x)|'''Unified CCE Software Compatibility Matrix for 8.0(x)''']] 

:*[[Unified CCE Software Compatibility Matrix for ALL 7.x Releases|'''Unified CCE Software Compatibility Matrix for ALL 7.x Releases''']]

 

|}

 

= General Compatibility information for CCE =

The following sections contain compatibility information that applies to all versions of CCE. 

{| cellspacing="1" cellpadding="1" border="1" style="width: 1043px; height: 310px"
|-
! style="background-color: rgb(255,255,204); color: green" | For Information on 
! style="background-color: rgb(255,255,204); color: green" | Scope/Further Reading 
|-
| valign="top" | Unified CCE Compatibility with Service/Maintenance Releases
| valign="top" | Except where specifically noted otherwise (in the tables below), Unified CCE supports all service/maintenance releases for compatible component versions. Cisco recommends that you run the latest available service/maintenance releases for Unified CCE components. For more information on the Unified CCE software maintenance strategy, see the [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_bulletins_list.html Software Release and Support Methodology: ICM/IPCC].
|-
| valign="top" | Component Versions Supported During Upgrade
| valign="top" | This document lists component versions supported for new installs and full upgrades. It does not list component versions that may be temporarily supported during an upgrade period. Consult the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Upgrade Guide for ICM and CTI OS for Cisco Unified Contact Center Enterprise] for your Unified CCE version for a list of any additional component versions supported during upgrade.
|-
| valign="top" | OS and Third-Party Software Compatibility 
| valign="top" | To verify operating system, database, and third-party software (that is, anti-virus, Web browser, remote administration) compatibility, consult the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Hardware & System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted] specific to your Unified CCE version. 
*The [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html Cisco Unified Communications Manager Compatibility Matrix] and related support information. 
*See also the [http://www.cisco.com/en/US/partner/prod/collateral/voicesw/custcosw/ps5694/ps3651/prod_bulletin09186a0080207fb9_ps1844_Products_Bulletin.html Third Pary Support Policy Bulletin ].

|-
| valign="top" | Unified CCE Component End of Life Notices 
| valign="top" | Find out when a Cisco product has reached its [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_eol_notices_list.html End of Life] and what product upgrade and substitution options.
Because this guide lists component versions until they reach last-date-of-support (the final stage in the end-of-life process) some of the component versions listed herein may have reached end-of-sale or end-of-software-maintenance-release.

|}

 

== General Compatibility Notes and Limitations ==

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Component
! style="background-color: rgb(255,255,204); color: green" scope="col" | Notes
|-
| valign="top" | Phones
| valign="top" | The following general limitations pertain to IP phones used with Unified CCE Enterprise deployments:
*Third-party SIP phones are not supported as contact center agent phones. The SIP standard does not include the necessary messaging for third-party Call Control (3PCC). Unified CCE relies on CTI capabilities on the SIP phones that third-party phones do not have. As an alternative, you may choose to deploy the Mobile Agent solution to enable Cisco Unified CCE and Contact Center Hosted (CCH) to use any phone as an agent phone. Please consult with your Cisco Sales Engineer for additional detail on this configuration.
*IP Communicator is not supported with Cisco Agent Desktop (CAD) IP Phone Agent.
*See the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html Cisco Unified Communications Manager Compatibility Guide ]for SIP and other phone protocol support.

|-
| valign="top" | System Peripheral Gateway (PG) Deployments
| valign="top" | The following general limitations pertain to Unified CCE deployments that use the System PG:
*E-Mail Manager Option, Web Collaboration Option (both end-of-life products), as well as E-Mail Interaction Manager and Web Interaction Manager (Unified EIM/WIM) are not supported with deployments that use the System PG. For Unified EIM/WIM documentation, see:[http://www.cisco.com/en/US/products/ps7233/tsd_products_support_series_home.html Cisco Unified E-Mail Interaction Manager ]and [http://www.cisco.com/en/US/products/ps7233/tsd_products_support_series_home.html Cisco Unified Web Interaction Manager].

|}

 

= Unified CCE Parent / Child Compatibility =

{| width="644" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" | Release 
! style="background-color: rgb(255,255,204); color: green" | Parent 7.0(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.1(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.2(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.5(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 8.0(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 8.5(x)
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.0(x)'''
| align="center" | Yes 
| align="center" | Yes 
| align="center" | No 
| align="center" | No 
| align="center" | No 
| align="center" | No
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.1(x)'''
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | No 
| align="center" | No 
| align="center" | No 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.2(x)'''
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" |  No 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.5(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 8.0(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 8.5(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|}

 

= Central Controller Backward Compatibility =

{| width="600" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | CentralController
! style="background-color: rgb(255,255,204); color: green" scope="col" | PG
! style="background-color: rgb(255,255,204); color: green" scope="col" | PG + CAD
|-
| align="center" | 8.5
| align="center" | 8.0
| align="center" | 8.0
|-
| align="center" | 8.5
| align="center" | 7.5
| align="center" | 7.5
|-
| align="center" | 8.0
| align="center" | 7.5
| align="center" | 7.5
|-
| align="center" | 8.0
| align="center" | 7.2
| align="center" | 7.2
|-
| align="center" | 8.0
| align="center" | 7.1
| 
|-
| align="center" | 7.5
| align="center" | 7.2
| align="center" | 7.2
|-
| align="center" | 7.5
| align="center" | 7.1
| 
|}

 

'''Note:''' Backward compatible PGs are intended to be supported during the transition when you upgrade the Central Controller and PGs to the same version.

'''Note: '''For Outbound deployments, the dialer PG and the Central Controller must be at the same version.

= VDI & Cisco VXI Support =

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Cisco Client Type
! style="background-color: rgb(255,255,204); color: green" scope="col" | Version
! style="background-color: rgb(255,255,204); color: green" scope="col" | Virtual Desktop Infrastructure
! style="background-color: rgb(255,255,204); color: green" scope="col" | OS Compatibility
! style="background-color: rgb(255,255,204); color: green" scope="col" | Cisco VXI Clients
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(1)
| valign="top" | VMWare View 3.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Unsupported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - N/A VXC 2200 - N/A VXC 2111 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2211 - Supported
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(1)
| valign="top" | Citrix XenDesktop 5.0 or 6.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Unsupported Win XP 32 Bit - Supported
| valign="top" | VXC 2100 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2200 - Supported VXC 2111 - N/A VXC 2211 - N/A
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.5(x), 9.0
| valign="top" | VMWare View 4.6
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Supported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - N/A VXC 2200 - N/A VXC 2111 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2211 - Supported
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.5(x), 9.0
| valign="top" | Citrix XenDesktop 5.0, 5.5 or 6.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Supported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2200 - Supported VXC 2111 - N/A VXC 2211 - N/A
|-
| valign="top" | Cisco Agent Desktop (CAD)
| valign="top" | All
| valign="top" | Not Supported
| valign="top" | Not Supported
| valign="top" | Not Supported
|}

 

= Application Virtualization =

Windows Server 2008 R2 (SP1)

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" style="background-color: rgb(255,255,204); color: green" | Cisco Client Version
! scope="col" style="background-color: rgb(255,255,204); color: green" | Version
! scope="col" style="background-color: rgb(255,255,204); color: green" | Citrix/XenApp
! scope="col" style="background-color: rgb(255,255,204); color: green" | Remote Desktop Services platform
|-
| valign="top" | CTI-OS Clients (All CILs) 
| valign="top" | 8.5(3) and up 
| valign="top" | XenApp 6.0 
| valign="top" | Windows Server 2008 R2 (SP1) 
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 7.5(9), 7.5(10), 8.0(1), or 8.5(x)
| valign="top" | XenApp 5.0
| valign="top" | Windows Server 2008 R2 (SP1) 
|}

'''Note:'''

*UCM Silent Monitoring is the only type of Silent Monitoring that is supported with VXI/VDI.
*Desktop solutions are supported on PC-like devices only that utilize a keyboard and mouse (no tablets or mobile devices supported at this time).
*The customer is not required to use Cisco VXI endpoints in a VDI solution. The customer can use any VDI endpoint that supports the specific Citrix or VMWare VDI solution versions supported by Cisco. The customer is responsible for ensuring that bandwidth and any other deployment considerations ensure that the solution can meet the performance and timing requirements of CTI-OS.
*For information about CAD wih thin client and virtual desktop environments, see the Integrating CAD with Thin Client and Virtual Desktop Environments document.

 

= Siebel Compatibility =

{{note| The Siebel Driver and CTIOS Server versions should be the same.}}

 

{| width="298" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" | Cisco Siebel Driver 
! style="background-color: rgb(255,255,204); color: green" | Siebel Release 
|-
| align="center" | 8.5(x)
| align="center" | 8.0(x)
|-
| align="center" | 8.0(x)
| align="center" | 8.0(x)
|-
| align="center" | 7.5(x)
| align="center" | 8.0(x)
|-
| align="center" | 7.5(10)
| align="center" | 7.7(x)
|-
| align="center" | 7.2(x)
| align="center" | 7.8(x)
|-
| align="center" | 7.1(x)
| align="center" | 7.8(x)
|-
| align="center" | 7.0(x)
| align="center" | 7.8(x)
|-
| align="center" | 6.0(x)
| align="center" | 7.7(x)
|}

 

= ICM-to-ICM Gateway Requirements =

 The following are system requirements for ICM-to-ICM Gateway.

*Both Client ICM and Server ICM must be supported releases of Unified ICME, and must bewithin one major version. If two connected ICMs are running with different releases ofUnified ICME, only the ICM-to-ICM Gateway features supported by the lowest release areavailable.
*Refer to the ICM-to-ICM Gateway Client and Server Release Requirements table below for additional information.

'''Note:''' A supported release includes “extended support releases”. For example, as of June2008, 7.1 (5) and 7.2(7) are considered as “extended support releases” that are within a minorversion of each other.

*An ICM communication network configuration that can support ICM-to-ICM Gateway. TheSignaling Access Network (SAN)/Public network is strongly recommended.

'''Note:''' Refer to the Pre-installation Planning Guide for Cisco Unified ICM Enterprise andHosted for information about the Signaling Access Network and ICM communicationsnetwork configurations. 

== ICM-to-ICM Gateway Client and Server Release Requirements ==

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Client/Server 1
! style="background-color: rgb(255,255,204); color: green" scope="col" | Client/Server 2
! style="background-color: rgb(255,255,204); color: green" scope="col" | Comments
|-
| valign="top" | 6.0
| valign="top" | 7.0, 7.1, 7.2
| valign="top" | ICM 6.0 has reached End of Life and End of Support. ICM6.0 is mentioned here only to provide the available upgradepaths.
|-
| valign="top" | 7.0, 7.1, 7.2
| valign="top" | 7.5
| valign="top" | ICM 7.0, 7.1 and 7.2 are End of Life and End of Support.They are mentioned here only to provide the available upgradepaths.
|-
| valign="top" | 7.5, 8.0
| valign="top" | 7.5, 8.0
| valign="top" | UCCE 8.0(1) is a major release.
|-
| valign="top" |
| valign="top" |
| valign="top" |
|}

 

 

----

----

 

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,255,204); color: green" | '''Back to:''' [[:Category:Unified Contact Center Enterprise|Category:Unified Contact Center Enterprise]]
|}

 

[[Category:Unified_Contact_Center_Enterprise]]

Compatibility Matrix for Unified CCE

2012-06-26T20:30:13Z

Jkratky:

'''Go to:''' [[Guidelines to Edit the Compatibility Matrix for Unified CCE|'''Guidelines to Edit the Compatibility Matrix for Unified CCE''']]

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,255,204); color: green" |
'''Introduction'''

|-
|
If you want to '''ask a question''', '''post a comment''', or '''discuss an issue''' regarding content on this wiki space:

::#Log in.
::#Navigate to the article in question.
::#Click the '''Discussion''' tab at the top of the page.
::#Edit the Discussion page as described above under Editing.
::#To start a different thread under a new subheading on the Discussion page, click the '''+''' tab at the top of the page instead of the Edit tab.

 

|-
|
If you want to '''be notified of changes to this wiki space''':

::#Log in.
::#Click the '''watch''' tab at the top of the page.

 

|-
|
'''Information will be added and updated on a regular basis, with an emphasis on applying, expanding, and clarifying the content. '''

|-
! style="background-color: rgb(255,255,204); color: green" |
'''Navigation'''

|-
| '''The following list contains compatibility information for specific versions of Cisco Unified Contact Center Enterprise (Unified CCE or CCE). Click the required link. For general compatibility information that applies across all versions of CCE, see additional information later in this page.'''
|-
|
 

:*[[Unified CCE Software Compatibility Matrix for 9.0(x)|'''Unified CCE Software Compatibility Matrix for 9.0(x)''']]

:*[[Unified CCE Software Compatibility Matrix for 8.5(x)|'''Unified CCE Software Compatibility Matrix for 8.5(x)''']]

:*[[Unified CCE Software Compatibility Matrix for 8.0(x)|'''Unified CCE Software Compatibility Matrix for 8.0(x)''']] 

:*[[Unified CCE Software Compatibility Matrix for ALL 7.x Releases|'''Unified CCE Software Compatibility Matrix for ALL 7.x Releases''']]

 

|}

 

= General Compatibility information for CCE =

The following sections contain compatibility information that applies to all versions of CCE. 

{| cellspacing="1" cellpadding="1" border="1" style="width: 1043px; height: 310px"
|-
! style="background-color: rgb(255,255,204); color: green" | For Information on 
! style="background-color: rgb(255,255,204); color: green" | Scope/Further Reading 
|-
| valign="top" | Unified CCE Compatibility with Service/Maintenance Releases
| valign="top" | Except where specifically noted otherwise (in the tables below), Unified CCE supports all service/maintenance releases for compatible component versions. Cisco recommends that you run the latest available service/maintenance releases for Unified CCE components. For more information on the Unified CCE software maintenance strategy, see the [http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1844/prod_bulletins_list.html Software Release and Support Methodology: ICM/IPCC].
|-
| valign="top" | Component Versions Supported During Upgrade
| valign="top" | This document lists component versions supported for new installs and full upgrades. It does not list component versions that may be temporarily supported during an upgrade period. Consult the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Upgrade Guide for ICM and CTI OS for Cisco Unified Contact Center Enterprise] for your Unified CCE version for a list of any additional component versions supported during upgrade.
|-
| valign="top" | OS and Third-Party Software Compatibility 
| valign="top" | To verify operating system, database, and third-party software (that is, anti-virus, Web browser, remote administration) compatibility, consult the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Hardware & System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted] specific to your Unified CCE version. 
*The [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html Cisco Unified Communications Manager Compatibility Matrix] and related support information. 
*See also the [http://www.cisco.com/en/US/partner/prod/collateral/voicesw/custcosw/ps5694/ps3651/prod_bulletin09186a0080207fb9_ps1844_Products_Bulletin.html Third Pary Support Policy Bulletin ].

|-
| valign="top" | Unified CCE Component End of Life Notices 
| valign="top" | Find out when a Cisco product has reached its [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_eol_notices_list.html End of Life] and what product upgrade and substitution options.
Because this guide lists component versions until they reach last-date-of-support (the final stage in the end-of-life process) some of the component versions listed herein may have reached end-of-sale or end-of-software-maintenance-release.

|}

 

== General Compatibility Notes and Limitations ==

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Component
! style="background-color: rgb(255,255,204); color: green" scope="col" | Notes
|-
| valign="top" | Phones
| valign="top" | The following general limitations pertain to IP phones used with Unified CCE Enterprise deployments:
*Third-party SIP phones are not supported as contact center agent phones. The SIP standard does not include the necessary messaging for third-party Call Control (3PCC). Unified CCE relies on CTI capabilities on the SIP phones that third-party phones do not have. As an alternative, you may choose to deploy the Mobile Agent solution to enable Cisco Unified CCE and Contact Center Hosted (CCH) to use any phone as an agent phone. Please consult with your Cisco Sales Engineer for additional detail on this configuration.
*IP Communicator is not supported with Cisco Agent Desktop (CAD) IP Phone Agent.
*See the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html Cisco Unified Communications Manager Compatibility Guide ]for SIP and other phone protocol support.

|-
| valign="top" | System Peripheral Gateway (PG) Deployments
| valign="top" | The following general limitations pertain to Unified CCE deployments that use the System PG:
*E-Mail Manager Option, Web Collaboration Option (both end-of-life products), as well as E-Mail Interaction Manager and Web Interaction Manager (Unified EIM/WIM) are not supported with deployments that use the System PG. For Unified EIM/WIM documentation, see:[http://www.cisco.com/en/US/products/ps7233/tsd_products_support_series_home.html Cisco Unified E-Mail Interaction Manager ]and [http://www.cisco.com/en/US/products/ps7233/tsd_products_support_series_home.html Cisco Unified Web Interaction Manager].

|}

 

= Unified CCE Parent / Child Compatibility =

{| width="644" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" | Release 
! style="background-color: rgb(255,255,204); color: green" | Parent 7.0(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.1(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.2(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 7.5(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 8.0(x)
! style="background-color: rgb(255,255,204); color: green" | Parent 8.5(x)
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.0(x)'''
| align="center" | Yes 
| align="center" | Yes 
| align="center" | No 
| align="center" | No 
| align="center" | No 
| align="center" | No
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.1(x)'''
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | No 
| align="center" | No 
| align="center" | No 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.2(x)'''
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" |  No 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 7.5(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 8.0(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|-
! style="background-color: rgb(255,255,204); color: green" | '''Child 8.5(x)'''
| align="center" | No 
| align="center" | No 
| align="center" | No 
| align="center" | Yes 
| align="center" | Yes 
| align="center" | Yes 
|}

 

= Central Controller Backward Compatibility =

{| width="600" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | CentralController
! style="background-color: rgb(255,255,204); color: green" scope="col" | PG
! style="background-color: rgb(255,255,204); color: green" scope="col" | PG + CAD
|-
| align="center" | 8.5
| align="center" | 8.0
| align="center" | 8.0
|-
| align="center" | 8.5
| align="center" | 7.5
| align="center" | 7.5
|-
| align="center" | 8.0
| align="center" | 7.5
| align="center" | 7.5
|-
| align="center" | 8.0
| align="center" | 7.2
| align="center" | 7.2
|-
| align="center" | 8.0
| align="center" | 7.1
| 
|-
| align="center" | 7.5
| align="center" | 7.2
| align="center" | 7.2
|-
| align="center" | 7.5
| align="center" | 7.1
| 
|}

 

'''Note:''' Backward compatible PGs are intended to be supported during the transition when you upgrade the Central Controller and PGs to the same version.

'''Note: '''For Outbound deployments, the dialer PG and the Central Controller must be at the same version.

= VDI & Cisco VXI Support =

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Cisco Client Type
! style="background-color: rgb(255,255,204); color: green" scope="col" | Version
! style="background-color: rgb(255,255,204); color: green" scope="col" | Virtual Desktop Infrastructure
! style="background-color: rgb(255,255,204); color: green" scope="col" | OS Compatibility
! style="background-color: rgb(255,255,204); color: green" scope="col" | Cisco VXI Clients
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(1)
| valign="top" | VMWare View 3.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Unsupported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - N/A VXC 2200 - N/A VXC 2111 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2211 - Supported
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.0(1) or 8.5(1)
| valign="top" | Citrix XenDesktop 5.0 or 6.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Unsupported Win XP 32 Bit - Supported
| valign="top" | VXC 2100 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2200 - Supported VXC 2111 - N/A VXC 2211 - N/A
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.5(x), 9.0
| valign="top" | VMWare View 4.6
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Supported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - N/A VXC 2200 - N/A VXC 2111 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2211 - Supported
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 8.5(x), 9.0
| valign="top" | Citrix XenDesktop 5.0, 5.5 or 6.0
| valign="top" | Windows 7 32 bit - Supported Windows 7 WoW64 - Supported Windows XP 32 bit - Supported
| valign="top" | VXC 2100 - Supported with Cisco Unified IP Phone 8961, 9951, and 9971 VXC 2200 - Supported VXC 2111 - N/A VXC 2211 - N/A
|-
| valign="top" | Cisco Agent Desktop (CAD)
| valign="top" | All
| valign="top" | Not Supported
| valign="top" | Not Supported
| valign="top" | Not Supported
|}

 

= Application Virtualization =

Windows Server 2008 R2 (SP1)

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" style="background-color: rgb(255,255,204); color: green" | Cisco Client Version
! scope="col" style="background-color: rgb(255,255,204); color: green" | Version
! scope="col" style="background-color: rgb(255,255,204); color: green" | Citrix/XenApp
! scope="col" style="background-color: rgb(255,255,204); color: green" | Remote Desktop Services platform
|-
| valign="top" | CTI-OS Clients (All CILs) 
| valign="top" | 8.5(3) and up 
| valign="top" | XenApp 6.0 
| valign="top" | Windows Server 2008 R2 (SP1) 
|-
| valign="top" | CTI-OS Clients (All CILs)
| valign="top" | 7.5(9), 7.5(10), 8.0(1), or 8.5(x)
| valign="top" | XenApp 5.0
| valign="top" | Windows Server 2008 R2 (SP1) 
|}

'''Note:'''

*UCM Silent Monitoring is the only type of Silent Monitoring that is supported with VXI/VDI.
*Desktop solutions are supported on PC-like devices only that utilize a keyboard and mouse (no tablets or mobile devices supported at this time).
*The customer is not required to use Cisco VXI endpoints in a VDI solution. The customer can use any VDI endpoint that supports the specific Citrix or VMWare VDI solution versions supported by Cisco. The customer is responsible for ensuring that bandwidth and any other deployment considerations ensure that the solution can meet the performance and timing requirements of CTI-OS.
*For information about CAD wih thin client and virtual desktop environments, see the Integrating CAD with Thin Client and Virtual Desktop Environments document.

 

= Siebel Compatibility =

{{note| The Siebel Driver and CTIOS Server versions should be the same.}}

 

{| width="298" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" | Cisco Siebel Driver 
! style="background-color: rgb(255,255,204); color: green" | Siebel Release 
|-
| align="center" | 8.5(x)
| align="center" | 8.0(x)
|-
| align="center" | 8.0(x)
| align="center" | 8.0(x)
|-
| align="center" | 7.5(x)
| align="center" | 8.0(x)
|-
| align="center" | 7.5(10)
| align="center" | 7.7(x)
|-
| align="center" | 7.2(x)
| align="center" | 7.8(x)
|-
| align="center" | 7.1(x)
| align="center" | 7.8(x)
|-
| align="center" | 7.0(x)
| align="center" | 7.8(x)
|-
| align="center" | 6.0(x)
| align="center" | 7.7(x)
|}

 

= ICM-to-ICM Gateway Requirements =

 The following are system requirements for ICM-to-ICM Gateway.

*Both Client ICM and Server ICM must be supported releases of Unified ICME, and must bewithin one major version. If two connected ICMs are running with different releases ofUnified ICME, only the ICM-to-ICM Gateway features supported by the lowest release areavailable.
*Refer to the ICM-to-ICM Gateway Client and Server Release Requirements table below for additional information.

'''Note:''' A supported release includes “extended support releases”. For example, as of June2008, 7.1 (5) and 7.2(7) are considered as “extended support releases” that are within a minorversion of each other.

*An ICM communication network configuration that can support ICM-to-ICM Gateway. TheSignaling Access Network (SAN)/Public network is strongly recommended.

'''Note:''' Refer to the Pre-installation Planning Guide for Cisco Unified ICM Enterprise andHosted for information about the Signaling Access Network and ICM communicationsnetwork configurations. 

== ICM-to-ICM Gateway Client and Server Release Requirements ==

{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
! style="background-color: rgb(255,255,204); color: green" scope="col" | Client/Server 1
! style="background-color: rgb(255,255,204); color: green" scope="col" | Client/Server 2
! style="background-color: rgb(255,255,204); color: green" scope="col" | Comments
|-
| valign="top" | 6.0
| valign="top" | 7.0, 7.1, 7.2
| valign="top" | ICM 6.0 has reached End of Life and End of Support. ICM6.0 is mentioned here only to provide the available upgradepaths.
|-
| valign="top" | 7.0, 7.1, 7.2
| valign="top" | 7.5
| valign="top" | ICM 7.0, 7.1 and 7.2 are End of Life and End of Support.They are mentioned here only to provide the available upgradepaths.
|-
| valign="top" | 7.5, 8.0
| valign="top" | 7.5, 8.0
| valign="top" | UCCE 8.0(1) is a major release.
|-
| valign="top" |
| valign="top" |
| valign="top" |
|}

 

 

----

----

 

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,255,204); color: green" | '''Back to:''' [[:Category:Unified Contact Center Enterprise|Category:Unified Contact Center Enterprise]]
|}

 

[[Category:Unified_Contact_Center_Enterprise]]

Compatibility Matrix for Unified CCE

2012-06-26T20:29:56Z

Jkratky: 1 revision

Compatibility Matrix for Unified CCE

2012-06-26T20:28:59Z

Jkratky: /* ICM-to-ICM Gateway Client and Server Release Requirements */

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T12:54:19Z

Jkratky:

Internetworking Technology Handbook

2012-06-20T12:54:00Z

Jkratky: /* Network Caching Technologies */

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.
|}

==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook]] that you can save on your computer and print.

==Internetworking Basics==
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:53:08Z

Jkratky:

Internetworking Technology Handbook

2012-06-20T12:52:49Z

Jkratky:

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.
|}

==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook]] that you can save on your computer and print.

==Internetworking Basics==
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:52:31Z

Jkratky: /* Creating a PDF of the Internetworking Technology Handbook */

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
|}

==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook]] that you can save on your computer and print.

==Internetworking Basics==
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:52:11Z

Jkratky: /* Creating a PDF of the Internetworking Technology Handbook */

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
|}

==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.

==Internetworking Basics==
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:52:01Z

Jkratky: /* Internetworking Basics */

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
|}

===Creating a PDF of the Internetworking Technology Handbook===

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.

==Internetworking Basics==
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:51:22Z

Jkratky: /* Creating a PDF of the Internetworking Technology Handbook */

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
|}

===Creating a PDF of the Internetworking Technology Handbook===

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.

===Internetworking Basics===
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:51:10Z

Jkratky:

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
|}

===Creating a PDF of the Internetworking Technology Handbook===

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook)]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.

===Internetworking Basics===
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:50:32Z

Jkratky:

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.|}
==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook)]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.

===Internetworking Basics===
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:50:16Z

Jkratky: /* Creating a PDF of the Internetworking Technology Handbook */

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Technology Handbook -- Creating a PDF|Create a PDF of the Internetworking Technology Handbook)]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.

===Internetworking Basics===
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:48:35Z

Jkratky:

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Terms and Acronyms (ITA) -- Creating a PDF|Create a PDF of the Internetworking Terms and Acronyms (ITA)]] that you can save on your computer and print.

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.
|}

===Internetworking Basics===
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook

2012-06-20T12:48:12Z

Jkratky:

{{Template:Required Metadata}}
{| align="center" border="1"
|align="left"|Welcome to '''Cisco DocWiki'''. We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to improve Cisco product documentation. Note that you cannot log in to DocWiki with Cisco.com "guest" account credentials. 
See [[DocWiki:Terms_of_use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki. 
Select the "Edit" tab to edit an article or select the "Leave a Comment" tab to submit questions or comments about the article. 

Click [http://www.cisco.com/en/US/products/ps6441/tsd_products_support_series_home.html here] to return to the Cisco IOS documentation on www.cisco.com.
|}

This article provides guidance for understanding internetworking technology. Different components of internetwork and the protocols used are described.
==Creating a PDF of the Internetworking Technology Handbook==

[[Internetworking Terms and Acronyms (ITA) -- Creating a PDF|Create a PDF of the Internetworking Terms and Acronyms (ITA)]] that you can save on your computer and print.

===Internetworking Basics===
An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.

The following articles provide information about internetworking basics:
* [[Internetworking Basics]]
* [[Introduction to LAN Protocols]]
* [[Introduction to WAN Technologies]]
* [[Bridging and Switching Basics]]
* [[Routing Basics]]
* [[Network Management Basics]]
* [[Open System Interconnection Protocols]]

==LAN Technologies ==
A LAN is a high-speed data network that covers a relatively small geographic area. It typically connects workstations, personal computers, printers, servers, and other devices. LANs offer computer users many advantages, including shared access to devices and applications, file exchange between connected users, and communication between users via electronic mail and other applications.

The following articles provide information different LAN technologies:
* [[Ethernet Technologies]]
* [[Token Ring/IEEE 802.5]]

==WAN Technologies==
A WAN is a data communications network that covers a relatively broad geographic area and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.

The following articles provide information about the various protocols and technologies used in WAN environments:
* [[Frame Relay]]
* [[High-Speed Serial Interface]]
* [[Integrated Services Digital Network]]
* [[Point-to-Point Protocol]]
* [[Switched Multimegabit Data Service]]
* [[Synchronous Data Link Control and Derivatives]]
* [[X.25]]
* [[Digital Subscriber Line]]

==Internet Protocols==
The Internet protocols are the world's most popular open-system (nonproprietary) protocol suite because they can be used to communicate across any set of interconnected networks and are equally well suited for LAN and WAN communications. The Internet protocols consist of a suite of communication protocols, of which the two best known are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). The Internet protocol suite not only includes lower-layer protocols (such as TCP and IP), but it also specifies common applications such as electronic mail, terminal emulation, and file transfer. This article provides a broad introduction to specifications that comprise the Internet protocols. Discussions include IP addressing and key upper-layer protocols used in the Internet. Specific routing protocols are addressed individually later in this document.

The following articles provide information about different IOS IP technologies:
* [[Internet Protocols]]
** [[AppleTalk]]
** [[Banyan VINES]]
** [[IBM Systems Network Architecture Protocols]]
** [[DECnet]]
** [[Simple Multicast Routing Protocol]]
* [[Internet Protocol Multicast]]
* [[IPv6]]

== Bridging and Switching==
Bridges and switches are data communication devices that operate principally at Layer 2 of the OSI reference model. As such, they are widely referred to as data link layer devices.
Several kinds of bridging have proven important as internetworking devices. Transparent bridging is found primarily in Ethernet environments, while source-route bridging occurs primarily in Token Ring environments. Translational bridging provides translation between the formats and transit principles of different media types (usually Ethernet and Token Ring). Finally, source-route transparent bridging combines the algorithms of transparent bridging and source-route bridging to enable communication in mixed Ethernet/Token Ring environments.
Today, switching technology has emerged as the evolutionary heir to bridging-based internetworking solutions. Switching implementations now dominate applications in which bridging technologies were implemented in prior network designs. Superior throughput performance, higher port density, lower per-port cost, and greater flexibility have contributed to the emergence of switches as replacement technology for bridges and as complements to routing technology.

The following articles provide information about the technologies employed in devices loosely referred to as bridges and switches:
* [[Transparent Bridging]]
* [[Mixed-Media Bridging]]
* [[Source-Route Bridging]]
* [[Asynchronous Transfer Mode Switching]]
* [[LAN Switching and VLANs]]
* [[MPLS/Tag Switching]]
* [[Data-Link Switching]]
* [[Tag Switching]]

==Routing==
Routing is the act of moving information across an internetwork from a source to a destination. Along the way, at least one intermediate node typically is encountered. Routing is often contrasted with bridging, which might seem to accomplish precisely the same thing to the casual observer. The primary difference between the two is that bridging occurs at Layer 2 (the link layer) of the OSI reference model, whereas routing occurs at Layer 3 (the network layer). This distinction provides routing and bridging with different information to use in the process of moving information from source to destination, so the two functions accomplish their tasks in different ways.

The following articles provide information different routing technologies:
* [[Fiber Distributed Data Interface]]
* [[IBM Systems Network Architecture Routing]]
* [[NetWare Link-Services Protocol]]
* [[Open System Interconnection Routing Protocol]]
* [[Open Shortest Path First]]
* [[Routing Information Protocol]]
* [[Border Gateway Protocol]]
* [[Interior Gateway Routing Protocol]]
* [[Enhanced Interior Gateway Routing Protocol]]
* [[Xerox Network Systems]]

==Network Management==
Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks.

The following articles provide information different network management technologies:
* [[Virtual Private Networks]]
* [[Directory-Enabled Networking]]
* [[Remote Monitoring]]
* [[Simple Network Management Protocol]]

== Voice/Data Integration Technologies==
Voice/data integration is important to network designers of both service providers and enterprise. Service providers are attracted by the lower-cost model-the cost of packet voice is currently estimated to be only 20 to 50 percent of the cost of a traditional circuit-based voice network. Likewise, enterprise network designers are interested in direct cost savings associated with toll-bypass and tandem switching. Both are also interested in so-called "soft savings" associated with reduced maintenance costs and more efficient network control and management. Finally, packet-based voice systems offer access to newly enhanced services such as Unified Messaging and application control. These, in turn, promise to increase the productivity of users and differentiate services.

Integration of voice and data technologies has accelerated rapidly in recent years because of both supply- and demand-side interactions. On the demand side, customers are leveraging investment in network infrastructure to take advantage of integrated applications such as voice applications. On the supply side, vendors have been able to take advantage of breakthroughs in many areas, including standards, technology, and network performance.

The following article provides information about Voice/Data Integration Technologies:
* [[Voice/Data Integration Technologies]]

== Wireless Technologies==
Wireless communication is the transfer of information over a distance without the use of electrical conductors or "wires".[1] The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

It encompasses various types of fixed, mobile, and portable two way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer mice, keyboards and headsets, satellite television and cordless telephones.

The following article provides information about Wireless Technologies:
* [[Wireless Technologies]]

== Cable Access Technologies==
Historically, CATV has been a unidirectional medium designed to carry broadcast analog video channels to the maximum number of customers at the lowest possible cost. CATV was introduced in the 1940s and 1950s and for many decades little changed beyond increasing the number of channels supported. The technology to provide high-margin, two-way services remained elusive to the operator.

The 2000s and the rise of IPTV saw this delivery model change. Today CATV providers utilize IP protocols for two-way data traffic while simultaneously delivering interactive video programing.

The following article provides information about Cable Access Technologies:
* [[Cable Access Technologies]]

== Dial-up Technology==
Dialup is simply the application of the Public Switched Telephone Network (PSTN) to carry data on behalf of the end user. It involves customer premises equipment (CPE) device sending the telephone switch a phone number to direct a connection to. The AS3600, AS5200, AS5300, and AS5800 are all examples of routers that have the capability to run a PRI along with banks of digital modems. The AS2511, on the other hand, is an example of a router that communicates with external modems.

Since the time of Internetworking Technologies Handbook, 2nd edition, the carrier market has continued to grow, and there have been demands for higher modem densities. The answer to this need was a higher degree of interoperation with the telco equipment and the refinement of the digital modem: a modem capable of direct digital access to the PSTN. This has allowed the development of faster CPE modems that take advantage of the clarity of signal that the digital modems enjoy. The fact that the digital modems connecting into the PSTN through a PRI or a BRI can transmit data at more than 53 K using the V.90 communication standard attests to the success of the idea.

The following article provides information about Dial-up Technology:
* [[Dial-up Technology]]

== Security Technologies==
With the rapid growth of interest in the Internet, network security has become a major concern to companies throughout the world. The fact that the information and tools needed to penetrate the security of corporate networks are widely available has increased that concern.

Because of this increased focus on network security, network administrators often spend more effort protecting their networks than on actual network setup and administration. Tools that probe for system vulnerabilities, such as the Security Administrator Tool for Analyzing Networks (SATAN), and some of the newly available scanning and intrusion detection packages and appliances, assist in these efforts, but these tools only point out areas of weakness and may not provide a means to protect networks from all possible attacks. Thus, as a network administrator, you must constantly try to keep abreast of the large number of security issues confronting you in today's world. This article describes many of the security issues that arise when connecting a private network to the Internet.

The following article provides information about Security Technologies:
* [[Security Technologies]]

== Quality of Service Networking==
Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks. This article outlines the features and benefits of the QoS provided by the Cisco IOS QoS.

The following articles provide information about Quality of Service:
* [[Quality of Service Networking]]
* [[Resource Reservation Protocol]]

== Network Caching Technologies==
Although the volume of Web traffic on the Internet is staggering, a large percentage of that traffic is redundant-multiple users at any given site request much of the same content. This means that a significant percentage of the WAN infrastructure carries the identical content (and identical requests for it) day after day. Eliminating a significant amount of recurring telecommunications charges offers an enormous savings opportunity for enterprise and service provider customers.

Web caching performs the local storage of Web content to serve these redundant user requests more quickly, without sending the requests and the resulting content over the WAN.

The following article provides information about Network Caching Technologies:
* [[Network Caching Technologies]]

== IBM Network Management==
IBM network management refers to any architecture used to manage IBM Systems Network Architecture (SNA) networks or Advanced Peer-to-Peer Networking (APPN) networks. IBM network management is part of the IBM Open-Network Architecture (ONA) and is performed centrally by using management platforms such as NetView and others. It is divided into five functions that are similar to the network management functions specified under the Open System Interconnection (OSI) model. This article summarizes the IBM network management functional areas, ONA network management architecture, and management platforms.

The following article provides information about IBM Network Management:
* [[IBM Network Management]]

== Multiservice Access Technologies==
Multiservice networking is emerging as a strategically important issue for enterprise and public service provider infrastructures alike. The proposition of multiservice networking is the combination of all types of communications, all types of data, voice, and video over a single packet-cell-based infrastructure. The benefits of multiservice networking are reduced operational costs, higher performance, greater flexibility, integration and control, and faster new application and service deployment.

The following article provides information about Multiservice Access Technologies:
* [[Multiservice Access Technologies]]

[[Category:IOS Technology Handbook]]

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T12:43:14Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T12:35:28Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T12:33:44Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T12:24:04Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T00:48:30Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T00:48:17Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T00:44:01Z

Jkratky:

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T00:39:25Z

Jkratky:

To return to the Internetworking Technology Handbook, [[Internetworking Technology Handbook|click here]].

The list of topics in the text box below are predefined according to the structure of traditional Cisco documentation. If this list does not meet your requirements, edit the list of topics that you want to include in your customized PDF.

1. Group together your preferred list of topics in the text box below.

2. Select "landscape".

3. Click Create PDF to generate the PDF. {{Template:PDF_Print_Form|ROWS=17|DEFAULT_FILENAME=ITA.pdf|BUTTON_LABEL=Create PDF|DEFAULT_TEXT=Internetworking Technology Handbook
Internetworking Terms and Acronyms (ITA) Guide
Internetworking Terms: ATM Interface Processor (AIP)
Internetworking Terms: ATM Network
Internetworking Terms: ATM Network Interface Card
Internetworking Terms: Address Translation Gateway (ATG)
Internetworking Terms: Airline Product Set (ALPS)
Internetworking Terms: Automated Packet Recognition-Translation (APaRT)
Internetworking Terms: Autonomous Switching
Internetworking Terms: BPX Service Node
Internetworking Terms: Bus Interface Gate Array (BIGA)
Internetworking Terms: Channel Interface Processor (CIP)
Internetworking Terms: Cisco Certified Design Associate (CCDA)
Internetworking Terms: Cisco Certified Internetwork Expert (CCIE)
Internetworking Terms: Cisco Certified Network Associate (CCNA)
Internetworking Terms: Cisco Discovery Protocol
Internetworking Terms: Cisco Encryption Technology (CET)
Internetworking Terms: Cisco Express Forwarding (CEF)
Internetworking Terms: Cisco Extended Bus (CxBus)
Internetworking Terms: Cisco Frame Relay Access Device (Cisco FRAD)
Internetworking Terms: Cisco ISDN User Part (C-ISUP)
Internetworking Terms: Cisco Link Services (CLS)
Internetworking Terms: Cisco Link Services Interface (CLSI)
Internetworking Terms: Cisco MGC Node Manager (CMNM)
Internetworking Terms: Cisco Network Registrar (CNR)
Internetworking Terms: Cisco Networking Services for Active Directory (CNS-AD)
Internetworking Terms: Cisco Optical Network Planner (ONP)
Internetworking Terms: Cisco Service Management (CSM)
Internetworking Terms: Cisco Subscriber Registration Center (CSRC)
Internetworking Terms: Cisco Wavelength Router Manager (Cisco WRM)
Internetworking Terms: Cisco Web Application Framework (CWAF)
Internetworking Terms: Cisco-trunk (private line) Call
Internetworking Terms: CiscoFusion
Internetworking Terms: CiscoView
Internetworking Terms: Class Selector (QoS - CS)
Internetworking Terms: Combinet Packet Protocol (CPP)
Internetworking Terms: Configuration Register
Internetworking Terms: DSPU concentration
Internetworking Terms: Data Movement Processor (DMP)
Internetworking Terms: Data-link Switching Plus (DLSw+)
Internetworking Terms: Diffusing Update Algorithm (DUAL)
Internetworking Terms: Director Response Protocol (DRP)
Internetworking Terms: DistributedDirector
Internetworking Terms: EXEC
Internetworking Terms: Enhanced Interior Gateway Routing Protocol (EIGRP)
Internetworking Terms: Enhanced Monitoring Services
Internetworking Terms: Ethernet Interface Processor (EIP)
Internetworking Terms: Extended Services Processor (ESP)
Internetworking Terms: FDDI Interface Processor (FIP)
Internetworking Terms: Fast Ethernet Interface Processor (FEIP)
Internetworking Terms: Fast Sequenced Transport (FST)
Internetworking Terms: Fast Serial Interface Processor (FSIP)
Internetworking Terms: Fast Switching
Internetworking Terms: Frame Relay access support (FRAS)
Internetworking Terms: Gateway Discovery Protocol (GDP)
Internetworking Terms: Generic Routing Encapsulation (GRE)
Internetworking Terms: HSSI Interface Processor (HIP)
Internetworking Terms: Helper Address
Internetworking Terms: High-Speed Communications Interface (HSCI)
Internetworking Terms: Hot Standby Router Protocol (HSRP)
Internetworking Terms: Inter-Switch Link (ISL)
Internetworking Terms: Interface Processor
Internetworking Terms: Interior Gateway Routing Protocol (IGRP)
Internetworking Terms: Internetworking Operating System (IOS)
Internetworking Terms: MultiChannel Interface Processor (MIP)
Internetworking Terms: Multiservice IOS Channel Aggregation (MICA)
Internetworking Terms: NETscout
Internetworking Terms: Native Client Interface Architecture (NCIA)
Internetworking Terms: NetFlow
Internetworking Terms: Network Management Processor (NMP)
Internetworking Terms: Open Packet Telephony (OPT)
Internetworking Terms: Open Peripheral Interface (OPI)
Internetworking Terms: Peripheral Interface Manager (PIM)
Internetworking Terms: Physical Layer Interface Module (PLIM)
Internetworking Terms: Policing
Internetworking Terms: Process Switching
Internetworking Terms: Proxy polling
Internetworking Terms: QoS Policy Manager (QPM)
Internetworking Terms: Reliable SAP Update Protocol (RSUP)
Internetworking Terms: Route Processor (RP)
Internetworking Terms: Route-Switch Processor (RSP)
Internetworking Terms: SDLC Transport
Internetworking Terms: SDLC broadcast
Internetworking Terms: SDLLC - SDLC Logical Link Control
Internetworking Terms: SMDS Interface Protocol (SIP)
Internetworking Terms: SPNNI connection
Internetworking Terms: Security Posture Assessment (SPA)
Internetworking Terms: Serial Interface Processor (SIP)
Internetworking Terms: Silicon Switch Processor (SSP)
Internetworking Terms: Silicon Switching Engine (SSE)
Internetworking Terms: Switch Processor (SP)
Internetworking Terms: Switched Port Analyzer (SPAN)
Internetworking Terms: THC over X.25
Internetworking Terms: Technical Assistance Center (TAC)
Internetworking Terms: Terminal access controller access control system plus (TACACS+)
Internetworking Terms: Token Ring Interface Processor (TRIP)
Internetworking Terms: Two-Way Simultaneous (TWS)
Internetworking Terms: UniDirectional Link Detection (UDLD)
Internetworking Terms: Versatile Interface Processor (VIP)
Internetworking Terms: Virtual Networking Services
Internetworking Terms: Virtual Switch Controller (VSC)
Internetworking Terms: WorkGroup Director
Internetworking Terms: X.25
Internetworking Terms: break-out break-in (BOBI)
Internetworking Terms: ciscoBus controller
Internetworking Terms: serial tunnel (STUN)
Internetworking Terms: silicon switching
Internetworking Terms: virtual IP }}

Internetworking Technology Handbook -- Creating a PDF

2012-06-20T00:38:17Z

Jkratky: Created page with "To return to the Internetworking Terms and Acronyms (ITA) Guide, click here. The list of topics in the text box below are pre..."

To return to the Internetworking Terms and Acronyms (ITA) Guide, [[Internetworking Terms and Acronyms (ITA) Guide|click here]].

The list of topics in the text box below are predefined according to the structure of traditional Cisco documentation. If this list does not meet your requirements, edit the list of topics that you want to include in your customized PDF.

1. Group together your preferred list of topics in the text box below.

2. Select "landscape".

3. Click Create PDF to generate the PDF. {{Template:PDF_Print_Form|ROWS=17|DEFAULT_FILENAME=ITA.pdf|BUTTON_LABEL=Create PDF|DEFAULT_TEXT=Internetworking Terms and Acronyms (ITA)
Internetworking Terms and Acronyms (ITA) Guide
Internetworking Terms: ATM Interface Processor (AIP)
Internetworking Terms: ATM Network
Internetworking Terms: ATM Network Interface Card
Internetworking Terms: Address Translation Gateway (ATG)
Internetworking Terms: Airline Product Set (ALPS)
Internetworking Terms: Automated Packet Recognition-Translation (APaRT)
Internetworking Terms: Autonomous Switching
Internetworking Terms: BPX Service Node
Internetworking Terms: Bus Interface Gate Array (BIGA)
Internetworking Terms: Channel Interface Processor (CIP)
Internetworking Terms: Cisco Certified Design Associate (CCDA)
Internetworking Terms: Cisco Certified Internetwork Expert (CCIE)
Internetworking Terms: Cisco Certified Network Associate (CCNA)
Internetworking Terms: Cisco Discovery Protocol
Internetworking Terms: Cisco Encryption Technology (CET)
Internetworking Terms: Cisco Express Forwarding (CEF)
Internetworking Terms: Cisco Extended Bus (CxBus)
Internetworking Terms: Cisco Frame Relay Access Device (Cisco FRAD)
Internetworking Terms: Cisco ISDN User Part (C-ISUP)
Internetworking Terms: Cisco Link Services (CLS)
Internetworking Terms: Cisco Link Services Interface (CLSI)
Internetworking Terms: Cisco MGC Node Manager (CMNM)
Internetworking Terms: Cisco Network Registrar (CNR)
Internetworking Terms: Cisco Networking Services for Active Directory (CNS-AD)
Internetworking Terms: Cisco Optical Network Planner (ONP)
Internetworking Terms: Cisco Service Management (CSM)
Internetworking Terms: Cisco Subscriber Registration Center (CSRC)
Internetworking Terms: Cisco Wavelength Router Manager (Cisco WRM)
Internetworking Terms: Cisco Web Application Framework (CWAF)
Internetworking Terms: Cisco-trunk (private line) Call
Internetworking Terms: CiscoFusion
Internetworking Terms: CiscoView
Internetworking Terms: Class Selector (QoS - CS)
Internetworking Terms: Combinet Packet Protocol (CPP)
Internetworking Terms: Configuration Register
Internetworking Terms: DSPU concentration
Internetworking Terms: Data Movement Processor (DMP)
Internetworking Terms: Data-link Switching Plus (DLSw+)
Internetworking Terms: Diffusing Update Algorithm (DUAL)
Internetworking Terms: Director Response Protocol (DRP)
Internetworking Terms: DistributedDirector
Internetworking Terms: EXEC
Internetworking Terms: Enhanced Interior Gateway Routing Protocol (EIGRP)
Internetworking Terms: Enhanced Monitoring Services
Internetworking Terms: Ethernet Interface Processor (EIP)
Internetworking Terms: Extended Services Processor (ESP)
Internetworking Terms: FDDI Interface Processor (FIP)
Internetworking Terms: Fast Ethernet Interface Processor (FEIP)
Internetworking Terms: Fast Sequenced Transport (FST)
Internetworking Terms: Fast Serial Interface Processor (FSIP)
Internetworking Terms: Fast Switching
Internetworking Terms: Frame Relay access support (FRAS)
Internetworking Terms: Gateway Discovery Protocol (GDP)
Internetworking Terms: Generic Routing Encapsulation (GRE)
Internetworking Terms: HSSI Interface Processor (HIP)
Internetworking Terms: Helper Address
Internetworking Terms: High-Speed Communications Interface (HSCI)
Internetworking Terms: Hot Standby Router Protocol (HSRP)
Internetworking Terms: Inter-Switch Link (ISL)
Internetworking Terms: Interface Processor
Internetworking Terms: Interior Gateway Routing Protocol (IGRP)
Internetworking Terms: Internetworking Operating System (IOS)
Internetworking Terms: MultiChannel Interface Processor (MIP)
Internetworking Terms: Multiservice IOS Channel Aggregation (MICA)
Internetworking Terms: NETscout
Internetworking Terms: Native Client Interface Architecture (NCIA)
Internetworking Terms: NetFlow
Internetworking Terms: Network Management Processor (NMP)
Internetworking Terms: Open Packet Telephony (OPT)
Internetworking Terms: Open Peripheral Interface (OPI)
Internetworking Terms: Peripheral Interface Manager (PIM)
Internetworking Terms: Physical Layer Interface Module (PLIM)
Internetworking Terms: Policing
Internetworking Terms: Process Switching
Internetworking Terms: Proxy polling
Internetworking Terms: QoS Policy Manager (QPM)
Internetworking Terms: Reliable SAP Update Protocol (RSUP)
Internetworking Terms: Route Processor (RP)
Internetworking Terms: Route-Switch Processor (RSP)
Internetworking Terms: SDLC Transport
Internetworking Terms: SDLC broadcast
Internetworking Terms: SDLLC - SDLC Logical Link Control
Internetworking Terms: SMDS Interface Protocol (SIP)
Internetworking Terms: SPNNI connection
Internetworking Terms: Security Posture Assessment (SPA)
Internetworking Terms: Serial Interface Processor (SIP)
Internetworking Terms: Silicon Switch Processor (SSP)
Internetworking Terms: Silicon Switching Engine (SSE)
Internetworking Terms: Switch Processor (SP)
Internetworking Terms: Switched Port Analyzer (SPAN)
Internetworking Terms: THC over X.25
Internetworking Terms: Technical Assistance Center (TAC)
Internetworking Terms: Terminal access controller access control system plus (TACACS+)
Internetworking Terms: Token Ring Interface Processor (TRIP)
Internetworking Terms: Two-Way Simultaneous (TWS)
Internetworking Terms: UniDirectional Link Detection (UDLD)
Internetworking Terms: Versatile Interface Processor (VIP)
Internetworking Terms: Virtual Networking Services
Internetworking Terms: Virtual Switch Controller (VSC)
Internetworking Terms: WorkGroup Director
Internetworking Terms: X.25
Internetworking Terms: break-out break-in (BOBI)
Internetworking Terms: ciscoBus controller
Internetworking Terms: serial tunnel (STUN)
Internetworking Terms: silicon switching
Internetworking Terms: virtual IP }}

Category:TelePresence

2012-05-23T18:45:47Z

Jkratky: Created page with "Category: Technologies"

[[Category: Technologies]]

Unified Communications Virtualization Sizing Guidelines

2012-05-11T20:38:34Z

Jkratky:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

== Introduction ==

This article provides specifics and examples to aid in sizing Unified Communications applications for the UCS B-series and C-series servers.

 

 

== Application Co-residency Support Policy ==

Cisco UC virtualization only supports application co-residency under the specific conditions described below and as clarified [http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml in TAC Technote Document ID: 113520.].

 This policy only covers the rules for physical/virtual hardware sizing, co-resident application mix and maximum VM count per physical server. All other UC virtualization rules still apply (e.g supported VMware vSphere ESXi versions or hardware options). Co-residency rules apply equally to all hardware options:

*[[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]
*[[Specification-Based Hardware Support|UC on UCS Specs-based]]
*[[Specification-Based Hardware Support|HP/IBM Specs-based]]

 

{{note | UC app VM performance is only guaranteed when installed on a [[Tested Reference Configurations (TRC) | UC on UCS Tested Reference Configuration]], and only if all other conditions in this policy are followed.}} 

"Application co-residency" in this UC support policy is defined as VMs sharing the same physical server and the same virtualization software host:

*E.g. VMs running on the same VMware vSphere ESXi host on the same physical rack-mount server, such as Cisco UCS C-Series.
*E.g. VMs running on the same VMware vSphere ESXi host on the same physical blade server in the same blade server chassis, such as Cisco UCS B-Series.
*"Co-resident application mix" in this UC support policy refers to the set of VMs sharing a physical server and a virtualization software host.
*VMs running on different virtualization hosts and different physical servers are not co-resident.
**E.g. VMs running on two different Cisco UCS C-Series rack-mount servers are not co-resident.
**E.g. VMs running on two different Cisco UCS B-Series blade servers in the same UCS 5100 blade server chassis are not co-resident.

[[Image:600px-UConUCS co-res 1 whatis.jpg|Co-residency defined]] Virtual Machines (VMs) are categorized as follows for purposes of this UC support policy:

*Cisco UC app VMs (or simply '''UC app VMs'''): a VM for one of the Cisco UC apps at [[Unified Communications Virtualization Supported Applications]].
*Cisco non-UC app VMs (or simply '''non-UC VMs'''): a VM for a Cisco application not listed at [[Unified Communications Virtualization Supported Applications]], such as the VM for Cisco Nexus 1000V's VSM.
*3rd-party application VMs (or simply '''3rd-party app VMs'''): a VM for a non-Cisco, application, such as VMware vCenter, 3rd-party Cisco Technology Developer Program applications, non-Cisco-provided TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, customer home-grown applications, etc.

 

{{note | Cisco does not support non-UC or 3rd-party applications VMs running on "Cisco UC Virtualization Hypervisor" or "Cisco UC Virtualization Foundation" (as described at [[Unified Communications VMware Requirements]]). If you want to deploy non-U / 3rd-party applications, you must deploy on VMware vSphere Standard, Advanced, Enterprise or Enterprise Plus Edition. }} 

Each Cisco UC app supports one of the following four types of co-residency: 

{{note | Troubleshooting UC VMs co-resident with non-UC/3rd-party app VMs may require the changes described at <<in this TAC Technical Tip>>. . To be supported by Cisco TAC, customers must agree to these changes if required by Cisco TAC.}} 

#'''None:''' Co-residency is not supported. The UC app only supports a single instance of itself in a single VM on the virtualization host / physical server. No co-residency with ANY other VM is allowed, whether Cisco UC app VM, Cisco non-UC VM, or 3rd-party application VM.
#'''Limited:''' The co-resident application mix is restricted to specified VM combinations only. Click on the "Limited" entry in the tables below to see which VM combinations are allowed. Co-residency with any VMs outside these combinations - including other Cisco VMs - is not supported (these applications must be placed on a separate physical server). The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] listed below.
#'''UC with UC only:''' The co-resident application mix is restricted to VMs for UC apps listed at [[Unified Communications Virtualization Supported Applications]]. Co-residency with Cisco non-UC VMs and/or 3rd-party application VMs is not supported; those VMs must be placed on a separate physical server. The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below.
#'''Full:''' The co-resident application mix may contain UC app VMs with Cisco non-UC VMs with 3rd-party application VMs. The deployment must follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below. The deployment must also follow the [[#Special_Rules_for_non-UC_and_3rd-party_Co-residency|Special Rules for non-UC and 3rd-party Co-residency]] below.

 

[[Image:500px-UConUCS co-res 2 types.jpg|Types of Co-residency]] 

 

==== General Rules for Co-residency and Physical/Virtual Hardware Sizing ====

See the tables after the rules for the co-residency policy of each UC app. 

{{note | Remember that virtualization and co-residency support varies by UC app '''version''', so don't forget to double-check inter-UC-app version compatibility, see [http://www.cisco.com/go/unified-techinfo Cisco Unified Communications System Documentation].}} 

:'''"Matching" Support Policies'''

All co-resident applications must "match" in the following areas:

*Same "server" support for compute/network/storage hardware (see [[Unified Communications Virtualization Supported Applications]])
**E.g. if you want to host co-resident apps on UCS C260 M2 TRC#1, all co-resident apps must have a hardware support policy that permits this.
**E.g. if you want to deploy instead as [[Specification-Based Hardware Support|UC on UCS Specs-based]] with a diskless UCS C260 M2 and a SAN/NAS storage array, all co-resident apps must support this.
**You must pick a hardware option that all the co-resident apps can support. For example, some UC apps do not support [[Specification-Based Hardware Support]] | Specs-based for UC on UCS or HP/IBM]], some UC apps do not support certain Tested Reference Configurations such as UC on UCS C200 M2 TRC#1 (as opposed to [[Specification-Based Hardware Support|UC on UCS C200 M2 specs-based]]).
*Same support for virtualization software product and version.
**E.g. one app supports vSphere 5.0, the other app only supports vSphere 4.1. vSphere 5.0 may not be used for this co-resident application mix.
*All apps must support a co-residency policy that permits the desired co-resident application mix.
**E.g. one app has a "Full" policy, another app has "UC with UC" policy. Co-resident non-UC or 3rd-party app VMs are not allowed.
**E.g. one app has a "UC with UC" policy, another app has "Limited" policy. Even though all apps will be UC, the desired combination may not be allowed by the "Limited" app.
**E.g. one app has "None" policy. No other apps can be co-resident with this app regardless of their policies.
*If support policies of a given co-resident app mix do not match, then the "least common denominator" is required.

 

:'''Virtual Machine Templates'''

All UC applications must use a supported virtual machine OVA template from [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. 

:'''No Hardware Oversubscription'''

All VMs require a one to one mapping between virtual hardware and physical hardware. See specifics below. 

::'''CPU'''

*Must map 1 VM vCPU core to 1 physical CPU core.
**For example, if you have a host with 12 total physical cores, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 12.
**The requirement is based on ''physical'' cores, not ''logical'' cores. If the physical CPU supports hyper-threading, this should be enabled, but for purposes of UC sizing the max number of vCPU cores is still limited to the number of ''physical'' cores.
*Cisco Unity VMs also require VMware CPU Affinity.
*If there is at least one live Unity Connection VM on the physical server, then one CPU core per physical server must be left unused (it is actually being used by ESXi scheduler).
**For example, if you have a host with 12 total physical cores and one or more of the VMs on that host will be Unity Connection, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 11, with the 12th core left unused. This is regardless of how many Unity Connection VMs are on that host.

::[[Image:400px-UConUCS co-res 3 UCxn 1core unused.jpg|Leaving 1 core unused for Cisco Unity Connection]]

*CPU reservations on the VMs are not required. Use of CPU reservations in lieu of one-to-one CPU core mappings is not supported.
**Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation.
**For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported.

 

::'''Memory/RAM'''

*Must map 1 GB of VM vRAM to 1 GB of physical RAM. Memory oversubscription is not supported for Cisco UC VMs.
*The sum of virtual machines' vRAM may not exceed the total physical memory on the physical server.
*Additional 2 GB of physical RAM must be provisioned for VMware ESXi itself (this is to cover ESXi overhead to run VMs; for more details see [http://pubs.vmware.com/vsp40_e/resmgmt/wwhelp/wwhimpl/common/html/wwhelp.htm#href=r_overhead_memory_on_virtual_machines.html&single=true "Understanding Memory Overhead" on vmware.com]).

 

 

::'''Storage'''

The following apply to supported DAS, SAN and NAS storage

*Must map 1 GB of VM vDisk to 1 GB of physical storage.
**Storage thin provisioning is not supported (whether at VM layer or storage array layer).
**Any other form of storage oversubscription is not supported.
**The sum of virtual machines' vDisks may not exceed the physical disk space of the physical server's logical volume capacity (i.e. capacity net of overhead for the VM itself, VMFS in vSphere and physical RAID configuration).
**Cisco recommends 10% buffer on top of vDisk values to handle overhead within the VM (such as swap files which are the size of the VM's vRAM). See [[Shared Storage Considerations]] for more details.
*The DAS, NAS or SAN storage solution must also supply enough performance to handle the total load of the VMs.
**Must provide enough IOPS to handle sum of the VMs.
**Kernel command latency must not exceed 2-3 milliseconds.
**Physical device command latency must not exceed 15-20 milliseconds.
**See [[Shared Storage Considerations]] and [[IO Operations Per Second (IOPS)|Storage Performance Requirements]] for more details.
*If the above capacity or performance requirements are not met, the storage system is overloaded and must be "fixed" by either moving virtual machines to alternate storage, or improving storage hardware.

 

::'''Network/LAN'''

*The aggregate networking load of the co-resident virtual machines must be met with the physical networking interface(s) on the host.
*See the UC application design guides (http://www.cisco.com/go/srnd) to size network utilization by UC app VMs. In general, most UC app VMs will not saturate a 1GbE link. Deployments leveraging non-FC-storage (iSCSI, NFS or Unified Fabric/FCoE including UCS B-Series FEX) must account for network traffic from both VM LAN access and VM storage access.
*For other network hardware best practices, see [[QoS Design Considerations for Virtual UC with UCS]].
*If the above capacity or performance requirements are not met, the networking hardware is congested and must be "fixed" by either moving virtual machines to a host with different network access, or provisioning more physical network interfaces.

 

::'''Maximum VM Count per Physical Server'''

*For hardware other than UCS C200 M2 TRC#1, you may mix and match Cisco UC app VM size and quantity as long as you follow all of the sizing rules described above. The maximum number of virtual machines per physical server that can be supported depends on several factors:
*"Capacity" of physical server hardware vs. the quantity and resource usage of [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|VM OVA templates]].
**E.g. using the above physical/virtual sizing rules for CPU, a physical server with 8 total physical cores can only host 4 of the "CUCM 7.5K user OVAs" since those are 2 vCPU each. If the physical server instead had 20 total physical cores, it could host 10 of these VMs (assuming memory, network and storage hardware are also sufficient using the UC sizing rules immediately below).
**All [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configurations]] are sized for co-residency except for UCS C210 M1 Tested Reference Configuration #1 (which is only sized to host a single CUCM VM of 7500 user capacity). Note UCS C200 M2 Tested Reference Configuration #1 has special restrictions on choice of UC VM, and its allowed VMs are at lower capacity per VM than for other Tested Reference Configurations.
**[[Specification-Based Hardware Support|UC on UCS Specs-based and HP/IBM Specs-based]] deployments allow hardware options that may support a higher or lower max VM count than a [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]. E.g. UCS C210 M2 TRC#1 is a dual-4-core CPU, but UCS C210 M2 specs-based could be configured with dual-6-core (for possibly more VMs) or a single 4-core (for possibly a single VM).
*Note the max VM count may also be further restricted by UC apps that only support "Limited" co-residency as described in the tables after the rules.

[[Image:500px-UConUCS_co-res_4_max_VM_count.jpg|Maximum VM count per physical server]] 

::'''Special Requirements for UCS C200 M2 TRC#1 Hardware'''

{{note | This section is only for [[Tested Reference Configurations (TRC)|UC on UCS C200 M2 Tested Reference Configuration #1 which uses Intel E5506 / 2.13 GHz CPU]]. UCS C200 M2 configured with a faster CPU (via [[Specification-Based Hardware Support]]) does not need to follow the rules in this section.}}

*For UCS C200 M2 TRC #1, there are additional TRC-specific restrictions since it uses a slower CPU than other TRCs or specs-based (i.e. E5506 / 2.13 GHz instead of CPU with 2.53 GHz speed or higher). A C200 M2 configured with a different CPU allowed by [[Specification-Based Hardware Support|UC on UCS Specs-based]] does not have these TRC-specific restrictions. Follow these rules for UCS C200M2 TRC#1 with E5506 / 2.13 GHz CPU:
**The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
***CUCM - Unified Communications Manager 1000 users
***CER - Emergency Responder 12,000 users
***CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
***CUP - Unified Presence 1000 users
***CUCCX - Unified Contact Center Express 100 agents
***CUxAC - Unified Department, Business and Enterprise Attendant Consoles
***Other unlisted OVA templates are not supported on C200 M2 TRC #1.
**Otherwise at this time the following co-residency scenarios are supported:
***Any combination allowed by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]].
***Any other combination provided you follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], and only use the above OVA templates supported for UCS C200 M2 TRC#1.

 

 

==== Special Rules for non-UC and 3rd-party Co-residency ====

See the tables after these rules for the co-residency policy of each Cisco UC app.

Non-UC VMs and 3rd-party app VMs that will be co-resident with Cisco UC app VMs are required to align with all of the following:

*[http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml TAC Technote Document ID: 113520.] For other details on co-resident application performance troubleshooting, see [[Troubleshooting and Performance Monitoring Virtualized Environments]].
*[[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]
*All of the special rules below.

 

 

:'''"Matching" Support Policies'''
:All co-resident VMs must follow the '''"Matching" Support Polices''' rule in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. www.cisco.com/go/uc-virtualized does not describe policies for Cisco non-UC apps or 3rd-party apps

 

:'''Virtual Machine Templates'''
:Cisco non-UC VMs and 3rd-party app VMs own definition of their supported VM OVA templates (or specs for one to be created), similar to what Cisco UC app VMs require in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. http://www.cisco.com/go/uc-virtualized does not describe VM templates for Cisco non-UC apps or 3rd-party apps.

 

:'''CPU'''
:All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''CPU''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]].

 

:'''Memory/RAM'''
:*To enforce "no memory oversubscription", each co-resident VM - whether UC, non-UC or 3rd-party - must have a reservation for vRAM that includes all the vRAM of the virtual machine. For example, if you have a virtual machine that is configured with 4GB of vRAM, then that virtual machine must also have a reservation of 4 GB of vRAM.
:*Otherwise all co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Memory/RAM''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. The 2 GB for VMware vSphere is in addition to the sum of the vRAM reservations for the VMs.

 

:'''Storage'''
:*Non-UC VMs and 3rd-party app VMs must define their storage capacity requirements (ideally in an OVA template) and storage performance requirements. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Storage''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient disk space, IOPS and low latency to handle the total VM load.
:*If DAS storage is to be used with non-UC / 3rd-party app VMs, it is highly recommended that pre-deployment testing be conducted, where all VMs are pushed to their highest level of IOPS generation. This is due to DAS environments being more capacity/performance-constrained in general, more dependent on adapter caches in RAID controllers, and Cisco DAS testing only done for UC apps on UCS Tested Reference Configurations.

 

:'''Network/LAN'''
:*Non-UC VMs and 3rd-party app VMs must define the network capacity/performance requirements of their VM OVA templates. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Network/LAN''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient physical interfaces.

 

 

=== Table of Co-residency Support Policy by Cisco UC Application ===

==== Call Processing and System Management Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Unified Communications Manager (1)
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| [[Cisco Unified Communications Manager Business Edition 6000|Limited]]
|-
| Cisco Emergency Responder
| UC with UC only
|-
| Session Manager Edition
|
*8.6(2)+: Full
*8.5(1) to 8.6(1): UC with UC only

|-
| Intercompany Media Engine
| Full
|-
| Unified Attendant Consoles
| UC with UC only
|-
| UC Management Suite (OM, SM, SSM, PM)
| Full
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

==== Messaging and Presence Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Cisco Unity Connection
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| Cisco Unity
| Full 
{{note|Cisco Unity requires CPU Affinity which may not be desirable for other applications co-resident with Unity.}}

|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
|
*8.6(1)+: Full
*8.0(2) to 8.5: UC with UC only

|}

 

==== Contact Center Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
|
*8.5(x): Full
*8.0(x): UC with UC only

|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO) components (WFM, QM, AQM, CR, etc.)]
|
*8.5(2)+: Full
*8.0(2) to 8.5(1): UC with UC only

|-
| [[Unified Contact Center Enterprise]] components and deployment models 
| [[Virtualization for Unified CCE|Limited ]]
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| [[Virtualization for Unified Intelligence Center|Limited]]
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| UC with UC only
|-
| [[Unified Customer Voice Portal]] (all components) 
| [[Virtualization for Unified CVP|Limited]]
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| UC with UC only
|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
| UC with UC only
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
| UC with UC only
|}

== Redundancy and Failover Considerations ==

Application-layer considerations (such as Unified CM Cluster over WAN or Unified CCE Remote Redundancy) are the same for virtualized (UC on UCS) or non-virtualized (MCS 7800) deployments.

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:

*Avoid placing a primary VM and a backup VM on the same server, chassis or site
*For failover groups, avoid placing all actives on the same server, chassis or site
*Avoid placing all VMs of the same role on the same server, chassis or site

 

== Network, QoS and Shared Storage Design Considerations ==

See [[QoS Design Considerations for Virtual UC with UCS|'''QoS Design Considerations for Virtual UC with UCS''']] and '''[[Shared Storage Considerations]]'''.

 

== Sizing Examples ==

This section shows a sample system configuration based on following the [[High-level Checklist for Design and Implementation]] for the following set of customer requirements:

*'''General Requirements'''
**Three sites - Headquarters (HQ) and two Branches (A and B)
**CUCM and Applications located at each site
**Up to 30,000 lines per sites
**100+ sites
**Transparent use of PSTN if IP WAN unavailable
*'''Headquarters (HQ) Requirements'''
**12K Phones, use Cisco TFTP server
**10K Messaging users
**10K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 240 agents and 10 supervisors
*'''Branch A Requirements'''
**2K Phones, use Cisco TFTP server
**2K Messaging users
**2K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 145 agents and 5 supervisors
*'''Branch B Requirements'''
**500 Phones, use Cisco TFTP server
**500 Messaging users
**500 users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 45 agents and 5 supervisors

 After going through the design process, the following servers were selected to host the virtualized UC applications:

*Six Cisco UCS B200 Blade Servers for HQ (running in a UCS 5100 Chassis connected to UCS 6100 Fabric Interconnect Switches), using TRC#1 (UCS-B200M2-VCS1).
*Three Cisco UCS C210 General-Purpose Rack-Mount Servers for Branch A, using TRC#1 (UCS-C210M2-VCD2)
*Two Cisco UCS C200 General-Purpose Rack-Mount Servers for Branch B, using TRC#1 UCS-C200M2-VCD2)
*Note this example does not include non-UC applications (such as [http://www.cisco.com/go/nexus1000v Cisco Nexus 1000V] or Cisco Network Registrar) or 3rd-party applications such as customer-provided DNS / DHCP / TFTP servers, directories, email, groupware or other business applications. These applications need to run on separate physical servers and are not allowed to be co-resident with UC at this time. See the Co-residency section on this page for more details.

[[Image:UCVirtualSizingEx1.jpg]]

 See below for details on the server layout and application/VM placement at each site. Note that Branch B is using UCS C200 M2 TRC #1 so has restrictions on which VM OVAs were able to be used.

'''HQ server detail:'''

[[Image:UCVirtualSizingEx2.jpg]]

'''Branch A server detail:'''

[[Image:UCVirtualSizingEx3.jpg]]

'''Branch B server detail:'''

[[Image:UCVirtualSizingEx4.jpg]]

== Sizing and Ordering Tools ==

The suite of tools listed below can assist you with the sizing, configuring and quoting of Cisco Unified Communications solutions on the Unified Computing System.

=== Cisco Solution Expert ===

[http://www.cisco.com/go/sx| Cisco Solution Expert] assists Cisco field and Cisco Unified Communications specialized channel partners in designing and quoting UC on UCS solutions using the Cisco Unified Workspace Licensing or the traditional design model. Solution Expert delivers a Bill of Materials for the Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUS.

=== Netformx DesignXpert ===

[http://www.cisco.com/go/designxpert Netformx DesignXpert] is a third party application used to design and quote the Cisco Unified Computing System B-series. DesignXpert has two advisor modules that can be used to quote a Unified Communications solution with the Unified Computing System:

::*UC Advisor – a designing and quoting solution used to quote Unified Communications software. The UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs can be quoted when ordering separate from the Unified Computing System. Other UCS B-series components must be configured via UCS Advisor below.
::*UCS Advisor - a design and quoting solution for all UCS B-series components including Blade Servers ordered as Collaboration or Data Center SKUs, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

=== Cisco Unified Communications Sizing Tool ===

[http://tools.cisco.com/cucst Cisco Unified Communications Sizing Tool] delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

=== Cisco Configuration Tool ===

Cisco Configuration Tool '''(need link here)''' is part of the suite of Internet Commerce Tools for managing online ordering of Cisco products. It enables you to configure products and view lead times and prices for each selection. The Cisco Configuration Tool, also known as the Dynamic Configuration Tool, is used to configure the Unified Communications products and the B series SKU and VMWare ordered as Collaboration SKUs.

=== Ordering Guides ===

Ordering Guides for Unified Communications System 8.x releases are available for Cisco sales, partners, and customers.

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Sizing Guidelines

2012-05-11T20:36:36Z

Jkratky:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

== Introduction ==

This article provides specifics and examples to aid in sizing Unified Communications applications for the UCS B-series and C-series servers.

 

 

== Application Co-residency Support Policy ==

Cisco UC virtualization only supports application co-residency under the specific conditions described below and as clarified [http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml in TAC Technote Document ID: 113520.].

 This policy only covers the rules for physical/virtual hardware sizing, co-resident application mix and maximum VM count per physical server. All other UC virtualization rules still apply (e.g supported VMware vSphere ESXi versions or hardware options). Co-residency rules apply equally to all hardware options:

*[[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]
*[[Specification-Based Hardware Support|UC on UCS Specs-based]]
*[[Specification-Based Hardware Support|HP/IBM Specs-based]]

 

{{note | UC app VM performance is only guaranteed when installed on a [[Tested Reference Configurations (TRC) | UC on UCS Tested Reference Configuration]], and only if all other conditions in this policy are followed.}} 

"Application co-residency" in this UC support policy is defined as VMs sharing the same physical server and the same virtualization software host:

*E.g. VMs running on the same VMware vSphere ESXi host on the same physical rack-mount server, such as Cisco UCS C-Series.
*E.g. VMs running on the same VMware vSphere ESXi host on the same physical blade server in the same blade server chassis, such as Cisco UCS B-Series.
*"Co-resident application mix" in this UC support policy refers to the set of VMs sharing a physical server and a virtualization software host.
*VMs running on different virtualization hosts and different physical servers are not co-resident.
**E.g. VMs running on two different Cisco UCS C-Series rack-mount servers are not co-resident.
**E.g. VMs running on two different Cisco UCS B-Series blade servers in the same UCS 5100 blade server chassis are not co-resident.

[[Image:600px-UConUCS co-res 1 whatis.jpg|Co-residency defined]] Virtual Machines (VMs) are categorized as follows for purposes of this UC support policy:

*Cisco UC app VMs (or simply '''UC app VMs'''): a VM for one of the Cisco UC apps at [[Unified Communications Virtualization Supported Applications]].
*Cisco non-UC app VMs (or simply '''non-UC VMs'''): a VM for a Cisco application not listed at [[Unified Communications Virtualization Supported Applications]], such as the VM for Cisco Nexus 1000V's VSM.
*3rd-party application VMs (or simply '''3rd-party app VMs'''): a VM for a non-Cisco, application, such as VMware vCenter, 3rd-party Cisco Technology Developer Program applications, non-Cisco-provided TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, customer home-grown applications, etc.

 

{{note | Cisco does not support non-UC or 3rd-party applications VMs running on "Cisco UC Virtualization Hypervisor" or "Cisco UC Virtualization Foundation" (as described at [[Unified Communications VMware Requirements]]). If you want to deploy non-U / 3rd-party applications, you must deploy on VMware vSphere Standard, Advanced, Enterprise or Enterprise Plus Edition. }} 

Each Cisco UC app supports one of the following four types of co-residency: 

{{note | Troubleshooting UC VMs co-resident with non-UC/3rd-party app VMs may require the changes described at <<in this TAC Technical Tip>>. . To be supported by Cisco TAC, customers must agree to these changes if required by Cisco TAC.}} 

#'''None:''' Co-residency is not supported. The UC app only supports a single instance of itself in a single VM on the virtualization host / physical server. No co-residency with ANY other VM is allowed, whether Cisco UC app VM, Cisco non-UC VM, or 3rd-party application VM.
#'''Limited:''' The co-resident application mix is restricted to specified VM combinations only. Click on the "Limited" entry in the tables below to see which VM combinations are allowed. Co-residency with any VMs outside these combinations - including other Cisco VMs - is not supported (these applications must be placed on a separate physical server). The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] listed below.
#'''UC with UC only:''' The co-resident application mix is restricted to VMs for UC apps listed at [[Unified Communications Virtualization Supported Applications]]. Co-residency with Cisco non-UC VMs and/or 3rd-party application VMs is not supported; those VMs must be placed on a separate physical server. The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below.
#'''Full:''' The co-resident application mix may contain UC app VMs with Cisco non-UC VMs with 3rd-party application VMs. The deployment must follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below. The deployment must also follow the [[#Special_Rules_for_non-UC_and_3rd-party_Co-residency|Special Rules for non-UC and 3rd-party Co-residency]] below.

 

[[Image:500px-UConUCS co-res 2 types.jpg|Types of Co-residency]] 

 

==== General Rules for Co-residency and Physical/Virtual Hardware Sizing ====

See the tables after the rules for the co-residency policy of each UC app. 

{{note | Remember that virtualization and co-residency support varies by UC app '''version''', so don't forget to double-check inter-UC-app version compatibility, see [http://www.cisco.com/go/unified-techinfo Cisco Unified Communications System Documentation].}} 

:'''"Matching" Support Policies'''

All co-resident applications must "match" in the following areas:

*Same "server" support for compute/network/storage hardware (see [[Unified Communications Virtualization Supported Applications]])
**E.g. if you want to host co-resident apps on UCS C260 M2 TRC#1, all co-resident apps must have a hardware support policy that permits this.
**E.g. if you want to deploy instead as [[Specification-Based Hardware Support|UC on UCS Specs-based]] with a diskless UCS C260 M2 and a SAN/NAS storage array, all co-resident apps must support this.
**You must pick a hardware option that all the co-resident apps can support. For example, some UC apps do not support [[Specification-Based Hardware Support]] | Specs-based for UC on UCS or HP/IBM]], some UC apps do not support certain Tested Reference Configurations such as UC on UCS C200 M2 TRC#1 (as opposed to [[Specification-Based Hardware Support|UC on UCS C200 M2 specs-based]]).
*Same support for virtualization software product and version.
**E.g. one app supports vSphere 5.0, the other app only supports vSphere 4.1. vSphere 5.0 may not be used for this co-resident application mix.
*All apps must support a co-residency policy that permits the desired co-resident application mix.
**E.g. one app has a "Full" policy, another app has "UC with UC" policy. Co-resident non-UC or 3rd-party app VMs are not allowed.
**E.g. one app has a "UC with UC" policy, another app has "Limited" policy. Even though all apps will be UC, the desired combination may not be allowed by the "Limited" app.
**E.g. one app has "None" policy. No other apps can be co-resident with this app regardless of their policies.
*If support policies of a given co-resident app mix do not match, then the "least common denominator" is required.

 

:'''Virtual Machine Templates'''

All UC applications must use a supported virtual machine OVA template from [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. 

:'''No Hardware Oversubscription'''

All VMs require a one to one mapping between virtual hardware and physical hardware. See specifics below. 

::'''CPU'''

*Must map 1 VM vCPU core to 1 physical CPU core.
**For example, if you have a host with 12 total physical cores, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 12.
**The requirement is based on ''physical'' cores, not ''logical'' cores. If the physical CPU supports hyper-threading, this should be enabled, but for purposes of UC sizing the max number of vCPU cores is still limited to the number of ''physical'' cores.
*Cisco Unity VMs also require VMware CPU Affinity.
*If there is at least one live Unity Connection VM on the physical server, then one CPU core per physical server must be left unused (it is actually being used by ESXi scheduler).
**For example, if you have a host with 12 total physical cores and one or more of the VMs on that host will be Unity Connection, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 11, with the 12th core left unused. This is regardless of how many Unity Connection VMs are on that host.

::[[Image:400px-UConUCS_co-res_3_UCxn_1core_unused.jpg|Leaving 1 core unused for Cisco Unity Connection]]

*CPU reservations on the VMs are not required. Use of CPU reservations in lieu of one-to-one CPU core mappings is not supported.
**Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation.
**For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported.

 

::'''Memory/RAM'''

*Must map 1 GB of VM vRAM to 1 GB of physical RAM. Memory oversubscription is not supported for Cisco UC VMs.
*The sum of virtual machines' vRAM may not exceed the total physical memory on the physical server.
*Additional 2 GB of physical RAM must be provisioned for VMware ESXi itself (this is to cover ESXi overhead to run VMs; for more details see [http://pubs.vmware.com/vsp40_e/resmgmt/wwhelp/wwhimpl/common/html/wwhelp.htm#href=r_overhead_memory_on_virtual_machines.html&single=true "Understanding Memory Overhead" on vmware.com]).

 

 

::'''Storage'''

The following apply to supported DAS, SAN and NAS storage

*Must map 1 GB of VM vDisk to 1 GB of physical storage.
**Storage thin provisioning is not supported (whether at VM layer or storage array layer).
**Any other form of storage oversubscription is not supported.
**The sum of virtual machines' vDisks may not exceed the physical disk space of the physical server's logical volume capacity (i.e. capacity net of overhead for the VM itself, VMFS in vSphere and physical RAID configuration).
**Cisco recommends 10% buffer on top of vDisk values to handle overhead within the VM (such as swap files which are the size of the VM's vRAM). See [[Shared Storage Considerations]] for more details.
*The DAS, NAS or SAN storage solution must also supply enough performance to handle the total load of the VMs.
**Must provide enough IOPS to handle sum of the VMs.
**Kernel command latency must not exceed 2-3 milliseconds.
**Physical device command latency must not exceed 15-20 milliseconds.
**See [[Shared Storage Considerations]] and [[IO Operations Per Second (IOPS)|Storage Performance Requirements]] for more details.
*If the above capacity or performance requirements are not met, the storage system is overloaded and must be "fixed" by either moving virtual machines to alternate storage, or improving storage hardware.

 

::'''Network/LAN'''

*The aggregate networking load of the co-resident virtual machines must be met with the physical networking interface(s) on the host.
*See the UC application design guides (http://www.cisco.com/go/srnd) to size network utilization by UC app VMs. In general, most UC app VMs will not saturate a 1GbE link. Deployments leveraging non-FC-storage (iSCSI, NFS or Unified Fabric/FCoE including UCS B-Series FEX) must account for network traffic from both VM LAN access and VM storage access.
*For other network hardware best practices, see [[QoS Design Considerations for Virtual UC with UCS]].
*If the above capacity or performance requirements are not met, the networking hardware is congested and must be "fixed" by either moving virtual machines to a host with different network access, or provisioning more physical network interfaces.

 

::'''Maximum VM Count per Physical Server'''

*For hardware other than UCS C200 M2 TRC#1, you may mix and match Cisco UC app VM size and quantity as long as you follow all of the sizing rules described above. The maximum number of virtual machines per physical server that can be supported depends on several factors:
*"Capacity" of physical server hardware vs. the quantity and resource usage of [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|VM OVA templates]].
**E.g. using the above physical/virtual sizing rules for CPU, a physical server with 8 total physical cores can only host 4 of the "CUCM 7.5K user OVAs" since those are 2 vCPU each. If the physical server instead had 20 total physical cores, it could host 10 of these VMs (assuming memory, network and storage hardware are also sufficient using the UC sizing rules immediately below).
**All [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configurations]] are sized for co-residency except for UCS C210 M1 Tested Reference Configuration #1 (which is only sized to host a single CUCM VM of 7500 user capacity). Note UCS C200 M2 Tested Reference Configuration #1 has special restrictions on choice of UC VM, and its allowed VMs are at lower capacity per VM than for other Tested Reference Configurations.
**[[Specification-Based Hardware Support|UC on UCS Specs-based and HP/IBM Specs-based]] deployments allow hardware options that may support a higher or lower max VM count than a [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]. E.g. UCS C210 M2 TRC#1 is a dual-4-core CPU, but UCS C210 M2 specs-based could be configured with dual-6-core (for possibly more VMs) or a single 4-core (for possibly a single VM).
*Note the max VM count may also be further restricted by UC apps that only support "Limited" co-residency as described in the tables after the rules.

[[Image:UConUCS co-res 4 max VM count.JPG|Maximum VM count per physical server]] 

 

::'''Special Requirements for UCS C200 M2 TRC#1 Hardware'''

{{note | This section is only for [[Tested Reference Configurations (TRC)|UC on UCS C200 M2 Tested Reference Configuration #1 which uses Intel E5506 / 2.13 GHz CPU]]. UCS C200 M2 configured with a faster CPU (via [[Specification-Based Hardware Support]]) does not need to follow the rules in this section.}}

*For UCS C200 M2 TRC #1, there are additional TRC-specific restrictions since it uses a slower CPU than other TRCs or specs-based (i.e. E5506 / 2.13 GHz instead of CPU with 2.53 GHz speed or higher). A C200 M2 configured with a different CPU allowed by [[Specification-Based Hardware Support|UC on UCS Specs-based]] does not have these TRC-specific restrictions. Follow these rules for UCS C200M2 TRC#1 with E5506 / 2.13 GHz CPU:
**The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
***CUCM - Unified Communications Manager 1000 users
***CER - Emergency Responder 12,000 users
***CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
***CUP - Unified Presence 1000 users
***CUCCX - Unified Contact Center Express 100 agents
***CUxAC - Unified Department, Business and Enterprise Attendant Consoles
***Other unlisted OVA templates are not supported on C200 M2 TRC #1.
**Otherwise at this time the following co-residency scenarios are supported:
***Any combination allowed by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]].
***Any other combination provided you follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], and only use the above OVA templates supported for UCS C200 M2 TRC#1.

 

 

==== Special Rules for non-UC and 3rd-party Co-residency ====

See the tables after these rules for the co-residency policy of each Cisco UC app.

Non-UC VMs and 3rd-party app VMs that will be co-resident with Cisco UC app VMs are required to align with all of the following:

*[http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml TAC Technote Document ID: 113520.] For other details on co-resident application performance troubleshooting, see [[Troubleshooting and Performance Monitoring Virtualized Environments]].
*[[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]
*All of the special rules below.

 

 

:'''"Matching" Support Policies'''
:All co-resident VMs must follow the '''"Matching" Support Polices''' rule in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. www.cisco.com/go/uc-virtualized does not describe policies for Cisco non-UC apps or 3rd-party apps

 

:'''Virtual Machine Templates'''
:Cisco non-UC VMs and 3rd-party app VMs own definition of their supported VM OVA templates (or specs for one to be created), similar to what Cisco UC app VMs require in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. http://www.cisco.com/go/uc-virtualized does not describe VM templates for Cisco non-UC apps or 3rd-party apps.

 

:'''CPU'''
:All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''CPU''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]].

 

:'''Memory/RAM'''
:*To enforce "no memory oversubscription", each co-resident VM - whether UC, non-UC or 3rd-party - must have a reservation for vRAM that includes all the vRAM of the virtual machine. For example, if you have a virtual machine that is configured with 4GB of vRAM, then that virtual machine must also have a reservation of 4 GB of vRAM.
:*Otherwise all co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Memory/RAM''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. The 2 GB for VMware vSphere is in addition to the sum of the vRAM reservations for the VMs.

 

:'''Storage'''
:*Non-UC VMs and 3rd-party app VMs must define their storage capacity requirements (ideally in an OVA template) and storage performance requirements. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Storage''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient disk space, IOPS and low latency to handle the total VM load.
:*If DAS storage is to be used with non-UC / 3rd-party app VMs, it is highly recommended that pre-deployment testing be conducted, where all VMs are pushed to their highest level of IOPS generation. This is due to DAS environments being more capacity/performance-constrained in general, more dependent on adapter caches in RAID controllers, and Cisco DAS testing only done for UC apps on UCS Tested Reference Configurations.

 

:'''Network/LAN'''
:*Non-UC VMs and 3rd-party app VMs must define the network capacity/performance requirements of their VM OVA templates. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Network/LAN''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient physical interfaces.

 

 

=== Table of Co-residency Support Policy by Cisco UC Application ===

==== Call Processing and System Management Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Unified Communications Manager (1)
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| [[Cisco Unified Communications Manager Business Edition 6000|Limited]]
|-
| Cisco Emergency Responder
| UC with UC only
|-
| Session Manager Edition
|
*8.6(2)+: Full
*8.5(1) to 8.6(1): UC with UC only

|-
| Intercompany Media Engine
| Full
|-
| Unified Attendant Consoles
| UC with UC only
|-
| UC Management Suite (OM, SM, SSM, PM)
| Full
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

==== Messaging and Presence Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Cisco Unity Connection
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| Cisco Unity
| Full 
{{note|Cisco Unity requires CPU Affinity which may not be desirable for other applications co-resident with Unity.}}

|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
|
*8.6(1)+: Full
*8.0(2) to 8.5: UC with UC only

|}

 

==== Contact Center Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
|
*8.5(x): Full
*8.0(x): UC with UC only

|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO) components (WFM, QM, AQM, CR, etc.)]
|
*8.5(2)+: Full
*8.0(2) to 8.5(1): UC with UC only

|-
| [[Unified Contact Center Enterprise]] components and deployment models 
| [[Virtualization for Unified CCE|Limited ]]
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| [[Virtualization for Unified Intelligence Center|Limited]]
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| UC with UC only
|-
| [[Unified Customer Voice Portal]] (all components) 
| [[Virtualization for Unified CVP|Limited]]
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| UC with UC only
|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
| UC with UC only
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
| UC with UC only
|}

== Redundancy and Failover Considerations ==

Application-layer considerations (such as Unified CM Cluster over WAN or Unified CCE Remote Redundancy) are the same for virtualized (UC on UCS) or non-virtualized (MCS 7800) deployments.

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:

*Avoid placing a primary VM and a backup VM on the same server, chassis or site
*For failover groups, avoid placing all actives on the same server, chassis or site
*Avoid placing all VMs of the same role on the same server, chassis or site

 

== Network, QoS and Shared Storage Design Considerations ==

See [[QoS Design Considerations for Virtual UC with UCS|'''QoS Design Considerations for Virtual UC with UCS''']] and '''[[Shared Storage Considerations]]'''.

 

== Sizing Examples ==

This section shows a sample system configuration based on following the [[High-level Checklist for Design and Implementation]] for the following set of customer requirements:

*'''General Requirements'''
**Three sites - Headquarters (HQ) and two Branches (A and B)
**CUCM and Applications located at each site
**Up to 30,000 lines per sites
**100+ sites
**Transparent use of PSTN if IP WAN unavailable
*'''Headquarters (HQ) Requirements'''
**12K Phones, use Cisco TFTP server
**10K Messaging users
**10K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 240 agents and 10 supervisors
*'''Branch A Requirements'''
**2K Phones, use Cisco TFTP server
**2K Messaging users
**2K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 145 agents and 5 supervisors
*'''Branch B Requirements'''
**500 Phones, use Cisco TFTP server
**500 Messaging users
**500 users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 45 agents and 5 supervisors

 After going through the design process, the following servers were selected to host the virtualized UC applications:

*Six Cisco UCS B200 Blade Servers for HQ (running in a UCS 5100 Chassis connected to UCS 6100 Fabric Interconnect Switches), using TRC#1 (UCS-B200M2-VCS1).
*Three Cisco UCS C210 General-Purpose Rack-Mount Servers for Branch A, using TRC#1 (UCS-C210M2-VCD2)
*Two Cisco UCS C200 General-Purpose Rack-Mount Servers for Branch B, using TRC#1 UCS-C200M2-VCD2)
*Note this example does not include non-UC applications (such as [http://www.cisco.com/go/nexus1000v Cisco Nexus 1000V] or Cisco Network Registrar) or 3rd-party applications such as customer-provided DNS / DHCP / TFTP servers, directories, email, groupware or other business applications. These applications need to run on separate physical servers and are not allowed to be co-resident with UC at this time. See the Co-residency section on this page for more details.

[[Image:UCVirtualSizingEx1.jpg]]

 See below for details on the server layout and application/VM placement at each site. Note that Branch B is using UCS C200 M2 TRC #1 so has restrictions on which VM OVAs were able to be used.

'''HQ server detail:'''

[[Image:UCVirtualSizingEx2.jpg]]

'''Branch A server detail:'''

[[Image:UCVirtualSizingEx3.jpg]]

'''Branch B server detail:'''

[[Image:UCVirtualSizingEx4.jpg]]

== Sizing and Ordering Tools ==

The suite of tools listed below can assist you with the sizing, configuring and quoting of Cisco Unified Communications solutions on the Unified Computing System.

=== Cisco Solution Expert ===

[http://www.cisco.com/go/sx| Cisco Solution Expert] assists Cisco field and Cisco Unified Communications specialized channel partners in designing and quoting UC on UCS solutions using the Cisco Unified Workspace Licensing or the traditional design model. Solution Expert delivers a Bill of Materials for the Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUS.

=== Netformx DesignXpert ===

[http://www.cisco.com/go/designxpert Netformx DesignXpert] is a third party application used to design and quote the Cisco Unified Computing System B-series. DesignXpert has two advisor modules that can be used to quote a Unified Communications solution with the Unified Computing System:

::*UC Advisor – a designing and quoting solution used to quote Unified Communications software. The UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs can be quoted when ordering separate from the Unified Computing System. Other UCS B-series components must be configured via UCS Advisor below.
::*UCS Advisor - a design and quoting solution for all UCS B-series components including Blade Servers ordered as Collaboration or Data Center SKUs, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

=== Cisco Unified Communications Sizing Tool ===

[http://tools.cisco.com/cucst Cisco Unified Communications Sizing Tool] delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

=== Cisco Configuration Tool ===

Cisco Configuration Tool '''(need link here)''' is part of the suite of Internet Commerce Tools for managing online ordering of Cisco products. It enables you to configure products and view lead times and prices for each selection. The Cisco Configuration Tool, also known as the Dynamic Configuration Tool, is used to configure the Unified Communications products and the B series SKU and VMWare ordered as Collaboration SKUs.

=== Ordering Guides ===

Ordering Guides for Unified Communications System 8.x releases are available for Cisco sales, partners, and customers.

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Sizing Guidelines

2012-05-11T20:33:34Z

Jkratky:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

== Introduction ==

This article provides specifics and examples to aid in sizing Unified Communications applications for the UCS B-series and C-series servers.

 

== Application Co-residency Support Policy ==

Cisco UC virtualization only supports application co-residency under the specific conditions described below and as clarified [http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml in TAC Technote Document ID: 113520.].

 This policy only covers the rules for physical/virtual hardware sizing, co-resident application mix and maximum VM count per physical server. All other UC virtualization rules still apply (e.g supported VMware vSphere ESXi versions or hardware options). Co-residency rules apply equally to all hardware options:

*[[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]
*[[Specification-Based Hardware Support|UC on UCS Specs-based]]
*[[Specification-Based Hardware Support|HP/IBM Specs-based]]

 

{{note | UC app VM performance is only guaranteed when installed on a [[Tested Reference Configurations (TRC) | UC on UCS Tested Reference Configuration]], and only if all other conditions in this policy are followed.}} 

"Application co-residency" in this UC support policy is defined as VMs sharing the same physical server and the same virtualization software host:

*E.g. VMs running on the same VMware vSphere ESXi host on the same physical rack-mount server, such as Cisco UCS C-Series.
*E.g. VMs running on the same VMware vSphere ESXi host on the same physical blade server in the same blade server chassis, such as Cisco UCS B-Series.
*"Co-resident application mix" in this UC support policy refers to the set of VMs sharing a physical server and a virtualization software host.
*VMs running on different virtualization hosts and different physical servers are not co-resident.
**E.g. VMs running on two different Cisco UCS C-Series rack-mount servers are not co-resident.
**E.g. VMs running on two different Cisco UCS B-Series blade servers in the same UCS 5100 blade server chassis are not co-resident.

[[Image:600px-UConUCS co-res 1 whatis.jpg|Co-residency defined]] Virtual Machines (VMs) are categorized as follows for purposes of this UC support policy:

*Cisco UC app VMs (or simply '''UC app VMs'''): a VM for one of the Cisco UC apps at [[Unified Communications Virtualization Supported Applications]].
*Cisco non-UC app VMs (or simply '''non-UC VMs'''): a VM for a Cisco application not listed at [[Unified Communications Virtualization Supported Applications]], such as the VM for Cisco Nexus 1000V's VSM.
*3rd-party application VMs (or simply '''3rd-party app VMs'''): a VM for a non-Cisco, application, such as VMware vCenter, 3rd-party Cisco Technology Developer Program applications, non-Cisco-provided TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, customer home-grown applications, etc.

 

{{note | Cisco does not support non-UC or 3rd-party applications VMs running on "Cisco UC Virtualization Hypervisor" or "Cisco UC Virtualization Foundation" (as described at [[Unified Communications VMware Requirements]]). If you want to deploy non-U / 3rd-party applications, you must deploy on VMware vSphere Standard, Advanced, Enterprise or Enterprise Plus Edition. }} 

Each Cisco UC app supports one of the following four types of co-residency: 

{{note | Troubleshooting UC VMs co-resident with non-UC/3rd-party app VMs may require the changes described at <<in this TAC Technical Tip>>. . To be supported by Cisco TAC, customers must agree to these changes if required by Cisco TAC.}} 

#'''None:''' Co-residency is not supported. The UC app only supports a single instance of itself in a single VM on the virtualization host / physical server. No co-residency with ANY other VM is allowed, whether Cisco UC app VM, Cisco non-UC VM, or 3rd-party application VM.
#'''Limited:''' The co-resident application mix is restricted to specified VM combinations only. Click on the "Limited" entry in the tables below to see which VM combinations are allowed. Co-residency with any VMs outside these combinations - including other Cisco VMs - is not supported (these applications must be placed on a separate physical server). The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] listed below.
#'''UC with UC only:''' The co-resident application mix is restricted to VMs for UC apps listed at [[Unified Communications Virtualization Supported Applications]]. Co-residency with Cisco non-UC VMs and/or 3rd-party application VMs is not supported; those VMs must be placed on a separate physical server. The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below.
#'''Full:''' The co-resident application mix may contain UC app VMs with Cisco non-UC VMs with 3rd-party application VMs. The deployment must follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below. The deployment must also follow the [[#Special_Rules_for_non-UC_and_3rd-party_Co-residency|Special Rules for non-UC and 3rd-party Co-residency]] below.

 

[[Image:500px-UConUCS_co-res_2_types.jpg|Types of Co-residency]] 

 

==== General Rules for Co-residency and Physical/Virtual Hardware Sizing ====

See the tables after the rules for the co-residency policy of each UC app. 

{{note | Remember that virtualization and co-residency support varies by UC app '''version''', so don't forget to double-check inter-UC-app version compatibility, see [http://www.cisco.com/go/unified-techinfo Cisco Unified Communications System Documentation].}} 

:'''"Matching" Support Policies'''

All co-resident applications must "match" in the following areas:

*Same "server" support for compute/network/storage hardware (see [[Unified Communications Virtualization Supported Applications]])
**E.g. if you want to host co-resident apps on UCS C260 M2 TRC#1, all co-resident apps must have a hardware support policy that permits this.
**E.g. if you want to deploy instead as [[Specification-Based Hardware Support|UC on UCS Specs-based]] with a diskless UCS C260 M2 and a SAN/NAS storage array, all co-resident apps must support this.
**You must pick a hardware option that all the co-resident apps can support. For example, some UC apps do not support [[Specification-Based Hardware Support]] | Specs-based for UC on UCS or HP/IBM]], some UC apps do not support certain Tested Reference Configurations such as UC on UCS C200 M2 TRC#1 (as opposed to [[Specification-Based Hardware Support|UC on UCS C200 M2 specs-based]]).
*Same support for virtualization software product and version.
**E.g. one app supports vSphere 5.0, the other app only supports vSphere 4.1. vSphere 5.0 may not be used for this co-resident application mix.
*All apps must support a co-residency policy that permits the desired co-resident application mix.
**E.g. one app has a "Full" policy, another app has "UC with UC" policy. Co-resident non-UC or 3rd-party app VMs are not allowed.
**E.g. one app has a "UC with UC" policy, another app has "Limited" policy. Even though all apps will be UC, the desired combination may not be allowed by the "Limited" app.
**E.g. one app has "None" policy. No other apps can be co-resident with this app regardless of their policies.
*If support policies of a given co-resident app mix do not match, then the "least common denominator" is required.

 

:'''Virtual Machine Templates'''

All UC applications must use a supported virtual machine OVA template from [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. 

:'''No Hardware Oversubscription'''

All VMs require a one to one mapping between virtual hardware and physical hardware. See specifics below. 

::'''CPU'''

*Must map 1 VM vCPU core to 1 physical CPU core.
**For example, if you have a host with 12 total physical cores, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 12.
**The requirement is based on ''physical'' cores, not ''logical'' cores. If the physical CPU supports hyper-threading, this should be enabled, but for purposes of UC sizing the max number of vCPU cores is still limited to the number of ''physical'' cores.
*Cisco Unity VMs also require VMware CPU Affinity.
*If there is at least one live Unity Connection VM on the physical server, then one CPU core per physical server must be left unused (it is actually being used by ESXi scheduler).
**For example, if you have a host with 12 total physical cores and one or more of the VMs on that host will be Unity Connection, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 11, with the 12th core left unused. This is regardless of how many Unity Connection VMs are on that host.

::[[Image:UConUCS co-res 3 UCxn 1core unused.JPG|Leaving 1 core unused for Cisco Unity Connection]]

*CPU reservations on the VMs are not required. Use of CPU reservations in lieu of one-to-one CPU core mappings is not supported.
**Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation.
**For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported.

 

::'''Memory/RAM'''

*Must map 1 GB of VM vRAM to 1 GB of physical RAM. Memory oversubscription is not supported for Cisco UC VMs.
*The sum of virtual machines' vRAM may not exceed the total physical memory on the physical server.
*Additional 2 GB of physical RAM must be provisioned for VMware ESXi itself (this is to cover ESXi overhead to run VMs; for more details see [http://pubs.vmware.com/vsp40_e/resmgmt/wwhelp/wwhimpl/common/html/wwhelp.htm#href=r_overhead_memory_on_virtual_machines.html&single=true "Understanding Memory Overhead" on vmware.com]).

 

 

::'''Storage'''

The following apply to supported DAS, SAN and NAS storage

*Must map 1 GB of VM vDisk to 1 GB of physical storage.
**Storage thin provisioning is not supported (whether at VM layer or storage array layer).
**Any other form of storage oversubscription is not supported.
**The sum of virtual machines' vDisks may not exceed the physical disk space of the physical server's logical volume capacity (i.e. capacity net of overhead for the VM itself, VMFS in vSphere and physical RAID configuration).
**Cisco recommends 10% buffer on top of vDisk values to handle overhead within the VM (such as swap files which are the size of the VM's vRAM). See [[Shared Storage Considerations]] for more details.
*The DAS, NAS or SAN storage solution must also supply enough performance to handle the total load of the VMs.
**Must provide enough IOPS to handle sum of the VMs.
**Kernel command latency must not exceed 2-3 milliseconds.
**Physical device command latency must not exceed 15-20 milliseconds.
**See [[Shared Storage Considerations]] and [[IO Operations Per Second (IOPS)|Storage Performance Requirements]] for more details.
*If the above capacity or performance requirements are not met, the storage system is overloaded and must be "fixed" by either moving virtual machines to alternate storage, or improving storage hardware.

 

::'''Network/LAN'''

*The aggregate networking load of the co-resident virtual machines must be met with the physical networking interface(s) on the host.
*See the UC application design guides (http://www.cisco.com/go/srnd) to size network utilization by UC app VMs. In general, most UC app VMs will not saturate a 1GbE link. Deployments leveraging non-FC-storage (iSCSI, NFS or Unified Fabric/FCoE including UCS B-Series FEX) must account for network traffic from both VM LAN access and VM storage access.
*For other network hardware best practices, see [[QoS Design Considerations for Virtual UC with UCS]].
*If the above capacity or performance requirements are not met, the networking hardware is congested and must be "fixed" by either moving virtual machines to a host with different network access, or provisioning more physical network interfaces.

 

::'''Maximum VM Count per Physical Server'''

*For hardware other than UCS C200 M2 TRC#1, you may mix and match Cisco UC app VM size and quantity as long as you follow all of the sizing rules described above. The maximum number of virtual machines per physical server that can be supported depends on several factors:
*"Capacity" of physical server hardware vs. the quantity and resource usage of [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|VM OVA templates]].
**E.g. using the above physical/virtual sizing rules for CPU, a physical server with 8 total physical cores can only host 4 of the "CUCM 7.5K user OVAs" since those are 2 vCPU each. If the physical server instead had 20 total physical cores, it could host 10 of these VMs (assuming memory, network and storage hardware are also sufficient using the UC sizing rules immediately below).
**All [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configurations]] are sized for co-residency except for UCS C210 M1 Tested Reference Configuration #1 (which is only sized to host a single CUCM VM of 7500 user capacity). Note UCS C200 M2 Tested Reference Configuration #1 has special restrictions on choice of UC VM, and its allowed VMs are at lower capacity per VM than for other Tested Reference Configurations.
**[[Specification-Based Hardware Support|UC on UCS Specs-based and HP/IBM Specs-based]] deployments allow hardware options that may support a higher or lower max VM count than a [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]. E.g. UCS C210 M2 TRC#1 is a dual-4-core CPU, but UCS C210 M2 specs-based could be configured with dual-6-core (for possibly more VMs) or a single 4-core (for possibly a single VM).
*Note the max VM count may also be further restricted by UC apps that only support "Limited" co-residency as described in the tables after the rules.

[[Image:UConUCS co-res 4 max VM count.JPG|Maximum VM count per physical server]] 

 

::'''Special Requirements for UCS C200 M2 TRC#1 Hardware'''

{{note | This section is only for [[Tested Reference Configurations (TRC)|UC on UCS C200 M2 Tested Reference Configuration #1 which uses Intel E5506 / 2.13 GHz CPU]]. UCS C200 M2 configured with a faster CPU (via [[Specification-Based Hardware Support]]) does not need to follow the rules in this section.}}

*For UCS C200 M2 TRC #1, there are additional TRC-specific restrictions since it uses a slower CPU than other TRCs or specs-based (i.e. E5506 / 2.13 GHz instead of CPU with 2.53 GHz speed or higher). A C200 M2 configured with a different CPU allowed by [[Specification-Based Hardware Support|UC on UCS Specs-based]] does not have these TRC-specific restrictions. Follow these rules for UCS C200M2 TRC#1 with E5506 / 2.13 GHz CPU:
**The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
***CUCM - Unified Communications Manager 1000 users
***CER - Emergency Responder 12,000 users
***CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
***CUP - Unified Presence 1000 users
***CUCCX - Unified Contact Center Express 100 agents
***CUxAC - Unified Department, Business and Enterprise Attendant Consoles
***Other unlisted OVA templates are not supported on C200 M2 TRC #1.
**Otherwise at this time the following co-residency scenarios are supported:
***Any combination allowed by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]].
***Any other combination provided you follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], and only use the above OVA templates supported for UCS C200 M2 TRC#1.

 

 

==== Special Rules for non-UC and 3rd-party Co-residency ====

See the tables after these rules for the co-residency policy of each Cisco UC app.

Non-UC VMs and 3rd-party app VMs that will be co-resident with Cisco UC app VMs are required to align with all of the following:

*[http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml TAC Technote Document ID: 113520.] For other details on co-resident application performance troubleshooting, see [[Troubleshooting and Performance Monitoring Virtualized Environments]].
*[[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]
*All of the special rules below.

 

 

:'''"Matching" Support Policies'''
:All co-resident VMs must follow the '''"Matching" Support Polices''' rule in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. www.cisco.com/go/uc-virtualized does not describe policies for Cisco non-UC apps or 3rd-party apps

 

:'''Virtual Machine Templates'''
:Cisco non-UC VMs and 3rd-party app VMs own definition of their supported VM OVA templates (or specs for one to be created), similar to what Cisco UC app VMs require in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. http://www.cisco.com/go/uc-virtualized does not describe VM templates for Cisco non-UC apps or 3rd-party apps.

 

:'''CPU'''
:All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''CPU''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]].

 

:'''Memory/RAM'''
:*To enforce "no memory oversubscription", each co-resident VM - whether UC, non-UC or 3rd-party - must have a reservation for vRAM that includes all the vRAM of the virtual machine. For example, if you have a virtual machine that is configured with 4GB of vRAM, then that virtual machine must also have a reservation of 4 GB of vRAM.
:*Otherwise all co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Memory/RAM''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. The 2 GB for VMware vSphere is in addition to the sum of the vRAM reservations for the VMs.

 

:'''Storage'''
:*Non-UC VMs and 3rd-party app VMs must define their storage capacity requirements (ideally in an OVA template) and storage performance requirements. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Storage''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient disk space, IOPS and low latency to handle the total VM load.
:*If DAS storage is to be used with non-UC / 3rd-party app VMs, it is highly recommended that pre-deployment testing be conducted, where all VMs are pushed to their highest level of IOPS generation. This is due to DAS environments being more capacity/performance-constrained in general, more dependent on adapter caches in RAID controllers, and Cisco DAS testing only done for UC apps on UCS Tested Reference Configurations.

 

:'''Network/LAN'''
:*Non-UC VMs and 3rd-party app VMs must define the network capacity/performance requirements of their VM OVA templates. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Network/LAN''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient physical interfaces.

 

 

=== Table of Co-residency Support Policy by Cisco UC Application ===

==== Call Processing and System Management Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Unified Communications Manager (1)
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| [[Cisco Unified Communications Manager Business Edition 6000|Limited]]
|-
| Cisco Emergency Responder
| UC with UC only
|-
| Session Manager Edition
|
*8.6(2)+: Full
*8.5(1) to 8.6(1): UC with UC only

|-
| Intercompany Media Engine
| Full
|-
| Unified Attendant Consoles
| UC with UC only
|-
| UC Management Suite (OM, SM, SSM, PM)
| Full
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

==== Messaging and Presence Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Cisco Unity Connection
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| Cisco Unity
| Full 
{{note|Cisco Unity requires CPU Affinity which may not be desirable for other applications co-resident with Unity.}}

|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
|
*8.6(1)+: Full
*8.0(2) to 8.5: UC with UC only

|}

 

==== Contact Center Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
|
*8.5(x): Full
*8.0(x): UC with UC only

|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO) components (WFM, QM, AQM, CR, etc.)]
|
*8.5(2)+: Full
*8.0(2) to 8.5(1): UC with UC only

|-
| [[Unified Contact Center Enterprise]] components and deployment models 
| [[Virtualization for Unified CCE|Limited ]]
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| [[Virtualization for Unified Intelligence Center|Limited]]
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| UC with UC only
|-
| [[Unified Customer Voice Portal]] (all components) 
| [[Virtualization for Unified CVP|Limited]]
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| UC with UC only
|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
| UC with UC only
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
| UC with UC only
|}

== Redundancy and Failover Considerations ==

Application-layer considerations (such as Unified CM Cluster over WAN or Unified CCE Remote Redundancy) are the same for virtualized (UC on UCS) or non-virtualized (MCS 7800) deployments.

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:

*Avoid placing a primary VM and a backup VM on the same server, chassis or site
*For failover groups, avoid placing all actives on the same server, chassis or site
*Avoid placing all VMs of the same role on the same server, chassis or site

 

== Network, QoS and Shared Storage Design Considerations ==

See [[QoS Design Considerations for Virtual UC with UCS|'''QoS Design Considerations for Virtual UC with UCS''']] and '''[[Shared Storage Considerations]]'''.

 

== Sizing Examples ==

This section shows a sample system configuration based on following the [[High-level Checklist for Design and Implementation]] for the following set of customer requirements:

*'''General Requirements'''
**Three sites - Headquarters (HQ) and two Branches (A and B)
**CUCM and Applications located at each site
**Up to 30,000 lines per sites
**100+ sites
**Transparent use of PSTN if IP WAN unavailable
*'''Headquarters (HQ) Requirements'''
**12K Phones, use Cisco TFTP server
**10K Messaging users
**10K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 240 agents and 10 supervisors
*'''Branch A Requirements'''
**2K Phones, use Cisco TFTP server
**2K Messaging users
**2K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 145 agents and 5 supervisors
*'''Branch B Requirements'''
**500 Phones, use Cisco TFTP server
**500 Messaging users
**500 users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 45 agents and 5 supervisors

 After going through the design process, the following servers were selected to host the virtualized UC applications:

*Six Cisco UCS B200 Blade Servers for HQ (running in a UCS 5100 Chassis connected to UCS 6100 Fabric Interconnect Switches), using TRC#1 (UCS-B200M2-VCS1).
*Three Cisco UCS C210 General-Purpose Rack-Mount Servers for Branch A, using TRC#1 (UCS-C210M2-VCD2)
*Two Cisco UCS C200 General-Purpose Rack-Mount Servers for Branch B, using TRC#1 UCS-C200M2-VCD2)
*Note this example does not include non-UC applications (such as [http://www.cisco.com/go/nexus1000v Cisco Nexus 1000V] or Cisco Network Registrar) or 3rd-party applications such as customer-provided DNS / DHCP / TFTP servers, directories, email, groupware or other business applications. These applications need to run on separate physical servers and are not allowed to be co-resident with UC at this time. See the Co-residency section on this page for more details.

[[Image:UCVirtualSizingEx1.jpg]]

 See below for details on the server layout and application/VM placement at each site. Note that Branch B is using UCS C200 M2 TRC #1 so has restrictions on which VM OVAs were able to be used.

'''HQ server detail:'''

[[Image:UCVirtualSizingEx2.jpg]]

'''Branch A server detail:'''

[[Image:UCVirtualSizingEx3.jpg]]

'''Branch B server detail:'''

[[Image:UCVirtualSizingEx4.jpg]]

== Sizing and Ordering Tools ==

The suite of tools listed below can assist you with the sizing, configuring and quoting of Cisco Unified Communications solutions on the Unified Computing System.

=== Cisco Solution Expert ===

[http://www.cisco.com/go/sx| Cisco Solution Expert] assists Cisco field and Cisco Unified Communications specialized channel partners in designing and quoting UC on UCS solutions using the Cisco Unified Workspace Licensing or the traditional design model. Solution Expert delivers a Bill of Materials for the Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUS.

=== Netformx DesignXpert ===

[http://www.cisco.com/go/designxpert Netformx DesignXpert] is a third party application used to design and quote the Cisco Unified Computing System B-series. DesignXpert has two advisor modules that can be used to quote a Unified Communications solution with the Unified Computing System:

::*UC Advisor – a designing and quoting solution used to quote Unified Communications software. The UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs can be quoted when ordering separate from the Unified Computing System. Other UCS B-series components must be configured via UCS Advisor below.
::*UCS Advisor - a design and quoting solution for all UCS B-series components including Blade Servers ordered as Collaboration or Data Center SKUs, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

=== Cisco Unified Communications Sizing Tool ===

[http://tools.cisco.com/cucst Cisco Unified Communications Sizing Tool] delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

=== Cisco Configuration Tool ===

Cisco Configuration Tool '''(need link here)''' is part of the suite of Internet Commerce Tools for managing online ordering of Cisco products. It enables you to configure products and view lead times and prices for each selection. The Cisco Configuration Tool, also known as the Dynamic Configuration Tool, is used to configure the Unified Communications products and the B series SKU and VMWare ordered as Collaboration SKUs.

=== Ordering Guides ===

Ordering Guides for Unified Communications System 8.x releases are available for Cisco sales, partners, and customers.

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Sizing Guidelines

2012-05-11T20:30:36Z

Jkratky:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

== Introduction ==

This article provides specifics and examples to aid in sizing Unified Communications applications for the UCS B-series and C-series servers.

 

== Application Co-residency Support Policy ==

Cisco UC virtualization only supports application co-residency under the specific conditions described below and as clarified [http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml in TAC Technote Document ID: 113520.].

 This policy only covers the rules for physical/virtual hardware sizing, co-resident application mix and maximum VM count per physical server. All other UC virtualization rules still apply (e.g supported VMware vSphere ESXi versions or hardware options). Co-residency rules apply equally to all hardware options:

*[[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]
*[[Specification-Based Hardware Support|UC on UCS Specs-based]]
*[[Specification-Based Hardware Support|HP/IBM Specs-based]]

 

{{note | UC app VM performance is only guaranteed when installed on a [[Tested Reference Configurations (TRC) | UC on UCS Tested Reference Configuration]], and only if all other conditions in this policy are followed.}} 

"Application co-residency" in this UC support policy is defined as VMs sharing the same physical server and the same virtualization software host:

*E.g. VMs running on the same VMware vSphere ESXi host on the same physical rack-mount server, such as Cisco UCS C-Series.
*E.g. VMs running on the same VMware vSphere ESXi host on the same physical blade server in the same blade server chassis, such as Cisco UCS B-Series.
*"Co-resident application mix" in this UC support policy refers to the set of VMs sharing a physical server and a virtualization software host.
*VMs running on different virtualization hosts and different physical servers are not co-resident.
**E.g. VMs running on two different Cisco UCS C-Series rack-mount servers are not co-resident.
**E.g. VMs running on two different Cisco UCS B-Series blade servers in the same UCS 5100 blade server chassis are not co-resident.

[[Image:600px-UConUCS co-res 1 whatis.jpg|Co-residency defined]] Virtual Machines (VMs) are categorized as follows for purposes of this UC support policy:

*Cisco UC app VMs (or simply '''UC app VMs'''): a VM for one of the Cisco UC apps at [[Unified Communications Virtualization Supported Applications]].
*Cisco non-UC app VMs (or simply '''non-UC VMs'''): a VM for a Cisco application not listed at [[Unified Communications Virtualization Supported Applications]], such as the VM for Cisco Nexus 1000V's VSM.
*3rd-party application VMs (or simply '''3rd-party app VMs'''): a VM for a non-Cisco, application, such as VMware vCenter, 3rd-party Cisco Technology Developer Program applications, non-Cisco-provided TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, customer home-grown applications, etc.

 

{{note | Cisco does not support non-UC or 3rd-party applications VMs running on "Cisco UC Virtualization Hypervisor" or "Cisco UC Virtualization Foundation" (as described at [[Unified Communications VMware Requirements]]). If you want to deploy non-U / 3rd-party applications, you must deploy on VMware vSphere Standard, Advanced, Enterprise or Enterprise Plus Edition. }} 

Each Cisco UC app supports one of the following four types of co-residency: 

{{note | Troubleshooting UC VMs co-resident with non-UC/3rd-party app VMs may require the changes described at <<in this TAC Technical Tip>>. . To be supported by Cisco TAC, customers must agree to these changes if required by Cisco TAC.}} 

#'''None:''' Co-residency is not supported. The UC app only supports a single instance of itself in a single VM on the virtualization host / physical server. No co-residency with ANY other VM is allowed, whether Cisco UC app VM, Cisco non-UC VM, or 3rd-party application VM.
#'''Limited:''' The co-resident application mix is restricted to specified VM combinations only. Click on the "Limited" entry in the tables below to see which VM combinations are allowed. Co-residency with any VMs outside these combinations - including other Cisco VMs - is not supported (these applications must be placed on a separate physical server). The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] listed below.
#'''UC with UC only:''' The co-resident application mix is restricted to VMs for UC apps listed at [[Unified Communications Virtualization Supported Applications]]. Co-residency with Cisco non-UC VMs and/or 3rd-party application VMs is not supported; those VMs must be placed on a separate physical server. The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below.
#'''Full:''' The co-resident application mix may contain UC app VMs with Cisco non-UC VMs with 3rd-party application VMs. The deployment must follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below. The deployment must also follow the [[#Special_Rules_for_non-UC_and_3rd-party_Co-residency|Special Rules for non-UC and 3rd-party Co-residency]] below.

 

[[Image:UConUCS co-res 2 types.JPG|Types of Co-residency]] 

 

==== General Rules for Co-residency and Physical/Virtual Hardware Sizing ====

See the tables after the rules for the co-residency policy of each UC app. 

{{note | Remember that virtualization and co-residency support varies by UC app '''version''', so don't forget to double-check inter-UC-app version compatibility, see [http://www.cisco.com/go/unified-techinfo Cisco Unified Communications System Documentation].}} 

:'''"Matching" Support Policies'''

All co-resident applications must "match" in the following areas:

*Same "server" support for compute/network/storage hardware (see [[Unified Communications Virtualization Supported Applications]])
**E.g. if you want to host co-resident apps on UCS C260 M2 TRC#1, all co-resident apps must have a hardware support policy that permits this.
**E.g. if you want to deploy instead as [[Specification-Based Hardware Support|UC on UCS Specs-based]] with a diskless UCS C260 M2 and a SAN/NAS storage array, all co-resident apps must support this.
**You must pick a hardware option that all the co-resident apps can support. For example, some UC apps do not support [[Specification-Based Hardware Support]] | Specs-based for UC on UCS or HP/IBM]], some UC apps do not support certain Tested Reference Configurations such as UC on UCS C200 M2 TRC#1 (as opposed to [[Specification-Based Hardware Support|UC on UCS C200 M2 specs-based]]).
*Same support for virtualization software product and version.
**E.g. one app supports vSphere 5.0, the other app only supports vSphere 4.1. vSphere 5.0 may not be used for this co-resident application mix.
*All apps must support a co-residency policy that permits the desired co-resident application mix.
**E.g. one app has a "Full" policy, another app has "UC with UC" policy. Co-resident non-UC or 3rd-party app VMs are not allowed.
**E.g. one app has a "UC with UC" policy, another app has "Limited" policy. Even though all apps will be UC, the desired combination may not be allowed by the "Limited" app.
**E.g. one app has "None" policy. No other apps can be co-resident with this app regardless of their policies.
*If support policies of a given co-resident app mix do not match, then the "least common denominator" is required.

 

:'''Virtual Machine Templates'''

All UC applications must use a supported virtual machine OVA template from [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. 

:'''No Hardware Oversubscription'''

All VMs require a one to one mapping between virtual hardware and physical hardware. See specifics below. 

::'''CPU'''

*Must map 1 VM vCPU core to 1 physical CPU core.
**For example, if you have a host with 12 total physical cores, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 12.
**The requirement is based on ''physical'' cores, not ''logical'' cores. If the physical CPU supports hyper-threading, this should be enabled, but for purposes of UC sizing the max number of vCPU cores is still limited to the number of ''physical'' cores.
*Cisco Unity VMs also require VMware CPU Affinity.
*If there is at least one live Unity Connection VM on the physical server, then one CPU core per physical server must be left unused (it is actually being used by ESXi scheduler).
**For example, if you have a host with 12 total physical cores and one or more of the VMs on that host will be Unity Connection, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 11, with the 12th core left unused. This is regardless of how many Unity Connection VMs are on that host.

::[[Image:UConUCS co-res 3 UCxn 1core unused.JPG|Leaving 1 core unused for Cisco Unity Connection]]

*CPU reservations on the VMs are not required. Use of CPU reservations in lieu of one-to-one CPU core mappings is not supported.
**Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation.
**For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported.

 

::'''Memory/RAM'''

*Must map 1 GB of VM vRAM to 1 GB of physical RAM. Memory oversubscription is not supported for Cisco UC VMs.
*The sum of virtual machines' vRAM may not exceed the total physical memory on the physical server.
*Additional 2 GB of physical RAM must be provisioned for VMware ESXi itself (this is to cover ESXi overhead to run VMs; for more details see [http://pubs.vmware.com/vsp40_e/resmgmt/wwhelp/wwhimpl/common/html/wwhelp.htm#href=r_overhead_memory_on_virtual_machines.html&single=true "Understanding Memory Overhead" on vmware.com]).

 

 

::'''Storage'''

The following apply to supported DAS, SAN and NAS storage

*Must map 1 GB of VM vDisk to 1 GB of physical storage.
**Storage thin provisioning is not supported (whether at VM layer or storage array layer).
**Any other form of storage oversubscription is not supported.
**The sum of virtual machines' vDisks may not exceed the physical disk space of the physical server's logical volume capacity (i.e. capacity net of overhead for the VM itself, VMFS in vSphere and physical RAID configuration).
**Cisco recommends 10% buffer on top of vDisk values to handle overhead within the VM (such as swap files which are the size of the VM's vRAM). See [[Shared Storage Considerations]] for more details.
*The DAS, NAS or SAN storage solution must also supply enough performance to handle the total load of the VMs.
**Must provide enough IOPS to handle sum of the VMs.
**Kernel command latency must not exceed 2-3 milliseconds.
**Physical device command latency must not exceed 15-20 milliseconds.
**See [[Shared Storage Considerations]] and [[IO Operations Per Second (IOPS)|Storage Performance Requirements]] for more details.
*If the above capacity or performance requirements are not met, the storage system is overloaded and must be "fixed" by either moving virtual machines to alternate storage, or improving storage hardware.

 

::'''Network/LAN'''

*The aggregate networking load of the co-resident virtual machines must be met with the physical networking interface(s) on the host.
*See the UC application design guides (http://www.cisco.com/go/srnd) to size network utilization by UC app VMs. In general, most UC app VMs will not saturate a 1GbE link. Deployments leveraging non-FC-storage (iSCSI, NFS or Unified Fabric/FCoE including UCS B-Series FEX) must account for network traffic from both VM LAN access and VM storage access.
*For other network hardware best practices, see [[QoS Design Considerations for Virtual UC with UCS]].
*If the above capacity or performance requirements are not met, the networking hardware is congested and must be "fixed" by either moving virtual machines to a host with different network access, or provisioning more physical network interfaces.

 

::'''Maximum VM Count per Physical Server'''

*For hardware other than UCS C200 M2 TRC#1, you may mix and match Cisco UC app VM size and quantity as long as you follow all of the sizing rules described above. The maximum number of virtual machines per physical server that can be supported depends on several factors:
*"Capacity" of physical server hardware vs. the quantity and resource usage of [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|VM OVA templates]].
**E.g. using the above physical/virtual sizing rules for CPU, a physical server with 8 total physical cores can only host 4 of the "CUCM 7.5K user OVAs" since those are 2 vCPU each. If the physical server instead had 20 total physical cores, it could host 10 of these VMs (assuming memory, network and storage hardware are also sufficient using the UC sizing rules immediately below).
**All [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configurations]] are sized for co-residency except for UCS C210 M1 Tested Reference Configuration #1 (which is only sized to host a single CUCM VM of 7500 user capacity). Note UCS C200 M2 Tested Reference Configuration #1 has special restrictions on choice of UC VM, and its allowed VMs are at lower capacity per VM than for other Tested Reference Configurations.
**[[Specification-Based Hardware Support|UC on UCS Specs-based and HP/IBM Specs-based]] deployments allow hardware options that may support a higher or lower max VM count than a [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]. E.g. UCS C210 M2 TRC#1 is a dual-4-core CPU, but UCS C210 M2 specs-based could be configured with dual-6-core (for possibly more VMs) or a single 4-core (for possibly a single VM).
*Note the max VM count may also be further restricted by UC apps that only support "Limited" co-residency as described in the tables after the rules.

[[Image:UConUCS co-res 4 max VM count.JPG|Maximum VM count per physical server]] 

 

::'''Special Requirements for UCS C200 M2 TRC#1 Hardware'''

{{note | This section is only for [[Tested Reference Configurations (TRC)|UC on UCS C200 M2 Tested Reference Configuration #1 which uses Intel E5506 / 2.13 GHz CPU]]. UCS C200 M2 configured with a faster CPU (via [[Specification-Based Hardware Support]]) does not need to follow the rules in this section.}}

*For UCS C200 M2 TRC #1, there are additional TRC-specific restrictions since it uses a slower CPU than other TRCs or specs-based (i.e. E5506 / 2.13 GHz instead of CPU with 2.53 GHz speed or higher). A C200 M2 configured with a different CPU allowed by [[Specification-Based Hardware Support|UC on UCS Specs-based]] does not have these TRC-specific restrictions. Follow these rules for UCS C200M2 TRC#1 with E5506 / 2.13 GHz CPU:
**The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
***CUCM - Unified Communications Manager 1000 users
***CER - Emergency Responder 12,000 users
***CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
***CUP - Unified Presence 1000 users
***CUCCX - Unified Contact Center Express 100 agents
***CUxAC - Unified Department, Business and Enterprise Attendant Consoles
***Other unlisted OVA templates are not supported on C200 M2 TRC #1.
**Otherwise at this time the following co-residency scenarios are supported:
***Any combination allowed by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]].
***Any other combination provided you follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], and only use the above OVA templates supported for UCS C200 M2 TRC#1.

 

 

==== Special Rules for non-UC and 3rd-party Co-residency ====

See the tables after these rules for the co-residency policy of each Cisco UC app.

Non-UC VMs and 3rd-party app VMs that will be co-resident with Cisco UC app VMs are required to align with all of the following:

*[http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml TAC Technote Document ID: 113520.] For other details on co-resident application performance troubleshooting, see [[Troubleshooting and Performance Monitoring Virtualized Environments]].
*[[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]
*All of the special rules below.

 

 

:'''"Matching" Support Policies'''
:All co-resident VMs must follow the '''"Matching" Support Polices''' rule in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. www.cisco.com/go/uc-virtualized does not describe policies for Cisco non-UC apps or 3rd-party apps

 

:'''Virtual Machine Templates'''
:Cisco non-UC VMs and 3rd-party app VMs own definition of their supported VM OVA templates (or specs for one to be created), similar to what Cisco UC app VMs require in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. http://www.cisco.com/go/uc-virtualized does not describe VM templates for Cisco non-UC apps or 3rd-party apps.

 

:'''CPU'''
:All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''CPU''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]].

 

:'''Memory/RAM'''
:*To enforce "no memory oversubscription", each co-resident VM - whether UC, non-UC or 3rd-party - must have a reservation for vRAM that includes all the vRAM of the virtual machine. For example, if you have a virtual machine that is configured with 4GB of vRAM, then that virtual machine must also have a reservation of 4 GB of vRAM.
:*Otherwise all co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Memory/RAM''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. The 2 GB for VMware vSphere is in addition to the sum of the vRAM reservations for the VMs.

 

:'''Storage'''
:*Non-UC VMs and 3rd-party app VMs must define their storage capacity requirements (ideally in an OVA template) and storage performance requirements. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Storage''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient disk space, IOPS and low latency to handle the total VM load.
:*If DAS storage is to be used with non-UC / 3rd-party app VMs, it is highly recommended that pre-deployment testing be conducted, where all VMs are pushed to their highest level of IOPS generation. This is due to DAS environments being more capacity/performance-constrained in general, more dependent on adapter caches in RAID controllers, and Cisco DAS testing only done for UC apps on UCS Tested Reference Configurations.

 

:'''Network/LAN'''
:*Non-UC VMs and 3rd-party app VMs must define the network capacity/performance requirements of their VM OVA templates. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Network/LAN''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient physical interfaces.

 

 

=== Table of Co-residency Support Policy by Cisco UC Application ===

==== Call Processing and System Management Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Unified Communications Manager (1)
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| [[Cisco Unified Communications Manager Business Edition 6000|Limited]]
|-
| Cisco Emergency Responder
| UC with UC only
|-
| Session Manager Edition
|
*8.6(2)+: Full
*8.5(1) to 8.6(1): UC with UC only

|-
| Intercompany Media Engine
| Full
|-
| Unified Attendant Consoles
| UC with UC only
|-
| UC Management Suite (OM, SM, SSM, PM)
| Full
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

==== Messaging and Presence Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Cisco Unity Connection
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| Cisco Unity
| Full 
{{note|Cisco Unity requires CPU Affinity which may not be desirable for other applications co-resident with Unity.}}

|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
|
*8.6(1)+: Full
*8.0(2) to 8.5: UC with UC only

|}

 

==== Contact Center Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
|
*8.5(x): Full
*8.0(x): UC with UC only

|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO) components (WFM, QM, AQM, CR, etc.)]
|
*8.5(2)+: Full
*8.0(2) to 8.5(1): UC with UC only

|-
| [[Unified Contact Center Enterprise]] components and deployment models 
| [[Virtualization for Unified CCE|Limited ]]
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| [[Virtualization for Unified Intelligence Center|Limited]]
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| UC with UC only
|-
| [[Unified Customer Voice Portal]] (all components) 
| [[Virtualization for Unified CVP|Limited]]
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| UC with UC only
|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
| UC with UC only
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
| UC with UC only
|}

== Redundancy and Failover Considerations ==

Application-layer considerations (such as Unified CM Cluster over WAN or Unified CCE Remote Redundancy) are the same for virtualized (UC on UCS) or non-virtualized (MCS 7800) deployments.

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:

*Avoid placing a primary VM and a backup VM on the same server, chassis or site
*For failover groups, avoid placing all actives on the same server, chassis or site
*Avoid placing all VMs of the same role on the same server, chassis or site

 

== Network, QoS and Shared Storage Design Considerations ==

See [[QoS Design Considerations for Virtual UC with UCS|'''QoS Design Considerations for Virtual UC with UCS''']] and '''[[Shared Storage Considerations]]'''.

 

== Sizing Examples ==

This section shows a sample system configuration based on following the [[High-level Checklist for Design and Implementation]] for the following set of customer requirements:

*'''General Requirements'''
**Three sites - Headquarters (HQ) and two Branches (A and B)
**CUCM and Applications located at each site
**Up to 30,000 lines per sites
**100+ sites
**Transparent use of PSTN if IP WAN unavailable
*'''Headquarters (HQ) Requirements'''
**12K Phones, use Cisco TFTP server
**10K Messaging users
**10K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 240 agents and 10 supervisors
*'''Branch A Requirements'''
**2K Phones, use Cisco TFTP server
**2K Messaging users
**2K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 145 agents and 5 supervisors
*'''Branch B Requirements'''
**500 Phones, use Cisco TFTP server
**500 Messaging users
**500 users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 45 agents and 5 supervisors

 After going through the design process, the following servers were selected to host the virtualized UC applications:

*Six Cisco UCS B200 Blade Servers for HQ (running in a UCS 5100 Chassis connected to UCS 6100 Fabric Interconnect Switches), using TRC#1 (UCS-B200M2-VCS1).
*Three Cisco UCS C210 General-Purpose Rack-Mount Servers for Branch A, using TRC#1 (UCS-C210M2-VCD2)
*Two Cisco UCS C200 General-Purpose Rack-Mount Servers for Branch B, using TRC#1 UCS-C200M2-VCD2)
*Note this example does not include non-UC applications (such as [http://www.cisco.com/go/nexus1000v Cisco Nexus 1000V] or Cisco Network Registrar) or 3rd-party applications such as customer-provided DNS / DHCP / TFTP servers, directories, email, groupware or other business applications. These applications need to run on separate physical servers and are not allowed to be co-resident with UC at this time. See the Co-residency section on this page for more details.

[[Image:UCVirtualSizingEx1.jpg]]

 See below for details on the server layout and application/VM placement at each site. Note that Branch B is using UCS C200 M2 TRC #1 so has restrictions on which VM OVAs were able to be used.

'''HQ server detail:'''

[[Image:UCVirtualSizingEx2.jpg]]

'''Branch A server detail:'''

[[Image:UCVirtualSizingEx3.jpg]]

'''Branch B server detail:'''

[[Image:UCVirtualSizingEx4.jpg]]

== Sizing and Ordering Tools ==

The suite of tools listed below can assist you with the sizing, configuring and quoting of Cisco Unified Communications solutions on the Unified Computing System.

=== Cisco Solution Expert ===

[http://www.cisco.com/go/sx| Cisco Solution Expert] assists Cisco field and Cisco Unified Communications specialized channel partners in designing and quoting UC on UCS solutions using the Cisco Unified Workspace Licensing or the traditional design model. Solution Expert delivers a Bill of Materials for the Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUS.

=== Netformx DesignXpert ===

[http://www.cisco.com/go/designxpert Netformx DesignXpert] is a third party application used to design and quote the Cisco Unified Computing System B-series. DesignXpert has two advisor modules that can be used to quote a Unified Communications solution with the Unified Computing System:

::*UC Advisor – a designing and quoting solution used to quote Unified Communications software. The UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs can be quoted when ordering separate from the Unified Computing System. Other UCS B-series components must be configured via UCS Advisor below.
::*UCS Advisor - a design and quoting solution for all UCS B-series components including Blade Servers ordered as Collaboration or Data Center SKUs, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

=== Cisco Unified Communications Sizing Tool ===

[http://tools.cisco.com/cucst Cisco Unified Communications Sizing Tool] delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

=== Cisco Configuration Tool ===

Cisco Configuration Tool '''(need link here)''' is part of the suite of Internet Commerce Tools for managing online ordering of Cisco products. It enables you to configure products and view lead times and prices for each selection. The Cisco Configuration Tool, also known as the Dynamic Configuration Tool, is used to configure the Unified Communications products and the B series SKU and VMWare ordered as Collaboration SKUs.

=== Ordering Guides ===

Ordering Guides for Unified Communications System 8.x releases are available for Cisco sales, partners, and customers.

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Sizing Guidelines

2012-05-11T20:28:25Z

Jkratky: /* Application Co-residency Support Policy */

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

== Introduction ==

This article provides specifics and examples to aid in sizing Unified Communications applications for the UCS B-series and C-series servers.

 

== Application Co-residency Support Policy ==

Cisco UC virtualization only supports application co-residency under the specific conditions described below and as clarified [http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml in TAC Technote Document ID: 113520.].

 This policy only covers the rules for physical/virtual hardware sizing, co-resident application mix and maximum VM count per physical server. All other UC virtualization rules still apply (e.g supported VMware vSphere ESXi versions or hardware options). Co-residency rules apply equally to all hardware options:

*[[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]
*[[Specification-Based Hardware Support|UC on UCS Specs-based]]
*[[Specification-Based Hardware Support|HP/IBM Specs-based]]

 

{{note | UC app VM performance is only guaranteed when installed on a [[Tested Reference Configurations (TRC) | UC on UCS Tested Reference Configuration]], and only if all other conditions in this policy are followed.}} 

"Application co-residency" in this UC support policy is defined as VMs sharing the same physical server and the same virtualization software host:

*E.g. VMs running on the same VMware vSphere ESXi host on the same physical rack-mount server, such as Cisco UCS C-Series.
*E.g. VMs running on the same VMware vSphere ESXi host on the same physical blade server in the same blade server chassis, such as Cisco UCS B-Series.
*"Co-resident application mix" in this UC support policy refers to the set of VMs sharing a physical server and a virtualization software host.
*VMs running on different virtualization hosts and different physical servers are not co-resident.
**E.g. VMs running on two different Cisco UCS C-Series rack-mount servers are not co-resident.
**E.g. VMs running on two different Cisco UCS B-Series blade servers in the same UCS 5100 blade server chassis are not co-resident.

[[Image:UConUCS co-res 1 whatis.JPG|Co-residency defined]] 

[[Image:600px-UConUCS_co-res_1_whatis.jpg]] Virtual Machines (VMs) are categorized as follows for purposes of this UC support policy:

*Cisco UC app VMs (or simply '''UC app VMs'''): a VM for one of the Cisco UC apps at [[Unified Communications Virtualization Supported Applications]].
*Cisco non-UC app VMs (or simply '''non-UC VMs'''): a VM for a Cisco application not listed at [[Unified Communications Virtualization Supported Applications]], such as the VM for Cisco Nexus 1000V's VSM.
*3rd-party application VMs (or simply '''3rd-party app VMs'''): a VM for a non-Cisco, application, such as VMware vCenter, 3rd-party Cisco Technology Developer Program applications, non-Cisco-provided TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, customer home-grown applications, etc.

 

{{note | Cisco does not support non-UC or 3rd-party applications VMs running on "Cisco UC Virtualization Hypervisor" or "Cisco UC Virtualization Foundation" (as described at [[Unified Communications VMware Requirements]]). If you want to deploy non-U / 3rd-party applications, you must deploy on VMware vSphere Standard, Advanced, Enterprise or Enterprise Plus Edition. }} 

Each Cisco UC app supports one of the following four types of co-residency: 

{{note | Troubleshooting UC VMs co-resident with non-UC/3rd-party app VMs may require the changes described at <<in this TAC Technical Tip>>. . To be supported by Cisco TAC, customers must agree to these changes if required by Cisco TAC.}} 

#'''None:''' Co-residency is not supported. The UC app only supports a single instance of itself in a single VM on the virtualization host / physical server. No co-residency with ANY other VM is allowed, whether Cisco UC app VM, Cisco non-UC VM, or 3rd-party application VM.
#'''Limited:''' The co-resident application mix is restricted to specified VM combinations only. Click on the "Limited" entry in the tables below to see which VM combinations are allowed. Co-residency with any VMs outside these combinations - including other Cisco VMs - is not supported (these applications must be placed on a separate physical server). The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] listed below.
#'''UC with UC only:''' The co-resident application mix is restricted to VMs for UC apps listed at [[Unified Communications Virtualization Supported Applications]]. Co-residency with Cisco non-UC VMs and/or 3rd-party application VMs is not supported; those VMs must be placed on a separate physical server. The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below.
#'''Full:''' The co-resident application mix may contain UC app VMs with Cisco non-UC VMs with 3rd-party application VMs. The deployment must follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below. The deployment must also follow the [[#Special_Rules_for_non-UC_and_3rd-party_Co-residency|Special Rules for non-UC and 3rd-party Co-residency]] below.

 

[[Image:UConUCS co-res 2 types.JPG|Types of Co-residency]] 

 

==== General Rules for Co-residency and Physical/Virtual Hardware Sizing ====

See the tables after the rules for the co-residency policy of each UC app. 

{{note | Remember that virtualization and co-residency support varies by UC app '''version''', so don't forget to double-check inter-UC-app version compatibility, see [http://www.cisco.com/go/unified-techinfo Cisco Unified Communications System Documentation].}} 

:'''"Matching" Support Policies'''

All co-resident applications must "match" in the following areas:

*Same "server" support for compute/network/storage hardware (see [[Unified Communications Virtualization Supported Applications]])
**E.g. if you want to host co-resident apps on UCS C260 M2 TRC#1, all co-resident apps must have a hardware support policy that permits this.
**E.g. if you want to deploy instead as [[Specification-Based Hardware Support|UC on UCS Specs-based]] with a diskless UCS C260 M2 and a SAN/NAS storage array, all co-resident apps must support this.
**You must pick a hardware option that all the co-resident apps can support. For example, some UC apps do not support [[Specification-Based Hardware Support]] | Specs-based for UC on UCS or HP/IBM]], some UC apps do not support certain Tested Reference Configurations such as UC on UCS C200 M2 TRC#1 (as opposed to [[Specification-Based Hardware Support|UC on UCS C200 M2 specs-based]]).
*Same support for virtualization software product and version.
**E.g. one app supports vSphere 5.0, the other app only supports vSphere 4.1. vSphere 5.0 may not be used for this co-resident application mix.
*All apps must support a co-residency policy that permits the desired co-resident application mix.
**E.g. one app has a "Full" policy, another app has "UC with UC" policy. Co-resident non-UC or 3rd-party app VMs are not allowed.
**E.g. one app has a "UC with UC" policy, another app has "Limited" policy. Even though all apps will be UC, the desired combination may not be allowed by the "Limited" app.
**E.g. one app has "None" policy. No other apps can be co-resident with this app regardless of their policies.
*If support policies of a given co-resident app mix do not match, then the "least common denominator" is required.

 

:'''Virtual Machine Templates'''

All UC applications must use a supported virtual machine OVA template from [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. 

:'''No Hardware Oversubscription'''

All VMs require a one to one mapping between virtual hardware and physical hardware. See specifics below. 

::'''CPU'''

*Must map 1 VM vCPU core to 1 physical CPU core.
**For example, if you have a host with 12 total physical cores, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 12.
**The requirement is based on ''physical'' cores, not ''logical'' cores. If the physical CPU supports hyper-threading, this should be enabled, but for purposes of UC sizing the max number of vCPU cores is still limited to the number of ''physical'' cores.
*Cisco Unity VMs also require VMware CPU Affinity.
*If there is at least one live Unity Connection VM on the physical server, then one CPU core per physical server must be left unused (it is actually being used by ESXi scheduler).
**For example, if you have a host with 12 total physical cores and one or more of the VMs on that host will be Unity Connection, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 11, with the 12th core left unused. This is regardless of how many Unity Connection VMs are on that host.

::[[Image:UConUCS co-res 3 UCxn 1core unused.JPG|Leaving 1 core unused for Cisco Unity Connection]]

*CPU reservations on the VMs are not required. Use of CPU reservations in lieu of one-to-one CPU core mappings is not supported.
**Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation.
**For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported.

 

::'''Memory/RAM'''

*Must map 1 GB of VM vRAM to 1 GB of physical RAM. Memory oversubscription is not supported for Cisco UC VMs.
*The sum of virtual machines' vRAM may not exceed the total physical memory on the physical server.
*Additional 2 GB of physical RAM must be provisioned for VMware ESXi itself (this is to cover ESXi overhead to run VMs; for more details see [http://pubs.vmware.com/vsp40_e/resmgmt/wwhelp/wwhimpl/common/html/wwhelp.htm#href=r_overhead_memory_on_virtual_machines.html&single=true "Understanding Memory Overhead" on vmware.com]).

 

 

::'''Storage'''

The following apply to supported DAS, SAN and NAS storage

*Must map 1 GB of VM vDisk to 1 GB of physical storage.
**Storage thin provisioning is not supported (whether at VM layer or storage array layer).
**Any other form of storage oversubscription is not supported.
**The sum of virtual machines' vDisks may not exceed the physical disk space of the physical server's logical volume capacity (i.e. capacity net of overhead for the VM itself, VMFS in vSphere and physical RAID configuration).
**Cisco recommends 10% buffer on top of vDisk values to handle overhead within the VM (such as swap files which are the size of the VM's vRAM). See [[Shared Storage Considerations]] for more details.
*The DAS, NAS or SAN storage solution must also supply enough performance to handle the total load of the VMs.
**Must provide enough IOPS to handle sum of the VMs.
**Kernel command latency must not exceed 2-3 milliseconds.
**Physical device command latency must not exceed 15-20 milliseconds.
**See [[Shared Storage Considerations]] and [[IO Operations Per Second (IOPS)|Storage Performance Requirements]] for more details.
*If the above capacity or performance requirements are not met, the storage system is overloaded and must be "fixed" by either moving virtual machines to alternate storage, or improving storage hardware.

 

::'''Network/LAN'''

*The aggregate networking load of the co-resident virtual machines must be met with the physical networking interface(s) on the host.
*See the UC application design guides (http://www.cisco.com/go/srnd) to size network utilization by UC app VMs. In general, most UC app VMs will not saturate a 1GbE link. Deployments leveraging non-FC-storage (iSCSI, NFS or Unified Fabric/FCoE including UCS B-Series FEX) must account for network traffic from both VM LAN access and VM storage access.
*For other network hardware best practices, see [[QoS Design Considerations for Virtual UC with UCS]].
*If the above capacity or performance requirements are not met, the networking hardware is congested and must be "fixed" by either moving virtual machines to a host with different network access, or provisioning more physical network interfaces.

 

::'''Maximum VM Count per Physical Server'''

*For hardware other than UCS C200 M2 TRC#1, you may mix and match Cisco UC app VM size and quantity as long as you follow all of the sizing rules described above. The maximum number of virtual machines per physical server that can be supported depends on several factors:
*"Capacity" of physical server hardware vs. the quantity and resource usage of [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|VM OVA templates]].
**E.g. using the above physical/virtual sizing rules for CPU, a physical server with 8 total physical cores can only host 4 of the "CUCM 7.5K user OVAs" since those are 2 vCPU each. If the physical server instead had 20 total physical cores, it could host 10 of these VMs (assuming memory, network and storage hardware are also sufficient using the UC sizing rules immediately below).
**All [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configurations]] are sized for co-residency except for UCS C210 M1 Tested Reference Configuration #1 (which is only sized to host a single CUCM VM of 7500 user capacity). Note UCS C200 M2 Tested Reference Configuration #1 has special restrictions on choice of UC VM, and its allowed VMs are at lower capacity per VM than for other Tested Reference Configurations.
**[[Specification-Based Hardware Support|UC on UCS Specs-based and HP/IBM Specs-based]] deployments allow hardware options that may support a higher or lower max VM count than a [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]. E.g. UCS C210 M2 TRC#1 is a dual-4-core CPU, but UCS C210 M2 specs-based could be configured with dual-6-core (for possibly more VMs) or a single 4-core (for possibly a single VM).
*Note the max VM count may also be further restricted by UC apps that only support "Limited" co-residency as described in the tables after the rules.

[[Image:UConUCS co-res 4 max VM count.JPG|Maximum VM count per physical server]] 

 

::'''Special Requirements for UCS C200 M2 TRC#1 Hardware'''

{{note | This section is only for [[Tested Reference Configurations (TRC)|UC on UCS C200 M2 Tested Reference Configuration #1 which uses Intel E5506 / 2.13 GHz CPU]]. UCS C200 M2 configured with a faster CPU (via [[Specification-Based Hardware Support]]) does not need to follow the rules in this section.}}

*For UCS C200 M2 TRC #1, there are additional TRC-specific restrictions since it uses a slower CPU than other TRCs or specs-based (i.e. E5506 / 2.13 GHz instead of CPU with 2.53 GHz speed or higher). A C200 M2 configured with a different CPU allowed by [[Specification-Based Hardware Support|UC on UCS Specs-based]] does not have these TRC-specific restrictions. Follow these rules for UCS C200M2 TRC#1 with E5506 / 2.13 GHz CPU:
**The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
***CUCM - Unified Communications Manager 1000 users
***CER - Emergency Responder 12,000 users
***CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
***CUP - Unified Presence 1000 users
***CUCCX - Unified Contact Center Express 100 agents
***CUxAC - Unified Department, Business and Enterprise Attendant Consoles
***Other unlisted OVA templates are not supported on C200 M2 TRC #1.
**Otherwise at this time the following co-residency scenarios are supported:
***Any combination allowed by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]].
***Any other combination provided you follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], and only use the above OVA templates supported for UCS C200 M2 TRC#1.

 

 

==== Special Rules for non-UC and 3rd-party Co-residency ====

See the tables after these rules for the co-residency policy of each Cisco UC app.

Non-UC VMs and 3rd-party app VMs that will be co-resident with Cisco UC app VMs are required to align with all of the following:

*[http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml TAC Technote Document ID: 113520.] For other details on co-resident application performance troubleshooting, see [[Troubleshooting and Performance Monitoring Virtualized Environments]].
*[[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]
*All of the special rules below.

 

 

:'''"Matching" Support Policies'''
:All co-resident VMs must follow the '''"Matching" Support Polices''' rule in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. www.cisco.com/go/uc-virtualized does not describe policies for Cisco non-UC apps or 3rd-party apps

 

:'''Virtual Machine Templates'''
:Cisco non-UC VMs and 3rd-party app VMs own definition of their supported VM OVA templates (or specs for one to be created), similar to what Cisco UC app VMs require in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. http://www.cisco.com/go/uc-virtualized does not describe VM templates for Cisco non-UC apps or 3rd-party apps.

 

:'''CPU'''
:All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''CPU''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]].

 

:'''Memory/RAM'''
:*To enforce "no memory oversubscription", each co-resident VM - whether UC, non-UC or 3rd-party - must have a reservation for vRAM that includes all the vRAM of the virtual machine. For example, if you have a virtual machine that is configured with 4GB of vRAM, then that virtual machine must also have a reservation of 4 GB of vRAM.
:*Otherwise all co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Memory/RAM''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. The 2 GB for VMware vSphere is in addition to the sum of the vRAM reservations for the VMs.

 

:'''Storage'''
:*Non-UC VMs and 3rd-party app VMs must define their storage capacity requirements (ideally in an OVA template) and storage performance requirements. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Storage''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient disk space, IOPS and low latency to handle the total VM load.
:*If DAS storage is to be used with non-UC / 3rd-party app VMs, it is highly recommended that pre-deployment testing be conducted, where all VMs are pushed to their highest level of IOPS generation. This is due to DAS environments being more capacity/performance-constrained in general, more dependent on adapter caches in RAID controllers, and Cisco DAS testing only done for UC apps on UCS Tested Reference Configurations.

 

:'''Network/LAN'''
:*Non-UC VMs and 3rd-party app VMs must define the network capacity/performance requirements of their VM OVA templates. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Network/LAN''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient physical interfaces.

 

 

=== Table of Co-residency Support Policy by Cisco UC Application ===

==== Call Processing and System Management Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Unified Communications Manager (1)
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| [[Cisco Unified Communications Manager Business Edition 6000|Limited]]
|-
| Cisco Emergency Responder
| UC with UC only
|-
| Session Manager Edition
|
*8.6(2)+: Full
*8.5(1) to 8.6(1): UC with UC only

|-
| Intercompany Media Engine
| Full
|-
| Unified Attendant Consoles
| UC with UC only
|-
| UC Management Suite (OM, SM, SSM, PM)
| Full
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

==== Messaging and Presence Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| Cisco Unity Connection
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| Cisco Unity
| Full 
{{note|Cisco Unity requires CPU Affinity which may not be desirable for other applications co-resident with Unity.}}

|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
|
*8.6(1)+: Full
*8.0(2) to 8.5: UC with UC only

|}

 

==== Contact Center Applications ====

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px"
|-
! UC Application
! Co-residency Support
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
|
*8.5(x): Full
*8.0(x): UC with UC only

|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO) components (WFM, QM, AQM, CR, etc.)]
|
*8.5(2)+: Full
*8.0(2) to 8.5(1): UC with UC only

|-
| [[Unified Contact Center Enterprise]] components and deployment models 
| [[Virtualization for Unified CCE|Limited ]]
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| [[Virtualization for Unified Intelligence Center|Limited]]
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| UC with UC only
|-
| [[Unified Customer Voice Portal]] (all components) 
| [[Virtualization for Unified CVP|Limited]]
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| UC with UC only
|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
| UC with UC only
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
| UC with UC only
|}

== Redundancy and Failover Considerations ==

Application-layer considerations (such as Unified CM Cluster over WAN or Unified CCE Remote Redundancy) are the same for virtualized (UC on UCS) or non-virtualized (MCS 7800) deployments.

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:

*Avoid placing a primary VM and a backup VM on the same server, chassis or site
*For failover groups, avoid placing all actives on the same server, chassis or site
*Avoid placing all VMs of the same role on the same server, chassis or site

 

== Network, QoS and Shared Storage Design Considerations ==

See [[QoS Design Considerations for Virtual UC with UCS|'''QoS Design Considerations for Virtual UC with UCS''']] and '''[[Shared Storage Considerations]]'''.

 

== Sizing Examples ==

This section shows a sample system configuration based on following the [[High-level Checklist for Design and Implementation]] for the following set of customer requirements:

*'''General Requirements'''
**Three sites - Headquarters (HQ) and two Branches (A and B)
**CUCM and Applications located at each site
**Up to 30,000 lines per sites
**100+ sites
**Transparent use of PSTN if IP WAN unavailable
*'''Headquarters (HQ) Requirements'''
**12K Phones, use Cisco TFTP server
**10K Messaging users
**10K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 240 agents and 10 supervisors
*'''Branch A Requirements'''
**2K Phones, use Cisco TFTP server
**2K Messaging users
**2K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 145 agents and 5 supervisors
*'''Branch B Requirements'''
**500 Phones, use Cisco TFTP server
**500 Messaging users
**500 users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 45 agents and 5 supervisors

 After going through the design process, the following servers were selected to host the virtualized UC applications:

*Six Cisco UCS B200 Blade Servers for HQ (running in a UCS 5100 Chassis connected to UCS 6100 Fabric Interconnect Switches), using TRC#1 (UCS-B200M2-VCS1).
*Three Cisco UCS C210 General-Purpose Rack-Mount Servers for Branch A, using TRC#1 (UCS-C210M2-VCD2)
*Two Cisco UCS C200 General-Purpose Rack-Mount Servers for Branch B, using TRC#1 UCS-C200M2-VCD2)
*Note this example does not include non-UC applications (such as [http://www.cisco.com/go/nexus1000v Cisco Nexus 1000V] or Cisco Network Registrar) or 3rd-party applications such as customer-provided DNS / DHCP / TFTP servers, directories, email, groupware or other business applications. These applications need to run on separate physical servers and are not allowed to be co-resident with UC at this time. See the Co-residency section on this page for more details.

[[Image:UCVirtualSizingEx1.jpg]]

 See below for details on the server layout and application/VM placement at each site. Note that Branch B is using UCS C200 M2 TRC #1 so has restrictions on which VM OVAs were able to be used.

'''HQ server detail:'''

[[Image:UCVirtualSizingEx2.jpg]]

'''Branch A server detail:'''

[[Image:UCVirtualSizingEx3.jpg]]

'''Branch B server detail:'''

[[Image:UCVirtualSizingEx4.jpg]]

== Sizing and Ordering Tools ==

The suite of tools listed below can assist you with the sizing, configuring and quoting of Cisco Unified Communications solutions on the Unified Computing System.

=== Cisco Solution Expert ===

[http://www.cisco.com/go/sx| Cisco Solution Expert] assists Cisco field and Cisco Unified Communications specialized channel partners in designing and quoting UC on UCS solutions using the Cisco Unified Workspace Licensing or the traditional design model. Solution Expert delivers a Bill of Materials for the Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUS.

=== Netformx DesignXpert ===

[http://www.cisco.com/go/designxpert Netformx DesignXpert] is a third party application used to design and quote the Cisco Unified Computing System B-series. DesignXpert has two advisor modules that can be used to quote a Unified Communications solution with the Unified Computing System:

::*UC Advisor – a designing and quoting solution used to quote Unified Communications software. The UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs can be quoted when ordering separate from the Unified Computing System. Other UCS B-series components must be configured via UCS Advisor below.
::*UCS Advisor - a design and quoting solution for all UCS B-series components including Blade Servers ordered as Collaboration or Data Center SKUs, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

=== Cisco Unified Communications Sizing Tool ===

[http://tools.cisco.com/cucst Cisco Unified Communications Sizing Tool] delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

=== Cisco Configuration Tool ===

Cisco Configuration Tool '''(need link here)''' is part of the suite of Internet Commerce Tools for managing online ordering of Cisco products. It enables you to configure products and view lead times and prices for each selection. The Cisco Configuration Tool, also known as the Dynamic Configuration Tool, is used to configure the Unified Communications products and the B series SKU and VMWare ordered as Collaboration SKUs.

=== Ordering Guides ===

Ordering Guides for Unified Communications System 8.x releases are available for Cisco sales, partners, and customers.

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

MediaWiki:Sitenotice

2012-05-01T17:52:15Z

Jkratky:

DocWiki will be unavailable Friday, May 4th from 11:30PM EST until Saturday May 5th, 8AM EST.

MediaWiki:Sitenotice

2012-05-01T17:51:02Z

Jkratky:

DocWiki will be unavailable on Friday, May 4th beginning at 11:30PM EST to Saturday May 5th, 8AM EST.

MediaWiki talk:Sitenotice

2012-05-01T17:50:53Z

Jkratky: Blanked the page

MediaWiki talk:Sitenotice

2012-05-01T17:49:12Z

Jkratky: Created page with "DocWiki will be unavailable on Friday, May 4th beginning at 11:30PM EST to Saturday May 5th, 8AM EST."

DocWiki will be unavailable on Friday, May 4th beginning at 11:30PM EST to Saturday May 5th, 8AM EST.

Category:Network Management

2012-04-20T16:35:02Z

Jkratky:

[[Category:Technologies]]
[[Category:Cisco Products]]

Category:Network Management

2012-04-20T16:34:53Z

Jkratky:

[[Category:Technologies]]
[[Category:Products]]

Template:Configuration Example IPv6/Preload

2012-04-13T19:56:10Z

Jkratky:

==Introduction==



==Design==



[[Image:sample_topology.jpg]]

==Configuration==



==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.



==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]

G.8032 Ethernet Ring Protection (ERP) Administrative Procedures

2012-04-10T16:26:47Z

Jkratky:

= G.8032 Ethernet Ring Protection Administrative Procedures =

This article contains information about commonly performed administrative procedures for provisioning and maintaining a G.8032-supported Ethernet Ring Protection (ERP) switching configuration. These administrative procedures include:

*Changes to VLANs (protected or unprotected) within ring instances.   
*Changes to ring instances.

:The specific ring instances, and the VLANs they contain, may experience a brief traffic outage (also known as a switch-over) while the procedure is being performed. Traffic outages to the VLANs can be mimimized by first migrating the VLANs to a different ring instance.

*Changes to the physical nodes, links, and the ring topology (for example, changing a ring from open to closed).

:When making changes to physical nodes, links, and the ring topology, all ring instances experience brief traffic outages (switch-overs). 

:When converting an open-ring topology to a closed-ring topology (or a closed-ring topology to an open-ring topology), the entire ring must be disabled.

== General Goals for Any Administrative Procedure ==

When administering a G.8032 Ethernet Protection Ring (ERP) switching configuration, keep the following goals in mind:

*Avoid creating a network loop.
*Minimize the extent of any traffic outages (switch-overs).
*Avoid letting the Ring Automatic Protection Switching (R-APS) control channel become dormant (inactive).  A dormant R-APS control channel may cause a Failure of Protocol — Time-out (FOP-TO) signal to be triggered by the nodes on the ring.
*Minimize the number of brief traffic outages (switch-overs).

 

=== VLAN Procedures ===

This section contains the procedures for creating and maintaining VLANs in an Ethernet ring topology, and explains how to:

*Add a VLAN to the inclusion list for a ring. (Once a VLAN is added to the inclusion list, the VLAN is considered "protected.")
*Add a VLAN to the exclusion list for a ring.
*Remove a VLAN from the inclusion list of a ring instance or from the exclusion list of a physical ring.
*Move a VLAN to a different ring instance.

The specific VLANs may experience brief traffic outages (switch-overs) while changes to the VLANs are being performed.

Also, these procedures assume that a physical ring with at least one instance has been configured for all nodes in the ring. For more information, see the [[#Ring_Instance_Procedures|Ring Instance Procedures]] section and the [[#Physical_Ring_Procedures|Physical Ring Procedures]] section.  

 

==== Adding a VLAN to the Inclusion List for a Ring ====

Once a VLAN is added to the inclusion list, the VLAN is considered "protected."

#Confirm that the VLAN is unused on (removed from)  all ring instances on all nodes. An unused VLAN is one that is not included in any inclusion or exclusion list (and is, therefore, blocked by the ring node). 
#Add the VLAN to the inclusion list of the desired ring instance on the Ring Protection Link (RPL) owner.  This VLAN remains blocked.
#Add the VLAN to the inclusion list of all other nodes on the ring.  This VLAN is unblocked as it is added to each node on the ring. 

 

==== Adding a VLAN to the Exclusion List for a Ring ====

#Confirm that the VLAN is unused on (removed from) all rings on all nodes. An unused VLAN is one that is not included in any inclusion or exclusion list (and is, therefore, blocked by the ring node). 
#Add the VLAN to the exclusion list for the appropriate nodes on the ring.  The VLAN becomes unblocked as it is added to each node. Ensure that a manual break remains in the forwarding path around the ring; otherwise, a network loop is created. 

==== Removing a VLAN from the Inclusion List of a Ring Instance or the Exclusion List of a Physical Ring ====

#Remove the VLAN from the inclusion list of a ring instance, or from the exclusion list for all non-RPL owner nodes on the physical ring.  The VLAN becomes unused and is, therefore, blocked by each node.
#Remove the VLAN from the inclusion list of a ring instance or from the exlusion list for the RPL owner node on the physical ring.  The VLAN becomes unused and is, therefore, blocked.

 

==== Moving a VLAN to a Different Ring Instance ====

A ring containing G.8032 V1 nodes can support one ring instance only.  This procedure applies to rings comprised entirely of G.8032 V2 nodes only.

#Complete the [[#Removing_a_VLAN_from_the_Inclusion_List_of_a_Ring_Instance_or_the_Exclusion_List_of_a_Physical_Ring|Remove a VLAN from the Inclusion List of a Ring Instance or the Exclusion List of a Physical Ring]] procedure.
#Complete the [[#Adding_a_VLAN_to_the_Inclusion_List_for_a_Ring|Adding a VLAN to the Inclusion List for a Ring]] procedure. 

=== Ring Instance Procedures ===

This section contains the procedures for creating and maintaining ring instances in a ring topology.  These procedures assume that a physical ring has been created and has been configured. For information about creating a physical ring, see the [[#Physical_Ring_Procedures|Physical Ring Procedures]] section.  

This section explains how to:

*Create a new ring instance on the Ethernet ring.
*Delete a ring instance on the Ethernet ring.
*Change the Automatic Protection Switching (APS) settings for a ring instance.
*Move the Ring Protection Link (RPL) to a new node on the Ethernet ring.
*Change the profile settings for the ring instance.

The specific ring instances and the VLANs that they contain may experience brief traffic outages (switch-overs) while these procedures are being performed. Traffic outages to the VLANs can be mimimized by first migrating the VLANs to a different ring instance.

 

==== Creating a Ring Instance on the Ethernet Ring ====

#Choose an unused VLAN to use for the Automatic Protection (APS) Switching channel.  An unused VLAN is one that is not included in any inclusion or exclusion list (and is, therefore, blocked by the Ethernet ring node).
#Choose one link and one node to be the Ring Protection Link (RPL) and RPL owner, respectively.
#Configure a ring instance on each of the non-RPL owner nodes.
#Configure a ring instance on the RPL owner node; the ring instance transitions to the idle state after the Wait-to-Restore timer expires or after a reversion has occurred.
#Add one or more VLANs to the ring instance by following the procedure in the [[#Adding_a_VLAN_to_the_Inclusion_List_for_a_Ring|Adding a VLAN to the Inclusion List for a Ring]] section.  

 

==== Deleting a Ring Instance on the Ethernet Ring ====

#Remove all VLANs from the ring instance by following the procedure in the  [[#Removing_a_VLAN_from_the_Inclusion_List_of_a_Ring_Instance_or_the_Exclusion_List_of_a_Physical_Ring|Removing a VLAN from the Inclusion List of Ring Instance or the Exclusion List of a Physical Ring]] section.
#Delete the ring instance from the non-Ring Protection Link (RPL) owner nodes.
#Delete the ring instance from the RPL owner node.

 

==== Changing the APS Settings for a Ring Instance ====

A ring instance cannot be in use while you are changing the Automatic Protection Swithing (APS) settings.  If the VLANs on the ring instance need to remain in use, move the VLANs to a different instance.  See the [[#Moving_a_VLAN_to_a_Different_Ring_Instance|Moving a VLAN to a Different Ring Instance]] section.

#Complete the [[#Deleting_a_Ring_Instance_on_the_Ethernet_Ring|Deleting a Ring Instance on the Ethernet Ring]] procedure.
#Complete the [[#Creating_a_Ring_Instance_on_the_Ethernet_Ring|Creating a Ring Instance on the Ethernet Ring]] procedure using the new APS VLAN.

 

==== Moving the RPL to a New Node on the Ethernet Ring ====

#Apply a manual switch on the new node of the Ring Protection Link (RPL) owner and the RPL.  The Ethernet ring will be in Manual Switch (MS) state.
#On the existing RPL owner node, remove the RPL owner configuration.  Removing the RPL owner configuration causes the Finite State Machine (FSM) state to reset and the node to become a "normal" node.  The Ethernet ring remains in the MS state.
#On the node now identified as the new RPL owner, clear the manual switch. Clearing the manual switch causes the ring to go into the pending state.
#Configure the node as the RPL owner.  Configuring the node as the RPL owner causes the FSM to reset and the node begins transmitting No Request (NR) RPL Blocked (RB) messages rather than NR messages.  The Ethernet ring goes into the idle state.  The Automatic Protection Switching (APS) channel will be dormant during the time required to complete Step 4.  Normally, Step 4 can be done by using the '''rpl''' command in Ethernet ring instance configuration mode (config-erp-inst), in which case the APS channel will not be dormant. 

==== Changing the Profile Settings for the Ring Instance ====

Profile settings that can be changed include the hold-off timer duration, the Wait-to-Restore (WTR) timer duration, and the reversion (on or off) setting.

#Confirm that the ring instances are in the idle state.  (Certain profile changes, such as changes to timer durations, do not take effect while the ring instances remain in the idle state because timers do not operate in the idle state.)
#Modify the profile settings for all nodes on the ring.  Certain profile settings, such as the WTR duration and the reversion setting, are used only by the Ring Protection Link (RPL) owner node and have no effect on the non-RPL owner nodes.
#If desired, you can test the WTR duration and reversion settings by applying a manual switch on the ring and then clearing the switch. If the manual switch is applied at the same node as the RPL, the ring instance changes only the state and does not experience a brief data outage (switch-over).
#If desired, you can test the hold-off interval setting by disabling the ring link.  Disabling the ring link causes a fault on the ring, the ring switches over, and a brief traffic outage occurs at all ring instances.

 

=== Physical Ring Procedures ===

This section contains the procedures for maintaining physical ring instances in an Ethernet ring topology. This section explains how to:

*Migrate the path of a ring to a new physical ring link or interface.
*Add a node to a physcial ring link.
*Remove a node from a physical ring link.
*Add or modify Connectivity Fault Management (CFM) monitoring for the physical ring link or interface.
*Remove CFM monitoring from a physical ring link or interface.
*Change the ring topology from open to closed or from closed to open. 

==== Migrating the Path of a Ring to a new Physical Ring Link or Physical Interface ====

During this procedure, all ring instances experience brief traffic outages (switch-overs).  The Automatic Protection Switching (APS) channel may become dormant, depending upon the physical ring link configuration completed in Step 5.  

#Install a new physical ring link and ensure that it is functional.  If you want to use Connectivity Fault Management (CFM) on this link, configure CFM and ensure it is  is functional.
#Disable the new physical interface.
#Configure Ethernet service instances on the new physical interface and associate them with the bridge domains on the physical ring link.
#Disable the previoulsy configured physical interface.  All ring instances transition to the protection state.
#Modify the physical ring link configuration on both nodes adjacent to the new link to point to the new physical interface.  To help reduce the chance of the APS channel becoming dormant, complete the configuration on one node before changing the configuration on the other node.   Otherwise, the APS channel becomes dormant if both nodes are unconfigured or unresolved.
#Enable the new physcial interface.  All ring instances transition to the pending state first, and then transition to the idle state after the reversion.
#If desired, disassociate the Ethernet service instances on the previously configured physical interface from the bridge domains on the physical ring link, and remove the Ethernet service instances. 

==== Adding a Node to a Ring ====

During this procedure, all ring instances experience a brief traffic outage (switch-over).

#Restart the new node and confirm that the node is functional.
#Install the new physical links and ensure that the physical links are functional.  If you want to use Connectivity Fault Management (CFM) on this physical link, configure CFM and ensure that it is functional.
#Disable the new physical interface.
#Add the ring configuration.  Confirm that the ring configuration is complete and that the ring configuration has been resolved.  Confirm that the ring instance is in the protection state for this node.
#Set up the new physical ring links on the neighboring nodes by following the [[#Migrating_the_Path_of_a_Ring_to_a_new_Physical_Ring_Link_or_Physical_Interface|Migrating the Path of a Ring to a new Physical Ring Link or Physical Interface]] procedure.  

 

==== Removing a Node from a Ring ====

The ITU-G standard, "G.8032 : Ethernet Ring Protection Switching" (published in March 2010) contains management procedure guidelines in Appendix IX.  Appendix IX describes a process for removing a node from a ring, using forced switches as part of the process.  Forced switches have the following disadvantages:

*Forced switches must be applied on ''each ''ring instance.
*Forced switches are disregarded by the node when an instance configuration is deleted or unresolved. If the forced switches are disregarded, the procedure in Appendix IX.2  of the standard must be followed to recover the ring.  For more information about the ITU-G standard, click [http://www.itu.int/rec/T-REC-G.8032/en here].

Therefore, the procedure below recommends disabling interfaces instead of using forced switches.  

#If applicable, install the new physical link between the neighboring nodes.  The goal of this new physical link is to bypass the node being removed from the ring.  After installing the new physical link, ensure that the new link is functional.
#Complete the steps in the [[#Migrating_the_Path_of_a_Ring_to_a_new_Physical_Ring_Link_or_Physical_Interface|Migrating the Path of a Ring to a new Physical Ring Link or Physical Interface]] procedure on the neighboring nodes. 
#Delete the ring configuration from the node being removed.

 

==== Adding or Modifying CFM Monitoring on a Physical Ring Link or Interface ====

Note:  A CFM upstream maintenance endpoint (MEP) configuration should '''not''' be used to monitor a physical ring link or interface.  Only a CFM downstream MEP or port MEP between two directly connected nodes should be used.

During this procedure, all ring instances experience a brief traffic outage (switch-over).

#Configure the downstream MEP on both ends of the link and confirm that the MEP is functional (that is, there are no fault conditions).
#Disable the physical interfaces on both nodes adjacent to the link.  All ring instances transition to the protection state.
#Modify the ring configuration on both nodes adjacent to the link to point to the new monitoring VLAN.  To help reduce the chance of the Automatic Protection Switching (APS) channel becoming dormant, complete the configuration on one node before changing the configuration on the other node. Otherwise, the APS channel becomes dormant if both nodes are unconfigured or unresolved.
#Enable the physical interface on both nodes adjacent to the link.  All ring instances transition to the pending state first, and then transition to the idle state after the reversion. 

==== Removing CFM Monitoring from a Physical Ring Link or Interface ====

During this procedure, all ring instances experience a brief traffic outage (switch-over).

#Disable the physical interfaces on both nodes adjacent to the link.  All ring instances transition to the protection state.
#Modify the ring configuration on both nodes adjacent to the link to remove the monitoring VLAN.  To help reduce the chance of the Automatic Protection Switching (APS) channel becoming dormant, complete the configuration on one node before changing the configuration on the other node. Otherwise, the APS channel becomes dormant  if both nodes are unconfigured or unresolved.
#Enable the physical interface on both nodes adjacent to the link.  All ring instances transition to the pending state first, and then transition to the idle state after the reversion.
#Delete the CFM configuration on both ends of the link.

 

==== Changing the Ring Topology from Open to Closed or from Closed to Open ====

This procedure affects the operation of ''all  ''Automatic Protection Switching ''(''APS) channels of ''all ''ring instances.  Therefore, do not complete this procedure on an operational ring.  Doing so could introduce a network loop in the APS channel.

#Delete all ring instances by following the procedure in the [[#Deleting_a_Ring_Instance_on_the_Ethernet_Ring|Deleting a Ring Instance on the Ethernet Ring]] section. 
#Modify the open-ring configuration on all nodes.
#Create all ring instances by following the procedure in the [[#Creating_a_Ring_Instance_on_the_Ethernet_Ring|Creating a Ring Instance on the Ethernet Ring]] section.

Cisco NX-OS IPv6 Feature Mapping

2012-03-29T15:39:33Z

Jkratky:

This table lists the IPv6 features supported in the Cisco NX-OS software release trains. It also identifies the earliest release for each software release train in which the feature became available. Unless noted otherwise, subsequent releases of that Cisco NX-OS software release train also support that feature. 

== IPv6 Forwarding Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! colspan="4" scope="col" | Cisco MDS 9000 
! colspan="7" scope="col" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
! scope="col" | Release 5.2
|-
! align="left" colspan="19" scope="col" | IPv6 Forwarding Features 
|-
| valign="top" align="center" | IPv6—ICMPv6 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—ICMPv6 Redirect 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—IPv6 Neighbor Discovery 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—6PE/6VPE 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/mpls/configuration/guide/mp_vpn_l3vpn.html Configuring MPLS Layer 3 VPNs] 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X 
|-
| valign="top" align="center" | IPv6—Label Allocation 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/mpls/configuration/guide/mp_vpn_per_vrf_lbl.html Configuring MPLS Layer 3 VPN Label Allocation] 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X 
|-
| valign="top" align="center" | IPv6 ND- Duplicate Address Detection 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—BFD 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_bfd.html Configuring Bidirectional Forwarding Detection] 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—Layer 3 Interfaces
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_layer3int.html Configuring Layer 3 Interfaces]
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—uRPF 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter23.html Configuring Unicast RPF] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|}

== IPv6 Fast Convergence Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! colspan="4" scope="col" | Cisco MDS 9000 
! colspan="6" scope="col" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Fast Convergence Features ''' 
|-
| valign="top" align="center" | BGPv6 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" |
*[http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_bgp.html Configuring Basic BGP]
*[http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_advbgp.html Configuring Advanced BGP]

| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|}

== IPv6 Routing Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! scope="col" colspan="4" | Cisco MDS 9000 
! scope="col" colspan="6" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Routing Features''' 
|-
| valign="top" align="center" | IP Routing—OSPFv3 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ospfv3.html Configuring OSPFv3] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IP Routing—Route Filters 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_rpm.html Configuring Route Policy Manager] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|}

== IPv6 Security, Qos, Accounting Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! scope="col" colspan="4" | Cisco MDS 9000 
! scope="col" colspan="6" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Security, Qos, Accounting Features '''
|-
| valign="top" align="center" | LDAP over IPv6
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter7.html Configuring LDAP]
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X
| align="center" | 
|-
| valign="top" align="center" | IPv6 access control lists (ACLs) 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipacl.html#wpxref62883 Configuring IPv4 and IPv6 Access Control Lists] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter14.html Configuring IP ACLs] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 VLAN access control lists (VACLs) 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter16.html Configuring VLAN ACLs] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 CoPP
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter24.html Configuring Control Plane Policing ]
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 QoS 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/qos/configuration/guide/classification.html Configuring Classification] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Access Services—RADIUS 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/cradtac1.html Configuring RADIUS and TACACS+] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter5.html Configuring RADIUS] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | TACACS+ over IPv6 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/cradtac1.html Configuring RADIUS and TACACS+] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter6.html Configuring TACACS+] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|}

 

== IPv6 Multicast Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! scope="col" colspan="4" | Cisco MDS 9000 
! scope="col" colspan="6" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Multicast Features''' 
|-
| valign="top" align="center" | IPv6 Multicast—Bidirectional Protocol Independent Multicast (Bidir PIM) 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/pim.html Configuring PIM and PIM6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Multicast—Multicast Listener Discovery (MLD) Protocol v1/v2 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/mld.html Configuring MLD] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Multicast—PIMv6-ASM 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/pim.html Configuring PIM and PIM6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Multicast—PIMv6-Sparse Mode 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/pim.html Configuring PIM and PIM6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Multicast—PIMv6 -SSM 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/pim.html Configuring PIM and PIM6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IP Multicast—BSR 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/pim.html Configuring PIM and PIM6] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Multicast—MLD Access Group 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/configuration/guide/mld.html Configuring MLD] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-

|}

== IPv6 Manageability Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! colspan="4" scope="col" | Cisco MDS 9000 
! colspan="2" scope="col" | Cisco Nexus 4000 Series Switches 
! colspan="7" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.1(2)E1(1)
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Manageability Features''' 
|-
| valign="top" align="center" | Ping
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/bb.html#wp1086969 Cisco MDS9000 Family CLI Guide] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/nexus4000/nexus4000_i/sw/configuration/guide/rel_4_1_2_E1_1/begin.html Using the Command-Line Interface] 
| align="center" | X 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/fundamentals/command/reference/fnd_commands.html Cisco Nexus 7000 Series NX-OS Fundamentals Commands]
| align="center" | X
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | Traceroute 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/bb.html#wp1086969 Cisco MDS9000 Family CLI Guide] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/fundamentals/command/reference/fnd_commands.html Cisco Nexus 7000 Series NX-OS Fundamentals Commands]
| align="center" | X
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | Telnet 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/nexus4000/nexus4000_i/sw/configuration/guide/rel_4_1_2_E1_1/sec_ssh.html Configuring SSH and Telnet] 
| align="center" | X 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter8.html Configuring SSH and Telnet] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | SSH (SCP) 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/nexus4000/nexus4000_i/sw/configuration/guide/rel_4_1_2_E1_1/sec_ssh.html Configuring SSH and Telnet] 
| align="center" | X 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter8.html Configuring SSH and Telnet] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | Syslog 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/log.html Configuring System Message Logging] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/system_management/configuration/guide/sm_5syslog.html Configuring System Message Logging] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | SNMP v1/v2/v3 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/snmp.html Configuring SNMP] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/system_management/configuration/guide/sm_9snmp.html Configuring SNMP] 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | API(XML)
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/dcnm/web_services/api/guide/web_services.html Cisco DCNM Web Services API Guide] 
| align="center" | 
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
|}

== IPv6 Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! scope="col" colspan="4" | Cisco MDS 9000 
! scope="col" colspan="6" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Features'''
|-
| valign="top" align="center" | IPv6—Addressing 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—CDP
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—CMP 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/hw/nexus7000/cmp/configuration/guide/n7cmp_configuring.html Connecting, Configuring, and Upgrading the CMP]  
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
|-
| valign="top" align="center" | IPv6—DNS
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—EIGRPv6 Enhanced Interior Gateway Routing Protocol (EIGRP) 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_eigrp.html Configuring EIGRP]
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—HSRPv6 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_hsrp.html Configuring HSRP] 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
|-
| valign="top" align="center" | IPv6—IPv6 Path MTU Discovery 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—IPv6 PBR 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_pbr.html Configuring Policy-Based Routing] 
| align="center" | 
| align="center" |
| align="center" | X 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—NetFlow
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/system_management/configuration/guide/sm_15netflow.html Configuring NetFlow] 
| align="center" | 
| align="center" | X 
| align="center" |
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—Object Tracking 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_object.html Configuring Object Tracking]
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | X 
| align="center" | 
|-
| valign="top" align="center" | IPv6—Packet Verification 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_ipv6.html Configuring IPv6] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—Prefix Lists 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_rpm.html Configuring Route Policy Manager] 
| align="center" | 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6—Static Routing 
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ipv6.html#wp1206558 Configuring IPv6 Static Routes] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_route.html Configuring Static Routing] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
|}

== IPv6 Services and Management Features ==

{| width="482" cellspacing="1" cellpadding="1" border="1" style=""
|-
! scope="col" | 
! scope="col" colspan="4" | Cisco MDS 9000 
! scope="col" colspan="6" | Cisco Nexus 7000 Series Switches 
|-
! scope="col" | Feature 
! scope="col" | Where Documented 
! scope="col" | Release 3.x 
! scope="col" | Release 4.x 
! scope="col" | Release 5.0 
! scope="col" | Where Documented 
! scope="col" | Release 4.0 
! scope="col" | Release 4.1 
! scope="col" | Release 4.2
! scope="col" | Release 5.0
! scope="col" | Release 5.1
|-
| valign="top" align="left" colspan="19" | '''IPv6 Services and Management Features '''
|-
| valign="top" align="center" | Call Home
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/call.html Configuring Call Home] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/system_management/configuration/guide/sm_6callhome.html Configuring Smart Call Home]
| align="center" | 
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | NTP
| align="center" | [http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/icfg.html#wp1192615 Configuring NTP] 
| align="center" | X 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/system_management/configuration/guide/sm_3ntp.html Configuring NTP] 
| align="center" | 
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Unicast Route Memory Resource
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/virtual_device_context/configuration/guide/vdc_mgmt.html Managing VDCs]
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
| align="center" | 
|-
| valign="top" align="center" | IPv6 Multicast Route Memory Resource
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | 
| align="center" | [http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/virtual_device_context/configuration/guide/vdc_mgmt.html Managing VDCs]
| align="center" | 
| align="center" | X
| align="center" | 
| align="center" | 
| align="center" | 
|}

 

== Additional Information ==

*[http://www.cisco.com/web/solutions/netsys/ipv6/knowledgebase/index.html Cisco IPv6 Knowledge Base Portal]
*[http://www.cisco.com/web/solutions/netsys/ipv6/index.html Cisco IPv6 Main Page] 
*[http://www.cisco.com/en/US/products/ps9402/products_installation_and_configuration_guides_list.html Cisco Nexus 7000 Series Switches Configuration Guides] 
*[http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_cli_nxos.html Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x] 
*[http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.htm MDS Documentation Locator] 

 
[[Category:IPv6]]

Cisco IOS XE IPv6 Feature Mapping

2012-03-29T15:39:11Z

Jkratky:

This table lists the IPv6 features supported in the Cisco IOS XE software release trains. It also identifies the earliest release for each software release train in which the feature became available. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.

== IPv6 Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6: uRPF

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: ICMPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: IPv6 neighbor discovery

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: IPv6 stateless autoconfiguration

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: IPv6 MTU path discovery

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: ping

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: Telnet, DNS, TFTP client, traceroute

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity], [http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: ICMPv6 redirect

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: ICMP rate limiting

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: neighbor discovery duplicate address detection

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: IPv6 static cache entry for neighbor discovery

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6 - Per interface neighbor discovery cache limit

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.6 
|- align="left" valign="top"
|
IPv6: IPv6 default router preferences

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: syslog over IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: IPv6 support for TCL

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
CNS agents for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6 for Config logger

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6: IPv6 default router preferences

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

| Cisco IOS XE Release 2.1 
|- align="left" valign="top"
|
IPv6 selective packet discard

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-spd_xe.html Implementing Selective Packet Discard in IPv6]

| Cisco IOS XE Release 2.6 
|- align="left" valign="top"
|
IPv6 Switching: Provider edge router over MPLS (6PE)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-over_mpls.html Implementing IPv6 over MPLS]

| Cisco IOS XE Release 3.1S 
|- align="left" valign="top"
|
IPv6 VPN over MPLS (6VPE)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ov_mpls_6vpe_xe.html Implementing IPv6 VPN over MPLS]

| Cisco IOS XE Release 3.1S 
|- align="left" valign="top"
|
MPLS VPN 6VPE support over IP tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ov_mpls_6vpe_xe.html Implementing IPv6 VPN over MPLS]

| Cisco IOS XE Release 3.1S 
|- align="left" valign="top"
|
IPv6 VPN over MPLS (6VPE) Inter-AS options

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ov_mpls_6vpe_xe.html Implementing IPv6 VPN over MPLS]

| Cisco IOS XE Release 3.1S 
|- align="left" valign="top"
|
BGP IPv6 PIC Edge for IP/MPLS

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ov_mpls_6vpe_xe.html Implementing IPv6 VPN over MPLS]

| Cisco IOS XE Release 3.3S 
|- align="left" valign="top"
|
Remote Access MPLS-VPNs

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/mpls/configuration/guide/mp_mngd_ipv6_lns_xe.html Configuring Managed IPv6 Layer 2 Tunnel Protocol Network Server]

| Cisco IOS XE Release 3.3S 
|}

== IPv6 Switching Services Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 switching: automatic 6to4 tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 switching: Cisco Express Forwarding/Distributed Cisco Express Forwarding support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 switching: CEFv6 switched ISATAP tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 switching: CEFv6 switched automatic IPv4- compatible tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|}

== IPv6 Routing Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 routing: RIP for IPv6 (RIPng)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-rip_xe.html Implementing RIP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: static routing

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-stat_routes_xe.html Implementing Static Routes for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: route redistribution

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-rip_xe.html][http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-rip_xe.html Implementing RIP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: multiprotocol BGP extensions for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mptcl_bgp_xe.html Implementing Multiprotocol BGP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: multiprotocol BGP link-local address peering

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mptcl_bgp_xe.html Implementing Multiprotocol BGP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: IS-IS support for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-is-is_xe.html Implementing IS-IS for IPv6]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
IPv6 routing: IS-IS multitopology support for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-is-is_xe.html Implementing IS-IS for IPv6]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 routing: IS-IS local RIB

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-is-is_xe.html Implementing IS-IS for IPv6]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
IPv6 routing: OSPF for IPv6 (OSPFv3)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ospf_xe.html Implementing OSPF for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: OSPFv3 Fast Convergence - LSA and SPF throttling

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ospf_xe.html Implementing OSPF for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
OSPFv3 graceful restart

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ospf_xe.html Implementing OSPF for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
OSPFv3 for BFD

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ospf_xe.html Implementing OSPF for IPv6]

[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-bfd_xe.html Implementing Bidirectional Forwarding Detection for IPv6 ]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
Implementing EIGRP for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-eigrp_xe.html Implementing EIGRP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6: NSF and graceful restart for MP-BGP IPv6 address family

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mptcl_bgp_xe.html Implementing Multiprotocol BGP for IPv6]

|
Cisco IOS XE Release 3.1S

|- align="left" valign="top"
|
IPv6 Policy-Based Routing

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-rip_xe.html Implementing Policy-Based Routing for IPv6]

|
Cisco IOS XE Release 3.2S

|}

== IPv6 Services and Management Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 services: AAAA DNS lookups over an IPv4 transport

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: standard access control lists

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-sec_trfltr_fw_xe.html Implementing Traffic Filters and Firewalls for IPv6 Security]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: DNS lookups over an IPv6 transport

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: Secure Shell (SSH) support over IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: Cisco Discovery Protocol— IPv6 address family support for neighbor information

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: RFC 4293 IP-MIB (IPv6 only) and RFC 4292 IP-FORWARD-MIB (IPv6 only)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: extended access control lists

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-sec_trfltr_fw_xe.html Implementing Traffic Filters and Firewalls for IPv6 Security]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 ACL - Template ACL

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-sec_trfltr_fw_xe.html Implementing Traffic Filters and Firewalls for IPv6 Security]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 services: SNMP over IPv6[1] 

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IP SLAs for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mng_apps_xe.html Implementing IPv6 for Network Management]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 IPSec Static Virtual Interface

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ipsec_xe.html Implementing IPsec in IPv6 Security]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
HSRP for IPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-fhrp_xe.html Configuring First Hop Redundancy Protocols in IPv6]

|
Cisco IOS XE Release 3.1S

|- align="left" valign="top"
|
NSF/SSO - HSRPv6 on VRF interfaces

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-fhrp_xe.html Configuring First Hop Redundancy Protocols in IPv6]

|
Cisco IOS XE Release 3.1S

|- align="left" valign="top"
|
ISSU - HSRPv6 on VRF interfaces

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-fhrp_xe.html Configuring First Hop Redundancy Protocols in IPv6]

|
Cisco IOS XE Release 3.1S

|- align="left" valign="top"
| Stateless Network Address Translation 64 
| [http://www.cisco.com/en/US/docs/ios-xml/ios/ipaddr_nat/configuration/xe-3s/Stateless_Network_Address_Translation_64.html Stateless Network Address Translation 64] 
| Cisco IOS XE Release 3.2S 
|}

== IPv6 Broadband Access Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
SSO - PPPoE IPv6

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
PPP enhancement for Broadband IPv6

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
AAA improvements for Broadband IPv6

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
DHCP enhancements to support IPv6 Broadband deployments

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
DHCP - DHCPv6 Prefix Delegation RADIUS VSA

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
IPv6 Access Services: AAA Support for Cisco VSA IPv6 Attributes

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
IPv6 Access Services: PPPoE

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
IPv6 Access Services: PPPoA

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 3.3S

|- align="left" valign="top"
|
IPv6 Access Services: AAA Support for RFC 3162 IPv6 RADIUS Attributes

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
Broadband IPv6 counter support at LNS

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
PPP: IPv6 accounting delay enhancements

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 3.2S

|- align="left" valign="top"
|
TACACS over IPv6

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 3.2S

|- align="left" valign="top"
|
RADIUS over IPv6

|
[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html Implementing ADSLfor IPv6]

|
Cisco IOS XE Release 3.2S

|- align="left" valign="top"
|
IPv6 Access Services: RBE

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 3.2S

|}

== DHCP Features for IPv6 ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 access services: DHCPv6 prefix delegation

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 access services: DHCPv6 relay agent notification for prefix delegation

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 access services: DHCPv6 relay - reload persistent interface ID option

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 access services: DHCPv6 Ethernet remote ID option

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 Access Services: Stateless DHCPv6

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 2.5

|- align="left" valign="top"
|
DHCPv6 Server - MPLS VPN Support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 3.3S

|- align="left" valign="top"
|
DHCPv6 Relay - MPLS VPN Support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-dhcp_xe.html Implementing DHCP for IPv6]

|
Cisco IOS XE Release 3.3S

|}

== IPv6 Multicast Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 multicast: Multicast Listener Discovery (MLD) protocol, versions 1 and 2

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: PIM Source Specific Multicast (PIM-SSM)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: PIM sparse mode (PIM-SM)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
PIM passive mode

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
IPv6 multicast: MLD access group

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: MLD group limits

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
IPv6 multicast: PIM accept register

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: static multicast routing (mroute)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 multicast: routable address hello option

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 multicast: address family support for multiprotocol Border Gateway Protocol (MBGP)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: Explicit tracking of receivers

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: IPv6 bidirectional PIM

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: IPv6 BSR

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 multicast: IPv6 BSR bidirectional support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 multicast: IPv6 BSR scoped-zone support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 multicast: SSM mapping for MLDv1 SSM

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 multicast: IPv6 BSR—ability to configure RP mapping

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6: Multicast address group range support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
IPv6 Multicast: bandwidth-based call admission control (CAC)

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.6

|- align="left" valign="top"
|
Threshold notification for mCAC limit

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-multicast_xe.html Implementing IPv6 Multicast]

|
Cisco IOS XE Release 2.6

|}

== IPv6 Tunnel Services Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 tunneling: automatic 6to4 tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 tunneling: manually configured IPv6 over IPv4 tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 tunneling: IPv6 over IPv4 GRE tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 tunneling: IP over IPv6 GRE tunnels

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.4

|- align="left" valign="top"
|
IPv6 tunneling: ISATAP tunnel support

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IP tunneling: 6RD IPv6 rapid deployment

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-tunnel_xe.html Implementing Tunneling for IPv6]

|
Cisco IOS XE Release 3.1S

|}

== IPv6 QoS (Quality of Service) Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 QoS: MQC packet classification

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-qos_xe.html Implementing QoS for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 QoS: MQC traffic shaping

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-qos_xe.html Implementing QoS for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 QoS: MQC traffic policing

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-qos_xe.html Implementing QoS for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 QoS: MQC packet marking/remarking

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-qos_xe.html Implementing QoS for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 QoS: queueing

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-qos_xe.html Implementing QoS for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 QoS: MQC weighted random early detection (WRED)-based drop

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-qos_xe.html Implementing QoS for IPv6]

|
Cisco IOS XE Release 2.1

|}

== IPv6 High Availability Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6: Base Protocols High Availability

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: RIPng nonstop forwarding

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-rip_xe.html Implementing RIP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 routing: NSF and graceful restart for MP-BGP IPv6 address family

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-mptcl_bgp_xe.html Implementing Multiprotocol BGP for IPv6]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
OSPFv3 graceful restart

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-ospf_xe.html Implementing OSPF for IPv6]

|
Cisco IOS XE Release 2.1

|}

== IPv6 Data Link Layer Features ==

{| cellpadding="2" border="1" width="80%" id="wp1186601table1074495"
|+ 
|- align="left" valign="bottom"
! scope="col" | <div class="pCH1_CellHead1">Feature </div>
! scope="col" | <div class="pCH1_CellHead1">Where Documented </div>
! scope="col" | <div class="pCH1_CellHead1">XE Release </div>
|- align="left" valign="top"
|
IPv6 data link: Fast Ethernet

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 data link: Frame Relay PVC

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 data link: High-Level Data Link Control

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 data link: PPP service over packet over SONET, ISDN, and serial (synchronous ad asynchronous) interfaces

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|- align="left" valign="top"
|
IPv6 data link: VLANs using IEEE 802.1Q encapsulation

|
[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/ip6-addrg_bsc_con_xe.html Implementing IPv6 Addressing and Basic Connectivity]

|
Cisco IOS XE Release 2.1

|}

[1] SNMP versions 1, 2, and 3 are supported over an IPv6 transport.

 

== Additional Information ==

*[http://www.cisco.com/en/US/products/ps11174/products_installation_and_configuration_guides_list.html Cisco IOS XE 3S Configuration Guides]
*[http://www.cisco.com/web/solutions/netsys/ipv6/knowledgebase/index.html Cisco IPv6 Knowledge Base Portal]
*[http://www.cisco.com/web/solutions/netsys/ipv6/index.html Cisco IPv6 Main Page] 
*[http://www.cisco.com/en/US/docs/ios/ios_xe/ipv6/configuration/guide/xe_3s/ipv6_xe_3s_book.html IPv6 Configuration Guide, Cisco IOS XE Release 3S]
[[Category:IPv6]]