1 About this Guide
2 Introduction to maxView Storage Manager
This section introduces the maxView Storage Manager software, explains the concept of “storage space” and provides a checklist of getting-started tasks.
3 Installing maxView Storage Manager
4 Exploring maxView Storage Manager
This section familiarizes you with the main features of the maxView Storage Manager graphical user interface. It describes how to start and login to maxView Storage Manager. It also explains how to get help and log out of maxView Storage Manager when you are finished working with the application.
5 Building Your Storage Space
6 Protecting Your Data
7 Modifying Your Storage Space
This section provides additional scenarios for creating and modifying arrays and logical drives. It explains how to check your logical drives for bad or inconsistent data; optimize controller and logical drive performance; move arrays and logical drives; and perform advanced operations, such as creating a split mirror backup array.
8 Working with maxCache Devices
9 Working with maxCrypto™ Devices
10 Working with Self Encrypting Drive (SED) Based Encryption
11 Working with Security Protocol and Data Model (SPDM)
12 Maintaining Physical Devices
- 12.1 Viewing Device Properties
- 12.2 Multi Actuator Drives
- 12.3 Locating Drives in Your Storage Space
- 12.4 Working with Physical Device Error Counters
- 12.5 Refresh SED Security Status
- 12.6 Working with Failed or Failing Disk Drives
- 12.7 Erasing a Disk Drive
- 12.8 Initializing and Uninitializing Disk Drives
  This section describes how to initialize/uninitialize disk drives to enable the erased drive, erase data and meta-data (including logical drive information) from the disk drives (and SSDs) in your storage space. You can initialize or uninitialize individual disks, or use the wizard to initialize/uninitialize all disks on a controller.
- 12.9 Setting the Physical Drive Boot Priority
  Use this option to set the boot priority of a physical device to Primary, Secondary, Primary and Secondary, or None (default). A controller can have only one physical (or logical) device as the primary or secondary boot device. When you select a new physical device as the primary/secondary boot drive, the boot priority of the existing primary/secondary boot drive is overwritten and set to None.
- 12.10 Working with Controllers
- 12.11 Working with Connectors
- 12.12 Updating Controller, Enclosure, Backplane, and Disk Drive Firmware
13 Monitoring Status and Activity
This section describes how maxView Storage Manager helps you monitor status and activity in your storage space.
14 Managing Your Storage Space
15 Solving Problems
This section describes how to troubleshoot the components in your storage space.
16 Silent Installation on Windows and Linux
17 Configuring SNMP Notifications on Windows and Linux
18 Using the maxView Plugin for VMware vSphere 7 HTML5
19 Using the maxView Plugin for VMware vSphere 8 HTML5
20 Using maxView Storage Manager with HBAs and Non-RAID Mode Controllers
21 Selecting the Best RAID Level
22 Icons At-a-Glance
23 Smart Controller Device Status
24 Display Properties of a Controller, Array, Logical Device, and a Physical Device
25 maxView Video Tutorials
26 Revision History
Microchip Information

12.11.2 Changing the Backplane Discovery Protocol Setting

A discovery protocol is the connector mode protocol that discovers the attached backplane on the connectors of the Adaptec Smart Storage Controller. Following are the supported backplane discovery protocols in maxView:

AutoDetect (With SAS/SATA fallback): The controller firmware attempts to automatically detect the discovery protocol of the backplane attached to the port.
SGPIO: The controller firmware uses Serial General Purpose Input/Output (SGPIO) to communicate with the backplane attached to the port.
UBM: The controller firmware uses Unified Backplane Management (UBM) protocol to communicate with the backplane attached to the port.
VPP: The controller firmware uses the Virtual Pin Port (VPP) protocol to communicate with the backplane attached to the port.
Direct-Attached Cable: The controller firmware uses the direct-attached cable protocol to communicate with direct attached drives. Provide the number of targets (drives) that matches the direct attached cable's capabilities. If the number of targets is not configured correctly, target drives may not get discovered.

Note: If the port discovery protocol is not configured correctly, some features of the backplane may not function as expected. A reboot is required for the new port discovery protocol to take effect.

To change the backplane discovery mode protocol settings from the connector level:

In the Enterprise View, select a connector.
On the ribbon, in the Controller group, click Set Properties.
The Set Properties window opens.
From the Backplanedrop-down menu, change the backplane setting of the connector to SGPIO, VPP, UBM, or Direct-Attached Cable.
Click OK.
Reboot the server.

The online versions of the documents are provided as a courtesy. Verify all content and data in the device’s PDF documentation found on the device product page.