Traffic Classification Rules
Traffic Classification rules allow you to assign VLAN membership and / or class of service to your network traffic based on the traffic's classification type. Classification types are derived from Layers 2, 3, and 4 of the OSI model, and all network traffic can be classified according to specific layer 2/3/4 information contained in each frame in Policy Manager, rules are used to provide four key policy features:.. traffic containment, traffic filtering, traffic security, and traffic prioritization Examples of how to design rules for each Of these features is given beelow.
A Traffic Classification rule has two main parts: Traffic Description and Actions The Traffic Description identifies the traffic classification type for the rule The Actions specify whether traffic matching that classification type will be assigned VLAN membership, class of service, or both When a... frame arrives on a port, the switch checks to see if the frame's classification type matches the type specified in a rule. If it does, then the actions defined in that rule will apply to the frame. Use the Policy Manager's rule Wizard to quickly and Easily Create a Rule and define ITS Traffic Description and Actions.
In Policy Manager, rules are created and then grouped together into Services, which are then used to define roles. A role is assigned to each port either through end user authentication or as the port's default role. This means that there can be multiple rules active ON A Port. When a frame is receivated on a port, IF The frame's classification type matches more Than One Rule, Classification Precedency Rules Are Used to Determine Which rule.
THE FOLLOWING INFORMATION IS Discussed in this file: Traffic Descriptions Actions
VLAN MEMBERSHIP Priority (Class of Service) Classification Types and Their Parameters
Layer 2 Data Link Classification Types Layer 3 Network Classification Types Layer 4 Application Transport Classification Types Examples Of How Rules Are Used
Traffic Containment Traffic Filtering Traffic SECURITY TRAFFIC PRIORTIZATION CLASSIFICATION Precedency Rules
Precedence Scenarios
Traffic DescriptionsWhen you create a Traffic Classification rule in Policy Manager, you must define the rule's traffic description. The traffic description identifies the traffic classification type for that rule. You must select a classification type, and then select or enter certain parameters or values for each TYPE.
Classification Types Are Grouped According to Layers 2, 3, And 4 of the OSI Model and There Multiple Classification Types for Each Layer.
OSI Model Layer 7 - ApplicationLayer 6 - PresentationLayer 5 - SessionLayer 4 - Transportlayer 3 - Networklayer 2 - Data Linklayer 1 - Physical
Specific Layer 2/3/4 Information Contained in The Header of Each Frame Is Used to Identify The Frame'S Classification Type. Each Layer Uses Different Information To Classify Frames.
Layer 2 Data Link - classifies frames based on an exact match of the MAC address or specific protocol type of each frame Layer 3 Network -.. Classifies IP or IPX frames based on specific information contained within the Layer 3 header Layer 4 Transport - - Classifies IP Frames Based ON Specific Layer 4 TCP OR UDP Port Numbers Conta $ The Header. for a Complete Description of Layer 2, 3, And 4 Classification, Refer to
Classification Types and Their Parameters.
ActionsWhen you create a Traffic Classification rule in Policy Manager, you must define the actions that the rule will perform. When a frame arrives on a port, the switch checks to see if the frame's classification type matches the type specified in a rule. If it does, then the actions defined in that rule will apply to the frame. Actions specify whether the frame will be assigned VLAN membership, class of service, or both.VLAN MembershipIn your network domains, you can create VLANs (Virtual Local Area Networks) that allow end systems connected to separate ports to send and receive traffic as though they were all connected to the same network segment. Using traffic classification rules, you can classify a frame based on the frame's classification type to have membership in a specific VLAN, providing important Traffic Containment, Filtering, And Security for your network.
For example, a network administrator could use rules to separate end-user traffic into VLANs according to protocol, subnet, or application. Rules could also be used to group geographically separate end systems into job specific workgroups.
Priority (Class of Service) Traffic Classification rules allow you to assign a transmission priority to frames received on a port based on the frame's classification type. For example, a network administrator could use rules to assign priority to one network application over another.
Priority is a value between 0 and 7 assigned to each frame as it is received on a port, with 7 being the highest priority. Frames assigned a higher priority will be transmitted before frames with a lower priority. Each of the priorities is mapped into a specific traffic queue by the switch or router. The insertion of the priority value (0-7) allows all 802.1Q devices in the network to make intelligent forwarding decisions based on its own level of support for prioritization.The Matrix product line supports four ( 0-3) or eight (0-7) traffic queues per port. The number of traffic queues varies by port type. These queues can be serviced based on a strict method, meaning that all frames in Queue 3 will be transmitted before the frames in Queue 0, or based on a fair weighted method. The weighted method allows the network administrator to give a certain percentage or weight to each queue, preventing a lower priority queue from being starved.
Policy Manager enables you to utilize priority by creating classes of service that include an 802.1p priority (rate-limited or not) and / or IP type of service values. You can then assign the class of service as a classification rule action, as part OR AS A ROLE DEFAULT. See How To Define A Bandwidth Rate Limiter And How To Create a Class of Service for More Information.
Classification Types and their ParametersWhen you define a rule's traffic description, you select a classification type, and then select or enter certain parameters or values for each type. Classification types are grouped according to Layers 2, 3, and 4 of the OSI model and there Are Multiple Classification Types for Each Layer.
Layer 2 - Data Link Classification Types
Layer 2 Classification Types Allow You to Define Classification Rules Based ON An Exact Match of The Mac Address or Specific Protocol Type of Each Frame.ethertype
This classification type is based on the specific protocol type of each frame defined in the two-byte Ethertype field. Each protocol has a corresponding classification type address that is automatically entered into the
Value Field. If you select
Other, You Must Manually Enter. You can Enter A Range of Values, However, Range Rules Are ONLY Supported ON Matrix N-Series Platinum Devices. Common Ethertypes and Their Values:
IP0x0800ARP0x0806Reverse ARP0x8035Novell IPX 10x8137Novell IPX 20x8138Banyan0x0badAppleTalk0x809bAppleTalk ARP0x80f3DECnet Phase 40x6003DEC MOP Dump / Load0x6001DEC MOP Remote Console 0x6002DEC LAT0x6004DEC Diagnostic Protocol 0x6005DEC Customer Protocol0x6006DEC LAVC, SCA0x6007DEC Unassigned0x6008-0x6009Other0x0600-0xFFFF
DSAP / SSAP
This classification type is based on the specific protocol type of each frame defined in the DSAP and SSAP fields. Each protocol has a corresponding classification type address that is automatically entered into the
Value Field. If you select
Other, you must manually enter the value in hexadecimal form. You can also enter advanced configurations, however, these are only supported on Matrix N-Series Platinum devices. The DSAP and SSAP values are one byte each, and these values must match. They Are Combined to create ONE TWO-BYTE VALUE (EG, A DSAP VALUE OF E0 and An Ssap Value of E0 Are Combined to create a two-byte value of e0E0). Common dsap / ssap types and their valuees:
IP0X0606IPX0XE0E0NETBIOS0XF0F0BANYAN VINES 0XBCBCSNA0X0404OTHERA Two-byte Value
MAC Address Source, MAC Address Destination, MAC Address BilateralThese classification types are based on an exact match of the source, destination, or bilateral (either source or destination) MAC address contained in an Ethernet frame. You can select a mask, however, masking a Mac Address is Only Supported on Matrix N-Series Platinum Devices.
Layer 3 - Network Classification TypesLayer 3 Network Classification Types Allow You to Define Classification Rules Based On Specific Information Conta $ The Layer 3 Header of An IP OR IPX Frame.
IP Type Of Service
This classification type is based on an exact match of the one-byte TOS / DSCP field contained in the IP header of a frame. The TOS (Type of Service) or DSCP (Diffserve Codepoint) value is defined by an 8-bit hexadecimal number BetWeen 0 and ff.
Type of Service can be used by applications to indicate priority and Quality of Service for each frame. The level of service is determined by a set of service parameters which provide a three way trade-off between low-delay, high-reliability, and high -throughput. The use of service parameters may increase the cost of service. In many networks, better performance for one of these parameters is coupled with worse performance on another. Except for very unusual cases, at most, two of the parameters should be set .
For A TOS Value, The 8-Bit Hexadecimal Number Breaks Down As Follows:
BITS 0-2: PRECEDENCEBIT 3: 0 = Normal delay, 1 = low delaybit 4: 0 = Normal Throughput, 1 = high throughputbit 5: 0 = Normal Reliability, 1 = High ReliabilityBits 6-7: Explicit Congestion Notification
The Precedence Bits (Bits 0-2) Break Down As Follows:
111 - Network Control110 - Internetwork Control101 - CRITIC / ECP100 - Flash Override011 - Flash010 - Immediate001 - Priority000 - RoutineThe Network Control precedence designation is intended to be used within a network only The actual use and control of that designation is up to each network.. .
For a DSCP value, the value represents codepoints for two Differentiated Services (DS) Per-Hop-Behavior (PHB) groups called Expedited Forwarding (EF) and Assured Forwarding (AF). For more information on these PHB groups, refer to RFC 2597 And RFC 2598.
For Information On How to Automatic Or Generate A TOS OR DSCP Value, See TOS / DSCP Configuration Window.
IP Protocol Type
This classification type is based on the specific protocol type defined in a field contained in the IP header of each frame. Each protocol has a corresponding classification type address that is automatically entered into the
Value Field. If you select
Other, You Must Manually Enter The Value in Decimal Form. You can Enter A Range of Values, However, Range Rules Are Only Supported ON Matrix N-Series Platinum Devices.
TIP: You can define a new IP Protocol Type using the Pre-Defined Well-Known IDs window Once defined, it is available for selection from the list of well-known values when defining the rule's traffic classification type.Common IP Protocol types and. Their Values:
ICMP 1IGMP2IPV641L2TP115OSPF89PIM103RSVP46TCP6UDP17VRRP112HER0-255
IP Address Source, IP Address Destination, IP Address Bilateral
These classification types are based on an exact match of the source, destination, or bilateral (either source or destination) IP address information contained within the IP header of each frame. This classification type must also contain a Mask entry along with the specific IP address . This Mask allows a switch to determine whether a classification is based on a specific IP address, IP subnet, or range within an IP subnet. For example, a user could define a rule where all frames from the 129.168.28.x network are Classified Into The Red Vlan by Setting The IP Address of 129.168.28.0 with the mask of 255.255.255.0.ip fragment
This classification type is based on Layer 4 information in fragmented frames. IP supports frame fragmentation, where large frames are divided into smaller fragments and sent wrapped in the original Layer 3 (IP) header. When a frame is fragmented, information that is Layer 4 and above is only present in the first fragment. for example, the first fragment may be classified to Layer 4, while subsequent fragments will be classified only to Layer 3. The Matrix product line does not support Layer 4 classification for IP frames that have been fragmented, as the Layer 4 information is not present in these frames. Using the IP Fragment classification rule, any frame which is a fragment of a larger frame, is classified according to the information in the original frame. If the first fragment is classified to Layer 4, Subsequent Fragments Will Also Be Classified To Layer 4.
IPX Class of Service
This classification type is based on specific information contained within the Layer 3 header of an IPX frame. This is a one-byte field used for transmission control (hop count) by IPX routers. Enter a valid IPX Class of Service in decimal form, 0 -255. You can Enter A Range of Values, HoWever, Range Rules Are Only Supported on Matrix N-Series Platinum Devices.ipx Packet Type
THIS Classification Type Is Based On Specific Information Contained WITED INTO FRAME. Each IPX Packet Type Has A Corresponding Classification Type That Is Automatically Entered Into The
Value Field. If you select
Other, You Must Manually Enter The Value in Decimal Form. You can Enter A Range of Values, HoWever, Range Rules Are Only Supported on Matrix N-Series Platinum Devices. Common IPX Packet Types and their Values:
Hello / Sap0rip1echo Packet2error Packet3NetWare 386 4seqPackProt5NetWare 28617other0-31
IPX Network Source, IPX NetWork Destination, IPX Network Bilateral
These classification types are based on specific information contained within the Layer 3 header of an IPX frame. It is a four-byte user-defined value that represents the IPX source, destination, or bilateral (either source or destination) network number. This value Must Be a Valid IPX Network Address in Hexadecimal Form. You Can Enter A Range of Values, However, Range Rules Are ONLY Supported on Matrix N-Series Platinum Devices.
IPX Socket Source, IPX Socket Destination, IPX Socket Bilateral
These classification types are based on specific information contained within the Layer 3 header of an IPX frame. It is a two-byte, user-defined value that represents the IPX source, destination, or bilateral (either source or destination) socket numbers. This value is used by higher layer protocols to target specific applications running among hosts. Each IPX Socket type has a corresponding classification type address that is automatically entered into theValue field. If you select
Other, You Must Manually Enter The Value in Decimal Form. You Can En ENTER A RANGE OF VALUES, HOWEVER, RANGE RULES Are Only Supported on Matrix N-Series Platinum Devices. Common IPX Socket Types and Their Values:
NCP1105SAP1106RIP1107NETBIOS1109Diagnostics 1110nslp36865ipx wan56868 other0-65535
ICMP
This classification type is based on an exact match of the ICMP (Internet Control Message Protocol) message contained in the ICMP tag within a frame. Each ICMP message has a corresponding value that is automatically entered in the
Value Field. If you select
Other, You Must Manually Enter The Value in Decimal Form. You Can Enter A Range of Values, However, Range Rules Are ONLY Supported on Matrix N-Series Platinum Devices. Common ICMP Messages and Their Values:
Echo Reply0Destination Unreachable3Source Quench4Redirect5Echo 8Router Advertisement9Router Solicitation10Time Exceeded11Parameter Problem12Timestamp13Timestamp Reply14Information Request15Information Reply16Address Mask Request17Address Mask Reply18
VLAN ID
This classification type is based on an exact match of the vlame. SELECT A VLAN ID (VID) from the list of vlans defined in Policy Manager. If you select
Other, You Must Enter A Single Vid or Specify A Range of Vids in Decimal Form. You Can Enter A Range of Values, HoWever, Range Rules Are ONLY Supported on Matrix N-Series Platinum Devices.priority
THIS Classification Type is based on an exact match of the prior tag contained within a frame. SELECT A Priority Value 0 - 7 from the list of well-knower value, or select
Other and Enter a value in Decimal Form. You can En En Enter A Range of Values, HOWEVER, RANGE RULES ARE ONLY Supported On Matrix N-Series Platinum Devices.
Layer 4 - Application Transport Classification TypesLayer 4 IP classification types allow you to define classification rules based on specific Layer 4 TCP or UDP port numbers contained in the header of an IP frame You can specify a specific port number or a range of port numbers. .
Note: The Matrix product line does not support Layer 4 classification for IP frames that have been fragmented, as the Layer 4 information is not present in these frames If a Matrix device has an FDDI HSIM installed, Layer 4 classification will not be supported for. any frames larger than 1500 bytes. Frames larger than 1500 bytes are fragmented internally in the switch. When creating classification rules based on specific Layer 4 information, using the IP Fragment classification rule will allow fragmented frames to be classified according to the Layer 4 information contained In The Original Frame.
IP UDP Port Source, IP UDP Port Destination, IP UDP Port Bilateral
THESE CLASSIFIC LAYER 4 UDP Port Numbers Contained with the Header of An IP Frame. Each UDP Type Has a Corresponding Classification Type Address That Is Automatically Entered Into
Value Field. If you select
. Other, you must manually enter the value in decimal form You can enter a range of values, however, range rules are only supported on Matrix N-Series Platinum devices UDP port numbers are defined in RFC 1700.TIP:. You can define a new value for a UDP port number using the Pre-defined Well-Known IDs window Once defined, it is available for selection from the list of well-known values when defining the rule's traffic classification type.Common UDP types and their values.:
FTP Data20FTP21SSH22Telnet23SMTP25TACACS49DNS53Bootps67Bootpc68TFTP69Finger79HTTP80POP3110Portmapper111NNTP119NTP123NetBIOS Name Service137NetBIOS Datagram138NetBIOS Session Service 139IMAP2143SNMP161IMAP3220LDAP389HTTPS443R-Exec512R-Login513R-Shell514LPR515SOCKS1080CITRIX ICA1494RADIUS1812RADIUS Accounting1813NFS2049Other0-65535
IP TCP Port Source, IP TCP Port Destination, IP TCP Port Bilateral
TCP Port Numbers Contained with the header of an ip frame. Each TCP TYPE HAS A CORRESPONDING CLASSIFICATION TYY Address That IS Automatically Entered Into That
Value Field. If you select
Other, You Must Manually Enter The Value in Decimal Form. You can Enter A Range of Values, HOWEVER, RANGE RULES Are ONLY Supported ON Matrix N-Series Platinum Devices. TCP Port Numbers Are Defined In RFC 1700.
TIP: You can define a new value for a TCP port number using the Pre-Defined Well-Known IDs window Once defined, it is available for selection from the list of well-known values when defining the rule's traffic classification type.Common TCP. Types and their value:
FTP Data20FTP21SSH22Telnet23SMTP25TACACS49DNS53Bootps67Bootpc68TFTP69Finger79HTTP80POP3110Portmapper111NNTP119NTP123NetBIOS Name Service137NetBIOS Datagram138NetBIOS Session Service 139IMAP2143SNMP161IMAP3220LDAP389HTTPS443R-Exec512R-Login513R-Shell514LPR515SOCKS1080CITRIX ICA1494RADIUS1812RADIUS Accounting1813NFS2049Other0-65535IP UDP Port Source Range, IP UDP Port Destination Range, IP UDP Port Bilateral Range
These classification types are based on Layer 4 UDP port numbers contained within the header of an IP frame. When you select this type, you enter a range of UDP port numbers that the port number in the header will be matched against. Enter the lower and UPP Port Numbers Are Defined In RFC 1700.
IP TCP Port Source Range, IP TCP Port Destination Range, IP TCP Port Bilateral Range
These classification types are based on Layer 4 TCP port numbers contained within the header of an IP frame. When you select this type, you enter a range of TCP port numbers that the port number in the header will be matched against. Enter the lower and Upper Range Values in Decimal Form. TCP Port Numbers Are Defined in RFC 1700.
Examples of How Rules Are USEDTRAFFIC CLASSIFICATION RULES ARE Used to Provide Four Key Policy Features: Traffic Containment, Traffic Filtering, Traffic Security, and Traffic Priority.
Traffic ContainmentUsing Classification Rules, Network Administrators Can Group Together Users of A Given Protocol, Subnet, or Application, And Control Where Their Traffic CAN Logically Go on The Network.
IP Traffic Containment
The figure above shows a configuration where the network administrator wants to separate end-user traffic into VLANs based on the assigned IP subnet of each department. This can easily be accomplished by creating two Layer 3 classification rules based on the IP subnet range of the respective DEPARTMENTS.RULE 1 - ENGINEERING, WHICH Uses the 132.181.28.x Subnet, Will Be Assigned to The Red VLAN.
Rule 2 - Sales, Which Uses The 132.181.29.x subnet, Will Be Assigned to the blue vlan.
Based on these two Layer 3 classification rules, the traffic from the Engineering VLAN will be isolated from the Sales VLAN. Since these rules are based on Layer 3 information, an Engineering user could enter the network from a connection in the Sales department, and that User Would Still Be Contained in The Engineering VLAN.
Traffic FilteringClassification rules can also be used to filter specific unwanted traffic. Filter criteria can include things such as broadcast routing protocols, specific IP addresses, or even applications such as HTTP or SMTP.
In Filtering Operations, The Traffic To Be Filtered is Assigned To The Discard Vlan. Since The Discard VLAS Not Configured To Exit The Switch, The Traffic Will Be Discarded.
OSPF / RIP Traffic Filtering
The figure above shows a common configuration in which a routed backbone is using both RIP and OSPF for its routing protocols. The network administrator does not want the multicast OSPF and broadcast RIP frames propagated to the end stations. The network is designed so that only end Users area attached to the mass defices.
TO IMPLEMENT FILTERING IN THIS SCENARIO, A Layer 3 Rule and a Layer 4 Rule Will Be CREATED.
Rule 1 (Layer 3) - Any Frame Received With an IP Protocol Type of 89 (OSPF) Will Be Classified Into The Discard Vlan.rule 2 (Layer 4) - Any Frame Received With A Bilateral UDP Port Number of 520 (RIP) WILL BE Classified Into The Discard VLAN.
.
Traffic SecurityTraffic Security Uses The Same Concepts As
Traffic Filtering. Imagine a scenario where network access is provided to a group of unknown users. There have been problems with these unknown users "hacking" into the router and altering the configuration. A simple classification rule can be put in place that will prevent these Types of occurrences.
ROUTER Traffic Security
In The Figure, The NetWork Components Include A Router and a Matrix E7. In this configuration end-users connect to the ports of the massix e7.
Since the end-user we 's IP address rule will be used., A layer 3 ip classification rule will be used.
Rule - Any Frames Received by The Switch with a Destination IP Address of the Router (129.168.1.2) Will Be Classified to The Discard Vlan. The Discard Vlan IS Configured So That Does Not Exit The Switch.
.
Traffic PrioritizationClassification rules can be used to specify that certain network applications receive the highest transmission priority. For example, a network administrator wants to assign priority to three network applications, SAP R / 3, web traffic, and email, in that order.
PrioritizationTo accomplish the prioritization goals in this example, there are two main steps required: creating the classification rules, and configuring the Priority-to-Traffic Queue mapping for the switch.
First, Create One Layer 3 and Two Layer 4 Classification Rules.
Rule 1, Layer 3 (SAP R / 3) - All frames to or from the IP Address of the SAP R / 3 Server Will Be Tagged with a priority INDATOR OF 7 (HIGHEST).
Rule 2, Layer 4 (Web) - All Frames With A UDP Port Number of 80 (HTTP) Will Be Tagged With A Priority Indicator Of 5.
Rule 3, Layer 4 (email) - All Frames with a UDP Port Number of 25 (SMTP) Will Be tagged with a priority Indicator Of 3.
Note: An IP address classification was selected for Rule 1 because it has been observed that SAP R / 3 dynamically negotiates the TCP / UDP port used, so the port number selections vary from session to session If this was not the case, a Layer. 4 UDP Classification Could Be.
Then, configure the priority-to-traffic queue mappings. Based on the default priority-to-traffic queue mapping (shown in the following table), the priorities assigned above will work out so that each frame classification type will be mapped to the desired traffic queue. This means that no user configuration of the priority-traffic queue mapping would be required. However, this mapping can be configured by the network administrator using local management or NetSight Atlas Console.
This Table Shows The Default Matrix E7 priority-to-queue mappings.
Priority Value Traffic Queue 7 3 6 3 5 2 4 2 3 1 2 0 1 0 0 1
Priority 7 = Highest Traffic Queue 3 IS Serviced First
With the classification rules described in Traffic Prioritization, the network traffic would be prioritized as shown in the table below.Application Classification Type Desired Priority Priority Value SS6000 Traffic Queue SAP R / 3 Bilateral IP High 7 3 Web UDP Port Number Medium 5 2 Email UDP Port Number Low 3 1
Classification Precedence RulesWhen there is a role with multiple classification rules assigned to a port, the device must determine which rule takes precedence. The order of precedence is predefined in the device, and is not configurable. Network administrators should have a comprehensive understanding of classification precedence , AS IT CAN Significantly Impact The Operation of Traffic Classification Rules. The
Device Support Tab (Role) Provides Rule Precenement Information for Each Role.
. ......................
Classification Precedence Layer 2 Source MAC Address 1 Destination MAC Address 2 Ethertype Field / DSAP / SSAP Fields 13Layer 3 IP TOS / IPX COS 11 IP Protocol Type / IPX Packet Type 12 Source IP Address Exact Match / Source IPX Network Number 3 Source IP Address Best Match / Destination IPX Network Number 4 Destination IP Address Exact Match 5 Destination IP Address Best Match 6 IP Fragment 7 Layer 3/4 IPX Socket Source / UDP Source Port / TCP Source Port 8 IPX Socket Destination / UDP Destination Port / TCP Destination Port 9 ICMP 10 VLAN ID14 Priority 15
EXACT MATCH INDICATES A MATCH OF An Explicitly Defined Address. Best Match Indicates A Match of An Entire Subnet, or Range Withnin A Subnet.
Note: The precedence of a rule based on a bilateral address match is determined frame by frame depending on whether the rule matches the destination or source address in the frame A bilateral address rule which matches the source address has higher precedence than a rule which matches. A Destination Address (or Any Other Lower Precedency Rule) .precedence Scenariosthe Following Scenarios Illustrate The Classification Precedency Rules.
Scenario 1A Network Administrator Has Defined Two Classification Rules:
Rule 1 - All Frames with a UDP Port Number of 55 (ISI Graphic Language) Are Assigned to The Red VLAN.
Rule 2- All Frames Sourced from The 132.181.28.x Subnet Areigned to the Blue VLAN.
If a frame is received with a source address of 132.181.28.99 and a UDP port number of 55, the frame will be assigned to the Blue VLAN because as shown in the Precedence Table, a Layer 3 IP Address rule takes precedence over a Layer 4 Rule.
Scenario 2a NetWork Administrator Defines Two Classification Rules:
Rule 1- All Frames with an IP TOS Value of Aa Are Assigned A Priority Of 7.
Rule 2- All Frames With A TCP Port Number of 80 (HTTP) Are Assigned A Priority of 3.
If a frame is received with a TOS value of AA and a TCP port number of 80, the frame will be assigned a priority of 3, because as shown in the Precedence Table, TCP port number classifications take precedence over IP TOS classifications.
Related InformationFor Information ON Related Tasks:
How to create or modify a rule how to define Traffic Descriptions for Information on Related Windows:
Actions Tab Traffic Description Tab
