LLD: macro supported

[steveboyson]

Hi folks,
while I understood the concept of LLD (both SNMP and agent based) I wonder it it is possible to have two LLD where the later relies on macros defined by the former.

Actual case is the discovery of VMware virtual machines running on ESXi 5.0.
The have a unique index which I can get via the "standard" discovery mechanisms.

But the VMs do not have an identical number of disks nor do the have the same amount of NICs, and they are connected to different vSwitches.

Example:

VMWARE-VMINFO-MIB::vmwVmMAC.92.5 = STRING: 0:c:29:93:1b:ef
VMWARE-VMINFO-MIB::vmwVmMAC.92.6 = STRING: 0:c:29:93:1b:f9
VMWARE-VMINFO-MIB::vmwVmMAC.92.7 = STRING: 0:c:29:93:1b:3
VMWARE-VMINFO-MIB::vmwVmMAC.92.8 = STRING: 0:50:56:bd:54:d7
VMWARE-VMINFO-MIB::vmwVmMAC.114.6 = STRING: 0:50:56:bd:f4:d4
VMWARE-VMINFO-MIB::vmwVmMAC.119.4 = STRING: 0:50:56:bd:e:ba
VMWARE-VMINFO-MIB::vmwVmMAC.124.5 = STRING: 0:50:56:bd:5a:4e
VMWARE-VMINFO-MIB::vmwVmMAC.126.3 = STRING: 0:50:56:bd:59:5
VMWARE-VMINFO-MIB::vmwVmMAC.126.4 = STRING: 0:50:56:bd:45:84
VMWARE-VMINFO-MIB::vmwVmMAC.126.5 = STRING: 0:50:56:bd:be:6d
VMWARE-VMINFO-MIB::vmwVmMAC.126.6 = STRING: 0:50:56:bd:8a:27

... where the number after "vmwVmMAC" is the VM_ID, the following number is the index to the NIC.
You see that the last number differs from machine to machine.

While I can LLD the VM_ID, I fail with the number following the VM_ID.

My question:
can a LLD rule use a previously discovered {#VM_ID}, aka
vmwVmMAC.{#VM_ID}.<discovery-starts-here> to get the correct results?

Thank you in advance!