Posts Tagged “networking”

There could be numerous reasons to create a fake Ethernet interface on a Linux server though I have heard that people might do so to get around licensing of software that is tied to the MAC address of a specific Ethernet port. You really just enable a dummy Ethernet interface and assign the MAC address to it which is explain in more detail below. The easiest way to do this is to simply assign a MAC address to an Ethernet interface you are not using on your server where the drivers have already been installed automatically. If you do not have a spare Ethernet interface then the instructions below will assist you to accomplish your goal.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , , , , , , , ,

Comments 1 Comment »

I was troubleshooting a Windows XP computer that had been brought in to my friends computer shop this afternoon and noticed something odd going on with the Windows Task Manager. The computer had multiple issues including various viruses, Norton Internet Security installed, hadn’t been upgraded or patched for over a year, and numerous other items going wrong. I will say that Norton Internet Security is probably the worst antivirus software I have ever come across because not only does it take over every aspect of your computer but on top of that it doesn’t even save your computer from getting infected by viruses. After getting the computer in working shape by removing Norton Internet Security and beginning the installation of Windows XP patches I launched Windows Task Manager to view something and when I did the list of running applications displayed but I could not click other tabs that normally appear at the top of the Task Manager. Below I display an image of what the Windows Task Manager looked like and how I easily resolved the issue.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , , , , , , , , ,

Comments 16 Comments »

With the release of Backtrack 4 final a few days ago I decided to make a post on installing backtrack in VMware. There are many ways to run backtrack including a hard disk install, a USB boot install and of course as a live cd. My preferred method is with VMware so I decided to document my steps in case there is any one who would like to install in this way.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , , ,

Comments 82 Comments »

If you use pastebin as much as I do then you will think this tool is as cool as I do. Pastebin is a online site which allows users to copy and paste snippets of code in order for share them with other people and get feed back.

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , ,

Comments 1 Comment »

--- GW IMAGE NOT DISPLAYED --- Configuring Services

Copyright 2006 GroundWork Open Source, Inc. (“GroundWork”).All rights reserved. Use is subject to GroundWork commercial license.

Contents

Configuring Services

--- GW IMAGE NOT DISPLAYED --- How Do I Define a New Service?


Step 1 will cover how to set up a new Service. When naming the Service you should use a standard naming convention to make it easier to tell what is going on later (e.g. ssh_disk_/). You will also need to select a Service Template to be associated with the new Service. A Service Template is useful when you have common attributes for multiple Services. A Service Template incorporates multiple Service detail directives and Service Check definitions. Then in Step 2, you will have the opportunity in the Service Detail screen to use (Set Inheritance) the selected template default attributes or you can uncheck each attribute which enables you to set individual attributes for the new Service and not inherit the default setting from the selected template. Next, you can continue with Step 3 to configure the Service Check.

See Chapter 5 Advanced Configuration – Configuring Profiles to learn about grouping Services into Service Profiles.

Step 1 – New Service

  1. Select Services from the Configuration menu options.
  2. Select New service.
  3. In the New Service screen, enter the properties (see Table 5.3.1a. below).
  4. Select Add to go to the Manage Service screen.

    Figure 5.3.1a. New Service

    --- GW IMAGE NOT DISPLAYED ---

    Table 5.3.1a. New Service

    Name [Required] Name of the new Service. Example: check-disk-sda1. Note: Monarch and GroundWork Monitor do not support backslashes in Host and Service names.
    Service Template [Required] This option sets the default template for the Service name definitions. Example: generic-service.

Step 2 – Service Detail

The Manage Service screen incorporates five tabs including Service Detail, Service Check, Service Dependencies, Services Profiles, Service Externals (optional), and Apply Hosts. Each of these tabs will be covered within this chapter.

  1. In the Service Detail tab, enter the properties (see Table 5.3.1b. below).
  2. Select Save to add the new Service. You will be prompted in the next screen that the Service has been save. Select Close. Delete removes the current Service, Rename is used to change the name of the current Service, and Close is used to exit the current Service without saving.

    Figure 5.3.1b. Service Detail

    --- GW IMAGE NOT DISPLAYED ---

    Table 5.3.1b. Service Detail

    Name Name of the Service entered on the previous screen.
    Service Template [Required] The Service Template most suitable for this Service, selected on the previous screen. You may re-select it here.
    Inherit All Values from Template [Optional] Checked sets all directive to inherit values from the selected template. Unchecked, directives below will override template values.
    Is Volatile [Required] This directive is used to denote whether the Service is Volatile. Services are normally not volatile. Unchecked Service is not volatile; Checked Service is volatile.
    Check Period [Required] This directive is used to specify the sort name of the time period during which active checks of this Service can be made.
    Max Check Attempts [Required] This directive is used to define the number of time that Nagios will retry the Service check command if it returns any state other than an OK state. Setting this value to 1 will cause Nagios to generate an alert without retrying the Service check again.
    Normal Check Interval [Required] This directive is used to define the number of time units to wait before scheduling the next regular check of the Service. Regular checks are those that occur when the Service is in an OK state or when the Service is in a non-OK state, but has already been rechecked max_attempts number of times. Unless the interval_length directive has been changed from the default value of 60, this number will mean minutes.
    Retry Check Interval [Required] This directive is used to define the number of time units to wait before scheduling a re-check of the Service. Services are rescheduled at the retry interval when they have changed to a non-OK state. Once the Service has been retried max_attempts times without a change in its status, it will revert to being scheduled at its normal rate as defined by the check_interval value. Unless you’ve changed the interval_length directive from the default value of 60, this number will mean minutes.
    Active Checks Enabled [Optional] This directive is used to determine whether or not active checks of this Service are enabled. Unchecked Disable Active Service Checks, Checked Enable Active Service Checks.
    Passive Checks Enabled Optional] This directive is use to determine whether or not passive checks of this Service are enabled. Unchecked Disable Passive Service Checks, Checked Enable Passive Service Checks.
    Parallelize Check [Optional] This directive is used to determine whether or not the Service check can be parallelized. By default, all Service checks are parallelized. Disabling parallel checks of Services can result in serious performance problems. Unchecked Service check cannot be parallelized (use with caution), Checked Service check can be parallelized.
    Obsess Over Service This value determines whether or not Nagios will obsess over Service checks results and run the obsessive compulsive Service processor command you define. This option is useful for performing distributed monitoring. If you’re not doing distributed monitoring, don’t enable this option.
    Check Freshness [Optional] This directive is used to determine whether or not freshness checks are enabled for this Service. Unchecked disable freshness checks, Checked enable freshness checks.
    Freshness Threshold [Optional] This directive is used to specify the freshness threshold (in seconds) for this Service. If you set this directive to a value of 0, Nagios will determine a freshness threshold to use automatically.
    Notifications Enabled [Optional] This directive is used to determine whether or not notifications for this Service are enabled. Unchecked Disable Service Notifications, Checked Enable Service Notifications.
    Notification Interval [Required] This directive is used to define the number of time units to wait before re-notifying a contact that this Service is still in a non-OK state. Unless you’ve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, Nagios will not re-notify contacts about problems for this Service – only one problem notification will be sent out, unless there has been a state change.
    Notification Period [Required] This directive is used to specify the short name of the time period during which notifications of events for this Service can be sent out to contacts. No Service Notifications will be sent out during times which are not covered by the time period.
    Notification Options [Required] This directive is used to determine when Notifications for the Service should be sent out. Valid options are a combination of one or more of the following: If checked Unknown send notifications on an UNKNOWN state, Critical send notification on a CRITICAL state, Warning = send notifications on a WARNING state, Recovery send notifications on recoveries in OK state. If you specify None as an option, no Service notifications will be sent out.
    Event Handler Enabled [Optional] This directive is used to determine whether or not the event handler for this Service is enabled. Unchecked Disables Service Event Handler, Checked Enables Service Event Handler.
    Event Handler [Optional] This directive is used to specify the short name of the command that should be run whenever a change in the state of the Host is detected (i.e. whenever it goes down or recovers). The maximum amount of time that the event handler command can run is controlled by the event_handler_timeout option.
    Flap Detection Enabled [Optional] This directive is used to determine whether or not flap detection is enabled for this Service. Unchecked Disable Service Flap Detection, checked Enable Service Flap Detection.
    Low Flap Threshold [Optional] This directive is used to specify the low state change threshold used in flap detection for this Service. If you set this directive to a value of 0, the program-wide value specified by the low_service_flap_threshold directive will be used.
    High Flap Threshold [Optional] This directive is used to specify the high state change threshold used in flap detection for this Service. If you set this directive to a value of 0, the program-wide value specified by the high_service_flap_threshold directive will be used.
    Process Perf Data [Optional] This directive is used to determine whether or not the processing of performance data is enabled for Services using this template. Uncheckeddisables performance data processing, Checked enables performance data processing.
    Retain status information [Optional] This directive is used to determine whether or not status-related information about the Service is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Unchecked disables status information retention, Checked enables status information retention.
    Retain Non-status Information [Optional] This directive is used to determine whether or not non-status information about the Service is retained across program restarts. This is only useful if you have enable state retention using the retain_state_information directive. Unchecked disables non-status information retention, Checked enables non-status information retention.
    Contact Groups Select the contact groups to be notified for this Service.
    Extended Info Template [Optional] Defines extended Service information for this Service name. The template controls the icon and URL link as seen in Nagios for Hosts assigned this Service definition.)
    Escalation Tree [Optional] Select an escalation tree appropriate for this Service. To avoid amplified notification (i.e. multiple notifications for the same event), a Service Escalation assigned to a Service should not be assigned to the Host or the Host Group.

Step 3 – Service Check

Here we will configure the Service Check for the new Service. You can create as many Services as you like. If you want to use some of the other options on the plugins, you’ll need to create new commands that set those options, and use them to create your Services. GroundWork Monitor comes loaded with many of the commonly used Services already preconfigured.

  1. Select the Service Check tab.
  2. De-select the Inherit check from template box which enables you to define a specific Check Command for this Service. Select the command (e.g. check_by_ssh_disk) from the drop-down list. GroundWork Monitor comes with a lot of standard commands already defined for you.
  3. Next, the ARG1!ARG2!ARG3 in the command line should be filled in to reflect the arguments to pass to the plugin. To run an example, use 20%!10%!/ to check the / partition and give a warning when less than 20% is free, and a critical alert when less than 10% is free.
  4. You can then test the Service against any Host from within this Service Check screen.
  5. Select Save to save the Service Check with the new Service.

    Figure 5.3.1c. Service Check

    --- GW IMAGES NOT DISPLAYED ---

OTHER SERVICE MANANGEMENT OPTIONS

Service Dependencies

Service Dependencies are optional and allow you to suppress Notifications and active checks of Services based on the status of one or more other Services. After defining the Service Detail and the Service Check attributes, you can select the Service Dependencies to add or remove service dependencies.

  1. Select Hosts from the Configuration menu options.
  2. Select the dependent host by using Search host. Or expand the Hosts navigation tree.
  3. Select a Host Group to expand the list of Hosts.
  4. Select the dependent Host to expand the navigation tree.
  5. From the navigation tree select a Service to get bring up the Manage Host Service screen.
  6. Select the Service Dependencies tab.
  7. Select the desired Dependency and then choose the Parent Host from the list.
  8. Click Add Dependency to create the new Service Dependency.

    Figure 5.3.1d. Service Dependencies through Manage Host Service

    --- GW IMAGES NOT DISPLAYED ---

The template you select defines a Parent Service relationship on a given Host. Monarch will create a Service Dependency relationship on a Host assigned to this Service name. To define a dependency from a Service running on a different Host use Hosts>Modify>Services>Service Dependency and select the Parent Host. Be careful to ensure that the Parent Service is assigned to the Parent Host definition and is included in the relevant Service Profiles.

To add a dependency, select from the dependency list and after the screen refreshes, choose the appropriate Host, or select same Host if the dependency is for Services on the same Host.

To configure a new, copy, or modify a Service Dependency Template go to Configuration>Services>Service Dependency Template where you can specify the Service, and specific execution failure criteria and notification failure criteria. These templates will then show up in the Manage Service, Service Dependencies screen. See Service Dependencies in this chapter.

Figure 5.3.1e. Service Dependencies

--- GW IMAGES NOT DISPLAYED ---

Service Profiles

A Service Profile is a collection of multiple Services. Once you have a Service Profile you can combine this with a Host Template and create a Host Profile. With GroundWork Monitor Professional, you get a preloaded set of Service Checks for multiple types of servers, devices, etc. that you can use out of the box. Service Profiles encapsulate a set of standard Services with Plugins and best practices that can be applied toward monitoring specific devices or protocols. The advantages of using a Service Profile is that it is pre-integrated. Using profiles, you can quickly configure GroundWork Monitor Professional to monitor groups of devices the same way. To define a Service Profile see Section 5 Configuration, Chapter 5 Advanced Configuration – Configuring Profiles.

  1. Here we will add or remove Service Profiles using this Service. Adding or removing a Service Profile here has no effect on the Service Profile’s member Hosts until the apply tab is used on the Service Profile (or Host Profile), or the Profile is applied on the individual Hosts.
  2. Select Save to save the selected Service Profiles using this Service.

    Figure 5.3.1f. Service Profiles

    --- GW IMAGES NOT DISPLAYED ---

Service Externals

The Externals feature enables you to add your own configuration data that is not related to Nagios but can be useful when integrating other tools. When Externals are enabled, you can add this data to Host and Service Profiles, which can then be applied to instantiated Host and Service definitions. You can then execute the Run Externals command, which will call a user written program in MonarchExternals.pm. The user program can process the Externals data associated with the Host and Service definitions in Monarch. For example, the Externals data can be used to generate a configuration update for another monitoring tool based on Monarch changes. This is an advanced feature that requires some knowledge of Perl to modify MonarchExternals.pm.

  1. To enable Externals within GroundWork Monitor Professional, select Control from the Configuration tab, then Setup and click the Enable Externals box, and Save. You are then able to define, add, and execute Externals using the Services, Profiles, and Hosts configuration tabs.

    Figure 5.3.1g. Enabling Externals

    --- GW IMAGES NOT DISPLAYED ---

  2. To create a Service External, select Services from the Configuration tab options.
  3. Select Service Externals.
  4. Select New service.
  5. Enter a Name, and Details for the Service External.
  6. Select Add and Continue, you will then see the new external listed under Modify.

    Figure 5.3.1h. Defining Service Externals

    --- GW IMAGES NOT DISPLAYED ---

  7. You can then add Service and Host Externals within the Services, Profiles, and Host configuration options.

    Figure 5.3.1i. Adding Externals

    --- GW IMAGES NOT DISPLAYED ---

  8. To execute the externals select Control from the Configuration tab options, and Run Externals, which will execute your code in MonarchExternals.pm.

    Figure 5.3.1j. Executing Code in MonarchExternals.pm

    --- GW IMAGES NOT DISPLAYED ---

Apply Hosts

In the Apply Hosts tab you will need to select the options you want to apply to the listed Hosts. The listed Hosts are Hosts that have this Service assigned to it within the Host configuration tab. The options for applying Hosts are detailed here: >

  1. Apply Service Check – Check this if you want to apply the Service Check defined in the Service Check tab to this Host.
  2. Apply Contact Groups – Check this if you want to apply the Service Contact properties to the listed Hosts.
  3. Apply Service Extended Info – Check this if you want to apply the Service Extended Info properties to the listed Hosts.
  4. Apply Service Escalation – Check this if you want to apply the Service Escalation properties to the listed Hosts.
  5. Apply Dependencies – Check this if you want to apply the Service Dependencies to the listed Hosts.
  6. Replace existing Service properties (force inheritance) – This refers to the properties selected on the Service Detail page and forces the inheritance of the Service Template.
  7. Merge existing Services properties (preserve overrides) – This refers to the properties selected on the Service Detail page and preserves the indicated check box overrides for the listed Hosts.

    Figure 5.3.1j. Apply Hosts

    --- GW IMAGES NOT DISPLAYED ---

Configuring Services

--- GW IMAGE NOT DISPLAYED --- How Do I Clone a Service?


Clone Service

  1. Select Services from the Configuration menu options.
  2. Select Clone Service.
  3. In the Clone Service screen, choose a Service to copy from the Select Service drop-down box, all available Services will be listed.
  4. Click Next to continue.
  5. Enter a new name for the cloned Service.
  6. Select Apply to Profiles to maintain the original Service Profile association for the new cloned Service. You will need to Commit the new Service.

    Figure 5.3.2a. Clone Service

    --- GW IMAGE NOT DISPLAYED ---

Configuring Services

--- GW IMAGE NOT DISPLAYED --- How Do I Create a New Service Template?


Step 1 – New Service Template

  1. Select Services from the Configuration menu options.
  2. Select Service Templates.
  3. Select New.
  4. In the New Service Template screen, enter the properties (see Table 5.3.2a. below).
  5. Select Add to add the template name and go to the next screen to define the template.

    Figure 5.3.3a. New Service Template

    --- GW IMAGES NOT DISPLAYED ---

    Table 5.3.3a. New Service Template

    Name Name of the new Service.

Step 2 – Manage Service Template – Service Detail

  1. In the Service Detail tab, enter the properties (see Table 5.3.3b. below).
  2. Select Save to save and add the new Service Template. Delete removes the current Service Template, Rename is used to change the name of the current Service Template, and Close is used to exit the current Service Template without saving. IMPORTANT NOTE: Each tab has its own save command. You need to select Save between each tab or you will lose your entries.

    Figure 5.3.3b. Service Detail

    --- GW IMAGES NOT DISPLAYED ---

    Table 5.3.3b. Service Detail

    Use [Required] Select the Service Template most suitable for this Service. Changing directives within this screen will override the template values.
    Is Volatile This directive is used to denote whether the Service is Volatile. Services are normally not volatile. Unchecked Service is not volatile; Checked Service is volatile.
    Check Period [Required] This directive is used to specify the sort name of the time period during which active checks of this Service can be made.
    Max Check Attempts [Required] This directive is used to define the number of time that Nagios will retry the Service check command if it returns any state other than an OK state. Setting this value to 1 will cause Nagios to generate an alert without retrying the Service check again.
    Normal Check Interval [Required] This directive is used to define the number of time units to wait before scheduling the next regular check of the Service. Regular checks are those that occur when the Service is in an OK state or when the Service is in a non-OK state, but has already been rechecked max_attempts number of times. Unless the interval_length directive has been changed from the default value of 60, this number will mean minutes.
    Retry Check Interval [Required] This directive is used to define the number of time units to wait before scheduling a re-check of the Service. Services are rescheduled at the retry interval when they have changed to a non-OK state. Once the Service has been retried max_attempts times without a change in its status, it will revert to being scheduled at its normal rate as defined by the check_interval value. Unless you’ve changed the interval_length directive from the default value of 60, this number will mean minutes.
    Active Checks Enabled [Optional] This directive is used to determine whether or not active checks of this Service are enabled. Unchecked Disables Active Service Checks, Checked Enables Active Service Checks.
    Passive Checks Enabled [Optional] This directive is use to determine whether or not passive checks of this Service are enabled. Unchecked Disables Passive Service Checks, Checked Enables Passive Service Checks.
    Parallelize Check [Optional] This directive is used to determine whether or not the Service check can be parallelized. By default, all Service checks are parallelized. Disabling parallel checks of Services can result in serious performance problems. Unchecked Service check cannot be parallelized (use with caution), Checked Service check can be parallelized.
    Obsess Over Service This value determines whether or not Nagios will obsess over Service checks results and run the obsessive compulsive Service processor command you define. This option is useful for performing distributed monitoring. If you’re not doing distributed monitoring, don’t enable this option.
    Check Freshness [Optional] This directive is used to determine whether or not freshness checks are enabled for this Service. Unchecked disables freshness checks, Checked enable freshness checks.
    Freshness Threshold [Optional] This directive is used to specify the freshness threshold (in seconds) for this Service. If you set this directive to a value of 0, Nagios will determine a freshness threshold to use automatically.
    Notifications Enabled [Optional] This directive is used to determine whether or not Notifications for this Service are enabled. Unchecked Disables Service Notifications, Checked Enables Service Notifications.
    Notification Interval [Required] This directive is used to define the number of time units to wait before re-notifying a contact that this Service is still in a non-OK state. Unless you’ve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, Nagios will not re-notify contacts about problems for this Service – only one problem notification will be sent out, unless there has been a state change.
    Notification Period [Required] This directive is used to specify the short name of the time period during which notifications of events for this Service can be sent out to contacts. No Service Notifications will be sent out during times which is not covered by the time period.
    Notification Options [Required] This directive is used to determine when notifications for the Service should be sent out. Valid options are a combination of one or more of the following: If checked Unknown send notifications on an UNKNOWN state, Critical send notification on a CRITICAL state, Warning send notifications on a WARNING state, Recovery send notifications on recoveries in OK state. If you specify None as an option, no Service notifications will be sent out.
    Event Handler Enabled [Optional] This directive is used to determine whether or not the event handler for this Service is enabled. Unchecked Disables Service Event Handler, Checked Enables Service Event Handler.
    Event Handler [Optional] This directive is used to specify the short name of the command that should be run whenever a change in the state of the Host is detected (i.e. whenever it goes down or recovers). The maximum amount of time that the event handler command can run is controlled by the event_handler_timeout option.
    Flap detection enabled [Optional] This directive is used to determine whether or not flap detection is enabled for this Service. Unchecked Disable Service Flap Detection, Checked Enable Service Flap Detection.
    Low Flap Threshold [Optional] This directive is used to specify the low state change threshold used in flap detection for this Service. If you set this directive to a value of 0, the program-wide value specified by the low_service_flap_threshold directive will be used.
    High Flap Threshold [Optional] This directive is used to specify the high state change threshold used in flap detection for this Service. If you set this directive to a value of 0, the program-wide value specified by the high_service_flap_threshold directive will be used.
    Process Perf Data [Optional] This directive is used to determine whether or not the processing of performance data is enabled for Services using this template. Unchecked disables performance data processing, Checked enables performance data processing.
    Retain status information [Optional] This directive is used to determine whether or not status-related information about the Service is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Unchecked disable status information retention, Checked enable status information retention.
    Retain Non-status Information [Optional] This directive is used to determine whether or not non-status information about the Service is retained across program restarts. This is only useful if you have enable state retention using the retain_state_information directive. Unchecked disables non-status information retention, Checked enables non-status information retention.
    Contact Groups Select the contact groups to be notified for this Service.

Step 3 – Service Check

  1. Next, select the Service Check tab to define a Service Check for this template.
  2. In the Service Check tab, enter the properties (see Table 5.3.3c. below).
  3. Select Save to save the check command. A screen will be displayed confirming your save. Select Close.

    Figure 5.3.3c. Service Check

    --- GW IMAGE NOT DISPLAYED ---

    Table 5.3.3c. Service Check

    Check Command This is the command that Nagios will run in order to check the status of the Service. There are three command formats that can be used; the Command, the Command with arguments, and a command line.
    Command Definition The command definition will be displayed here after selection of the check command.
    Usage The command usage parameters.
    Command Line If the check command requires arguments this is where you would enter the check command with command arguments separated by a ! character. Example: check_disk!/dev/sda1.
    Test Enter a Host and arguments for the command line. When you click the “Test” button this parses through the command definition, performs the macro substitutions, inserts the Hostname from the Host box, puts the resulting command into a shell command line and executes, returning the results of the execution in the box to the right.

Configuring Services

--- GW IMAGE NOT DISPLAYED --- How Do I Configure a New Service Dependency Template?


Step 1 – New Service Template

  1. Select Services from the Configuration menu options.
  2. Select Service Dependency Templates.
  3. Select New.
  4. In the Service Dependency Template screen, enter the properties (see Table 5.3.4a. below).
  5. Select Save to save the Service Dependency Template. Delete removes the current template, and Rename is used to change the name of the current template. You will be notified on the next screen that the Service Dependency Template has been saved, select Continue.

    Figure 5.3.4a. Service Dependency Template

    --- GW IMAGE NOT DISPLAYED ---

    Table 5.3.4a. Service Dependency Template

    Name [Required] Name of the Service Dependency Template.
    Service Name [Required] This is the Parent Service name.
    Execution failure criteria [Optional] This directive is used to specify the criteria that determine when the dependent Service should not be executed. If the Service that is being depended upon is in one of the failure states we specify, the dependent Service will not be executed. Valid options are a combination of one or more of the following: Okay checked fail on an OK state, Warning checked fail on a WARNING state, Unknown checked fail on an UNKNOWN state, and Critical checked fail on a CRITICAL state. If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent Service will always be executed. Example: If you specify o,c,u in this field, the dependent Service will not be executed if the Service that’s being depended upon is in either an OK, a CRITICAL, or an UNKNOWN state.)
    Notification failure criteria [Optional] This directive is used to define the criteria that determine when notifications for the dependent Service should not be sent out. If the Service that is being depended upon is in one of the failure states we specify, notifications for the dependent Service will not be sent to contacts. Valid options are a combination of one or more of the following: Okay checked fail on an OK state, Warning checked fail on a WARNING state, Unknown checked fail on an UNKNOWN state, and Critical checked fail on a CRITICAL state. If you specify n (none) as an option, the notification dependency will never fail and notifications for the dependent Service will always be sent out. Example: If you specify w in this field, the notifications for the dependent Service will not be sent out if the Service that is being depended upon is in a WARNING state.)

Configuring Services

--- GW IMAGE NOT DISPLAYED --- How Do I Create an Extended Service Info Template?


Step 1 – Extended Service Info Template

  1. Select Services from the Configuration menu options.
  2. Select Extended Service Info Templates.
  3. Select New.
  4. In the Extended Service Info Template screen, enter the properties (see Table 5.3.5a. below).
  5. Select Add to add the new Extended Service Info Template.
  6. You will be prompted that the template has been saved. Select Continue.

    Figure 5.3.5a. Extended Service Info Template

    --- GW IMAGE NOT DISPLAYED ---

    Table 5.3.5a. Extended Service Info Template

    Name [Required] Name of the Extended Service Info Template.
    Notes URL [Optional] Define a URL that can be used to provide additional information to other support staff about the Host, such as emergency contact methods.
    Icon Image [Optional] This variable is used to define the name of an image to be associated with this Host. This image will be displayed in the status and extended information CGIs.
    Icon Image Alt [Optional] This variable is used to define an optional string that is used in the Alt tag of the image specified by the Icon Image.

Configuring Services

--- GW IMAGE NOT DISPLAYED --- How Do I Create Service Groups?


Step 1 – Service Group

  1. Select Services from the Configuration menu options.
  2. Select Service Groups.
  3. Select New.
  4. In the Service Group screen, enter the properties (see Table 5.3.6a. below).
  5. Select Add to go to the Service Group screen.
  6. Select the Host drop-down box to select a Host. Available Services will be listed.
  7. Select a Service to add and click Add Service(s). The Host and Service columns above will displayed your selections. To remove a selected Service click the X corresponding to the line to be deleted.
  8. Select the Service drop-down box to select a Service, available Hosts will be listed.
  9. Select a Host to add and click Add Host(s). The Host and Service columns above will display your selections. To remove a selected Host click the X corresponding to the line to be deleted.
  10. Select Save to save the Service Group. Delete removes the current Service Group, and Rename is used to change the name of the current Service Group. You will be notified on the next screen that the Service Groups has been updated.

    Figure 5.3.6a. Service Groups

    --- GW IMAGE NOT DISPLAYED ---

    Table 5.3.6a. Service Groups

    Name [Required] Name of the Service Group. Example: dbservices
    Alias [Required] This directive is is used to define a longer name or description used to identify the Service Group. It is provided in order to allow you to more easily identify a particular Service Group. Example: Database Services
    Host/Service [Required] This is a list of the descriptions of Services (and the names of their corresponding Hosts) that should be included in this group.
DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , ,

Comments No Comments »