Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Interface Naming and Mapping

    Table 1 shows the vSRX and AWS interface names. The first network interface is used for the out-of-band management (fxp0) for vSRX.

    Table 1: vSRX and AWS Interface Names

    Interface
    Number

    vSRX Interface

    AWS Interface

    1

    fxp0

    eth0

    2

    ge-0/0/0

    eth1

    3

    ge-0/0/1

    eth2

    4

    ge-0/0/2

    eth3

    5

    ge-0/0/3

    eth4

    6

    ge-0/0/4

    eth5

    7

    ge-0/0/5

    eth6

    8

    ge-0/0/6

    eth7

    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.

    Note: Ensure that interfaces belonging to the same security zone are in the same routing instance. See KB Article - Interface must be in the same routing instance as the other interfaces in the zone.

    Modified: 2017-07-14