![]() ![]() Stop monitoring $Dsv and remove the domain from the Objectives DB: MONITOR DISK $Dsv, delete 4. ![]() Start monitoring $Tools (all Disk domains are automatically monitored by default, so adding them to the ObjectivesDB is not mandatory): MONITOR DISK $Tools 3. Display the currently configured domains in the Objectives DB of the local node: MONITOR DISK Disk \Chicago On - $Data On - $Dsv On - $System 2. Display currently configured objectives in the Objectives DB of the local node: RANK CPU Cpu \Chicago Busy for example, Busy, Queue, Disp, and so on. Set a global objective on the CPU BUSY attribute: RANK CPU, BUSY for CPU 01, generate a critical EMS event when the objective is not met, and repeat the event at every sampling that the condition persists: RANK CPU 01, BUSY ASAP migration guide for NSX and OMF users A–2ĩ. Display currently configured objectives in the Objectives DB of the local node: RANK CPU 7. ![]() Display currently configured domains in the Objectives DB of a remote node: MONITOR CPU \NEWYORK Cpu \NewYork On – 00 On - 01 On - 02 On - 03 6. Commit the changes so you can see results at the next sample: COMMIT 5. Review the list of CPU domains: MONITOR CPU Cpu \Chicago On - 00 Off – 01 4. Stop monitoring CPU 1, but keep the domain in the Objectives DB: MONITOR CPU 1, OFF 3. Display currently configured domains in the Objectives DB of the local node (all CPU domains are automatically monitored by default, so adding them to the Objectives DB is not mandatory): MONITOR CPU Cpu \Chicago On - 00 On - 01 2. Check if the Collector and Monitors are running correctly: STATUS COLLECT STATUS \* LOG LOG \NEWYORK monitoring CPU 1. Start the ASAP Monitor on the third node: SET DISK ON, PARAM “RATE 5” SET TAPE ON SET SPOOLER OFF SET FILE OFF START \HOUSTON 6. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |