IBM Power Linux Cluster Fence device on Power8 Platform Post: 302982343

6 More Discussions You Might Find Interesting

1. Solaris

Increasing Raw device Sun Cluster 3.0

Hi All , I would like to know the procedure for increasing shared volume space in sun cluster . Currently the configuration is like these . Main stripe oradb1/d91 2 1 /dev/did/rdsk/d35s0 1 /dev/did/rdsk/d36s0 =Total 49 Gb oradb1/d94 -p oradb1/d91 -o 88080480 -b 14680064 ==Total 7 GB...

2. AIX

IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE

Hello, I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization. So when booted , it goes into OPEN Firmware I/O Hosting requires a hosting partition boot not permitted exit called > ok Panel shows > IO...

3. AIX

New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config?

Hello, Got a IBM Power8 box (S822) that I am configuring for replacement of our existing IBM machine. Wanted to touch base with the expert community here to ensure I don't miss anything critical in my setup/config of AIX. Did a fresh AIX 7.1 install on the internal scsi hdisk, mirror'ed...

4. Red Hat

PaceMaker Cluster Fence Device

I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online. I have the cluster...

5. Solaris

Solaris Cluster Device Problem

I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk). 1 shared disk for vtoc 2 shared disk for NFS resource group 2 shared disk for WEB resource group When I finished my work; two nodes was ok and shared disk...

6. AIX

IBM Power 740 won't boot after firmware update

A team member installed the wrong version of License Code on a Power 740 system used in our Development environment. The system will no longer boot. Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version...

LEARN ABOUT NETBSD

tr

TR(4)							   BSD Kernel Interfaces Manual 						     TR(4)

NAME

     tr -- TROPIC based shared memory Token-Ring cards device driver

SYNOPSIS

     tr0 at isa? port 0xa20 iomem 0xd800 irq ?
     tr* at isa? port ? irq ?
     tr* at isapnp?
     tr* at mca? slot ?
     tr* at pcmcia? function ?

DESCRIPTION

     The tr device driver supports TROPIC I based shared-memory Token-Ring cards.

HARDWARE

     Supported cards include the following IBM and 3Com models:

	   IBM	 Token-Ring Network PC Adapter

	   IBM	 Token-Ring Network PC Adapter II

	   IBM	 Token-Ring Network Adapter/A

	   IBM	 Token-Ring Network 16/4 Adapter

	   IBM	 Token-Ring Network 16/4 Adapter/A

	   IBM	 Token-Ring 16/4 Credit Card Adapter

	   IBM	 Token Ring Auto 16/4 Credit Card Adapter

	   IBM	 Turbo 16/4 Token Ring PC Card

	   IBM	 16/4 ISA Adapter

	   IBM	 Auto 16/4 Token-Ring ISA Adapter

	   IBM	 Token Ring 16/4 Credit Card Adapter

	   IBM	 Token Ring Auto 16/4 Credit Card Adapter

	   IBM	 Turbo 16/4 Token Ring PC Card

	   3Com  3C619 TokenLink

	   3Com  3C319 TokenLink Velocity

	   3Com  3C389 TokenLink Velocity PC Card

SOURCE ROUTING

     Setting IFF_LINK0 enables Token-Ring source routing.  Setting IFF_LINK1 uses all-routes broadcasts otherwise single-route broadcasts are
     used.

NOTES

     The MCA attachment has been only tested on IBM Token Ring 16/4 Adapter/A so far.  It doesn't support ifmedia(4) yet, too.

SEE ALSO

     ifmedia(4), intro(4), isa(4), isapnp(4), mca(4), pcmcia(4), ifconfig(8)

HISTORY

     The tr driver appeared in NetBSD 1.4.

BUGS

     The PCMCIA attachment does not work with the cbb(4) CardBus driver.

BSD
								  April 14, 1999							       BSD