Skip to main content
NetApp Knowledge Base

What is the ONTAP e0S interface?

  1. Last updated
  2. Save as PDF
Views:
2,539
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
HW
Last Updated:

Applies to

  • AFF A900
  • AFF A800, AFF C800
  • AFF A700s
  • AFF A400, AFF C400
  • AFF A320
  • AFF A250, AFF C250
  • FAS9500
  • FAS8700
  • FAS8300
  • FAS500f
  • FAS2820

Answer

The e0S interface is an interface in newer FAS and AFF storage systems.

Conceptually, e0S is an ONTAP interface on a node that is used for internal communication with its service processor (SP) or baseboard management controller (BMC).

  • It is auto-configured with hard-coded IP addresses in the 192.0.2.x subnet.
  • On most platforms, it is used for SP/BMC firmware updates and error condition reporting directly between the SP/BMC and ONTAP internally
  • On many BMC-based platforms, this internal subnet is used for HW-assisted storage failover, as well (since both nodes' e0S interfaces and BMCs can see each other internally).
Details
  • A private and internal Ethernet-switched subnet exists between both ONTAP HA partners and both BMCs:
    • ONTAP interface: e0S
    • BMC interface: Either eth0 or eth1, depending on the platform model
  • Uses subnet 192.0.2.0/24 with statically-assigned IP addresses for all interfaces
  • Features such as HW-assisted failover, ONTAP <-> BMC communications (IPMI), and BMC FW updates are performed over this private network
  • Boot media replacements for these platforms will use the e0S IP address for the system node restore-backup command
  • HW-assisted takeover is not configurable – it uses statically-assigned addresses (see the table, below)

The IP addressing is static and automatically configured on all related Ethernet interfaces:

Controller e0S Address/Mask BMC Address/Mask
A 192.0.2.84/24 192.0.2.81/24
B 192.0.2.85/24 192.0.2.82/24

Additional Information

What is the ONTAP e0M-16 interface?

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.