Important

   

Starting version 8.9.03, BMC Network Automation is renamed to TrueSight Network Automation. This space contains information about BMC Network Automation 8.9.02 and previous versions. For TrueSight Network Automation 8.9.03 and later releases, see the TrueSight Network Automation documentation.

Understanding globally unique identifiers

Global unique identifier (GUIDs) are 36 characters long and consist of hexadecimal digits and hyphens. They are used in BMC Network Automation to identify device types, vendors, custom actions, and trails. The following topic provides briefly describes how to use a built-in script to generate new GUIDs that you might require and lists the GUID types and values that BMC Network Automation uses to prevent potential ID collisions.

You can also find the device type, vendor, custom action, and trail GUID values by viewing them on the Network Administration > Device Adapters page or exporting the corresponding adapter definition.

Creating GUIDs

If you develop a new custom device type or custom action you must create a new, unique GUID. Insert the GUID string in the guid tags of your device adapter import file.

To generate a new GUID, use the create_guid.sh or create_guid.bat script in the BCAN_HOME/tools directory.

This script prints a GUID string to the screen. For more information, see Understanding tools and scripts.

Important: If you are performing a BMC Network Automation application server upgrade, you must follow the procedure for upgrading existing XML files that reside in the BCAN_DATA directory. Be sure to preserve the id tags in your existing custom extension files to facilitate database upgrades. See Upgrading.

Configuration trail GUIDs

Shipped trails are identified by the GUID values listed in the following table:

Trail

GUID

ARP Table

67868622-37E9-40B6-AA10-E43E5037ABE8

Alcatel ESS/SR bof.cfg File7F2F7B75-7D05-4726-97E0-EAEDD96C0F60

MAC Table

BF839166-E9C9-42C2-8397-0FFD6362BCFC

Avaya Module 1

50590DF3-0647-4113-A7F0-744D7C18AD31

Avaya Module 2

796CD804-10A0-4D2E-93DD-D5F72F7302F7

Avaya Module 3

51722558-7284-4A79-99CA-43C1740E00EB

Avaya Module 4

7BB0824F-9B6D-427B-9B37-9F1A4B46AEEA

Avaya Module 5

F3E2E525-442F-4820-A3B0-217EF3791897

BNA Device Attributes4220A707-8D57-4F12-BD47-601A17DE32F3

Check Point Asm.C

4B8D1417-B776-47F3-AE0D-A808DF925C6F

Check Point Objects.C

F03918C7-A95B-4055-97DF-D6E64CD1BA1E

Check Point Rules.C

D48C7DA9-95B3-4899-8730-FF13D8545970

Check Point TGZ File

5FAB2910-CD3B-45BC-8224-FAADEA2F6D44

Cisco Sourcefire Sensor Access Control Configuration File7F2F7B75-7D05-4726-97E0-EAEDD86C0C67

Extreme XOS XML

A3EC716E-35A8-406A-864F-2863E9ABBE20

F5 bigip_base.conf

442BEAF7-48EF-45B5-B664-3D1D3BDF958B

F5 bigip.conf

3BB55D88-1F96-4BC9-8994-2D77ECABA5FE

F5 BigIP Database

5F8399ED-8065-451B-B918-970C95D54FB9

F5 BigIP License

6740A202-D3BC-4C8A-9FA4-9DD3B97F83B3

F5 BigIP UCS

708CF096-0279-41FF-A60C-AA22F2B14D46

IOS vlan.dat

294DA341-E2E1-43CE-9E2E-54634CCC228D

IOS XR admin.cfg

73765516-1161-49B5-B4D4-69EB450ED9A5

IOS XR router.cfg

4B22A18F-FF23-49E7-8D76-405D626430AF

Nortel Passport 8000 boot.cfg File9EF43FC9-2C16-484D-954C-1810460EF25F

Running

02C89A1F-A5D2-44B0-AE1E-B714EB0E3FAF

Startup

1D168B48-15CC-416E-AB4A-88E2E7104E2D

WAAS SYSREPORT

9A05AFEA-58F8-4582-8F66-B14107C8E3B7

WAAS WAFS Configuration Tar File

80BF1CB0-B1C6-4C07-9686-43D7E20AE129

Was this page helpful? Yes No Submitting... Thank you

Comments