Home
In Data Center Operation, the Data Center Operation server supports these SNMP OIDs and response values.
To implement the alarm statuses in Data Center Expert, update the Device Definition File, schneiderops.xml, in Data Center Expert. Download the file from the software download link provided by Schneider Electric and follow the instructions about updating DDFs in the DCE user assistance.
Application server (OID .1.3.6.1.4.1.318.1.2.2.1.1.0)
|
Response |
Name |
Description |
|---|---|---|
|
1 |
Unknown |
The status of the application server is unknown. Check Webmin and if the problem persists, contact Technical Support. |
|
2 |
Stopped |
Restart the Data Center Operation server. If the server was part of a cluster, see the Data Center Operation User Assistance about rejoining the cluster. If the problem persists, contact Technical Support. |
|
3 |
Running |
No problem |
|
4 |
Running but missing nodes |
High availability is lost. The Data Center Operation Application server is running but one or more nodes are not available. If the Data Center Operation server is part of a cluster, ensure all nodes are running and there is a network connection between the nodes. If the problem persists, contact Technical Support. |
|
5 |
Initializing |
Wait for the Data Center Operation Application server to initialize. If the problem persists, contact Technical Support. |
|
6 |
Starting or non responding |
Wait for the Data Center Operation Application server to finish starting. If |
|
7 |
Disaster Recovery |
This node is running in DR mode. |
|
8 |
Running but postoffice is inconsistent |
The JBoss postoffice is currently inconsistent. This may be a temporary issue. If |
|
9 |
Running but missing jgroups |
The JBoss is missing jgroups. This may be a temporary issue. If the problem persists for more than 10 minutes, contact Technical Support. |
Database server (OID .1.3.6.1.4.1.318.1.2.2.1.2.0)
|
Response |
Name |
Description |
|---|---|---|
|
1 |
Unknown |
The status of the database is unknown. Check Webmin and if the problem persists, contact Technical Support. |
|
2 |
Stopped |
Restart the Data Center Operation server. If the server was part of a cluster, see the Data Center Operation User Assistance about rejoining the cluster. If the problem persists, contact Technical Support. |
|
3 |
Running |
No problem |
|
4 |
Detached |
High availability is lost. The database is detached from the cluster and does not receive updates. See the Data Center Operation User Assistance about reattaching the database node to the Data Center Operation cluster. If the problem persists, contact Technical Support. |
|
5 |
Catching up |
The database is catching up with the cluster. Wait for the Data Center Operation database to retrieve all updates from the master node. If the problem persists, contact Technical Support. |
|
6 |
Attaching |
The database is attaching to the cluster. Wait for the Data Center Operation database to attach to the cluster. If the problem persists, contact Technical Support. |
|
7 |
Running as Master |
The database is the master in a cluster. |
|
8 |
Running as Primary slave |
The database is the primary slave in the cluster. All changes on master are synchronously replicated to this node. |
|
9 |
Running as slave |
The database is the secondary slave in the cluster. All changes on master are asynchronously replicated to this node. |
|
10 |
Running alone |
The database does not replicate its changes to other nodes. |
Load balancer (OID .1.3.6.1.4.1.318.1.2.2.1.3.0)
|
Response |
Name |
Description |
|---|---|---|
|
1 |
Unknown |
Load Balancer status is unknown. Check Webmin and if the problem persists, contact Technical Support. |
|
2 |
Stopped |
Load Balancer stopped. Restart the Data Center Operation server. If the problem persists, contact Technical Support. |
|
3 |
Running |
Normal status |
|
4 |
Running but missing nodes |
High availability is lost. The Data Center Operation Load Balancer is running but one or more |
General and essential services (OID .1.3.6.1.4.1.318.1.2.2.1.4.0)
|
Response |
Name |
Description |
|---|---|---|
|
1 |
Unknown |
Unknown status. Check Webmin and if the problem persists, contact Technical Support. |
|
2 |
Stopped |
Essential services are not running on the Data Center Operation server. Reboot the node and monitor the status page in Webmin. If the problem persists, contact Technical Support. |
|
3 |
Running |
Normal status |
|
4 |
Time is out of sync between cluster nodes |
The time difference between the Data Center Operation slave and the master node is too big. Correct the time on the slave to match the time on the master. Consider using an NTP server. If the problem persists, contact Technical Support. |
| 5 | Backup failed | The last backup that was attempted on this server was not successful. Ensure the system can write to the location specified as backup location. This is particularly relevant for network attached storage. |
ETL (OID .1.3.6.1.4.1.318.1.2.2.1.5.0)
|
Response |
Name |
Description |
|---|---|---|
|
1 |
Unknown |
Unknown status. Check Webmin and if the problem persists, contact Technical Support. |
|
2 |
OK |
Normal status |
|
3 |
Error |
ETL experienced an error while running the transformation. Monitor the status page in Webmin. The scheduler will try to run the transformation again as scheduled. |
|
4 |
Paused |
ETL is paused on the Data Center Operation server. Monitor the ETL status page in Webmin. Try to start the job if needed using the management button. |
| 5 | Stopped | For future use |
0 comments
Please sign in to leave a comment.