Browse Source

isisd: ignore unknown interfaces when adjusting IS-IS mtu

For example during startup of isisd, the MTU of interfaces is not
known, since this information will only be available once the
interfaces have been learned from zebra.

It makes no sense to include the MTU 0 that is stored for interfaces
in this state in the consideration whether a new lsp-mtu for an
area is valid, so skip interfaces which are in this state.

Signed-off-by: Christian Franke <nobody@nowhere.ws>
Christian Franke 6 years ago
parent
commit
e7207098c0
1 changed files with 2 additions and 0 deletions
  1. 2 0
      isisd/isisd.c

+ 2 - 0
isisd/isisd.c

@@ -1619,6 +1619,8 @@ int area_set_lsp_mtu(struct vty *vty, struct isis_area *area, unsigned int lsp_m
 
   for (ALL_LIST_ELEMENTS_RO(area->circuit_list, node, circuit))
     {
+      if(circuit->state != C_STATE_INIT && circuit->state != C_STATE_UP)
+        continue;
       if(lsp_mtu > isis_circuit_pdu_size(circuit))
         {
           vty_out(vty, "ISIS area contains circuit %s, which has a maximum PDU size of %zu.%s",