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

Conference smurf::ase

Title:ase
Moderator:SMURF::GROSSO
Created:Thu Jul 29 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2114
Total number of notes:7347

1908.0. "De500 100M arp failover" by GIDDAY::SCHWARZ () Sun Mar 02 1997 21:29

    
    
    This is a slimilar problem that has been reported elsewhere without
    resolution.
    
    A customer has a service that has an ip address associated to it ( not
    sure if its a NFS or disk service ). When the service fails over
    DECsafe issues an
    
    ifconfig xx -alias xxxx netmask xxxx and a
    ifconfig xx alias xxxx netmask xxxx
    
    The customer has DE500 network cards and this works fine when the cards
    are set to 10M. Their router does  see a 
    
    src IP=(service IP for www-main) / dest IP=(service IP for www-main)
    
    If they set the cards to 100M this does not occur and they are not
    able to ping the alias address.
    
    They are running v4.0B and Trucluster 1.4
    
    Has anyone seen this before? Any suggestions as to what is going on?
    
    
    Regards
    
    Kym Schwarz
    Unix support 
    CSC Sydney
    
T.RTitleUserPersonal
Name
DateLines
1908.1KITCHE::schottEric R. Schott USG Product ManagementThu Mar 06 1997 07:4936
Hi

I suggest you file an  IPMT to escalate this...

>
>    
>    
>    This is a slimilar problem that has been reported elsewhere without
>    resolution.
>    
>    A customer has a service that has an ip address associated to it ( not
>    sure if its a NFS or disk service ). When the service fails over
>    DECsafe issues an
>    
>    ifconfig xx -alias xxxx netmask xxxx and a
>    ifconfig xx alias xxxx netmask xxxx
>    
>    The customer has DE500 network cards and this works fine when the cards
>    are set to 10M. Their router does  see a 
>    
>    src IP=(service IP for www-main) / dest IP=(service IP for www-main)
>    
>    If they set the cards to 100M this does not occur and they are not
>    able to ping the alias address.
>    
>    They are running v4.0B and Trucluster 1.4
>    
>    Has anyone seen this before? Any suggestions as to what is going on?
>    
>    
>    Regards
>    
>    Kym Schwarz
>    Unix support 
>    CSC Sydney
>