The Organizational view (aka Org-Chart/Services view) allows you to group subnets and device models based on organizational considerations such as:
• Corporate structure; for example, the finance department network device models are grouped in their own organizational view.
• Services; for example, a set of devices are essential for supporting the E-mail service which provides E-mail for several different departments.
• Administrative responsibilities; for example, an operator has been assigned responsibility for all routers in your network.
A variety of Org-Chart/Services views are available to help you manage your network based on your specific needs and network design. The first example below shows how to use organizational views to track the
business impact of network problems by modeling how corporate services are linked to corporate structure.
The second example shows how to use organizational views to track network problems by administrative responsibility.
Creating a Network Model that Shows the Business Impact of Services on Administrative Structure
The procedure described below is an example of how to create an Org-Chart/Services view for the management of a service that one or more administrative groups depend on.
1. From the View menu of any Topology view, select New View > Org-Chart/Services.
2. Select Edit from the File menu in the Org-Chart/Services view.
3. Select New Model from the Edit menu.
4. Select Department from the New Model dialog box and click OK.
5. Enter a unique name to best represent your Department model. In this example, the model name is Engineering because it will contain the devices and services that the Engineering department depends on. The Department model icon will appear in the Org-Chart/Services view.
6. Select Close Edit from the File menu.
7. Double-click on the view button on the Engineering Department model to navigate into the Engineering Department container.
8. Select Edit from the File menu.
9. Select New Model from the Edit menu.
10. Select Service_Owns from the New Model dialog box and click OK.
11. Enter a unique name to best describe the service you want to
represent. In this example, the model name is E-mail because it will contain the devices that make up the E-mail service. The
Service_Owns model icon will appear.
12. Select Close Edit from the File menu.
13. Double-click on the view button on the E-mail Service_Owns model to navigate into the E-mail Service_Owns container.
14. Select Edit from the File menu.
15. You will need to place all device models that represent components of the E-mail service into this container.
If these devices are already modeled in another view (or views), go to that view and use the Copy command to copy those models. Return to this view and paste the models into the container.
If these devices have not yet been modeled, you can create models for them using the Edit > New Model command (see Adding and Removing Device Models [page 49] for further instructions).
16. Select Close Edit from the File menu.
17. You have now created a model to manage the E-mail service and have shown that the Engineering department depends on this service.
Other Department container models can be created to represent additional departments. (Enterprise, Division, Landscape, or Subsidiary container model types can also be used.) The E-mail Service_Owns container can be copied and pasted into any of those Department containers that represent departments which depend on the E-mail service.
The condition of a service is displayed on the Service_Owns container model. For example, if two routers contained in the E-mail Service_Owns container have gone down and a red alarm is generated on each of them, the E-mail Service_Owns container model will show a red condition. If you open the Alarm Manager from the Service_Owns container model,
SPECTRUM shows all alarms for devices contained within the Service_Owns container.
In addition, the rollup condition (see Rollup Condition Colors [page 102]) of the department is displayed on the Department container model. Thus, if network problems exist which affect services to a department, this will be reflected in the rollup condition shown on the Department container model.
Once you have created a network model that represents your enterprise’s departments and services, the business impact of network problems can be easily determined. Network operators can correlate an alarm on a single device to the service(s) this device is critical to, and the departments that depend on that service.
Creating a Network Model that Shows Administrative Responsibilities The procedure described below is an example of how to create an Org-Chart/Services view for the management of routers that a given administrator is responsible for.
1. From the View menu of any Topology view, select New View > Org-Chart/Services.
2. Select Edit from the File menu in the Org-Chart/Services view.
3. Select New Model from the Edit menu.
4. Select Org_Owns from the New Model dialog box and click OK.
5. Enter a unique name to best represent your Org_Owns model. In this example, the model name is ITClevelandRouters because it will contain all of the routers that the IT department in Cleveland is responsible for. The Org_Owns model icon will appear in the Org-Chart/Services view.
6. Select Close Edit from the File menu.
7. Double-click on the Org_Owns view button to open the view.
8. Select Edit from the File menu in the Org_Owns view.
9. Copy all routers that the IT department in Cleveland is responsible for into this view as follows:
a. Open the applicable Topology view and select Edit from the File menu.
b. Highlight all routers in the Topology view to be copied into the Org_Owns view.
c. Select Copy from the Edit menu in the applicable Topology view.
Click OK in the Confirm dialog box.
d. Select Paste from the File menu in the Org_Owns view. All routers copied will appear in the view.
e. You can arrange routers in the view as shown below.
File View Tools Bookmarks Help
0 Org_Owns ITClevelandRouters
0
SpectroGRAPH: Org-Chart/Services: TopOrg
f. Select Close Edit from the Topology views and the Org_Owns view to return to view mode.
10. Using the Annotation Tool Box, label each router as to its location or significance. This will allow identification of the router for
manageability.