> - Downloads
> - Adding VPNs for Retailers and Enterprises

> # Adding VPNs for Retailers and Enterprises

> When you add a VPN to the SRC configuration, you are creating a VPN configuration object that represents a VPN that is already configured in the network. You can add a VPN for a retailer or for an enterprise.

> Before you add a VPN to the configuration, obtain the identifier for the VPN. This identifier is the name of the routing instances on a JUNOS routing platform that implements the VPN.

> To add a VPN to subscriber configuration for a retailer or an enterprise:

> 1. From configuration mode, access the configuration statement that configures the VPN.
>    `
>    [edit]
>    user@host# edit subscribers retailer name vpn vpn-id
>    `

>    or

>    `
>    [edit]
>    user@host# edit subscribers retailer name subscriber-folder folder-name enterprise name vpn vpn-id
>    `

>    where vpn-id is the name of the routing instances on a JUNOS routing platform that implements the VPN.

> 2. (Optional) Provide a name to identify the VPN as it appears in other SRC components, such a the Enterprise Manager Portal or other login pages.
>    `
>    [edit subscribers retailer name vpn vpn-id ]
>    user@host# edit display-name display-name
>    `

>    For example, to label the VPN as one used for video conferences with corporate partners:

>    `
>    [edit subscribers retailer name vpn vpn-id ]
>    user@host# edit display-name “ Partner Video Conference”
>    `
> 3. (Optional) Add a description of the VPN.
>    `
>    [edit subscribers retailer name vpn vpn-id ]
>    user@host# edit description description
>    `

>    For example:

>    `
>    [edit subscribers retailer name vpn vpn-id ]
>    user@host# edit description “ VPN for video conference with partners”
>    `
> 4. Verify that the configuration is correct. For example:

>        [edit subscribers retailer Acme vpn 1234]
>        user@host# show
>        display-name "Partner Video Conference";
>        description "VPN for video conference with partners.";

> #### Published: 2009-09-13

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.