Order of interface Mapping when a VPX is provisioned from SVM:
When a VPX is provisioned from SVM, the order of interface mapping is based on sequence:
Seq-1:
If VPX is provisioned with PF’s 10/1, 10/11, 10//2; then the VPX will enumerate them as {PF 10/1 => VF 10/1, PF 10/2 => VF 10/2, PF 10/11 => VF 10/3}
Now, if another PF is added 10/3, then, it will have enumerated as {PF 10/1 => VF 10/1, PF 10/2 => VF 10/2, PF 10/11 => VF 10/3, PF 10/3 => VF 10/4}
However, if the sequence was:
Seq-2:
VPX provisioned with PF’s 10/1, 10/11, 10/2 and 10/3, then VPX will enumerate them as {PF 10/1 => VF 10/1, PF 10/2 => VF 10/2, PF 10/3 => VF 10/3, PF 10/11 => VF 10/4}
In the first instance, since 10/3 was already assigned to PF 10/11 and config built in the VPX with 10/3, it does not change its name, when a new PF is added.
PF: Physical Function (Physical Interface).
VF: Virtual Function (Virtual Interface).