Sponsored Content
Full Discussion: VIO SEA Adapters
Operating Systems AIX VIO SEA Adapters Post 302842727 by karlochacon on Friday 9th of August 2013 05:58:34 PM
Old 08-09-2013
Quote:
Originally Posted by ibmtech
Ok,
When you click "View/Modify Host Ethernet Adapters", you are seeing two HEA's, now check the one on the top and select properties,
under general tab check mark the option called "Allow virtual Ethernet bridging" click ok and do the same for the other HEA adapter.

Then go to "Virtual Ethernet Bridge" and you will see a adapter.

Basically you are bridging two HEA adapters for redundancy.
thanks a lot

you know I can continue bothering you with question since I pretty lost in this topic for instance you say SEA makes no sense when having one VIO but my previous partner configured SEA... weird.

any documentation to read and continue after this since now I have to understand more about networking in VIO
 

7 More Discussions You Might Find Interesting

1. AIX

20EE0008 : No adapters found Adapter, Riser, System Bd.

Hello, When I try to upgrade AIX from 5.1 to 5.3 I get this error message 20EE0008 : No adapters found Adapter, Riser, System Bd. Anyone know anything about it ? (1 Reply)
Discussion started by: filosophizer
1 Replies

2. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. Red Hat

Designating Default Gateway for multiple networks/adapters

Hi I have 4 NIC's connected to my RHEL 5.3 server. Two on one subnet creating bond0, and two on a second subnet which create bond1. Both bonds are set to use DHCP to obtain IP addresses. Here is the config file for ifcfg-bond0: DHCP_HOSTNAME=rrnltshckvmx001 DEVICE=bond0 BOOTPROTO=dhcp... (2 Replies)
Discussion started by: Padow
2 Replies

4. AIX

SEA

Hi all, I set up the following configuration on my system: - An LPar with a virtual adapter, first one with a vlan id=703 and id port=13. - The first adapter have to connect to a VIOS in which i configured an SEA. So, the VA is set up on interface ent2, SEA on ent29 (by linking a... (0 Replies)
Discussion started by: idro
0 Replies

5. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

6. Windows & DOS: Issues & Discussions

Order of Adapters in Windows 7

I am trying to get my boss' ipad to print on our local printers, and rapidly coming to loathe the product. After several false starts I'm attempting to use the free WePrint application, running on a Windows machine, to "forward" our printers from it to the ipad over the local network. I've hit... (2 Replies)
Discussion started by: Corona688
2 Replies

7. AIX

VIOS - fibre adapters not seeing luns

Hi guys, I've been trying to tackle this issue for days and I'm stumped. Hopefully someone can give more light on what else I can do. I have a p7 series box, with dual VIOS and 10 lpars and everything was working fine until I had to move the box to another location in the data centre. Ensured... (16 Replies)
Discussion started by: aixkidbee
16 Replies
xna(4)							     Kernel Interfaces Manual							    xna(4)

Name
       xna - DEBNI and DEMNA Ethernet interfaces

Syntax
       device xna0 at vaxbi? node? vector xnaintr (DEBNI)
       device xna0 at xmi? node? vector xnaintr (DEMNA)

Description
       The  driver provides access to a 10 Mbytes Ethernet network through the DEBNI and DEMNA adapters.  The DEBNI is an Ethernet to BI bus.  The
       DEMNA is an Ethernet to XMI adapter.

       The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl.  The driver employs the Address  Resolution  Protocol,	as
       described in to map dynamically between Internet and Ethernet addresses on the local network.

       The  driver normally tries to use a trailer encapsulation to minimize copying data on input and output.	This can be disabled for an inter-
       face by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.  Trailers are used only for packets destined for Internet hosts.

       The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and SIOCRPHYSADDR  can  be  used  to  read  its  physical
       address.   SIOCADDMULTI	and  SIOCDELMULTI can be used to add or delete multicast addresses.  The driver supports a maximum of 12 multicast
       addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in

       SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear network counters. The argument  to  the	latter	two  ioctls  is  a
       pointer to a counter structure ``ctrreq'' found in

       The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode.

Restrictions
       The PUP protocol family is not supported.

Diagnostics
       xna%d: port self-test failed:<register list>
       Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment fails.

       xna%d: couldn't allocate...
       The driver was unable to allocate memory for adapter data structures.  The port attachment fails.

       xna%d: port probe failed:<register list>
       The driver was unable to bring the adapter into the initialized state.  The port attachment fails.

       xna%d: port init failed:<register list>
       The driver failed to prepare the adapter for runtime use.

       xna%d: port state changed, resetting:<register list>
       The adapter issued a port state change interrupt. The port state is reset.

       xna%d: port reset failed
       The driver was unable to bring the adapter into the initialized state during a port reset.

       xna%d: command failed, error code:<error code>
       The adapter port command failed. The error code gives reason for failure.

       xna%d: couldn't handle af%d
       A packet with an undefined protocol type has been sent to the adapter.

       xna%d: addmulti failed, multicast list full
       Too many multicast requests have been made.

See Also
       arp(4p), inet(4f), intro(4n)

																	    xna(4)
All times are GMT -4. The time now is 01:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy