Sponsored Content
Operating Systems Solaris Network interfaces on T2000 - e1000g1 and ipge1 Post 302796383 by chilinski on Friday 19th of April 2013 12:01:11 PM
Old 04-19-2013
I tried letting it rebuild the path_to_inst and rebooting and all that. The script ran fine, but the box would not reboot. I had an Oracle engineer on site who tried a couple of things, too, and could not get it to boot after doing that.

You'll find this interesting. I have four T2000s (dev, test, prod and spare) that I inherited when I started here in Nov. 2012. All of the boxes need serious updates. Both dev and test use the e1000g. The prod box uses the ipge0 (and there's evidence that someone tried to switch it to the e1000g in the past).

Before updating the real boxes, I cloned dev and test to the spare using a FLAR image. Everything went fine. When I cloned prod to the spare during testing, I simply could not get the e1000g to work no matter what I did. I decided that I wasn't going to spend any more time than I already have trying to solve the e1000g/ipge issue because we plan to move to RedHat boxes later this year. As long as I can get the ipge to run when new CPUs come out, I'll hold off and not worry about it.
 

10 More Discussions You Might Find Interesting

1. Solaris

HOW-TO Retrieve all network interfaces??!

Yes. But just wait a bit. How to do it via system calls? I'm just a newbie in Unix\Linux\Solaris e.t.c. programming. Can anyone help me? I need an advice probably how to do it or may be what API to read... :) Please, help... (2 Replies)
Discussion started by: LocalStorm
2 Replies

2. SCO

Network interfaces problem

Hi, I have problems with my SCO unix network interfaces. Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot. Installed driver using SCO Software manager - successfully Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies

3. AIX

NIM w/ two network interfaces

Hi all, this is my first post on this forum. My main problem is this: I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (0 Replies)
Discussion started by: snakernetb
0 Replies

4. Solaris

Network Install Problems T2000

Hi I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1). But when I try to install using # boot net -s I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies

5. AIX

NIM w/ two network interfaces

Hi all, this is my first post on this forum. My main problem is this: I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (1 Reply)
Discussion started by: snakernetb
1 Replies

6. Solaris

Network Interfaces

I got second IOU in my M5000 but not able bring internal network interfcae .. ike i don't get link on those 2 interfaces .. and the same network cable plugged in PCI network card it works like a charm Is there any special way to enable the internal IOU interfaces or i have bad nics ? (8 Replies)
Discussion started by: fugitive
8 Replies

7. Debian

/etc/network/interfaces problem

Hello i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address then i save it wq! then i restart the networking , /etc/init.d/networking restart . but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address... (5 Replies)
Discussion started by: learn82
5 Replies

8. UNIX for Advanced & Expert Users

How to bond network interfaces

All, I have a quad NIC on a V880 running Solaris 9. I've heard you can bond interfaces together and get better throughput. I found this link that seems to describe the process well. However, the command mentioned (dladm) is missing. Is there some package I need to install to get this command? Thx.... (2 Replies)
Discussion started by: agcodba
2 Replies

9. UNIX for Dummies Questions & Answers

/etc/network/interfaces

i need a one liner command that writes in /var/log/net.log the date when i connect to the network and when i disconect ..i know that i need to write somethin in /etc/network/interfaces but idk what ! please help (1 Reply)
Discussion started by: g0dlik3
1 Replies

10. Linux

Network interfaces error

I just ran sudo service networking start on Ubuntu 16.00 and came out with error message Job for networking service failed because control process exited with error code see systemctl status networking.service I tried to also run this command systemctl status networking.service I also got an... (4 Replies)
Discussion started by: DOkuwa
4 Replies
e1000g(7D)																e1000g(7D)

NAME
e1000g, e1000 - Intel PRO/1000 Gigabit family of network interface controllers SYNOPSIS
/dev/e1000g The e1000g Gigabit Ethernet driver is a multi-threaded, loadable, clonable, GLD-based STREAMS driver supporting the Data Link Provider Interface, dlpi(7P), over Intel PRO/1000 family of Gigabit controllers. This driver supports multiple Intel Gigabit controllers installed within the system. The e1000g driver provides basic support including chip initialization, frame transmit and receive, multi- cast support, and error recovery and reporting. APPLICATION PROGRAMMING INTERFACE
The cloning, character-special device /dev/e1000g is used to access all Intel Gigabit devices installed within the system. The e1000g driver is managed by the dladm(1M) command line utility, which allows VLANs to be defined on top of bge instances and for bge instances to be aggregated. See dladm(1M) for more details. You must send an explicit DL_ATTACH_REQ message to associate the opened stream with a particular device (PPA). The PPA ID is interpreted as an unsigned integer data type and indicates the corresponding device instance (unit) number. The driver returns an error (DL_ERROR_ACK) if the PPA field value does not correspond to a valid device instance number. The values returned by the driver in the DL_INFO_ACK primitive in response to the DL_INFO_REQ are as follows: o The maximum SDU (with jumbo frame) is 16128 (ETHERMTU). o The minimum SDU is 0. The driver pads to the mandatory 60-octet minimum packet size. o The dlsap address length is 8. o The MAC type is DL_ETHER. o The sap length value is -2, meaning the physical address component is followed immediately by a 2-byte sap component within the DLSAP address. o The broadcast address value is Ethernet/IEEE broadcast address (FF:FF:FF:FF:FF:FF). CONFIGURATION
The e1000g driver does not support the use of shared RAM on the board. To configure the e1000g driver: o Use prtconf -v | grep pci8086,[12][01][01][0-F] to obtain the instance number of the driver. o Use ifconfig e1000ginstance plumb to plumb the controller. o Use ifconfig e1000ginstance inet ip_address netmask + broadcast + -trailers up to bring up the interface. o Use the ping(1M) command to contact interfaces on the network to verify that the configuration is operational. Configuration File Options The following e1000g.conf configuration options are supported: AutoNegAdvertised This is a bitmap for the speeds advertised during autonegotiation. Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 Setting| N/A | N/A | 1000F | N/A | 100F | 100H | 10F | 10H The adapter only autonegotiates to a speed which is advertised. For example: AutoNegAdvertised = 4 causes an adapter to only advertise autonegotiation at 100 Mbps, full duplex. No other link speeds is accepted or given during autonegotiation. AutoNegAdvertised=47 adver- tises all speeds available, This is the same as using the default setting of 0. 0-255 Allowed values 0 Default DmaFairness When enabled, direct memory access by the driver is fair, meaning transmit and receive have equal priority. When disabled, receive takes priority over transmit. The allowed values are: 0 Disable. 1 Enable.This is the default. FlowControl Flow control utilizes ethernet XON and unicast and multicast XOFF packets to allow ethernet equipment to slow down the stream of data between two ethernet devices. The allowed values are: 0 Disable. Packets can get dropped in high throughput situations, leading to reduced network performance. 1 Receive only. 2 Transmit only. 3 Receive and transmit. This is the default. 4 Use adapter's EEPROM-programmed factory default setting. ForceSpeedDuplex Specify the speed and duplex mode for each instance. If you set ForceSpeedDuplex=7,4, the e1000g0 is set to autonegotiate and e1000g1 is set to 100 Mbps, full duplex. Fiber optic ethernet adapters ignore this setting. The allowed values are: 1 10 Megabits per second, Half Duplex. 2 10 Megabits per second, Full Duplex. 3 100 Megabits per second, Half Duplex. 4 100 Megabits per second, Full Duplex. 7 Autonegotiate speed and duplex.This is the default. MaxFrags Maximum number of STREAMS memory buffer fragmentation of incoming or outgoing packets. This value can effect the performance and memory requirements of the driver. 2-8 Allowed values 8 Default MaxFrameSize Upper limit on the maximum MTU size the driver allows. All Intel gigabit adapters, except the 82542-based Intel PRO/1000 adapter, allow the configuration of jumbo frames. The maximum MTU accepted by the MAC is 16128. Use ifconfig(1M) To configure jumbo frames. ifconfig with the adapter instance and the mtu argument (ifconfig e1000g0 mtu 16128) configures adapter e1000g0 for the maximum allowable jumbo frame size. The allowed values are: 0 Standard ethernet frames with a MTU equal to 1500. This is the default. 1 Jumbo frames with a maximum MTU of 4096. 2 Jumbo frames with a maximum MTU of 8192. 3 Jumbo frames with a maximum MTU of 16384. MaxFreeListBuf Maximum number or pre-allocated buffers the driver can use for received data. Pre-allocating buffers can help with receive performance. It also increases the memory requirements of the driver. 0-4096 Allowed values 256 Default MaxNumReceivePackets Maximum number of receive packets that the driver can handle for each interrupt. CPU utilization can be lowered through more effecient interrupt management. If this value is increased, the time needed by the CPU to process the individual interrupts can increase and nullify any performance gains realized by handling less interrupts. 16-1024 Allowed values 32 Default MWIEnable Architecture servers based on the Intel 450NX chipset are known to have problems with Memory Write and Invalidate. Disable this fea- ture only for this chipset. The allowed values are: 0 Disable. This is the default. 1 Enable. NumRxDescriptors Number of receive descriptors available to the driver. More receive descriptors increase receive performance at the penalty of decreased available memory. If you set this value to 256 on Solaris 7 when multiple Intel Gigabit NICs are configured, it causes memory allocation problems. It is recommended that you set this value lower when using multiple Intel Gigabit adapters on Solaris 7. 80-256 Allowed values 256 Default NumTxDescriptors Number of transmit descriptors available to the driver. More transmit descriptors increase transmit performance at the penalty of decreased available memory. If you set this value to 256 on Solaris 7 when multiple Intel Gigabit NICs are configured, it causes memory allocation problems. It is recommended that you set this value lower when using multiple Intel Gigabit adapters on Solaris 7. 80-256 Allowed values 256 Default ProfileJumboTraffic If you need to collect statistics on jumbo frame usage, enabling this parameter causes the e1000g driver to keep a count of the number of jumbo frames transmitted and received. Use the kstat command to view jumbo frame utilization statistics. See kstat(1M) The allowed values are: 0 Disable. This is the default. 1 Enable. TbiCompatibilityEnable=1; You must enable this feature on Intel 82543CG-based copper adapters to operate correctly with TBI mode ethernet hardware. The allowed values are: 0 Disable. 1 Enable. This is the default. TxInterruptDelay Amount of time (in 1.024 micro second units) between the time transmit data is queued in a transmit descriptor and the transmit inter- rupt is sent. 0-65535 Allowed values. A value of 0 completely disables any transmit interrupt delay. Some delay is benefical in reducing CPU uti- lization by the driver. 300 Default. dev/e1000g Character special device. /kernel/drv/e1000g.conf 32-bit driver configuration file. /kernel/drv/sparcv9/e1000g SPARC e1000g driver binary. /kernel/drv/amd64/e1000g 64-bit x86 e1000g driver binary. /kernel/drv/e1000g 32-bit x86 e1000g driver binary. sys/stropts.h stropts network header file. sys/ethernet.h Ethernet network header file. sys/dlpi.h dlpi network header file. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC, X86 | +-----------------------------+-----------------------------+ dladm(1M), ifconfig(1M), kstat(1M), ping(1M), attributes(5), dlpi(7P) Intel PRO/1000 Gigabit Adapter Driver Installation Notes for Solaris Writing Device Drivers STREAMS Programming Guide Network Interfaces Guide 23 Aug 2005 e1000g(7D)
All times are GMT -4. The time now is 03:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy