28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Use the following command to display information about the local certificate:<br />

aviva@RouterA> show security pki local-certificate<br />

Certificate identifier: local-entrust<br />

Issued to: RouterA.mycompany.com, Issued by: mycompany<br />

Validity:<br />

Not before: 2005 Nov 21st, 23:28:22 GMT<br />

Not after: 2008 Nov 21st, 23:58:22 GMT<br />

Public key algorithm: rsaEncryption(1024 bits)<br />

Public key verification status: Passed<br />

The first line of the output shows the name of the certificate—here, local-entrust.<br />

The second line shows the router and company to whom the certificate has been<br />

issued. The certificate is valid for three years from the date of issue.<br />

When you have the signed local certificate, configure IKE and IPSec to use it. The<br />

configuration is more involved than that shown in Recipe 3.3 because this recipe<br />

uses fewer of the default values.<br />

In configuring IKE, the set ike proposal command has IKE use the digital certificate<br />

for authentication (with the option authentication-method rsa-signatures) instead<br />

of the default preshared keys. In the IKE policy, the set proposals command references<br />

the IKE proposal. The second and third commands give the fully qualified<br />

domain names of the local and remote routers that are the IPSec tunnel peers. The<br />

last command configures the name of the local router’s digital certificate. Finally,<br />

define a rule for the IKE SA. This recipe creates a rule named digital-cert-rule. The<br />

first set term command defines the IP address of the remote end of the IPSec tunnel,<br />

and the second associates the IKE policy with the SA so that matching packets can be<br />

sent across the tunnel.<br />

Next, configure IPSec. The service set is the same as that shown in Recipe 3.3, with<br />

the addition of the set ipsec-vpn-options trusted-ca command, which points to the<br />

CA you defined with the set security pki ca-profile command. Finally, use the set<br />

ipsec-vpn establish-tunnels immediately command to create the IPSec tunnel immediately<br />

after the configuration is activated rather than wait for traffic before setting it<br />

up.<br />

In this recipe, the configuration for the services interface, the physical interface, and<br />

the IGP is the same as in Recipe 3.3. And again, configure the remote security router<br />

in the same way.<br />

To check the operation of IKE and IPSec, use the commands shown in Recipe 3.3.<br />

Use the show services ipsec-vpn certificates command to check that the correct<br />

digital certificates are being used to establish the IPSec tunnel:<br />

aviva@RouterA> show services ipsec-vpn certificates<br />

Service set: ipsec-domain, Total entries: 3<br />

Certificate cache entry: 3<br />

Flags: Non-root Trusted<br />

Issued to: RouterB.mycompany.com, Issued by: mycompany<br />

126 | Chapter 3: IPSec<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!