Conference netcad::hub_mgnt

Should be missed in Agent files ??

 try to add it


 jean-yves

    Phil,
    
    You need to make sure that you have the terminal server added in the
    AGENT file table.  You can muck with it in the office also, as there is
    a 90M and 900 in the demo room.
    
    ttfn,
    j
    

    Re: .1, .2-
    
    	 Perhaps I'm missing something, so let me explain the flow again:
    
    	1) Start HUBwatch from Program Manager
    
    	2) Enter the agent's name at the "Specify Agent" prompt. (This is
    the DEChub 900 (manager Slot 7) containing the DS90M in Slot 6.)
    
    	3) Physical DEChub 900 view is displayed, (including DECserver 90M in
    Slot 6).
    
    	4) Selecting the DS90M (by double click) produces a message box 
    stating: "No agent specified for slot MAC address- please check logging 
    messages in the HUBwatch startup window". (Selecting any other module
    works just fine, BTW.)
    
    	5) Using Configure tool bar, perform a Delete and then an Add of
    the DS90M in Slot 6.
    
    	6) DS90M can now be selected from the physical map. Other modules
    can still be selected. Returning to the DS90M continues to work. (Normal
    behavior IMO.)
    
    	7) Now, the problem: If another Community is selected from the Manage
    Table/Manage Current toolbar, subsequently returning to the Community 
    containing the DS90M, the scenario repeats at step 3) above. If HUBwatch 
    is restarted, the scenario repeats at step 1) above.
    
    	Also, the LAN interconnect display shows a black box at the
    junction of the DS90M with the Thinwire segment rather than a number
    within the box. Is this expected or significant?
    
    	Am I missing a detail here or what?
    
    Thanks,
    
    Phil

OK, I'll repeat what both Jean-Yves (.1) and JD (.2) said...

	PUT AN ENTRY FOR THE 90M IN YOUR AGENTS FILE.

"But Tom, I did that when I added the module."
"No, fraid not."
"Huh?"
"Let me explain...  From the HUBwatch front panel window, put your cursor
 over the "Community" menu at the top of the window.  Press the left mouse
 button.  Slide the pointer to "Manage Table".  Release the left mouse 
 button.  Press the "Add" button, about 1/2 way down the screen on the 
 right size.  Enter an IP Address, name, and MAC address for the DS90M.
 Optionally, select "Terminal Server" as the agent type.  Optionally,
 enter some descriptive description to the "Comments" field.  When you
 are happy with everything, press the OK button at the bottom.  You are
 now back at the Community table window.  If this ADD did not work, you do
 not have the logical name HUBWATCH$LIBRARY (OpenVMS) or the environment
 variable HUBWATCH_LIBRARY (Unix or Windows) defined."
"Oh, I see. Thank you."
"You're welcome."
"But why does this work when I first add the module, but not later?"
"Because when you use Add Module, HUBwatch learns how to talk with the
 device, because you are entering the addresses directly.  Later, HUBwatch
 has the MAC address of the server, but must use the Agents File to translate
 the MAC and get the agent IP address."
"Really?"
"Yup."
"Bye"
"Bye"

    Re: .4-
    
	>PUT AN ENTRY FOR THE 90M IN YOUR AGENTS FILE.

    	OK, I can take a hint :-)....
    	
    	Now I have another agent selection in the Community table and all
    is well. The DS90M can be selected as its own Community and also by 
    selecting it from the DEChub 900 physical view.
    
    "So Tom, thanks very much for restating what I could not grasp."
    "No problem, why was it so confusing?"
    "Well, I did not have to add DECserver 900s in this manner. They
    automagically displayed when double-clicked from the Physical View
    DEChub display. I initially added the DEChub as an agent, but
    subsequently installed DS900s could be selected and managed straight
    away." 
    "Yeah, well the DS90M has a built in agent, but only has Thinwire
    connectivity as it is a 90 series module. It also has a Left Hitchcock
    management bus."
    "Yes Tom, I know that, but I guess I'm missing the difference in DEChub 
    900's function in managing the DS90M vs. a DS900...please explain so
    that I might not produce ignorant questions henceforth."
    "OK, now I understand your confusion- let me explain..."
    
    To be continued (hopefully) ;-).
    
    Phil

"Well, Phil, I'd be glad to explain."
"Good.  I knew you would"
"The explaination is that a DECserver 90M is not a DECserver 900TM"
"Tom, you're making fun of me, aren't you?"
"No.  Really.  If I could explain (and prevent) differences like this,
   I'd be a happier HUBwatch programmer."
"Oh.  That was kind of a disappointing explaination, Tom"
"Sorry, Phil.  Some stuff is not intuitive because we try to be backwards
   compatable.  Older devices have the weight of history behind them, so that
   leaves us to do workarounds.  Some devices don't come from the DEChub group
   directly, and, although those groups try to do the right thing, sometimes
   things don't end up as integrated as we'd like.  With any luck, all new
   devices that plug into the hubs just plug-n-play in HUBwatch without user
   intervention, just as the 900TM does."
"Yeah, I guess so, Tom, but how do *you* remember these rules?"
"Phil, let me tell you.  Most mornings I don't even remember my password.  
   For most of this stuff, I try it, and if it works, I don't give it a second
   thought.  If it doesn't work, I stand up and yell, 'Does anyone remember 
   what you have to do to make a DECthing 90X work in a 900 hub?'  Sometimes
   other people remember.  Most of the time, I end up first trying different
   things, then when that fails, I look in the doucmentation."
"That was another slap, wasn't it, Tom?"
"No.  I don't look at the documentation until last, just like most
   everyone else.  But I do get a special joy from typing things like 'read
   the release notes'  and 'it is on page nn in the Use Manual'.  It makes
   me feel like I know what I'm doing.  In short, do as I say, not as I do."
"Gotcha.  Later, dude"

Tom, you keep this up and you'll end up talking to yourself.

    Tom's just got cabin fever. He's waiting for the ice to melt
    on his favorite rapids so he do the kayaking thaing....
    Anybody got a pc with some multi-media so we can pipe some
    sounds of waterfalls, and rapids into his office? :-)
    
    Bob :-)

    "Phil you ignorant.....(grin)"
    "What, Jon? I called you the other day and you didn't answer..."
    "Of course, Phil, you called my HOME number and left a message there,
       if you'd called work I would have been paged and answered, so
       I didn't get your phone message until late Thursday and won't be
       home from business until Sunday morning.  I'm home 2 days this week,
       out all the rest...aarugh."
    "Oh, I see, silly me."
    "Right, Phil, now about that agent addition, what box did you click..?"
    "I clicked the ADD box at the far LEFT."
    "I see, that confused me too, Phil."
    "It did?"
    "Yes, actually even if you had read the manual for addition of a
        terminal server it would NOT have helped you.  You see, the
        current manual is wrong."
    "Jon, I didn't read the manual..."
    "I know, but it didn't matter anyway..."
    "But I got it to work with some help from the NOTES file...."
    "Ah, so did I, but that was a few weeks back and I died at the Post
        Gazette where I couldn't get the servers to work there...., I hope
        that you weren't caught at the customer with the book and dying?"
    "(mumble)"
    "S'ok, Phil, I called Bill Seaver and the fellow (damnifiremember) who
        did the manual - we walked through it and, hopefully, in the next
        edition the terminal server addition page will be right, or at
        least nearer to reality..."
    "Well, one day, Jon, maybe I'll actually get a real manual anyway..."
    "Anyway, I'm in Findlay Ohio on MOnday (aarugh) it was supposed to be
         vacation, but will be back in the office around Thursday...
         maybe we can play with the hub in the demo room.  The one up
         there has a 900tm and 90m...ok?"
    "Jon, I'm never in the office either..."
    "I know, what's the office?  My floor is moving in two weeks..."
    "Will you get a cube bigger than the standard 6 x 6 one?"
    "That' unlikely, Phil, mine will probably continue to look like the
        combo of IKEA and DEC-standard junk...as long as it has a network
        port and a snow-shovel to dig my way in/out I don't care..."
    "Ok, will see you next week, maybe..."
    "G'Nite, Phil"
    "G'Nite, Jon".

    Ok, What about a ds900tm that all of a sudden gives the same error
    stated in .0 when I try to click on it.  I could of sworn that this
    worked prior to a power failur that the customer had and lost all of
    their ds900tm settings BTW!  I sure did have fun explaining that to the
    customer.  Anyway, I do digress.  How can I get communications back to
    the ds900tms?  They have snmp on, ip address/mask are setup as well as
    internet gateway, not that it is needed here.
    
    thanks
    -jon