Eicon Networks S52 Guía de usuario descargar pdf (Pagina 50)

Using Eiconcard Routing Services

page 48

7. On Sys-2, set the password authentication parameters as follows:

Local PAP User Name System2

Local PAP Password Pass2

Remote PAP User Name System1

Remote PAP Password Pass1

Local CHAP User Name Sys2

Local CHAP Secret Password

Remote CHAP User Name Sys1

8. Press F3 twice to return to the Protocol Configuration screen. Leave the default value for

Dialer selection, Direct, for both systems.

9. Access the Sync Driver Configuration screen (via Dialer selection) and set Clocking to

Internal for Sys-2. Sys-1 keeps the Clocking default, External.

10. On the same screen, you can set Line speed (bps) up to 64000 for Sys-2, provided you

are using a maximum length of 8 feet for the RS-232 cable that will connect the two

Eiconcards back to back.

11. Once the parameters are set, press F2 Save and F10 to exit. The two ec.cfg files are now

configured for Sys-1 and Sys-2’s back-to-back connection.

12. If the Eiconcard is already loaded and running (using eccard start), run eccard stop

to stop it.

13. Connect the Eiconcard in Sys-1 to the Eiconcard in Sys-2 with an RS-232 null-modem cable.

14. Run eccard start on both systems to start the Eiconcards. The Eiconcards on each system

are loaded and configured according to the parameters found in the system’s ec.cfg file.

15. Once eccard start has run successfully (no errors reported), you can use ecstatus on

both systems to check the integrity of the connection between Sys-1 and Sys-2.

16. Create a test circuit on both systems. Two sample files, sys1pap.if and sys2pap.if, are

provided with Routing Services which are configured for the purpose of running this test.

Sys-1 is configured as the authenticator and Sys-2 as the system to be authenticated, as

shown in the sample circuit definitions.

Note: When using PAP and CHAP to configure Eiconcard Routing Services, one side of the

connection must be configured as the authenticator for incoming connections, and the

other as the system to be authenticated, that is, the system making the call.

Note: Circuit names need only be unique within one Linux system; you can specify the

same name for the test circuits used on Sys-1 and Sys-2.

17. Ensure the Eiconcards are already started, and run mprload -f sys1pap.if on Sys-1 and

mprload -f sys2pap.if on Sys-2. This loads the specified interface file down to the

Eiconcard Routing Services driver. If the -f option is not specified, the default file mpr.if

is loaded down to the driver.

18. Run mprstart on both systems to start the circuits. If you stop an Eiconcard after creating

a circuit entry, use mprstart to restart the circuit once you have restarted the card.

Important: If these parameters are not configured correctly on both

sides of the connection, the circuits will not start.

1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 90 91

Comentarios a estos manuales

Sin comentarios

Eicon Networks S52 Guía de usuario Pagina 50

Comentarios a estos manuales

Relacionado con productos y manuales para Redes Eicon Networks S52