[c-nsp] Customer access to PE

[Aaron]

Perhaps they should have a vpls/vpws (mpls l2vpn) whereas they can do
whatever they want on the ce ends at their premise and you just give them
the wire between via an mpls l2vpn

Aaron

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
Richard Clayton
Sent: Tuesday, September 17, 2013 3:06 PM
To: Trey Howland
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Customer access to PE

I've worked in a couple of ISP's and MPLS VPN environments and have friends
that currently work in other providers, we've never had experience of
customers having configuration CLI access to what I presume is a PE with
multiple customers configurations on, I believe Provider Edge should be just
for the provider.


On 17 September 2013 13:12, Trey Howland <trey.howland at gmail.com> wrote:

> I have a scenario where a customer wants CLI access to the PE in the 
> provider's network.  This access would allow the customer to 
> create/delete VRFs, configure interfaces/sub-interfaces, configure 
> VRRP, etc.  All CLI access would be controlled by TACACS to limit the 
> customer to specific commands.
>
> So my question is:  does anyone have examples where this is done today?
>  In a corporate environment between business units?  Looking for 
> examples where this has been successful or unsuccessful.
>
> v/r,
> Trey
> ______________________________**_________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> https://puck.nether.net/**mailman/listinfo/cisco-nsp<https://puck.neth
> er.net/mailman/listinfo/cisco-nsp>
> archive at 
> http://puck.nether.net/**pipermail/cisco-nsp/<http://puck.nether.net/p
> ipermail/cisco-nsp/>
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/