

Provide this worksheet to your LAN administrator. Default values are shown in braces.
Caution:
It is crucial to coordinate the IP addresses that will be 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.
For more information, Job Aids.
The worksheet items are arranged in the order in which they are needed during server configuration. For an illustration of these items, see IP Connect duplex configuration.
Name of server 1: __________________________________
Name of server 2: __________________________________
Active server name: __________________________________
Ethernet interface functions (the corporate LAN function may be assigned to Ethernet 4 if the IP-configuration uses a private LAN for its control network)
Function assigned to Ethernet 0: {control network A plus the corporate LAN, if a private control network is not used} _____________________
Function assigned to Ethernet 1: {services laptop} _____________________
Function assigned to Ethernet 2: {duplication link} _____________________
Function assigned to Ethernet 4: {corporate LAN, if a private control network is used} _____________________
Ethernet 0 default addresses (for control network A plus the corporate LAN if a private control network is not used):
Server 1 IP address on control network A/corporate LAN: {198.152.254.201} _____________________
Server 2 IP address on control network A/corporate LAN: {198.152.254.202} _____________________
Active server IP address on control network A/corporate LAN: {198.152.254.200} _____________________
Gateway IP address for control network A/corporate LAN: _____________________
Subnet mask for control network A/corporate LAN: {255.255.255.0} _____________________
Speed of link (10 or 100 megabit, full or half duplex): {autosense} _____________________
VLAN 802.1q priority tagging: {off} _____________________
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} _____________________
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 |
Number of Ethernet switches: {1} _____
Ethernet switch 1 IP address: {198.152.254.240} _____________________
SNMP GET (read) community string: {public} _____________________
SNMP SET (write) community string: _____________________
Ethernet switch 2 IP address: {198.152.254.241} _____________________
SNMP GET (read) community string: {public} _____________________
SNMP SET (write) community string: _____________________
|
|
If Ethernet switches are part of the switch configuration and report alarms to the media servers using SNMP, they must be on the same subnet as the media servers. |
Specify the UPS units for the server
Number of UPS units: {2} _____
UPS 1 IP address: {198.152.254.239} _____________________
SNMP GET (read) community string: {public} _____________________
SNMP SET (write) community string: _____________________
UPS 2 IP address: {198.152.254.238} _____________________
SNMP GET (read) community string: {public} _____________________
SNMP SET (write) community string: _____________________
The UPS units must be on the same subnet as the media servers, and must report alarms through SNMP to the servers in order for the servers to respond correctly to a loss of power.
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: _____________________
|
|
DHCP service is not currently available for S8700 IP Connect. |
Optional: Enter any static IP addresses required to ensure delivery of information over certain parts of the network.
|
IP address of endpoint server is trying to reach |
Subnet mask used by all endpoints |
Gateway IP address (optional) |
Ethernet interface |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Primary NTS name or IP address: _____________________
Secondary NTS name or IP address: _____________________
Tertiary NTS name or IP address: _____________________
Trusted Key: _____________________
Request Key: _____________________
Control Key: _____________________
IP address of the PPP dial-up link for server 1: _____________________
IP address of the PPP dial-up link for server 2: _____________________
IP address of SNMP trap destination: _____________________
Community name: _____________________
Notification type (trap/inform): _____________________
Community name: _____________________
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): _____________________