Network interfaces on T2000 - e1000g1 and ipge1


 
Thread Tools Search this Thread
Operating Systems Solaris Network interfaces on T2000 - e1000g1 and ipge1
# 8  
Old 04-18-2013
Quote:
Originally Posted by hergp
In 2006 I think, Sun switched from the ipge-driver to the more advanced e1000g driver for the Intel PRO/1000 adapter present in a T2000.

I can't explain, why this setup fault happened. But there is a shellscript /usr/sbin/e1000g_transition which will help you to switch your configuraion to the e1000g driver.

The help text taken from the script:

Code:
This script allows you to perform an optional driver upgrade
for the Intel PRO/1000 device present on this system from the "ipge"
network driver to the Sun standard "e1000g" network driver. The
e1000g driver include features such as link aggregation as well as
superior performance in most environments.  Moving forward, e1000g
will benefit from new features as they become available, bug fixes,
and performance enhancements.  The disadvantage is that some
applications configuration files may require modification to use
e1000g if they reference the ipge network interface.

This script must be run in single user mode.
This script will alter network interfaces and related system
configuration files. Configuration files for 3rd party applications
will NOT be changed. After running this script, applications present
on the system may require maintenance. The system may be in an
unsecured state. The effects of this script may be reversed using
the backout (-b) option.


For the latest information regarding this script, please refer
to Sun Alert ID 102502. This Sun Alert can be accessed from
http://sunsolve.sun.com.
Use the Sun Alert ID (102502) as the search query and choose
"Sun Alert Notifications" under "Sun Solve Collections."

Once the script has completed a system reboot will be required
to complete the upgrade.

Thanks. Very interesting - I will try this.

To be honest, I'm wondering whether its just going to be OK to sys-unconfig and let it start back up as ipge. Might be quicker.

---------- Post updated at 11:59 AM ---------- Previous update was at 11:57 AM ----------

Quote:
Originally Posted by hicksd8
That is weird but since it's a T2000 I would check that the firmware/OBP/hypervisor versions are up to date.

I've had some nasty experiences with Solaris version upgrades and/or putting on patchsets where the system crashes. Assuming it was caused by just a glitch I've recovered the system and done it over and over before searching and finding that the firmware was incompatible but Sun (Oracle) gave no warning in version release notes and/or patchset release notes. I've only ever had this problem with T2000's.

Do you know the history of your box? What version of firmware does it have and is it up to date?

Search unix.com for stuff like "T2000 patching".

After all the bad experience I have my own rule that if a T2000 gives any trouble always upgrade firmware/OBP/hypervisor before anything else.

Hope that helps.
Thanks. Yes, will do this I think.

Sun-Fire-T2000 System Firmware 6.7.6 2009/10/29 16:06

Host flash versions:
OBP 4.30.4 2009/08/19 07:24
Hypervisor 1.7.3.a 2009/10/29 15:50
POST 4.30.4 2009/08/19 07:47
# 9  
Old 04-18-2013
Quote:
To be honest, I'm wondering whether its just going to be OK to sys-unconfig and let it start back up as ipge. Might be quicker.
It might work that way but a T2000 with recent Solaris versions should be configured e1000g1-e1000g4 so something would be wrong in using ipge1-ipge4.
# 10  
Old 04-18-2013
I ran into this exact same thing. I ended up leaving it with the IPGE because I simply could NOT get it to work on the e1000g. When I ran the e1000g script to update to that driver the entire system refused to boot.

I ended up doing the install from the CD/DVD without setting up any networking. That way, it didn't try to force the e1000g. After booting, I plumbed the ipge and did all the setup and it works just fine. I filed an SR with Oracle, and they were no help at all in getting it to run on the e1000g, and since it was working fine with the ipge, I closed the case and got on with life.
# 11  
Old 04-18-2013
Out of interest, I tried running the script. This is what I got:-

WARNING:
The script detected that both "ipge" and "e1000g" interfaces
exist in the system. The script can not handle this situation, as
there are potential conflicts between existing "ipge" and "e1000g"
instances. You will need to manually resolve device instance numbers
and configure your system configuration files.

---------- Post updated at 04:08 PM ---------- Previous update was at 04:08 PM ----------

Quote:
Originally Posted by chilinski
I ran into this exact same thing. I ended up leaving it with the IPGE because I simply could NOT get it to work on the e1000g. When I ran the e1000g script to update to that driver the entire system refused to boot.

I ended up doing the install from the CD/DVD without setting up any networking. That way, it didn't try to force the e1000g. After booting, I plumbed the ipge and did all the setup and it works just fine. I filed an SR with Oracle, and they were no help at all in getting it to run on the e1000g, and since it was working fine with the ipge, I closed the case and got on with life.
Yeh. Wondering if it might be an idea. So you've experienced no problems?

---------- Post updated at 04:30 PM ---------- Previous update was at 04:08 PM ----------

UPDATE

Think I've cracked it. This is what I did:-

cp /etc/path_to_inst /etc/old.path_to_inst
rm /etc/path_to_inst
init 0
ok> boot -ar
(accept defaults and let it rebuild /etc/path_to_inst)
init s
cd /usr/sbin
./e1000g_transition -e
init 6

And it works with e1000g now....

Many thanks to hergp for the info about this script....
# 12  
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.
# 13  
Old 04-19-2013
Quote:
Originally Posted by paulfoel
...
And it works with e1000g now....
Many thanks to hergp for the info about this script....
You are welcome, paulfoel. Glad, I could help.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
Login or Register to Ask a Question