Nimbostratus
I just talked to a member of our SNMP development team and the outlook is not good for your request. There is a method in the default naming of the interfaces with the "1.x", "2.x" and "3.x" formats depending on the type of interfaces. The problem arises that the number of interfaces is dependent not only on the physical characteristics of your system, but the software configuration as well.
Physical System:
Your system looks to have 16 10/100 ports, 2 Gig ports, and 1 admin port. We have other systems with more & less 10/100 and gig ports. For instance, our appliance product has 2 10/100 plus an admin port. I believe in this case the interface index 3 would map to 3.1 but in your system it would map to 1.3.
Software Configuration:
Each configured VLAN will create a new interface and from what I remember we support in the 1000's of VLANs on our devices. Plus a VLAN can be on 10/100 or Gig which would yield different interface name prefixes.
The SNMP index numbers are used solely to help with MIB table lookups. Within the index for the interface you are interested in, our MIB has the interface name as an attribute right next to the index number. The best solution we can recommend right now is to query the interface name in your SNMP application and use that when forwarding iControl requests.
-Joe
