vmwNsxTAuditLogHealthAuditLogFileUpdateError

VMWARE-NSX-MIB · .1.3.6.1.4.1.6876.120.1.0.24.0.1
MIB view Table view

Object

notification 
At least one of the monitored log files has read-only permissions or has
incorrect user/group ownership on Manager, Global Manager, Edge, Public
Cloud Gateway, KVM or Linux Physical Server nodes. Or log folder is
missing in Windows Physical Server nodes. Or rsyslog.log is
missing on Manager, Global Manager, Edge or Public Cloud Gateway nodes.
          
Action required:
1. On Manager and Global Managaer nodes, Edge and Public Cloud Gateway
nodes, Ubuntu KVM Host nodes ensure the permissions for the /var/log
directory is 775 and the ownership is root:syslog. One Rhel KVM and BMS
Host nodes ensure the permission for the /var/log directory is 755 and
the ownership is root:root.
2. On Manager and Global Manager nodes, ensure the file permissions
for auth.log, nsx-audit.log, nsx-audit-write.log, rsyslog.log and syslog
under /var/log is 640 and ownership is syslog:admin.
3. On Edge and Public Cloud Gateway nodes, ensure the file permissions
for rsyslog.log and syslog under /var/log is 640 and ownership is
syslog:admin.
4. On Ubuntu KVM Host and Ubuntu Physical Server nodes, ensure the
file permissions of auth.log and vmware/nsx-syslog under /var/log is
640 and ownership is syslog:admin.
5. On Rhel KVM Host nodes and Centos/Rhel/Sles Physical Server nodes,
ensure the file permission of vmware/nsx-syslog under /var/log is 640
and ownership is root:root.
6. If any of these files have incorrect permissions or ownership, invoke
the commands `chmod <mode> <path>` and `chown <user>:<group> <path>`.
7. If rsyslog.log is missing on Manager, Global Manager, Edge or Public
Cloud Gateway nodes, invoke the NSX CLI command `restart service syslog`
which restarts the logging service and regenerates /var/log/rsyslog.log.
8. On Windows Physical Server nodes, ensure the log folder:
C:\ProgramData\VMware\NSX\Logs exists. If not, re-install NSX on the
Windows Physical Server nodes.

Context

MIB
VMWARE-NSX-MIB
OID
.1.3.6.1.4.1.6876.120.1.0.24.0.1
Type
notification
Status
current
Parent
vmwNsxTAuditLogHealthFeature
Siblings
3

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Sibling Objects
ObjectTypeSyntaxOID
vmwNsxTAuditLogHealthAuditLogFileUpdateErrorClear
All monitored log files have the correct file permissions and ownership and rsyslog.log exists on Manager, Global Manager, Edge or Public Cloud Gateway nodes. Action re…
notification-.1.3.6.1.4.1.6876.120.1.0.24.0.2
vmwNsxTAuditLogHealthRemoteLoggingServerError
Log messages to logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) cannot be delivered possibly due to an unresolvable FQDN, an invalid TLS ce…
notification-.1.3.6.1.4.1.6876.120.1.0.24.0.3
vmwNsxTAuditLogHealthRemoteLoggingServerErrorClear
Configuration for logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) appear correct. Action required: None, receipt of this notific…
notification-.1.3.6.1.4.1.6876.120.1.0.24.0.4
Notification Objects
ObjectTypeSyntaxOID
vmwNsxTDataCenterTimestamp
The timestamp when the NSX Data Center event occurred.
scalarSNMPv2-TCDateAndTime.1.3.6.1.4.1.6876.120.1.1.1
vmwNsxTDataCenterFeatureName
The NSX Data Center feature ID associated with the event.
scalarVmwNsxTDataCenterFeatureIdType.1.3.6.1.4.1.6876.120.1.1.2
vmwNsxTDataCenterEventType
The name of the NSX Data Center event.
scalarVmwNsxTDataCenterEventTypeType.1.3.6.1.4.1.6876.120.1.1.3
vmwNsxTDataCenterEventSeverity
The severity of the NSX Data Center event.
scalarVmwNsxTDataCenterSeverityType.1.3.6.1.4.1.6876.120.1.1.4
vmwNsxTDataCenterNodeId
The node ID from where a NSX Data Center event was emitted.
scalarVmwNsxTDataCenterNodeIdType.1.3.6.1.4.1.6876.120.1.1.5
vmwNsxTDataCenterNodeType
The type of node from where a NSX Data Center event was emitted.
scalarVmwNsxTDataCenterNodeTypeType.1.3.6.1.4.1.6876.120.1.1.6
vmwNsxTDataCenterEntityId
The ID of a NSX Data Center entity an event pertains to. The event description field provides additional details of the entity. For example the ID can be for a specific Load Balan…
scalarVmwNsxTDataCenterEntityIdType.1.3.6.1.4.1.6876.120.1.1.21