[f-nsp] Question about MLX/XMR capabilities

[Colin Horsington]

Hi Allan,
Foundry have implemented a their IP sub-interface using global VLAN
resources.  This means if you want an IP sub-interface (labelled
VE) attached to interface 4/5 and associated to VLAN 100, then you are using
a global VLAN resource.  Other ports associated with a global VLAN will also
share the same sub-interface.

An example:

vlan 100 name test
  tag ethernet 4/5
  router-interface ve 100
interface ve 100
  ip address 1.1.1.1/30

If you then associated interface 4/6 with the same VLAN you would have the
following configuration:

vlan 100 name test
  tag ethernet 4/5 ethernet 4/6
  router-interface ve 100
interface ve 100
  ip address 1.1.1.1/30


If you then wish to rate-limit all traffic associated with this
sub-interface, in this case VLAN 100 traffic you can perform the following
on interface 4/5.

The below example rate-limits VLAN 100 to 100Kbps with a 10Kbps burst.

interface ethernet 4/5
  rate-limit input vlan-id 100 100000 10000
  rate-limit output vlan-id 100 100000 10000

You can apply many rate-limits of the same kind (VLAN or ACL) to an
interface.  They can also be combined with a policy-map to include EIR
remarking if desired.

On a different note, VLANs can be port specific but as already discussed in
this thread, only for VLL and VPLS services.  These services cannot
currently be combined with IP services without the use of a loop back.

The below example will translate VLAN 100 to VLAN 101 from interface 4/5 to
5/6.  The two VLANs (100 and 101) are port specific and do not clash with
global VLANs.

router mpls
  vll-local test
    vlan 100
      tagged ethernet 4/5
   vlan 101
      tagged ethernet 5/6

You would be best to speak to an SE as to your specific requirements.

Cheers.

Colin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20090128/82ca473f/attachment.html>