05-16-2006
hacmp network adapter re-define
I have an LPAR in a P5 machine which has been setup in an HACMP cluster. The person who set it up allocated the wrong network adapter (en) to the persistent network. For the life of me I cannot find where I can re-assign this adapter. Anyone able to help me as I am tearing my hair out and do not have much anyway!
10 More Discussions You Might Find Interesting
1. Solaris
Is it possible to team two network adapters for fault tolerance in a Sun v440 or v880 Solaris 8 box? If so how would I go about doing so? (1 Reply)
Discussion started by: ghuber
1 Replies
2. IP Networking
what method would I use to determine which IP protocols network (0 Replies)
Discussion started by: mar mar
0 Replies
3. AIX
hello
i've need to change network adapter on machine H80 aix 4.3.3 hacmp ( ent0 )
what i need to do after the new adapter installed on the machine?
thanks
best regards
ariec (1 Reply)
Discussion started by: ariec
1 Replies
4. AIX
When I configure two VIO Servers, VIOS1 used to ping its gateway, after I configured second VIOS2, VIOS1 cannpt ping its gateway, when I run this command:
entstat -all ent#|grep -i priority
Priority: 5 Active: False
How to make Active to True? (1 Reply)
Discussion started by: rainbow_bean
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
I am new here - this is my first post.
I have installed Solaris 10 5/09 on my Dell M6300. The install went well, but the Dell's onboard network card is the Broadcom BCM5756ME Gigabit Ethernet - and sadly no Solaris driver exists for it. The Solaris 10 install just jumped by the... (1 Reply)
Discussion started by: soulmerchant
1 Replies
6. AIX
Hi,
lets say we have two boot interfaces en0 en1
and two resource groups, with two service ips, sip1 and sip2, one persistent ip pers1
both persistend and service ips are applied as ip-alias
when I start the cluster, and bring the resource groups up, it looks like
en0: sip1 and sip2
... (4 Replies)
Discussion started by: funksen
4 Replies
7. UNIX for Dummies Questions & Answers
Hi All
I P2Vd a Unixware 7.1.4 box with VMWare Vsphere. I try to add a network adapter under Network Configuration Manager and it comes up with the error attached.
I've added a virtual adapter using the "E1000" option. It detects both the AMD PCI NET and E1000 virtual adapters under Network... (8 Replies)
Discussion started by: flashinwrx
8 Replies
8. UNIX for Dummies Questions & Answers
Hi all, I got sort of a task to do. I have to write in C "simulated network driver". What does it mean?
- It has to run on all network adapters
- It has to be as simple as it can be
- It has to run on all linux distributions (or at least most of them)
- It does not have to run a network... (4 Replies)
Discussion started by: Chrisdot
4 Replies
9. Hardware
Good Day All,
There are numerous results when searching google on this issue, however, none seem to have a solution.
I have read until my eyes bleed and banged my head on the table more than once! :)
I am hoping to resolve this issue -- or at least have a decent workaround.
It is a real... (13 Replies)
Discussion started by: RogerBaran
13 Replies
10. SCO
hi .I've installed an operating system SCO in HP Z400 and network cards ZyXEL model FN312 with Chipset RTL8139D put it on .network card installed but do not display network card with command ifconfig -a in list and just show loopback.
show message :
dlpid:unable to open network adapter driver... (14 Replies)
Discussion started by: moein.mojtaba
14 Replies
vb(7) Miscellaneous Information Manual vb(7)
NAME
vb, sys_attrs_vme_vba - VMEbus backplane Ethernet interface
SYNOPSIS
controller vb0 at vba0
DESCRIPTION
The VMEbus backplane (vb) interface provides access to an Ethernet network through the VMEbus backplane driver, which acts as an Ethernet
Datalink Layer driver. This interface allows VMEbus-based systems to communicate directly over the VMEbus to other VMEbus-based systems on
the same backplane, or on other Ethernet connected systems outside the backplane through a gateway node on the backplane.
Both the Tru64 UNIX and VxWorks for Alpha (Version 3.1 or higher) software support the vb driver as well as communication between these
systems on the same backplane. The Tru64 UNIX vb driver is supported on AXPvme and Alpha VME SBCs and Alpha VME 2100 systems.
The VMEbus backplane interface requires you to modify the /etc/sysconfigtab file on your AXPvme or Alpha VME system in order to configure
the vb driver and to map VMEbus windows for the system. Mapping the VMEbus windows on one node requires knowledge about every node in the
vb network.
Note
Do not modify any vme_vba kernel subsystem attributes. To configure a vb network node, you modify attributes of the vb driver (vb:) and
the system's VMEbus adapter (vba_vipvic: or vba_univ:).
See System Configuration Supplement: OEM Platforms for detailed information about the use of the vb interface on Alpha VME systems, includ-
ing the following topics: VMEbus backplane (vb) network overview Configuring vb network nodes Modifying vb driver attributes Modifying
vba_vipvic adapter attributes Modifying vba_univ adapter attributes Examples Related ioctl commands Diagnostic messages Errors
RELATED INFORMATION
Interfaces: sys_attrs_vba_vipvic(7), sys_attrs_vba_univ(7), sysconfigdb(8)
Network Administration, System Configuration Supplement: OEM Platforms delim off
vb(7)