Cisco Provisioning Center User's Guide, 4.2
Working with Networks and Services
Downloads: This chapterpdf (PDF - 281.0KB) | Feedback

Working with Networks and Services

Table Of Contents

Working with Networks and Services

Working with Networks

Viewing Standard Network Elements

Viewing Equipment Module Elements and Profiles

Working with Equipment Modules

Uploading Fabric and Services

Time Slot Usage Range

Time Slot Usage Range in Logical and Physical Port Lister

Displaying Available Time Slots When Creating or Modifying Logical Ports

Selecting and Deselecting All Available Time Slots

Working with Links

Creating Links

Configuring NNI Resiliency

Shared Links Policy

Specifying NNI Resiliency Priority

Grouping NNI Links

Failing NNI Links

Recovering NNI Links

Rebalancing NNI Links

Configuring UNI Resiliency

Specifying UNI Resiliency Priority

Backing Up a UNI Logical Port

Failing UNI Ports

Recovering UNI Ports

Configuring Pre-Provisioned Service Elements

Working with Services

Viewing Service Objects or Profiles

Viewing Service Objects Through the Service View

Static Labels

Drilling Down on Service Elements

Retrieving Service Object Details Through the Details View

User-Defined Methods

Applying the User-Defined Method to Multiple Objects


Working with Networks and Services


This chapter covers the commons tasks that you will perform when you are working with features on the networks and services tabs.

The first section,"Working with Networks", includes the following tasks:

Viewing Standard Network Elements

Viewing Equipment Module Elements and Profiles

Working with Equipment Modules

Uploading Fabric and Services

Working with Links

Configuring NNI Resiliency

Configuring UNI Resiliency

Configuring Pre-Provisioned Service Elements

The second section, "Working with Services", includes the following tasks:

Viewing Service Objects or Profiles

Viewing Service Objects Through the Service View

Retrieving Service Object Details Through the Details View

For more information on any task, see the relevant Equipment Module or Service Application documentation.

Working with Networks

When you log onto Cisco Provisioning Center, the Networks View appears. Click the networks button at any time to return to the Networks View.

You can access four different types of information from the Networks View:

standard Cisco Provisioning Center object classes (click Standard Resource Model))

standard ATM specific object classes (click ATM Resource Model)

standard IP specific object classes (click IP Resource Model)

standard SONET specific object classes (click SONET Resource Model)

Equipment Module specific Network elements and profiles (click on the specific Equipment Module).

This section describes how to view standard network elements, how to create, modify and delete service and profile elements of Equipment Modules, upload Fabric and Services, work with links, and configure UNI and NNI resiliency.

Viewing Standard Network Elements

You can view the following standard Cisco Provisioning Center objects in the Standard Resource Model folder of the Networks View:

Network

Physical Link

Node

Logical Link

Physical Port

Network Connection

Logical Port

Multiple Range Item


You can view other objects in the Standard folder, if they are required by certain service applications.

For each class of object in the Standard folder, you can view a list of all the objects belonging to that class in your network. For example, you can view all of the nodes in your network regardless of the equipment vendor or equipment type (e.g., DSLAM, switch, or router).

To list all of the elements belonging to a particular class, follow these steps:


Step 1 Navigate to networks > Activator Standard Resource > Elements > Standard Object Class.

The Standard Object Class Lister appears in the Content Area.

Step 2 Click the Get List button.

Step 3 To retrieve additional information on any object listed, click the object's Name or Item Number. An Object View displays the attributes for the object.


Viewing Equipment Module Elements and Profiles

You can view a list of elements and profiles for each Equipment Module. For example, you can list all of the Universal Access Nodes in your network or all of the existing Universal Access ATM Logical Port profiles.

To view Equipment Module elements or profiles, follow these steps:


Step 1 Navigate to networks> Specific Equipment Module> [Elements|Profiles]> Specific EM Object.

The Specific EM Object Lister appears in the Content Area.

Step 2 Click the Get List button. An Object View displays the attributes for the object you selected including Equipment Module specific attributes.


Working with Equipment Modules

You can view network elements and profiles for each installed Equipment Module. You can also create, modify and delete Equipment Module elements and profiles.

The following sub-folders appear when you click an Equipment Module folder:

Elements—This sub-folder contains the fabric and service elements available through the Equipment Module.

Profiles—This sub-folder contains the service element profiles available through the Equipment Module.

You can use Cisco Provisioning Center to create, modify and delete the service elements and profiles available through each Equipment Module (provided that such actions are supported). For detailed information on how to manipulate specific service elements and profiles, refer to the relevant Equipment Module Configuration Guides.

Uploading Fabric and Services

Once you've created networks and nodes, you can begin the process of uploading Fabric and Service elements.

In order to provision services, the Cisco Provisioning Center database must have detailed knowledge of the managed subnetworks. Using the upload feature, objects are created within the Cisco Provisioning Center database that represent objects of the managed network. This information is acquired through the upload process.

The upload function takes precedence over any transactions which are running at the time of upload. If the upload function makes a change to the fabric which affects a running transaction (such as deleting a logical port that the threader has decided to use) then this transaction fails and must be restarted.

The fabric elements for a network object are nodes, physical ports and logical ports. The service elements are the objects used to create services (for example, PVCs).

For details on which objects can be uploaded and how to upload them, refer to the relevant Equipment Module Configuration Guide.

You should upload only when you are populating the database for the first time. You must re-upload selected nodes and networks periodically to ensure that the Cisco Provisioning Center database is synchronized with the actual network.

Time Slot Usage Range

The GUI can now display the time slot usage range for both channelized logical and physical ports. Available time slots are time slots not taken by logical ports that are currently associated with the selected physical port.

This information is displayed when you create or modify a logical or physical port.

Time Slot Usage Range in Logical and Physical Port Lister

For channelized logical ports the Timeslots attribute (srchanmap) may be displayed on the Lister view. If the GUI encounters "Timeslots" attribute in the lister, then for each logical port shown, the GUI will calculate it's the port's time slot usage range and display it in the Timeslots column. For example: the following values displayed in the 1-3,10,11,15 Timeslots column would indicate that for the selected logical port time slots 1,2,3,11 and 15 are already in use. The time slot numbers listed are adjusted according to the "First Channel on the Port"(srstartchan) defined for the physical port).

Since the value of "Timeslots" is calculated after querying the database search criteria and sort order are not supported for this field.

Channelized physical port Timeslots (timeslots) may also be displayed on the Lister view to show all time slots that have been used by the logical ports that are associated with the selected physical port. When the GUI encounters the Timeslots attribute in the physical port lister, it will calculate time slot usage of all logical ports associated with the selected physical. The time slots listed are adjusted according to the First Channel on the Port attribute (srstartchan) defined for the physical port.

As with the logical port, search criteria and sort order are not supported for this field.

Displaying Available Time Slots When Creating or Modifying Logical Ports

The GUI can calculate which time slots that are in use by the logical ports associated with the selected physical port and show these values in read-only mode. All time slots that are occupied by a a logical port and are available time slots will be shown in read/write mode.

When you are creating or modifying logical ports, use the find/choose feature to select a physical port. The object viewer will be refreshed and the GUI will calculate physical port time slot allocation. For all time slots that are allocated to other logical ports, the GUI will set them to read-only. All available time slots on the parent physical port will be shown in read/write mode.

For example. if ds0toggle1 in your logical port is false, and ds0toggle1 is true on the associated physical port, this means this time slot is used by other logical port on this physical port, therefore ds0toggle1 should be set to read-only for this logical port.

If you select another Physical Port, the object viewer will be refreshed and the occupied time slots will be recalculated based on the new physical port.

Occupied time slots whether they are in a pending or current state can not be allocated again. If a logical port is created and saved in a transaction, the time slots occupied by this logical port cannot be assigned to other logical ports either in the same transaction or in another transactions. However if a logical port is deleted and saved in a transaction, the time slots occupied by this logical port will be freed and can be allocated to other logical ports in the same transaction. Time slots occupied by the delete pending logical ports cannot be allocated to other logical ports in other transactions until the pending is applied successfully. If you are modifying a logical ports, the un-allocated time slots from the modified logical port cannot be assigned to other logical ports in the same transaction or in other transaction until the transaction is applied.

Selecting and Deselecting All Available Time Slots

You can select all available time slots or deselect all available time slots when creating or modifying channelized logical port using the "Channel Autoselection" attribute When you are creating or modifying a logical port, this field will be set to "None" and all time slot fields will have values that represent the current time slot usage of the selected logical port. If you choose "Select All", the object view will refresh and all available time slots will be set to "TRUE". If you choose "Deselect All", the object view will refreshed and all available time slots (including time slots currently occupied by this logical port) will be set to "FALSE". After each refresh, the value for Channel Auto Selection field will be reset to "None" so that you can select "Select All" or "Deselect All" as required.

The "Channel Autoselection" field will only be shown when you are creating or modifying channelized logical ports. It will not be shown in read only object view form.

Working with Links

After uploading new fabric and service elements, you can create, modify or delete inter-networking links.

Links must be created from the Cisco Provisioning Center Standard Resource folder since they are out of the scope of any one Equipment Module.

Creating Links

To create a link, follow these steps:


Step 1 Navigate to networks> Activator Standard Resource > Elements> Logical Link.

The Content Area displays the Link Lister.

Step 2 Click the Create button.

A Link Object View appears in the Content Area.

Step 3 Enter the required attribute values in the Link Object View.


Note You must use the Find and Choose function to find suitable logical ports.


For attribute values, see "Inter-Network Link Attributes".

Step 4 Click the apply now button, or click the save button if you are making multiple changes.


Configuring NNI Resiliency

NNI resiliency allows you to rethread circuits that pass through a failed link. A resiliency policy can be associated with a single link. The policy is invoked when you rethread or restore the link. A resiliency priority can be associated with each service. Those with higher priorities are rethreaded first during a link failure situation.

A Cisco Provisioning Center administrator configures the policies that are used on the various links. Currently, the only supported resiliency policy is the Shared Links Policy (shared1).

During service provisioning, Cisco Provisioning Center propagates the resiliency priority specified for the service object to the service elements that make up the service.

You can invoke NNI resiliency functions to rethread a failed link and to rebalance a set of links over the same link group. The actions taken depend on the resiliency policy defined for the links.

Shared Links Policy

Cisco Provisioning Center currently implements one resiliency policy—the Shared Links Policy. A group of links can be defined to share their capacity. A portion of the capacity of each is reserved, so that when one or more members of the group fail, the others take on more of the load. When a link failure is initiated, circuits on the failed link are moved onto others in the group. On recovery, the links are not moved, but load on the links can be manually rebalanced. All links in the group must connect the same two subnetworks.

You can use Cisco Provisioning Center to specify NNI resiliency priority, or group, fail, recover and rebalance NNI links.

Specifying NNI Resiliency Priority

To specify an NNI resiliency priority for a service, follow these steps:


Step 1 Navigate to services > Specific Service Application > Elements > Specific Service object class.

Step 2 Click the Get List button.

Step 3 Select the Service you want to set a NNI resiliency priority for.

Step 4 Click the modify button on the Action Bar.

Step 5 Enter the value in the NNI Recovery Priority field.

Step 6 Click the apply now button, or click the save button if you are making multiple changes.


Grouping NNI Links

To define a group of NNI links that will share their capacity, follow these steps:


Step 1 Navigate to networks > Activator Standard Resource > Elements > Logical Link.

Step 2 Click the Get List button.

Step 3 Click the link you want to include in the group.

Step 4 Enter a name (any alpha-numeric string) for the Resiliency Group attribute. Enter `shared1' for the Resiliency Policy attribute.

Step 5 Click the Save button.

Step 6 Repeat steps 4 and 5 for all required links.

Use the same resiliency group name for each link. Names are case sensitive.

Step 7 Click the apply now button, or click the save button if you are making multiple changes.


Failing NNI Links

When a link fails, the other links in the group compensate by using bandwidth above and beyond nominal thresholds.

Cisco Provisioning Center locks the failed link's logical ports and re-distributes services from the failed link over the other links in the group.

To mark an NNI link as failed:


Step 1 Navigate to networks > Activator Standard Resource > Elements > Logical Link.

Step 2 Click the Get List button.

Step 3 Check the Select box beside the link you want to fail.

Step 4 Click the NNI fail button on the Action bar.

Step 5 Click the apply now button.


Recovering NNI Links

When a failed link is recovered, no automatic re-distribution of services occurs. The restored link is made available to new services, and the total committed bandwidth is adjusted on the non-failed links. The total committed bandwidth on the restored link is set to re-establish the total available bandwidth for the group as it was before the failure. In the process, the logical ports of the failed link are unlocked.

To recover a failed NNI link, follow these steps:


Step 1 Navigate to networks > Activator Standard Resource > Elements > Logical Link.

Step 2 Click the Get List button.

Step 3 Check the Select box beside the link you want to recover.

Step 4 Click the NNI recover button on the Action bar.

Step 5 Click the apply now button.


Rebalancing NNI Links

You can rebalance the load across links in the group. The service over the link you select is re-distributed evenly over other links in the group. Cisco Provisioning Center re-distributes services with highest priority last.

To rebalance an NNI link, follow these steps:


Step 1 Navigate to networks > Activator Standard Resource > Elements > Logical Link.

Step 2 Click the Get List button.

Step 3 Check the Select box beside the link you want to rebalance.

Step 4 Click the NNI rebalance button on the Action bar.

Step 5 Click the apply now button.


Configuring UNI Resiliency

UNI Resiliency provides the ability to specify a backup logical port to use when a failure occurs on a UNI. You can specify when to move the services to a backup logical port and when to move them back to the primary logical port. You can also specify priorities, so that the services are moved in a pre-defined order (or not at all). Those services with higher priorities are more likely to survive a failure.

During service provisioning, Cisco Provisioning Center propagates the resiliency priority specified for the service object to the service elements that make up the service.

You invoke UNI resiliency functions to move PVCs to a backup logical port when a failure occurs on a UNI and to move PVCs back when a recovery is made on a UNI.

You can use Cisco Provisioning Center to specify UNI resiliency priority, and also to fail and recover UNI ports.

Specifying UNI Resiliency Priority

To specify a UNI resiliency priority for a service, follow these steps:


Step 1 Navigate to services > Specific Service Application > Elements > Specific Service object class.

Step 2 Click the Get List button.

Step 3 Select the Service you want to set a UNI resiliency priority for.

Step 4 Click the modify button on the Action Bar.

Step 5 Enter the value in the UNI Recovery Priority field.

Step 6 Click the apply now button, or click the save button if you are making multiple changes.


Backing Up a UNI Logical Port

You can specify a backup logical port, and mark a UNI port as failed.

When a primary logical port fails, Cisco Provisioning Center locks the primary logical port, unlocks the backup if it is locked, and moves PVCs from the primary logical port to the backup logical port according to the UNI Resiliency priority of each PVC.

To specify a backup logical port, follow these steps:


Step 1 Navigate to networks > Specific Equipment Module > Elements > Logical port type.

Step 2 Click the Get List button.

Step 3 Select the logical port you want to back up.

Step 4 Click the modify button on the Action Bar.

Step 5 Enter a backup logical port in the Backup LPort field using the Find button.

Step 6 Click the apply now button, or click the save button if you are making multiple changes.


Failing UNI Ports

To mark a UNI port as failed, follow these steps:


Step 1 Navigate to networks > Specific Equipment Module > Elements > Logical port type.

Step 2 Click the Get List button.

Step 3 Select the logical port you want to fail.

Step 4 Click the UNI fail button on the Action Bar.

Step 5 Click the apply now button.


Recovering UNI Ports

When a foreground logical port recovers, Cisco Provisioning Center moves PVCs back from the backup logical port to the foreground logical port. Cisco Provisioning Center does not lock the backup logical port; it can be used as a foreground or as a backup logical port for another foreground logical port.

To recover a foreground logical port, follow these steps:


Step 1 Navigate to networks > Specific Equipment Module > Elements > Logical port type.

Step 2 Click the Get List button.

Step 3 Select the logical port you want to recover.

Step 4 Click the UNI recover button on the Action Bar.

Step 5 Click the apply now button.


Configuring Pre-Provisioned Service Elements

The attribute Pre-provisioned can be found in Node and Network Object Views as a drop-down list with the following options:

None—the equipment is not pre-provisioned (default).

Init—the equipment is initially pre-provisioned, but can be modified through download. If a service object is deleted and the associated service element is contained by a Network/Node in Init mode, the corresponding service element is deleted.

Full—the equipment is initially pre-provisioned and cannot be modified (download is not supported). If a service object is deleted and the associated service element is contained by a Network/Node in Full mode, the service element is returned to the pool of available elements and is not deleted from the device.

When the Pre-provisioned attribute is set to Full or Init, Cisco Provisioning Center service objects can use the existing unassigned service elements on the node or within the network instead of creating new elements.

Working with Services

Click the services button to open the Services View. The Tree View is populated with folders for each Service Application installed.

Click a Service Application folder. The following sub-folders appear:

Elements—the service objects available through the Service Application.

Profiles—the service object profiles available through the Service Application.

You can use Cisco Provisioning Center to create, modify and delete the service objects and profiles available through each Service Application. For detailed information on how to manipulate specific service objects and profiles, refer to the relevant Service Application Solutions Guide.

Figure 6-1 Services Tree View

Viewing Service Objects or Profiles

To view existing service objects or profiles through the service object specific Listers, follow these steps:


Step 1 Navigate to services > Specific Service Application > [Elements|Profiles]> Specific SA Object.

The Specific SA Object Lister appears in the Content Area.

Step 2 Click the Get List button.

Step 3 To retrieve additional information for any of the objects listed, click the object's name or item number. An Object View displays the attributes for the object you selected.


Viewing Service Objects Through the Service View

The Service View allows you to view graphical representation of a service object. Only Service objects that represent a connection between two endpoints can be viewed through the service viewer.

To view a Service object through the Service View, follow these steps:


Step 1 Navigate to services > Specific Service Application > Elements > Specific SA Class.

Step 2 Click the Get List button.

Step 3 Check the Select box beside the Service object that you want to view.

Step 4 Click the Graph button on the Action Bar.


The Content Area displays the Service View for the Service object you selected and a link to the Service object's Object View. See Figure 6-2.

Figure 6-2 Service View

Static Labels

Static labels show detailed information about each component in the provisioned service. This feature is optional and all service applications may not implement the functionality. The information for each label is derived from the details feature.

Drilling Down on Service Elements

From the Service View, you can drill down on the Service elements that make up the Service in order to obtain more information about them.

To drill down on Service elements in a Service View, follow these steps:


Step 1 Position the mouse pointer over the service element you want more information on.

A label appears that displays the object class and its name.

Step 2 Click the element for which you want more information.


An Object View for the Service element you selected appears in the Content Area including the object's Action Bar which shows the actions you can perform on the object. Alternatively, you can view the Service View and Object view together by opening another window for the Object View. To do this, right-click the element and select Open in New Window (Internet Explorer) or Open Link in New Window (Netscape).

Retrieving Service Object Details Through the Details View

You can retrieve additional information about a Service object's underlying Service elements through the Details View. The Details View displays Object Views for each Service element that comprises the end-to-end Service.

Detail Views are only available for Service objects that are present in the live network (and not just the database).

To retrieve Service object details, follow these steps:


Step 1 Navigate to services > Specific Service Application > Elements > Specific SA Object.

Step 2 Click the Get List button.

Step 3 Check the Select box beside the Service object for which you want details .

Step 4 Click the Details button on the Action Bar. The Content Area displays an Object View for each Service element that makes up the Service object.


User-Defined Methods

A user-defined method can be any generic operation defined by a Service Application. If a user-defined method has been created and defined for a service object class, then the generic operation icon will be displayed up on the action bar of the lister and object viewer for that class.

All user-defined methods use the same icon. Move your mouse over the user-defined icon to see the tooltip for that icon. The tooltip indicates the name of the user-defined method. To access the method, click on the icon. A provisioning form is displayed for the object. You can modify the displayed attribute values and click the save and Apply button. A generic request is sent to the SA for processing. A provisioning results page will then be displayed containing the result of the operation.

Permissions to utilize the user-defined method can be granted to selected users through the security roles. In terms of GUI security, user defined methods are handles in the same manner as other standard operations like Create and Modify.

Applying the User-Defined Method to Multiple Objects

A user-defined method may also support multiple object selection. If this functionality is supported, you can click on the selection box for each object of interest or use the Select All button to select all the items and then click the user-defined method. If multiple objects are selected, the provisioning page will display parameters from the user-defined method. Selected values will be passed to the user-defined method along with the list of selected objects.

When you click the user-defined button with multiple object selected, the GUI will open a transaction and then call the user-defined method. If the transaction succeeds, the GUI will display a message indicating that the operation has succeeded. If the transaction fails, the associated error message will be displayed.

When you are working with multiple objects you must observe the following.

The GUI does not check whether the selected objects are pending or not. If a user-defined method is run on the pending objects it may result in an error, which will be caught by the provisioning server.

If you want to perform the user-defined method on all objects that satisfy a particular search criteria in the lister, use the Select All button and execute the user-defined method on each lister page.

Currently, there is a limitation on passing a large number of objects for operations (delete and user-defined method. The maximum number of objects that can be selected for a user-defined method is 200. If you select more than 200 objects either by "Select All" or manually selecting the check boxes, a warning message will be displayed.

The GUI view for a user-defined method that supports multiple objects can only contain non-refresh, enumerated attributes.