[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

2672.0. "DECrepeater 90TS management question again ??" by GIDDAY::STANISLAUS () Thu Aug 24 1995 04:27

	
	I have read several notes in thi sconference about DR90TS management
and sometimes feel everything is  as clear as a crystal and sometimes 
everything is as clear as mud. So I am making statements and I request someone
to say yes or no and if possible add comments:

	I will be talking about DR90TS in DH90 only not DH900, because I
understand the DH900MS management strategy.

	1)Customer says he was told by Digital a while ago that a DH90 should
not have DR90T and DR90TS in the same 8 slot or 16 slot hub. He says he was
told by Digital that it would confuse the hell out for management. I said wrong.
The DR90TS units if given their own IP addrss will be managed by SNMP. The DR90T
units all need one DB90 or DA90 in that 8 slot or 16 slot hub. If it is a DB90,
then somewhere on the network there should be a DA90 able to talk to the DB90 in
the 8 slot or 16 slot DH90 holding the DR90T units. I also said that the DA90
or DB90 can via LH protocol autodiscover the DR90TS in the DH90 via the
Management Bus, but that the actual management of the DR90TS is via SNMP from
the NMS.

	2)If you don't mind the loss of some functionality such as performance
and security, each DR90TS need not be given an IP address. Just give one IP
address to one DR90TS in a 8 slot or 16 slot DH90. That DR90TS will act as a 
proxy SNMP agent and talk to other DR90TS in that 8 or 16 slot hub. I want to
say to the customer that this statement is true but I said that I will check
first and hence this note.

	3)A DR90TS acting as a SNMP agent in a 8 slot or 16 slot hub cannot
manage DR90T and DR90C units in that 8 or 16 slot hub as of today. This feature
may or may not be available in future, thereby making it needles to have a 
DA90 or DB90 to DR90T and DR90C if the feature ever becomes available.

	Can someone clarify the above, especially why the customer thinks he
should not put DR90T and DR90TS in the same 8 slot or 16 slot DH90.

Alphonse
T.RTitleUserPersonal
Name		DateLines
2672.1Some AnswersNETCAD::DRAGONThu Aug 24 1995 08:5843
    
    Alphonse,
    
    >1) Customer says he was told by Digital a while ago that a DH90 should
    >not have DR90T and DR90TS in the same 8 slot or 16 slot hub. He says he
    >was told by Digital that it would confuse the hell out for management.
    >I said wrong. The DR90TS units if given their own IP addrss will be
    >managed by SNMP. The DR90T units all need one DB90 or DA90 in that 8
    >slot or 16 slot hub. If it is a DB90, then somewhere on the network
    >there should be a DA90 able to talk to the DB90 in the 8 slot or 16
    >slot DH90 holding the DR90T units. I also said that the DA90 or DB90
    >can via LH protocol autodiscover the DR90TS in the DH90 via the
    >Management Bus, but that the actual management of the DR90TS is via
    >SNMP from the NMS.
    
    Your statements sound correct. I've never heard of a limitation on mixing
    DECrepeater 90T and 90TS in a DEChub 90.
    
    
    >2) If you don't mind the loss of some functionality such as performance
    >and security, each DR90TS need not be given an IP address. Just give
    >one IP address to one DR90TS in a 8 slot or 16 slot DH90. That DR90TS
    >will act as a proxy SNMP agent and talk to other DR90TS in that 8 or 16
    >slot hub. I want to say to the customer that this statement is true but
    >I said that I will check first and hence this note.
    
    This is correct. In the upcoming release, when DECrepeater 90TS/FS modules 
    are managed via a DECrepeater 90TS/FS proxy agent, they do not have the
    same level of MIB support as when managed standalone, however no IP
    address is needed for the modules (except of course the hub master).
    
    >3) A DR90TS acting as a SNMP agent in a 8 slot or 16 slot hub cannot
    >manage DR90T and DR90C units in that 8 or 16 slot hub as of today. This
    >feature may or may not be available in future, thereby making it
    >needles to have a DA90 or DB90 to DR90T and DR90C if the feature ever
    >becomes available.
    
    In the upcoming release DR90TS will be able to manage any 90 repeater
    in a DEChub 90.
    
    Hope that this helps,
    Bob
2672.2Can new DR90TS firmware handle DR90T if there is a DB90 in the same HUB?ROM01::GALLANAFrancesco GallanaFri Oct 06 1995 08:1622
Bob, 
As you stated in the previous reply, 

> In the upcoming release DR90TS will be able to manage any 90 repeater
> in a DEChub 90.

but, in the point 1) there is a statement that says:

> The DR90T units all need one DB90 or DA90 in that 8 slot or 16 slot hub.

My question is:

What happens if, with the new microcode, there will be a DB90, a DR90T and a
DR90TS in the same HUB?

who will manage the DR90T?

There will be any conflict?

Thank you in advance

Francesco
2672.3NETCAD::DRAGONMon Oct 09 1995 08:2212
    
    Francesco,
    
    > What happens if, with the new microcode, there will be a DB90, DR90T and a
    > DR90TS in the same HUB?
    
    > who will manage the DR90T?
    
    The DR90TS will manage the DR90T.
    
    Regards,
    Bob