The ng_state development cycle is closed now.
Last month we did 3-5 patches, mostly monitoring-related.
Now we've got some activity numbers, now it's clear that in peak times a server serves 7.5K customers with 50% CPU utilization. This is pretty good numbers, they indicate total server capacity is more then 10K customers.
I am going to switch to a new project now.
One of the most interesting required to do now - is implement 'global switching' project.
Here is the details.
- companies lease town-wide L2 connectivity between locations
- our network is NOT mpls and especially, VPLS ready
- we have PC-based devices for L2 on top of L3 (Ethernet over IP) connectivity
- those devices acts like Ethernet repeaters in hub-and-spoke topology, meaning all traffic is distributed between ALL nodes, regardless of need of a VLAN in the HUB.
- so we need at least some kind of 'VLAN pruning'
- it would be much better to switch from hub-and spoke to partial mesh topology, and prevent L2 looping by a kind of split horizon.
Sure i want it to be as simple as possible, so the following things desired
- dynamical exchange of VLAN list
- path costs accounting in partial mesh
- automatical or semi-automatical neighbors discovery
Yes, that sounds like a kind of a routing protocol, and in fact, it is.
So i'd like to utilize one of current IGPs running in the network core to do the VLAN exchange (or maybe start one more - mp-bgp? ospfv3? ... whatever...).
Last month we did 3-5 patches, mostly monitoring-related.
Now we've got some activity numbers, now it's clear that in peak times a server serves 7.5K customers with 50% CPU utilization. This is pretty good numbers, they indicate total server capacity is more then 10K customers.
I am going to switch to a new project now.
One of the most interesting required to do now - is implement 'global switching' project.
Here is the details.
- companies lease town-wide L2 connectivity between locations
- our network is NOT mpls and especially, VPLS ready
- we have PC-based devices for L2 on top of L3 (Ethernet over IP) connectivity
- those devices acts like Ethernet repeaters in hub-and-spoke topology, meaning all traffic is distributed between ALL nodes, regardless of need of a VLAN in the HUB.
- so we need at least some kind of 'VLAN pruning'
- it would be much better to switch from hub-and spoke to partial mesh topology, and prevent L2 looping by a kind of split horizon.
Sure i want it to be as simple as possible, so the following things desired
- dynamical exchange of VLAN list
- path costs accounting in partial mesh
- automatical or semi-automatical neighbors discovery
Yes, that sounds like a kind of a routing protocol, and in fact, it is.
So i'd like to utilize one of current IGPs running in the network core to do the VLAN exchange (or maybe start one more - mp-bgp? ospfv3? ... whatever...).
No comments:
Post a Comment