Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

1. To view the details of rules within a routing protocol policy of an edge, do the following:

2. In the Cloud Services Portal, click Manage > Service Edge > Edges. 

3. Click the edge. On the right-hand panel, click the  icon. Note that this panel might already have expanded when you logged in.  

4. Click the profile link (in blue) to expand the section, and then click the number link next to it. The number represents the total number of routing protocol rules in the respective policy.

  • The Routing Protocols dialog displays the following information:
    • NAME: The name of the routing protocol rule associated with the edge.
    • TYPE: The type of routing protocol configured for the rule. Possible values are RIP, BGP, and OSPF. Depending on the protocol type, some of the following fields might or might not be applicable to the protocol type displayed here. For more information, see Creating Routing Protocols.
    • NETWORKS ADVERTISED: The total number of networks to which the rule advertises.
    • NETWORKS LEARNED: The total number of networks learned through routing.
    • LOCAL AS: The total number of autonomous systems for the BGP protocol.
    • ROUTER ID: The router ID for the BGP protocol.
    • STATUS: The current status of the rule’s configuration:
      • Not Available: The rule is not available. You might see this status if, for example, the rule was added to the policy but was later deleted and no longer exists within the policy.
      • Not Associated to Edge: The rule is not associated with the edge. For example, because rules are shared among profiles, not all profiles are applicable to the edge due to how they are defined. 
      • Pending: The rule is being configured. This should take no more than five seconds. 
      • Programming Success: The configuration is successful. You will see this if (1) the configuration has been successfully sent from the cloud to the edge and (2) the service edge services have been deployed successfully. 
      • Programming Failed: The configuration failed. The following are the two possible reasons: 
        • One of the modules for programming routing is not running properly, or communication between components is broken.

        • Routing contains any user groups in the source attributes, and registration of user groups to the edge failed.

To fix this problem, disable and then enable the BloxOne Service Edge routing service on premises. If that does not resolve the problem, disable and then enable all Service Edge services. For more information, see Enabling Services for BloxOne Service Edge.

5. Click Expand All Rows to see more information about the rule:

  • Network Interface: The network interface used for the routing protocol rule. Only the LAN is supported.
  • Networks Advertised: The network IP to which the routing protocol advertises.
  • Network Learned: The network IP of which the rule has learned through routing. 
  • Next Hop: The network IP of the next hop in the routing table to ensure that the network is reachable.
  • Metric: The routing metric that captures the number of hops needed to find the best path between the source and the destination.
  • No labels