Sponsored Content
Operating Systems Solaris Solaris 8: Multiple primary interfaces connected to the same network Post 302528199 by aeg on Monday 6th of June 2011 03:53:24 PM
Old 06-06-2011
Question Solaris 8: Multiple primary interfaces connected to the same network

Hello,

I have a machine with Solaris 8, and it has multiple interfaces that are connected to the same network which means they all have metric 0 (1 hop) to the default gateway.

assume:

* e1000g0: 10.1.1.70
* e1000g2: 10.1.1.72
* e1000g4: 10.1.1.74
* e1000g5: 10.1.1.76
* gateway: 10.1.1.65 (Cisco Router)

However, it seems like despite the fact that they have a direct connection, they seem to be using e1000g0 to access the 10.1.1.0 network to get to the default gateway and then to anywhere else.

When I send a ping to say, 10.1.1.74 (IP of e1000g4) and capture packets on e1000g0, I see the "echo reply" messages going out of it as opposed to e1000g4 even though e1000g4 is the one receiving the "echo request". This should not happen and these should be completely independent as they should all be advertising a 1 hop to that network

This gets even more confusing when I go into the Cisco router and run the command: "show mac address-table" where only the MAC address of e1000g0 is shown for the switch port it's connected to, but not for the other interfaces which are connected to the switch. Yes, all ports are active (no shut) and are pingable.

Also, the odd thing is that ALL of these individual MACs show up in the router ARP table when the machine comes up, however after sending a ping to one of them, after a certain expiry or whatever period, the MACs disappear from the router ARP table and only the MAC for e1000g0 shows up. The arp table of the solaris machine however shows all the relevant MACs of each port of the router that it's physically connected to (This is actually a Cisco Switch with the advanced IP services imagine and L3 routing turned on)

The routing table inside the machine also looks good and clearly shows each interface itself being the gateway to the 10.1.1.0 network.

I need to somehow assign all these interfaces equal priority and make them understand that they're physically connected to the 10.1.1.0 network and there's no need to go through e1000g0 to get to it.

This is causing a lot of problems as eventually all traffic will end up going through the e1000g0 interface and that will become a bottle neck.

Please help
Thanks in advance
 

10 More Discussions You Might Find Interesting

1. IP Networking

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

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. UNIX for Dummies Questions & Answers

How to display the primary network interface...

How do I find out what the primary network interface is on an AIX system.. Found commands to display information on the various interfaces but nothing that guides me to how to tell which one is the primary network interface. Thanks, ~D (1 Reply)
Discussion started by: djlerman
1 Replies

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

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. Shell Programming and Scripting

Shell script using ssh remains connected at primary site

Hi All, OS:AIX 5.3 L My shell script using ssh remains connected at primary site and ssh doesn't get disconnected.What should be typed and where in the shell script below to do it. Shell script ======== #!/usr/bin/ksh v_standby=`sqlplus -s /nolog <<END @standby.sql END` echo... (5 Replies)
Discussion started by: a1_win
5 Replies

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

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

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

Problem with multiple network interfaces

Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket. Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B. Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies
ROUTE(8)						      System Manager's Manual							  ROUTE(8)

NAME
route - manually manipulate the routing tables SYNOPSIS
/sbin/route [ -f ] [ -n ] [ command args ] DESCRIPTION
Route is a program used to manually manipulate the network routing tables. It normally is not needed, as the system routing table manage- ment daemon, routed(8), should tend to this task. Route accepts two commands: add, to add a route, and delete, to delete a route. All commands have the following syntax: /sbin/route command [ net | host ] destination gateway [ metric ] where destination is the destination host or network, gateway is the next-hop gateway to which packets should be addressed, and metric is a count indicating the number of hops to the destination. The metric is required for add commands; it must be zero if the destination is on a directly-attached network, and nonzero if the route utilizes one or more gateways. If adding a route with metric 0, the gateway given is the address of this host on the common network, indicating the interface to be used for transmission. Routes to a particular host are dis- tinguished from those to a network by interpreting the Internet address associated with destination. The optional keywords net and host force the destination to be interpreted as a network or a host, respectively. Otherwise, if the destination has a ``local address part'' of INADDR_ANY, or if the destination is the symbolic name of a network, then the route is assumed to be to a network; otherwise, it is pre- sumed to be a route to a host. If the route is to a destination connected via a gateway, the metric should be greater than 0. All sym- bolic names specified for a destination or gateway are looked up first as a host name using gethostbyname(3N). If this lookup fails, get- netbyname(3N) is then used to interpret the name as that of a network. Route uses a raw socket and the SIOCADDRT and SIOCDELRT ioctl's to do its work. As such, only the super-user may modify the routing tables. If the -f option is specified, route will ``flush'' the routing tables of all gateway entries. If this is used in conjunction with one of the commands described above, the tables are flushed prior to the command's application. The -n option prevents attempts to print host and network names symbolically when reporting actions. DIAGNOSTICS
``add [ host | network ] %s: gateway %s flags %x'' The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl call. If the gateway address used was not the primary address of the gateway (the first one returned by gethostbyname), the gateway address is printed numerically as well as symbolically. ``delete [ host | network ] %s: gateway %s flags %x'' As above, but when deleting an entry. ``%s %s done'' When the -f flag is specified, each routing table entry deleted is indicated with a message of this form. ``Network is unreachable'' An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given. ``not in table'' A delete operation was attempted for an entry which wasn't present in the tables. ``routing table overflow'' An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry. SEE ALSO
intro(4N), routed(8), XNSrouted(8) 4.2 Berkeley Distribution November 16, 1996 ROUTE(8)
All times are GMT -4. The time now is 02:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy