Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Configuration 3:R8si R8r Gateway R8si 111 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 3 C-LAN Administration 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. 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-3 Processor Channel screen must also be set to 0. 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. Processor Channel 32: (The Ethernet side of the gateway) Enable Set to y. Appl. Use gtwy-tcp for conversion between X.25 and TCP/IP. Gateway To Indicates a software connection between processor channels 32 and 23. 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 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. 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. Field Conditions/Comments 3 of 4
Configuration 3:R8si R8r Gateway R8si 3 C-LAN Administration Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 112 > Submit the screen End 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-3 Processor Channel screen must also be set to 0. 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 Leave blank for gtwy-tcp. Field Conditions/Comments 4 of 4
Configuration 3:R8si R8r Gateway R8si 113 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 3 C-LAN Administration Switch 2 Task — Assign Link via procr-intf Data Module to Switch 1 This task administers a processor-interface data module for the x.25 connection to node 1. The data module associates a link number with a physical channel number and extension number for the PI port used for this connection. Begin Steps > Open Data Module form — enter a da n > Enter values. add data-module next Page 1 of 1 DATA MODULE Data Extension: 4121 Name: _x.25 on link 2 to node-1 __ Type: procr-intf COS: 1 Maintenance Extension: 4191Physical Channel: 02_ COR: 1 Destination Number: 8122102 ITC: Restricted TN: 1 Establish Connection? n Link: 2_ DTE/DCE: dce Connected Data Module: _______ Enable Link: n ABBREVIATED DIALING List1: _______________ SPECIAL DIALING OPTION: ________________ ASSIGNED MEMBER (Station with a data extension button for this data module) Ext Name 1. Field Conditions/Comments Type: This indicates the data-module type for this connection. Physical Channel: This must be the same as the link number. ITC: Enter restricted. (unrestricted is used only for wideband transmission.) Link: The link number must be in the range 1 –25 (for R8si), not previously assigned on this switch. Name: Information-only; appears in list generated by the “list data module” command. COS: The values for these fields will be specified by the system administrator. COR: TN: DTE/DCE: The DTE/DCE assignments must be opposites on the two ends of the connection. Use dte for node 1. 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 114 Enable Link?: Set to y after the processor channels have been assigned. Maintenance Extension: Specified on dial plan. Destination Number: TAC (812) + extension (2102) of the data module on the far end that will establish the connection. Establish Connection?n means that the switch at the remote end of this connection (Switch 1 in this case) will be responsible for the call setup. Enter y when administering the data module for Switch 1. Connected Data Module:This is an information-only field. Keep the default values for the rest of the fields. Field Conditions/Comments 2 of 2
Configuration 3:R8si R8r Gateway R8si 115 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 3 C-LAN Administration Switch 2 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on Switch 2. 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____ ___ ___ __ : 21: y dcs____ _ 2_ 21___ _________ 0____ 21_ 21_ 1_ 23: y dcs____ _ 2_ 23___ _________ 0__23_ 23_ 3_ : 256: n _______ _ __ _____ _________ 0____ ___ ___ __ Field Conditions/Comments Processor Channel 21: (X.25 connection to Switch 1) Enable Set to y. Appl. Set to dcs for DCS signaling. Mode Used for TCP/IP connections only. Interface Link This must match the link number assigned on the procr-intf data module screen. Interface Chan The interface channel number must be in the range 1 – 64 for an X.25 link. Destination Node Used for TCP/IP connections only. Destination Port Used for TCP/IP connections only. 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 116 > 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. This is usually called the “node number.” Processor Channel 23: (connection to Switch 1 for gateway to Switch 3) Enable Set to y. Appl. Set to dcs for DCS signaling. Mode Used for TCP/IP connections only. Interface Link This must match the link number assigned on the procr-intf data module screen. Interface Chan The interface channel number must be in the range 1 – 64 for an X.25 link. Destination Node Used for TCP/IP connections only. Destination Port Used for TCP/IP connections only. 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 117 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 3 C-LAN Administration Switch 3 Task — Assign Node Names This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 3. 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_.1__ _______________ ___.___.___.___ node-3____ 192.168.10_.3__ _______________ ___.___.___.___ ________________ ___.___.___.___ _______________ ___.___.___.___ Field Conditions/Comments Name Enter unique node names for the following 2 nodes: •C-LAN Ethernet port on Switch 3 •C-LAN Ethernet port on Switch 1. IP Address The unique IP addresses of the nodes named in the previous field.
Configuration 3:R8si R8r Gateway R8si 3 C-LAN Administration Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 118 Switch 1 Task — Assign IP Interfaces The IP interface for each C-LAN 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 01a10 TN799 B node-1 255.255.255.0 .._. 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 3:R8si R8r Gateway R8si 119 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 3 C-LAN Administration 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). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address. See the discussion of subnetting, Subnetting (page 16), in Chapter 1 and Configuration 1: R8r R8si (page 60) in this chapter for details about subnet masks. Gateway Addr Leave blank for this configuration. The only connection to this IP interface is node-1 on Switch 1. Node-1 is on the same subnetwork as this IP interface, so no gateway is needed. In general, for connectivity to other (sub)networks, enter the address of a network node that will serve as the default gateway to the other (sub)networks. Net Rgn Enter the region number for this IP interface. Field Conditions/Comments 2 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 120 Switch 3 Task — Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module on Switch 3 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 a da n > Enter values. > Submit the screen End add data module next Page 1 of x DATA MODULE Data Extension: 4531 Name: ethernet on link 3 BCC: 2 Type: ethernet Port: 01a1017 Link: 3_ Network uses 1’s for broadcast addresses? y 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 01a10; the ethernet connection is through port 17. Link:The link number must be in the range 1 – 25 (for R8si), not previously assigned on this switch. Name: Information-only; appears in the “list data module” command list. 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.