Reconfiguring Networkcard Post: 302221935

Sponsored Content

Operating Systems AIX Reconfiguring Networkcard Post 302221935 by dukessd on Tuesday 5th of August 2008 01:41:08 PM

08-05-2008

Registered User

AIX 4.43? do you mean 4.3.3? (oslevel)

If a card was added after AIX was installed then when you restore the cards may be discovered and configured in another order, so the ent that used to be entx is now enty and the ent that used to be enty will now be entx.

Yes, the ent device is the physical adapter and the en and et devices are the available interfaces that are available on the adapter.

You can only configure one en interface OR one et interface per ent device.

I've never met a system that uses the et interface, always use only the en interface.

The et interface is some old, never used, ethernet standard.

HTH.

dukessd

View Public Profile for dukessd

Find all posts by dukessd

2 More Discussions You Might Find Interesting

1. Solaris

Reconfiguring the network

Hi, I am a beginner to Solaris. I installed it on a AMD Athlon 2000+, dual booting with XP. When I installed it, I didn't setup the network section and went on to install it without the n/w config. Now I have ethernet access at my school, and wanted to be able to connect to the internet through...

2. Homework & Coursework Questions

Reconfiguring the kernel

1. The problem statement, all variables and given/known data: Download the newest kernel version. Once your kernel has been re-configured, your lilo or grub should have a choice of 2 different kernels. You should have the choice of picking either one of them. The first choice should be the...

LEARN ABOUT PHP

vni

vni(7d) 							      Devices								   vni(7d)

NAME

       vni - STREAMS virtual network interface driver

DESCRIPTION

       The  vni  pseudo  device  is  a	multi-threaded, loadable, clonable, STREAMS pseudo-device supporting the connectionless Data Link Provider
       Interface dlpi(7P) Style 2. Note that DLPI is intended to interact with IP, meaning that DLPI access to applications is not supported. (For
       example, snoop fails on the vni interface.)

       The  vni  device is a software-only interface and does not send or receive data. The device provides a DLPI upper interface that identifies
       itself to IP with a private media type. It can be configured via ifconfig(1M) and can have IP addresses assigned to it, making aliases pos-
       sible.

       The  vni  pseudo  device  is  particularly  useful in hosting an IP address when used in conjunction with the 'usesrc' ifconfig option (see
       ifconfig(1M) for examples).  The logical instances of the device can also be used to host addresses as an alternative to hosting them  over
       the loopback interface.

       Multicast  is not supported on this device. More specifically, the following options return an error when used with an address specified on
       vni: IP_MULTICAST_IF, IP_ADD_MEMBERSHIP, IP_DROP_MEMBERSHIP, IPV6_MULTICAST_IF, IPV6_JOIN_GROUP, IPV6_LEAVE_GROUP. In  addition,  broadcast
       is not supported.

       Because	there  is no physical hardware configured below it, no traffic can be received through nor transmitted on a virtual interface. All
       packet transmission and reception is accomplished with existing physical interfaces and tunnels. Because applications that deal with packet
       transmission  and  reception  (such  as packet filters) cannot filter traffic on virtual interfaces, you cannot set up a packet filter on a
       virtual interface. Instead, you should configure the policy rules to apply to the physical interfaces and tunnels, and  if  necessary,  use
       the virtual IP addresses themselves as part of the rule configuration. Also, note that the virtual interface cannot be part of an IP multi-
       pathing (IPMP) group.

FILES

       /dev/vni

	   64-bit ELF kernel driver

SEE ALSO

       ifconfig(1M), in.mpathd(1M), ip(7P), ip6(7P)

SunOS 5.10							   18 July 2004 							   vni(7d)