IBM Cloud Docs
Glossary of vSRX terminology

Glossary of vSRX terminology

Interface names

Review the following interface names.

ae - Aggregated Ethernet interface. This interface is a virtual aggregated link and has a different naming format from most PICs. For more information, see Aggregated Ethernet Interfaces.

fxp - Management and internal Ethernet interfaces. You can use the show chassis hardware command to display hardware information about the router, including its Routing Engine model. To determine which management interface is supported on your router and Routing Engine combination, see Management Ethernet Interfaces Overview.

ge - Gigabit Ethernet interface.

  `user@host> show configuration interfaces`

  or

  `user@host> show configuration interfaces ge-4/0/0`

gr - Generic routing encapsulation (GRE) tunnel interface.

gre - Internally generated interface that is configurable only as the control channel for Generalized MPLS (GMPLS). For more information, see the MPLS applications user guide.

You can configure gre interfaces (gre-x/y/z) only for GMPLS control channels. gre interfaces are not supported or configurable for other applications.

lo - Loopback interface. The Junos OS automatically configures one loopback interface (lo0). The logical interface lo0.16383 is a nonconfigurable interface for router control traffic.

reth - redundant Ethernet interface is a pseudo-interface that includes a physical interface from each node of a cluster. A reth interface of the active node is responsible for passing the traffic in a chassis cluster setup.

A redundant Ethernet interface inherits its failover properties from the redundancy group x that it belongs to. A redundant Ethernet interface remains active if its primary child interface is available or active. For example, if reth0 is associated with redundancy group 1 and redundancy group 1 is active on node 0, then reth0 is up if the node 0 child of reth0 is up.

st0 - Secure Tunnel interface, which is used for routing traffic in VPNs. For every new VPN destination, use a different st0. Don't use st1, st2, and so on.

For more information, see Interface Naming Overview.