Network Router User Manual
Table Of Contents
- Router Platform User Interface Reference
- NAT Policy Page
- Router Interfaces Page
- Advanced Interface Settings Page
- AIM-IPS Interface Settings Page
- Dialer Policy Page
- ADSL Policy Page
- SHDSL Policy Page
- PVC Policy Page
- PPP/MLP Policy Page
- AAA Policy Page
- Accounts and Credential s Policy Page
- Bridging Policy Page
- Clock Policy Page
- CPU Policy Page
- HTTP Policy Page
- Console Policy Page
- VTY Policy Page
- Secure Shell Policy Page
- SNMP Policy Page
- DNS Policy Page
- Hostname Policy Page
- Memory Policy Page
- Secure Device Provisioning Policy Page
- DHCP Policy Page
- NTP Policy Page
- 802.1x Policy Page
- Network Admission Control Policy Page
- Logging Setup Policy Page
- Syslog Servers Policy Page
- Quality of Service Policy Page
- BGP Routing Policy Page
- EIGRP Routing Policy Page
- OSPF Interface Policy Page
- OSPF Process Policy Page
- RIP Routing Policy Page
- Static Routing Policy Page
K-165
User Guide for Cisco Security Manager 3.2
OL-16066-01
Appendix K Router Platform User Interface Reference
Secure Device Provisioning Policy Page
Petitioner
Authentication
The CA server that authenticates the identity of the petitioner:
• Local CA Server—Select this option when the router itself is already
configured to act as the CA server. Enter the name of the local CA in the
field provided.
Note If you have not configured the router as the CA server, enter the
command Crypto pki server [name] using the CLI or FlexConfigs.
This command is mandatory when you deploy an SDP policy
configured with a local CA server.
• Remote CA Server—Select this option when using an external CA
server. Enter the name of a a PKI enrollment object, or click Select to
display an Object Selectors, page F-593.
If the server you want is not listed, click the Create button in either
selector to display the PKI Enrollment Dialog Box, page F-481. From
here you can define a PKI enrollment object.
Introduction Page The source of the introduction page to display to the introducer after
authorization is performed:
• Use default introduction page—Uses a default page provided with
Security Manager.
• Specify introduction page URL—Uses the introduction page specified
in the URL field. Supported protocols include: FTP, HTTP, HTTPS,
null, NVRAM, RCP, SCP, system, TFTP, Webflash, and XMODEM.
Table K-73 Secure Device Provisioning Page (Continued)