Quanta Cloud Technology QuantaMesh QNOS5, Configuration Manual

Page: 155 / 256

155
(QCT) (Config-classmap)#match srcip 172.16.40.0 255.255.255.0
(QCT) (Config-classmap)#exit
3. Create a DiffServ policy for inbound traffic named internet_access, adding the previously created
department classes as instances within this policy. This policy uses the assign-queue attribute to put each
department's traffic on a different egress queue. This is how the DiffServ inbound policy connects to the CoS
queue settings established below.
(QCT) (Config)#policy-map internet_access in
(QCT) (Config-policy-map)#class finance_dept
(QCT) (Config-policy-classmap)#assign-queue 1
(QCT) (Config-policy-classmap)#exit
(QCT) (Config-policy-map)#class marketing_dept
(QCT) (Config-policy-classmap)#assign-queue 2
(QCT) (Config-policy-classmap)#exit
(QCT) (Config-policy-map)#class test_dept
(QCT) (Config-policy-classmap)#assign-queue 3
(QCT) (Config-policy-classmap)#exit
(QCT) (Config-policy-map)#class development_dept
(QCT) (Config-policy-classmap)#assign-queue 4
(QCT) (Config-policy-classmap)#exit
(QCT) (Config-policy-map)#exit
4. Attach the defined policy to interfaces 0/1 through 0/4 in the inbound direction
(QCT) (Config)#interface range 0/1-0/4
(QCT) (Interface 0/1-0/4)#service-policy in internet_access
(QCT) (Interface 0/1-0/4)#exit
5. Set the CoS queue configuration for the (presumed) egress interface 0/1 such that each of queues 1, 2, 3
and 4 get a minimum guaranteed bandwidth of 25%. All queues for this interface use weighted round robin
scheduling by default. The DiffServ inbound policy designates that these queues are to be used for the
departmental traffic through the assign-queue attribute. It is presumed that the switch will forward this
traffic to interface 0/1 based on a normal destination address lookup for internet traffic.
(QCT) (Config)#interface 0/5
(QCT) (Interface 0/5)#queue cos-queue min-bandwidth 0 25 25 25 25 0 0 0
(QCT) (Interface 0/5)#exit
(QCT) (Config)#exit