| 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 |
I upgraded my workstation from a working hubwatch IFT11-2 to IFT1-1.8
and it failed because of a missing subset MMAHWMSU100 ?
Any suggestions?
Thanks Mark.
log of install and other information below....
# tar xvf MMAHWMSU118.tar
x ./instctrl/
x ./instctrl/MMA118.comp, 0 bytes, 0 blocks
x ./instctrl/MMAHWMSU118.ctrl, 116 bytes, 1 blocks
x ./instctrl/MMAHWMSU118.inv, 5626 bytes, 11 blocks
x ./instctrl/MMAHWMSU118.scp, 26935 bytes, 53 blocks
x ./instctrl/MMA.image, 24 bytes, 1 blocks
x ./MMAHWMSU117, 3389440 bytes, 6620 blocks
x ./INSTCTRL, 40960 bytes, 80 blocks
x ./MMA.image, 24 bytes, 1 blocks
x ./MMAHWMSU118, 3409920 bytes, 6660 blocks
# setld -l .
*** Enter Subset Selections ***
The subsets listed below are optional:
1) HUBwatch for ULTRIX
2) All of the Above
3) None of the Above
4) Exit without installing subsets
Enter your choice(s): 1
You are installing the following subsets:
HUBwatch for ULTRIX - IFT 1.1-8
Is this correct? (y/n): y
-n
HUBwatch for ULTRIX - IFT 1.1-8 (MMAHWMSU118)
Copying from . (disk)
Working....Tue Apr 13 13:22:10 GMT+11:00 1993
Verifying
Working....Tue Apr 13 13:23:12 GMT+11:00 1993
-n
Install Configuration for HUBwatch for DECmcc Management Station for ULTRIX
CANNOT be done until the basic kit installation completes.
The kit MMAHWMSU100 must be completely installed
#
#
# lmf list
Product Status Users: Total Active
HUBWATCH active unlimited
HUBWATCH-FOR-MSU terminated
DECMCC-MSU-RISC active unlimited
DECNET-ULTRIX active unlimited
ULTRIX active 2 1
#
#
(part listing of setld)
MMAHWMSU112 installed HUBwatch for ULTRIX - IFT 1.1-2
MMAHWMSU118 installed HUBwatch for ULTRIX - IFT 1.1-8
MSRBASE110 installed DECmcc MSU V1.1 BASE KIT
MSUAGNTEX110 installed DECmcc MSU V1.1 SNMP AGENT EXAMPLES
MSUMAN110 installed DECmcc MSU V1.1 MANUAL PAGES
#
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 207.1 | Deinstall, then install *latest* kit. | SLINK::HOOD | Just add water | Tue Apr 20 1993 12:43 | 5 |
T1.1.8 is fairly old. De-install the two previous versions of HUBwatch you've got loaded (MMAHWMSU112 and MMAHWMSU118), and then copy the latest kit, which is T1.1.18 and install that. It should work ok. Tom | |||||
| 207.2 | thanks and .. | MEO78A::BARNHOORN | Barney to his friends | Wed Apr 21 1993 04:33 | 29 |
Hi Tom, thanks for the information. I installed succesfully the new kit and it works fine. The only question is at startup, it gives warning and error messages. akubra> hubwatch -a ma42b -x 16.153.224.204 -c meo42bw & [1] 4425 akubra> (W) HUBWATCH_LIBRARY not defined (E) Can't open HUBWATCH_LIBRARY/hubwatch_agents - no such directory (W) Current agent not in the agent table (D) HUB CONFIGURATION: (I) ___________________________________________________________________________ (D) Slots: 1 2 3 4 5 6 7 8 (D) Cards: Empty Empty Empty DETMR DETMR Empty DENMA DEWGB (I) ___________________________________________________________________________ (D) Slot 4: Port 1: status = DISCONNECTED (OFF) (D) Slot 4: Port 2: status = ONLINE (D) Slot 4: Port 3: status = ONLINE (D) (etc) thanks again Mark. PS this machine is only running HUBWATCH no MSU or MCC. | |||||
| 207.3 | Agents file info, HUBWATCH_LIBRARY environment variable. | SLINK::HOOD | Just add water | Wed Apr 21 1993 12:33 | 36 |
> (W) HUBWATCH_LIBRARY not defined > (E) Can't open HUBWATCH_LIBRARY/hubwatch_agents - no such directory > (W) Current agent not in the agent table HUBwatch Version 1.1 requires that you define the (a) ULTRIX environment variable HUBWATCH_LIBRARY (b) OpenVMS logical name HUBWATCH$LIBRARY as the directory which contains or will contain the agents file (a) HUBWATCH_LIBRARY/hubwatch_agents (b) HUBWATCH$LIBRARY:HUBWATCH_AGENTS.DAT in order to read, write, or create the agents file. Although you can run HUBwatch 1.1 under either OpenVMS or ULTRIX without an agents file or HUBWATCH_LIBRARY / HUBWATCH$LIBRARY defined, you will need to completely specify the agent on the command line every time, and will not be able to switch among agents while in HUBwatch In version 1.0, and early T versions of 1.1, the agents file was called DH90_agents (I forget which directory was searched). The format of the agents file has changed for 1.1, although if you have an agents file from 1.0, it is backwards compatable. You do not have to create or edit the agents file by hand. It can be completely done within HUBwatch. All you have to do is define the name. (a) > setenv HUBWATCH_LIBRARY /usr/users/smith/agents/ (ULTRIX) (b) $ define hubwatch$library mydisk:[smith.agents] (OpenVMS) and HUBwatch will open or create /usr/users/smith/agents/hubwatch_agents or mydisk:[smith.agents]hubwatch_agents.dat The system startup procedure for OpenVMS (SYS$STARTUP:HUBWATCH$STARTUP.COM) automatically defines the system-wide logical name HUBWATCH$LIBRARY as SYS$LOGIN. Unfortunetly, there is no similar mechanism available for ULTRIX, so each user should add the setenv to his/her .cshrc or .login file. Tom Hood | |||||
| 207.4 | works fine. | MEO78A::BARNHOORN | Barney to his friends | Mon Apr 26 1993 20:01 | 7 |
Hi Tom, thanks, that works fine. regards Mark. | |||||