HPE 9000 and HPE e3000 Servers
Showing results for 
Search instead for 
Did you mean: 

Re: Superdome server


Superdome server

What is BIB in superdome server?
Acclaimed Contributor

Re: Superdome server

BIB = boot is blocked.

Hope this helps!

There are only 10 types of people in the world -
those who understand binary, and those who don't.

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Honored Contributor

Re: Superdome server


on this link you will find more info :


Trusted Contributor

Re: Superdome server


Usually when you power ON the HP Servers, it will start boot automatically. But if you want check something in GSP, before boot the Server (This is required when you are performing any hardware change) you need to stop it when Server promt at 10 Sec count down. You can consider BIB is another option. If BIB is enabled, you have to boot the Partion using "boot" OR "bo" command from MP. Otherwise Server will stop after completing POST.

Honored Contributor

Re: Superdome server

Dear Ragesh

BiB means boot is blocked, when it illuminated it tells the end user the system is ready to boot.

thanks and regards

sajjad Sahir
Honored Contributor

Re: Superdome server

consider a hypothetical NPAR that has 4 cells cell0, 1 ,2 and 3.(The congiuration i site here for example might not be a good NPAR Configuration)..
you have
cell 0 as 64 GB RAM and 4 sockets,IO capable
cell 1 as 28 GB RAM and 2 sockets,
cell 2 as 28 GB RAM and 3 sockets,IO capable
cell 3 as 32 GB RAM and 2 sockets,

When NPAR shall start all the cells shall power on, varying on their resource sizes and that on whether they have IO chassis attached they will individually need to initialise all of them at power on.

A cell(cell 0, here) with more resoureces and IO, shall need to do POST and all Tests on CPU and RAM and IO before that is ready to boot and shall require more time to be ready as compared smaller cell (cell1, here), so cell1 has to wait for cell 0 to complete all the initializations and tests to be ready.
once a cell is ready, a BIB flag is set to block the boot of the cell. This is to make sure that all other participating cells have also performed the inventory and have reached the BIB state of their own.
When all cells cell0,1,2,3 hacve reached BIB, GSP checks if there is a new configuration is to be pushed to the cells and that there is pending Reconfig, if so the Reconf profile is pushed to the cells.

once that is done, the BIB is released and you can see the Rendezvous(coming together of the cells) takes place and the boot of the NPAR starts like a simple UNIX server might boot.


Re: Superdome server

Hi Raquesh,

BIB (Boot is blocked) is implemented on any cell based Server:
(PA-RISC) HP 9000: e.g. HP rp7420, HP rp8420, HP 9000 Superdome
as well as on cell based (Intanium) Integrity Servers,
e.g: HP rx7640, HP rx8640, HP Integrity Superdome

BIB is needed, when using HP-UX 11iv1 (11.11) on HP9000 or HP-UX11iv2 (11.23) on HP9000 or HP Integrity cell based servers, if you want to reconfigure the n-par(s) (hardware-partitions). A n-par is built by at least one cell(-board) ("motherboard) with CPU(s) and RAM installed. Also one I/O cage is needed which always is directly connected to the cell. In an I/O cage you will place your PCI-X or PCI-e LAN-, SCSI-, SAN-FC-HBA, etc. I/O cards. Without ony of them you cannot boot (no LAN, SAN, disk conncetion where the CPU can boot the OS from)
Starting with an n-par which only has one cell (e.g. cell0), you want to enlarge your n-par by adding another cell (e.g. cell1) which also has an I/O cage attached. This can only be done. This can only be done by going into BIB mode, alter the n-par configuration, save it, "activate" it and go on with the boot, passing the POST check and having the two cells (automatically) joining in a rendevouz algorithmn, so that they act as one "monolythic" server. The same must be be done analogously if you want to reduce the n-par by eliminating one cell.

With HP-UX 11v3 (11.31), you are able to even dynamically reconfigure a n-par _without_ reboot of the "affected" OS (or OSses if you have vPars or Integrity VMs in place).