Upgrade Guide for Cisco Unity Connection Release 7.x
Index
Downloads: This chapterpdf (PDF - 131.0KB) The complete bookPDF (PDF - 2.41MB) | Feedback

Index

Table Of Contents

A - C - D - E - H - I - L - M - P - R - S - T - U -

Index

A

adding a server to create a cluster 8-1

associated components on which IP address of server must be changed 9-2

C

changing

IP address for publisher defined by host name 9-7

IP address for publisher defined by IP address 9-9

IP address for single server defined by an IP address (no cluster) 9-5

IP address for single server that is defined by a hostname (no cluster) 9-3

IP address for subscriber defined by host name 9-12

IP address for subscriber defined by IP address 9-14

language settings 6-7

cluster

replacing publisher and subscriber servers 7-9

replacing publisher server 7-2

replacing subscriber server 7-5

reverting servers to version on inactive partition 3-2

COBRAS

for migrating data from 1.x to 7.x 4-1

for migrating data from Cisco Unity 4.x to Connection 7.x 5-1

importing user data and messages from Cisco Unity 4.x to Connection 7.x 5-8

conventions, documentation -vii

converting publisher to single server without a cluster 8-3

D

database replication, resetting after reverting servers in a cluster to version on inactive partition 3-3

documentation conventions -vii

E

effects of reverting to version on inactive partition 3-1

H

hard disks

replacing for 1.x to 7.x migration 4-5

replacing for 2.x or later upgrade to 7.x 2-3

replacing for Cisco Unity 4.x to Connection 7.x migration 5-5

host name, determining whether servers are defined by 9-1

I

importing user data and messages

with 1.x to 2.x Migration Import tool 4-9

with Cisco COBRAS 5-8

with Cisco Unity 4.x to Connection 2.x Migration Import tool 5-9

installing

memory upgrade for 1.x to 7.x migration 4-5

memory upgrade for 2.x or later upgrade to 7.x 2-3

memory upgrade for Cisco Unity 4.x to Connection 7.x migration 5-5

IP addresses

changing for publisher defined by host name 9-7

changing for publisher defined by IP address 9-9

changing for single server defined by a hostname (no cluster) 9-3

changing for single server defined by an IP address (no cluster) 9-5

changing for subscriber defined by host name 9-12

changing for subscriber defined by IP address 9-14

changing on associated components 9-2

determining whether servers are defined by 9-1

L

languages

adding to a Connection cluster (task list) 6-2

adding to a Connection server without a cluster (task list) 6-1

changing settings 6-7

removing files 6-7

M

memory upgrade

installing for 1.x to 7.x migration 4-5

installing for 2.x or later upgrade to 7.x 2-3

installing for Cisco Unity 4.x to Connection 7.x migration 5-5

messages, importing with COBRAS

from Cisco Unity 4.x to Connection 7.x 5-8

messages, importing with Migration Import tool

from 1.x to 7.x 4-9

from Cisco Unity 4.x to Connection 7.x 5-9

migrating

from 1.x to 7.x, task list 4-2

from Cisco Unity 4.x to Connection 7.x, task list 5-2

Migration Export tool

for migrating data from 1.x to 7.x 4-2

for migrating data from Cisco Unity 4.x to Connection 7.x 5-2

Migration Import tool

importing user data and messages from 1.x to 7.x 4-9

importing user data and messages from Cisco Unity 4.x to Connection 7.x 5-9

P

preparing to create user accounts with multiple templates

for 1.x to 7.x migration 4-8

for Cisco Unity 4.x to Connection 7.x migration 5-8

publisher server

converting to single server without a cluster 8-3

renaming 10-3

replacing 7-2

replacing along with subscriber server 7-9

reverting to version on inactive partition 3-2

R

removing language files 6-7

renaming

publisher server 10-3

single server without a cluster 10-1

subscriber server 10-6

replacing

hard disks for 1.x to 7.x migration 4-5

hard disks for 2.x or later upgrade to 7.x 2-3

hard disks for Cisco Unity 4.x to Connection 7.x migration 5-5

publisher and subscriber servers 7-9

publisher server 7-2

single server without Connection cluster 7-1

subscriber server 7-5

resetting database replication in a cluster after reverting servers to version on inactive partition 3-3

reverting

effects of 3-1

server, or publisher server in a cluster to version on inactive partition 3-2

servers in a cluster to version on inactive partition 3-2

subscriber server in a cluster to version on inactive partition 3-3

S

servers

adding to create a cluster 8-1

associated components on which IP address must be changed 9-2

changing IP address for publisher defined by host name 9-7

changing IP address for publisher defined by IP address 9-9

changing IP address for single defined by a hostname (no cluster) 9-3

changing IP address for single server defined by an IP address (no cluster) 9-5

changing IP address for subscriber defined by host name 9-12

changing IP address for subscriber defined by IP address 9-14

converting publisher to single server without a cluster 8-3

determining whether server is defined by host name or IP address 9-1

renaming publisher 10-3

renaming single without a cluster 10-1

renaming subscriber 10-6

replacing publisher 7-2

replacing publisher and subscriber 7-9

replacing single without Connection cluster 7-1

replacing subscriber 7-5

reverting to version on inactive partition in a cluster 3-2

software, reverting to version on inactive partition 3-1

subscriber server

renaming 10-6

replacing 7-5

replacing along with publisher server 7-9

reverting to version on inactive partition 3-3

T

task lists

for adding languages to a Connection cluster 6-2

for adding languages to a Connection server without a cluster 6-1

for migrating from 1.x to 7.x 4-2

for migrating from Cisco Unity 4.x to Connection 7.x 5-2

for reverting servers in a cluster to version on inactive partition 3-2

for upgrading Connection 2.x software to shipping 7.x version 2-1

for upgrading Connection 7.x software to shipping 7.x version (no cluster) 1-1

for upgrading Connection 7.x software to shipping 7.x version in a Connection cluster 1-2

tools for migrating data

from 1.x to 7.x, about 4-1

from Cisco Unity 4.x to Connection 7.x, about 5-1

U

upgrading

Connection 2.x software to shipping 7.x version (task list) 2-1

Connection 7.x software to shipping 7.x version, no cluster (task list) 1-1

Connection 7.x software to shipping 7.x version in a Connection cluster (task list) 1-2

user accounts, preparing to create with multiple templates

for 1.x to 7.x migration 4-8

for Cisco Unity 4.x to Connection 7.x migration 5-8

user data, importing with COBRAS

from Cisco Unity 4.x to Connection 7.x 5-8

user data, importing with Migration Import tool

from 1.x to 7.x 4-9

from Cisco Unity 4.x to Connection 7.x 5-9