Classic-Central

Classic Central Workflows

This repository contains Python based workflows & code samples that utilize Classic Central's automation capabilities and the Python SDK pycentral

Classic Central REST APIs

• Device Provisioning
  • Create a group (Template-based group)
  • Upload Configuration Template to Group
  • Move Devices to the newly created Group.
  • Create a Site
  • Move Devices to the newly created Site.
• Device Onboarding
  • Assign Devices to Central Application Instance
  • Provide Devices with Central Subscriptions.
  • Create a template group (Template-based group)
  • Upload Configuration Template to Group
  • Move Devices to the newly created Group.
  • Create a Site
  • Move Devices to the newly created Site.
• MSP Customer Onboarding
  • Create a customer account within the Greenlake MSP account
  • Install an Classic Central instance in the customer account & set the default group.
  • Move & assign subscriptions to devices in the customer's Central Instance
  • Optional Steps
    • Create a Site in the customer's Central instance
    • Move Devices to the newly created Site.
• MSP Customer Deletion
  • Unassigns all devices & licenses within the customer's Classic Central Instance. The devices & licenses will be moved back to the MSP's inventory.
  • Uninstall the customer's Classic Central instance
  • Delete the customer's Greenlake Instance
• Inventory to Excel Workflows
  This workflow creates excel files populated with device details from devices currently in inventory.
• AP CLI Workflows
  Access point(AP) config workflows use direct command line interface(CLI) commands to configure APs in an Classic Central group or directly to an AOS10 AP.
• WLAN Workflows
  This workflow can be used to create and manage WLANs in groups on an Classic Central.
• Detailed Central Device Inventory
  This workflow can be used to fetch additional details for device inventory in Classic Central & export it as a CSV.
• Device Inventory Migration This workflow automates the migration of multiple devices between two Classic Central accounts.
• User Provisioning
  This workflow can be used to provision new users to HPE Greenlake and Classic Central.
• Bulk Renaming of APs (with CSV)
  This workflow can be used to rename access points in Classic Central with a custom CSV upload of serial numbers and names.
• Connected Clients
  • Gather connected client information based on site name and time frame
  • Output csv files are generated and created within workflow folder
• Classic Central Postman Collection
  Postman is a popular tool used to test HTTP Requests to API endpoints. Classic Central offers a Postman collection and Postman environment that you can use to test REST APIs with Classic Central.

To manage REST APIs in Classic Central, go to MAINTAIN -> ORGANIZATION -> PLATFORM INTEGRATION -> REST API.
Learn more about Classic Central REST APIs here.

Classic Central Streaming API

• Streaming API Websocket Client Application The sample script in this section contains sample websocket client application based on python. The sample python script would establish a websocket connection and decode the google protobuf message to human readable format.

To manage Streaming APIs in Classic Central, go to MAINTAIN -> ORGANIZATION -> PLATFORM INTEGRATION -> STREAMING.
Learn more about Classic Central Streaming APIs here.

Classic Central Webhooks

• Webhook Client application The sample script in this section would start a HTTP(s) client to receive Alerts from Classic Central via webhooks.

To manage Webhooks in Classic Central, go to MAINTAIN -> ORGANIZATION -> PLATFORM INTEGRATION -> WEBHOOKS.
Learn more about Classic Central Webhooks here.

For more information about Classic Central, refer here