Configuring 2nd NIC IP address problem. "Multiple Interfaces detected". Help urgent!!

[Leonard Thng]

Hi,

Currently i've a NIC configured as 192.168.1.10, /24, no gateway is configured in my HP RP3440 box. I've installed an additional 1 port Gigabit Ethernet Adapter NIC card into the server. The OS detects the hardware installed and i'm able to configure the IP as 192.168.155.21, /24, no gateway for the newly NIC using SAM. This newly installed NIC is intended for backup connection to my backup device. However, i encountered problem routing through the existing NIC. When i did "traceroute ***.***.***.***", it shows me multiple NICs found and the traffic is being routed through my newly installed NIC which it shouldn't be so. Is there any configurations i should perform or disable any services for my NICs to be functioning properly as they should?

The 2 IPs that are configured are as followed.

1) On-board NIC: 192.168.1.21, 255.255.255.0
2) Additional NIC: 192.168.155.21, 255.255.255.0

They are both in the same subnet mask. Does it mean it will not work?

When i tried do a traceroute, it will show the system has "multiple interfaces" and will use the "192.168.155.21" which is the additional NIC that i've installed and configured.

1 thing that i've noticed when i configure the additional NIC in SAM. The "IP interface#" is "0" which is the same ip interface as the existing NIC that is configured. If the IP interface is the same, does it mean there will be a conflict?

Help & suggestions is needed urgently. Thanks in advance!!


leonard

[Steven E. Protter]

Shalom,

This question was answered earlier today.

The subnet mask devides the ip address into two sections. network and host.

255.255.255.0 means the first three octets of the address are the network.

Look at your two ip addresses. They are on differient networks. Therefore this configuration, nothing else being wrong should work.

If it does not work, something else is wrong and it may not be your system, it could be the wiring or network infrastructure.

SEP

[Leonard Thng]

Hi Steven,

sorry for repeating the same qn over & over.

so in other words, the IP addresses that are being configured as shown above should be functioning properly even though the 2 IP addresses have the same subnet mask?

leonard

[Leonard Thng]

Will patching up the server helps?

[spex]

Hi Leonard,

Don't get hung up on the subnet mask being the same for both interfaces--this is normal.

This seems like a routing issue to me. Do a 'netstat -nr'. 'Dest/Netmask' of 192.168.1.0 should have 'Gateway' 192.168.1.21. If not, you will need to add a route using the 'route' command. For example, 'route add 192.168.1.0 255.255.255.0 192.168.1.21'. Then do another traceroute and compare the results.

PCS

[Yang Qin_1]

Hi, Leonard, did you check your /etc/rc.config.d/netconf? it seems that you replaced interface [0] with the new NIC via SAM. If you are not sure what was configured and how they were configured, you can post your netconf file here. It will be easier to understand the problem with netconf.


Yang

[George Liu_4]

It seems you have two different subnet configured on the same box. It should be no issue on that. Are you sure the other side on the network cables are plugged in to appropriate network devices such as switches or a router? try get ifconfig to get the status of the network connection status.