| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 756.1 | An IP address is needed to be managed remotely. | QUIVER::GALLAGHER | | Wed Feb 23 1994 14:11 | 26 |
| >Can any body tell me whether you can connect to a DEC Agent 90 over the network
>assuming the Agent has not yet been assigned an IP address or name, i.e. is a
>newly installed agent.
Nope. You must first give it an IP address.
>I have tried MOP RCF connect but the Agent appears to send a garbage packet in
>response to reserve console and request id from the VAX.
>
>Is there anything within hubwatch which will allow you to connect to the agent.
>
>The reason I ask is that a customer has a specific need to configure new Agents
>remotely.
(I have no clue about the "garbage packet".)
MOP is not a routed protocol. I would claim that even if you could configure
the DECagent90's IP address using MOP this would still not satisfy your
customer's requirement.
I don't think we're doing anything different than other vendors. In order
to be managed remotely you need a routing protocol. In order to initialize
your routing protocol you need a routing address. Please let me know if
other vendors claim to meet this requirement, and how they do it.
-Shawn
|
| 756.2 | When I say "remote" | KERNEL::EVANSN | | Wed Feb 23 1994 14:35 | 11 |
| When I said remote I merely meant that the customer would set host to a machine
on the same LAN as the new agent, I realise that MOP is not routable.
But if you say MOP won't work then that's good enough for me.
However it would be nice to know why the Agent even bothers to respond to the
connect, even if it is a rubbish packet.
Regards
Neal
|
| 756.3 | And as far as HUBwatch goes... | SLINK::HOOD | I'd rather be surfing | Wed Feb 23 1994 15:48 | 3 |
| HUBwatch only speaks SNMP, so it can't do what you want.
Tom
|
| 756.4 | BOOTP instead of MOP? | QUIVER::GALLAGHER | | Wed Feb 23 1994 16:35 | 12 |
| Neal,
The DECagent90 doesn't support inbound MOP remote console. It does use
MOP to manage other devices. So no, you can't use MOP. (The garbage
packet is still a mystery to me. If you could capture the request and
response I'm sure some of the DECagent folks would be interested.)
But, the DECagent90 does support BOOTP. Your customer could set host
to an U*IX station and configure the BOOTP table to give the DECagent90
an IP address. Perhaps this satisfies your customer's requirement?
-Shawn
|
| 756.5 | How about SLIP? | ARRODS::GILLJ | John, DTN 847-5849 | Thu Feb 24 1994 09:16 | 4 |
| Having configured the DECagent 90 is it possible to connect to it using
SLIP (i.e. Out of band through it's console port)?
JG
|
| 756.6 | SLIP support ... YES | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Feb 24 1994 19:14 | 4 |
| DECagent V2.0 will provide this functionality. It is not in pre-V2.0 DECagents.
Roger Gaudet
DECagent 90 devo
|
| 756.7 | DECagent v2 kit? | ARRODS::GILLJ | John, DTN 847-5849 | Fri Feb 25 1994 08:23 | 8 |
| This is very good news Roger.
Do you have a network pointer for the DECagent v2 kit?
Thanks,
John
|
| 756.8 | Kit location | LEVERS::BENSON | DTN 227-3555 | Fri Feb 25 1994 17:05 | 12 |
| John,
The field test kits are located at:
Quiver::proj$722:[onehub.release.denma.t2_0]
$$README.TXT (how to)
DECHUB90.MIB (MIB)
DENMA_FT020.A (VMS)
DENMA_FT200.TAR (ULTRIX)
Comments to me (LEVERS::BENSON) or Roger (QUIVER::GAUDET).
|