Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

opCharts enables you to schedule NMIS outages and add multiple Nodes, Interfaces or InterfacesElements, or a combination of both, to a single outage event. You can also schedule a one-time outage or a recurring event outage for the required Node Nodes or Interface Elements on the opCharts Scheduled Outages page. 

This document describes how you can schedule an outage a Node Outage using opCharts 4 and above, and Element Outages with Interfaces from opCharts 4.5.9 and above, and Element Outages with Other elements from opCharts 4.5.10 and above.

Creating a Scheduled Outage

  1. To schedule an outage on the opCharts page, from the menu, click Views > Scheduled Outages
    Image RemovedImage Added
  2. On the Outages page that opens, click New Outage
    Image RemovedImage Added
  3. Add a Description for the outage.
  4. Specify a Change ID for easy identification of the outage event.
  5. You can schedule a one-time outage or a recurring event under Frequency.

    Note

    By default, NMIS collects the performance data during every outage event. You may choose to discard it by selecting the Discard Performance Data check box. 


  6. Under Outage Window, specify the Start and End time for the outage.

    Info

    Click the Common Time Formats link to know more about the time formats supported by Opmantek applications for parsing the start and end times.

    Image RemovedImage Added

  7. Under Node/Element Selection, choose the Selector Type - the type of device this outage is being configured for - either Node or Element.
    • In case of a Node, choose the Node Property to select Nodes by.
      • Select or enter the required Values. You can enter multiple Node Values (separated by commas) for the Property chosen.
    • How to add a custom node property ?
      In opCharts Outages, Custom properties can be added in Node property section to create outages for nodes.
      To add a custom property, Please editing opCharts_node_selector_sections.json and add in any new property of catchall.
      For example :-  Addition of Node Model in opCharts_node_selector_sections.json 

      {
      "name" : "catchall.data.model",
      "label" : "Node Model"
      }

    • In case of an Element, first search for and select the Nodethe Node which the element(s) are on.
    • From For Element Section Type you can either select Interface or Other 
      • For Interface :
        • From Choose how you want to search for elements on the Interface / Regex drop-down list, select the elements - select  Interface or Interface Regex. 
          • In case of Interface, select the required element Interfaces(s) from drop-down (exexample: Vlan1)
          • In case of Interface Regex, enter a valid regex pattern (exexamples: vlan* or ^Vlan.*?$)
      • For Other :
        • From the Match Type drop-down list, select either String or Regex
          • In case of stringString, Enter enter the valid string for that selected node under the Element in Value
          • In case of Regex, enter a valid regex pattern (exexamples: vlan* or ^Vlan.*?$)Image Removed
            Image Added
  1. Click the Add new selector button to add another Node or Element to the same Scheduled Outage. 
  2. Click Save and Back to finish scheduling the outage.

...

Configuration Details :- NMIS Configuration (purge_outages_after)

Section

Name

Original Value


Possible Values

Description

expirationpurge_outages_after86400
-past non-recurring outages

Integration with NMIS and opEvents

When a Scheduled Outage commences, on the next node collect cycle a "Planned Outage Open" event is created in NMIS and opEvents. Similarly when the scheduled outage is completed a "Planned Outage Closed" event is created in NMIS and opEvents.

For events that occur that relate to the impacted node/element during the defined scheduled outage window, the "event.planned_outage" property in opEvents will be set to true.

Further information about this property and others can be found here: opEvents Normalised Event Properties