Perhaps one of the hardest issues to resolve are intermittent errors which only become apparent when the StoreServ is under load. If you do receive a mismatch then this will result in poorer performance, CRC errors or device resets. 4 x Wide Ports into 4 x Wide Ports and one port doesn’t negotiate correctly. 2 x 1 Gb links, one negotiates at 100 Mb Half Duplex the same occurrence can happen with SAS. In exactly the same way as we can have ethernet alignment mismatches when negotiating e.g. Whereas the individual Disk Drives are connected to SAS Expander (Drive Enclosure) the by a 1 x Narrow Physical Port (phys). We can see the SAS Controller and Disk Enclosures are connected via 4 x Wide Physical Ports (Phys). I prefer working in pictures as they make more sense to me. Narrow consists of a single physical interconnect and wide consists of two physical interconnects. W e have two types of ‘phy’ ports, narrow and wide. The data path is essentially the SAS interconnects. If you have no space and you cannot add another Disk Enclosure, then err work quickly!.Then add another Disk Enclosure, vacate the disks and then remove the failed Disk Enclosure. If you don’t have enough space on existing disks, but another Disk Enclosure can be added.If you have enough space on existing disks, then the disks can be vacated and the back plane replaced.If you a Disk Enclosure back plan failure then your choices are as follows: Right so what happens then if we have a back plane failure? Well if it’s the original StoreServe 7000 enclosure you want to shut the system down and phone HP! Power Supply, Fan, Battery, Interface Card, will result in an alarm and an Amber LED being displayed until the component can be replaced.
![no stor serv systems detected 3par ssmc no stor serv systems detected 3par ssmc](https://d8tadude.com/wp-content/uploads/2014/12/00_ssmc-2_login_1680x1050_300dpi.png)
The only exception to this is the back plane.Īny failure of a Cage component e.g. The good news is that if everything is cabled correctly we have dual paths. I think the first thing to remember is that connectivity issues can be caused by component failures.Ĭomponents can be broken down into two areas Cage and Data Path. It’s pretty obvious really, but make sure that all your devices are supported, two which aren’t are: six enclosure on a StoreServ 7200 two node, this is pretty simple, unplug it! The correct cabling diagram is shown below.įixing an issue where you have to many Disk Enclosures above the supported maximum e.g. Let’s say that you have cabled incorrectly, most likely if you loose a cage, then you will loose connectivity to all the other cages downstream. The good news is that configuration errors are detected by the StoreServ and you will receive an alert. These would mostly come from incorrect cabling, adding more cages than is supported and adding a cage to the wrong enclosure. In the following section we are going to cover these in a little more detail. We have an interconnect failure or perhaps even faulty e.g.
![no stor serv systems detected 3par ssmc no stor serv systems detected 3par ssmc](https://docplayer.net/docs-images/66/54417892/images/82-0.jpg)
Not so bad, as it wasn’t caused by us! We have a component failure e.g.
![no stor serv systems detected 3par ssmc no stor serv systems detected 3par ssmc](https://d8tadude.com/wp-content/uploads/2015/05/SSMC-Install-welcome-screen.png)
What are the issues we are going to encounter? Well these can be broken down into three areas.Įrr we the awesome StoreServ administrator has configured the 3PAR in an unsupported manner. Let’s say that we have had our StoreServ in and running for a few months and everything has been ‘tickety boo’ until we have an error or as I prefer to call it a ‘man down’ scenario.