[c-nsp] handling customer interfaces for single IP address

root net rootnet08 at gmail.com
Wed Nov 16 19:57:28 EST 2011


I wanted to find out how some of you are handling customer interfaces,
specifically when giving a customer one IP address. How do you make sure
the customer is only getting bandwidth he/she is paying for?

Currently, we assign customers /29 subnet to their 802.1Q sub interface and
apply some policies to the sub interface. For customers wanting a single IP
or broadband package that included only a single IP we have a 802.1Q sub
interface with a /24 and we just assign the static IPs to the customer as
they need. With this model you have to throw more bandwidth at the link in
order to satisfy all customers wanting for example 20 down / 5 up

Using ATM DSL this was a walk in the park but just trying to make sure we
hit the nail on the head since it's all Ethernet and L2 ports for customers.

I believe if we simply did a /30 for each customer on a 802.1Q interface
that would solve our issue but we would waste IP addresses. Also if we did
this we could route a /29 or any subnet size to their interface at that
point should they need. What are your experiences and do you have any other
suggestions?

We do all routing on our side and hand off a L2 port.

Thanks in advance,

rootnet


More information about the cisco-nsp mailing list