| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hi,
Is it possible to upgrade a DECbridge 90 that has a console password
configured?
I just spoke to a service engineer that had had problems with upgrading
a DB90. It showed up that the customer had configured the DB90 with
a remote console password and she tried to specify the `/pass=xxx'
qualifier with VMS NDU and the `/p passwd' qualifier with DOS NDU.
It didnt't work until she removed the bridge password.
I'm not sure if the `Bridge Password' and a `MOP Password' is the same
thing, and I currently don't have the equipment inhouse to test with.
I have not found any documented restriction concerning console password
and NDU. Should this work?
If not, I can imagine that users may run into situations as described
above, but with more hubs...
Another interesting thing; the SHOW command doesn't work from NDU DOS.
`decndup /s 08-00-2B-BE-26-23' to a DB90 gives 'DECNDUplus:device not
found'. It works to a DB90FL but it is identified as a DEFEB_510.
Does this have to do with the `SYS$SYSTEM:NDU$DEVICE.DAT' file, mentioned
in note #1668.1?
But if one tries the show commnad against the DB90, which fails, and then
against the DB90FL, it also fails with 'CDI_bind error-DLL_open failed-000C'.
If the PC is rebooted and NDUplus restarted, `/s' works to the DB90FL again.
Nils.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1948.1 | Can do! | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Feb 02 1995 10:23 | 29 |
You need to specify the /n switch on the DOS command line or the /nomanagement qualifier on VMS command line. Continue to use the /p switch (DOS) or /password qualifier (VMS) to specify the bridge password that was previously defined using the DEFINE BRIDGE PASSWORD command. Even though the DECbridge 90 supports the RBMS protocol, MOP is used to perform the downline load, so you must specify the "nomanagement" switch. As for the other problems you saw, yeah the NDU device data file is less than complete, so you will see strange things like a DEFEB device type for the DECbridge 90FL. You are correct that the NDU$DEVICE.DAT file is the culprit. The problem is that this file is indexed by an RBMS device code, which (unfortunately) happens to be the same for the DECbridge 90FL and the DECbridge 510. If you add the following two lines to the top of your SYS$SYSTEM:NDU$DEVICE.DAT file, you will not see the problem with your DECbridge 90's anymore (although if you ever upgrade a DECbridge 510, it will identify it as a DECbridge 90FL!). DECbridge90 DEWGB 0f 90 nn DECbridge90_FL DEWGF 10 90 nn As for the NDU SHOW command on DOS, that's another interesting one. I don't know why it happens, but I've seen the same behavior that if an error occurs in a SHOW command, any future SHOW commands will fail with the BIND error. I think there's something that gets out of whack with the IP stack, but I have no evidence to support that claim. HUBloader should make all these problems go away! ...Roger... | |||||
| 1948.2 | Tnx! | STKHLM::DUFVA | Nils Dufva - TSSC G�vle Sweden | Mon Feb 06 1995 10:14 | 3 |
Thank you for your explanation!
Nils.
| |||||