Configure Physical Network Connectivity Requirements
It is possible to configure new connectivity requirements or modify the properties on existing ones using the Resource Connections - Inventory tab.
To configure a connectivity requirement:
-
In the Resource Connections dialog box, click the Inventory tab.
To edit an existing connectivity requirement, in the blueprint or sandbox, click a connectivity requirement. From the context menu, select the Inventory option.
-
In the Inventory tab, click a connectivity requirement.
The connectivity requirement's row expands.
-
You can edit the following:
Field | Description |
---|---|
Alias | Click the Alias field and enter the description. The route's alias is displayed for the route in the diagram workspace. |
Type | To define the data transfer direction between the resources, from the Type dropdown list, select the suitable option:
|
Status | As this feature imposes many restrictions on how environments are resolved and cannot be used in conjunction with some other features such as abstract resources, it is strongly recommended to use shared routes only if it is absolutely required. Shared routes enable you to dynamically create an L1 route and then share it across several sandboxes. When reserving a blueprint containing a shared route, it is initially resolved like any other route by the reservation process. However, any subsequent reservations of blueprints containing that same route will simply be associated with that active route. Note that CloudShell does not prevent users from disconnecting/reconnecting shared routes in their sandbox, even if other sandboxes are currently using it. When a sandbox containing a shared route ends, CloudShell checks if any other sandboxes are currently associated with the same shared route, and will only disconnect that route when the last remaining sandbox is no longer active. In effect, a shared route is started by the first sandbox requesting it and automatically disconnects when the last sandbox referencing it ends. note Disconnecting a shared route or tearing down the route's sandbox does not affect other shared routes. Points to consider:
|
Max Hops | This value determines the maximum number of leaps, or hops, between L1 switches or patch panels in the route. For example, if a route has 2 maximum hops defined but the only available connection solution is |
Attribute | Route attributes are attributes that have the Link Configurations rule enabled. These attributes reside on the L1 resource ports. Note that changing a route attribute's value updates the actual port on the L1 resource. note In the blueprint, you can change port attributes in the route's Resource Connections dialog box or Connection Properties side pane, while in the sandbox, you need to use the side pane. To change a route attribute's value:
|
- Click Save.