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.
The G700, in this case, may also share the same network region as the CLAN board(s).
However, it may have a different network region because of the geographic distances of the
connections between the G700 and the S8500 or S8700. The G700 network region may also
differ because of the nature of the endpoints connected to it.
To define IP network regions for the G700 and CLAN board(s)
!
CAUTION:
Defining IP network regions can be quite complex. For detailed information on
CAUTION:
the use and administration of IP network regions, see ''Administration for Network
Connectivity for Avaya Communication Manager,'' 555-233-504.
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
501