Skip to main content
NetApp Knowledge Base

Old Storage Array name for E-Series is still recorded in the ASUP transmission logs after rename

Views:
242
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
esg
Last Updated:

Applies to

E-Series

Issue

AutoSupport(ASUP) transmission logs still record the old Storage Array name even after renaming it to a new one.

Example:

  1. Change Storage Array name from E2824 to E2824-test on 7/2/20.
  2. The transmission logs on 7/3/20 still show the old name like below:

7/3/20 00:28:25 UTC -> Priority:INFO, ASUP Message Type:Daily Schedule, ASUP Task Type:Collection, Status:NONE, Storage Array:E2824, SAID:xxxx, Chassis Serial Number:xxxx, Thread ID:431,900, Delivery Method:NONE, Sequence Number:1049, Delivery URI:N/A, AutoSupport Decompressed Size:16970150, Total Collection Time:24134, Message:AutoSupport message collection initiated.
7/3/20 00:28:26 UTC -> Priority:INFO, ASUP Message Type:Large File Chunk, ASUP Task Type:Delivery, Status:NONE, Storage Array:E2824, SAID:xxxx, Chassis Serial Number:xxxx, Thread ID:432,409, Delivery Method:HTTPS, Sequence Number:1049, Delivery URI:support.netapp.com/put/AsupPut/, AutoSupport Decompressed Size:N/A, Total Collection Time:N/A, Message:AutoSupport message delivery is initiated.

 

 

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.