xaminmo: (Computer Drive)
[personal profile] xaminmo
Info from digging into DS6800 (baby shark) which I didn't find online.
It's pretty sparse for the actual raw troubleshooting.
Basically though, it looks like there are recurring I/O channel failures for the primary processor card.
This has been replaced before, so it's probably a chassis issue.
There were power failures, so maybe it's a poor power regulation issue.
The PSU should take the hit and not kill the proc cards.

Since the site PDU was replaced, hopefully those problems will be gone.

Anyway, a CE is coming out to replace this processor card.
Read more... )
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
I updated firmware from to on this new v7000.

Trying to re-backup the config, I get:
IBM_2076:v7000:xaminmo>svcconfig backup
CMMVC6202E This command can only be run by the superuser.

CMMVC6156W SVCCONFIG processing completed with errors

I search on this, and 3 hits, all the docs.

Reference > Block storage system messages and codes > Command-line interface messages

The cluster was not modified because the IP address is not valid.

An attempt was made to change the IP address of a cluster to an address that is not valid.
User response

Correct the address and reissue the command.
Parent topic: Command-line interface messages

What makes it most annoying is that:
A) You cannot use the same authorized_keys SSH key for more than one user
B) Only one key attempt is allowed

So, if using pagent, you have to delete the key you used for the other user, and add the one for superuser. You can't have both.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
CMMVC8004E Cannot execute on a node with a location error
This is because the expansion and control cans were swapped between enclosures.
Once fixed and powered back up, cluster config takes 60 seconds (60 amber blinks)
You'll need to recreate your satask.txt if you haven't already.
xaminmo: (Computer Drive)
[personal profile] xaminmo
Controller 1 is WWN 04xxxxxxxxxx
Controller 2 is WWN 05xxxxxxxxxx
Each controller will be ONE target, and the LUNs will be subdevices of that target.

The target numbers assigned by Windows will, by default, be based on the order in which they WWNs are found.

If your windows box only has one HBA, the order of the target numbering to WWN mapping may flip between boots or between hosts.

As such, MSCS won't see the devices as the same device, because the target number differs.

The solutions are to:
A) Use one HBA to one controller port mapping (ie 2 HBAs)
B) Use SANSURFER to set which WWN is which target number (ie 1 HBA)


eserver: (Default)
IBM POWER servers

June 2017

45678 910


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 23rd, 2017 09:32 am
Powered by Dreamwidth Studios