| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3158.1 | Not V3.1 | NETCAD::FORINO | | Mon Jan 15 1996 12:11 | 4 |
| No - the V3.1 HUBwatch has no knowledge of the 900EE/EF running
routing code.
John
|
| 3158.2 | | CHR27::YEUNG | im2bz2p,ru? | Tue Jan 16 1996 15:14 | 11 |
| re .1:
> No - the V3.1 HUBwatch has no knowledge of the 900EE/EF running
> routing code.
The customer is an all VAX/VMS site. Does this mean they have to get
an Alpha/UNIX machine to run HUBwatch V4.x? Is the VAX/VMS HUBwatch
license transferable to DEC UNIX?
Thanks
Tim
|
| 3158.3 | You really need V5. | SLINK::HOOD | My God, what have I done to my spleen? | Tue Jan 16 1996 16:43 | 9 |
| A clarification...
You, in fact, need V5 of HUBwatch to manage switches running routing
code. Version 4 of HUBwatch will show the front panel bezel, and when
double-clicked, bring up a TELNET window to the router. Once you're
running the routing code, V4 HUBwatch no longer does the bridging
management.
Tom Hood
|
| 3158.4 | routing code on 900ee problem | VIVIAN::M_PATTEN | The truth is out there | Thu Feb 29 1996 03:39 | 32 |
|
I am currently trying to install a DECswitch900EE with the routing code
installed into a dechub900.
For some reason it is not allowing me to divert the switch ports onto
the backplane.
Under hubwatch, no handles are shown under the DECswitch in the lan
connect view and in the telnet accessed configuration menus, no option
is shown to do this.
I have read the manuals and I know what options should be shown and
where they are accessed from. These do not appear.
It appears that the DECswitch is not recognising that it is in a hub,
or that the routing code doesn't think that the DECswitch is capable of
having its ports redirected.
any ideas ??
This is urgent btw I need to get this guy running by firday (yes I know
its thursday)
Thanks in advance
Martin patten
|
| 3158.5 | | NETCAD::DOODY | Michael Doody | Thu Feb 29 1996 09:45 | 10 |
| 1) use the latest hubwatch. v4.1.1. or whatever. There is no getting
around this.
2) In the lan interconnect view, click exactly _once_ on the 900EE
icon. Then click the config button.
3) choose the "port out back" types for the ports you want directed to
the backplane.
md
|
| 3158.6 | could try HW for Win 4.1.2 | SNOFS1::KHOOJEANNIE | Humpty Dumpty was pushed | Thu Feb 29 1996 17:40 | 8 |
| Martin,
What about using HUBwatch for Windows v4.1.2, which has the fix for
the DECswitch 900EE/EF (Router) LAN interconnect?
It's documented in Notes 2990 and 2878.
Jeannie
|
| 3158.7 | V4.1.2 required for routeabout 900ee and EF | VIVIAN::M_PATTEN | The truth is out there | Fri Mar 01 1996 03:08 | 15 |
| Gents.
The manual supplied specifies HW V4.1 this is WRONG !!!!
V4.1.1 will not allow you to click the config button for this module,
it retuirns an error.
V4.1.2 fixes this problem
Thanks
Martin
|
| 3158.8 | | CSC32::B_GOODWIN | MCI Mission Critical Support Team | Fri Mar 01 1996 04:38 | 7 |
| re: .-1
I just used D-unix HW V4.1.1 and it works fine for creating the lan
interconnects on my DS900EF/MP.
Brad
|
| 3158.9 | | VIVIAN::M_PATTEN | The truth is out there | Fri Mar 01 1996 04:59 | 11 |
|
re -1
it looks like the problem only exists with the windows version
V 4.1.2 is required for windows to manage the routeabout versions of
the ef/ee
Martin Patten
|