Conference netcad::hub_mgnt

Hmmm.  I can't speak for the hub, but the first thing HUBwatch does is to ask
the DECbrouter 90 how many ports it has.  (There's no other way through SNMP
to tell a 90T1 from a 90T2) - (And there's no way to tell a 90T2 from a 90T2A)

At the DECbrouter console, does it report three ports (2 WAN & 1 Ethernet)?

Otherwise, congratulations!  You've gotten an extra port at no extra cost!!!


Tom Hood

Awesome!!

er....'cept I only see one port when I look at it with my eyes, as opposed to hubwatch!

ah well...DECagent90 on the way...

Will post more info when I get that thing plugged in a fired up.

-Stephen

OK, this is really confusing me.

It says in the HUBwatch use manual that DECbrouter T1's
have their own built in SNMP agent.

So this is what I have done...I've run setup against the 
brouter, assigned an IP address against the ethernet port
that shows up as being connected to the backplane 10mb
internal segment...

I'm using a DECswitch 900ef as my 'IP services' module and
have assigned an IP address to my hub for 'in-band' management
purposes.  Everything works fine against the Hub backplane
and the switch...but the brouters don't work at all.

Aside from the DEChub seeing them as the wrong model number,
I get the following errors on HUBwatch startup:

3:29:08.63 (I) Using in-band agent (16.64.0.2 [slot 8])
13:29:11.14 (I) HUBWATCH_LIBRARY = /usr/kits/HUBwatch
13:29:11.14 (E) No agent found for module in slot 1 (mac= 08-00-2B-B6-AA-E6)
13:29:11.15 (W) TO BE ABLE TO MANAGE MODULE IN SLOT 1, 
13:29:11.16 (W) PLEASE ADD ENTRY FOR MAC 08-00-2B-B6-AA-E6 TO THE AGENT TABLE
13:29:11.17 (W) Can't verify brouter type for slot 1 - agent unknown
13:29:11.18 (E) snmp: request has no agent defined (slot= 1)
13:29:11.18 (E) Invalid request agent
13:29:11.19 (I) HUBWATCH_LIBRARY = /usr/kits/HUBwatch
13:29:11.20 (E) No agent found for module in slot 3 (mac= 08-00-2B-B6-AD-CA)
13:29:11.22 (W) TO BE ABLE TO MANAGE MODULE IN SLOT 3, 
13:29:11.23 (W) PLEASE ADD ENTRY FOR MAC 08-00-2B-B6-AD-CA TO THE AGENT TABLE
13:29:11.24 (W) Can't verify brouter type for slot 3 - agent unknown
13:29:11.24 (E) snmp: request has no agent defined (slot= 3)
13:29:11.25 (E) Invalid request agent
13:29:11.26 (I) 
13:29:11.28 (I) HUB CONFIGURATION:
13:29:11.29 (I)
___________________________________________________________________________
13:29:11.29 (I) Slots:
1..........2..........3..........4..........5..........6..........7..........8
13:29:11.30 (I) Cards: DBRUT2  Empty   DBRUT2  Empty   Empty   Empty   Empty  
DEFBA*  
13:29:11.31 (I)
___________________________________________________________________________
13:29:11.33 (I) 
13:29:11.33 (I) Power Configuration:
13:29:11.34 (I) _______________________________________________
13:29:11.35 (I) Power Slots:1       2       3       4       
13:29:11.36 (I) Supplies:         In      In      -       -       
13:29:11.37 (I) _______________________________________________
13:29:13.64 (E) snmp: request has no agent defined (slot= 1)
13:29:13.64 (E) Invalid request agent
13:29:13.65 (E) snmp: request has no agent defined (slot= 3)
13:29:13.70 (E) Invalid request agent
13:29:14.41 (I) HUBwatch for Digital UNIX, Revision V4.1.1

My hubwatch_agents files looks like this:

16.64.0.2 pbxhub "sensored" 10 3 08-00-2b-b5-5b-xx AGENT900 #
16.64.0.56 ljot1 "sensored" 10 3 00-08-2b-b6-aa-xx BROUTER #

*note: SNMP community and last two digits of phy address sensored*
*******

So uh.....any ideas?

thanks,

-Stephen

OK, I think I have everything setup properly now as far as hubwatch_agents

am now getting this error:

14:35:59.41 (I) Using in-band agent (16.64.0.2 [slot 8])
14:36:02.00 (I) HUBWATCH_LIBRARY = /usr/kits/HUBwatch
14:36:42.08 (W) BROUTER: SNMP timeout in [MODULE]TYPE group.
14:36:42.09 (W) fp: can't determine brouter type in slot 1

Is this setup related on the brouter itself?

thanks,

-Stephen (hacking my way through this)

P.S.

Here is my hubwatch_agents file:

16.64.0.2 pbxhub "sensored" 10 3 08-00-2b-b5-5b-xx AGENT900 #
16.64.0.56 ljot1 "sensored" 10 3 08-00-2b-b6-aa-xx BROUTER #
16.64.0.5 pbxswitch "sensored" 10 3 08-00-2b-b5-5b-xx BRIDGE #

    Stephen,
    
    <soapbox on>
    I'm not trying to be a smart-ass here by suggesting that you read the
    HUBwatch config & installation manual.  You'll save yourself a lot of
    time for these non-self-configuring modules.  It includes step-by-step
    instructions on how to config modules and/or HUBwatch.  And the writers
    did an excellent job!  Everything you need on one page.
    <soapbox off>
    
    What the last batch of messages is saying is that the brouter is not
    responding to snmp.  Make sure you've got the brouter's SNMP engine
    enabled.  (I'm not in the office right now and forget the brouter
    console setup commands to do this.)
    
    That should do it for you.  Once that's done, your brouter will be
    manageable.
    
    Tom Hood
    clearVISN ex-brouter guy

Did it, first thing...

What is really starting to freak me out now is why the
DEChub thinks all three of my brouters are T2's when they
are really T1's...

I better get hubloader ready to rock.

I have a feeling that you are gonna start asking me about
firmware revs.

But all this stuff is brand new?

-Stephen

    Stephen, there is also a DEWBR notes conf (KALI::DEWBR) I think,
    which may also have answers & words, for your perusal.
    
    Bob

    actually i think that if you DON't configure the brouter for IP (i.e.
    give it an IP address etc.,) even if you give it a MAC address etc.
    HUBWatch wont' deal with it (i.e. launch TELnet to it etc.)
    
    So, be sure the brouter is set-up first before you try to manage it.
    
    Regards,j