T.R | Title | User | Personal Name | Date | Lines |
---|
3119.1 | Need more information | NETRIX::"[email protected]" | steven Freke | Thu Jan 04 1996 11:05 | 13 |
| Anthony
I need a few more details. What version of code is the switch running?
what version of hubwatch are you using, and what version are you running
on the hub. Is this after power up, or just in regular use.
I guess that they have a module in the hub, that offers IP services, what
module is this. Can you click on any other modules in the hub or is this
hub wide.
Steven Freke
LAN Team
UK CSC, Basingstoke
[Posted by WWW Notes gateway]
|
3119.2 | DECswitch 900 | HGOVC::ANTHONYCHIU | | Fri Jan 12 1996 03:51 | 26 |
| Steven,
Thanks for your response first. Today I got more details from the
customer :
1) The version of F/W has been upgraded to DECbrouter 900
2) The version of HUBwatch is 3.1
3) The switch is a standalone module
4) The error message happened after power-up
5) The switch itself has been configured with IP address
The error message is "Agent type not correct"
Therefore, the question is does this version of HUBwatch supports
DECbrouter 900 firmware ?
If not, what version would be the suitable one ?
Thanks
Anthony
|
3119.3 | Not supported in verion 3.1 | SLINK::HOOD | My God, what have I done to my spleen? | Fri Jan 12 1996 11:34 | 14 |
| You need at least HUBwatch 4.0, and possibly 4.1.
The release notes for each version of HUBwatch lists the devices that version
supports. None of the routing DECswitches are supported before 4.0.
You should know that when you're running the routing code in a DECswitch,
here's what HUBwatch provides for that module:
- Front panel bezel
- TELNET connection window.
You will lose the bridging management.
HUBwatch 5.0 will include some basic router management, but you'll want the
separately sold) clearVISN router manager application to really handle
routers.
|