| 1 |
Please confirm that this is a request for a fresh install. Please circle one option in the
Response column. |
Yes / No If Yes, this is a fresh install, please continue with this table. If No, this is an
upgrade, then please go to for Upgrades only table
below. |
| 2 |
Please provide the collector version you would like to install. NOTE: Please install the
latest available version that is compatible with your SevOne NMS, SevOne Data Insight, APIC, and ACI
MSO versions. Please refer to the Compatibility Matrix for version compatibility
details. |
<enter version here> |
| 3 |
Have you verified the checksum of the installer file? NOTE: If you do not know how to verify
the checksum, please refer to SevOne SDN Collector Solution Installation Guide >
Configuration > Step-3. If you are still not able to verify the checksum, please
contact IBM SevOne Support. |
Yes / No |
| 4 |
Have you checked and verified the version numbers of your SevOne NMS, SevOne Data Insight,
SOA, Docker, APIC, and ACI MSO? If Yes, please provide the current versions of your setup in the
Response column. NOTE: Please refer to the Compatibility Matrix below for version compatibility
details. To check the docker version, please run the following command on the collector and
augmentor VM: $ docker -v To check the SOA version, please run the following command on the
NMS appliance: $ docker ps | grep soa If you do not have access to shell prompt, please
contact IBM SevOne Support. |
- SevOne NMS Version:
- SevOne Data Insight Version:
- SOA Version:
- Docker Version:
- APIC Version:
- ACI MSO Version:
|
| 5 |
Have you checked the license capacity on NMS to accommodate the devices and objects which
will be created by the collector? If Yes, please provide the total number of devices/objects and
other information available in your setup in the Response column. NOTE: If you are unable to locate
this information, please contact your SDN Cisco ACI System Administrator directly. |
Devices/Objects Total Number
- APICs:
- Spine Switches:
- Leaf Switches:
- Physical Interfaces:
- Port Channels:
- Tenants:
- Application Profiles:
- Endpoint Groups:
- Endpoints:
- Static Endpoint:
- Bridge Domains:
- Private Network (VRFs):
- Contracts:
- Hypervisors:
- Virtual Machines:
- External Switches:
- Tunnel:
|
| 6 |
Please provide the NMS appliance IP address / Virtual IP address and protocol (https or http)
details. NOTE: The collector is installed on this appliance. |
<enter IP address / Virtual IP address here <enter protocol here> |
| 7 |
Please provide the system configuration details (RAM, Hard disk size, and CPU) of SevOne NMS.
NOTE: These are the system configuration details for SevOne NMS appliance where the deployment
script will be executed from and where the collector will be sending data to. If you are unable to
locate this information, please contact IBM SevOne Support. |
<enter configuration details> |
| 8 |
Do you want to distribute devices created by the collector among all or some peers of the NMS
cluster? NOTE: If you want to distribute devices to some peers only then, please provide the IP
addresses / peer names of those selected peers in the Response column. |
<All / Some> <If Some, please enter IP addresses / peer names of selected
peers> |
| 9 |
Please provide the NMS appliance username for an administrator-level account. |
<enter NMS appliance username here> |
| 10 |
Is password for NMS ready to share during the installation/upgrade session? Please circle one
option in the Response column. NOTE: Please ensure all passwords are available prior to the
session. |
Yes / No |
| 11 |
Do you want to collect information from multi-site manager? Please circle one option in the
Response column. If Yes, please provide the details of MSO in the Response column. NOTE: Please
ensure all passwords are available prior to the session. |
Yes / No <enter protocol here> <enter IP address here> <enter Username
here> <Password availability (Yes / No)> |
| 12 |
Do you want to skip adding a prefix to the device names of Spines, Leaves, and APICs? Please
circle one option in the Response column. |
Yes / No |
| 13 |
Do you want to add a prefix for the NMS alert summary? Please circle one option in the
Response column. |
Yes / No |
| 14 |
Please provide the details of an individual APIC for each site along with the site name and
device name prefix in case you do not want to collect information from multi-site manager. In case
of multiple sites, please provide details for each site. NOTE: Please ensure all passwords are
available prior to the session. |
Site-1 Protocol: <enter protocol here> IP Address: <enter IP address here>
Username: <enter Username here> Password Availability: <Yes / No> Site Name: <enter
site name here> Device Name Prefix: <enter device name prefix here> Site-2 Site-3 . .
Site-N |
| 15 |
Please provide the version of ACI that is running on APICs. NOTE: Please check the exact
version details on the login screen of APIC. |
<enter version here> |
| 16 |
Do you want to collect health and fault statistics for ACI physical devices? Please circle
one option in the Response column. |
Yes / No |
| 17 |
Do you want to collect traffic statistics for ACI physical devices? Please circle one option
in the Response column. |
Yes / No |
| 18 |
Do you want to collect health and fault statistics for ACI policy model? Please circle one
option in the Response column. |
Yes / No |
| 19 |
Do you want to collect traffic statistics for ACI policy model? Please circle one option in
the Response column. |
Yes / No |
| 20 |
Do you want to collect ACI faults and create alarms in the PAS? Please circle one option in
the Response column. |
Yes / No |
| 21 |
Do you want to filter and create alarms only for specific ACI faults? If Yes, please provide
codes for those faults in the Response column. NOTE: To search for fault codes, please refer to
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/all/syslog/guide/b_ACI_System_Messages_Guide.html |
<enter codes for faults here> |
| 22 |
Do you want to modify the default mapping of severity? If Yes, please provide mapping details
in the Response column. NOTE: The following table represents the default mapping for severity. APIC
to SevOne NMS Severity Mapping for Alerts
| APIC |
NMS |
| Critical |
Alert |
| Major |
Critical |
| Minor |
Error |
| Warning |
Waring |
| Info |
Notice |
| Cleared |
Notice |
|
<enter mapping details here> <Accepted keywords are emergency, alert, critical,
error, warning, notice, info, and debug>
|
| 23 |
Do you want to collect data for topology report? Please circle one option in the Response
column. |
Yes / No |
| 24 |
Do you want to collect health & fault statistics on ACI connected hypervisors and virtual
machines? Please circle one option in the Response column. |
Yes / No |
| 25 |
Do you want to collect statistics on ACI connected hypervisors and virtual machines? Please
circle one option in the Response column. |
Yes / No |
| 26 |
Do you want to collect statistics on external switches visible to the ACI fabric? Please
circle one option in the Response column. |
Yes / No |
| 27 |
Do you want to use pre-existing SNMP devices? Please circle one option in the Response
column. NOTE: If you select Yes, all SNMP devices will be renamed to incorporate the collector
naming convention. |
Yes / No |
| 28 |
Do you want to enable Self-monitoring feature for the collector? Please circle one option in
the Response column. NOTE: Once enabled, collector will create a device in NMS and monitor the
performance and statistics related to the collector. It will then store this data as
objects/indicators in the device created. |
Yes / No |
| 29 |
Have you checked the reachability of APIC/MSO from the collector PAS? Please circle one
option in the Response column. NOTE: Please check the reachability by running the following command.
If you do not have access to shell prompt, please contact IBM SevOne Support. curl -k
--location --request POST 'https://<apic-ip>/api/aaaLogin.json' \ --header 'Content-Type:
application/json' \ --data '{ "aaaUser": { "attributes": { "name": "<apic-username>", "pwd":
"<apic-password>" } } }' MSO connectivity: curl -k --location --request POST
'https://<mso-ip>/api/v1/auth/login' \ --header 'Content-Type: application/json' \ --data '{
"username": "<mso-username>", "password": "<mso-password>" }' |
Yes / No |