Configuring IP Verify - IP-Verify/Configuring-IP-Verify

Configuring IP Verify

ft:locale
en-US
ft:sourceName
Paligo_Prod
Document Type
Article

Complete the following to configure an Test Instance.

  1. Log into NetCloud Manager.

  2. Select Devices in the left-side navigation panel.

  3. Select a router from the Routers page. Alternatively, to make configuration changes to a group, navigate to the Groups page and select a group.

  4. Select Configuration and then Edit.

  5. Navigate to IDENTITIES > IP Verify.

    The IP Verify Identities page displays.

  6. Click Add.

    The Add or Edit Test Instance dialog displays.

    ipverify-page.png
  7. Configure the Test Instance using the following options:

    • Test Name: Enter a name to identify the test instance. This will be used to associate action to test results.

    • Enabled: Select Enabled to enable the test instance.

    • Interval: Defines the time interval between test iteration. Use this to control how frequently entity identified by test needs to be monitored. and retry fields define the frequency of the test run.

    • Retry Interval and Retry Count: When the test determines that the monitored entity is not in an expected state, it retries and waits for a certain duration. If the monitored entity consistently stays in an unexpected state during this interval, the test is declared a failure. Use the Retry Interval and Retry Count to control how long the test waits before declaring it a failure. Retry Interval defines the time interval between retries and Retry Count defines the number of times to retry.

    • Log On Pass and Log On Fail: When the monitored entity transitions out of expected state, an event is logged via syslog.

    • Alert On Pass and Alert On Fail: When monitored entity transitions out of expected state, generate an alert.

    • Test Type: Identifies the router entity to be monitored. Options include the following:

      Note

      Selecting a specific test type adds test-specific fields to the page, which are listed below.

      • Test VRRP state: Checks the VRRP state in a local area network.

        • LAN ID: The local network to be monitored.

        • VRRP State: The state to consider the test as success.

      • Test Ethernet port state: Checks if an Ethernet port is up.

        • Port Identifier: Specifies the Ethernet port to be monitored.

      • Test SFP port state: Check if SFP port is up.

        • Port Identifier: Specifies the SFP port to be monitored.

      • Test WAN device state: Checks the state WAN device(s).

        • Wan Binding: Specifies the WAN device(s) to monitor.

        • State: Select the expected state of WAN device(s). Select All if all selected WAN device(s) should be in expected state, otherwise at least one WAN device should be in expected state.

      • Test if the route exists: Checks if a route exist in given routing table.

        • Destination IP/Network address: The address should be in CIDR form like the following:  

          IPv4: 1.2.3.0/24 

          IPv6: 0123:4567:CDEF::/64

          A default route destination is specified as:  IPv4: 0.0.0.0/0  IPv6: ::/0

        • Gateway: (Optional) Enter the IPv4 or IPv6 gateway address to match. The network address must match the IP version entered here. A default route destination is specified as:  

          IPv4: 0.0.0.0/0  

          IPv6: ::/0

        • Device: (Optional) Enter the device interface to match.

        • Metric: (Optional) Enter the route metric to match.

      • Test BGP peer reachability: Checks if the BGP Peer is up.

      • Test ICMP echo (ping) response

        • Target Address: Target address to Ping to

        • Source Address: Source address to Ping from

        • WAN Binding: The wan binding parameters can be used to select a wan interface for sending Ping packets

        • Invert Binding: Advanced option that inverts the meaning of WAN Binding to establish Ping when the specified WAN Binding device(s) are NOT connected.

      • Composite Test: Checks the result of a set of other tests.

        • Expression: Composite test is specified as logical expression.

      • Custom test: Tests result of a custom application (like a SDK application). For example, an SDK application will put it results in control tree, and custom test will monitor control tree for pass and fail events.Name refers to name of custom application.

  8. Click Save.