One of those mysteries I will never understand - vmnic order

Talking to several people shows I am not imagining things 
Have three server, same hardware, same model, same configuration.
Two onboard nics, two dual port ETs - totaling 6 ports..
System 1 ... onboard nics :vmnic4/vmnic5
System 2 ... onboard nics :vmnic2/vmnic3
System 3 ... onboard nics :vmnic0/vmnic5
With random things like that - how are hardware profiles / stateless systems supposed to work without problem (never tried it mind you).
And that goes back to ESX 3.x days. Back in the days there was the theory that IRQ Remapping has to be disabled ... which only worked to avoid the order to be mixed when other hardware, i.e. raid controller, were insert. But obviously not in that case, as the system has to run before you can disable that to start with...

Have three server, same hardware, same model, same configuration.
Two onboard nics, two dual port ETs - totaling 6 ports..
System 1 ... onboard nics :vmnic4/vmnic5
System 2 ... onboard nics :vmnic2/vmnic3
System 3 ... onboard nics :vmnic0/vmnic5
With random things like that - how are hardware profiles / stateless systems supposed to work without problem (never tried it mind you).
And that goes back to ESX 3.x days. Back in the days there was the theory that IRQ Remapping has to be disabled ... which only worked to avoid the order to be mixed when other hardware, i.e. raid controller, were insert. But obviously not in that case, as the system has to run before you can disable that to start with...
My own knowledge base made public: http://open902.com 

Comments
MCSA 2003, LFCS, LFCE (expired), VCP6-DCV
Maybe its a random vmnic generator.