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

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

3703.0. "AWxxx and ip services" by ATYISA::CARRAYROU () Thu Jul 11 1996 10:16

        I use with success AW90 version 1.1 or T1.56 as ip service module
    in a DEChub900 V 4.20. I can use clearvisn or ping MAM .
        
    When i upgrade AW90 or AW900 with version T201  , a can ping the AWxxx
    but i can't ping the MAM  
    on the hub console 
        
    show ip config
        
    hub slot 5 10.1.1.60 255.255.255.0 10.1.1.51  active   ( aw90 v1.x)
    hub slot 8 10.1.9.60 255.255.255.0 10.1.9.51  not configure(aw900T201) 
        
    when i use the redirect option 
    slot 8
        
    inbound 10.1.1.52
            10.1.9.51
    I restart the AW900 module and reset the mam with current setting 
        
    hub slot 5 10.1.1.60 255.255.255.0 10.1.1.51  active   ( aw90 v1.x)
    hub slot 8 10.1.9.60 255.255.255.0 10.1.9.51  active (aw900T201)
        
    but i can't ping mam
        
    on aw900 the ip order doesn't effect
        
    inbound 10.1.1.52   or 10.1.9.51
            10.1.9.51      10.1.1.52
    
    I change my configuration
        
    with only 
    
    hub slot 8 10.1.9.60 255.255.255.0 10.1.9.51  active
    
    and 
    
    slot 8 
    inbound 10.1.9.51 only
           
    but i can't ping mam
        
        
        Didier

T.R Title User Personal
Name Date Lines

3703.1 Duplicate addresses don't work NETCAD::MILLBRANDT answer mam Wed Jul 17 1996 12:06 26

T.R	Title	User	Personal Name	Date	Lines
3703.1	Duplicate addresses don't work	NETCAD::MILLBRANDT	answer mam	`Wed Jul 17 1996 12:06`	26
	Didier, You can't use the same address for IP Services to the MAM as you use for in-band traffic to a module. Below, you are using 10.1.9.51 in two places. show ip config hub slot 5 10.1.1.60 255.255.255.0 10.1.1.51 active ( aw90 v1.x) hub slot 8 10.1.9.60 255.255.255.0 10.1.9.51 not configure(aw900T201) when i use the redirect option slot 8 inbound 10.1.1.52 10.1.9.51 If you check the hub error log (item 5 on the setup console menu), you will find a "Duplicate Address in Slot 8" message. The "not configured" status is correct here. When you reset the aw900 and the MAM, you managed to find a timing window where the duplicate address wasn't detected. Only one of the devices will actually get the traffic, and not reliably. Dotsie

Didier,

You can't use the same address for IP Services to the MAM as you
use for in-band traffic to a module.  Below, you are using
10.1.9.51 in two places.

    show ip config
        
    hub slot 5 10.1.1.60 255.255.255.0 10.1.1.51  active   ( aw90 v1.x)
    hub slot 8 10.1.9.60 255.255.255.0 10.1.9.51  not configure(aw900T201) 
        
    when i use the redirect option 
    slot 8
        
    inbound 10.1.1.52
            10.1.9.51

If you check the hub error log (item 5 on the setup console menu),
you will find a "Duplicate Address in Slot 8" message.  The
"not configured" status is correct here.

When you reset the aw900 and the MAM, you managed to find a timing
window where the duplicate address wasn't detected.  Only one of
the devices will actually get the traffic, and not reliably.

	Dotsie