![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||
Solution Type Troubleshooting Sure Solution 2263463.1 : FS System: Troubleshooting an FS1-2 Pilot Private Interconnect Link Failure message
In this Document
Applies to:Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. PurposeTo assist users in identifying the proper network port based on an FS1-2 Pilot Private Interconnect Link Failure. Troubleshooting StepsThere are a series of connections between Pilots and Controllers, Pilots and Pilots & Controllers and Controllers. These connections form what is known as the Private Management Interface or PMI and the status of the connections relating to the Pilot can be observed using the Pilot View (System tab, Hardware, Pilots then double click on a specific Pilot): When there is a problem with one or more of these connections, a System Alert will be generated. For example:
Here is what the actual hardware and associated network connections looks like:
NOTE: the red circles above are software network bridges that effectively create the PMI loop.
The problem is that the hardware is labeled NET0-3, the FS1-2 software uses Eth0-3. In addition the numbering is also not the same. The following table shows how to map these interfaces from their software name to the hardware name, what they do and what it means if their status changes to Not Connected:
Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||
|