|
|
The Cisco AccessPath Manager (APM) Configuration Template Manager allows you to manage APM default and custom configuration templates.
APM configuration templates are text files that contain Cisco IOS command-line interface (CLI) commands and template variables. APM creates configuration files to download to the devices in your AccessPath system by substituting data for the template variables based on your entries:
There are two types of templates:
The basic tasks you can perform using the Configuration Template Manager include:
This chapter concludes with an example of creating and using a custom configuration template, "ExampleConfiguring a Cisco AccessPath-LS3 System".
Table 5-1 lists the default configuration templates for each type of AccessPath platform.
| System | Template | Supports |
|---|---|---|
Cisco AccessPath-TS | Cisco 2511 | |
Cisco 7206 using a Catalyst 5000 for switching | ||
Cisco AS5200s using channelized T1 or E1 | ||
Cisco AS5200s using PRI | ||
Catalyst 5000 | ||
Cisco AccessPath-TS3 | Cisco 3640 | |
Cisco 7206 using two Switch Blade cards for switching | ||
Cisco 7206 using a Catalyst 5002 for its primary switching path | ||
Cisco AS5300s using channelized T1 or E1 | ||
Cisco AS5200s using PRI | ||
Catalyst 5002 |
To create a custom configuration template:
Step 1 Open the Template Manager. Click Configure, then Template Manager, then Execute. The Configuration Template screen appears. (See Figure 5-1.)

Step 2 Open the template you would like to use as the basis of your custom template.
(a) Use the pull-down menu in the Template Manager to select the device type. Valid choices include 2511, 3640, 7206, 7206_ENTRY, 7206_MIDHIGH, AS5200, AS5300, CAT5K, and All. Figure 5-1 shows the Configuration Template Manager screen with All selected.
(b) Click Open. APM will open the template in an editor to allow you to modify it. (See Figure 5-2.)

Step 3 Make any modifications you would like to the template.
Step 4 Edit the name field to give this template a new name and the description field to give this template a new description. Click Save As.
Step 5 (Optional.) Click the Back button on your browser to go back to the list of templates. Click the Update button in the Template Manager window to view the list of templates that includes the template you just created.
The template you have created can now be used to configure AccessPath shelves using Shelf Add or Shelf Modify. (See Chapter 4, "Configuring AccessPath Shelves Using APM.")
![]() | Caution If you delete a custom configuration template you will not be able to recover it. |
Step 1 Open the Template Manager. Click Configure, then Template Manager, then Execute. The Configuration Template screen appears. (See Figure 5-1.)
Step 2 Select the custom template you would like to delete. Use the pull-down menu in the Template Manager to select the device type of the custom template, then select the specific custom template you want to delete.
Step 3 Click Delete.
Step 4 (Optional.) Click the Back button on your browser to go back to the list of templates. Click the Update button in the Template Manager window to view the list of templates that no longer includes the template you just deleted.
This panel provides a summary of APM job status. Information on two kinds of jobs can be displayed:
To view job status, click Configure, then Config Job Status, then Execute.
To refresh the display for Scheduled Configuration Jobs, click Refresh.
To view a list of jobs that are currently waiting or actively running in the APM job queue, click Running/Queued Jobs.
To delete a scheduled configuration job, select the single job you would like to delete and click Delete Job Now.
The information provided in the Scheduled Configuration Jobs screen is as follows:
| Field | Description |
|---|---|
Job # | Identifier used by APM to uniquely identify scheduled configuration jobs. |
Job Type | Type of configuration job. |
Run Time | Time this job is scheduled to run, that is, when it will become a running/queued job. Time is shown in the format: MM/DD HH:MM.
|
Stack Name | User-defined named of the stack on which this process will be run. |
Shelf # | Number of the shelf on which this process will be run. This field only applies to shelf-specific operations. Stack-level processes, such as Modify Stack will be described as n/a. |
To be able to download configuration files to an AccessPath-LS3 system, you must complete the following steps.
Step 1 Create a custom configuration template for the Cisco 3640.
(a) Click Configure, then Template Manager, then Execute.
(b) Use the pull-down menu in the Template Manager to select the device type 3640.
(c) Select the Cisco 3640 default configuration template 3640-default. You will base your custom template on this default template. Click Open. APM will open the template in an editor to allow you to modify it. (See Figure 5-3.)

(d) Change the line:
to:
(e) Toward the end of the template and just after the SNMP server commands, you will find the line:
Change it to read:
(f) Edit the name field to give this template a new name and the description field to give this template a new description. Click Save As.
(g) (Optional.) Click the Back button on your browser to go back to the list of Cisco 3640 templates. Click the Update button in the Template Manager window to view the list of Cisco 3640 templates that includes the template you just created.
Step 2 Create a new stack. (See the section "Creating or Modifying a Stack" in Chapter 3, "Configuring AccessPath Stacks Using APM.")
When asked to choose a stack type, choose AP-TS3 (AS5300-based with optional Catalyst 5002).
Step 3 Add shelves to the stack. (See the section "Adding or Modifying a Shelf" in Chapter 4, "Configuring AccessPath Shelves Using APM.")
(a) Add the Cisco 3640 to the stack. When you are asked to choose a configuration template, select the custom configuration template you created for the Cisco 3640 (see Figure 4-4 and Table 4-8).
(b) Add the Cisco AS5300(s) to the stack.
The configurations will download to the devices in your Cisco AccessPath-LS3 system when you configured them to do so.
|
|