Skip to content

Latest commit

 

History

History
632 lines (433 loc) · 20.2 KB

README.ezday2tools.md

File metadata and controls

632 lines (433 loc) · 20.2 KB

EZDAY2TOOLS Synopsis

The purpose of ezday2tools.py is to manage Server Environments in Intersight for day 2 management tasks. It provides tools to help in obtaining reports on identities, adding new VLANs to policies for domain and server policies.

Capabilities

  • add_policies: Update Policies attached to chassis, domain, server profiles/templates within the same organization or from a shared organization.
  • add_vlans: Function to add a VLAN to existing VLAN Poilcy and Ethernet Network Group Policies. Optionally can also create LAN Connectivity Policies.
  • audit_logs: Function to Get List of Users that have logged into the Account and performed actions/changes.
  • clone_policies: Function to clone policies from one Organization to another.
  • hcl_status: Function to take UCS inventory from vCenter and validate the status of the HCL VIB.
  • inventory: Function to Create a Spreadsheet with inventory for Domains, Chassis, Servers.
  • server_identities: Function to get WWNN/WWPN and MAC identities. By default it only gathers the fibre-channel identities. To get full identities list add the -fi option at the CLI.,

Running the EZDAY2TOOLS

It is recommend to add the following secure variables to your environment before running the script.

Linux

## Bash Intersight Variables
export intersight_api_key_id="<your_intersight_api_key>"
export intersight_secret_key="~/Downloads/SecretKey.txt"

Windows

## Powershell Intersight Variables
$env:intersight_api_key_id="<your_intersight_api_key>"
$env:intersight_secret_key="$HOME\Downloads\SecretKey.txt"

Back to Top

Add Policies

EZDAY2TOOLS - add_policies: Use Case

  • Update Policies attached to chassis, domain, server profiles/templates within the same organization or from a shared organization.

EZDAY2TOOLS - add_policies: Run the wizard

Linux

ezday2tools.py -p add_policies

------------------------------------------------------------------------------------------------------------

   Begin Function: add_policies.

------------------------------------------------------------------------------------------------------------


------------------------------------------------------------------------------------------------------------

 Select the Source Organization for the pools/policies:
 
    Select an Option Below:
      1. Asgard
      2. common
      3. default
      4. RICH
      5. Wakanda

Please Enter the Option Number to select for Organization.  [3]: 2

------------------------------------------------------------------------------------------------------------

 Select the Organization for the Profiles:
 
    Select an Option Below:
      1. Asgard
      2. common
      3. default
      4. RICH
      5. Wakanda

Please Enter the Option Number to select for Organization.  [3]: 5

------------------------------------------------------------------------------------------------------------

 Select the Profile Type.  Options are:
   * chassis: Chassis Profiles.
   * domain: Domain Profiles.
   * FIAttached: Domain Attached Server Profiles/Templates.
   * Standalone: Standalone Server Profiles/Templates.
 
    Select an Option Below:
      1. chassis
      2. domain
      3. FIAttached
      4. Standalone

Please Enter the Option Number to select for Profile Type.  [3]: 1

------------------------------------------------------------------------------------------------------------

 Select the policy types you would like to clone in the environment:
 
     Note: Answer can be:
       * Single: 1
       * Multiple: `1,2,3` or `1-3,5-6`
     Select Option(s) Below:
      1. imc_access
      2. power
      3. snmp
      4. syslog
      5. thermal

Please Enter the Option Number(s) to select for Policy Types.  [press enter to skip]: 3

------------------------------------------------------------------------------------------------------------

 Select the snmp policy from source org: `common` to attach to chassis(s) in org: `Wakanda`.
 
    Select an Option Below:
      1. snmp

Please Enter the Option Number to select for snmp Policy: 1

------------------------------------------------------------------------------------------------------------

    snmp: snmp

------------------------------------------------------------------------------------------------------------


------------------------------------------------------------------------------------------------------------

 Do You want to accept the above configuration for the `policy bucket update`?


Enter `Y` for `True` or `N` for `False` for `Accept`. [Y]: 

------------------------------------------------------------------------------------------------------------

 Select the `chassis` Profiles to update.
 
     Note: Answer can be:
       * Single: 1
       * Multiple: `1,2,3` or `1-3,5-6`
     Select Option(s) Below:
      1. r143e-2-1

Please Enter the Option Number(s) to select for chassis Profiles.  [1]: 
     - Completed PATCH for Org: Wakanda > Name: r143e-2-1 - Moid: 6605c56077696e3201f34e73

------------------------------------------------------------------------------------------------------------

 Do you want to Deploy/Activate the `chassis` profiles?


Enter `Y` for `True` or `N` for `False` for `Deploy Profiles`. [N]: Y

------------------------------------------------------------------------------------------------------------

     - Beginning Profile Deployment for `r143e-2-1`.
     - Completed PATCH for Org: Wakanda > Name: r143e-2-1 - Moid: 6605c56077696e3201f34e73
       * Deploy Still Occuring on `r143e-2-1`.  Waiting 60 seconds.
     - Completed Profile Deployment for `r143e-2-1`.

------------------------------------------------------------------------------------------------------------


------------------------------------------------------------------------------------------------------------

   End Function: add_policies.

------------------------------------------------------------------------------------------------------------

Back to Top

Add VLANs

EZDAY2TOOLS - add_vlans: Use Cases

  • Add VLAN to VLAN Policy and Ethernet Network Groups to Organization List. If desired also create a new LAN Connectivity Policy for the new VLAN.

EZDAY2TOOLS - add_vlans: Build the YAML definition File

See example examples/day2tools/add_vlans/add_vlans.yaml.

  • The function will loop through all organizations listed. To create ethernet_network_groups, a vlan_policy, and lan_connectivity.
  • lan_connectivity is optional.
  • If lan_connectivity is defined all attributes shown are required. Can have one or more vnics.

Linux

ezday2tools.py -p add_vlans -y add_vlans.yaml

Windows

python ezday2tools.py -p add_vlans -y add_vlans.yaml

Example Output

tyscott@TYSCOTT-DESKTOP:~/scotttyso/intersight-tools/examples/day2tools/add_vlans$ ezday2tools.py -y add_vlans.yaml

------------------------------------------------------------------------------------------------------------

 Select the Process to run:
   * add_policies: Update Policies attached to chassis, domain, server profiles/templates within the
     same organization or from a shared organization.
   * add_vlans: Function to add a VLAN to existing VLAN Poilcy and Ethernet Network Group Policies.
     Optionally can also create LAN Connectivity Policies.
   * audit_logs: Function to Get List of Users that have logged into the Account and performed
     actions/changes.
   * clone_policies: Function to clone policies from one Organization to another.
   * hcl_status: Function to take UCS inventory from vCenter and validate the status of the HCL VIB.
   * inventory: Function to Create a Spreadsheet with inventory for Domains, Chassis, Servers.
   * server_identities: Function to get WWNN/WWPN and MAC identities.  By default it only gathers the
     fibre-channel identities. To get full identities list add the `-fi` option at the CLI.
 
 
    Select an Option Below:
       1. add_policies
       2. add_vlans
       3. audit_logs
       4. clone_policies
       5. hcl_status
       6. inventory
       7. server_identities

Please Enter the Option Number to select for Day2Tools Process.  [6]: 2

------------------------------------------------------------------------------------------------------------

   Begin Function: add_vlans.

------------------------------------------------------------------------------------------------------------


------------------------------------------------------------------------------------------------------------

   Beginning Ethernet Network Group Policies Deployments.

       * Skipping Org: Common; Ethernet Network Group Policy: `ESX`.  Intersight Matches Configuration.
         Moid: 660af2316f626932018a62e8
       * Skipping Org: Common; Ethernet Network Group Policy: `UPLINK`.  Intersight Matches
         Configuration.  Moid: 65bbdf2e6f626932017a44cd
       * Skipping Org: Common; Ethernet Network Group Policy: `301-NIC-A`.  Intersight Matches
         Configuration.  Moid: 663ce2dc6f626932019a2c38
       * Skipping Org: Common; Ethernet Network Group Policy: `1444-NIC-A`.  Intersight Matches
         Configuration.  Moid: 663ce2dc6f626932019a2c53
 
   Completed Ethernet Network Group Policies Deployments.

------------------------------------------------------------------------------------------------------------

   Beginning Lan Connectivity Policies Deployments.

       * Skipping Org: Common; Lan Connectivity Policy: `301`.  Intersight Matches Configuration.
         Moid: 663ce36e4ff5f73001def317
       * Skipping Org: Common; Lan Connectivity Policy: `1444`.  Intersight Matches Configuration.
         Moid: 663ce36e4ff5f73001def31f
       * Skipping Org: Common; Lan Connectivity Policy `301`: VNIC: `NIC-A`.  Intersight Matches
         Configuration.  Moid: 663ce3b04ff5f73001df4a5b
       * Skipping Org: Common; Lan Connectivity Policy `1444`: VNIC: `NIC-A`.  Intersight Matches
         Configuration.  Moid: 663ce3b04ff5f73001df4b18
 
   Completed Lan Connectivity Policies Deployments.

------------------------------------------------------------------------------------------------------------

   Beginning VLAN Policies Deployments.

       * Skipping Org: Common; VLAN Policy: `VLAN`.  Intersight Matches Configuration.  Moid:
         65bbdea96f626932017a0825
       * Skipping Org: Common; VLAN Policy: `VLAN`, VLAN: `301`.  Intersight Matches Configuration.
         Moid: 663bb2df6f62693201e7c451
       * Skipping Org: Common; VLAN Policy: `VLAN`, VLAN: `1444`.  Intersight Matches Configuration.
         Moid: 663cee226f62693201a20f91
 
   Completed VLAN Policies Deployments.

------------------------------------------------------------------------------------------------------------

   End Function: add_vlans.

------------------------------------------------------------------------------------------------------------

tyscott@TYSCOTT-DESKTOP:~/scotttyso/intersight-tools/examples/day2tools/add_vlans$

Back to Top

Audit Logs

EZDAY2TOOLS - audit_logs: Use Cases

  • Get list of All Users that have logged into Intersight Account and how many days they have logged in a interval (number of months)

Linux

ezday2tools.py -p audit_logs

Windows

python ezday2tools.py -p audit_logs

Back to Top

Clone Policies

EZDAY2TOOLS - clone_policies: Use Cases

  • Clone policies from one org to another

EZDAY2TOOLS - clone_policies: Run the wizard

  • supports cloning one or more policy types from source to destination organization.
  • supports cloning one or more policies of each policy type.
  • policies with child policies are not supported currently. If desired please open an Issue. It just needs some additional development and I didn't have the need.

Not supported:

  • IMC Access
  • iSCSI Boot
  • LAN Connectivity
  • LDAP
  • Local User
  • Port
  • Profiles (chassis/domain/server)
  • SAN Connectivity
  • Storage
  • VLAN
  • VSAN

Linux

ezday2tools.py -p clone_policies

------------------------------------------------------------------------------------------------------------

   Begin Function: clone_policies.

------------------------------------------------------------------------------------------------------------


------------------------------------------------------------------------------------------------------------

 Select the Source Organization to clone the pools/policies from.
 
    Select an Option Below:
      1. Asgard
      2. common
      3. default
      4. RICH
      5. Wakanda

Please Enter the Option Number to select for Organization.  [3]: 2

------------------------------------------------------------------------------------------------------------

 Select the Destination Organization to clone the policies to.
 
    Select an Option Below:
      1. Asgard
      2. common
      3. default
      4. RICH
      5. Wakanda

Please Enter the Option Number to select for Organization.  [3]: 

------------------------------------------------------------------------------------------------------------

   * chassis: Chassis Profiles.
   * domain: Domain Profiles.
   * FIAttached: Domain Attached Server Profiles/Templates.
   * Standalone: Standalone Server Profiles/Templates. 

    Select an Option Below:
      1. chassis
      2. domain
      3. FIAttached
      4. Standalone

Please Enter the Option Number to select for Target Platform.  [3]: 

------------------------------------------------------------------------------------------------------------

 Select the policy types you would like to clone in the environment:
 
     Note: Answer can be:
       * Single: 1
       * Multiple: `1,2,3` or `1-3,5-6`
     Select Option(s) Below:
      1. bios
      2. boot_order
      3. certificate_management
      4. drive_security
      5. ethernet_adapter
      6. ethernet_network_control
      7. ethernet_network_group
      8. ethernet_qos
      9. fc_zone
     10. fibre_channel_adapter
     11. fibre_channel_network
     12. fibre_channel_qos
     13. firmware
     14. ipmi_over_lan
     15. iscsi_adapter
     16. iscsi_static_target
     17. power
     18. sd_card
     19. serial_over_lan
     20. snmp
     21. syslog
     22. thermal
     23. virtual_kvm
     24. virtual_media

Please Enter the Option Number(s) to select for Policies.  [press enter to skip]: 1

------------------------------------------------------------------------------------------------------------

 Select the pool types you would like to clone in the environment:
 
     Note: Answer can be:
       * Single: 1
       * Multiple: `1,2,3` or `1-3,5-6`
     Select Option(s) Below:
      1. ip
      2. iqn
      3. mac
      4. resource
      5. uuid
      6. wwnn
      7. wwpn

Please Enter the Option Number(s) to select for Pools.  [press enter to skip]: 

------------------------------------------------------------------------------------------------------------

 Select the `bios` policies to clone from source org: `common` to destination org: `default`.
 
     Note: Answer can be:
       * Single: 1
       * Multiple: `1,2,3` or `1-3,5-6`
     Select Option(s) Below:
      1. M5-intel-virtual
      2. M5-intel-virtual-tpm
      3. M6-intel-virtual-tpm

Please Enter the Option Number(s) to select for bios Policies: 3
     - Completed POST for Org: common Name: M6-intel-virtual-tpm - Moid: 661980966275723101045b92

------------------------------------------------------------------------------------------------------------

   End Function: clone_policies.

------------------------------------------------------------------------------------------------------------

Back to Top

HCL Status

EZDAY2TOOLS - hcl_status: Use Cases

  • Collect UCS Inventory from list of vCenters and compare HCL inventory results in Intersight.

EZDAY2TOOLS - hcl_status: Obtain vCenter Inventory with vcenter-hcl-inventory.ps1

Install PowerShell - Mac/Linux

Run the PowerShell Script (Windows)

.\vcenter-hcl-inventory.ps1 -j inventory.json

Run the PowerShell Script (Linux)

pwsh
./vcenter-hcl-inventory.ps1 -j inventory.json

See example inventory.json file in examples/day2tools/hcl_status.

EZDAY2TOOLS - hcl_status: Compare Inventory to Intersight and Create Spreadsheet.

From the previous PowerShell module use the output file for input to ezday2tools.py in example 2024-04-10_09-49-27.json.

Linux

ezday2tools.py -p hcl_status -j 2024-04-10_09-49-27.json

Windows

python ezday2tools.py -p hcl_status -j 2024-04-10_09-49-27.json

See example Excel output in examples/day2tools/hcl_status.

Back to Top

Inventory

EZDAY2TOOLS - inventory: Use Cases

  • Collect Domain Inventory.
    • Contracts
    • Domain/Switch Profile(s)
    • Fans
    • Installed Firmware
    • Power Supplies
  • Collect Chassis Inventory.
    • Chassis Profile
    • Contracts
    • Fans
    • Installed Firmware
    • IO Modules (IFMs/IOMs)
    • Power Supplies
    • Slot Inventory - Accounting for X410 double slot, PCI Nodes, and B480 double wides
    • X-Fabric Modules
  • Collect Server Inventory.
    • Adapters
    • Contracts
    • Fans
    • GPUs
    • Installed Firmware
    • Memory - Available Memory/DIMM part numbers and installed slots
    • PCI Node - with GPU's
    • Power Supplies
    • Processors
    • Server Profile
    • Storage Controller - Including physical drives and virtual drives
    • TPM Chips

EZDAY2TOOLS - inventory: Get Server Identities from Intersight and Create Spreadsheet.

Linux

ezday2tools.py -p inventory

Windows

python ezday2tools.py -p inventory

See example output in examples/day2tools/inventory.

Example Output

tyscott@TYSCOTT-DESKTOP:~$ ezday2tools.py -p inventory

------------------------------------------------------------------------------------------------------------

   Begin Function: inventory.

------------------------------------------------------------------------------------------------------------

     * Querying `firmware/RunningFirmwares` for Inventory.
     * Querying `asset/DeviceRegistrations` for Inventory.
     * Querying `network/Elements` for Inventory.
     * Querying `fabric/SwitchProfiles` for Inventory.
     * Querying `fabric/SwitchClusterProfiles` for Inventory.
     * Querying `equipment/Chasses` for Inventory.
     * Querying `equipment/ExpanderModules` for Inventory.
     * Querying `equipment/IoCards` for Inventory.
     * Querying `chassis/Profiles` for Inventory.
     * Querying `compute/Blades` for Inventory.
     * Querying `compute/RackUnits` for Inventory.
     * Querying `compute/Boards` for Inventory.
     * Querying `pci/Nodes` for Inventory.
     * Querying `memory/Arrays` for Inventory.
     * Querying `storage/Controllers` for Inventory.
     * Querying `server/Profiles` for Inventory.
     * Querying `storage/VirtualDrives` for Inventory.
     * Querying `asset/DeviceContractInformations` for Inventory.

------------------------------------------------------------------------------------------------------------

   End Function: inventory.

------------------------------------------------------------------------------------------------------------

tyscott@TYSCOTT-DESKTOP:~$

Back to Top

Server Identities

EZDAY2TOOLS - server_identities: Use Cases

  • Collect UCS Server Identities and export to Spreadsheet.

EZDAY2TOOLS - server_identities: Get Server Identities from Intersight and Create Spreadsheet.

Linux

ezday2tools.py -p server_identities -fi

Windows

python ezday2tools.py -p server_identities -fi

Note: -fi pulls adds more details; without, primarily focused of function is WWNN/WWPN identities for server profiles.

See example output in examples/day2tools/server_identities.

Back to Top