Skip to main content
NetApp Knowledge Base

What is the ONTAP e0M-16 interface?

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

Applies to

  • AFF A700, AFF A220, AFF A200, AFF C190
  • FAS9000, FAS8200, FAS2750, FAS2720, FAS2650, FAS2620
  • ONTAP 9.2+

Answer

  • e0M-16 is a hidden, internal ONTAP interface on a node that is used for 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
HA Systems Details
  • AFF A700/FAS9000
  • AFF A300/FAS8200
  • AFF A220/FAS2750/FAS2720
  • AFF A200/FAS2650/FAS620
  • AFF C190
  • e0M-16 (specifically using VLAN tag 16) is sharing the same physical internal Ethernet port as e0M, but is restricted to only communicate with its local SP or BMC, also on VLAN tag 16
  • e0M-16 is always hard-coded to 192.0.2.83. The SP or BMC eth0.16 interface is always configured with 192.0.2.80
  • e0M-16 is in its own IPspace (OS2SP)
  • HW-assisted failover does not use e0M-16 when communicating with the partner's SP or BMC
  • Prior to ONTAP 9.2 the e0M port was bifurcated into e0S on these platforms

Additional Information

What is the ONTAP e0S 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.