| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 81.1 | Both needed for SNMP. | CGOS01::DMARLOWE | PDP 11: MOV -(PC),-(PC) | Wed Nov 18 1992 10:41 | 7 |
| You still need the DB90 to do repeater management in the hub. The
DECagent cannot directly manage repeaters. The DECagent can be
either in the hub or running standalone on the LAN somewhere.
Even if you put the DECagent in the hub it can still manage other
hubs, through DB90s, on the LAN.
dmm
|
| 81.2 | Agent 1.1 will not need a bridge | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Mon Nov 30 1992 22:28 | 3 |
| version 1.1 or the agent (coming out in January will allow repeater
management without the bridge, but then the agent must be in the same
hub as the repeaters.
|
| 81.3 | Will agent support Telnet ? | DC101::COLE | ADEG Programs Team/Greenbelt,Md | Mon Dec 07 1992 10:47 | 12 |
|
> version 1.1 or the agent (coming out in January will allow repeater
> management without the bridge, but then the agent must be in the same
> hub as the repeaters.
Will it support Telnet for management ?
larry cole
|
| 81.4 | no Telent support in agent 1.1 | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Tue Dec 08 1992 20:48 | 4 |
| no. could you send me mail explaining who wants Telnet for management,
why, and what you feel the business potential would be?
Thanks
|
| 81.5 | Does the agent90 (SW1.1) management Repeater | DESS01::WITTAYAJ | | Fri Jul 16 1993 04:57 | 10 |
| Dear all.
I have been a agent90 and SW1.1 ,but I could not added repeater90T or
repeater 90C into agent's module.( I do not have Hub90 ) So I think
the agent90 can not managenemt a Repeater90 if it is stand alone (Yes
or No).But if I have a Hub90 and them is contained in the Hub90 ,I will
management a Repeater90 by without a Bridge90 .( Yes or No ).
Thank a lot.
Janmayka
|
| 81.6 | V1.1 needs a bridge to manage repeaters | QUIVER::GAUDET | | Tue Jul 20 1993 11:58 | 5 |
| You are correct. Standalone DECrepeaters are not manageable. V1.1 of
the DECagent 90 does not support management of DECrepeaters without a
DECbridge in the hub. Look for this support in V2.0.
...Roger...
|
| 81.7 | DECagent V1.1 ? | HGOVA::SIUKEUNGLEE | | Mon Sep 06 1993 03:06 | 2 |
| How can I get DECagent V1.1 ?
|
| 81.8 | DECagent 90 V1.1 pointer | NAC::FORREST | | Fri Oct 29 1993 09:04 | 76 |
| 15 October 1993- NAC::MANAGEMENT:AGENT_LOAD.TXT
DECagent 90 firmware V1.1 is now available.
The installation kits, update documentation and MIB descriptions may be found
in the following directory:
QUIVER::PROJ$722:[ONEHUB.RELEASE.DENMA.V1_1]
Where you may find the following files:
$$WHAT_ARE_THESE_FILES.READ_ME;3 2 24-JUN-1993 15:40:51.36
BRIDGE_MIB.TXT;11 90 12-MAY-1992 15:35:30.00
CHAR_MIB.TXT;7 42 12-MAY-1992 15:32:37.00
DECAGENT_UPDATE_ULTRIX.PS;1 1034 17-JUN-1993 09:55:04.95
DECAGENT_UPDATE_VMS.PS;1 1041 17-JUN-1993 09:54:44.87
DENMA011.A;1 666 24-JUN-1993 13:10:58.00
DENMA110.TAR;1 680 24-JUN-1993 12:00:26.99
DENMA_LOAD_PROCEDURE.TXT;6 16 24-JUN-1993 16:28:06.05
DH90_MIB.TXT;37 190 26-MAY-1993 13:11:57.00
MOBJ_MIBII_MIB.TXT;3 163 28-DEC-1990 18:54:50.00
MOBJ_PARENT_MIB.TXT;3 6 12-MAY-1992 13:00:17.00
RS232_MIB.TXT;6 37 12-MAY-1992 15:37:56.00
Refer to the $$WHAT_ARE_THESE_FILES.READ_ME file for a one line description of
each files contents.
Refer to the DENMA_LOAD_PROCEDURE.TXT file for a brief description of how to
install the kits for VMS or ULTRIX, and how to perform the update to the
DECagent 90. The more detailed descriptions of how to perform the updates are
available in the manuals: DECAGENT_UPDATE_ULTRIX.PS and DECAGENT_UPDATE_VMS.PS.
Important notes:
1. PERFORM A FACTORY RESET AFTER UPDATE TO V1.1!
Due to a bug recently found in the DENMA V1.1 code it is necessary to
perform a FACTORY RESET after upgrading to V1.1 from a previous
version.
The problems may only surface when a bridge is present in the AGENT's
HUB. One failure mode causes the repeaters in the AGENT's community to
not be manageable. If the bridge in the AGENT's community is queried
via mop console for the status of the repeaters, it replies that 'the
bridge is not the hub manager'. Another possible failure mode is that
the AGENT exports the bridge out of the AGENT's community.
It is necessary to FACTORY RESET all DENMAs regardless of configuration
to prevent this problem from resurfacing after some later
reconfiguration of the HUB.
2. DO NOT USE VT102 TERMINALS OR EMULATORS TO CONNECT TO THE CONSOLE PORT!
A bug causes the DECagent90 to hang if we see a particular response
string when the terminal is asked for its type.
When the DECagent90 detects that a console port connection is made, it
sends an ENQ to the terminal, and wants to see a VTxx series response.
Normally, the VTxx response is received and the console menu is
activated. A bug causes the DECagent90 to hang only if a VT102
response is received. The DECagent90 must be repowered to correct the
condition.
Any other terminal emulation in the VT series works fine (VT100, VT220,
VT320, etc.).
3. See below for a faster/easier DENMA load procedure for VMS
In an effort to streamline the process of loading DENMA V1.1 to units
in manufacturing, an intermediate loader has been created which
solicits for the load of the DENMA V1.1 image. (Thanks Roger!) This
simplifies the load procedure, as NCP is not required to initiate the
load to the DENMA. This is supported on VMS hosts only at this time.
The procedure to use this new intermediate loader is
RAPID_LOAD_PROCEDURE_VMS.TXT. The loader is LOAD_NMA_V11.SYS.
|