Move ESXi VM and keep MAC address
-
@scottalanmiller said:
@Dashrender said:
Are you saying that either a) you are expressly told in the software you typically deal with, or b) you expressly inquire so you know how it works?
I feel like the software selection process has somehow always enabled us to avoid these kinds of products. A trial, for example, would normally tell you or reviews. I can't imagine quality software that would work this way. Hard to believe that there weren't warning signs.
You can't really avoid solidworks & AutoDesk both with engineering
-
Everyone gets caught by weird licensing sometime. But nearly always I found that it is from a time when IT decision making was bypassed. Never seen IT get caught by this, only IT get stuck cleaning it up. I've seen IT have things like this, but they knew about it before installing.
-
@thecreativeone91 said:
@scottalanmiller said:
@Dashrender said:
Are you saying that either a) you are expressly told in the software you typically deal with, or b) you expressly inquire so you know how it works?
I feel like the software selection process has somehow always enabled us to avoid these kinds of products. A trial, for example, would normally tell you or reviews. I can't imagine quality software that would work this way. Hard to believe that there weren't warning signs.
You can't really avoid solidworks & AutoDesk both with engineering
True. But I think people tend to be aware of how the licensing works with those. How often do you see those catching people "by surprise" after install time?
-
@Dashrender said:
@thecreativeone91 said:
@Dashrender said:
And I've installed AutoCAD server before and don't recall it saying that it tied to the MAC either.
AutoDesk specifically tells you this when you ask about licensing.
when you ask? meaning you are talking to a person? the last time I installed Autodesk was 15 years ago.. so it could be completely different today.
I and most people I work with always as vendors how their licensing works. It's uses part of the pre-sales and post sales meetings as well.
-
@thecreativeone91 said:
@Dashrender said:
@thecreativeone91 said:
@Dashrender said:
And I've installed AutoCAD server before and don't recall it saying that it tied to the MAC either.
AutoDesk specifically tells you this when you ask about licensing.
when you ask? meaning you are talking to a person? the last time I installed Autodesk was 15 years ago.. so it could be completely different today.
I and most people I work with always as vendors how their licensing works. It's uses part of the pre-sales and post sales meetings as well.
You have control of what software you purchase? It isn't just thrown on your desk?
-
These particular problems are pretty wide and far between, and almost never effect consumers...
But Scott's right, when the decision is made my non IT, that's when most problems occur, and where I have found myself more often than not.
-
@Dashrender said:
These particular problems are pretty wide and far between, and almost never effect consumers...
But Scott's right, when the decision is made my non IT, that's when most problems occur, and where I have found myself more often than not.
Right, which bypasses IT "knowing" and explains why IT often gets caught cleaning up licensing issues. If IT does the decision making and approval and research sure, licensing blips will slip by sometimes, but by and large I think the majority of weird issues like this get caught and either avoided (move to a different vendor) or mitigated (come up with a good strategy for dealing with it like virtualizing MACs or just documenting well.)
-
One, after the fact use cases I ran into, was when I was playing with ESXi and Veeam replication of vCenter 5.0. Upon successful replication of the vCenter appliance from one host to another, I found that the O/S running vCenter, some flavor of Linux, would assign a new MAC address to a new eth0 NIC. You could go in via command line and fix that, but as a more Windows-type admin, no one has time for that. My fix then was to copy the MAC address on host one. When you switch the MAC type to static, it will want to assign something new (why you copied prior to this). Once done, I now had a good replicated vCenter. My environment really doesn't need one, but was playing.
If I remember, possibly newer versions of ESXi have a reserved block of MACs that may be causing the error above. Anyway, that's my 2 pennies.
-
@DenisKelley said:
....some flavor of Linux, would assign a new MAC address to a new eth0 NIC.
The MAC isn't assigned by Linux. You can override it there. But this would be the hardware, the hypervisor or the driver doing that, not Linux.
-
@DenisKelley said:
If I remember, possibly newer versions of ESXi have a reserved block of MACs that may be causing the error above.
Yes, that's what I have seen people run into. Using the reserved block and then wanting mobility of the reserved block.
-
@scottalanmiller said:
@DenisKelley said:
....some flavor of Linux, would assign a new MAC address to a new eth0 NIC.
The MAC isn't assigned by Linux. You can override it there. But this would be the hardware, the hypervisor or the driver doing that, not Linux.
Good to know. Just knew it was add and assigned new MAC as first NIC.
@scottalanmiller said:
@DenisKelley said:
If I remember, possibly newer versions of ESXi have a reserved block of MACs that may be causing the error above.
Yes, that's what I have seen people run into. Using the reserved block and then wanting mobility of the reserved block.
So you're saying I can't have my cake and eat it too?
-
@DenisKelley said:
Yes, that's what I have seen people run into. Using the reserved block and then wanting mobility of the reserved block.
So you're saying I can't have my cake and eat it too?
Pretty much
