Network blueprints


BMC Helix AIOps offers several out-of-the-box blueprints that are ready to use and consist of rule-based templates for creating services or applications. Find the details of the default application blueprints in the following sections:


Default Blueprint for Network device and its connections

Use this default blueprint to create a technical service.

Important

If this blueprint has multiple versions, the version is added to the Description field, for example, Using network device name to get its connections, v2.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Network Device through which the network infrastructure is accessible
  • Traversal path and connected nodes: Associated Network Interfaces and Network Devices interconnected with Load Balancer member nodes, other network devices such as printers, SNMP Managed devices, and so on, as shown in the following image:
    network_devices_connections_3_244.png
  • Default filter rules:
    • The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of the Network Device as input when creating the service model.
      network_devices_connections_3_filter_part1_244.png
    • The filter rule applied in all other Network Device nodes is of type Device in Stack, as shown in the following image:
      network_devices_connections_2.0_filter_part2_244.png


Default Blueprint for Network Device to Host

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Network Device through which the host is accessible
  • Traversal path and connected nodes: Network Device, Network Interfaces, and Host, as shown in the following image:
    network_device_to_host_2_244.png
  • Default filter rules: The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of the Network Device Name as input when creating the service model.
    network_device_to_host_2_filter_244.png


Default Blueprint for Physical Host to Network Device

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Host through which the network devices are accessible
  • Traversal path and connected nodes: Host, Network Interfaces, and Network Device, as shown in the following image:
    physical_host_to_network_device_1.0_244.png
  • Default filter rules: The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of the Host as input when creating the service model.
    host_to_network_1.0_filter_part1_244.png

Earlier version of the blueprint

Click here to expand.

Important

Earlier, this blueprint name appeared as Default Blueprint for Host to Network on the console.

Version 1.0 nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Host through which the network devices are accessible
  • Traversal path and connected nodes: Host, Network Interfaces, and Network Device, as shown in the following image:
    host_to_network_1.0.png
  • Default filter rules: The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of the Host as input when creating the service model.
    host_to_network_1.0_filter_part1.png


Default Blueprint for Virtual Host to Network Device

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Host through which the network devices are accessible
  • Traversal path and connected nodes: Host, Network Interfaces, and Network Device, as shown in the following image:
    virtual_host_network_device_244.png
  • Default filter rules:
    • The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of the Host as input when creating the service model.
      virtual_host_network_device_filter01_244.png

    • The default Filter by Kind link rule is enabled between the Virtual Machine and Host nodes connection, as shown in the following image:
      virtual_host_network_device_filter02.jpg


Default Blueprint for Wireless LAN Controller Network Device Name

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Network Device of type Wireless LAN Controller
  • Traversal path and connected nodes: Network Interfaces with interconnected Hosts and Network Devices, as shown in the following image:
    wireless_lan_controller_244.png
  • Default filter rules: The filter criteria are set in the start node, as shown in the following image. The filters apply to applications that are of the Wireless LAN Controller type. The service designer needs to select the names of the Wireless LAN Controllers as input when creating the service model.
    wireless_lan_controller_filter_part1_244.png

Where to go from here

Creating-service-models

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*