Use the Issues view to review possible problems with Teradata Fabric. Some of these issues might require you to take action. The following types of issues are reported:
- Teradata Fabric component has gone offline.
- Teradata Fabric Manager has failed.
- Teradata Fabric Manager backup failed.
- Teradata Fabric Manager is running out of disk space.
- One or more Teradata Fabric Managers are running different versions of the Teradata Fabric Manager package.
- One or more nodes on the system are missing the connector package.
- System time is incorrect on a node or a Teradata Fabric Manager.
- Fabric unexpectedly restarted.
- Driver unexpectedly restarted.
- Connector is missing a link.
- Network configuration of link has failed to match network address on nodes.
- Certificate authority or server certificates are about to expire.
- Link name or fabric port conflicts for multiple Teradata Fabric Manager clusters.
- Inconsistent primary Teradata Fabric Manager cluster for system.
- Offline nodes scheduled for deletion.
- Node is unable to bind to proxy port.
- Node is running out of disk space.
Each condition has an associated severity, either critical or warning.
You can view the history of an issue. With the exception of unexpected fabric and driver restart issues, issues are automatically resolved when the underlying problem is corrected. You can manually delete the fabric and driver restart issues to clear them.
Use the Monitored Systems administration portlet in Viewpoint to configure issues to automatically generate alerts. See the Teradata® Viewpoint User Guide, B035-2206 for more information.