| To manage a DECserver 90TL (1Meg) in a 900 hub, do the following:
Connect a terminal to the 90TL, and:
(1) Assign an IP address to the 90TL
(2) Enable SNMP state on the 90TL.
(3) Enable community PUBLIC to SNMP SET and GETNEXT on the 90TL
(4) Re-start the 90TL (Local> INIT DELAY 0).
Run HUBwatch, and:
(5) "Community->Manage Table" window: Add an entry to the agents file
for the 90TL. Include the MAC, IP, and community.
(6) "Configure->Add Module" window: Add the 90TL to the hub, with slot
polling disabled.
(7) You might need to exit and re-start HUBwatch after this.
Now, you've got a 900 hub with a DECserver 90TL which is manageable.
If you've got a DECserver running Network Access Software, you only need
to do steps 1-4.
(This info is also in the HUBwatch Installation & Configuration manual.)
Tom Hood
former TL guy.
|
|
Tom,
Thank you for your procedure. Everything is correct up to point 5,
but point 6 is not accepted by DEChub 900 because ADD Module in HUB 900
is illegal operation.
I need refresh DEChub to see TL but not manageble. Next steps are:
- Configure->Delete Module
- Configure->Add Module
- set IP,MAC and Community
After that I really have manageble TL module. Exiting and restarting
HUBwatch I get not manageble again. In View->Massage Box I read
NO AGENT FOUND IN SLOT=6, NO MAC ADDRESS
and I have the same situation again.
Have you any idea?
Krzysztof
|
|
Hello all and specially Tom,
There are so many Entrys about the Mgnt of the 90TL in the Hub900:
the Entrys: 171/209/293/331/1310/2540/3079/3348
Most of them have the Problem, that it is n o t possible to klick
the 90TL in the Hub900. The Message is always:"No Agent Specified...."
But: the Module is o n l y managable via the Community Table in the
Hub900!
It is exactly as Notes 3348.2 says: After Add in the Agent File, and
Configure->Add Module, it works as long, untill i do a Exit and Restart
of Hubwatch again, now you can n o t manage it any more out of the Hub.
(via Community Table is always ok)
So please, is there anybody out, who can c o n f i r m that these
really works? (should, or Could, or really does......?
Situation: (I really set it up exactly as Tom said in Note 3348.1)
----------
Customer Situation reproduced in our Test HUB:
-Hubwatch 4.1.2
-DEChub900 MAM 4.1.1
-Slot 3 90TL V1.1A BL45-11
I really hope, that somebody can Help about these, to clarify the
Situation.
Thanks a lot,
Daniel MCS Switzerland
|
|
<some time its magic...>
Hello Tom,
Thanks for Your fast Response. Now the DS90TL works.
My Customer will be happy.
But the Problem was not a missing Entry in any Table,
(as i told You, the Module was always managable as
a standalone Module out of the Community Table),
I really did the 2-Step approach bevore i made
these Entry. Configure-> Add Module and the Entry in
the Community Table.
But now i had to do the magic approach:
"Reset the MAM with Current Settings !
But now, the Story is not at the End, it goes on:
!-> I tried now the DS90M with NAS 1.5 BL95-32 loaded,
but these Module is really (i mean really!) only
standalone managable. No Click out of the Hub display!
I tried also with add Module, but these should really
not be necessary, a DECserver with NAS SW loaded is
autodiscovered by the Hub900. No magic approach helps,
its just not possible to manage.. (Click in the Hub)
For the same Problem i made long Time ago the Entry 2940.0
in these Conference, but there was just "silence in the
Forest" out there... (as we call it here)
May any Comment to these?
Thanks,
Daniel MCS Switzerland
|
|
<Thanks for all the Comments to these Problems and all
the Answers i dident get ....>
I am sure, that everybody who wants to manage a 90M/90TL
runs in to the same Problems, because all the Entrys
171/209/293/331/1310/2540/3079/3348 and all the no-made Entrys..!
Strange behaviour for 90TL/90M in Hub900
----------------------------------------
I tested now seriously the Problematic:
Situation: DS90TL V1.1A BL45-11
----------
-When first inserted a DS90TL in to a DEChub900, then
to a "delete Module" in that Slot and a "add Module" from one
of the Mgnt PCs. (polling disable)
These creates an Entry on the MAM Module for the 90TL.
(i tested it, these has to be done only one Time, from one
PC, after these Entry on the MAM, it will discovered by any
other PC!
-Second create the Entry in the Community Table for the 90TL,
Community Public.
-Now you can click the Module out of the Hub Display, and it
is manageable fine.
-Now there are several Conditions, how to get the following
Error: "No Agent specified for Slot Mac Address"
1) after the Configuration above, it is managable fine.
Now, go in to Community Table do a "make Current" of the
DS90TL and you get the standalone Module, MGNT works ok.
But when you change back the Community to the whole Hub,
click the DS90TL Module, you will get the above Error.....
2)after the configuration like above it is managable fine.
Exit now Hubwatch, start up Hubwatch again, try now to
click the DS90TL out of the Hub, now you will get the
above Error....
3)If you change now the Community to some other then Public,
you will get the above Error...
Solution
--------
-after the configuration like above it is managable fine.
-Now there are two Steps to do, that it works also for
the 3 Conditions i described above.
First: -Reset of the MAM with current Settings
Second: -Reboot your Managemennt PC
Now it works! now you can start and shutdown Hubwatch or
whatever it works as long, as you dont change anything on
the Config.
Just for Clarification: Only reboot of the PC does not work!
Only Reboot of Hubwatch does not work!
Only Reset of the MAM without reboot
of the PC does not work!
Really: if you dont do these two Steps in the right Order,
you get always the above error during the Configuration.
Just some words for the 90M (only Community Public works in Hub)
---------------------------
-If you put it in as a new Module in to the Hub, it will
be autodiscovered and displayed as 90M.
-Entry in Community Table, Community Public, these works.
Sometimes, its really not clear why, you get also the same
Error as above...
-In these Case, you have to do the 2 Steps:
First: -Reset of the MAM with current Settings
Second: -Reboot your Managemennt PC
Note:
-----
-It works o n l y with Community Public out of the Hub.
-you can use another Community then Public o n l y as
standalone Module.
-I was not able to get it working with another Community
then Public. I tried all the Steps above, but no Chance.
These must be a bug, and as soon as i get again a Customer
Call about these Problem, i will open up a IPMT and than
these Problem m u s t be fixed.
Some Words to the DECSErver 900TM: (always NAS SW loaded)
----------------------------------
-These Module will be autodisovered by the MAM Module.
-It is managable w i t h o u t any Entry in the
Community Table. And these works also with another Community
than Public!
-Just the Module needs the Ip Address on it and SNMP hase to
be enabled, plus SNMP set enabled, thats all.
(the Dokumentation and a Stars Entry says, that it has to
be configured in the Community Table, but these is just
not neccessary!
-another Bug?.....or may a very usefull unknown feature?
***********************************************************
These is now the Result of my serious testing of the whole
DECserver 90TL/90M/900TM Stuff. I hope that these Entry
help some persons out in the Field, that always have the
same Problems with managing DECservers out in the Field.
********************************************************
I hope that someone from Engineering gives some Comments
to these, but please not just any Advices, may
someone t r i e s and sees all the Problems they can
happen, but are nowhere documented. (it needs not so much
Time to reproduce ist) more to get out of it....
Thanks and Regards,
Daniel MCS Switzerland
|