Multi-connect preinstallation worksheet

Provide this worksheet to the LAN administrator. Default values are shown in braces.

• The administrator may require you to change IP addresses to prevent conflicts with existing endpoints on the corporate  LAN. Make precise notes of any changes and follow instructions exactly.

• Allow up to 4 hours to complete this worksheet to speed up server configuration, which could prevent you from losing work in progress.

Caution:
It is crucial to coordinate the IP addresses used with your Avaya media server with those on the corporate LAN. If you specify an Ethernet address for the Avaya server component that conflicts with another Ethernet endpoint, the resulting problems with traffic on the local area network may be extremely difficult to diagnose and solve.

Avaya S8700 media server for multi-connect configuration worksheet

The worksheet items are arranged in the order in which they are needed during server configuration. For an illustration of these items, see Related Topics.

For the Set Server Identities screen

1. Server number 1 & 2 must be on the same subnet (be sure to configure both servers)
2. Server names (these should also be administered on any relevant corporate DNS servers)

Name of server 1: __________________________________

Name of server 2: __________________________________

Active server name: __________________________________

3. Ethernet interface functions (control network B is only used for high- and critical-reliability configurations; the others are always present)

Function assigned to Ethernet 0: {control network A} _____________________

Function assigned to Ethernet 1: {services laptop} _____________________

Function assigned to Ethernet 2: {duplication link} _____________________

Function assigned to Ethernet 3: {control network B} _____________________

Function assigned to Ethernet 4: {corporate LAN} _____________________

For the Configure Ethernet Interfaces screen

1. Ethernet 0 default addresses (for control network A):

Server 1 IP address on control network A: {198.152.254.201} _____________________

Server 2 IP address on control network A: {198.152.254.202} _____________________

Active server IP address on control network A: {198.152.254.200} _____________________

Subnet mask for control network A: {255.255.255.0} _____________________

Speed of link (10 or 100 megabit, full or half duplex): {autosense} _____________________

VLAN 802.1q priority tagging: {off} _____________________

2. Ethernet 2 default addresses (for duplication link):

Server 1 IP address on duplication link: {192.11.13.13} _____________________

Server 2 IP address on duplication link: {192.11.13.14} _____________________

Subnet mask for the duplication link: {255.255.255.252} _____________________

Speed of link (100 megabit, full duplex): {autosense} _____________________

3. Ethernet 3 default addresses (for control network B, if present):

Server 1 IP address on control network B: {198.152.255.201} _____________________

Server 2 IP address on control network B: {198.152.255.202} _____________________

Active server IP address on control network B: {198.152.255.200} _____________________

Subnet mask for control network B: {255.255.255.0} _____________________

Speed of link (10 or 100 megabit, full or half duplex): {autosense} _____________________

VLAN 802.1q priority tagging: {off} _____________________

4. Ethernet 4 addresses (for corporate LAN, no default values):

Server 1 IP address on the corporate LAN: _____________________

Server 2 IP address on the corporate LAN: _____________________

Active server IP address on the corporate LAN: _____________________

Gateway IP address for the corporate LAN: _____________________

Subnet mask for the corporate LAN: _____________________

Speed of link (10 or 100 megabit, full or half duplex): {autosense} _____________________

VLAN 802.1q priority tagging: {off} _____________________

Ethernet 1 addresses are fixed for the services (laptop) interface:

IP address for every Avaya media server: 192.11.13.6

Subnet mask for the laptop link: 255.255.255.252

For the Control Switches and UPS screen

1. Specify the Ethernet switches for each control network (two may be used per control network if there are a large number of port networks)

Number of Ethernet switches per control network: {1} _____

Ethernet switch 1 IP address on control network A: {198.152.254.240} _____________________

        SNMP GET (read) community string: {public} _____________________

        SNMP SET (write) community string:  _____________________

Ethernet switch 2 IP address  on control network A: {198.152.254.241} _____________________

        SNMP GET (read) community string: {public} _____________________

        SNMP SET (write) community string:  _____________________

Ethernet switch 1 IP address on control network B: {198.152.255.240} _____________________

        SNMP GET (read) community string: {public} _____________________

        SNMP SET (write) community string:  _____________________

Ethernet switch 2 IP address  on control network B: {198.152.255.241} _____________________

        SNMP GET (read) community string: {public} _____________________

        SNMP SET (write) community string:  _____________________

2. Specify the UPS units for each control network

Number of UPS units for the control network: {2} _____

UPS 1 IP address on control network A: {198.152.254.239} _____________________

        SNMP GET (read) community string: {public} _____________________

        SNMP SET (write) community string:  _____________________

UPS 2 IP address on control network B: {198.152.255.239} _____________________

        SNMP GET (read) community string: {public} _____________________

        SNMP SET (write) community string:  _____________________

For the DNS and DHCP Server Configuration screen

1. Optional: If domain name service (DNS) servers are to be used, complete as many of the following fields as needed to set up DNS service and limit unresolved name searching. Fill out only as many server and search domain fields as are needed:

DNS server 1 IP address: _____________________

DNS server 2 IP address: _____________________

DNS server 3 IP address: _____________________

DNS domain name: _____________________

Search domain name 1: _____________________

Search domain name 2: _____________________

Search domain name 3: _____________________

Search domain name 4: _____________________

Search domain name 5: _____________________

2. Specify whether the Avaya media server will provide DHCP service, or whether IPSI IP addresses will be manually assigned:

Enable DHCP service on media servers: {yes} _____

For the Set Static Network Routes screen

Optional: Enter any static IP addresses required to ensure delivery of information over certain parts of the network.

For the Network Time Server screen

1. Is a Network Time Server (NTS) available to be used as the time source? (y/n) _____
2. If NTSs are available, enter their DNS name or IP address (up to 3, in preferred order)

Primary NTS name or IP address: _____________________

Secondary NTS name or IP address: _____________________

Tertiary NTS name or IP address: _____________________

1. Should the server support NTSs that multicast timing messages? (y/n): _____
2. Enter any valid key numbers supplied by the LAN administrator (otherwise leave blank)

Trusted Key: _____________________

Request Key: _____________________

Control Key: _____________________

3. Provide the location or content of the keys file (if used): _____________________

For the Set Modem Interface screen

1. Specify the IP address for each server's modem (this information must be provided by Avaya Services if a maintenance contract is in force):

IP address of the PPP dial-up link for server 1: _____________________

IP address of the PPP dial-up link for server 2: _____________________

2. Use the default return routes provided by Services (unless specifically instructed to change them).

For the Configure Trap Destinations screen

1. Specify Simple Network Management Protocol (SNMP) alarming information for each trap destination (needed only if a corporate network management system is in use)

IP address of SNMP trap destination: _____________________

1. SNMP protocol version (1, 2c or 3): _____
2. Required for version 1:

Community name: _____________________

3. Required for version 2c:

Notification type (trap/inform): _____________________

Community name: _____________________

4. Required for version 3:

Notification type (trap/inform): _____________________

User name: _____________________

Security model (none, authentication, or privacy): _____________________

Authentication password (required for authentication and privacy model): _____________________

Privacy password (required for privacy model): _____________________