Avaya 555-245-600 manual Example 2 C-LANS cannot tag their traffic, CommandMeaning

Models: 555-245-600

1 378
Download 378 pages 58.63 Kb
Page 335
Image 335

Examples of QoS implementation

Example 2: C-LANS cannot tag their traffic

Assumptions for Example 2

The C-LANs 192.168.1.10 and.11 cannot tag their traffic (TN-799C or earlier).

The configuration commands in Table 59 are applied only to the left router.

Administration commands for Example 2

Table 59: Administration commands for Example 2

CommandMeaning

1.access-list 101 permit ip host 192.168.1.10

192.168.2.0 0.0.0.255

2.access-list 101 permit ip host 192.168.1.11

192.168.2.0 0.0.0.255

3.class-map match-any untaggedVoIP

4.match access-group 101

5.policy-map setDSCP

6.class untaggedVoIP set ip dscp 46

7.interface Ethernet 0/0 service-policy input setDSCP

The command “access-list 101...” permits any IP traffic from the 2 C-LANs to the 192.168.2.0/24 network. There is an implicit “deny any” at the end of this access list.

Create a class map called “untaggedVoIP.”

Packets that match access list 101 are in the class that is “untaggedVoIP.”

Create a policy map called “setDSCP.”

For all packets in the class “untaggedVoIP,” set the DSCP to 46.

Apply the “setDSCP” policy inbound on this interface.

Issue 6 January 2008 335

Page 335
Image 335
Avaya 555-245-600 manual Example 2 C-LANS cannot tag their traffic, CommandMeaning