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, I have just upgraded our DECagent 90 from V1.1 to T2.0.9 and now I cannot connect via MOP to the console of the agent. From a Phase V system I get the following, $ set host/mop denma %MOP-E-NOCON, console carrier not supported by remote system $ and from a Phase IV system I get... NCP>conn via sva-0 phys addr 08-00-2B-2D-4A-ED Target does not respond NCP> Please note that the above commands return immediately, if I change the address on the Phase IV system (e.g. to 08-00-2b-ff-ff-ff) then it takes quite a while longer before timeing out. Also... should the agent see the 90l+'s that are in our hub, it only now picks up the DECbridge 90 and the DECrepeater 90C ? Alan Lloyd. CSC Basingstoke.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
653.1 | DECserver 90L+ | LEVERS::DRAGON | Tue Jan 25 1994 08:58 | 8 | |
Alan, Some DECserver 90L+s are autodiscoverable (DECserver 90L++), while other older revs are not. Those which are not autodiscoverable must be added via HUBwatch. Bob | |||||
653.2 | 1 down, 1 to go !!! | KERNEL::LLOYDA | Don't worry... Be Happy ;^) | Tue Jan 25 1994 09:33 | 7 |
Bob, O.k. that explains why they aren't available. Now then.... why can't I connect via MOP ? Al. | |||||
653.3 | DECagent 90 never supported inbound MOP | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Jan 25 1994 10:10 | 6 |
You never could. The DECagent 90 does not support inbound MOP connections. The only way to get the console menu is to connect a terminal or modem. If you have succeeded at doing this in the past I would be very interested in how. Roger Gaudet DECagent 90 Development |