Do remember though that hard coding the MAC address in the *LIND is a *LANDMINE during side by side migration scenarios. If you restore the source system to the target system and then try to vary on the line you will have a conflict that may be very difficult to troubleshoot and may very will knock down both lines. This is ESPECIALLY true if you use SNA because you probably copied over system name and all the SNA stuff too. I have been called in to fix such problems when the customer went a migration on their own and was having a 'Bad Monday.'

With TCP/IP there is no good reason to hard code the MAC address.

- Larry

rob@xxxxxxxxx wrote:
I, too, was going to suggest that Pete. However, why would one care what the hard adapter address is? That's why I always assign one when I create a line description. This way my saves and restores don't confuse network equipment that might have linked the old hard mac address. Been doing this since, well, when serial numbers were numeric and I embedded that into my mac address. Then I started doing stuff like division number, etc. Then it got really run converting TR mac addresses to Ethernet.

Rob Berendt


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].