[UPLSA]in.routed(1M) Deletes Or Adds The Static Routes Illegally (Doc ID 1951381.1)

Last updated on JULY 29, 2016

Applies to:

Solaris Operating System - Version 10 10/08 U6 and later
Information in this document applies to any platform.

Symptoms

A problem is observed with static routes in solaris 10 when interfaces are brought up and down several timees.  It is observed that some additional redundant routes are added occasionally.  And, sometimes, some static routes are getting deleted.

Here is a machine with 10 static routes:

 # netstat -rn

 Routing Table: IPv4
   Destination           Gateway           Flags  Ref     Use     Interface
  -------------------- -------------------- ----- ----- ---------- ---------
  default              10.187.70.1          UG        1          2
  10.187.70.0          10.187.70.83         U         1         90 e1000g0
  172.30.0.1           192.168.1.105        UGH       1          0
  172.30.0.2           192.168.1.105        UGH       1          0
  172.30.0.3           192.168.1.105        UGH       1          0
  172.30.0.4           192.168.1.105        UGH       1          0
  172.30.0.5           192.168.1.105        UGH       1          0
  172.30.0.6           192.168.1.105        UGH       1          0
  172.30.0.7           192.168.1.105        UGH       1          0
  172.30.0.8           192.168.1.105        UGH       1          0
  172.30.0.9           192.168.1.105        UGH       1          0
  172.30.0.10          192.168.1.105        UGH       1          0
  192.168.1.0          192.168.1.141        U         1          0 e1000g1
  224.0.0.0            10.187.70.83         U         1          0 e1000g0
  127.0.0.1            127.0.0.1            UH        1         56 lo0
  
  After creating these static routes, bring e1000g1 and wait for some time.  
  Then bring up e1000g1 and wait for some time.  Keep doing this repeatedly.  
  During this process of bringing down/up interface, it is observed that
  sometimes netstat -rn output gives the following:
 
  netstat rn
 
  Routing Table: IPv4
   Destination           Gateway           Flags  Ref     Use     Interface
  -------------------- -------------------- ----- ----- ---------- ---------
  default              10.187.70.1          UG        1         57  
  10.187.70.0          10.187.70.83         U         1          4 e1000g0
  172.30.0.1           192.168.1.105        UGH       1          0  
  172.30.0.1           192.168.1.105        UGH       1          0 e1000g1   <<<<< extra
  172.30.0.2           192.168.1.105        UGH       1          0
  172.30.0.3           192.168.1.105        UGH       1          0
  172.30.0.4           192.168.1.105        UGH       1          0
  172.30.0.5           192.168.1.105        UGH       1          0
  172.30.0.6           192.168.1.105        UGH       1          0
  172.30.0.7           192.168.1.105        UGH       1          0 172.30.0.8  
  172.30.0.8           192.168.1.105        UGH       1          0
  172.30.0.9           192.168.1.105        UGH       1          0
  172.30.0.10          192.168.1.105        UGH       1          0
  172.30.0.10          192.168.1.105        UGH       1          0 e1000g1   <<<<<extra
  192.168.1.0          192.168.1.141        U         1          0 e1000g1
  224.0.0.0            10.187.70.83         U         1          0 e1000g0
  127.0.0.1            127.0.0.1            UH        1         56 lo0
 
  Note the extra route getting added (marked above).
 
  Also, repeated testing showed the following routing table occasionally.
 
  Routing Table: IPv4^M
   Destination           Gateway           Flags  Ref     Use     Interface
  -------------------- -------------------- ----- ----- ---------- ---------
  default              10.187.70.1          UG        1        334  
  10.187.70.0          10.187.70.83         U         1          4 e1000g0
  172.30.0.2           192.168.1.105        UGH       1          0
  172.30.0.3           192.168.1.105        UGH       1          0
  172.30.0.4           192.168.1.105        UGH       1          0
  172.30.0.5           192.168.1.105        UGH       1          0
  172.30.0.6           192.168.1.105        UGH       1          0
  172.30.0.7           192.168.1.105        UGH       1          0  
  172.30.0.8           192.168.1.105        UGH       1          0
  172.30.0.9           192.168.1.105        UGH       1          0
  224.0.0.0            10.187.70.83         U         1          0 e1000g0
  127.0.0.1            127.0.0.1            UH        1         56 lo0
  
  Note that two routes are missing in the above outputs (route for 172.30.0.1 and 172.30.0.10).

 Refer to bug 16632701 for further details.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms