The requirements that apply to every VCF Extension — VCF Operations version, Cloud Proxy, TLS, certificate handling and registry access — are defined once in Technical and Security Requirements.
This page describes only what is specific to VCF SAN Insight: the permissions required on the fabric switch, the connection to the device and the adapter fields.
| Component | Minimum | Verified with |
|---|
| VMware Aria Operations (VCF Operations) | 8.10.0 | current 9.x release |
| Brocade Fabric OS | 9.2 | 9.2 |
| Cisco NX-OS (MDS 9000) | to be confirmed in the deployment card | to be confirmed in the deployment card |
| Category | Description |
|---|
| Broadcom Brocade account | A dedicated read-only account on the switch. The account must be allowed to read the fabric, switch, port and zone configuration and the performance counters. |
| Cisco MDS account | A dedicated read-only account on the switch or director, allowed to use NX-API for the inventory and the interface counters. |
| One adapter per switch | Each adapter instance connects to a single fabric switch. A fabric with several switches is covered by one adapter instance per switch, and the relationship model joins them into one fabric. |
| Cloud Proxy to switch | HTTPS on port 443 from the Cloud Proxy belonging to the collector group to the management interface of the switch. |
| TLS | The certificate of the switch management interface is validated against the system trust store. Self-signed certificates are supported through the Skip TLS certificate validation parameter, intended for lab or explicitly accepted targets. |
- SSH as
root to the Cloud Proxies belonging to the collector group where the adapter is to run. - Log in to the registry:
docker login registry.indevops.com. Use the Harbor robot account designated for that deployment, provided by Indevops. - Pull the image:
docker pull <IMAGE NAME>. The image name is shown on the release page for the version being installed.
- Download the PAK file matching the pre-pulled adapter image.
- In VCF Operations go to
Data Sources > Integrations > Repository > Add and upload the PAK file, selecting both Install the PAK file even if it is already installed and Ignore the PAK file signature checking. - Complete the installation wizard.
- Go to
Administration > Integrations > Repository, filter for INDEVOPS and select the VCF SAN Insight brick. - Select
ADD ACCOUNT. - Fill in the credentials and the instance parameters below.
One credential type, SAN credentials, shared by both vendors.
| Field | Definition |
|---|
Username | Account name on the fabric switch |
Password | Password of that account |
| Field | Default | Definition |
|---|
Name | — | Unique name of the adapter instance |
Description | — | Free-text description of the instance |
Vendor | Brocade | Producer of the device this instance connects to: Brocade uses the Brocade REST API, Cisco MDS uses Cisco NX-API. Both share the same object model. Part of the instance identity. |
API Host | — | Hostname or IP address of the management interface of the switch |
API Port | 443 | Port of the management API |
Credentials | — | Account used for collection, see above |
Collector / Group | — | Collector group that runs the adapter; must contain a Cloud Proxy with the image pre-pulled |
Skip TLS certificate validation | false | Disables certificate verification when connecting to the API. Insecure; keep false on production systems. |
Collect Info events | false | Whether info level fabric events are collected |
Collect Warning events | false | Whether warning level fabric events are collected |
Collect Immediately events | false | Whether events flagged immediately are collected |
Collect Critical events | false | Whether critical level fabric events are collected |
Adapter Memory Limit (MB) | 1024 | Maximum memory the adapter container may use |
Log Level | Normal | Logging verbosity: Debug, Normal or Trace |
