[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

1195.0. "ChasPortSubTypeSelect ?" by PRSSOS::GROSSETETE () Thu Jul 07 1994 05:49

        Hi,

        Even if I am already convinced that Hubwatch is a MUST
    when you configure different LAN's on a DEChub 900, I tried
    to understand SNMP SET commands which are sent to a DEChub 900
    (This may be useful to restore a lost config. using an SNMP
    station).
    I used a LAN analyzer to trace the frames sent and received between
    Hubwatch and our DEChub 900.


        On our DEChub 900, I created an Ethernet LAN. This is done
    by sending two SNMP SET commands which contain the "segment
    number" I created with name, type and "created request" arguments
    for the first one, then "valid" for the second.


        Then, I assigned a DECrepeater 900TM located in slot 4
    to this Ethernet segment. Three SNMP SET commands were sent
    but I have difficulties to understand the first one, could
    somebody comment ?

    SNMP SET Request ->
	1.3.6.1.4.1.36.2.18.11		DEChub 900 MIB
	1.1.1				Chassis MIB
	4.1.1.5.3			ChasPortSubTypeSelect
		Integer 5 ??

	If I assigned an other DECrepeater 900TM located in
	slot 5, I got an integer value of 7

	Regards
	Patrick

T.R	Title	User	Personal Name	Date	Lines
1195.1	I don't parse it that way.	NACAD::GALLAGHER		`Thu Jul 07 1994 09:29`	24
	Patrick, You are either very dedicated, very curious, or have far too much time on your hands ;-) There are a couple things I don't understand about your note. > 1.3.6.1.4.1.36.2.18.11 DEChub 900 MIB > 1.1.1 Chassis MIB > 4.1.1.5.3 ChasPortSubTypeSelect > Integer 5 ?? chasPortSubtypeSelect's OID is 1.3.6.1.4.1.36.2.18.11.1.1.1.6.2.1.5.n, not the OID you list. The OID you list (1.3.6.1.4.1.36.2.18.11.1.1.1.4.1.1.5.3) is the 3rd instance of chasSegmentEntryStatus. chasSegmentEntryStatus can't be set to 5. I'm very confused. If you've captured the packet, feel free to send it to me off-line and I'll see if I can decode it. -Shawn
1195.2	More on decoding packets	SLINK::HOOD	I'd rather be at the Kennebec	`Thu Jul 07 1994 10:50`	9
	If you have HUBwatch for OpenVMS or ULTRIX (any rev), you can get it to print an SNMP trace of all the SETs and GETs that HUBwatch does. This hidden / undocumented / unsupported feature will also be available with HUBwatch for Windows V3.1. It displays both the MIB variable names and the values. If you have questions about it, send me mail. Tom Hood HUBwatch
1195.3	Request from customer	PRSSOS::GROSSETETE		`Thu Jul 07 1994 10:50`	25
	Shaw, I have no extra time, but I try to answer a question from France Telecom (french operator) who is offering a public FDDI services which (I expect) may be based on our DECconcentrator 900 DEChub 900. As they are already using H.P. OpenView as Network Management station, they asked us to provide informations on how to manage a DEChub 900 without using Hubwatch from their Network Operation Center. I can't tell them it waste time since I was not even able to demonstrate them Hubwatch on Windows v.3.1 to correctly manage our DEChub 900 with FDDI modules. To get some ideas, I traced an ethernet lan creation and a DECrepeater 900 TM channel assigment using a WG DA30 analyzer which decoded SNMP for me. I will repeat it and send you the trace by mail. Best regards Patrick
1195.4		LEVERS::SLAWRENCE		`Mon Jul 11 1994 10:37`	8
	A word of warning - as you might expect, creating an Ethernet LAN on the backplane is _much_ simpler than creating and FDDI LAN (just ask the HUBwatch developers :-). If you pick up a copy of the Chassis MIB (available in file://ftp.digital.com/pub/DEC/hub900/mibs/) there is quite a lot of explanation in the comments (which your browser doesn't display).