[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1986.0. "Register / CISCO Address Translation Gateway / Cluster Alias ?" by CSC32::D_GARZANITI (Dominick Garzaniti CSC/CS Networks) Mon Dec 23 1991 15:56

Hi,

I have a customer who is trying to register a node that is accessible through
a CISCO Address Translation Gateway and she is getting and error that the node
is a Cluster Alias.

It appears that this nodes real address is 48.135 and this CISCO Address
Translation Gateway is telling the MCC node that the address is 51.4.

When the customer attempts to register the address 51.4, MCC returns a message
that specified node4 is a cluster alias, use a cluster member and it gives the 
address 48.135.

Whe she attempts to register the address 48.135, MCC returns this same message
indicating that 48.135 is a cluster alias and a member address.

Has anyone seen this before either with the CISCO or our Address Translation
Gateway product ?

I can understand how MCC believes that the address 51.4 is reachable via the
node 48.135 and assumes this to be a cluster alias, however what I don't 
understand is why it thinks the address 48.135 is a cluster alias as well.

Any hint or pointers are greatly appreciated.

Thanks in advance.

Dominick Garzanit
CSC/CS Networks
T.RTitleUserPersonal
Name
DateLines
1986.1Knock Knock KnockCSC32::D_GARZANITIDominick Garzaniti CSC/CS NetworksMon Dec 30 1991 14:052
HELLO, is there is anybody home ?

1986.2Two different hosts at 48.135SUBWAY::REILLYMike Reilly - New York Bank DistrictMon Dec 30 1991 15:2813
    When customers use address translation gateways they are usually
    tring to cope with a networking environment where the same network
    address's have been used at different sites in the same internet.
    
    In this case it appears that there may be two 48.135s on the
    network.  With the cisco address translating software enabled
    attempts to register 51.4 should fail beacuse it appears to be a
    cluster alias.  Attempts to register 48.135 should fail because this
    address should be unreachable.  If 48.135 is responding then it is a
    different host.  Try setting host t0 48.135 and 51.4 and see if they
    are the same machine.
    
    - Mike