Greatly appreciate all the responses. My carrier is a customer to this
carrier and configuration on these PEs support transit of my traffic.
Based on the on-list and off-list responses, finding a new provider
should be on the table.
Trey
On 9/17/13 3:06 PM, Richard Clayton wrote:
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.howl...@gmail.com
<mailto:trey.howl...@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@puck.nether.net
<mailto:cisco-nsp@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
