Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 25 results
    • Why EMS alerts are not seen in OSM dashboard?
      https://kb.netapp.com/on-prem/ontap/DM/System_Manager/SM-KBs/Why_EMS_alerts_are_not_seen_in_OSM_dashboard
      Applies to ONTAP System Manager (OSM) 9.8 and above Answer The number of alerts on the dashboard was reduced since there were too many EMS alerts Access the events and alerts pages within System Manag...Applies to ONTAP System Manager (OSM) 9.8 and above Answer The number of alerts on the dashboard was reduced since there were too many EMS alerts Access the events and alerts pages within System Manager to see the EMS alerts Events: Click Events System Alerts: Click EVENTS & JOBS in the left pane Click System Alerts Additional Information additionalInformation_text
    • Event log showing failed to contact peer cluster
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Event_log_showing_failed_to_contact_peer_cluster
      Applies to ONTAP 9 Event Log (EMS) Cluster Peering Issue Peer relationship has been deleted but failed to contact peer cluster errors still show up in event log
    • Home directory access fails and EMS logs Nblade.cifsShrConnectFailed
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Home_directory_access_fails_and_EMS_logs_Nblade.cifsShrConnectFailed
      When a user tries to connect to Home dir share, it fails: ERROR Nblade.cifsShrConnectFailed: Vserver name: <vserver_name>, Vserver ID: 12, error description: No such object, error code: 2, share name:...When a user tries to connect to Home dir share, it fails: ERROR Nblade.cifsShrConnectFailed: Vserver name: <vserver_name>, Vserver ID: 12, error description: No such object, error code: 2, share name: %w, Windows user name: Domain\user2, UNIX user name: pcuser, server IP address: 1.2.4.1, client IP address: 1.2.3.4. Note: If it is unclear on which user home dir access is failing, a packet trace might be needed to find the user who is trying to connect to the home directory.
    • Data ONTAP 8: Where are EMS and messages log files written in Data ONTAP 8.0?
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Data_ONTAP_8__Where_are_EMS_and_messages_log_files_written_in_Data_ONTAP_8_0
      Clustered Data ONTAP 8 Data ONTAP 8 7-mode Messages and EMS log files in Data ONTAP 8.0: Data ONTAP 8.0 7-Mode: EMS_decode+dblade_syslog => old messages file (/etc/messages symlink with /etc/log/messa...Clustered Data ONTAP 8 Data ONTAP 8 7-mode Messages and EMS log files in Data ONTAP 8.0: Data ONTAP 8.0 7-Mode: EMS_decode+dblade_syslog => old messages file (/etc/messages symlink with /etc/log/messages) mhost messages => mhost messages file (/etc/log/mlog/messages.log) EMS only logs => ems log file (/etc/log/ems) Data ONTAP 8.0 Cluster-Mode: EMS+mhost messages => mhost messages file (/mroot/etc/log/mlog/messages.log) EMS only logs => ems log file (/mroot/etc/log/ems)
    • EMS Nblade.CifsLongRunPattMatch repeats due to '*' query as a wildcard search
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/EMS_Nblade.CifsLongRunPattMatch_repeats_due_to_'*'_query_as_a_wildcard_search
      Applies to CIFS EMS Nblade.CifsLongRunPattMatch repeats every 15 minutes for specific client IP. [node_name: kernel: Nblade.CifsLongRunPattMatch:error]: Detected a long running CIFS pattern matching o...Applies to CIFS EMS Nblade.CifsLongRunPattMatch repeats every 15 minutes for specific client IP. [node_name: kernel: Nblade.CifsLongRunPattMatch:error]: Detected a long running CIFS pattern matching operation. SMB dialect: SMB2/SMB3 Allowed pattern matching threshold (ms): 1000 Total pattern matching time taken(ms): 1015 Client IP address: xx.xxx.xxx.xxx Target Vserver name: svm_name Target Vserver ID: svm_id Wildcard Pattern: file* Share name: share_name Directory Path: path\sub_dir\sub_dir
    • Is it possible to modify the event filter, "important-events"
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Is_it_possible_to_modify_the_event_filter_important_events
      Applies to ONTAP 9 Answer "important-events" is system-defined filter. The system defined filter cannot be modified. Example: ::> event filter rule add -filter-name important-events -type exclude -mes...Applies to ONTAP 9 Answer "important-events" is system-defined filter. The system defined filter cannot be modified. Example: ::> event filter rule add -filter-name important-events -type exclude -message-name security.invalid.login Error: command failed: "important-events" is a system-defined filter and cannot be modified. Additional Information additionalInformation_text
    • Unix root user not able to access NTFS volume when there is no name mapping for root user
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unix_root_user_not_able_to_access_NTFS_volume_when_there_is_no_name_mapping_for_root_user
      Applies to ONTAP 9 Multiple Protocol Access Issue Not able to access NTFS volume from unix client using root user and getting below error in EMS logs: secd.nfsAuth.problem: vserver (vs1) General NFS a...Applies to ONTAP 9 Multiple Protocol Access Issue Not able to access NTFS volume from unix client using root user and getting below error in EMS logs: secd.nfsAuth.problem: vserver (vs1) General NFS authorization problem. Error: Get user credentials procedure failed
    • FabricPool - object.store.unavailable: Unable to connect to the object store "S3Bucket" from node
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Tiering/FabricPool_object_store_unavailable__Unable_to_connect_to_the_object_store_S3Bucket_from_node
      Applies to Cloud Volume ONTAP (CVO) Amazon Web Services (AWS) NetApp FabricPool Issue Multiple EMS alerts triggering daily: object.store.unavailable: Unable to connect to the object store "S3Bucket" f...Applies to Cloud Volume ONTAP (CVO) Amazon Web Services (AWS) NetApp FabricPool Issue Multiple EMS alerts triggering daily: object.store.unavailable: Unable to connect to the object store "S3Bucket" from node
    • EMS displays 'sfu.firmwareDownrev.shelf: Shelf 0a.shelf0 has downrev firmware'
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/EMS_displays_sfu_firmwareDownrev_shelf__Shelf_0a_shelf0_has_downrev_firmware
      Applies to ONTAP 9 Issue The following error message is displayed in EMS: cluster::> event log show Time Node Severity Event ------------------- ---------------- ------------- ------------------------...Applies to ONTAP 9 Issue The following error message is displayed in EMS: cluster::> event log show Time Node Severity Event ------------------- ---------------- ------------- --------------------------- 1/25/2021 10:51:37 node ERROR sfu.firmwareDownrev.shelf: Shelf 0a.shelf0 has downrev firmware.
    • AIQ Unified Manager event "too many snapshots" with an unexpected number of snapshots
      https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/AIQ_Unified_Manager_event_too_many_snapshots_with_an_unexpected_number_of_snapshots
      UM reports the event: Event: Too many Snapshot Copies The maximum number of Snapshot copies configured for this volume has been breached. The volume contains 70 Snapshot copies. The event displays the...UM reports the event: Event: Too many Snapshot Copies The maximum number of Snapshot copies configured for this volume has been breached. The volume contains 70 Snapshot copies. The event displays the Source Groups This event occurs while the number of snapshot does not match the configured volume threshold under STORAGE -> Select volume -> Edit Threshold -> Snapshot Copies The number of snapshots does also not match the global volume threshold under EVENT THRESHOLDS -> Volume -> Snapshot Copies
    • Alert EMS Message - secd.dc.out.of.pipe.instances
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Alert_EMS_Message_-_secd.dc.out.of.pipe.instances
      [kern_secd:info:11767] | [001.524.340] debug: Retrying Smb2NtCreateAndXFile to account for PIPE NOT AVAILABLE error { in Smb2NtCreateAndXFile() at src/Actions/ActionsONTAP.cpp:3094 } [kern_secd:info:1...[kern_secd:info:11767] | [001.524.340] debug: Retrying Smb2NtCreateAndXFile to account for PIPE NOT AVAILABLE error { in Smb2NtCreateAndXFile() at src/Actions/ActionsONTAP.cpp:3094 } [kern_secd:info:11767] | [001.524.484] ERR : Encountered NT error (NT_STATUS_PIPE_NOT_AVAILABLE) for SMB command Create { in LogNtStatusCode() at src/Commands/Commands.cpp:609 } [kern_secd:info:11767] | [001.524.488] ERR : SMB2 response has NT error 0xc00000ac { in ParseSmb2HeaderResponse() at src/Smb2/Smb2Utils.cp…