ONTAP Operating System Issues
ONTAP Operating System Issues
Highest rated
(rating)- CONTAP-248510: Vserver delete fails with "Internal error. Failed to delete network configurations for Vserver"
- CONTAP-208827: Performance degradation is occurring due to high utilization of the root aggregate
- CONTAP-170136: FAS8200 and AFF A300 systems might experience non-responsive CPUs followed by multiple watchdog controller disruptions
- CONTAP-158564: Cluster is indicating "l2_reachability" for the cluster ports or data ports.
- CONTAP-234754: Bug public information is not yet available.
- CONTAP-258788: Scheduled configuration backup upload fails via PUT over HTTPS
- CONTAP-124322: Snapmirror resync fails on a Snapmirror Synchronous relationship.
- CONTAP-92516: Log forwarding requests fail when ONTAP upgrade adds management log forwarding LIF service
- CONTAP-203682: RFE: Indicate that access to SPI is not possible with AD accounts in 500 Internal Error pages
- CONTAP-274996: Observing periodic replace route update calls
- CONTAP-94107: ONTAP cluster node reboots unexpectedly
- CONTAP-277463: ONTAP cluster node reboots unexpectedly
- CONTAP-262447: Configuration backup error observed in EMS
- CONTAP-272863: MGWD application reboots on the node unexpectedly
- CONTAP-204169: Update validation fails with: Automated NDU is not supported when MetroCluster is in the configuration state "mcc-not-set"
Recently updated
(date updated)- CONTAP-183577: MAV can be bypassed when SAML and AD authentication methods are used for the same user
- CONTAP-193448: Slow mroot's unmount and mgwd restarting occurs when reverting to 9.1x.1
- CONTAP-171832: CBS - Object-Store changed association from Admin to Data vserver unexpectedly
- CONTAP-178257: Single-Node Azure CVO with a 90GB boot disk stops booting after upgrade to 9.14.1
- CONTAP-166169: ONTAP pre-update check for SnapMirror fails to execute properly
- CONTAP-169924: Cluster ports on FAS26xx, FAS27xx, FAS8200 and AFF C190, AFF A200, AFF A220, AFF A300 fail unexpectedly
- CONTAP-170030: netif.fatal.err:ALERT: The network device in slot 0 encountered fatal error e0a/e0b
- CONTAP-173273: Domain user in ONTAP with a custom role doesnt get the same authorization as a local user with same role
- CONTAP-169935: ONTAP cluster node reboots unexpectedly
- CONTAP-59311: SVM Disaster Recovery (SVMDR) relationship becomes unhealthy due to certificate conflict
- CONTAP-85001: Unable to login to node via SSH and the message [xinetd.hit.cps.limit:error] is seen in EMS logs.
- CONTAP-87533: bsdsocket.queueLimit.reached alert on port 966
- CONTAP-89439: Cloud Volumes ONTAP Azure virtual machine (VM) report health status as unhealthy in Azure portal
- CONTAP-163546: Apply failed for Object: volume Method: baseline. Reason: Volume - DR config replication failed
- CONTAP-114795: Node watchdog panic during [system configuration recovery node restore] command
Recently added
(date created)- CONTAP-350525: LIF rename fails with an error reporting that the port does not exist on the node
- CONTAP-353587: LIF taken down during ANDU when the LIF had conflicting failover policy and failover group
- CONTAP-352928: TLSv1 is allowed despite it being enabled
- CONTAP-90306: Allow configuration of username and password for mail relay server
- CONTAP-178830: MGWD spammed with pubsub::config_writer events
- CONTAP-344185: vifmgr.clusterBD.Partition observed yet cluster network is healthy
- CONTAP-115704: After upgrade to 9.13.1a one or more node's /tmp/ directory is intermittently hitting 100% capacity
- CONTAP-343689: Add email notifications for successful logins
- CONTAP-320038: Memory resource exhaustion caused pthread creation failed
- CONTAP-170049: ONTAP cluster node reboots unexpectedly
- CONTAP-277483: Schedules missing after SVM-DR migration to MetroCluster
- CONTAP-311675: SVM Migrate fails with "release failed"
- CONTAP-339960: Mellanox CQ completion failed due to incorrect memory access.
- CONTAP-301662: Unexpected panic after deleting large FlexCache containing a very large number of files
- CONTAP-317869: Suppress erroneous EMS for az-id metadata request failure in AWS-CVO instance