Skip to main content
NetApp Stage KB

E-Series component location in MajorEventLog is not present in external syslog event

  1. Last updated
  2. Save as PDF

Views:
1
Visibility:
Public
Votes:
0
Category:
e-series-santricity-web-services-proxy
Specialty:
esg
Last Updated:

Applies to

  • NetApp E-Series
  • SANtricity System Manager
  • External syslog configuration

Issue

  • The component location recorded in the MEL (Major Event Log) is not present in the alert received on the external syslog server.
  • In SANtricity System Manager > Support > Event Log records:

"Date/Time","Priority","Component Type","Component Location","Description","Sequence Number","Event Type","Event Specific Codes","Event Category","Logged By"

"Jul 30, 2025 6:11:04 AM","Critical","Channel","Host-side: Controller B, Port 6","Fibre channel link errors - threshold exceeded","156621","1207","0/0/0","Error","B"

  • External syslog server alert is retrieved with the following details without component location above:

2025-07-30T06:11:09Z <MgmtIP> StorageArray <ArrayName>;1207;Critical;Fibre channel link errors - threshold exceeded

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.