Network not working after changing the IP, Gateway and subnet

[gab_in]

Hi,

We have moved two of our tru64 servers from one localtion to another location. After I changed the IP Address, gateway and subnet mask of the network card according to new location network, both the servers are not connecting to the network.

Could you please help to fix this issue.

Thanks
Gab

[Vladimir Fabecic]

First, what is your OS version?
How did you do it?
Did you use "netsetup" or sysman?
Or you just edited files?

[gab_in]

First, what is your OS version?

Tru64 Unix Ver 5.1A
&
Tru64 Unix Ver 5.1B

How did you do it?

through "sysman"

[Vladimir Fabecic]

Please post output of:
# ifconfig -a
# netstat -nr

Did you change default gateway?

[gab_in]

Thanks for reply.
The server is in data center which is another location. I will go tommorrow and get the output. But I checked the
"ifconfig -a" and 'netstat -rn' output and didn't finf anything there. Can u pls suggest what needs to be checked there and what else we can check so that tommorrow I can get all the output.

Thanks again
Gab

[Vladimir Fabecic]

OK.
Also send outup of:
# cat /etc/rc.config
# cat /etc/hosts
Did you ask network manager is everything OK with ports on network switch?

[gab_in]

Do we need to check anything on the ports or network switch side? I used the same network port for HP-UX L-class machine and the network working fine.

Pls suggest.

Thanks
Gab

[Rob Leadbeater]

Hi Gab,

You might also want to check whether there was any switch port configuration (speed / duplex) at the original location that hasn't been setup at the new location.

Knowing the exact hardware configurations would be useful...

Cheers,

Rob

[gab_in]

Hi Rob,

Thanks for the response. Can you pls tell me what exactly we need to ask from the network manager to check on the switch side?

On the OS side , the network card is set for auto negotiation and full duplex and only one LED is ON out of three in the Network Card.

Thanks
Gab

[Vladimir Fabecic]

There may be problem with communication between Alpha server NIC and port of network switch.
I suggest to disable auto negotiation both on NIC and port.
If your alpha servers have fast ethernet NICs, set fix speed for them in SRM. Also ask your network manager to do the same for port on network switch.
Auto negotiation often does not work well and can make problems.

[Pieter 't Hart]

In addition to Vladimirs suggestion, there are three possible means of setting speed/duplex, depending on the type of network interface you must select the right one.
1) console variables,
2) ifconfig
3) lan_config
>>>
You can configure only tu interfaces (DE5xx) by setting the appropriate
console environment variables.
<<<
>>>
The ifconfig command can modify most of the operating parameters associated
with network interfaces, including some low-level parameters, such as the
speed (10, 100, or 1000 Mb/s) and mode (half-duplex or full-duplex) parame-
ters. However, to set other low-level parameters, such as the media type
(AUI, BNC, UTP, or Fiber) or IEEE 802.3u autonegotiation, you must use the
lan_config command or possibly a console firmware command. See
lan_config(8) for more information about changing these low-level parame-
ters, and viewing their current values.
<<<

[Rob Leadbeater]

Hi Gab,

> On the OS side , the network card is set
> for auto negotiation and full duplex

You are contradicting yourself... You can't have auto negotiation AND Full Duplex.

Contrary to the previous advice, I wouldn't necessarily fix NICs and switch ports. You mention that there are three LEDs on the NIC which *suggests* that it's a Gigabit card, which tend to work better with everything set to Auto.

Please let us know the exact hardware configuration, so we don't have to guess.

Cheers,

Rob

[gab_in]

Hi Rob,

This is an ALPHA Server 4100 Model with external storage.Pls suggest what network setting can be used on the same. So that I can ask my network team to set the same at switch label.

Pls let us know if anything else needs to be checked.

Thanks a lot

Gab

[Vladimir Fabecic]

We can have more information if you send output of:
>>> show config
>>> show *
From "show config" we would see what kind if NIC you have.