正文文本
What is in an E-Series Support Bundle?
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/What_is_in_an_E_Series_Support_Bundle
Updated: Wed, 15 Jan 2025 14:58:21 GMT
Applies to
NetApp E-Series and EF-Series
Answer
This article describes some of the basic files/items you can find in a support bundle. The following is a list of
quick descriptions of the files in a support bundle:
Note: This list is subject to constant updates and changes.
Filename Description
asup- List of attempts to send ASUP messages to NetApp. Reports a 'beginning' attempt
'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 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
transmission-
and an 'ending', such as successful or failed
logs.txt
Displays the Drive Expansion Enclosure IDs and port connection details, shows
connection.txt which port connects to which port
controller-
Record of the last 100 error check conditions/errors reported by individual drives, not
drive-error- persistent through reboot
event-log.txt
core-dump-
Metadata about the core dump, includes Capture Time, Serial numbers of controllers
info.xml / all- (as well as platform and firmware level), size of the core, and trigger reason
coredump.xml
cumulative-drive-vol-
Drive and Volume statistics, such as read/write IOs, errors, and so on
stats.xml
drive-command-
Current and default settings for drive timeout values
aging-timeout.txt
Drive health data read from the drives themselves and sent for analysis in the future
drive-health-data.bin
using ASUP
drive-performance- Data from the Slow Drive Detection feature, include slow, none, idle and exempt
log.txt periods
Enterprise Management Window data from SANtricity, shows which subsystems are
emwdata_v04.bin
connected
failed-repository- Displays detailed information about repository faults, including what type of fault and
analysis.txt where it was found
feature-bundle.txt Shows all features on the subsystem (premium features)
firmware-
Devices firmware in the system
inventory.txt
ib-statistics.csv Infiniband statistics. Only collected on systems with Host Side Infiniband protocol
io-dump-metadata.txt Metadata for an IOC log dump. If one exists, indicates that an IOC had an issue
Displays the initiator-target-LUN nexus details on a per volume/initiator and IO
io-path-statistics.7z
shipping details
Copied out of SANtricity directly. It displays the date, local time, and description,
major-event-log.txt
event number, and event code. Each entry has a hex underneath for raw data
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
iscsi-session-
iSCSI connections. Only collected on systems with Host Side iSCSI protocol
connections.txt
iscsi-statistics.csv iSCSI Statistics. Only collected on systems with Host Side iSCSI protocol
List (manifest) of files in the support bundle/ASUP and metadata about them, such
manifest.xml
as size, time collected, and so on
Data about the management software (SANtricity), such as OS, previous errors,
msw-runtime-info.txt
firmware history, and directory location
nvsram-data.txt Dump of most of the NVSRAM data/settings
All devices state and status in the system. - A way to read the object graph, but small
Object-bundle.bin
bits of it
perf-stats-daily- Performance stats for each controller throughout the day broken down into minute
summary-[a | b].csv granularity
persistent-
List of SCSI reservations for multiple hosts connecting to a single volume
reservations.txt
pref_01.bin Preferences file from SANtricity, includes ASUP setup information
Gives link errors that occurred on the Fiber Channel Loop. Fiber Channel Backend
read-link-status.csv
Only
recovery-guru-
System list of errors or concerns in a user-friendly format with suggested actions.
procedures.html
Configuration and recent changes. This file (and a .bak backup) is also stored on the
recovery-profile.csv
HSW system and updated with configuration changes.
sas-phy-error- Errors on the SAS backend, includes invalid dwords, disparity errors, lost
logs.csv dword synchronization, and no dword synchronization
soc-statistics.csv Gives errors through "Switch on Chip". Fibre Channel Backend Only
A large list of controller shell commands run against each controller. More
state-capture-data.txt information about the content of the state capture can be found in What is in a
StateCapture as of Controller Firmware 8.20
storage-array-
Saved configuration script to recreate the configuration of a system
configuration.cfg
Parsed limited object bundle, shows components, states, mappings, and so on. More
storage-array-
information about the content of the state capture can be found in What is in a
profile.txt
Storage Array Profile?
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3
Debug Queue (DQ) logs. Detailed event logs that often record more than 5 items per
trace-buffers.7z second. 5MB limit and support bundle only captures the most recent trace. This file
needs to be parsed
tray-component- ESM logs, include event logging comparable to DQ and state capture similar to
state-capture.7z controller state capture
unreadable-
Sectors that are physically or logically unreadable (data is inaccessible)
sectors.txt
Metadata about the support bundle/ASUP itself. Used to route and categorize
x-header-data.txt
ASUPs (same information as headers)
Additional Information
additionalInformation_text
© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 4