Overview of pod and container blueprints
BMC Network Automation is installed with pod and container blueprints that you can use as a template for a pod or container that is customized for your network environment. These files are located in the *{_}BCAN_HOME{_}{*}*/public/bmc/bca-networks/csm* directory and subdirectories.
This topic summarizes the purpose of the pod and container files. The topic includes the following sections:
Network pod blueprint templates
Subdirectory | File | Description |
|---|---|---|
samples | SamplePodBlueprint.xml | General pod blueprint template. You can use the comments in this file to construct new pod blueprints for any environment or devices. |
sampleWithF5BigPipeVlb | SamplePodBlueprintF5Bigpipe.xml | Sample pod blueprint featuring F5 load balancer. |
sampleWithF5BigPipeVlb | SamplePodBlueprintF5BigpipeHA.xml | Sample pod blueprint featuring F5 load balancer in high-availablity (redundant) mode. |
sampleWithJuniperSrxVfw | SamplePodBlueprintJuniperSRX.xml | Sample pod blueprint featuring Juniper SRX Firewall. |
sampleWithVSG | SamplePodBlueprintVSG.xml | Sample pod blueprint featuring Cisco VSG (Virtual Security Gateway.) |
compact-2.1 | VMDC2-1podbprv9.xml | VMDC 2.1 pod blueprint. |
large-2.0 | LargePodBlueprint.xml | VMDC 2.0 pod blueprint. |
super-container | SuperPodBlueprint.xml | Multi-zone Cisco SuperContainer pod blueprint. |
Network container blueprint templates
Subdirectory | File | Description |
|---|---|---|
samples | SampleContainerBlueprint.xml | General container blueprint template. You can use the comments in this file to construct new container blueprints for any environment or devices. |
sampleWithF5BigPipeVlb | SampleContainerBlueprintF5Bigpipe.xml | Sample container blueprint featuring F5 load balancer. |
sampleWithF5BigPipeVlb | SampleContainerBlueprintF5BigpipeHA.xml | Sample container blueprint featuring F5 load balancer in high-availablity (redundant) mode. |
sampleWithJuniperSrxVfw | SampleContainerBlueprintJuniperSRX.xml | Sample container blueprint featuring Juniper SRX Firewall. |
sampleWithVSG | SampleContainerBlueprintVSG.xml | Sample container blueprint featuring Cisco VSG (Virtual Security Gateway.) |
compact-2.1 | VMDC2-1contbprv9.xml | Cisco Virtualized Multi-Tenant Data Center (VMDC) 2.1 container blueprint. |
large-2.0 | LargeBronzeContainerBlueprint.xml | VMDC 2.0 bronze container blueprint for Cisco IOS XR Routers. |
large-2.0 | LargeSilverContainerBlueprint.xml | VMDC 2.0 silver container blueprint for Cisco IOS XR Routers. |
large-2.0 | LargeGoldContainerBlueprint.xml | VMDC 2.0 gold container blueprint for Cisco IOS XR Routers. |
large-2.0 | LargeBronzeContainerBlueprint7600.xml | VMDC 2.0 bronze container blueprint with Edge 1 and Edge 2 coded for IOS Routers. |
large-2.0 | LargeSilverContainerBlueprint7600.xml | VMDC 2.0 silver container blueprint with Edge 1 and Edge 2 coded for IOS Routers. |
large-2.0 | LargeGoldContainerBlueprint7600.xml | VMDC 2.0 gold container blueprint with Edge 1 and Edge 2 coded for IOS Routers. |
super-container | SuperContainerBlueprint.xml | Multi-zone Cisco SuperContainer container blueprint. |
About the templates
Note
For proof-of-concept environments, you can request the _Baby_ container blueprint and _Baby_ pod blueprint from BMC Support or consultants. The _Baby_ network container includes a single zone containing one data network. Network containers built from this blueprint should be used with pods built from the _Baby_ pod blueprint.
The VMDC 2.0 templates are intended to be used with the most complex network architectures.
The VMDC 2.1 templates are intended to be used with less complex implementations, typically up to 32 tenants and 4,000 VM instances. These templates include fewer options. They are easier to customize in cases where they are sufficient.
These architectures are explained further on the Cisco web site:
The bronze, silver, and gold models are summarized in the following table:
Model | Number of | Number of management | Number of virtual load | Number of virtual |
|---|---|---|---|---|
Bronze | 1 | 1 | 0 | 0 |
Silver | 3 | 1 | 1 | 0 |
Gold | 3 | 1 | 1 | 1 |
The pod consists of a stack of connected switching layers, namely:
- Edge
- Core
- Aggregation
- Services
- Access
The load balancer and firewall hosts are connected to the services layer.
Redundancy is defined at each layer in the container. Active-active fault tolerance is used in the VLBs and VFWs. Cisco Carrier Routing System (CRS) devices are used in the edge layer. Cisco Nexus 7000 Series (N7K) Switches are used in the core and aggregation layers. C6K devices are used in the services layer. The UCS devices host a Cisco Nexus 1000 (N1K) hypervisor switch and represent the access layer.
Related BMC Communities videos
The following BMC Communities video (6:46) describes how to use IP address resources in network blueprints using BMC Network Automation. The blueprints can then be imported into BMC Cloud Lifecycle Management.
The following BMC Communities video (4:11) discusses how to use VLAN resources in pod and container blueprints.
Comments
Log in or register to comment.