Title: | DEC WANrouter 90/250 V1.3 |
Notice: | KITS and DOCS: see note 815 4 |
Moderator: | MGB::GILLOTT R |
Created: | Thu Jun 18 1992 |
Last Modified: | Thu Jun 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 971 |
Total number of notes: | 4115 |
Hello I will require some advice and comments on the following configuration.\ I have tried to put in the maximum info which might help u in understanding the situation. The Scenario ============ LEASED LINE thinwire -------|---MODEM--------------MODEM-----WR90(1)-------------ALPHA (192.9.200.18) x.25 |------VAX1(VMS/UCX/DECNETOSI) HAVING DSV11 (UNIX/TCPIP) switch | -------|-| | MODEM |LEASED LINE | MODEM | | ---------- THINWIRE x.25 |--------WR90(2)-----------------VAX(2)-----ETC----ETC-----| switch | (vms/ucx/decnetosi) | ---------- INFORMATION =========== DTE address of WR90(1) 40495090 DTE address of WR90(2) 40491020 IP address of alpha 192.9.200.18 IP address of WR90(1) 192.9.200.100 IP address of WR90(2) 196.6.5.1 IP address of VAX(2) 196.6.0.1 IP address of VAX(1) 193.6.0.1 DTE address of VAX(1) 40495010 The alpha is used to download Router image and management file for WR90(1) using decrou_host_config and vr2_router_config (DECnetosi was temporarily loaded to do this) OBJECTIVE ========= I want to reach VAX(2) from alpha over tcpip EXERCISE DONE ============= WR90(1) has been configured to run IP routing,RIP has been enabled on csmacd circuit The serial port of WR90(1) is configured to run X.25 X.25 dynamic circuit has been defined to route IP data only The filter for this circuit has been defined with incoming DTE address as 4049* OSI reachable address is not defined IP reachable address has been defined to reach over X.25 dynamic circuit Destination IP address has been given as 196.6.0.1 (that of VAX2) DTE address of next IP router has been defined as 40491020(that of WR90(2)) ---------------------------------------------------------------------------- QUESTION ======== 1>>The WR90(2) configuration is not in my hands. Have i configured WR90(1) correctly so that it reaches VAX(2) over tcpip. Should there be a similar X25 dynamic circuit on the WR90(2) side defined which should actually point to receive incoming calls from alpha. 2>>What is to be done to reach VAX(1) from alpha over tcpip,both on alpha side and VAX(1) side. ASSUMPTIONS =========== For all templates and filters defined there is no ambiguity in DTE class, call data value and call data mask. Actually this connectivity is to be done in minimum time ,hence i want the clarifications. thanks in advance Somenath Ghose
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
963.1 | MARVIN::WALTER | Mon Mar 10 1997 10:58 | 27 | ||
>QUESTION >======== >1>>The WR90(2) configuration is not in my hands. > Have i configured WR90(1) correctly so that it reaches VAX(2) over tcpip. > Should there be a similar X25 dynamic circuit on the WR90(2) > side defined which should actually point to receive incoming calls > from alpha. Yes, you certainly need to define a dynamic circuit in both WR90's. And not just for incoming calls, since either DA circuit may want to initiate the call request if it has data to send. Basically the configurations will be symmetrical, apart from the appropriate IP and X25 address assignments. >2>>What is to be done to reach VAX(1) from alpha over tcpip,both on alpha side and VAX(1) side. I don't know how to configure UCX over PSI. In fact I don't think that you can. You might try asking in the HELP::DECNET-OSI_FOR_VMS or LASSIE::UCX notes conferences. It's most likely that you would need another WR90 for the VAX1 site. Or, if you need native mode PSI at VAX1, then you would have to use a Routeabout90. |