Powerha on P595 and Blade HX5 Type 787 Post: 302562427

5 More Discussions You Might Find Interesting

1. AIX

How to know the hardware configuration on P595 LAPRs

The p595 have 6 Lpars, not all hardware resource assigned to 6 lpars. which command can list all hardware configuration on p595? Do I need go to each lapr to list?

2. AIX

p595 LPAR no longer sees SAN boot disk

Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines. Now, on two...

3. AIX

Virtualizing the Fiber card (VFC) on P595

Hi, We have a P595 machine with a dual port Fiber card per VIOs. We have two VIOs in the box. VIO1: ---> 2 port Fiber Card VIO2: ---> 2 port Fiber Card One port on each fiber card is utilized. Connected to SAN switches. We are getting all disks from SAN both for VIOs and LPARs. Now...

4. AIX

HMC Hardware Discovery does not work for p595 frames

Hi, I require help with hardware discovery while running a command from an HMC with firmware V7.3.5 SP 3. The two frames I am running the command for are p 5 595's. Command input: lshwres -m swdc-c02-9119-595-SN02780CF -r io --rsubtype slotchildren -F lpar_name Error output: The managed...

5. Red Hat

How to know full width blade or half width blade?

HI, How do we figure out if the server is half blade server or full blade server? Anything we need to look at to know on this? thanks in advance

LEARN ABOUT DEBIAN

4s-backend-setup

4S-BACKEND_SETUP(1J)						      4store						      4S-BACKEND_SETUP(1J)

NAME

     4s-backend-setup -- Create a new 4store KB

SYNOPSIS

     4s-backend-setup kbname [--node node-number] [--cluster cluster-size] [--segments segment-count] kb-name

		      --node  Number of this node in the cluster, values range from 0 to cluster-size - 1.  The default is 0.

		      --cluster
			      The number of nodes in the cluster.  The default is 1.

		      --segments
			      The number of segments in the cluster. The default is 2. We recommend one for each CPU core in the cluster as a good
			      starting point. Higher numbers tend to consume more resources, but may result in increased performance.

NOTES

     Once crated with 4s-backend-setup KBs should be started with 4s-backend(1)

SEE ALSO

     4s-query(1), 4s-size(1), 4s-httpd(1), 4s-backend(1), 4s-delete-model(1)

EXAMPLES

     $ 4s-backend-setup --node 0 --cluster 1 --segments 4 demo

     Creates the indexes for a single-machine KB with four segments, named "demo".

4store								   May 31, 2019 							    4store