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 |
A stupid question, but noone seems to know here: Who is responsible for firmware upgrades in DEChubs covered by a service contract? Is it done by the customers themselves or by Digital CS? Does it depend on the type of service agreement or is it handled differently in different countries? Regards, Nils.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1828.1 | customer dependent? | NAC::FORREST | Thu Jan 12 1995 20:29 | 6 | |
Nils, I expect it mostly depends on the particular customer and their relationship to their Services people. I may be wrong, but I think the Services offering provides the customer with the new firmware kit, but with no assistance to upgrade. You might try contacting Elaine Davis in OGO for clarification. | |||||
1828.2 | Thanks for the response! | STKHLM::DUFVA | Mon Jan 16 1995 08:08 | 1 | |
1828.3 | DR90FS/TS unknown to DB90 | CSC32::RA_HALL | Wed Jan 18 1995 16:12 | 11 | |
One added point to your question. If you have a DR90TS or DR90FS in a DH90 that is using a DB90 as bus master, the modules will show up as unknown in the hub. The only way to display them is to configure the DR90TS or DR90FS as standalone modules. The modules will show up in a DH90 with a DA90 bus master. We have seen several calls here from customers on this and they consider it a problem. I have sent up an IPMT on this. Ray Hall CSC/CS Network Support. | |||||
1828.4 | It's a bridge restriction | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jan 20 1995 11:16 | 13 |
This is a known limitation when the DECbridge 90 is the hub master. The problem is that the backplane WhoAreYou responses from the DECrepeater 90FS and DECrepeater 90TS are *much* longer than 16 characters, which is all the bridge can handle. Within these 16 characters is the slot number and MAC address of the device, which is insufficient to identify the type of device. When the DECagent is the hub master it reads the entire device response on the backplane, which includes the system object identifier, system name, and IP address (to name a few). This is more than sufficient to identify the device. This has been investigated and would require a major rewrite of the DECbridge firmware. It is not likely to happen. ...Roger... |