[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

125.0. "DECagent 90 and OBM missing..." by CGOS01::DMARLOWE (dsk dsk dsk (tsk tsk tsk)) Wed Jan 13 1993 11:41

I have a DECagent 90 (V1.0) in hub and a DECbridge 90 (V3.0).

I have been working with the OBM port only.  I think the OBM is a 
great start.  Unfortunately from the main menu you cannot enable or 
disable repeater ports.  It is a pain to have to use the CONNECT to 
MOP address option.

Ok, so I do the connect and do a SET PORT 1,2,1 DISABLE.  I then ^D 
and go back to the main menu.  I do a SHOW COMMUNITY or a SHOW MODULE 
but the disabled repeater ports to not show up as disabled.  In the 
SHOW MODULE they show as all enabled.  Even if I wait for hours and 
then do a SHOW MODULE, same thing.

I know DECagent V1.1 will be in field test soon, will this cure the 
problem of:

1. enabling and disabling repeater ports without using CONNECT to a 
DB90, ie. OBM port?

2. via the menu, correctly displaying the correct status of the 
repeater ports?

The pseudo VT graphics are great on the DECagent are great, now we 
have to fill the holes.

dave
    
PS.  cross posted in ETHERNET notes.

T.R	Title	User	Personal Name	Date	Lines
125.1	What the DENMA does in OBM	EMDS::SEAVER	LENAC Net Mgnt Mktg 223-4573	`Sun Jan 17 1993 20:50`	18
	The V1.0 DENMA code does indeed show repeater port status on both the Show Community and Show Module screens. However, in the scenario described by Mr. Marlowe, he went around the agent by MOPing into the bridge and changing the ADMIN status of a port. In this case, the agent is not notified that the ADMIN status of the repeater port has been changed, and this information is not obtainable over the backplane bus. We can only get OPER status (the actual operational status of the port). It is the combined ADMIN and OPER status that is displayed by the DENMA, which should reflect the actual state of the LED as seen on the repeater. By not using SNMP to enable/disable the port, there's no way for the DENMA to know of the port ADMIN status change, so the screen does not change. At this point, I'm not sure what the repeater port management scheme from the DENMA console will look like. We will be doing direct backplane management (i.e. you won't need a bridge to do auto-discovery or get repeater port status) but there hasn't been much time to polish up the user interface for the repeater port manegement scheme.
125.2	I stand corrected	KALI::GAUDET		`Mon Jan 18 1993 17:57`	6
	I boo-boo'ed ... the backplane responses do indeed report the port status with enough detail to determine the state of the LED. We've fixed a problem in the agent code which will be avaiable in V1.1 that will handle the display of repeater port status in a much cleaner way. ...Roger...
125.3	Maybe V1.1 has the missing pieces.	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Tue Jan 19 1993 12:34`	4
	Now all we need is the ability to ENABLE/DISABLE repeater ports from the OBM main menu. dave
125.4	I thought repater OMB mgnt was coming	EMDS::SEAVER	LENAC Net Mgnt Mktg 223-4573	`Thu Jan 21 1993 14:07`	2
	Dave- my impression was Roger had siad he was looking at that and may yet have it (not yet promised for 1.1, but might. Do you agree?
125.5	patiently waiting 8^)	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Fri Jan 22 1993 23:56`	11
	Bill, I agree about Roger's comments and V1.1. Hopefully repeater port management from the OBM port will get into V1.1. If not then I hope V1.2 comes out as fast as possible. When you finally get a piece of hardware to play with, you actually have a chance to try things before a customer gets to you and says, "Did you know that you can't .... ?". dave