About the Demands Tab (Planner)
On the Demands tab of the network table (Planning > Networks > Offline Models > Model-Name > Open), view the information about demands in your offline network.
Demands represent unidirectional traffic flow between a pair of nodes that need to be routed with specific constraints and performance goals. Demands are created when you want to analyze the traffic between the nodes.
Tasks You Can Perform
You can perform the following tasks on the Demands tab:
-
Download—To download demands-related data to your local system, click Download. The data is downloaded to your local system as a comma-separated values (CSV) file.
-
From the More list, you can perform the following tasks:
-
View details of a demand—To view the details of a demand, you can do one of the following:
-
Select a demand on the table and click More > Show Details.
-
Hover over a Demand row in the table and click the Details icon.
The Demand - Demand-Name page appears. You can view basic information such as ingress and egress nodes and their IP addresses and bandwidth of the demand.
-
-
-
Add demands to the network model—Click + to add new demands. For more information see Create a Demand (Planner).
-
Edit a demand—To edit a demand, select the demand and click the edit icon to open the Edit Demand page. After you edit, click Submit. A message confirms that the edit request is sent.
Note:You cannot edit the name of a demand.
-
Delete a demand—To delete a demand, select the demand and click the delete icon. A message confirms that the demand is deleted.
-
To perform common actions such as filtering using advanced filter criteria and resetting preferences, see Network Table Overview.
| Column | Description |
|---|---|
|
Name |
Displays the name of the demand. |
|
Device A |
Displays the device at which demand enters. |
|
Device Z |
Displays the device at which demand exits. |
|
IP A |
Displays the IPv4 address of the interface from which device A sends traffic. |
|
IP Z |
Displays the IPv4 address of device Z interface that receives traffic. |
|
Bandwidth |
Displays the traffic rate (bps) associated with the demand. |
|
Type |
Displays the type of demand—RSVP or SR. |
| Current Path | Displays the current path that the demand traverses. It is represented as an
ordered list of hops with link IP addresses or router/node IDs. If you have imported a Segment Routed (SR) demand through a JSON file, then the current path will be empty. |
|
Required Path |
Displays the required path that the demand traverses. It is represented as an ordered list of hops with link IP addresses or router/node IDs. This information is derived from the Routing Path Type configured at the time of demand creation, or from the demand collectedProperties.ero attribute if you are importing from file (config collection). When you perform the Update Models and Path operation, Routing Director considers only the required path if the demand has both required path and preferred path. |
| Preferred Path | Displays the preferred path that the demand traverses. It is represented as an ordered list of hops with link IP addresses or router/node IDs. If you are importing from the live network, this information is derived from the Routing Path Type configured at the time of demand creation. If you are importing from file (config collection), the Preferred path will be empty. When you perform the Update Models and Path operation, Routing Director considers only the required path if the demand has both required path and preferred path. |
| Diversity Group |
Displays the name of the diversity group to which the demand belongs. |
| Diversity Level |
Displays the diversity level of (Link, Shared Risk Link Group, or Site) the demand. |
|
Record Route |
The Record Route is used to record the path that the demand traverses. It includes the IP address and/or router or node ID of each node in the path. |
|
Description |
Displays the description that you added at the time of demand creation. |