04.11.2014 Views

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuration 4: R8csi R8si Gateway<br />

R8csi<br />

3 C-LAN <strong>Admin</strong>istration<br />

> Submit the screen<br />

End<br />

Field<br />

Session - Local<br />

Session -<br />

Remote<br />

Mach ID<br />

The Local and Remote Session numbers can be any value<br />

between 1 and 256 (si model) or 384 (r model), but they must<br />

be consistent between endpoints. For each connection, the<br />

Local Session number on this switch must equal the Remote<br />

Session number on the remote switch and vice versa.<br />

It is allowed, and sometimes convenient, to use the same<br />

number <strong>for</strong> the Local and Remote Session numbers. It is<br />

allowed, but not re<strong>com</strong>mended, to use the same Session<br />

numbers <strong>for</strong> two or more connections.<br />

Destination switch ID identified on the dial plan of the<br />

destination switch.<br />

Processor Channel 32: (connection to Switch 1 <strong>for</strong> gateway to Switch 2)<br />

Enable Set to y.<br />

Appl.:<br />

Set to dcs <strong>for</strong> DCS signaling.<br />

Mode<br />

Node-3 is the “client” <strong>for</strong> this session. Set node-1 to “server”<br />

(s).<br />

Interface Link This must match the link number assigned on the data module<br />

screen.<br />

Interface Chan A value of 0 allows any available interface channel to be used<br />

<strong>for</strong> this connection. This number must match the Destination<br />

Port number on the Switch-1 Processor Channel screen.<br />

Destination<br />

Node<br />

Destination Port<br />

Session - Local<br />

Session -<br />

Remote<br />

Mach ID<br />

Conditions/Comments<br />

Node name <strong>for</strong> the gateway through which the destination is<br />

reached. This must be a name entered on the Node Names<br />

screen. For ppp connections, it must match the Destination<br />

Node Name entered on the ppp Data Module screen.<br />

This must match the Interface Channel number assigned on<br />

the Switch-1 Processor Channel screen.<br />

For each connection, the Local Session number on this switch<br />

must equal the Remote Session number on the remote switch<br />

and vice versa.<br />

Destination switch ID identified on the dial plan of the<br />

destination switch.<br />

2 of 2<br />

144<br />

<strong>Admin</strong>istration <strong>for</strong> <strong>Network</strong> <strong>Connectivity</strong><br />

CID: 77730 555-233-504 — Issue 1 — April 2000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!