Support Center > Search Results > SecureKnowledge Details
When fetch topology from Security Management, route that leads to logical interface as nexthop is ignored
Symptoms
  • After defining a route that leads to a logical interface as nexthop on the Security Gateway, when fetch topology from the Security Management, this route is ignored, and not added to the interface networks group under the ifc topology tab.
  • From fwm debug:
    [FWM 5096 2012784320]@fw-test-int-1[27 May 15:19:48] FWMTPL_GetStrValue_CPMI: get field named 'osRoutingIntrf' str_val='eth2.201'
    [FWM 5096 2012784320]@fw-test-int-1[27 May 15:19:48] FWMTPL_AssignEntryToInterface: route entry: [dst='83.10.0.0' mask='FFFFFFF0' next_hop='0.0.0.0' ifname='eth2.201' type=0]
    [FWM 5096 2012784320]@fw-test-int-1[27 May 15:19:48] FWMTPL_AssignEntryToInterface: route entry next_hop is 0.0.0.0 (this sometimes come from MIB2 routing tables and from IPSO gateways). ignoring this route entry.
Solution
Note: To view this solution you need to Sign In .