RE: Internet usage for customers spanning data centers

I was debating MPLS myself....  It seems like the obvious choice.  In this 
case, I think I'm still faced with multiple internet-facing interfaces for 
the customer though.  Each of our data centers has different paths to the 
internet.  The customer's stuff will be located in separate data centers. 
I think I've still got to deal with some kind of aggregate number for 
billing their traffic to the internet...  Ack.

--Rick

On Thu, 9 Jun 2011, James Jun wrote:

> We run into this issue rather frequently.
>
> What we ended up doing in every data center deployment is to run MPLS on
> backbone and operate a separate off-band transport network ("lan bridge")
> for customer interconnects.  So customers receive one layer3 port for
> internet, the other port comes off of LAN bridge switch that connects to his
> cage in 2nd data center.
>
> James
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Rick Kunkel
> Sent: Thursday, June 09, 2011 3:00 PM
> To: [email protected]
> Subject: Internet usage for customers spanning data centers
>
> Hello folks,
>
> It's been a long while since I've asked anything on here...
>
> I've been dodging this issue for quite some time, but it's time to address
> it.  I have a couple of data centers.  Customer X has always had equipment
> in only one of these data centers, and getting usage data for him has
> always been pretty easy using SNMP.  Now though, he wants to have
> equipment in both data centers,and he plans to send a lot of replication
> data back and forth between the two data centers.  We only bill for
> bandwidth to the outside world.
>
> How do others handle billing/usage in this situation?  I want to make sure
> that I'm charging him only for traffic that leaves our network.  My old
> method, gathering SNMP data on his switchport, will now include traffic
> destined for his machines in the other data center, and will therefore not
> work.
>
> Thanks!
>
> Rick
> -- 
> Eat sushi frequently. - Avi
> [email protected] is the human contact address.
> [email protected] is the list posting address.
> See below URL for subscribe/unsubscribe and list options:
> http://inet-access.net/mailman/listinfo/list
>
> -- 
> Eat sushi frequently. - Avi
> [email protected] is the human contact address.
> [email protected] is the list posting address.
> See below URL for subscribe/unsubscribe and list options:
> http://inet-access.net/mailman/listinfo/list
>
-- 
Eat sushi frequently. - Avi
[email protected] is the human contact address.
[email protected] is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list