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

							Configuration 3:R8si R8r Gateway 
 R8si 
121
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 3 Task — Assign Processor Channels 
This task associates data links (hardware) with processor channels (software) on 
Switch 3.
Begin
Steps
> Open Processor Channel Assignment form — enter  ch com p
Note:The Processor Channel number, the Interface Channel number, and the 
Local and Remote Session numbers do not need to be the same number 
but they should be made the same whenever possible to simplify network 
“bookkeeping” and diagnostics.
> 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:  n
 _______  _     __  _____  ____________ 0____  ___   ___    __
  2:  n  _______  _     __  _____  ____________ 0____  ___   ___    __
:
31: y
 dcs____  c    3_0_ node-1______ 5003 31_   31_    1_
:    
32: y
 dcs____ c 3_ 0node-1______ 6002 32_   32_    2_
 :    
256:  n
  _______  _     __  _____  ____________ 0____  ___   ___    __
Field Conditions/Comments
For Processor Channel 31: (ethernet connection to Switch 1)
Enable Set to y.
Appl. Indicates that this connection will carry DCS data.
Mode Node-3 is the “client” for this session. Set node-1 to 
“server” (s).
Interface Link This must match the link number assigned on the node-3 
data module screen.
Interface Chan A value of 0 allows any available interface channel to be 
used for this connection. This number must match the 
Destination Port number on the Switch-1 Processor 
Channel screen.
Destination Node Name of the far-end node for this channel. This must be a 
name entered on the Node Names screen.
1 of 2 
						

							Configuration 3:R8si R8r Gateway 
 R8si 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
122
> Submit the screen the screen
End
Destination Port The Destination Port number must match the Interface 
Channel number for this connection on the Switch-1 
Processor Channel screen.
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.
Processor Channel 32: (connection to Switch 1 for gateway to Switch 2)
Enable Set to y.
Appl. Set to dcs for DCS signaling.
ModeNode-3 is the “client” for this session. Set node-1 to 
“server” (s).
Interface Link This must match the link number assigned on the node-3 
data module screen.
Interface Chan A value of 0 allows any available interface channel to be 
used for this connection. This number must match the 
Destination Port number on the Switch-1 Processor 
Channel screen.
Destination Node Name of the far-end node for this channel. This must be a 
name entered on the Node Names screen.
Destination Port The Destination Port number must match the Interface 
Channel number for this connection on the Switch-1 
Processor Channel screen.
Session - Local For each connection, the Local Session number on this 
switch must equal the Remote Session number on the 
remote switch and vice versa. Session - Remote
Mach ID Destination switch ID identified on the dial plan of the 
destination switch. Field Conditions/Comments
2 of 2 
						

							Configuration 3:R8si R8r Gateway 
 R8si 
123
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
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 4:  R8csi  R8si Gateway 
 R8csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
124
Configuration 4:  R8csi  R8si Gateway  R8csi 
In this configuration, a DEFINITY ECS R8r provides gateway conversion between 
ISDN and TCP/IP.
Task Summary
The following tasks need to be completed for Switch 1, Switch 2, and Switch 3:
1  Review checklist
2  Switch 1 administration
 a  Assign node names
 b  Assign signaling group and administered NCA TSC
 c  Assign ISDN-TSC Gateway Channel
 d  Assign link (via a data module) to node 3
 e  Assign processor channels
3  Switch 2 administration
 a  Assign signaling group and administered NCA TSC
4  Switch 3 administration
 a  Enable bus bridge connectivity
 b  Assign node names
 c  Assign link (via a data module) to node 1
 d  Assign processor channels
5  Enable links and processor channels
DEFINITY
ECS R8si
ISDNSwitch 1
DEFINITY ECS
Switch 3
DEFINITY ECS
Switch 2
R8csi ppp    
R8csi
DS1
DS1
node-3 node-1
DS1
C-LAN
DS1
C-LAN 
						

							Configuration 4:  R8csi  R8si Gateway 
 R8csi 
125
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Prerequisite Administration
There are some system administration tasks that need to be completed before you can 
proceed with the connectivity administration described in this section.
Review the checklist of prerequisite administration tasks in Checklist for Prerequisite 
Administration  (page 54), before proceeding with the connectivity administration in 
this section.
SWITCH 2 SWITCH 1 SWITCH 3
Configuration 4
DEFINITY ECS R7csi DEFINITY ECS R7si DEFINITY ECS R7csi
Processor
channelsInterface
channels Interface
channelsProcessor
channels
1
2
13
14
2561
2
31
32
256 1
5000
5001
64500 1
5000
5001
5003
6002
64500
Link 1 Link 1
x
x1
2(any)
(any) 1
1 1
1Sig
Grp Sig
Grp
Index
1
2 Index
1
2Extn
2951
2952 Extn
1701
1702gateway
Bus
bridge
Voice
data
ppp
data
Bus
bridge
hardware connections
Processor
TN790B
Processor
bus
Packet bus
TDM
bus TDM bus TDM
bus
Packet bus Packet bus
Proc
798B DS1
TN767/
TN464 DS1
TN767/
TN464Processor
TN798BVoice
data
ISDN-PRI
dataNetPkt
TN794
43
21
cydfec4a EWS 052099
Ext 1701
Ext 1702
loc 1a1024Ext 2951
Ext 2952
loc 1b0924node-1
Ext 5803
loc 1b1115
192.168.10.101node-3
Ext 2801
loc 1a0906
192.168.10.103
1324
DS1
TN767/
TN464DS1
TN767/
TN464
C-LAN
TN799 C-LAN
TN799C-LAN
TN799
software-defined connections 
						

							Configuration 4:  R8csi  R8si Gateway 
 R8csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
126
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 from 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.10_.101    _______________    ___.___.___.___
node-3___        192.168.10_.103    _______________    ___.___.___.___
________________  ___.___.___.___    _______________    ___.___.___.___
Field Conditions/Comments
Name Enter unique node names for the following 2 nodes:
•C-LAN PPP port on Switch 1
•C-LAN PPP port on Switch 3.
IP Address The unique IP addresses of the nodes named in the previous 
field. 
						

							Configuration 4:  R8csi  R8si Gateway 
 R8csi 
127
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 1 Task — Assign Link via ppp Data Module to Switch 3
This task administers a ppp data module for the ppp connection to node 3. The data 
module associates a link number with a port address, extension number, and node 
name for the C-LAN port used for this connection.
Begin
Steps
> 
Open Data Module form — enter ad da 5803
[This data module is assigned the extension 5803; you can assign any unused 
extension in the dial plan]
> Enter values
add data-module 5803 
                                                                 Page 1 of x
                          DATA MODULE
    Data Extension: 5803            Name: _ppp on link 1 to node-3___
  BCC: 2
              Type: ppp
     COS: 1              Port: 01b1115      COR: 1              Link: 1_            TN: 1
       Enable Link? n
         Node Name: node-1 _____
Subnet Mask: 255.255.255.0 
Establish Connection: y
DESTINATION
            Digits: 792801
_________
      Node Name: node-3_________
              CHAP? n
Field Conditions/Comments
Type: This indicates the data-module type for this connection.
Port: In this example, the C-LAN circuit pack is in slot 01b11; the ppp 
connection is through port 15.
Link: The link number must be in the range 1 – 25 (for R8si), not 
previously assigned on this switch.
Enable 
Link?If you need to add an IP route that uses this node as a gateway, 
this field must be set to 
y before adding the IP route. Otherwise 
leave this field set to 
n until the link administration is complete; 
that is, until after all data modules and the processor channels are 
assigned, then set to 
y.
Name: Information-only; appears in list generated by the “list data 
module” command.
1 of 2 
						

							Configuration 4:  R8csi  R8si Gateway 
 R8csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
128
> Submit the screen
End
BCC: Bearer Capability Class. This is a display-only field.
COS
The values for these fields will be specified by the system 
administrator. COR:
TN:
Node Name: The node name for the interface defined by this data module. 
This must be a name entered on the Node Names screen.
Establish 
Connection?y means that this switch will be responsible for call setup for this 
connection. Enter n when administering the data module for 
Switch 3.
Destination 
Digits:Trunk access code (79) plus extension of data module on node-3 
(2801).
Destination 
Node Name:Name of the node at the far end of this connection. This must be a 
name entered on the Node Names screen
CHAP? This field enables/disables the Challenge Handshake 
Authentication Protocol security mechanism on this link. If you 
enter y, the system will prompt for a CHAP secret (password). Field Conditions/Comments
2 of 2 
						

							Configuration 4:  R8csi  R8si Gateway 
 R8csi 
129
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
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:  n
  _______   _    __  _____  __________  0____  ___   ___    __
  2:  n  _______   _    __  _____  __________  0____  ___   ___    __
  :  
13:   y
  dcs___ s    1_ 5003_  node-3____ 0 13__ 31_    3_14:   ygateways    1_ 6002_ node-3____ 0 14__ 32___
:
 64:  n
  _______  _    __  _____  __________  0____  ___   ___    __
Field Conditions/Comments
Processor Channel 13: (ppp connection to Switch 3)
Enable Set to y.
Appl. Set to dcs for DCS signaling.
Mode Node-1 is the “server” for this session. Set node-3 to “client” 
(c).
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.
This number must match the Destination Port number on the 
node-3 Processor Channel screen.
1 of 3 
						

							Configuration 4:  R8csi  R8si Gateway 
 R8csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
130
Destination 
NodeName of the far-end node for this channel. This must be a name 
entered on the Node Names screen. For ppp connections, it must 
match the Destination Node Name entered on the ppp Data 
Module screen.
Destination 
PortA value of 0 allows any available interface channel on the 
destination node to be used for this connection. The Interface 
Channel number for this connection on the Switch-3 Processor 
Channel screen must also be set to 0.
Session - 
LocalThe 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.
Processor Channel 14: (Gateway between Switch 2 and Switch 3)
Enable Set to y.
Appl. Set to gateway for conversion between ISDN and TCP/IP.
ModeNode-1 is the “server” for this session. Set node-3 to “client” 
(c).
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.
This number must match the Destination Port number on the 
node-3 Processor Channel screen. Field Conditions/Comments
2 of 3