ONTAP Operating System Issues
ONTAP Operating System Issues
Highest rated
(rating)- CONTAP-108899: Upgrade stopped due to an NVRAM log not synchronized
- CONTAP-122618: vifmgr.clusterBD.Partition EMS event observed on switchless cluster
- CONTAP-248510: Vserver delete fails with "Internal error. Failed to delete network configurations for Vserver"
- CONTAP-258788: Scheduled configuration backup upload fails via PUT over HTTPS
- CONTAP-208827: Performance degradation is occurring due to high utilization of the root aggregate
- CONTAP-266869: CVE-2024-6387 OpenSSH Vulnerability in ONTAP 9
- CONTAP-170136: FAS8200 and AFF A300 systems might experience non-responsive CPUs followed by multiple watchdog controller disruptions
- CONTAP-47858: Configuration replication service might fail in a MetroCluster configuration
- CONTAP-30152: Feature request: Add secure SMTP support for ONTAP event config
- CONTAP-277483: Schedules missing after SVM-DR migration to MetroCluster
- CONTAP-277809: vifmgr reboots when ONTAP REST API retrieves port information
- CONTAP-361979: Vserver in a MetroCluster config goes to degraded state due to publickey failing to replicate
- CONTAP-265323: Configuration backups fail due to small scratch space available
- CONTAP-349530: Keys managed by External KMIP Server may not be restored during reboot
- CONTAP-158564: Cluster is indicating "l2_reachability" for the cluster ports or data ports.
Recently updated
(date updated)- CONTAP-447334: ONTAP ports in LACP ifgrp flap repeatedly
- CONTAP-520139: System became unresponsive due to low FreeBSD memory availability - high dma_buffer allocations
- CONTAP-170030: netif.fatal.err:ALERT: The network device in slot 0 encountered fatal error e0a/e0b
- CONTAP-59311: SVM Disaster Recovery (SVMDR) relationship becomes unhealthy due to certificate conflict
- CONTAP-67864: ONTAP httpd process may consume excessive memory
- CONTAP-98254: "coredump.long.running.msg: Coredump manager finished processing a long running message" repeatedly logged in event log
- CONTAP-81802: SSH-RSA is not supported in FIPS mode.
- CONTAP-87056: LS mirror updates fail when the transfer coincides with a snapshot schedule on the source volume
- CONTAP-94633: SnapMirror transfer failure causes memory leak
- CONTAP-530670: Inconsistent Snapmirror show output for SM-S relationships
- CONTAP-536159: Node reboot due to page fault error
- CONTAP-278690: System with Intel CVL E810 card panics with error code 0x8029
- CONTAP-428370: VLDB restart on node
- CONTAP-170049: ONTAP cluster node reboots unexpectedly
- CONTAP-598661: ONTAP upgrade to NODAR image causes node to fail boot after giveback
Recently added
(date created)- CONTAP-607439: ONTAP disaggregated shows callhome.spm.process.maxexit:error during boot
- CONTAP-607421: DR CONFIG REPLICATION FAILED: Apply failed for Object: vserverPeer_permission_api_byuuid Method: baseline. Reason: A cluster that is peered with the MetroCluster partner cluster is not peered with the local cluster
- CONTAP-236819: ICMP Timestamp Request Remote Date Disclosure
- CONTAP-553627: Single Node GCP CVO did not boot up automatically after a live backend host migration
- CONTAP-606766: Drives might fail with medium errors
- CONTAP-574337: DR CONFIG REPLICATION FAILED: Apply failed for Object: root_volume_view Method: baseline. Reason: Another volume is currently being created with the name
- CONTAP-598661: ONTAP upgrade to NODAR image causes node to fail boot after giveback
- CONTAP-604033: Autosupport management.log collections getting failed with duplicate payload body filename errors
- CONTAP-84239: LDAP configuration with Active Directory requires Unix attributes
- CONTAP-538480: ONTAP cluster node reboots unexpectedly
- CONTAP-594983: Node names are not anonymized in BOOT-DEVICE-INFO.txt ASUP file
- CONTAP-594778: Customer sensitive info not redacted in few ASUP XML files
- CONTAP-594861: Node names are not anonymized in bsd-df-i-k.txt, bsd-sysctl-spinvfs.txt and bsd-tmp-file-list.txt
- CONTAP-470402: ONTAP cluster node reboots unexpectedly
- CONTAP-467432: TLS Connections for Liveness checks get hung