The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Creating a plan file for modeling purposes requires specifying a number of objects that cannot be discovered directly from the network. WAE Design enables you to import shared-risk link groups (SRLGs), a Layer 1 (L1) model, a QoS model, demand groupings, external endpoints, and tags from one plan file to another, all from the File->Import menu. You can also import demand groupings from a file containing a <DemandGroupings> table.
These import tools simplify and expedite the process of importing specific objects and models. For instance, if you want to copy an L1 model into an existing plan file, you could do so using the Copy from Template tool, which copies over more information than just the Layer 1 model. Using these import tools described in this chapter allows you to copy only what is necessary.
When importing SRLGs, you can combine the imported SRLGs with existing SRLGS as follows.
Step 1 Select the File->Import->SRLGs menu.
Step 2 Browse to or enter the full path of the plan file from which you are importing SRLGs.
Step 3 Select how you want the existing SRLGs handled (Delete, Keep, Update), and click OK.
|
|
---|---|
Importing a Layer 1 model imports all Layer 1 objects, including L1 nodes, L1 links, L1 circuits, L1 circuit hops, and L1 waypoints from one plan file to another.
Step 1 Select the File->Import->Layer 1 menu.
Step 2 Browse to or enter the full path of the plan file from which you are importing L1 objects, and click OK.
|
|
---|---|
The QoS model consists of the mapping between service classes and interface queues, and service class policies.
Step 1 Select the File->Import->QoS Model menu.
Step 2 Browse to or enter the full path of the plan file from which you are importing the QoS model, and click OK.
|
|
---|---|
QoS modeling, including service classes, service class policies, and interface queues |
|
Demand groupings define a group of demands and provide a convenient way of specifying aggregated traffic in a plan, which can be used as a basis for growth forecasting.
When importing demand groupings, you have the option of importing demand groupings from either another plan file or from a file containing a <DemandGroupings> table. You can combine the imported demand groupings with existing demand groupings as follows.
Step 1 Select the File->Import->Demand Groupings menu.
Step 2 Select one of these import methods.
Step 3 Select how you want the existing demand groupings handled (Delete, Keep, Update).
Step 4 Select whether to import tags for sites, nodes, AS’s, and demands, and click OK.
|
|
---|---|
When importing external endpoints, you can combine them with existing external endpoints as follows.
Step 1 Select the File->Import->External Endpoints menu.
Step 2 Browse to or enter the full path of the plan file from which you are importing external endpoints.
Step 3 Select how you want the existing external endpoints handled (Delete, Keep, Update), and click OK.
|
|
---|---|
When importing tags, you can keep or delete existing tags as follows.
Step 1 Select the File->Import->Tags menu.
Step 2 Browse to or enter the full path of the plan file from which you are importing tags.
Step 3 Select one or more object types for which you are importing tags.
Step 4 Select how you want the existing tags handled (Delete, Keep), and click OK.
|
|
---|---|