Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual

							Configuration 1: R8r  R8si 
71
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
> Submit the screen
End
Session - Local The Local and Remote Session numbers can be any value 
between 1 and 256 (si model) or 384 (r model), but they must 
be consistent between endpoints. For each connection, the 
Local Session number on this switch must equal the Remote 
Session number on the remote switch and vice versa.
It is allowed, and sometimes convenient, to use the same 
number for the Local and Remote Session numbers. It is 
allowed, but not recommended, to use the same Session 
numbers for two or more connections. Session - Remote
Mach ID Destination switch ID identified on the dial plan of the 
destination switch. Field Conditions/Comments
2 of 2 
						

							Configuration 1: R8r  R8si 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
72
Enable links and processor channels
You must enable links and processor channels before the connections can be used.
To enable a link, open its data module screen (ch da [ext]) and set the Enable 
Link? field to y. 
[note: to view a list of assigned data modules and their extensions, enter the “list 
data-module” command (l da)]
To enable the processor channels, open the processor channel screen (ch com p) 
and set the Enable field to y for each assigned processor channel.
Note:1. You must disable a link or processor channel before you can change its 
parameters.
Note:2. The busy-out command overrules the data module Enable Link? field.
Note:3. On the C-LAN boards, low-level connectivity can remain intact when 
higher-level applications such as DCS are not functioning. For example, 
an external ping to a C-LAN’s ethernet port could be successful even 
when the board is busied-out. When debugging connectivity problems, 
pinging only checks low-level connectivity. 
						

							Configuration 2: R7r (+CMS)  R7csi 
73
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Configuration 2: R7r (+CMS)  R7csi 
This configuration is a 10BaseT ethernet connection between a DEFINITY ECS R8r 
and a DEFINITY ECS R8csi switch in a DCS network, which includes routers 
between the switches. The R8r is connected to a CMS adjunct (the DEFINITY 
administration for Intuity AUDIX would be similar) via the LAN. 
Note:This network has 5 IP nodes: 2 DCS nodes, 2 nodes on the router and one 
adjunct node. The router separates two subnets, so IP routes are needed 
from each switch to the nodes on the other side of the network.
DEFINITY ECSEthernet
Switch 1Switch 2
DEFINITY ECS
R8csi
C-LAN
R8r
C-LAN
CMS
or
Intuity
LAN
node-1node-2node-3
node-4
node-5
AUDIX
WAN
Router
Router 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
74
Task Summary
The following tasks need to be completed for Switch 1 and Switch 2:
1  Review prerequisite administration checklist
2  Switch 1 administration
 a  Assign node names
 b  Assign IP Interfaces
 c  Assign link (via a data module) to the LAN
 d  Assign processor channels
3  Switch 2 administration
 a  Enable bus bridge connectivity
 b  Assign node names
 c  Assign IP Interfaces
 d  Assign link (via a data module) to the LAN
 e  Assign IP routes
 f  Assign processor channels
4  Intuity AUDIX administration
 a  Administer the UNIX name and IP address 
 b  Administer the switch interface link
 c  Administer extension numbers, channels, and services
 d  Administer subscribers
5  CMS administration.
See CentreVu CMS Software Installation and Setup, 585-215-866 and CentreVu 
CMS Switch Connections and Administration, 585-215-876 for details of CMS 
setup and administration. (For Intuity AUDIX connections, see Intuity Messaging 
Solutions LAN Integration with DEFINITY ECS, 585-313-602.)
6  Enable links and processor channels 
						

							Configuration 2: R7r (+CMS)  R7csi 
75
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
SWITCH 1Configuration 2
DEFINITY ECS R8rDEFINITY ECS R8csi
Processor
channelsProcessor
channelsInterface
channelsInterface
channels
1
2
12
3841
5000
5001
x(any)
645001
2
21
256
Link 2Link 5
1
5000
5001
5003
64500
SWITCH 2
hardware connectionsProcessor
UN331B
Processor bus
TDM bus
Packet bus
DS1
TN767/
TN464
C-LAN
TN799
Voice data
Ethernet
dataNetwork
control
UN332B
51
2
cydfec2b KLC 101899
node-1
Ext 2377
loc 1co877
192.168.1.124
1
node-2
192.168.1.125
2
node-3
192.168.1.97
3
node-4
192.168.1.39
4
Node-5
Ext 3201
loc 1a0517
192.168.1.51
5 PktInt
TN1655
Bus
bridge
TDM bus
Packet bus
DS1
TN767/
TN464
C-LAN
TN799
Processor
TN798B
Router
Router
software-defined connections
LAN
3
4
WAN
CMS or
Intuity
AUDIX 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
76
Switch 1 Task — Assign Node Names
This task assigns node names and IP addresses to each node in the network. This 
screen is administered on Switch 1. A Node Names screen must be administered on 
each switch in the network.
The node names and IP addresses in any network should be assigned in a logical and 
consistent manner from the point of view of the whole network. These names and 
addresses should be assigned in the planning stages of the network and should be 
available from the customer system administrator or a Lucent representative.
Note:Enter node names for Intuity AUDIX and MSA adjuncts on page 1. Enter 
node names for switches, routers, and CMS starting on page 2.
Begin
Steps
> Open Node Names form — enter  ch node-n
> Go to page 2
> Enter values.
> Submit the screen
End
change node names  Page 2 of 6
                            NODE NAMES
Name              IP Address          Name                IP Address
default
_________ 0__.0__.0__.0__ _______________ ___.___.___.___
node-1  __
  192.168.1 _.124  _______________    ___.___.___.___
node-2___        192.168.1 _.125   _______________    ___.___.___.___
node-3__________  192.168.1 _.97_  _______________    ___.___.___.___
node-5_____
_____  192.168.1 _.51_ _______________    ___.___.___.___
Field Conditions/Comments
Name: Enter node names for the following 4 nodes:
•node-1: C-LAN Ethernet port on Switch 1
•node-2: CMS node (for consistency, use the host name of the 
CMS computer assigned during the CMS setup procedure — 
see CentreVu CMS Software Installation and Setup, 
585-215-866)
•node-3: Interface on the router to the subnet of Switch 1.
•node-5: C-LAN Ethernet port on Switch 2.
IP Address: The unique IP addresses for the nodes named in the previous field. 
See the description of the Subnet Mask field in the next task for 
information on valid IP addresses. 
						

							Configuration 2: R7r (+CMS)  R7csi 
77
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 1 Task — Assign IP Interfaces
The IP interface for each C-LAN and MedPro board on the switch must be defined on 
the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces 
form.
Begin
Steps
> Open IP Interfaces form — enter  ch ip-i
> Enter values
change ip-interfaces  Page   1 of   2 
IP Interfaces
Inter-region IP connectivity allowed?  n
Enable Net
Eth Pt Type   Slot  Code Sfx Node Name   Subnet Mask  Gateway Addr Rgn
y   C-LAN  01c08 TN799 B  node-1  255.255.255.224  192.168.1_.97_  1
n  255.255.255.0 
n  255.255.255.0 
n  255.255.255.0 
Field Conditions/Comments
Inter-region IP 
connectivity 
allowed?Enter y to allow IP endpoints (phones and trunks) to use MedPro 
resources administered in regions that are different from the 
endpoints’ regions.
Enable Eth Pt The Ethernet port must be enabled (y) before it can be used. The 
port must be disabled (n) before changes can be made to its 
attributes on this screen.
Type Enter c-lan or medpro.
Slot Enter the slot location for the circuit pack.
Code Display only. This field is automatically populated with TN799 
for C-LAN or TN802 for MedPro.
Sfx Display only. This field is automatically populated with B for 
the TN802 and TN799.
Node name Enter the unique node name for the IP interface. The node name 
here must already be administered on the Node Names screen
1 of 2 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
78
> Submit the screen
End
Subnet Mask Enter the subnet mask associated with the IP address for this IP 
interface. 
The IP address for node-1, specified on the Node Names screen, 
is 192.168.1.124. The 192 in the first octet puts this address in 
the range of “Class C” addresses, which means the first 3 octets 
are used for the network ID and the fourth octet is used for host 
IDs.
The subnet mask defines the network and host parts of the IP 
addresses. In the Subnet Mask for this example (192.168.1.224), 
the 224 in the fourth octet indicates that 3 high-order bits from 
the fourth octet are used to define subnets on the network 
192.168.1 (224 = 128+64+32 = 11100000). The first 3 bits are 
used for subnet IDs and the last 5 bits are used for host IDs. 
Eight subnets can be defined with 3 bits and each subnet can 
have a maximum of 32 hosts, defined with the remaining 5 bits. 
Of these, only 6 subnets with 30 hosts each are usable. 
The usable IP addresses in the 6 subnets have the following 
ranges of values for the fourth octet: 33–62,  65–94,  97–126, 
129–158,  161–190, and 193–222. The IP address for this 
(node-1) IP interface, 192.168.1.124, is on the third subnet 
because 124 lies in the range 97–126. Note that node 2 (adjunct, 
192.168.1.125) and node 3 (router, 192.168.1.97) are both also 
on the third subnet. Node 4 (192.168.1.51) and node 5 
(192.168.1.39) are both on the first subnet.
The first and last IP addresses in each subnet are not usable as 
host addresses because they have all 0’s or all 1’s for host IDs. 
For example, in the third subnet, the fourth octet of the first IP 
address is 96 (= 01100000
) and the fourth octet of the last IP 
address is 127 (= 01111111
). 
The “network address” of a subnet is the first IP address (the all 
0’s host ID) of that subnet. In this example, the subnet addresses 
of the six subnets are — 1st: 192.168.1.32 2nd: 192.168.1.64 
3rd: 192.168.1.96 4th: 192.168.1.128 5th: 192.168.1.160 
6th: 192.168.1.192. 
See Chapter 1 for more information on IP addresses and 
subnetting.
Gateway Addr Enter the address of a network node that will serve as the default 
gateway for the IP interface.
Net Rgn Enter the region number for this IP interface. Field Conditions/Comments
2 of 2 
						

							Configuration 2: R7r (+CMS)  R7csi 
79
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 1 Task — Assign Link via ethernet Data Module to the LAN  
This task administers an ethernet data module for the ethernet connection to the CMS 
adjunct and to Switch 2. The data module defines a network interface — it associates 
a link number with a port address and node name for the C-LAN port used for this 
connection.
Begin
Steps
> Open Data Module form — enter  a da n
> Enter values
> Submit the screen
End
add data-module next 
                                                                  Page 1 of X
                           DATA MODULE
    Data Extension: 2377            Name: ethernet on link 2  
Type: ethernet              Port: 01c0817_
              Link: 2 
Network uses 1’s for broadcast addresses? y
Field Conditions/Comments
Type: This indicates the data-module type for this link.
Port: Ethernet connections must be assigned to port 17 on the C-LAN 
circuit pack.
Link:The link number must be in the range 1 – 33 (for G3r), not 
previously assigned on this switch.
Name: This field is information-only; it appears in lists generated by the 
“list data module” command.
Network 
uses 1’s for 
broadcast 
addresses?Leave the default (y) if the private network contains only 
DEFINITY switches and adjuncts. Set to n only if the network 
includes non-DEFINITY switches that use the 0’s method of 
forming broadcast addresses. See Appendix A, “Data Module - 
type ethernet” for more information about this field. 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
80
Switch 1 Task — Assign Processor Channels
This task associates data links (hardware) with processor channels (software) on the 
node 1 switch. 
Begin
Steps
> Open the Processor Channel Assignment form — enter  ch com p
> Enter values
change communications-interface processor-channels
                                                                    Page 1 of X
PROCESSOR CHANNEL ASSIGNMENT
Proc                Gtwy        Interface    Destination      Session    Mach
Chan Enable  Appl.  To  Mode  Link/Chan   Node       Port  Local/Remote  ID
  1:  y
 mis____  s 2_ 5001__ node-2____ 0____ 1 _ 1_ __
  2:  n  _______   _    __  _____  __________  0____  ___   ___    __
  3:  n
  _______   _    __  _____  __________  0____  ___   ___    __
  4:  n  _______   _    __  _____  __________ 0____  ___   ___    __
  :
12: y
  dcs___ s    2_ 5003__ node-5____ 0____ 12_21_    2_:    
 64:  n ________   _    __  _____  __________  0____  ___   ___    __
Field Conditions/Comments
Processor Channel 1: (connection to CMS)
Enable Set to y.
Appl. Enter mis for the CMS connection on Processor Channel 1.
Mode Set the Mode to s (“server”) on both switches for connections 
to CMS.
Interface Link This must match the link number assigned on the node-1 data 
module screen.
Interface Chan For TCP/IP, interface channel numbers are in the range 5000 
– 64500.
The recommended values are: 5001 for CMS, 5002 for Intuity 
AUDIX, and 5003 for DCS connections that are not 
gateways. These three values should be reused for multiple 
instances of these applications; for example, if there are two 
Intuity AUDIX’s, use 5002 for both; or if there are four 
DEFINITY ECS’s, use 5003 for all four. The combination of 
Link, Interface Channel, and Mach ID must be unique.
The recommended values for gateway switches is 6001–6099. 
The interface channel number must be unique for each 
gateway.
1 of 3