• February 06, 2012, 04:34:36 PM
Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: QoS implementing on Contivity 1700  (Read 1815 times)

0 Members and 1 Guest are viewing this topic.

Offline Iurii

  • Rookie
  • **
  • Posts: 3
QoS implementing on Contivity 1700
« on: September 07, 2009, 04:00:24 AM »
Having looked through the official docs I tried to implement QoS on the contivity. I wanted to mark the traffic destined to my videoserver as a premium class traffic. Here are my suggestions:

qos mf-class rule add RULE1
qos mf-class rule RULE1
     destination-address VIDEOSERVER ip 192.168.1.1 mask 255.255.255.0
     diffserv-marking EF
qos mf-class add PREMIUM
qos mf-class PREMIUM
     add-rule RULE1

on the interface:

qos traffic-conditioning enable
qos mf-class enable
qos mf-class egress-mf-class PREMIUM
qos mf-class egress-mf-class PREMIUM ingress-mf-class PREMIUM

But something's not okay, something's missing...


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 2151
    • Michael McNamara
Re: QoS implementing on Contivity 1700
« Reply #1 on: September 07, 2009, 10:22:19 AM »
That's a great question... unfortunately I've never had to look at the QoS options on the Contivity (Nortel VPN Router).

Your trying to classify traffic within the tunnel correct? Who gets the tunnel bandwidth before others?

Perhaps someone else will have some ideas... let me see what I can find in the testlab.

What version of software are you running on the endpoints? What are you using to test? packet sniffer?

In my workings with QoS it's generally a better approach to classify/tag packets on the network edge and then configure the uplink/downlink ports as trusted.
If you've found this site useful and helpful, please help me spread the word. Link to us in your blog or homepage or Tweet about us! - Thanks!