[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

2540.0. "Cannot manage 90TL in a HUB900 after restarting Hubwatch" by GIDDAY::LEUNG (Dennis Leung, Sydney CSC) Tue Jul 18 1995 23:59

Hubwatch V4.0.1
ds90tl V1.1 BL44-10

Hub900
Slots	1	ds90tl
	2	packetprobe
	3	decagent90
	4	conc. 900mx
	5	repeater 900gm
	6	nil
	7	bridge 900mx
	8	repeater 900tm

Steps done to manage ds90tl:
1) Community -> Manage Table -> Add an agent for the ds90tl in slot 1
2) Click on slot 1 -> Configuration -> Add
		Slot	1
		Type	DecServer90Tl
		Disable Status Polling
		Enter Mac Address of ds90tl
		Enter IP address of ds90tl
		Enter community of public for ds90tl
3) ds90tl appears in slot 1 and I can double-click on it.
4) I exit from Hubwatch, then restart Hubwatch
5) When I double-click on ds90tl, I get No Agent specified for the slot Mac  	
   Address.

If I go under Community -> Manage Table, I can choose the ds90tl agent and I can
double-click on the standalone module.
I have checked that the ds90tl has snmp enabled.

If I delete the ds90tl from slot 1 and re-add it, I can double-click on it again
until I exit from Hubwatch.

I am out of ideas of what is wrong here and would appreciate any help.

Thanks
Dennis
T.RTitleUserPersonal
Name		DateLines
2540.1SNMP/CommunityNames on DS90TL ??ZTOIS1::VISTARenato VISTA/MCS/NS France/ZTOThu Jul 20 1995 10:2111
    
    Hi Dennis,
    
    I've met such problem with previous versions of HUB900/MS + DS700 +
    HUBwatch/VMS... It was due to multiple snmp/communityNames on the
    DS700... Maybe you have to reset snmp communityNames, and only allow
    the "public any dis dis" access rights, simply to test...
    
    Renato
2540.2works in Hub90 but not in Hub900GIDDAY::LEUNGDennis Leung, Sydney CSCThu Jul 20 1995 22:4527
Re : .1

Hi Renato,

Thanks for the reply. But it did not make any difference. I reset the 90tl to
factory defaults and re-start from the beginning but I still get the same
problem.

I have done further testings as follows :

If I move the same ds90tl from the Hub900 to a Hub90 with a DECagent90, it works
fine, i.e, I can double-click on the ds90tl even after exiting and restarting
HubWatch.

Other observations when ds90tl is in a Hub900 :

Even before adding agent for the ds90tl or add the module using 
Configuration -> Add, when I start HubWatch and choose the Hub900, it displays
that the ds90tl is in slot 1. (seems like it has auto-discovered that the ds90tl
is in that slot). I have to manually delete (using Configuration -> Delete) that
a ds90tl is in that slot. Then add an Agent for the ds90tl and then re-add the
ds90tl in that slot.

Anyone has seen this before?

Thanks
Dennis
2540.3nonFatalFailure Control Status ??ZTOIS1::VISTARenato VISTA/MCS/NS France/ZTOFri Jul 21 1995 06:0114
    
    Dennis,
    
    I cannot test locally with a DS90TL within a DEChub900... But, a next
    check might be to have a look at the green control window on the front
    of the DEChub900, and to see whether the Slot where the DS90TL is
    installed is correctly described by the HUB/MS Manager, and that the
    DS90TL status is UP (... and not nonFatalFailure ...).
    
    If it is the case, you maybe have a firmware compatibility version
    problem between the HUB/MS & the DS90TL downline-loaded software...
    
    Renato
2540.4probleme connuPRSSOS::PEYRACHEJean-Yves Peyrache Country Support Group FranceFri Jul 21 1995 08:137

 Could you provide the Version of decserver90TL, i think it's old bug with
 older version of 90TL. see notes 212,331,283,1310...


  JYP
2540.5same problem in Hub900 with latest version of ds90tl V1.1A BL45-11IAMOSI::LEUNGDennis Leung, Sydney CSCSun Jul 23 1995 20:5214
Re:.3
	After the ds90tl has passed self-test, the Hub900 LCD panel displays
that a Decserver90TL is in slot 1 and status is UP. After the MNENG1 image is
loaded, the status changes to UNKNOWN.

Re:.4
	DS90TL V1.1 BL44-10
	I have upgraded the DS90TL to V1.1A BL45-11 but problem still exists.


Any other ideas?

Thanks
Dennis
2540.6I have the same problem... Hubwatch is 4.02ROM01::GALLANAFrancesco GallanaMon Aug 28 1995 09:313
Has somebody seen the same problem?

Francesco
2540.7Sorry, Hub Manager is V4.02, Hubwatch is V3.1ROM01::GALLANAFrancesco GallanaMon Aug 28 1995 09:430