Ran Meng writes: > Here I unplugged the copper of e1000g1, the ping was working fine so I > inserted it back. > And then I unplugged e1000g0, the ping stopped work and even > ping -i e1000g1 10.13.49.105 didn't work. > > Seems the only way to get out of that situation is either > plug the e1000g0 in > or > remove the first route entry manually. > > Is this behavior normal/expected??
Unfortunately, yes. Nothing in the kernel does anything special when a network cable is pulled, other than to turn off the IFF_RUNNING flag and send up a routing socket message to clients. In particular, the kernel's forwarding table is not altered. If it needs to be, then that's generally the responsibility of a routing daemon. (And since routing daemons aren't supposed to be in charge of interface status, there are holes in this story as well. NWAM is a big part of filling the gaps here.) zhang yi writes: > local harddisk booted system can dynamic route the IP traffic to the remain > alive NIC interface. we can check it use 'netstat -nr' and see that alive NIC > interface's route gatway is refreshed to first level route priority. while > the unpluged NIC interface's all route information disappear on route table. I'd like to see before-and-after information from actual commands (such as "netstat -nr" and "ifconfig -a") showing the behavior you describe, and showing scenarios where it works and does not work. A text description of the issue is much harder to debug. > while on iSCSi booting scenario, when NIC is unpluged, we do not see anything > changed in route table using 'netstat -nr'. Is it possible that you're using special iSCSI bits with the fix for PSARC 2008/640? > Here I am suspect that route table is stored in local file system, No, it's not. The kernel's forwarding table and all of the user level routing daemon tables are held in memory, not on disk. The only thing on disk would be static routes that the user explicitly configured. > and when route table changes, in.routed need refresh those content in > persistent store. and this lead dynamic route fail when network booting. > because unplug network cable would lead root file system unreachable. while > network booting need solaris' dynamic route to failover to the health NIC > card to get root file system. that lead a deadlock of routing and root file > system. Interesting theory, but I don't think it matches the system design. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
