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

    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.

    Note: Starting in Junos OS Release 15.1X49-D100 for vSRX, support for chassis clustering to provide network node redundancy is only available on Windows Hyper-V Server 2016.

    • 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 vSRX VM

    Network
    Adapter

    Interface Names in Standalone Mode

    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

    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
    Adapter

    Interface Names in a Cluster

    1

    fxp0 (node 0 and 1)

    2

    em0 (node 0 and 1)

    3

    ge-0/0/0 (node 0)
    ge-7/0/0 (node 1)

    4

    ge-0/0/1 (node 0)
    ge-7/0/1 (node 1)

    5

    ge-0/0/2 (node 0)
    ge-7/0/2 (node 1)

    6

    ge-0/0/3 (node 0)
    ge-7/0/3 (node 1)

    7

    ge-0/0/4 (node 0)
    ge-7/0/4 (node 1)

    8

    ge-0/0/5 (node 0)
    ge-7/0/5 (node 1)

    Release History Table

    Release
    Description
    Starting in Junos OS Release 15.1X49-D100 for vSRX, support for chassis clustering to provide network node redundancy is only available on Windows Hyper-V Server 2016.

    Modified: 2017-09-27