Assigning Node Names and IP Addresses for the C-LANs and LSPs
Note:
The CLAN boards must be TN799DP running version 5 or greater firmware. Be
Note:
sure to check the firmware version for these boards on the S8700. For
information on how to upgrade the firmware on the S8700, please see the section
"Upgrade Firmware in Selected Port Cabinet Packs" in Upgrading the Avaya
media server Configuration in the S8700 documentation portion of this
documentation CD, ''Avaya S8300, S8500, and S8700 media server Library CD,"
555-233-325.''
To assign node names and IP addresses
1. At the SAT prompt, type change node-names ip to open the Node Names screen.
Example Node Names Screen
change node-names ip
Name
default_________
node-1-clan
node-2-clan
node-10-lsp
node-11-lsp
__________
__________
__________
2. Enter the name and IP address for the C-LANs and LSPs.
3. Press F3 (Enter) when complete.
Administering Network Regions
Before assigning an IP network region to a G700, you must define network region on the IP
Network Region form. After a network region is defined, you can assign it to the various network
elements (servers, gateways, IP phones).
The information you need to do this should be provided in your planning documentation. Use
the system defaults if the planning documentation does not specify otherwise.
For a G700 with an S8300 LSP and an S8500 or S8700 as the primary controller, there may be
more than one network region, since there can be up to 250 G700 media gateways connected
to the S8500 or S8700 with thousands of telephones in the network. In this case, you define a
network region for each CLAN board on the S8500 or S8700 port networks, though they may
also have the same network region.
IP NODE NAMES
IP Address
0__.0__.0__.0__
__
192.168.1 _.124
192.168.1 _.97_
192.168.1 _.50_
192.168.1 _.51_
___.___.___.
_
___.___.___.
_
___.___.___.
_
Administer Communication Manager
Name
_______________
___.___.___.___
_______________
___.___.___.___
_______________
___.___.___.___
_______________
___.___.___.___
_______________
___.___.___.___
_______________
___.___.___.___
_______________
___.___.___.___
_______________
___.___.___.___
Page 1 of 1
IP Address
Issue 8.1 June 2005
167