DescriptionAnnouncing Exinda Management Center 1.0.0
Release Date: March 31, 2015
- Exinda Management Center 1.0.0 only supports appliance firmware versions 7.0.2 Update 1 and 7.0.3.
- Exinda Management Center 1.0.0 is available as VMware, XenServer, and SaaS subscription.
Installing a virtual machine instance of Exinda Management Center 1.0.0
- Xen Server
http://updates.exinda.com/oc/virtual/xen/1.0.0/Exinda-MC-126.96.36.1995.xvaPlease read the Install Guide for instructions for installing Exinda Management Center.
Size in bytes: 1,615,156,736
Multi-Tenant Policy Configuration for Multiple Appliances
- Exinda Management Center supports creating an Optimizer policy tree (including circuits, virtual circuits, policy sets, and policy rules) associated with a group of appliances. When the configuration is sent to the appliances, then all the appliances in the group receive the policy tree configuration. Multiple appliance groups can be created each with separate policy.
- Policy sets are used to group the policy rules. These policy sets can then be assigned to the multiple virtual circuits in various appliance groups.
Supported components for building configuration
- The following components are supported: network objects, schedules, custom applications
Map circuits to multiple named bridges via the Circuit Type object.
- Appliance bridges are mapped to the circuit types, which are mapped to circuits. For example, you can map appliance bridges to one circuit type and two other bridges to another circuit type.
Network Objects use the Local Network Object to determine its location
- When a network object is sent to an appliance, the network object is compared to the applianceÕs local network object to determine the network objectÕs location.
- [D-04340] Help is not complete. We expect the online user documentation to be updated on or about April 22.
- [D-04354] Renaming the current appliance group name will not update the name in the header of the left blue navigation menu. To force it to change, select a different appliance group, then reselect the newly named appliance group.
- [D-04357] When moving an appliance to the tenantÕs unallocated (Not Deployed) group, it will still be shown in the appliance groupÕs appliance list. This is a display issue. To force a refresh of the list, move to a different page such as the library, then back to the appliance group.
- [D-04065] Upon reordering virtual circuits in the Optimizer Policy Tree, the Send Configuration icon that is used to initiate sending the configuration to the appliances does not appear. To force it to appear, you can open any form for editing and press the Update button without making any changes.
- [D-04089] Upon updating a policyÕs type (eg. such as changing from Optimize to Ignore) within a policy set, if the policy is saved but the policy set is not saved, the Send Configuration icon that is used to initiate sending the configuration to the appliances does not appear. To force it to appear, you can open any form for editing and press the Update button without making any changes.
- [E-01581] Acceleration policies are not validated against the licenses on your appliances. That is, you can send down acceleration policies to appliances that are not licensed for acceleration. However, this configuration will not work on those appliances.
- [D-04328] Built-in apps cannot be edited. You can edit the app and the app group that it may belong to using the CLI editor. (Note: In the next release, you will not be able to edit the built-in app, however, you will be able to replace the built-in app with a custom app.)
- [B-03739] Circuits cannot yet be renamed.
- [B-04252] Virtual circuits cannot yet be renamed.
- [B-04253] Policies cannot yet be renamed.
- [B-04666] Schedules cannot yet be renamed.
- [B-04665] Custom applications cannot yet be renamed.
- [B-04667] Network objects cannot yet be renamed.
- [E-01426] Creating and editing application groups is not yet an available feature. The system will allow you to use standard application groups when defining policies or virtual circuits. To edit a standard application group, it is recommended to use the CLI editor in the system to modify the application groups:
?> application-group Òapp group nameÓ application Òapp nameÓ
To create policy that uses an application group, you can create a policy where each application in the application group is specified in the policy filter.