• February 19, 2018, 03:18:42 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Interface shaping on a subinterface basis in hub and spoke topologies, VSP 9000  (Read 1157 times)

0 Members and 1 Guest are viewing this topic.

Offline OfWolfAndMan

  • Rookie
  • **
  • Posts: 12
Good evening all,

Current situation: We currently use Cisco ASR 1002x as our head-end for a hub and spoke Metro-E topology supporting about 40 remote sites. These sites were originally going to be moved to a subinterface configured ASR for the purpose of more control per site and the ability to do per-site shaping at the egress.

Our new situation is this: VSP 9000 as headend router, using multiple VLAN interfaces on a single gigabit port, something like this:

interface 8/10
name "Metro-E headend"
qos if-shaper shape-rate 500000
auto-negotiate

vlan create 1551 name "Metro-E site 1" type port 1
vlan member 1551 8/10
interface vlan 1551
ip address 10.10.10.1 255.255.255.252
ip ospf area 0.0.0.1
ip ospf enable

vlan create 1552 name "Metro-E site 1" type port 1
vlan member 1552 8/10
interface vlan 1552
ip address 10.10.10.5 255.255.255.252
ip ospf area 0.0.0.1
ip ospf enable

On the remote site, I will be running an ERS 4850 with an Advanced License with OSPF support, using area 1, possibly converting it to a stub. The reasoning behind area 1 is because of the 512 route entry limitation of the 4850 (So I can summarize my backbone to them).

My goal is to shape at a subinterface (Per-vlan P2P interface) level, however the if-shaper option is not there. Does anyone have any insight on how I could do this?


Offline TankII

  • Hero Member
  • *****
  • Posts: 542
OSPF Areas have nothing to do with route table sizes.  And, if you are on 5.9.X, there are 2000 routes in the table.
Areas are meant for you to summarize networks behind.  For example, you might have an area 0.0.0.64, with all networks from 10.0.0.0 to 10.63.255.255 in it.  You summarize at the transition point to area 0.0.0.0, so only one route is injected into the backbone network of 0.0.0.0.

To shape the networks, you can apply a policy on the ports.
We don't have any VSP9000's here, but on the ERS switches, you can create shaper policies like:
Per port:
qos if-queue-shaper port 1/1 queue 1 name "Sec MGMT 1" shape-rate 768 shape-min-rate 512

By class of service:
qos if-group name "Slow_Video_Ports" create class unrestricted
qos if-assign-list add portlist 3 name Slow_Video_Ports
qos if-assign-list add portlist 4 name Slow_Video_Ports
qos ip-filter 1 create src-ip 10.X.X.X 255.255.255.248 dst-ip 10.X.X.X 255.255.255.255  protocol udp
qos ip-filter-set 1 create set 1 name Video filter 1 filter-prec 1
qos policy 1 create name Video if-group "Slow_Video_Ports" filter-set-type ip filter-set 1 meter 0 in-profile-action 65527 out-profile-action 65528 order 1

Maybe these help?

TankII


Offline OfWolfAndMan

  • Rookie
  • **
  • Posts: 12
I didn't include all details for the OSPF aspect it seems.

I would be applying a route-map or distribute list into the OSPF process to reduce the table of the spokes.

I know how to shape on the spokes. That's not what I'm asking. On  the hub side, I will be using per-VLAN P2P interfaces to connect the spokes to the hub.

So, based on my first example

vlan create 1551 name "Metro-E site 1" type port 1
vlan member 1551 8/10
interface vlan 1551
ip address 10.10.10.1 255.255.255.252
ip ospf area 0.0.0.1
ip ospf enable

THIS IS THE HUB

vlan create 155 name "Metro-E site 1" type port 1
vlan member 1551 50
interface vlan 1551
ip address 10.10.10.2 255.255.255.252
ip ospf area 0.0.0.1
ip ospf enable

THIS IS THE SPOKE

This way, I can control their routing interfaces on a per spoke basis.

What I was asking is to apply a shaper on the HEADEND on the VLAN interface, as having a 500M headend but a 10 or 100M spoke with shaping on the spoke but a 500M shaper on the hub physical port is not optimal. I wanted to shape on a per VLAN interface P2P basis so the shaping is optimal bi-directionally.