Supported Platforms
Interface Naming and Mapping
Each network adapter defined for a vSRX is mapped to a specific interface, depending on whether the vSRX instance is a standalone VM or one of a cluster pair for high availability. The interface names and mappings in vSRX have changed since the previous release (called Firefly Perimeter), as shownTable 1 and Table 2. Note the following changes:
- In standalone mode:
- fxp0 is the out-of-band management interface.
- ge-0/0/0 is the first traffic (revenue) interface.
- In cluster mode:
- fxp0 is the out-of-band management interface.
- em0 is the cluster control link for both nodes.
- Any of the traffic interfaces can be specified as the fabric links, such as ge-0/0/0 for fab0 on node 0 and ge-7/0/0 for fab1 on node 1.
Table 1 shows the interface names and mappings for a standalone vSRX VM.
Table 1: Interface Names for a Standalone vSRX VM
Network | Interface Name in Junos OS 15.1X49 for vSRX |
|---|---|
1 | fxp0 |
2 | ge-0/0/0 |
3 | ge-0/0/1 |
4 | ge-0/0/2 |
5 | ge-0/0/3 |
6 | ge-0/0/4 |
7 | ge-0/0/5 |
8 | ge-0/0/6 |
9 | ge-0/0/7 |
10 | ge-0/0/8 |
Table 2 shows the interface names and mappings for a pair of vSRX VMs in a cluster (node 0 and node 1).
Table 2: Interface Names for a vSRX Cluster Pair
Network | Interface Name in Junos OS 15.1X49 for vSRX |
|---|---|
1 | fxp0 (node 0 and 1) |
2 | em0 (node 0 and 1) |
3 | ge-0/0/0 (node 0) |
4 | ge-0/0/1 (node 0) |
5 | ge-0/0/2 (node 0) |
6 | ge-0/0/3 (node 0) |
7 | ge-0/0/4 (node 0) |
8 | ge-0/0/5 (node 0) |
9 | ge-0/0/6 (node 0) |
10 | ge-0/0/7 (node 0) |
