Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DOC and version 7.3.0-7.3.2

...

Note
titleLocal Software Requirements Update

For local installation customers, ProVision versions 7.0.0 and newer have upgraded software requirements (in red, below):


Required

Link

Operating System

Linux/BSD/OSX


Apache

 Apache 2.4

http://httpd.apache.org/

PHP

PHP 7.1

http://php.net/downloads.php

MySQL

MySQL 5.7

http://www.mysql.com/downloads/


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
titleUsing File Connectors...

Using Router File Connectors

Step 1

Generate 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:


terminal length 0
show bgp ipv4 unicast sum
show bgp ipv4 unicast neighbor
show bgp ipv6 unicast neighbor
show bgp neighbor | display xml | no-more
show bgp group | display xml | no-more
terminal length 0
show ip bgp summary
show ip bgp neighbors


Step 2

Create 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 3

Navigate 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 APIv2

The 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
titleExample Output

Example .csv Output

To 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. 

Name

A QA Entry 3 Child

Section

Resource Holder

Category

QA

Created

2020-01-30T10:28:42-0800

Modified

2020-02-05T16:20:49-0800

Hostname

test.com.

Resource Holder ID

123

Contract Number

12345

URL

http://google.com

Text Area

Some Text Box Information

Text Input

Some Data Here

Status

☻ Active

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

...