timestamp fib not updating

Created: Jan 22, 2020 12:04:29Latest reply: Jan 23, 2020 09:56:15 88 5 0 0
  Rewarded Hi-coins: 0 (problem resolved)

Hi,


On a stack of two S5720-32C-HI-24S-AC's running V200R013C00SPC300 I see the timestamps on the masterswitch not increasing when using the "display fib 0" command. When I issue the same command adding the verbose option I do see an increasing age counter. The timestamp counter is also increasing on the standby switch:

active:


dis fib 0
Route Flags: G - Gateway Route, H - Host Route,    U - Up Route
             S - Static Route,  D - Dynamic Route, B - Black Hole Route
             L - Vlink Route
--------------------------------------------------------------------------------
 FIB Table:
 Total number of Routes : 5

Destination/Mask   Nexthop         Flag  TimeStamp     Interface      TunnelID
127.0.0.1/32       127.0.0.1       HU    t[791]        InLoop0        0x0
10.80.1.3/32       127.0.0.1       HU    t[791]        InLoop0        0x0
10.80.0.0/16       10.80.1.3       U     t[791]        Vlanif80       0x0
127.0.0.0/8        127.0.0.1       U     t[791]        InLoop0        0x0
0.0.0.0/0          10.80.0.1       GSU   t[791]        Vlanif80       0x0


Standby:

dis fib 1
 FIB Table:
 Total number of Routes : 5

Destination/Mask   Nexthop         Flag  TimeStamp     Interface      TunnelID
127.0.0.1/32       127.0.0.1       HU    t[18569129]   InLoop0        0x0
10.80.1.3/32       127.0.0.1       HU    t[18569129]   InLoop0        0x0
10.80.0.0/16       10.80.1.3       U     t[18569129]   Vlanif80       0x0
127.0.0.0/8        127.0.0.1       U     t[18569129]   InLoop0        0x0
0.0.0.0/0          10.80.0.1       GSU   t[18569129]   Vlanif80       0x0


Verbose of active:

dis fib 0 verbose
Route Flags: G - Gateway Route, H - Host Route,    U - Up Route
             S - Static Route,  D - Dynamic Route, B - Black Hole Route
             L - Vlink Route
------------------------------------------------------------------------------
 FIB Table:
 Total number of Routes : 5

 Destination: 127.0.0.1           Mask     : 255.255.255.255
 Nexthop    : 127.0.0.1           OutIf    : InLoopBack0
 LocalAddr  : 127.0.0.1           LocalMask: 0.0.0.0
 Flags      : HU                  Age      : 18568746sec
 ATIndex    : 0                   Slot     : 0
 LspFwdFlag : 0                   LspToken : 0x0
 InLabel    : NULL                OriginAs : 0
 BGPNextHop : 0.0.0.0             PeerAs   : 0
 QosInfo    : 0x0                 OriginQos: 0x0
 NexthopBak : 0.0.0.0             OutIfBak : [No Intf]
 LspTokenBak: 0x0                 InLabelBak : NULL
 LspToken_ForInLabelBak : 0x0
 EntryRefCount : 0
 VlanId : 0x0
 BgpKey : 0
 BgpKeyBak : 0
 LspType         : 0              Label_ForLspTokenBak   : 0


Is this a known bug that I'm running into?


Thanks in advance!

  • x
  • convention:

Featured Answers
chenhui
Admin Created Jan 23, 2020 09:56:15 Helpful(0) Helpful(0)

Posted by Erik_van_der_Burg at 2020-01-23 08:46 Hi, @chenhui ,Thanks for your reply. It doesn't make sense to me then that the FIB timestamp date on ...
I think the reason for timestamp on the standby switch increasing is the FIB entry synchronization between master and slave.
  • x
  • convention:

chenhui
Admin Created Jan 23, 2020 01:37:03 Helpful(0) Helpful(0)

Hi @Erik_van_der_Burg
No, it's normal. The timestamp indicates the time equal to FIB entry generation time minus system startup time, so it wouldn't increase or decrease when the entery didn't change, while age filed displays lifetime of a route, it indicates how long has been since the entry generated, it will keep increase.
  • x
  • convention:

All Answers
E.DR_91
E.DR_91 MVE Created Jan 22, 2020 12:34:02 Helpful(1) Helpful(1)

Dear Please try below command and check  if the timestamp updated or not  

display fib interface command


please note: the timestamp Indicates the lifetime of this entry, in seconds.
  • x
  • convention:

I%20am%20an%20information%20Technology%20Engineer%3B%20I%20work%20as%20Head%20of%20section%20in%20Management%20Information%20System%20with%20over%20five%20years%20of%20experience%20specializing%20in%20Software%20Testing.%20I%20am%20looking%20forward%20to%20growing%20my%20management%20skills%20to%20develop%20and%20inspire%20my%20team%20and%20I%20am%20a%20MVE%20in%20this%20forum
Erik_van_der_Burg
Erik_van_der_Burg Created Jan 22, 2020 12:42:23 Helpful(0) Helpful(0)

thanks for your reply.

display fib interface Vlanif 80
Destination/Mask Nexthop Flag TimeStamp Interface TunnelID
10.80.0.0/16 10.80.1.3 U t[791] Vlanif80 0x0
0.0.0.0/0 10.80.0.1 GSU t[791] Vlanif80 0x0


so no it's not updating.... could just be a visual bug but I do think it's strange to see the counter increase on the standby stackmember.
  • x
  • convention:

chenhui
chenhui Admin Created Jan 23, 2020 01:37:03 Helpful(0) Helpful(0)

Hi @Erik_van_der_Burg
No, it's normal. The timestamp indicates the time equal to FIB entry generation time minus system startup time, so it wouldn't increase or decrease when the entery didn't change, while age filed displays lifetime of a route, it indicates how long has been since the entry generated, it will keep increase.
  • x
  • convention:

Erik_van_der_Burg
Erik_van_der_Burg Created Jan 23, 2020 08:46:46 Helpful(0) Helpful(0)

Hi, @chenhui ,

Thanks for your reply. It doesn't make sense to me then that the FIB timestamp date on the standby switch does increase. For that switch the exact same FIB entry's apply, or is the standby stackmember treating the FIB differently?

Kind regards,
Erik van der Burg
  • x
  • convention:

chenhui
chenhui Admin Created Jan 23, 2020 09:56:15 Helpful(0) Helpful(0)

Posted by Erik_van_der_Burg at 2020-01-23 08:46 Hi, @chenhui ,Thanks for your reply. It doesn't make sense to me then that the FIB timestamp date on ...
I think the reason for timestamp on the standby switch increasing is the FIB entry synchronization between master and slave.
  • x
  • convention:

Comment

Reply
You need to log in to reply to the post Login | Register

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login