Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Networking models

You can find information on the models used for BMC Network Automation cloud implementations in the BMC Network Automation online technical documentation topics listed in the following table:

Pod model

ModelDescriptionFor more information
Pod

A pod is composed of the following types of elements: name, ID, site ID, parametersresource collectionsnodespairs, and NIC segments.

A pod also maintains a reference to the name of the blueprint which created it. A pod name is unique among all pods. The ID is also unique among all pods, and is a number generated by BMC Network Automation. The site ID must refer to a BMC_PhysicalLocation object in the CMDB (or it can be null if the site is unknown). One is free to modify or delete the blueprint used to create a pod without affecting the pod.

Pod model
Network container

A container is composed of the following types of elements:

  • name
  • ID
  • type (optional)
  • acquired resources
  • segments
  • network paths
  • path rules
  • zones
  • nodes
  • pairs

A container also maintains a reference to the name of the blueprint from which it was created. A container name must be unique among all containers. The ID is a number generated by BMC Network Automation that also is unique among all containers. The type is a string value used purely for self documenting purposes. You can modify or delete the blueprint used to create a container without affecting the container that was created earlier. The structure of container blueprints mirrors the structure of containers, but it represents a reusable formulation of the information that is present within a container, which is pod-independent.

Container model

For descriptions of the use cases for the interactions between BMC Network Automation and BMC Cloud Lifecycle Management, see Networking use cases.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments