ONES 3.1.1
Release
  • Open Networking Enterprise Suite (ONES)
    • ONES Application
      • ONES Telemetry Collector(s) and Visibility
      • ONES Time Scale Metric Calculation
      • ONES Rule Engine
      • ONES Orchestration
      • ONE DL
      • ONES AVIZ Support
      • ONES Security
      • ONES Multisite
    • Licensing
  • What's new?
  • Getting Started
    • Supported Switch Platforms and NOS
    • Scalability
    • Subscription
    • ONES Installation
      • Installation Pre-requisites
      • Download ONES Package
      • Installing ONES Application
      • Upgrade ONES Application
      • ONE-DL cloud Deployment
      • Installing ONES Agents 3.1.1
        • ONES Telemetry Agent Installation
        • ONES Server Agent Installation
        • ONES Orchestration Agent Installation
        • Agent Less Telemetry
          • Cumulus(NVUE API)
          • Arista EOS (eAPI)
          • CISCO NXOS (GRPC)
      • Adding New Controller
      • Installing ONES Multisite
  • ONES Web GUI Administration
    • Login Page
    • Adding Devices
    • AI Assistance
    • Monitor
    • Inventory
      • Devices
      • Configurations
        • YAML Based Configuration
          • VXLAN-Symmetric
            • VXLAN-Symmetric-SAG-no-mclag-vrf
            • VXLAN-Symmetric-SAG-mclag-vrf
            • VXLAN-Symmetric-SVI-no-mclag-vrf
            • VXLAN-Symmetric-SVI-mclag-vrf
            • VXLAN-Symmetric-SAG-vrf-RoCE
          • VXLAN-SVI
            • VXLAN-SVI-no-mclag-IPv6-eBGP-IPv6-SVI
            • VXLAN-SVI-no-mclag-iBGP-IPv4-Underlay
            • VXLAN-SVI-no-mclag-eBGP-IPv6-SAG
            • VXLAN-SVI-no-mclag-eBGP-IPv4-Underlay
            • VXLAN-svi-no-mclag-eBGP-BGPU-Underlay
          • VXLAN-SAG
            • VXLAN-SAG-no-mclag-iBGP-no-host
            • VXLAN-SAG-no-mclag-iBGP-BGPU-Underlay
            • VXLAN-SAG-no-mclag-iBGP-BGPU-Underlay-HostPO
            • VXLAN-SAG-no-mclag-ebgp-no-host
          • VXLAN-MGLAG
            • VXLAN-MCLAG-ibgp-sag
            • VXLAN-MCLAG-ebgp-svi.yaml
            • VXLAN-MCLAG-ipv6-ibgp-sag
            • VXLAN-MCLAG-ebgp-BGPU-IPv6SAG
            • VXLAN-MCLAG-ibgp-BGPU-IPv6svi
            • VXLAN-MCLAG-ipv4-ibgp-svi
            • VXLAN-MCLAG-ipv6-ebgp-sag
          • VXLAN-Asymmetric
            • VXLAN-Asymmetric-SAG-no-mclag
            • VXLAN-Asymmetric-SAG-mclag
            • VXLAN-Asymmetric-SVI-no-mclag
            • VXLAN-Asymmetric-SVI-mclag
          • MH-VXLAN
            • MH-VXLAN-ibgp-sag
            • MH-VXLAN-ipv6-ibgp-sag
            • MH-VXLAN-Asymmetric-SAG
            • MH-VXLAN-ebgp-BGPU-IPv6SAG
            • MH-VXLAN-ipv6-ebgp-sag
            • MH-VXLAN-Symmetric-2-SAG-vrf
          • MCLAG
            • MCLAG-IPv4-SVI-AccessHosts
            • MCLAG-ibgp-BGPU-Underlay-IPv4SVI-AccessHosts
            • MCLAG-ibgp-IPv6-Underlay-IPv6SVI-AccessHosts
            • MCLAG-IPv4-Underlay-IPv6SVI-AccessHosts
            • MCLAG-IPv6-Underlay-IPv6SVI-AccessHosts
          • L3-MCLAG
            • L3-MCLAG
            • L3-MCLAG-bgpU-combinedLink
            • L3-MCLAG-bgp-combinedLink
          • L2-LS
            • L2LS-EC-L2
            • L2LS-EC-L3-ipv4
            • L2LS-EC-L3-ipv6
          • iBGP
            • i-BGP-IPv6-CLOS-IPv6-host
            • i-BGP-IPv6-CLOS-IPv4-svi
            • i-BGP-IPv4-CLOS-L2PO-host
            • i-BGP-IPv4-CLOS-L2-host
            • i-BGP-IPv4-CLOS-IPv6-svi
            • i-BGP-IPv4-CLOS-IPv4-PO-host
            • i-BGP-BGP-U-CLOS-IPv4-svi
            • i-BGP-BGP-U-CLOS-IPv4-host
          • e-BGP
            • e-BGP-IPv6-CLOS-IPv6-host
            • e-BGP-IPv6-CLOS-IPv4-svi
            • e-BGP-IPv4-CLOS-L2-host
            • e-BGP-IPv4-CLOS-IPv6-svi
            • e-BGP-BGP-U-CLOS-IPv6-svi
            • e-BGP-BGP-U-CLOS-IPv6-host
          • BGP-PO
            • BGP-PO-SLFOW-LeafOnly-EC
            • BGP-PO-SLFOW-LeafOnly-EC-incr1
            • BGP-PO-MCLAG-SLFOW-LeafOnly-EC
          • LeafOnly-EC
          • IPCLOS-1-IPv4-SVI-AccessHosts
          • DHCP-IPCLOS-IPv4-SVI-AccessHosts
          • VXLAN-Symmetric-SAG-vrf-RoCE
        • GUI Based Configuration
        • NetOps Based Configuration
    • Rule Engine
      • Rules Type
        • Add Rules: Entity
        • Add Rules: Entity by Properties
      • Alerts
    • Analytics
    • Settings
    • Integrations
      • Slack Channel Integration
      • Zendesk Support Integration
      • Service Now Integration
      • Cloud Services
        • Splunk
        • Amazon S3
    • Accounts
  • Support
    • How to contact Aviz Networks Support?
    • Backup and Recovery
Powered by GitBook
On this page
  • Rules Type
  • 1. Entity Based explained
  • Possible Values & Description
  • Conditions
  • Notification
  • 2. Entity by Property
  • Possible Values & Description
  • Conditions
  • Notification
  1. ONES Web GUI Administration
  2. Rule Engine

Rules Type

Rules Type

There are two types of Rule a user can configure

  1. Entity Based

    1. Allow a user to create Rules per device

      1. Allow user to include or exclude the devices from the rule

  2. Entity by Property

    1. Allow a user to create Rules by using HwSKU, Role, OS Version across all the managed devices

1. Entity Based explained

Possible Values & Description

  1. Rule Name: The user can choose any related name

  2. For: The user can choose 2 options

Device: Once the user chooses the rule for Devices it will show the below Metrics
  • ASIC IPv4 Routes

  • ASIC IPv6 Routes

  • BGP Neighbours Down

  • Device CPU Core Temperature

  • Device CPU Utilization

  • Device Down

  • Device Memory Utilization

  • Device Queue Transmit Counter

  • FAN Speed

  • Failed FANs

  • Failed PSUs

  • PSU Temperature

  • SSD Health

  • SSD Temeperature

  • SSD Used Memory Percent

  • frr CPU Utilization

  • syncd CPU Utilization

Interface: Once the user chooses the rule for Interfaces it will show the below Metrics
  • Interface flap

  • Interface PFC Receive Counters

  • Interface PFC Transmit Counters

  • Interface Queue Transmit Counters

  • Traffic InDiscards

  • Traffic InErrors

  • Traffic OutDiscards

  • Traffic OutErrors

  • Traffic Rx Utilization

  • Traffic Tx Utilization

  • Transceiver Rx Power

  • Transceiver Temperature

  • Transceiver Tx Power

  • Transceiver Voltage

Server: The user will be able to get alerts for IntelGaudy
  • CPU Core Temperature

  • CPU Utilization

  • Device Down

  • FAN Speed

  • GPU Memory Utilization

  • GPU PSU 1 Power Draw

  • GPU PSU 2 Power Draw

  • GPU Temperature

  • GPU Utilization

  • Memory Utilization

  1. Metrics: Metrics depend on the above (For: Device/Interface) condition

  2. Measure: Metrics are measured in three diff ways

    1. MIN

    2. AVG

    3. MAX

  3. Period: Measured metrics can be verified with a buffer of a timer

    1. 5 min

    2. 10 min

    3. 15 min

    4. 30 min

    5. 1 hour

Conditions

  1. When Measured Value is: This option allows a user to choose what condition has to match when the measured value is

    1. EQ: Equal to

    2. NEQ: Not Equal to

    3. GE: Greater than Equal to

    4. LE: Less than Equal to

    5. GT: Greater than

    6. LT: Less than

  2. Critical Threshold: The user can set a Critical value on which push notification will be triggered

  3. Warning Threshold: The user can set a Warning value on which push notification will be triggered

Notification

  1. Notify: The user can choose the integrated SLACK Channel

  2. Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket

  3. Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket

  4. Weekly Digest: Slack Users can choose this for Weekly Digest to SLACK Channel

  5. Do not notify if the same alert trigger in: 30min, 1hour, 2hours, 10hours, 24hours

  6. Stop notifying after: The user can choose a value of occurrence then it will not trigger the same in the next 24 hours

2. Entity by Property

Possible Values & Description

  1. Rule Name: The user can choose any related name

  2. Filter: user can filter the rule for all managed devices by

    1. HWSKU

    2. ROLE

    3. OS Version

  3. For: The user can choose 2 options

Device: Once the user chooses the rule for Devices it will show the below Metrics
  • ASIC IPv4 Routes

  • ASIC IPv6 Routes

  • BGP Neighbours Down

  • Device CPU Core Temperature

  • Device CPU Utilization

  • Device Down

  • Device Memory Utilization

  • Device Queue Counter

  • FAN Speed

  • Failed FANs

  • Failed PSUs

  • PSU Temperature

  • SSD Health

  • SSD Temeperature

  • SSD Used Memory Percent

  • frr CPU Utilization

  • syncd CPU Utilization

Interface: Once the user chooses the rule for Interfaces it will show the below Metrics
  • Interface Flap

  • Interface PFC Counters

  • Interface Queue Counters

  • Traffic InDiscards

  • Traffic InErrors

  • Traffic OutDiscards

  • Traffic OutErrors

  • Traffic Rx Utilization

  • Traffic Tx Utilization

  • Transceiver Rx Power

  • Transceiver Temperature

  • Transceiver Tx Power

  • Transceiver Voltage

  1. Select: this option depends on the Filter category, possible values are

    1. Select HWSKU :

    2. Select ROLE :

    3. Select OS VERSION :

  2. Metrics: Metrics depend on the above (For: Device/Interface) condition

  3. Measure: Metrics are measured in three diff ways

    1. MIN

    2. AVG

    3. MAX

  4. Period: Measured metrics can be verified with a buffer of a timer

    1. 5 min

    2. 10 min

    3. 15 min

    4. 30 min

    5. 1 hour

Conditions

  1. When Measured Value is: This option allows a user to choose what condition has to match when the measured value is

    1. EQ: Equal to

    2. NEQ: Not Equal to

    3. GE: Greater than Equal to

    4. LE: Less than Equal to

    5. GT: Greater than

    6. LT: Less than

  2. Critical Threshold: The user can set a Critical value on which push notification will be triggered

  3. Warning Threshold: The user can set a Warning value on which push notification will be triggered

Notification

  1. Notify: The user can choose the integrated SLACK Channel

  2. Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket

  3. Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket

  4. Weekly Digest: Slack Users can choose this for Weekly Digest to SLACK Channel

  5. Do not notify if the same alert trigger in 30min, 1hour, 2hours, 10hours, 24hours

  6. Stop notifying after: The user can choose a value of occurrence then it will not trigger the same in the next 24 hours

PreviousRule EngineNextAdd Rules: Entity