[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC Network Integration Server (DECNIS) |
| Notice: | Please read note 1 to use this conference effectively |
| Moderator: | MARVIN::WELCH |
|
| Created: | Wed Sep 18 1991 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3660 |
| Total number of notes: | 15082 |
3618.0. "Manual adjacency problem between DECnis and VMS DSG" by SCASS1::ROCHELEAU (Rod Rocheleau - 972-527-2272) Mon Apr 28 1997 21:31
We are having manual adjacency problems with system behind a VMS secure gateway.
Any help on the problem would be appreciated, the customer has been down
since the DECnis's on the public side of the gateway were converted to IS-IS.
DECnis on Public side of network CXO28E, CXO28F
The secure gateway is node GATE01 28.696 - AA-00-04-00-B8-72
There are 24 nodes behind the gateway
example: CHIMAY 28.23 aa-00-04-00-17-70
LONGNK 28.167 aa-00-04-00-a7-70
The command used to add these adjacencies is as following
create routing circuit securenet adja Gate01_chimay -
lan addr AA-00-04-00-B8-72, -
endnode ids { AA-00-04-00-17-70}, data format phaseiv
create routing circuit securenet adja Gate01_longnk -
lan addr AA-00-04-00-B8-72, -
endnode ids { AA-00-04-00-A7-70}, data format phaseiv
The problem is that connectivity to these nodes does not work most of the time.
Sporadically connectivity is possible but we have never fully established
what causes it to work. We do know that if you log onto the node behind the
gateway, and then set host to a system on the other side of the gateway
connectivity is established. Once the connection between the systems is
closed, communication between the public side of the net and the secure system
is not possible.
Ncl show
Node .cxo.cxo28e Routing Circuit securenet Adjacency Gate01_chimay
AT 1997-04-28-16:26:46.251-05:00I-----
Identifiers
Name = Gate01_chimay
Status
Type = Manual
State = Up
LAN Address = aa-00-04-00-b8-72 (DEC:.cxo.gate01)
Neighbor Node Type = Phase IV Endnode
Endnode IDs =
{
aa-00-04-00-17-70 (28.23)
}
Endnode NETs =
{
49::00-1C:AA-00-04-00-17-70:00
}
Node .cxo.cxo28e Routing Circuit securenet Adjacency Gate01_longnk
AT 1997-04-28-16:26:47.361-05:00I-----
Identifiers
Name = Gate01_longnk
Status
Type = Manual
State = Up
LAN Address = aa-00-04-00-b8-72 (28.696)
Neighbor Node Type = Phase IV Endnode
Endnode IDs =
{
aa-00-04-00-a7-70 (28.167)
}
Endnode NETs =
{
49::00-1C:AA-00-04-00-A7-70:00 (DEC:.cxo.longnk)
}
_______
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3618.1 | Reverse Path? | MARVIN::SHAND | Mike Shand | Tue Apr 29 1997 09:38 | 8 |
| I know nothing about the secure gateway, but you have described how the
connectivity from the decnis to the gateway is set up (and that looks OK), but
you have not described the connectivity in the reverse direction. (nor for that
matter have you described the connectivity in either direction between the
actual nodes and the gateway. My guess would be that you have a problem
with one or more of these other 3 connections.
Mike
|
| 3618.2 | Thanks, problems appears to be solved | SCASS1::ROCHELEAU | Rod Rocheleau - 972-527-2272 | Tue Apr 29 1997 13:31 | 9 |
| Mike
Thanks for the sanity check ... the command works exactly as advertized
but it has to point to the right LAN before it will work. Your analysis pushed
us to look in the right place for the problem. The Secure Gateway was found, the
manual adjancency was moved and all appears to be working now.
Thanks again
Rod
|