[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

3209.0. "Questions to PORTswtiches,DECservers and Rep. 90T-16" by VNAED2::SEIDLER () Mon Jan 29 1996 05:29

Hello,

I have the following questions:

1. In the "Hubwatch for Windows - Use" manual (V4) there is on page 6-38 a 
picture of a port switching module (maybe PORTswitch 900CP). There is a check 
on a MAC field. For what is that. I do'nt have a Portswitch module, i just want 
to know. 

2. is the following ok or missed i something?
If i want to manage a DECserver 900TM in a HUB900 i have to enable SNMP, IP
... as discussed in diff. topics and to set it up in the "manage table" in
HUBwatch. I will see the Server in the front panel view, but cannot call
the server picture from that. If i want to manage the server i have to go into
the "Manage Table" and select the DECserver from it - with the result of a
picture showing and empty HUB900 just with that DECserver that you can then 
select. (the same with DECserver 90M and TL). If this is ok - will it be
changed or did i something wrong?

3. To manage a DECrepeater 90T-16 you need a DECagent 90. Is the following
possible? (I don't have yet any 90T-16, so i cannot try it)

               
	           DECagent 90       90T-16
			|               |
                        |               |
                      -----------------------
                                |
                              Bridge
                                |
                      ------------------------
			|		|
                        |               |
                      90T-16          90T-16

all modules standalone. Can i manage with the Agent90 all 90_T16?

many thanks in advance

Christian
T.RTitleUserPersonal
Name
DateLines
3209.1Some answers...SLINK::HOODThey call me MISTER Dilbert.Mon Jan 29 1996 13:0416
1. Maybe some other people can give a more full explaination, but many
   of the repeaters/portswitches have a MAC (Ethernet address). Using
   that check-box, you can assign the MAC to whichever port/group you want.

2. To manage a DECserver 900TM, do the required setup using one of the
   DECserver's ports (SNMP enabled, IP address assigned, etc). That's it.
   It doesn't need to be in the agents file and you don't have to do any-
   thing else to manage it.  From that point on, just treat it like any
   other hub module.  (From the hub's front panel view in HUBwatch, double
   click on the DECserver, and you're there.)

3. I don't think that will work - you also need at least a 90TS repeater 
   in the same hub if the DECagent 90 is in a different hub.  If I'm wrong, 
   I'm sure some helpful people will correct me :-)

Tom
3209.2See notes 1131.11 and 1131.13 for more infoNETCAD::PAGLIARORich Pagliaro, Networks BU, HPNMon Jan 29 1996 13:577
>>  1. In the "Hubwatch for Windows - Use" manual (V4) there is on page
>>  6-38 a  picture of a port switching module (maybe PORTswitch 900CP).
>>  There is a check  on a MAC field. For what is that. I do'nt have a
>>  Portswitch module, i just want  to know. 
    
    
    Notes 1131.11 and 1131.13 provide some more detail on this topic.
3209.3NETCAD::BRANAMSteve, Hub Products Engineering, LKG2-2, DTN 226-6043Thu Feb 01 1996 15:428
The 90T-16 is a "dumb" repeater, with no in-band management capability. The only
way to manage it is to put it on the same management bus as a DECagent 90, 90TS,
or 90FS (or in a DEChub900), which are all capable of acting as management
agents for it. By management bus, I mean the async management bus built into a
DEChub90 or DEChub900, or the async management bus in a MultiStack; this is
*not* the LAN wire. Which is all the long-winded way to say it has to be in the
same hub or stack as its management agent, it is not manageable over the LAN as
you have illustrated.
3209.4ThanksVNAED2::SEIDLERWed Feb 07 1996 07:491
    Many thnaks, it's clear now