|
|
This chapter describes the functionality of the CPC GUI. It provides an overview of the following areas:
In addition to the FTI, CPC offers a GUI which can be used for both administrative tasks and service provisioning.
This section describes each GUI viewer and explains how to navigate between them.
The CPC GUI uses a model-view controller paradigm to manipulate objects. CPC models an object, such as a PVC. That model can be seen through different viewers providing unique ways of visualizing the model. When the model is viewed, controllers provide ways to manipulate the model.
The CPC GUI is also an object-action based interface. An object, such as a Service Object or a Node Object, can be selected and actions are performed on that object (such as modifying and uploading). The GUI also supports direct manipulation, allowing you to perform operations like cutting and pasting objects between viewers.
Objects can be displayed a variety of ways. Viewers are accessed from the View menu on the menu bar. Most action commands are initiated by selecting menu options on the menu bar. Below the menu bar is CPC's toolbar. The toolbar provides you with immediate access to the actions that are used most often. The toolbar uses icons to represent commands. Table 6-1 outlines the commands that you can execute from the CPC toolbar.
| Icon | Description |
|---|---|
| Apply--Click this button to apply the highlighted Transaction. |
| Abandon--Click this button to stop all preparation, delivery, and activation operations in progress and place the highlighted Transaction in a state of Rejected. |
| Close--Click this button to close the highlighted Transaction. |
| Get List--Click this button to get a list of objects based on the criteria that you have entered. |
| Copy--Click this button to copy information that you have highlighted. |
| Delete--Click this button to delete the object that you have highlighted from CPC's database. |
| Service Viewer--Click this button to show the Service Viewer for the service object that you have selected. |
| Save--Click this button to save the object you are creating or modifying. |
| Find to Paste--Click this button to select form a list of values available for the particular cell you have chosen. |
| Log Viewer--Click this button to open a Log Viewer. |
| Object Viewer--Click this button to open an Object Viewer. |
| Open--Click this button to open a Transaction. |
| Paste--Click this button to paste information that you have viewer. |
| Paste Context--Click this button to paste an object into a viewer. |
| Schedule--Click this button to schedule a Transaction. |
| Stop--Click this button to stop the current command. |
| Subset Viewer--Click this button to open a Subset Viewer. |
| Tree Viewer--Click this button to open a Tree Viewer. |
| Unschedule--Click this button to unschedule a Transaction. |
CPC's main window also has a series of status indicators at the bottom of the window. The Status Indicator indicates the progress of the action that you have selected. The Transaction Indicator specifies the number and name of the Current Transaction. The Progress Bar is a graphical representation of the progress of an CPC task. There are several Filter Bars that allow you to filter a list for certain criteria. The Toolbar contains a set of functions that are used the most when provisioning a service. The Menu Bar contains all of the actions that you are able to perform when using CPC. The Base Type Selector and Navigation Bar are windows within the Subset Viewer that are used to navigate between classes.
The copy and paste feature allows data to be copied from one field and pasted into another. Objects can be copied from any field (in the Tree Viewer, Object Viewer or Subset Viewer) and pasted into any field in the Object or Subset Viewers. Objects such as networks, nodes and physical ports can be copied and pasted into the current field.
The following list summarized the functionality of the copy and paste feature with respect to the Object Viewer:
The following list summarizes the functionality of the copy and paste feature with respect to the Subset Viewer.
CPC's Tree Viewer provides a group of Folders that illustrate containment relationships. These folders are used to access CPC objects.
The Root folder represents the highest level within the CPC Tree Viewer. When you open a Tree Viewer, only the Root folder is visible. Double-click the Root folder to see all of the folders it contains. These folders may include:
The Service Application folder provides access to Service objects and Service object profiles. Within this folder you will find subfolders for each of the following available Service Applications:
Within each Service Application folder there are subfolders that provide access to Service Objects and Service Object profiles. Initiating a Subset Viewer or Object Viewer from these subfolders will enable you to create, modify, and delete specific Services and Service Object profiles.
The Upload Request folder provides address to all of CPC's Upload Requests. Double-click Upload Request to see a list of all the Upload Requests and their ID numbers. The Upload Request folder can be used to monitor the status of uploads. Double-click a specific Upload Request to see a subfolder containing a list of objects that were uploaded within the context of that Upload Request. To view the attributes of an uploaded object, click the object in the Tree Viewer and click the Object Viewer button on the toolbar.
The Transaction folder provides access to all of CPC's Transaction Management commands. Double-click Transaction and a list of all the Transactions, including their State and ID number will appear. To create a new Transaction as required, click the Transaction folder and click the Subset Viewer button on the toolbar.
Each Network folder provides access to all of CPC's Network Objects. Double-click a Network folder to access the following objects:
Double-click any of these folders to display a list of the corresponding objects.
The Equipment Module folder provides access to all of CPC's installed Equipment Modules and their service element profiles. Double-click the Equipment Module folder to access a list of the installed Equipment Modules. Double-click a specific Equipment Module folder to see a list of the PVCs, logical ports, VCs, and other vendor-specific Service elements. You will also see service element profiles within the Equipment Module folder.
The System Log folder provides access to an Event Log as well as logs for the specific Equipment Modules. To view a log click it and then select Long Viewer from the View menu. The Log Viewer displays messages as they are written to the log. Messages appear in chronological order. A scroll bar enables you to scroll backwards through the log.
Log files which can be viewed are described in detail in the chapter "Maintenance".
Content-specific viewer are provided so that you can visualize objects and efficiently access critical configuration details.
The CPC Tree Viewer is the starting point for CPC GUI navigation. It contains a set of folders that contain other labelled folders. Folders are provided for Service Object, Transaction, Generic Objects, and Network Elements. The Tree Viewer displays information based on containment relationships. This allows you easier navigation to specific objects. The Root folder contains the following subfolders:
You can filter the contents of any of the folders in the Tree Viewer using the filtering fields at the bottom of the Tree Viewer window. To filter a selection, enter the criteria in the appropriate field and then click the get list button on the toolbar. A number of wildcarding and pattern-matching options are supported. The filter criteria for each attribute remains in the corresponding filter field until it is modified or deleted. The get list button must be clicked after every filter operation to show the new search criteria.
The Subset Viewer provides an expanded view of an object or list of objects. To open a Subset Viewer, click an object in the Tree Viewer and then click the Subset Viewer button on the toolbar. CPC's Subset Viewer displays information in a spreadsheet format. Attribute fields can be added or removed from the Subset Viewer, refer to the section titled "Customization" in this chapter for more information. The Subset Viewer allows you to list, create, modify, and delete objects. Figure 6-5 shows an example of a CPC Log Viewer.
You can filter the contents of the Subset Viewer using the filter row at the top of the viewer. To filter a selection, enter the criteria in the appropriate field and then click the get list button on the toolbar. A number of wildcarding and pattern-matching options are supported. The filter criteria for each attribute remains in the corresponding filter field until it is modified or deleted. The get list button must be clicked after every filter operation to show the new search criteria.
The CPC Log Viewer provides an expanded view of a log. To open a Log viewer, click a log object in the Tree Viewer and then click the Log Viewer button on the toolbar. CPC's Log Viewer displays information in a notepad format. Transaction logs and system logs can be viewed within the Log Viewer. Figure 6-5 shows an example of a Log Viewer.
The CPC Object Viewer provides an expanded view of objects and their attributes. To open an Object Viewer, click an object in the Tree Viewer and then click the Object Viewer button on the toolbar. The Object Viewer may contain some attributes that are not accessible from the Subset Viewer. Figure 6-6 shows an example of an Object Viewer.
The Service Viewer window provides a graphical representation of activated Services. To open a Service Viewer, click a service object in the Tree Viewer and then click the Service Viewer button on the toolbar. You can display the Service Viewer for the associated object by double-clicking on its name and/or symbol.Figure 6-7 shows an example of a Service Viewer.
Information contained in the Help menu acts as an online resource that can be accessed at any time during an CPC GUI session. The information contained in the Help menu is the same as the information contained in this guide. This includes Service Applications, Equipment Modules and general CPC information. The help system is HTML based and includes hypertext links that can be selected when more information is needed about a particular topic. The following help modes can be found in the Help menu:
Figure 6-8 shows an CPC Help Viewer.
The Help Viewer contains two views that are used to navigate and display the contents of the help system.
The navigational view allows you to navigate through the contents of the help system when the table of contents or index tabs have been selected. This view is analogous to the Tree Viewer in the CPC GUI. Topic folders can be opened to reveal their contents or they can be closed to hide them. Double-clicking topics in this view displays their contents in the content view.
This view also allows you to perform searches when the find tab is selected.
The content view displays information on the topic selected in the navigational view. You can also navigate this view by double-clicking hypertext words and phrases that reveal more detail about a topic. Back and forward buttons can be used to navigate through the pages in this view.
Navigation within the Help Viewer is analogous to navigating a web page. You can move forward or backward through pages much like you would navigate the hypertext pages on a web browser. You can select specific topics by navigating through topic folders in the navigational view (for more information on the views in the Help viewer, refer to the section titled "Views Within the Help Viewer" in this chapter). Table 6-2 below describes the buttons and tabs available in the Help Viewer.
| Icon/Tab | Description |
|---|---|
| Table of Contents. This tab allows you to select help topics from a list and to read their contents. This is analogous to navigating the Tree Viewer in the CPC GUI. Double-clicking a topic displays its contents in the content viewer. |
| Index. This tab allows you to select help topics from an index and to read their contents. Double-clicking a topic displays its contents in the content viewer. This tab also contains a find field that can be used to filter through the list of topics in the index |
| Back. This button allows you to go back one page in the content view. |
| Forward. This button allows you to go forward one page in the content view. |
| Print. This button allows you to print the topic displayed in the content view. After clicking this button, a dialog box appears. Information about the number of copies, printer, and print options can be specified in this box. Click the Print button in the dialog box to print. |
There are four different help modes that can be accessed through the Help menu.
This mode allows the user to retrieve general information about CPC. This mode is not dependent on the current viewer or object and can be used at any time.
This mode allows the user to retrieve information about the current viewer. For this mode to be operational, a viewer must be selected. If no viewers are selected, an error message will appear.
Opening a Transaction sets the operational mode of a change to the network to manual. One or many services may be created, modified or deleted within a Transaction. The associated configuration changes will either all be applied to the network or if any of the changes is not possible, all will be rolled back. A single Transaction may contain changes for multiple services, but changes to a single service will never span multiple Transactions.
The Transaction Subset Viewer is the primary interface to the Transaction. From the Transaction Subset Viewer you can use the get list function to list the Transactions that match specific search criteria and you can create, delete, open, or close a Transaction. It is also from this window that you would apply the current Transaction to the network, schedule a Transaction for a later date/time, or unschedule or abandon it beforehand. A scheduled Transaction can also be rescheduled for a different time. Figure 6-9 shows an example of a Transaction Subset Viewer.
To create a Transaction, perform the following procedure:
Step 2 Click the Transaction folder to highlight it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Enter the appropriate values in the available row of cells and press Enter on the keyboard. The Transaction is created and put into the Ready State.
CPC object configuration changes must be made within an open Transaction. To open a Transaction, perform the following procedure:
Step 2 Click the Transaction folder to highlight it.
Step 3 Click the specific Transaction that you want to open to highlight it.
Step 4 Select open from the Transaction menu. The Transaction is now opened and put into the Current State.
 |
Note You are only able to open Transactions that are in the Ready State. |
Once the necessary configuration changes have been made, a Transaction must be selected (put into the Ready State) before it is applied.
Step 2 Click the Transaction folder to highlight it.
Step 3 Click the specific Transaction that you want to open to highlight it.
Step 4 Select close from the Transaction menu. The Transaction is now closed and put into the Ready State.
CPC will enable you to choose Transaction processing in the foreground session or in a background session. The apply function uses foreground processing as the default. While a Transaction is processing using the apply function, all other Transaction activities will be blocked from processing.
When you use the apply function, the Transaction is processed immediately in the foreground session. If a Transaction is scheduled for a future date/time using the schedule function, that Transaction will be processed at that late date/time in the background.
The apply function is available to any session, and performs all of the steps of Transaction processing. It allows a single session to carry a Transaction through all phases from Ready to Applied or to Abandoned.
To apply a Transaction:
Step 2 Double-click the Transaction folder to open it.
Step 3 Click the specific Transaction that you want to apply to highlight it.
Step 4 Select apply from the Transaction menu or click the apply button on the toolbar. The Transaction is now applied to the database.
CPC provides with the ability to schedule a Transaction to be applied to the network at a later date and time. You are able to request that a Transaction be applied within minutes, hours, days, months, or years. After the date has been specified, the Transaction will rest in the Scheduled state until the date and time become current. At that moment, the Transaction will be applied automatically. If "now" is specified as the time, the Transaction will be applied immediately in the background. Other Transaction activities will not be blocked from processing if the Transaction is scheduled as "now."
To schedule a Transaction:
Step 2 Click the Transaction folder to open it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Select the Transaction that you wish to schedule by clicking on a row to highlight it. Each row within the Transaction Subset Viewer represents one Transaction.
Step 5 Click the Schedule button on the toolbar. A Scheduling Window will appear.
Step 6 Within the Scheduling Window, enter the time that you wish to schedule the Transaction in the field provided. This field contains "now" as the default. If "now" is used, the Transaction will be applied immediately in the background. The time must be in the yyy/mm/dd hh:mm:ss format, and hh:mm:ss must use a 24 hour clock. See Figure 6-10 for an example of this format.
Step 7 Once the date and time, or the command "now" have been entered, click the OK button to schedule the Transaction. The State within the Transaction Subset Viewer should change from Ready to Busy. The State will remain Busy until the scheduled time becomes current, then it will change to Applied. The scheduledfortime field for the corresponding Transaction should reflect the time that you specified.
Once you have scheduled a Transaction, you have the option of re-scheduling it. To re-schedule a Transaction.
Step 2 Click the Transaction folder to open it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Select the Transaction that you wish to schedule by clicking on a row to highlight it. Each row within the Transaction Subset Viewer represents one Transaction.
Step 5 Select schedule from the Transaction menu. A Scheduling Window will appear.
Step 6 Within the Scheduling Window, enter the time that you wish to re-schedule the Transaction in the field provided. This field contains "now" as a default. If "now" is used, the Transaction will be applied immediately in the background. The time must be in the yyyy/mm/dd hh:mm format, and hh:mm must use a 24 hour clock.
Step 7 Click OK to re-schedule the Transaction. Within the Subset Viewer, verify that the schedule has changed by clicking get list from the tool bar. The scheduledfortime field for the corresponding Transaction should reflect the newly scheduled time.
Once a Transaction is scheduled, it is possible to abort it before it is applied. When the Transaction is aborted, it is returned to the ready state. The configurations contained within the Transaction remain intact by the scheduling details are cleared. When the Transaction is in the Ready state, you can open it again to add more changes, apply the changes immediately, or schedule the Transaction again.
To abort a Transaction:
Step 2 Click the Transaction folder to open it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Click the scheduled Transaction you want to abort to highlight it and select abort from the Transaction menu.
Step 5 Click the get list button on the toolbar to verify that the Transaction State is now "Aborted."
To list Transactions:
Step 2 Click the Subset Viewer button on the toolbar.
Step 3 Select a state from the State menu within the Transaction Subset Viewer.
Step 4 Click the get list button on the toolbar. A list of Transactions in the State that you specified appears within the Transaction Subset Viewer.
CPC enables you to view Transactions according to a variety of different variables. Variables include Transaction number, State, Submission date, Submitted by, Domain, Customer, scheduledfortime and Brief Description. The process of listing specific Transactions according to a certain variable consists of the following steps:
Step 2 Click the Transaction folder to highlight it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Click a filter field above the green bar in the Transaction Subset Viewer. Enter the information for the attribute you want the list filtered for.
Step 5 Click the get list button on the toolbar. The filtered list of Transactions appears in the Transaction Subset Viewer.
You can delete a Transaction that you no longer wish to keep. The delete function remove the applied or abandoned Transaction and all of its associated configuration and log files.
You can only delete Transactions in the Applied or Abandoned state.
Step 2 Click the Transaction folder to highlight it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Select the Transaction that you wish to delete by clicking on any of the fields in its rows. Each row within the Transaction Subset Viewer represents one Transaction.
Step 5 Click the delete button on the toolbar.
|
Note To delete multiple Transactions, hold down the Control key on the keyboard while clicking on the Transactions that you wish to delete. |
You can manually terminate the processing of a Transaction. This function stops all preparation, delivery, and activation operations in progress and places the Transaction in the Rejected state. All the changes within the Transaction are lost. During the Abandon process, the Transaction state changes from Aborting to Failed, then Rejected.
To abandon a Transaction:
Step 2 Click the Transaction folder to highlight it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Click the get list button on the toolbar.
Step 5 Click the scheduled Transaction that you wish to abandon by clicking on any of the fields in its row. Each row within the Transaction Subset Viewer represents one Transaction.
Step 6 Select abandon from the Transaction menu.
Step 7 Click the get list button on the toolbar to verify that the Transaction State is now "Abandoned."
CPC manages a database which contains a representation of the state of the network(s) being managed. This information is used to make modifications to the network fabric in order to satisfy user requests.
If delivery to any site in a Transaction fails, CPC reverses the changes to all sites in that Transaction. This process is called rollback. Under normal circumstances, rollback succeeds and the changes to the network fabric are removed.
Some circumstances, such as EMS failure during processing, may cause rollback to fail, leaving the network fabric in some indeterminate state. When this occurs, the state of the CPC database no longer represents the state of the network.
Refer to the section titled "Rollback" in the chapter titled "General Functions and Features" for a description of how an Operator should recover from this kind of failure.
CPC allows multiple Transactions to process in parallel. Parallel processing provides higher throughput because more processors are used. Concurrent Transactions are supported only in CPC installations where all Equipment Modules support concurrent Transactions. If an Equipment Module does not support concurrent Transactions, then CPC only supports serial processing.
Each Equipment Module contains a configuration variable within its configuration file (.cfg) that indicates whether or not that Equipment Module supports concurrent Transactions. The variable cc.supportConcurrentRequests (where cc represents the Equipment Module code) is set to 0 if the Equipment Module does not support concurrency. The variable is set to 1 if the Equipment Module supports concurrent Transactions. This variable is not a user configurable property. If all Equipment Modules have their blade-specific supportConcurrentRequests variable set to 1, then the global variable SYRTM.enableConcurrentRequests will be set to "on." otherwise this variable will be set to "off."
Configuration files for each EM can be found in the $CCP REL/mng/config directory, where $CCP REL is the CPC Server home directory.
In CPC 2.0 there are two types of profiles:
Service object profiles are used to store default attribute values for creating Service objects, such that it is not necessary for an Operator to supply values for all of the attributes when activating a Service. You can simply supply the name of a Service object profile on the Service object Subset Viewer and the Service object itself retrieves the attribute values from the profile.
Service element profiles are used to store the vendor specific attributes for PVCs, VCs and logical ports. There is a corresponding Service element profile for each type of service element that the Equipment Module supports. Service element profiles provide initial attribute values for the corresponding object class whenever a new object of that class is created. A Service element profile can be specified when creating Service object profiles or when activating Services.
Default Service element profiles are provided with CPC and can also be used when activating Services. These default profiles are intended for demonstration and/or evaluation purposes of CPC and are not designed to represent each provider's network or service offerings. You must create new profiles based on your own network configuration and service offerings or modify the default profiles to function in your own operating environment.
There are certain attributes in Service element profiles that should not be modified. If these values are modified, the new values that you have specified will not take effect. The tables that follow list common elements that are included in Service element profiles but have no effect when modified.
| Attribute | Description |
|---|---|
srpriority | Recovery Priority |
srsoid | Service Object Id |
sraz_bandwidth, srza_bandwidth | AZ bandwidth, ZA bandwidth |
raa_vpi, raz_vpi | A/Z side VPI |
raa_vci, raz_vci | A/Z side VCI |
raaz_pcr, raza_pcr | AZ/ZA Peak Cell Rate |
raaz_scr, raza_scr | AZ/ZA Sustained Cell Rate |
raaz_mcr, raza_mcr | AZ/ZA Minimum Cell Rate |
raaz_mbs, raza_mbs | AZ/ZA Maximum Burst Size |
ATM SPVC Service Element Profile non-modifiable attributes include the attributes specified in Table 6-2 with the following additions:
| Attribute | Description |
|---|---|
raaddress | ATM address |
raaddresstype | ATM address type |
| Attribute | Description |
|---|---|
srpriority | Recovery Priority |
sroid | Service Object Id |
sraz_abandwidth, srza_bandwidth | Frame Relay AZ/ZA Bandwidth |
sraz_zbandwidth, srza_zbandwidth | ATM AZ/ZA Bandwidth |
rfa_dlci | Frame Relay DLCI |
raz_vpi | ATM VPI |
raz_vci | ATM VCI |
rfaz_cir, rfza_cir | AZ/ZA Frame Relay Certified Information Rate |
rfaz_bc, rfza_bc | AZ/ZA Frame Relay Burst Committed |
rfaz_pcr, raza_pcr | AZ/ZA Frame Relay Burst Excess |
raaz_pcr, raza_pcr | AZ/ZA ATM Peak Cell Rate |
raaz_scr, raza_scr | AZ/ZA ATM Sustained Cell Rate |
raaz_mcr, raza_mcr | AZ/ZA ATM Minimum Cell Rate |
raaz_mbs, raza_mbs | AZ/ZA ATM Maximum Burst Size |
| Attribute | Description |
|---|---|
srpriority | Recovery Priority |
srsoid | Service Object Id |
sraz_bandwidth, srza_bandwidth | AZ/ZA Bandwidth |
rfa_dlci | A-Side DLCI |
rfz_dlci | Z-Side DLCI |
rfaz_cir, rfza_cir | AZ/ZA Frame Relay Certified Information Rate |
rfaz_bc, rfza_bc | AZ/ZA Frame Relay Burst Committed |
rfaz_be, rfza_be | AZ/ZA Frame Relay Burst Excess |
| Attribute | Description |
|---|---|
srpriority | Recovery Priority |
srsoid | Service Object Id |
sraz_bandwidth, srza_bandwidth | AZ/ZA Bandwidth |
srpriority | Recovery Priority |
srsoid | Service Object Id |
raz_vpi | ATM VPI |
raz_vci | ATM VCI |
raaz_pcr, raza_pcr | AZ/ZA ATM Peak Cell Rate |
Some of the attributes are duplicated. For example, you can specify the QoS for an ATM service when you create the service, when you create the Service object profile, and when you create the Service element profile. If you provide different values for the same attribute in multiple places, the Threader will override the values based on the following scale of priorities:
1. Service object Subset Viewer--All information provided in the Service object Subset Viewer is used to create the Service.
2. Service object profile--The attributes specified in the Service object profile are only used if they are available or specified in the Service Object Subset Viewer.
3. Service element profile--The attributes specified in the Service element profile are only used if they are not specified in the Service object profile or in the Service object Subset Viewer.
The Threader selects a path for each activated service based on the attributes you specified when you created the service, the Service object profile (if specified), and the Service element profile (if specified). If you wish, you can customize the Threader path by adding your own custom callout code. The custom callout code allows you to adjust the priorities of the candidate paths before the Threader lays them in.
The Network Manager must establish names for the classes of service which will be offered (for example, Gold, Silver, and Bronze ATM service). Service object and Service element profiles can then be created for each of these classes of service. When you activate a Service object, you provide the name of the Service object profile and the service element profile to be used. Attributes which are not specified on the Service object Subset Viewer (including all of those which are not defined in the resource model) take their values from the profiles.
For each class of service, the Network Administrator should create profiles before any services are provisioned.
When a Service is traversing multiple networks composed of multi-vendor equipment, it uses the name of the Service element profile and looks for this profile for each Equipment Module it is communicating with.
It is important to use the same name for the Service element profile to define similar classes of service among different networks. For example, if you are creating an ATM service that crosses two different networks composed of different vendor's equipment you could specify that you want it to use the "Gold" Service element profile and to use the "Gold" Service element profile for any of the networks that service is traversing, the service will use the default Service element profile for that service.
Hybrid ATM QoS provides you with the option to not select a QoS when you activate a service, and instead indicate that it is profiled in the Service element profile. This allows you to use multiple networks with different QoS. For more information about Hybrid ATM QoS, refer to the chapter titled "Provisioning ATM Services"
The Local Access Transport Area (LATA) defines the geographic area over which the Local Exchange Carrier may provide toll calls. When creating a Network Connection, CPC will take LATAs into account. Both endpoints and all intermediate Logical Ports in a Service must also be in that LATA (have the same value in srnode.srarea). Any Logical Ports that do not have this value are removed from the list of candidate paths. The name of the LATA is stored in the attribute srarea.
CPC's GUI allows you to customize the Subset Viewer to include or exclude certain attributes depending on your requirements. You must create a file named SPgui.properties. This file is user-definable and overrides any information in the default GUI.properties files that are shipped with CPC. The SPgui.properties file will be loaded last, enabling the customization changes to be initialized upon start up of the CPC GUI.
To add, modify, or delete object attributes within the Subset Viewer.
Step 2 Navigate to $CCP REL/sys/resources.
Step 3 Open the .properties file that contains the FilterContainer of attributes that you want to add other attributes to. Refer to Table 6-6 below for a description of Equipment Module and Service.properties files.
Step 4 Copy the FilterContained of the object that you want to modify from the specific .properties file (shipped with CPC) into the CPgui.properties file.
Step 5 In a separate window, as the admin use, open the SPgui.properties file contained in the directory $CCP REL/sys/resources.
Step 6 Paste in the FilterContainer that you have copied from the original .properties file.
Step 7 Redefine the FilterContainer values to include the attributes that you require for a certain object. Add or delete attributes to the specific FilterContainer as required.
|
Note To add or delete attributes, you will need to know the name of the those attributes. For more information on attributes, refer to the section on OAD files in the Cisco Provisioning Center Programme's Guide. OAF files are located in $CCP REL/sys/bin. |
For example, the unmodified configuration of DSL Subscriber Aggregation Point Service and Service Profile that will appear in the Subset Viewer contains the following attributes in the SDL gui.properties file:
#------------------------------------ #SDL Connection #------------------------------------ SDLConnection.CAN Be CREATED = true SDLConnection.CAN Be MODIFIED = true SDLConnection.CAN BE DELETED = true SDLConnectionProf.CAN Be CREATED = true SDLConnectionProf.CAN Be MODIFIED = true SDLConnectionProf.CAN Be DELETED = true SDLConnection.OBJECT NAME = name SDLConnectionProf.OBJECT NAME = sy profname SDLConnectionProf.CLASS NAME = DSL Subscriber Aggregation Point Service Profile FilterContainer | SDLConnection.SEARCH ATTRIBUTES = name srprofile.sy profname provider pap maxsubscribers aggpoint agginterfacetype bridgeprofile ipaddress uprate dnrate connectprofile providervpi providervci providerdlci policy rfu1 rfu2 FilterContainer | SDLConnectionProf.SEARCH ATTRIBUTES = sy profname vpn agginterfacetype uprate dnrate maxsubscribers
Step 8 After the modifications have been made, save the file and exist the text editor.
Step 9 Restart the client to verify the changes to the GUI.
|
Note Make sure that you are working within the CPgui.properties file and NOT the files shipped with CPC. |
| GUI Properties File | Description |
|---|---|
CSgui.properties | Cisco Equipment Module GUI properties |
RASOgui.properties | ATM Service GUI properties |
RFSOgui.properties | Frame Relay Service GUI properties |
SCBSOgui.properties | Private Line Service GUI properties |
SDLgui.properties | DSL Service GUI properties |
SLIgui.properties | T-LAN Service GUI properties |
SYgui.properties | GUI color parameters and behavior |
You can change the default color and font sizes found in the GUI by modifying the SYgui.properties file. This file contains properties that can be manipulated in order to change the look and feel of the GUI.
To modify the GUI's appearance, complete the following steps:
Step 2 Navigate to $CCP REL/sys/resources.
Step 3 The SYgui.properties file contains the properties that can be modified. Open the SYgui.properties file using a text editor.
Step 4 This file contains the GUI's configurable attributes. You can customize the colors, fonts and font sizes that appear in the GUI.
Step 5 After making the changes, overwrite the SYgui.properties file and exit the text editor.
Step 6 Restart the client and verify the changes to the GUI.
Posted: Thu Aug 3 16:37:57 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
