How to delete a config Item in OTRS ?
How to remove a policy from Management Station of OVO ?
Here are the steps to remove a particular policy on a node from management station of OVO.
1. First log onto your management station.
2. On Management station, run the following command.
ovpolicy -remove –polname “Policy Name” -host “hostname”
Example:
ovpolicy -remove -polname “My_Monitor_Policy” -host myHostA
Here is how the sample output looks
* Remove all policies for the specified selection on host
‘myHostA’.
At this point the policy My_Monitor_Policy is removed on node “myHostA”
You can check the policy in remote host by following
ovpolicy -list -host myHostA
You would not see the policy My_Monitor_Policy is listed anymore.
How to disable a policy on a node from Management station of OVO ?
Here are the steps to disable a particular policy on a node from management station of OVO.
1. First log onto your management station.
2. On Management station, run the following command.
ovpolicy -disable –polname “Policy Name” -host “hostname”
Example:
ovpolicy -disable -polname “My_Monitor_Policy” -host myHostA
Here is how the sample output looks
* Disable all policies for the specified selection on host
‘myHostA’.
At this point the policy My_Monitor_Policy is disabled on node “myHostA”
How to disable ping a node in OVO ?
Here are the steps to disable ping a node in OVO.
1. Open the node.
2. Click Edit. Go to Management
3. Change the “Polling” to “No Polling”
4.save it.
Now that particular Node won’t be pinged any more.
What are the policies deployed on a OVOu node ?
To know the policies deployed on a specific node, run the following command on that node
opctemplate -list
How to check status of licenses of all installed & Licensed components of OVO unix ?
Run the following command.
ovlicense -status -product HPOM
To create a report on license, run the following commandovlicense -report -product HPOM
How to Create a Customer Company in OTRS
The description below uses the OTRS version 3.1.1.
Here are the steps to add a new customer company in OTRS.
- 1. Go to “Admin” tab.
- 2. Under “Customer Management” section, select “Customer Companies”. It open up a new screen.
- 3.Under “Customer Company Management” Click “Add Customer Company”.
- 4. Enter all the info such as below.
– CustomerID : 100
-Company: Joe Smith Company
- 5. Click “Submit”.
A new customer company is created.
How can I change the no of attempts before an issue is emailed in Icinga ?
The description below uses the Icinga version 1.6.1.
Here are the steps.
- 1. Go to /usr/local/icinga/etc/objects/templates.cfg
- 2.Search for the template that you are working on. Say you are working on a template called name = linux-server
- 3.Change the parameter called “max_check_attempts” to 3 ( Here you want to change to 3 attempts, before email is sent. Default Value is 10 )
- 4. Restart the Icinga by running the command: /etc/init.d/icinga restart
How to create a new config Item in OTRS ?
The description below uses the OTRS version 3.1.1.
Here are the steps to create a new config Item in OTRS.
- 1. Go to “Admin” tab.
- 2. Under “Ticket Settings” section, select “General Catalog”. It open up a new screen.
- 3. Under “General Catalog Management” , from drop down select “ITSM::ConfigItem::Class” and Click “+ for Add Catalog Item”.
- 4. Enter all the info ( Remember to enter permission = itsm-configitem ) and Click “Submit”.
- 5. Now you can see the new “CI” if you go to “CMDB” tab from top.
A new “Config Item” is created. You can verify the “Config Item” as it would be displayed under “CMDB” tab . Go to the tab “CMDB” and click on “OverView”. You will see the new “Config Item” that you created.
How to create a SLA in OTRS ?
The description below uses the OTRS version 3.1.1.
Here are the steps to create a new SLA in OTRS.
- 1. Go to “Admin” tab.
- 2. Under “Ticket Settings” section, select “Service Level Agreements”. It open up a new screen.
- 3. Click “Add SLA” and add all the information.
- 4. “save” it.
A new SLA is created. You can verify the SLA as it would be displayed under List of SLAs.