I want to know the consequences of this error.
What I see is that sometimes a procedure from another of out intranet servers is connecting to the database of this server of the warning message and gives time out. Sometimes it worked , sometimes it doesnt. Is an intermitent situation.
I would like to know what this message means, what happened and what can be done to fix it.
traceroute: Warning: Multiple interfaces found; using <Ip address> @ ce2
/usr/sbin> ./ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST
inet <Ip address .142> netmask fffffffc broadcast <Ip address.143>
ce1: flags=1000843<UP,BROADCAST
inet <Ip address 146> netmask fffffffc broadcast <Ip address.147>
ce2: flags=1000843<UP,BROADCAST
inet <DB Ip address> netmask ffffffe0 broadcast <Ip address.31>
dman0: flags=1008843<UP,BROADCAST
5
inet <ip address.3> netmask ffffffe0 broadcast <Ip address.31>
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The thing is that one "Senior Network Consultann" told me that that message can be causing comunications problems of the kind that I mentioned before. He traveled back to US and I don't have his phone anymore.
He told something that the equipment attached to the <Db ip address> that I mentioned above has more than one "NETWORK" activated or connected.
But attached to the same IP address?
But lok this one: This has two Ip's in the same cable, look:
netstat -rn:
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- ------------------- ----- ----- ------ ---------
<Ip adress.1.0 > <IPaddress.1.7> U 1 7766 dman0
<Ip address.111.0> <IPaddress.111.16> U 1 7888 ce0 ---> Look ce0
<IPaddress.0.0.0> <Ipaddress.111.16> U 1 0 ce0-------> Look ce0 again
default <Ipaddress.111.1> UG 1 60186
127.0.0.1 127.0.0.1 UH 6 325956 lo0
Something definitely must be happening because there is Warning.
LindC
Yes it looks like 2 ipaddress are assigned to same interface,
paste the output of
/etc/path_to_inst
where do you see this error ?
traceroute: Warning: Multiple interfaces found; using <Ip address> @ ce2
Provide the following informaiton
/etc/path_to_inst
OS ?
OS version ?
Hardware platform (Make & Model )
Javeed A
15k running solaris8 EOL
---->>>>Network interfaces <-------
"/pci@3c,600000/pci@1/netw
"/pci@3c,600000/pci@1/netw
"/pci@3d,600000/pci@1/netw
"/pci@3d,600000/pci@1/netw
"/pci@3c,700000/network@3,
Need more info .
Can you able to boot the system with boot -r option
--->This will reconfigure the network interfaces but won't loose the ipaddress (unless they are plumbed temporarly)
Are you seeing the error messages in /var/adm/message ?( provide message events)
-Are you able to ping the ipaddress ? all of them
-Are you able to telnet and ssh the ipaddress ? all of them
javeed A
First off, your ifconfig -a output does not show more than one IP address per interface. Second, there is nothing wrong with having more than one IP address attached to the same interface, most virtualization technologies (zones, virtual box) depend on it. The netstat -rn output does not show more than one IP address attached to the same interface, it shows more than one *route* that uses the same interface and that is totally normal and expected. In fact, I bet the second one on ce0 was 224.0.0.0, which is the multicast route. Which brings up another point, namely that silly obfuscation you are using on the IP addresses. It makes it very difficult to see what is going on, and I can't imagine what info in the IP address you think you are protecting. If you must obfuscate it, try changing the top couple of octets of your private IP addresses to something else in the same address class.
Now back to the traceroute. The message really isn't a warning of a network problem, it is a warning to the user that the route that traceroute is printing may not be the same one that a packet would really take. Traceroute is choosing the first hop of the route based on its own heuristics and not on the system routing table and if it shooses a different interface than the routing tables would have used, then the route displayed will not match the route the packets will actually use. If you know that the interface is wrong, you can tell traceroute explicitly what interface to use and get the real route. So, just ignore the fact that the message says "warning".
I think interface should have being plumb and made it up like ce:0 and ce:1
--->>instead it was plumbed as ce0 <-------
netstat -rn:
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-----------------
<Ip adress.1.0 > <IPaddress.1.7> U 1 7766 dman0
<Ip address.111.0> <IPaddress.111.16> U 1 7888 ce0 ---> Look ce0
<IPaddress.0.0.0> <Ipaddress.111.16> U 1 0 ce0-------> Look ce0 again
default <Ipaddress.111.1> UG 1 60186
127.0.0.1 127.0.0.1 UH 6 325956 lo0
also provide
------>netstat -rvan
------>netstat -pn
------>netstat -in
------>ifconfig -a
And by the way, I wouldn't do a "boot -r" without knowing what you are doing. It is usually safe, but it can invalidate the openboot prom macros for some devices, and if the device that gets invalidated happens to be the boot device, you might render the system unbootable. I have no idea why the "boot -r" was recommended above, that is what the purpose was, since you are not having a problem with seeing any devices.
In the ifconfig -a output, if there was more than one IP address assigned to a single interface, then you would indeed show the other addresses assigned to interfaces like ce0:0 or ce2:1. However, in the ifconfig -a output you posted at the beginning, there is only one IP address per interface and there is only one instance of each interface and there are no virtual interfaces. You seem to be hung up on the "netstat -rn" output now. The output of "netstat -rn" shows routes, not interfaces, and there can be an unlimited number of routes that use the same interface and thus any given interface could show up on the list any number of times. By default, in Solaris, the multicast route is added to one interface in addition to the normal default routes, meaning that one interface will automatically appear on the list twice. But if you add other routes, or if the system learns about them dynamically, then any interface could appear more times.
I hope that is clear. You may have a problem, since you are getting timeouts, but so far your problems have nothing to do with what you have asked about.
the ping that sked Javeedabdul. I can ping all except 224.0.0.0.0
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
10.0.0.140 10.0.0.142 U 1 0 ce0
10.0.0.144 10.0.0.146 U 1 0 ce1
10.0.111.0 10.0.111.12 U 1 1124 ce2
10.2.1.0 10.2.1.3 U 1 66 dman0
224.0.0.0 10.0.111.12 U 1 0 ce2
default 10.0.111.1 UG 1 8312
127.0.0.1 127.0.0.1 UH 31998750771 lo0
/usr/sbin> ./ping 10.0.0.140
10.0.0.140 is alive
/usr/sbin> ./ping 10.0.0.144
10.0.0.144 is alive
/usr/sbin> ./ping 10.0.0.142
10.0.0.142 is alive
/usr/sbin> ./ping 10.0.0.46
/usr/sbin> ./ping 10.0.0.146
10.0.0.146 is alive
/usr/sbin> ./ping 10.0.111.0
10.0.111.0 is alive
/usr/sbin> ./ping 10.0.111.12
10.0.111.12 is alive
/usr/sbin> ./ping 10.2.1.0
10.2.1.0 is alive
/usr/sbin> ./ping 224.0.0.0
/usr/sbin> ./ping 10.0.111.1
10.0.111.1 is alive
/usr/sbin> ./ping 127.0.0.1
127.0.0.1 is alive
/usr/sbin>
Look, you don't need to look at the path_to_inst file. All of your interfaces are working fine. If one of them wasn't seen, then sure, the path_to_inst file is important. But that is not your problem. Just forget the path_to_inst file.
Likewise, pinging things. Your problem is intermittent. The only thing you need to care about is can the client ping the server?
Since you get timeouts, have you considered the possibility that the server is just not keeping up with the clients? What is the system load when the timeouts occur? Do you get occasional timeouts, or do they come in bursts? Do you know what is actually happening when the application says that it got a timeout?
the timeouts are inconsisten, sometime they work, sometimes not.
Now, a sysadmin told me the folowing: There is a clsutering configured, but there is no such clustering, look in the /etc/hosts.
I search in the /etc/hosts, and look what I've found:
Extract of /etc/hosts
# Cluster Heartbeats
10.0.0.142 heartbeat1
10.0.0.146 heartbeat2
# Cluster Manager
10.0.111.23 <host name>_cluster
10.2.1.3 <host name>-int <host name + domain>.net
10.2.1.1 scmain
Business Accounts
Answer for Membership
by: bluPosted on 2009-09-08 at 07:53:36ID: 25282491
I am sorry, I am not sure what you are asking. It sounds like some of your servers connect to the database and timeout. But then you also seem to be asking about the message from traceroute. The traceroute message is normal and will happen on any system with more than one interface.