Interface Naming and Mapping
Table 1 lists the vSRX and Microsoft Azure interface names. The first network interface is used for the out-of-band management (fxp0) for vSRX.
Table 1: vSRX and Microsoft Azure Interface Names
Interface | vSRX Interface | Microsoft Azure Interface |
|---|---|---|
1 | fxp0 | eth0 |
2 | ge-0/0/0 | eth1 |
3 | ge-0/0/1 | eth2 |
4 | ge-0/0/2 | eth3 |
We recommend putting revenue interfaces in routing instances as a best practice to avoid asymmetric traffic/routing, because fxp0 is part of the default (inet.0) table by default. With fxp0 as part of the default routing table, there might be two default routes needed: one for the fxp0 interface for external management access, and the other for the revenue interfaces for traffic access. Putting the revenue interfaces in a separate routing instance avoids this situation of two default routes in a single routing instance. Ensure that interfaces belonging to the same security zone are in the same routing instance.
