Workflows are available from XMC version 8.1.5 as beta feature. Fully supported since XMC version 8.2 GA and XIQ Site Engine
- Import the sctript = Open the web GUI -> Tasks -> Workflow -> Import...
| Workflow name | Description | Comment | Version |
|---|---|---|---|
| XIQ-SE licensing calculation | The Workflow reports number of Pilot and Navigator licenses required by ExtremeCloud IQ - Site Engine. Check KB article on how to use it on Windows. | Define the email recipients. | v107 |
| Aggregated report Device Down | This workflow creates aggregated report over the time. Instead of 300 emails if 300 devices go down, you will get one email with a list of 300 devices. | Create Alarm for Device Down based on contact lost and as action assign this workflow. You can define the aggregation time in minutes in the workflow Input. Define email recipients. | 8.5.1.60v20 |
| Link Aggregate Alarm | This workflow creates one email for each link down event. Instead of 2 emails if the link goes down, you will get one email with all link details. | Create Alarm for Link Down based on selected trap (you can copy or modify the original alarm) and as action assign this workflow. Define email recipients. | 8.4.0.115v8 |
| ERS inventory | This workflow creates one email with CSV file attached. All ERS devices are there with IP, serial numbers, and many details. | Select ERS devices. Check your ERS devices do have defined Network OS. | 8.4.2.30v111 |
| ERS port counters | This workflow creates one email with CSV file attached. Ports with the defined property above the defined threshold are in the list. | Select ERS devices. Define property (e.g. Dropped on no resources), define threshold (e.g. 0), define email address. | 8.4.2.38v39 |
| Open ServiceNow Ticket | This workflow creates ticket in ServiceNow through the API call based on the alarm. | Define variables for ServiceNow (Instance, credentials, queue, priority). Create an alarm to trigger this workflow. | 8.4.2.38v3 |
| Aggregated Report Alarm History | This workflow creates an aggregated CSV report of alarm history. Columns in the CSV file are AlarmName, Source, Subcomponent, Occurrence. | The workflow can be executed or scheduled. You can define the aggregation time in seconds in the workflow Input. Define email recipients. | 8.4.3.24v28 |
| Universal Alarm Email List | This workflow sends an email to the recipient based on sysLocation. The translation from sysLocation to email address is defined in the CSV file. The first column in the CSV file is sysLocation. The second column is EmailAddress. | The workflow must be executed by an alarm. You can define the location of the CSV file. | 8.4.4.26v1 |
| Report configuration changes by email | This workflow sends an email to the recipient with the configuration changes detected. It compares last two archived configurations. New addition: it reports which users were logged into the switch in between the differing config archives, by inspecting XIQ-SE's syslog file (this additional function currently only works with EXOS/Switch Engine syslog messages, which need to be configured for severity "Info" in order to send login/logout syslog messages; but the rest of the workflow will still work with non EXOS/SwitchEngine devices as well) | The workflow can be executed by an alarm. Define the email recipients. | 22.6.13.9v33 |
| Extended Alarm Information to Email | The workflow contains the dictionary of CLI commands to be executed based on alarm name. The workflow determines the alarm name and based on the information in the dictionary the set of CLI commands are executed. The result is then send to email recipients. | The workflow must be executed by an alarm. Modify the dictionary in the workflow. Define the email recipients. | 8.5.3.66v6 |
| Report Congestions | The Workflow checks congestions on ports through SNMP and if congestion is detected then the email report is generated. | Define devices inside of the activity and threshold. Define the email recipients. | 8.5.5.30v67 |
| Workflow name | Description | Comment | Version |
|---|---|---|---|
| Uptime and Tech Support | Checks the uptime of each device (families: Wireless Controller, VSP, Summit Series, Catalyst, Extreme Access Series, VDX). If the uptime is lower then configured value and the device is not in maintenance then the workflow gathers tech support information and send an email. | Add XMC to devices with proper CLI credentials. Configure variables and email destination. | 22.3.1.1v90 |
| Gather Show Support | Workflow gathers show support information from devices (families: Wireless Controller, VSP, Summit Series, Catalyst, Extreme Access Series, VDX, SLX). The workflow should be executed by alarm or with right-click on the device. Workflow generates an email with tech support attached. | Configure the email destination. Create an Alarm to execute this workflow. Add Site Engine to the database with CLI credentials or define XMC credentials in variables. | 23.4.10.57v31 |
| Gather Show Fulltech Support | Workflow gathers show support information from devices (families: Wireless Controller, VSP, Summit Series, Catalyst, Extreme Access Series, VDX, SLX, Universal). The workflow should be executed by alarm or with right-click on the device. Workflow generates an email with tech support attached. On VOSS/Fabric Engine it gathers full tech support. | Configure the email destination. Create an Alarm to execute this workflow. Add Site Engine to the database with CLI credentials or define XMC credentials in variables. | 23.4.10.57v9 |
| Workflow name | Description | Comment | Version |
|---|---|---|---|
| Export Site Structure | Exports Site structure to the file or email. | Inputs: FileName including full path, the email address is optional. | 8.4.1.24v1 |
| Import Site Structure | Automatically creates sites and subsites based on input file | Inputs: File with site names. Parent site must exist. | 8.2.5.50v2 |
| Import Devices | Import devices to the database based on input file | Inputs: File with devices. The file contains IP (IPv4/IPv6), Nickname, Site, Profile. The workflow finishes quickly, added devices will start to appear in the XMC sequentially. | 8.4.4.26v6 |
| Import VLANs | Import VLANs to the Site based on input file | Inputs: File with VLANs. The file contains VlanID, VlanName. Chose method ADD (fails if the VLAN exists) or REPLACE (if does not exist then it creates the VLAN). Specify the Site. | 8.3.0.106v3 |
| Import VLANs to Sites | Import VLANs to Sites based on input CSV text | Inputs: CSV formated text with SiteName, VlanID, VlanName. Chose action: Check only (generates report), Add non-existing (Adds only non-existing VLANs) or Modify & Add (Renames existing VLANs and Adds non-existing VLANs). | 8.5.3.66v52 |
| Import VRFs and VLANs and Services from VSP | Workflow reads VRFs, VLANs, L2VSN, L3VSN from VSP, and import it to Service Defintions. | Inputs: Service Application, VSP device, or XA. The Service Definition is determined automatically = VSP must be assigned to the site with Service Definition. | 22.3.1.1v39 |
| Import End-Systems to XCA | This workflow reads the CSV file with MACs and descriptions. The workflow injects the content of the CSV file to the end-system group in Extreme Cloud Appliance through the API. The XCA must be in XMC and must have CLI credentials defined. The end-system group must exist. The maximum number of entries in one run is 100 for XCA version 04.36.02.0014 | Inputs: File with End-systems. The file contains MAC, description. | 8.3.0.111v4 |
| Import L2VSNs to XIQ-SE | Imports VLANs and L2VSNs from file to XMC Service Definitions and Service Applications. If Service Definition does not exist then it is created. If Service Application does not exist then it is created. If Vlan ID exists then it is updated. If NSI exists then it is updated. The goal is: You do not need to manually create each VLAN and ISID in XMC. | Inputs: File with Services | 23.4.12.3v9 |
| Create Device Groups from Sites | Based on the Site structure user groups will be created. Workflow stops if there is a name conflict: if a group with the same name already exists. Backup of the XMC is strongly recommended before the workflow execution. | Name of each site must be unique. A restart of XMC is mandatory after the workflow execution. | 8.4.0.115v25 |
| Change EXOS policy Rule model | This workflow address incompatibility of EXOS 30.5 with Policy Manager in XMC 8.4 and older. KB article. The workflow can be executed through ZTP+ process or manually. | CLI access must work, Policy domain must be assigned. ZTP+ settings | 8.4.3.10v29 |
| ZTP+ Remove Redundant IPs | During the ZTP+ process the switch can learn multip IPs from the DHCP server. This workflow can be executed after the EXOS device is onboarded and it does remove IPs from EXOS not registered in Site Engine. | Configure Site Actions to execute this workflow as part of ZTP+ process, select saving configuration or not. | 23.4.10.57v10 |
| ZTP+ Change the persona to VOSS | Workflow changes persona to VOSS from EXOS. Removes the device from the XMC and allow ZTP+ to happen. Tested with 5520/5420 platform. | Configure the VOSS firmware file name for the right platform, TFTP directory with the firmware. Configure Site Actions to execute this workflow as part of ZTP+ process. | 22.3.10.74v28 |
| ZTP+ Change the persona to EXOS | Workflow changes persona from VOSS to EXOS. Removes the device from the XMC and allow ZTP+ to happen. Tested with 5520 platform. | Configure the EXOS firmware file name, TFTP directory with the firmware. | 22.3.1.1v38 |
| Update PVI from CSV | Workflow reads VLANs and NSIs from CSV files and updates the Policy Vlan Islands in the specified Policy Domain. | Inputs:PVI_NSIs.csv,PVI_VLANs.csv, Policy domain, Force unlock. | 8.5.1.60v6 |
| Update PVI | Workflow updates th Policy VLAN Islands in the specified Policy Domain based on information provided in the input form. | Inputs:PVI NSIs, PVI VLANs, Policy domain, Force unlock. | 8.5.1.60v8 |
| Delete VLANs from Policy Domain | Workflow deletes VLANs from the policy domain without deleting those VLANs from switches. It is useful for migration to PVI. | Inputs:Policy domain, Comma separated list of VLANs, Confirmation. | 8.5.1.60v6 |
| ZTP+ Adding Commands per Port Template | Workflow executes commands to update the EXOS configuration. Define commands to execute per Port Template. The workflow replaces "{}" with the port. | Inputs:CLI Commands for each port template, CLI Commands for switch. | 22.3.1.1v6 |
| Clear Nicknames | Workflow removes Nicknames from all devices in the database except those without sysName (e.g. ICMP monitored). If the Nickname is not present then XMC display actual sysName. | Inputs:Confirm the action. | 8.5.1.60v6 |
| Onboard VSP | This workflow allows for automated onboarding of VSP Edge and is designed to be assigned to a Site, under Action tab, as a Custom Configuration Task. The workflow inputs can be set on the workflow itself (if all VSPs will be onboarded to the same Site) or can be set to ${<site-custom-variable>} where the appropriate variable has been set under the Site Custom Variables tab as category "Site", site the site itself (not Global), and type "String". The workflow inputs will determine whether the onboarded VSP is NAC enabled (this will both configure the VSP switch and add the VSP switch to the correct XMC AccessControl Engine Group) and whether the VSP is made into a DVR Leaf node. Auto-sense configuration is also applied if provided and any additional CLI config commands can also be applied at the same time. Activation of DVR Leaf mode, will trigger a VSP switch reboot at the end of the workflow. | Inputs: DVR Leaf enable/disable, NAC enable/disable, NAC Engine Group name, RADIUS attributes template, RADIUS shared secret, Location Group, Auto-sense voice I-SID/VLAN, Auto-sense Data I-SID, Auto-sense ISIS Authentication key, Auto-sense FA Authentication key, Additional CLI commands (Changes) | 23.4.12.3v105 |
| PaloAlto Firewall sync VLANs | This workflow get kicked by a Alarm watching about a the Firewall syslog message containg "commit". He wait 20 seconds and go back to the Firewall and read via API call the Interface data including the VLAN information. This data is than compared and synct with the coresponding VSP interface. As result the XIQ-SE follow automaticaly all VLAN adds and removes form the firewall. | Inputs: PAN_API_KEY, VSP_IP_ADDR, VSP_ISID_OFFSET, VSP_PORTS, VSP_VLAN_DELETE true/false, VSP_VLAN_SLPP true/false | 22.3.10.74v91 |
| Apply Config Template | Workflow to apply an ASCII config template containing variables. The embedded variables can be of three types: XIQ-SE Global or Site specific variables, in this preference order: local site, site parents, global; Device specific variables extracted from supplied CSV file; Device specific values extracted from device User Data 1-4. For the CSV variables, a CSV file must be provided by placing it on the XIQ-SE filesystem. See the "How-to-use" link | (How-to-use)(Changes) | 23.4.12.3v61 |
| Fabric Extend Onboard | Workflow to onboard newly provisioned VSPs with Fabric Extend. The first two activities will move the mgmt VLAN IP onto newly defined Fabric Extend VLAN and VRF. The middle activity, Apply Config Template, pushes an ASCII config template where variables can be dereferenced against site variables and/or a CSV file. The last activity, if enabled, configures a mgmt CLIP on the device, deletes the device from XIQ-SE and re-adds the device with its new mgmt CLIP IP. Both the ASCII config template and CSV file need to be uploaded to the XIQ-SE filesystem. This workflow is designed to be assigned to a Site, under Action tab, as a Custom Configuration Task | (How-to-use)(Changes) | 23.4.11.15v67 |
| Onboard Mgmt VLAN | Workflow to onboard a VOSS/Fabric Engine switch onto a dedicated switch mgmt VLAN/L2VSN | (How-to-use)(Changes) | 23.11.12.3v68 |
| Onboard Mgmt CLIP | Workflow to onboard a VOSS/Fabric Engine switch onto a dedicated switch mgmt CLIP | (How-to-use)(Changes) | 23.11.12.3v38 |
| Disable IQAgent | Workflow disables IQAgent on devices running Switch Engine, Fabric Engine, EXOS, VOSS. | Execute the workflow on one or multiple devices. | 22.6.10.67v10 |
| Fabric MultiArea Migrate | Workflow allows changing the ISIS area of a switch in a multi-area design where nodes need to be migrated to new areas. | (How-to-use)(Changes) | 23.2.10.82v64 |
| XIQ-C PSK update using QR code | Workflow is changing the PSK of a specific SSID on a XIQ-C. A QR codes will be generated and the PSK + QR-code is delievered by e-mail | you have to fillout the dialog fileds prompted during exection. The XIQ-C have to be part of the XIQ-SE inventory to get the login crendetials for the API calls. | 23.4.12.3v103 |
| reboot AP's | The workflow finds APs by LLDP and disable PoE, wait for 10 seconds, and enable the PoE. All switches like EXOS, ERS, VOSS, Fabric- and Switch-Engine are supported. Also any switch with have the public MIB for LLDP + PoE implemented. | 23.7.11.6v29 | |
| I-SID to Name syncing | The workflow uses a CSV-like input for I-SID to name binding and applied by SNMP against VOSS and Fabric Engine based switches. | the input is like this "123450,Demo-123450" | 23.7.11.6v52 |
| Bounce PoE | The workflow disables PoE, wait for 10 seconds, and enable the PoE. | Select port or multiple ports | 24.2.10.49v9 |
| Disable PoE | The workflow disables PoE on selected ports | Select port or multiple ports | 24.2.10.49v2 |
| Enable PoE | The workflow enables PoE on selected ports | Select port or multiple ports | 24.2.10.49v2 |
| Workflow name | Description | Comment | Version |
|---|---|---|---|
| Send System Time by Email | Gather system time from a group of EXOS devices sequentially and the aggregated result is sent by email. | Configure the email recipients before executing. | 22.3.1.1v24 |
| Update Device Notes - Group Membership | The workflow does modify device property to reflect groups the device belongs to. | Modify the Inputs to define what property you want to modify and what prefix you want to use. Run the workflow and save it as task. Schedule the task for periodic execution. | 8.2.4.24v13 |
| Assign Device to User Device Group based on SysObjectID | Automatically assigns the device to the user device group based on SysObjectID. All devices of the same type will be in the same user device group. | Inputs:File with mapping, SOAP credentials. The user device group must exist. Workflow can be executed automatically by Alarm (new device added). Workflow can be executed manually or scheduled. | 8.2.5.50v4 |
| Assign Device to User Device Group based on site | Automatically assigns the device to the user device group based on site. | Define SOAP credentials. User device group must exist (Use workflow "Create Device Groups from Sites" to create the user group structure.). Workflow can be executed manually or scheduled or part of the site actions. Multiple devices can be processed by one run. | 8.4.0.115v3 |
| Synchronize Vlans on Catalyst | This workflow creates VLANs on the Cisco Catalyst switch based on Site and Services VLAN configuration. The workflow deletes VLANs from the switch if the VLAN does not exist in the Site nor in the Services definition. The workflow renames VLAN name to match the Site or Services. | If a change has been made, the event is generated and configuration is saved. | 8.4.3.24v19 |
| Synchronize Vlans on ERS | This workflow creates VLANs on the ERS switch based on a combination of Site and Services VLAN configuration. The workflow deletes VLANs from the switch if the VLAN does not exist in the Site nor in the Services definition. The workflow renames VLAN name to match the Site or Services. | If a change has been made, the event is generated. | 8.4.1.23v20 |
| Synchronize Vlans on HPE | This workflow creates VLANs on the HPE switch based on Site and Services VLAN configuration. The workflow deletes VLANs from the switch if the VLAN does not exist in the Site nor the Services definition. The workflow renames VLAN name to match the Site or Services. | If a change has been made, the event is generated and configuration is saved. | 8.4.3.24v2 |
| Synchronize Vlans on ISW | This workflow creates VLANs on the ISW switch based on a combination of Site and Services VLAN configuration. The workflow deletes VLANs from the switch if the VLAN does not exist in the Site nor in the Services definition. The workflow renames VLAN name to match the Site or Services. | If a change has been made, the event is generated. | 8.4.3.24v6 |
| Synchronize Vlans on EXOS | This workflow creates VLANs on the EXOS switch based on a combination of Site and Services VLAN configuration. The workflow deletes VLANs from the switch if the VLAN does not exist in the Site nor the Services definition. The workflow renames VLAN name to match the Site or Services. | If a change has been made, the event is generated. | 22.6.10.70v58 |
| Disable unused ports | If the port is unused for more than X days then the port is set to Admin-Down state and ifAlias is configured. On EXOS and BOSS and FastPath and ISW devices, there is an option to save the configuration. | Variable PortDescription defines ifAlias prefix. Custom Inputs: Topology roles delimited by comma (XMC version 8.3 the roles are numbers starting from 0, XMC version 8.4 roles are "L2 Leaf,L2 Access,...", how many days should be the port down before workflow takes the action if you do want to save the changed configuration. What sites and subsites you want this workflow to execute. You can schedule the workflow execution in task scheduler. | 8.4.4.26v66 |
| Refresh Neighbor Devices | This workflow checks neighbor devices based on XMC link database and executes refresh of each neighbor. If the device goes down or up then the map is automatically updated. | Create Status Change Alarm and for both contact lost and contact established add action run task with this workflow. | 8.2.4.55v2 |
| Execute CLI commands in Enable mode | This workflow automatically enters the enable mode and passes the enable password. Then it executes user-defined commands. Both Single and Multi-device execution is supported. | The enable password must be configured in the CLI credentials. The Network OS must be one of the defined in the list. | 8.5.0.169v11 |
| XIQ AP import | This workflow automatically adds APs from Extreme Cloud IQ to XIQ-SE and to ExtremeControl. Make sure the APs support SNMP using the Network Policies and device templates. | You may consider to update the variables like NAC_GROUP or SHARED_SECRET if needed. | 22.9.11.11v275 |
| Check XIQ Connectivity Timeout | The workflow checks if the connection to XIQ is not available for more that X days and in case of the threshold is crossed it informs the recipients by email. | Define the threshold and email recipients. Schedule the workflow execution every day. | 22.9.10.70v16 |
| Check ICMP on Status Change | In case of SNMP failure the workflow checks ICMP. If both SNMP and ICMP fails then the alarm is created. PING only devices are ignored. See the alarm definition. | Define alarms, define where the workflow can store temporary data in the Input. Minimum version of Site Engine is 23.4.10 | 23.4.10.52v4 |
| Workflow name | Description | Comment | Version |
|---|---|---|---|
| Delete end-system from ExtremeControl | This workflow deletes End-System with specified MAC from the database. Can help with the implementation of GDPR "Right to be forgotten". | Various MAC address formats are accepted: lowercase, uppercase, dot delimited, colon-delimited, dash delimited, not delimited | 8.2.4.41v6 |
| Delete from ExtremeControl | This workflow deletes End-System with specified MAC or Username from the database. Can help with the implementation of GDPR "Right to be forgotten". | Various MAC address formats are accepted: lowercase, uppercase, dot delimited, colon-delimited, dash delimited, not delimited. The domain is not mandatory in the username. | 8.2.4.41v4 |
| Investigate End-System History | Workflow generates an email with table of end-system events based on defined criteria. | Input: MAC or Username, Date range. Define email recipients before use. The InstallDirectory is referring to the XMC installation path. | 8.2.5.50v48 |
| Remove all End-Systems from group | This workflow removes all end-systems from the end-system group. It can be scheduled to execute periodically. | Define an end-system group in variable "EndSystemGroup" default end-system group: "Access Expired". | 23.4.12.3v21 |
| Import credentials from MySQL to local repository | Workflow connects to an external MySQL server and read usernames and passwords. These are then injected to the local password repository. Can be executed once, can be scheduled. | Input: SQL server, SQL username, SQL password, SQL database, SQL table, Column with usernames, Column with passwords. | 8.4.0.115v13 |
| RFC3580 for ISW through CLI | This workflow delivers missing RFC3580 feature on the ISW for Macauth. If it is mac authentication then it configures on the switch VLAN based on authorization VLAN in the radius response. The configuration is done through ssh/telnet. When the end-system is disconnected it returns the port VLAN to default. | Define disconnected PVID. Create 2 notification rules. State Change and New End-System Added. | 8.4.2.38v11 |
| RFC3580 for ISW through SNMP | This workflow delivers missing RFC3580 feature on the ISW for Macauth. If it is mac authentication then it configures on the switch VLAN based on authorization VLAN in the radius response. The configuration is done through SNMP. When the end-system is disconnected it returns the port VLAN to default. | Define disconnected PVID. Create 2 notification rules. State Change and New End-System Added. | 8.4.2.38v2 |
| Limit number of End-Systems with the same Username | The workflow reads all end-systems and process only those in Accept state. If the number of end-systems with the same name is higher than the threshold then one of the following will happen: UserName can be added to the defined User Group and all end-systems are reauthenticated. All MACs for that username are added to the defined ES group and all those end-systems are reauthenticated. Only older MACs for that username are added to the defined ES group and are reauthenticated. | Define the number of allowed end-systems with the same username, action what will happen, group to add MACs/Username. Schedule the workflow execution. | 8.4.2.38v2 |
| Add MAC to the Blaclist to inform user | This workflow adds MAC address to ES group and creates a event. | Description can be defined and end-system group can be defined. | 8.5.0.169v6 |
| Report 802.1X Rejects | Workflow generates an email with table of User Names with too many rejects in last X hours. | Input: Number of Hours. Threshold. Email Address. | 8.5.5.30v2 |
| Import FDB from ERS to NAC | Workflow reads the MAC address table from ERS devices and imports those to End-System groups, creates NAC profiles and NAC rules. If duplicate MAC is seen on more VLANs then VoIP vlan makes precedence. If duplicate MAC is not seen on VoIP VLAN then the duplicate MAC is not imported. | Input: Site with VLAN names, NAC config name. VoIP VLAN ID, Name prefix | 21.9.10.90v19 |
| Import PaloAlto IoT devices to NAC | Workflow reads the device information form Palo Alto IoT Cloude service and imports those to End-System groups. | Input: Customer name, API-ID, API-Key | 22.3.10.74v58 |
| Import Policy Mappings from CSV to NAC | Workflow reads the policy mappings from CSV file and imports it to the NAC. The format of the CSV file is fixed. Site engine must be minimum version 22.9. | Input: FileName | 22.9.10.54v39 |
| Name | Workflows | Description | How To | Version |
|---|---|---|---|---|
| Add NSI to Vlan Egress = After Policy Enforcement | Run Add NSI After Policy Enforcement, Add NSI prefix to vlan egress | There maybe tagged egress vlans in the policy profiles. This workflow ensures these egress vlans are mapped to proper NSI on EXOS switch. This check is executed on each reachable device in the policy domain, when the enforce is completed. | Import both workflows. The "Run Add NSI After Policy Enforcement" should be executable by Alarm. Configure the path to the "Add NSI prefix to vlan egress" workflow. Create Alarm to execute the workflow if the policy domain is enforced. Create topology if you do not have any. Create Service and Application. Assign Topology to the Site. Assign Service Definition to the Site. | 8.4.0.107v11 22.3.1.1v37 |
| User authenticated on domain computer | Add MAC to Domain Computers, Clear old End-Systems in the group | "Add MAC to Domain Computers" is executed when the computer authenticates. The MAC address is added to End-System and the timestamp is created (updated). Consequent User authentication can be combined with the condition of the End-System group. "Clear old End-Systems in the group" checks if the timestamp is older than X hours and old End-Systems are deleted from the group. | Create End-System group "Domain Computers". Create User Group Username starts with host/. Create notification Domain authentication - after logoff. Create notification Domain authentication - after boot. Configure inputs for workflows. Schedule the workflow execution to clean old end-systems from the End-Systems group. Create NAC rule | 8.3.1.9v3 8.3.1.9v5 |
| IGE Governance Regime | Governance Regime Export, Governance Regime Import | Governance Regime can be exported and then imported to other XMC instance. You can share your regime with the community. Professionals can share regimes with their customers. | You may need to modify the InstallDirectory variable. During Export, you need to specify the name of the regime. The regime is exported to the file system InstallDirectory/GovernanceEngine/audit-tests/ as tgz file. The export workflow can email the regime. Transfer the file to the new system. During the import select if imported tests will be marked read-only or editable. | 8.4.1.23v7 8.4.1.23v4 |
| Workflow Name | Description | How To | Version |
|---|---|---|---|
| Day 0 Create Fabric | Creates Fabric through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 1 Create Tenant | Creates Tenant through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 1 Create EPG | Creates VRF, Port Channels, EndPointGroup through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress, PortChannelSpeed, PortChannelNegotiation, PoName to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Add Ports to Tenant | Adds ports to existing Tenant through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Add Ports to EPG | Adds ports to existing EndPointGroup through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress, PortChannelSpeed, PortChannelNegotiation to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Create PortChannel | Creates PortChannel through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress, PortChannelSpeed, PortChannelNegotiation to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Create VRF | Creates VRF through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Delete Fabric | Workflow deletes existing Fabrics through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Delete Tenant | Workflow deletes existing Tenants through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Delete PortChannel | Workflow deletes existing Port Channels through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Delete VRF | Workflow deletes existing VRFs through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| Day 2 Delete EPG | Workflow deletes existing EPGs through Extreme Fabric Automation. | EFA must be in the XMC with valid CLI credentials. Modify variable EFAaddress to reflect your environment. | EFA version 2.2.0, XMC version 8.4 |
| EFAv210 package | All EFA workflows zipped to one package. | Unzip and import. | EFA version 2.1.0, XMC version 8.2 |
| Whole EFA package | All EFA workflows zipped to one package. | Unzip and import. | EFA version 2.2.0, XMC version 8.4 |
| Workflow Name | Description |
|---|---|
| EXOS Switch Audit System Disabled | This workflow is used as part of an educational training video. It does not work as standalone workflow. |
| Store Active Clients in Cloud Database | This workflow is used as part of an educational training video. It does not work as standalone workflow. |
| Workflow name | Description | Version |
|---|---|---|
| Deploy Insight VM (How-to-use) | Workflow to deploy an IAH Insight VM on EXOS or VOSS capable switch. For EXOS it works on standalone switches and Stacks. This workflow is designed to be run manually, by selecting the switch and executing the workflow against it. The VM image must be already added to XIQ-SE Firmware under /tftpboot/firmware/images/ ( or as set in workflow variable const_XMC_IAH_IMAGE_PATH ). Note that files larger than 4096MB cannot be transferred using the web interface, in which case the image needs to be FTPed directly to XIQ-SE. The workflow takes care of transferring the VM image to the switch (FTP with VOSS and SCP with EXOS) unless the image, with the right size is already found to be on the switch, in which case the existing file is used to save time (the image transfer with FTP/SCP can take up to 15 minutes). The workflow inputs will determine which sideband port to use as well as CPU and memory resources to assign to the VM. This data is then used to install and start up the VM on the target switch. The workflow can be run on one or more switches at the same time. Input values for EXOS and VOSS will be somewhat different though these can be supplied as ${variable} where the relevant site of the switch will be used to obtain values for the variable. | 22.6.12.11v95 |
| Upgrade FIGW (How-to-use) | Workflow to upgrade the FIGW VM on an Insight/IAH capable VSP7400/VSP4900/5720. The workflow will expect to already find a FIGW running on the target switch, and will simply back that up, delete it, re-deploy the new (or same) version of FIGW, then re-apply the config to the new FIGW. This workflow is designed to be run manually, by selecting the VSP and executing the workflow against it. Workflow can be run on multiple switches at the same time. (Changes) | 22.9.12.14v42 |
The software is provided as-is and Extreme Networks has no obligation to provide maintenance, support, updates, enhancements, or modifications. Any support provided by Extreme Networks is at its sole discretion.
Issues and/or bug fixes may be reported on The Hub.
Be Extreme