Support Center > Search Results > SecureKnowledge Details
"Get Interfaces" in the Cluster object does not update the Topology after changing a physical interface to VLAN interface with the same IP address, or vice versa
Symptoms

  • Topology in the Cluster object is not updated in the following scenario in R80 SmartConsole:

    1. Configure cluster members with physical interfaces (no VLAN interfaces)
    2. Configure Cluster object and check its "Topology" configuration - as expected, only physical interfaces are shown
    3. On cluster members, remove an IP address from some physical interface (e.g., Sync - eth3)
    4. On cluster members, on that physical interface (e.g., Sync - eth3) add a VLAN interface (e.g., eth3.200)
    5. On cluster members, assign the same IP address that was previously assigned to the underlying physical interface (e.g., Sync - eth3) to that VLAN interface (e.g., eth3.200)
    6. In the Cluster object, go to the "Topology" pane - click on the "Get Interfaces" button
    7. The "Topology" configuration is not updated to show the new VLAN interface (e.g., eth3.200) with its IP address - still shows that underlying physical interface (e.g., Sync - eth3) with its IP address

  • Topology in the Cluster object is not updated in the following scenario in R80 SmartConsole:

    1. Configure cluster members with at least one VLAN interface (e.g., eth3.200) on some physical interface (e.g., Sync - eth3)
    2. Configure Cluster object and check its "Topology" configuration
    3. On cluster members, remove an IP address from that VLAN interface (e.g., eth3.200)
    4. On cluster members, assign the same IP address that was previously assigned to the VLAN interface (e.g., eth3.200) to the underlying physical interface (e.g., Sync - eth3)
    5. In the Cluster object, go to the "Topology" pane - click on the "Get Interfaces" button
    6. The "Topology" configuration is not updated to show the underlying physical interface (e.g., Sync - eth3) with its IP address - still shows that VLAN interface (e.g., eth3.200) with its IP address

  • There are no errors in SmartDashboard after clicking on the "Get Interfaces" button.

Cause

Internal naming issue in the management database (during Gateway Network creation) on R80 Security Management Server / Domain Management Server.


Solution
 Note: To view this solution you need to Sign In .