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

							Configuration 2: R7r (+CMS)  R7csi 
81
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Destination Node Name of the far-end node for this channel. This must be a 
name entered on the Node Names screen. 
Destination Port A value of 0 allows any available interface channel on the 
destination node to be used for this connection. The Interface 
Channel number on the Switch-2 Processor Channel screen 
must also be set to 0.
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 This field is not used for CMS.
Processor Channel 12: (ethernet connection to Switch 2)
Enable Set to y.
Appl. Enter dcs for the DCS connection on Processor Channel 12.
Mode Set the node-5 Mode field to c (“client”) on the Processor 
Channel Assignment screen on Switch 2.
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.
Destination Node Name of the far-end node for this channel. This must be a 
name entered on the Node Names screen.
Destination Port A value of 0 allows any available interface channel on the 
destination node to be used for this connection. The Interface 
Channel number on the Switch-2 Processor Channel screen 
must also be set to 0. Field Conditions/Comments
2 of 3 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
82
> 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. This is the Local Node Number on the 
dial plan of the destination switch. Field Conditions/Comments
3 of 3 
						

							Configuration 2: R7r (+CMS)  R7csi 
83
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 2 Task — Enable Bus Bridge Connectivity
This task enables the bus bridge functionality on the C-LAN circuit pack to provide a 
path between the packet bus and the processor. 
Note:Bus Bridge Connectivity is used on the csi model only. This task may 
have been completed when the C-LAN circuit pack was installed.
Begin
Steps
> Open the Maintenance-Related System Parameters form — enter  ch sys ma
> Go to page 2 and skip to the Packet Intf2? field near the bottom of the screen.
> Enter values
> Submit the screen
End
change system-parameters maintenance                            Page   2 of   3
 
                   MAINTENANCE-RELATED SYSTEM PARAMETERS           
MINIMUM MAINTENANCE THRESHOLDS ( Before Notification )
        TTRs: 4        CPTRs: 1        Call Classifier Ports: 0  
        MMIs: 0          VCs: 0  
TERMINATING TRUNK TRANSMISSION TEST ( Extension )
   Test Type 100:          Test Type 102:          Test Type 105:     
ISDN MAINTENANCE
   ISDN-PRI Test Call Extension:         ISDN-BRI Service SPID:           
DS1 MAINTENANCE
   DS0 Loop-Around Test Call Extension:      
LOSS PLAN ( Leave Blank if no Extra Loss is Required )
   Minimum Number of Parties in a Conference Before Adding Extra Loss:  
SPE OPTIONAL BOARDS
                     Packet Intf1? y     Packet Intf2? y
         Bus Bridge: 01a05_
  Inter-Board Link Timeslots  Pt0: 6 Pt1: 1 Pt2: 1
Field Conditions/Comments
Packet Intf2? Enables the bus bridge.
Bus Bridge: Location of the C-LAN circuit pack. If the system has two
C-LANs, only one is administered for bus bridge.
Inter-Board 
Link 
Timeslots: 
Pt0, Pt1, Pt2Specifies the bandwidth used on the 3 ports of the Inter-Board 
Link. The total number of timeslots assigned cannot exceed 11. 
Pt0 carries PPP traffic and can have 1–9 timeslots. Pt1 carries 
maintenance messages and can have 1–3 timeslots. Pt2 carries 
broadcast messages and can have 1–3 timeslots. 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
84
Switch 2 Task — Assign Node Names
This task assigns node names and IP addresses to each node in the network on the 
Node Names screen. This screen is administered on Switch 2. A Node Names screen 
must be administered on each switch in the network.
The node names and IP addresses in a 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__  _______________ ___.___.___.___
net-96  _
 192.168.1 _.96 _______________    ___.___.___.___
node-1  _ 192.168.1 _.124  _______________    ___.___.___.___
node-2___        192.168.1 _.125   _______________    ___.___.___.___
node-4_____
_____  192.168.1 _.39_ _______________    ___.___.___.___
node-5__________  192.168.1 _.51_ _______________    ___.___.___.___
Field Conditions/Comments
Name: Enter node names for the following 5 nodes:
•net-96: the network address of the node-1 and node-2 subnet
(this is described in the IP-Route task)
•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-4: Interface on the router to the subnet of Switch 2.
•node-5: C-LAN Ethernet port on Switch 2.
IP Address: The unique IP addresses of the nodes named in the previous field. 
						

							Configuration 2: R7r (+CMS)  R7csi 
85
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 2 Task — Define 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  01a05 TN799 B  node-5  255.255.255.224  ___
.___.___.__ 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.
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
86
Subnet Mask Enter the subnet mask associated with the IP address for 
this IP interface. (The IP address is associated with the 
node name on the Node Names screen). 
Since the node-1 and node-5 IP interfaces are on the same 
network (192.168.1), they must be assigned the same 
subnet mask.
In this example, the subnet mask 255.255.255.224 divides 
the network 192.168.10 into 6 (usable) subnets. This 
C-LAN IP Interface (node-5) is on the first subnet. See 
Switch 1 Task — Assign IP Interfaces  (page 77) for an 
explanation of this subnet. See Subnetting  (page 16) in 
Chapter 1 for a detailed description of subnetting.
Gateway Addr Leaving this field blank adds a level of network security 
for this IP interface but requires that IP routes be 
administered to enable communication with nodes on 
different (sub)networks.
Net Rgn Enter the region number for this IP interface. Field Conditions/Comments
2 of 2 
						

							Configuration 2: R7r (+CMS)  R7csi 
87
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Switch 2 Task— Assign Link via ethernet Data Module to the LAN
This task administers an ethernet data module on Switch 2 for the ethernet connection 
to Switch 1. 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 n
[This data module is assigned the next available extension, 3020.]
> Enter values
> Submit the screen
End
add data next 
                                                                  Page 1 of X
                        DATA MODULE
    Data Extension: 3201  Name: ethernet on link 5  
 Type: ethernet              Port: 01a0517_
              Link: 5 
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. In this example, the C-LAN circuit pack is in slot 
1a05.
Link:The link number must be in the range 1 – 25 (R8csi), not 
previously assigned on this switch.
Name: Information-only; appears in list 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
88
Switch 2 Task — Assign IP Route (to Switch 1)
This task specifies a route for packets sent by the node 5 IP interface (the ethernet port 
on the switch-2 C-LAN board) to the nodes 1 and 2. An IP route is required because 
node 5 is on a different subnetwork from nodes 1&2 (as defined in the Subnet Mask 
field on the IP Interfaces screen), and the Gateway Address field for node 5 on the IP 
Interfaces screen was left blank. 
The Destination Node will be set to “net-96”, which is associated with the network IP 
address of 192.168.1.96 on the Node Names screen. This will enable node 5 to 
communicate with any node on the 192.168.1.96 subnetwork.
Begin
Steps
> Open the IP Routing form — enter  a ip n
[The system assigns the route number 2.]
> Enter values
> Submit the screen
End
add ip-route next  Page   1 of   1 
IP ROUTING 
     Route Number: 2 
 Destination Node: net-96 _
__          Gateway: node-4        C-LAN Board: 1c05 
Metric: 0
 
Field Conditions/Comments
Destination 
Node:The name of the node at the destination of this route. In this case, 
net-96 is associated with IP address 192.168.1.96 on the Node 
Names screen. This is the network IP address of the subnet that 
nodes 1 and 2 are on. See the description of the Subnet Mask field 
in Switch 1 Task — Assign IP Interfaces  (page 77).
Gateway: Node name of the IP-route gateway by which the destination node 
is reached for this route. In this case, it is the node name of the 
router port.
C-LAN 
Board:The location of the C-LAN circuit pack that provides the interface 
for this route. 
Metric: Enter 0.
See IP Routing  (page 251) in Appendix A for more information 
on the use of the Metric field. 
						

							Configuration 2: R7r (+CMS)  R7csi 
89
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Note:We could have defined 2 individual IP routes, one each to node-1 and 
node-2, instead of this IP route. However, the network route is easier 
because we need only one. The network route enables packets to get to 
any IP address on the 192.168.1.96 subnet (that is, addresses 
192.168.1.97 through 192.168.1.126), so no other IP routes are needed.
No IP routes were needed on Switch-1 because a gateway address was 
assigned to the C-LAN on the IP Interfaces screen. IP routes are needed 
in only two cases: when a gateway address is not assigned for an ethernet 
interface, and when there are intermediate nodes between the endpoints 
of a ppp connection. 
						

							Configuration 2: R7r (+CMS)  R7csi 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
90
Switch 2 Task— Assign Processor Channels
This task associates data links (hardware) with processor channels (software) on 
Switch 2.
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 5_ 5001__ node-2____ 0____ 1 _1__ __
  2: n  _______   _    __  _____  __________  0____  ___   ___    __
  3:  n
  _______   _    __  _____  __________  0____  ___   ___    __
  4:  n  _______   _    __  _____  __________ 0____  ___   ___    __
  :
21:   y
  dcs___ c 5_ 0 node-1____ 5003_  21_ 12_    1_:    
 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-5 data 
module screen on this switch.
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