Understanding the public XML files
You can modify the files in the public XML directory to customize or tweak the BMC Network Automation system.
Each XML file has an associated XSD schema file that can be used to validate and verify changes made to the XML files.
Device Import formats file
Location: BCAN_HOME/public/bmc/bca-networks/xml/DeviceImportFormatMap.xml
This file contains the Device Import formats available to you on the Device Import GUI. Any entry added to this file must have an associated XSL translator stylesheet.
Category names and ID file
Location: BCAN_HOME/public/bmc/bca-networks/xml/CategoryMap.xml
This file contains the legal device Category names and IDs. It is used by device adapter definition to associate device types and their SNMP OIDs with appropriate categories. This affects which categories are available for selection while editing a device.
Time period types file
Location: BCAN_HOME/public/bmc/bca-networks/xml/TimePeriodTypeMap.xml
This file specifies the types of time periods that are shipped with BMC Network Automation and are used to construct third-party URLs and to write the web service Java client.
Security vulnerability files
Location: BCAN_HOME/public/bmc/bca-networks/securityVulnerabilities
This directory and its subdirectories contain canned security vulnerability files downloaded from vendors shortly prior to release time. Each supported vendor has a subdirectory containing applicable files. These files are loaded into BMC Network Automation during installation or upgrade. The files are not used thereafter, but you can re-import them if they are erroneously deleted.
BMC Cloud Lifecycle Management blueprints and templates
The following tables list the .XML template files related to the BMC Cloud Lifecycle Management pod and container blueprints.
General blueprint templates
Location: BCAN_HOME/public/bmc/bca-networks/csm/docs
The following table describes these templates.
File | Description |
---|---|
ContainerBlueprint.xml | General container blueprint template. You can use the comments in this file to construct new container blueprints for any environment or devices. |
PodBlueprint.xml | General pod blueprint template. You can use the comments in this file to construct new pod blueprints for any environment or devices. |
Cisco Virtualized Multi-tenant Data Center blueprint templates
Location for Cisco Virtualized Multi-tenant Data Center version 2.1 templates:
BCAN_HOME/public/bmc/bca-networks/csm/compact-2.1
The following table describes these templates.
File | Description |
---|---|
VMDC2-1contbprv9.xml | VMDC version 2.1 container blueprint. Additional .XML template files related to the container blueprint are found in the BCAN_HOME/public/bmc/bca-networks/csm/compact-2.1/templates directory. For more information, see Correspondence of blueprints and templates. |
VMDC2-1podbprv9.xml | VMDC version 2.1 pod blueprint. |
Location for Cisco VMDC version 2.0 templates: BCAN_HOME /public/bmc/bca-networks/csm/large-2.0
The following table describes these templates.
File | Description |
---|---|
LargeBronzeContainerBlueprint.xml | VMDC 2.0 bronze container blueprint for Cisco IOS XR Routers. |
LargeSilverContainerBlueprint.xml | VMDC 2.0 silver container blueprint for Cisco IOS XR Routers. |
LargeGoldContainerBlueprint.xml | VMDC 2.0 gold container blueprint for Cisco IOS XR Routers. |
LargeBronzeContainerBlueprint7600.xml | VMDC 2.0 bronze container blueprint with Edge 1 and Edge 2 coded for IOS Routers. |
LargeSilverContainerBlueprint7600.xml | VMDC 2.0 silver container blueprint with Edge 1 and Edge 2 coded for IOS Routers. |
LargeGoldContainerBlueprint7600.xml | VMDC 2.0 gold container blueprint with Edge 1 and Edge 2 coded for IOS Routers. |
LargePodBlueprint.xml | VMDC 2.0 pod blueprint. |
Additional .XML template files related to the container blueprint files listed above are found in the BCAN_HOME/public/bmc/bca-networks/csm/large-2.0/templates/ directory. See Correspondence of blueprints and templates for more information.
The VMDC 2.0 and 2.1 blueprints and the Bronze, Silver, and Gold pod blueprints are designed for specific Cisco configurations.
Correspondence of blueprints and templates
The correspondence of blueprints and templates follows an informal file-naming standard. This practice is illustrated by the following example.
The following table lists the template files that are referenced by LargeGoldContainerBlueprint.xml. The files that are referenced only by the large gold container blueprint contain gold in the file name. Files that are referenced by multiple blueprints contain common in the file name.
File | Description |
---|---|
LargeCommonConfigureCore1.xml | Configures a core switch. |
LargeCommonUnconfigureCore1.xml | Unconfigures a core switch. |
LargeCommonConfigureEdge1.xml | Configures an edge switch. |
LargeCommonUnconfigureEdge1.xml | Unconfigures an edge switch. |
LargeGoldConfigureAccess.xml | Configures an access switch. |
LargeGoldUnconfigureAccess.xml | Unconfigures an access switch when deprovisioning a container. |
LargeGoldConfigureServices.xml | Configures services switch. |
LargeGoldUnconfigureServices.xml | Unconfigures services switch. |
LargeGoldConfigureServicesBGP1.xml | Configures border gateway protocol on the Services switch. |
LargeGoldCreateFirewallGuest.xml | Creates a firewall guest. |
LargeGoldInitializeFirewallGuest.xml | Initializes a firewall guest. |
LargeGoldDestroyFirewallGuest.xml | Destroys a firewall guest. |
LargeGoldCreateLoadBalancerGuest.xml | Creates a load balancer guest. |
LargeGoldInitializeLoadBalancerGuest.xml | Initializes a load balancer guest. |
LargeCommonDestroyLoadBalancerGuest.xml | Destroys a load balancer guest. |
LargeGoldConfigureAgg1.xml | Configures an aggregation switch. |
LargeGoldUnconfigureAgg1.xml | Unconfigures an aggregation switch. |
Comments