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 Next »

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

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

2. Click the edge and, in the panel on the right, click the  icon. Note that this panel might already be expanded when you log in. 

3. 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 rules in the policy.

The Routing Rules dialog opens and displays the following information:

  • PRIORITY: The priority of this routing rule. The smaller the number, the higher the priority.
  • NAME: The name of the routing rule associated with the edge.
  • EGRESS: The interface from which the outgoing traffic originates. 
  • NEXT HOP: The next hop in which data packets will be routed: Gateway IP address or None
  • SOURCES: The configured source of the routing rule: NetworkIdentity, or None.
  • DESTINATIONS: The total number of destinations configured for the routing rule.
  • HIT COUNT: The total number of packets that have hit the routing rule.
  • STATUS: The current status of the rule’s configuration:
    • Not Available: The routing rule is not available. You might see this status if, for example, the routing rule was added to the policy but was later deleted and no longer exists within the policy.
    • Not Associated to Edge: The routing 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 to complete. 
    • 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 successfully deployed.
    • 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.

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

  • Sources: The IP address of the source port.
  • Destinations: The IP address of the destination port. 
  • Service Objects Groups: The service object groups selected for the routing rule. 
  • Service Parameters: The number of service parameters configured in the routing rule. 
  • No labels