On Tue, October 25, 2005 8:37 am, Rinaldo.Eversdijk at
stork.com said:
items for replacements in case one of all items run
down so we can
replace it immediatly, but we are now only missing the protocol to do so
for the ethernet address items.
Hope this helps for solving the installation problem.
I don't understand what you're trying to achieve here. The Ethernet
address is that device's unique world wide identifier so no two ethernet
devices have the same address, well, back in the days of the kit you're
talking about that was definitely true. If a piece of your equipment dies
you put another one in and VMS doesn't care a bit. Your terminal servers
are only managed by ethernet address (in that you can connect to it via
NCP using the ethernet address), the VXT doesn't care either.
Both the DECservers and the VXT are client devices and talk to the VAX
using LAT or IP (DS250 is LAT only). LAT doesn't care about the ethernet
address other than to use it as a destination for ethernet packets.
I thought it was part of the ethernet spec that the hardware address
couldn't be changed unless you're running a VMScluster.
cheers
--
adrian/witchy
Binary Dinosaurs creator/curator
www.binarydinosaurs.co.uk - the UKs biggest home computer collection?