...
Note | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
For local installation customers, ProVision versions 7.0.0 and newer have upgraded software requirements (in red, below):
Note on MySQL: We recommend setting the max_allowed_packet setting in the MySQL configuration file to 128MB (or similar) to account for the typical dataset size handled in ProVision. |
...
Expand | |||
---|---|---|---|
| |||
Using Router File ConnectorsStep 1Generate a router response data text file (it should be named “cisco_router_data.txt”, “juniper_router_data.txt” or “arista_router_data.txt”) and place it in ProVision's /data directory. To generate the router response, run the following commands:
Step 2Create a new 'Router' in ProVision, selecting the appropriate file connector as the Router Make type - CiscoFile, JuniperFile, or AristaFile. Note: These connector types are only used for this direct data import process - do not select these for standard ProVision router/session creation, as management functions (config pushes, session states, etc) do not obtain a router connection while using File Connectors. Step 3Navigate to Admin → Data Import → Peering BGP Import. Select the appropriate exchange, then the File Connector Router that you created. Click "Load Sessions", and the sessions contained within the router data file will be available to review, select, and/or import into ProVision. Via APIv2The same import process may also be performed via APIv2, using the following information: 1) "router id" contained within the URL for an already-created File Connector Router 2) "ix_id" (the ID of the exchange) in the body 3) "router_response" (the output from the router) in the body The APIv2 details can be view from ProVision swagger documentation at ['instance']/dev/swagger/spec.php?family=peering#/default/single_parse_bgp_info That command will parse the router output and return an array of detected sessions and groups. The sessions and groups then need to be individually added using POST /peering/sessions and POST /peering/peergroups. |
...
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
Example .csv OutputTo export .csv information for the linked resource in the Resource Linkage Gadget, click on the wrench icon for the linked resource, then select "Export to .csv". The file will download from your browser. The .csv outputs data in two columns, arranged as Field Name (column 1) and Field Data (column 2). Standard resource metadata fields ("Name", "Section","Category", "Created", "Modified") will always be exported for a resource. Additional custom fields - those that have been added to the Section / Resource Field Gadget and contain data - will also be exported if they exist, and included after the standard metadata information. In this example, "Hostname", "Resource Holder ID", "Contract Number", "URL", "Text Area", "Text Input", and "Status" are custom fields.
|
For additional information on adding fields to Sections, the Resource Field Gadget, and the Resource Linkage Gadget, see: Customizing Sections , Customizing Fields, and Gadgets.
...
For additional information on how to edit Admin Preferences or Scheduler Tasks, see Admin Preferences and Scheduler Tab.
ACP Improvements
For detailed information on 6connect ACP on ACP (API Composer Platform), see ACP Overview Documentation or or request a demo at info@6connect.com.
Admin ACP Settings
IM - 3472: Added ACP Instance Settings to Admin Preferences
...
See APIv2 docs from your instance at: https://host.com/[your instance]/dev/swagger/spec.php?family=peering
Or, public APIv2 docs at: https://cloud.6connect.com/APIv2/spec.php?family=peeringAPIv2 - Peering public documentation.
Bug Fixes/Minor Improvements
...