Filter
Top Products
Classifier-Based Software Configuration
Creating a Traffic Class
Optional IGMP Match Criteria
To more precisely define the IGMP packets that you want to match in an IPv4
traffic class, use the optional parameter settings described in this section. For
example, instead of matching all IGMP traffic, you can configure a class that
matches only a specific IGMP packet type.
Context: Class configuration
Syntax: [no] [seq-number] < match | ignore > igmp
< source-address > < destination-address > [ igmp-type ]
[ ip-dscp codepoint ] [ precedence precedence-value ]
[ tos tos-value ] [ vlan vlan-id ]
If you enter igmp as the IP protocol type in a match/ignore
statement, you can optionally specify an IGMP packet type
to more precisely define match criteria for a traffic class.
Enter the optional IGMP match criteria immediately after
the destination IP address (DA) value in the command
syntax; for example:
ProCurve(config-class)# match igmp any any host-
query
[ igmp-type ]
Configures an IGMP packet type as match criteria in a class
configuration. Some of the valid values for IGMP packet-type
names are as follows:
dvmrp mtrace-request trace
host-query mtrace-reply v2-host-leave
host-report pim v2-host-report
v3-host-report
To display a list of valid igmp-type entries when you enter igmp
as the IP protocol type in a match/ignore statement, type ?.
9-16