Solaris

ossuser@PNR1RAD01 # cat hostname.e1000g0
PNR1RAD01
ossuser@PNR1RAD01 # cat hostname.e1000g1
10.200.3.58
ossuser@PNR1RAD01 #

yes these cables go to the same switch, pls note this was working before but somehow this suddenly went down.

Normally, a /etc/hostname.<interface name> file contains just a hostname (as you have in your hostname.e1000g0 file). The host names provided in these files is looked-up in /etc/hosts to tell Unix what ip address to use for that interface.

Anyway, you have different ip subnet addresses on these interfaces which, depending on how clever your network switch is, might confuse the hell out of the switch and cause it to "down" one of the interfaces.

You could provide different hostnames in each "hostname" file and different ip addresses for these in /etc/hosts.

Alternatively, if your switch will understand, you could set up an aggregate interface (Google that "aggr1") to combine two or more interfaces to look like one and load share via a clever switch.

Code:

root@PNR1RAD01 # cat /etc/hosts 
# 
# Internet host table 
# 
127.0.0.1       localhost        
::1     localhost        
10.200.2.73     PNR1RAD01       loghost 
10.200.3.58     PNR1RAD01

yes its defined as above, but am still not able to resolve this issue, gave a soft reboot to the server as well but it did not help to resolve the issue.

With a /etc/hosts containing the same hostname twice, only the first entry will ever be used when the system searches to resolve a hostname.

That's why you have an ip address in the second hostname file.

This is very unusual.

You are definitely saying that both network interfaces were working a short while ago? Has the network switch been changed recently?

Or, has there been another change on the network that might have created a loop that the switch can see? This could be just a cable being moved or something elsewhere on your network.

I reckon that network conditions (loops???) are causing your switch to drop one of the Solaris interfaces.

Hopefully, I can get a second opinion on this forum from another Solaris networking expert. I can't think of much else it can be.

---------- Post updated at 08:55 PM ---------- Previous update was at 08:15 PM ----------

Here's an idea..........

If you've got a spare switch put each interface cable into different switches. Connect just a PC or something to the spare switch too.

See if you can ping the respective ip address from each "separate" network and also see if both interfaces stay up.

If the interfaces stay up then that pretty much eliminates the Solaris box as being the problem.