vgeek79

Hi, Is there a way to map my virtual HW virtual NIC in order? VM HW map JSON mac's DSM LAN # vNIC #1 mac1 LAN 1 vNIC #2 mac2 LAN 2 vNIC #3 mac3 LAN 8 vNIC #4 mac4 LAN 4 MySetup: ESXi 7.0U3 / RedPill DS3622xs / DSM 7.1-42661 Update 1 JSON included my VMX MAC's "mac1": "005056AA001", "mac2": "005056AA002", "mac3": "005056AA003", "mac4": "005056AA004", In TinyCore vNIC# + eth# & mac# matches order root@box:/home/tc# dmesg | grep eth [ 1.279973] vmxnet3 0000:04:00.0 eth0: NIC Link is Up 10000 Mbps [ 1.281575] vmxnet3 0000:05:00.0 eth1: NIC Link is Down [ 1.283729] vmxnet3 0000:06:00.0 eth2: NIC Link is Down [ 1.284765] vmxnet3 0000:07:00.0 eth3: NIC Link is Down In DSM it looks like that admin01@xpenologydsm7:/$ dmesg | grep eth [ 50.596284] vmxnet3 0000:04:00.0 eth0: NIC Link is Up 10000 Mbps [ 50.597589] vmxnet3 0000:05:00.0 eth1: NIC Link is Down [ 50.599181] vmxnet3 0000:06:00.0 eth2: NIC Link is Down [ 50.600224] vmxnet3 0000:07:00.0 eth3: NIC Link is Down [ 55.824233] vmxnet3 0000:06:00.0 eth7: renamed from eth2 <--- Wierd? What's happening here and would there be a way to force this in Redpill? PS: When using 3vNIC's all is good, haven't tried adding a 5th nic yet. Added extra parameters to my VMX file to play with PCI Bus, SLots, POrt to see if that changed anything, still DSM acts funky .vmx settings for vNICs ethernet0.pciSlotNumber=1184 ethernet1.pciSlotNumber=2208 ethernet2.pciSlotNumber=3232 ethernet3.pciSlotNumber=4256

Ah, My VMDK2 was on SATA 0:1 fixed now @ SATA 1:0 vNIC Ordering well I'll have to tame my OCD 😅 One last thing if I go beyond 4 NIC, I cant force DSM to use my VM HW MAC, @ 00:50:56:XX:XX:XX but 00:00:7F or similar, any ideas, tried grub grub.cfg

When using SATA for disk 2 I get this

VMDK #1 is on SATA Controller VMDK #2 is on PVSCSCI

Hi, Is there a way to force DSM do detect my VMDK #2 as disk 1? Also is there a way to map my virtual HW virtual NIC in the same order? VM HW map grub mac1 DSM LAN # vNIC #1 mac1 LAN 2 vNIC #2 mac2 LAN 3 vNIC #3 mac3 LAN 4 vNIC #4 mac4 LAN 1 MySetup: ESXi 7.0U1 / Jun 1.03b DS3617xs / DSM 6.2.3-25426 / FixSynoboot.sh VM HW VMDK #1 is Synoboot SATA VMDK #2 is for DSM on PVSCIS (also tried SAS) show has disk 2 Will later add LSI3008 SAS Passthru