7210 SAS E OS Routing Protocols Guide. Software Version: 7210 SAS OS 2.0 Rev. 02 July 2010 Document Part Number: * *

Transcription

1 7210 SAS E OS Routing Protocols Guide Software Version: 7210 SAS OS 2.0 Rev. 02 July 2010 Document Part Number: * *

2 This document is protected by copyright. Except as specifically permitted herein, no portion of the provided information can be reproduced in any form, or by any means, without prior written permission from Alcatel-Lucent. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright Copyright 2010 Alcatel-Lucent All rights reserved.

3 TABLE OF CONTENTS Preface Route Policies Configuring Route Policies Policy Statements Default Action Behavior Denied IP Prefixes Configuration Notes General Configuring Route Policies with CLI Route Policy Configuration Overview When to Create Routing Policies Policy Evaluation Basic Configurations Configuring Route Policy Components Beginning the Policy Statement Creating a Route Policy Configuring a Default Action Configuring an Entry Route Policy Configuration Management Tasks Editing Policy Statements and Parameters Deleting an Entry Deleting a Policy Statement Route Policy Command Reference Route Policy Command Reference Generic Commands Route Policy Options Route Policy Prefix Commands Route Policy Entry Match Commands Route Policy Action Commands Show Commands Standards and Protocol Support Index SAS E OS Routing Protocols Guide Page 3

4 Table of Contents Page SAS E OS Routing Protocols Guide

5 LIST OF FIGURES Route Policies Figure 1: Route Policy Process Example SAS E OS Routing Protocols Guide Page 5

6 List of Figures Page SAS E OS Routing Protocols Guide

7 Preface About This Guide This guide describes route policies provided by the 7210-SAS E OS and presents configuration and implementation examples. This document is organized into functional chapters and provides concepts and descriptions of the implementation flow, as well as Command Line Interface (CLI) syntax and command usage. Audience This manual is intended for network administrators who are responsible for configuring the 7210 SAS E-Series routers. It is assumed that the network administrators have an understanding of networking principles and configurations. Protocols, standards, and services described in this manual include the following: Route policies 7210 SAS E OS Routing Protocols GuidePage 11

8 Preface List of Technical Publications The 7210-SAS E OS documentation set is composed of the following books: 7210-SAS E OS Basic System Configuration Guide This guide describes basic system configurations and operations SAS E OS System Management Guide This guide describes system security and access configurations as well as event logging and accounting logs SAS E OS Interface Configuration Guide This guide describes card, Media Dependent Adapter (MDA), and port provisioning SAS E OS Router Configuration Guide This guide describes logical IP routing interfaces and associated attributes such as an IP address, port, link aggregation group (LAG) as well as IP and MAC-based filtering SAS E OS Routing Protocols Guide This guide provides an overview configuration examples for route policies SAS E OS Services Guide This guide describes how to configure service parameters such as customer information and user services SAS E OS OAM and Diagnostic Guide This guide describes how to configure features such as service mirroring and Operations, Administration and Management (OAM) tools SAS E OS Quality of Service Guide This guide describes how to configure Quality of Service (QoS) policy management. Page SAS E OS Routing Protocols Guide

9 Preface Technical Support If you purchased a service agreement for your 7210 SAS router and related products from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcome center at: Web: SAS E OS Routing Protocols Guide Page 13

10 Preface Page SAS E OS Routing Protocols Guide

11 Route Policies In This Chapter This chapter provides information about configuring route policies. Topics in this chapter include: Configuring Route Policies on page 278 Policy Statements on page 279 Default Action Behavior on page 280 Configuration Notes on page SAS E OS Routing Protocols Guide Page 277

12 Configuring Route Policies Configuring Route Policies Alcatel-Lucent's 7210 SAS E supports route policies to allow users to enable IGMP group membership report filtering. IGMP group membership report filtering allows the user to configure rules which can be used to restrict the IGMP groups that subscribers/hosts can enrol to. This is achieved by using route policies that specify the set of hosts whose group membership reports are to be accepted (and further processed appropriately by the system) or rejected. There are no default route policies. Each policy must be created explicitly. Policy parameters are modifiable. Page SAS E OS Routing Protocols Guide

13 Route Policies Policy Statements Route policies contain policy statements containing ordered entries containing match conditions and actions you specify. The entries should be sequenced from the most explicit to least explicit. IGMP group membership report processing can be implemented according to your defined policies. Policy-based routing allows you to dictate whether to process or drop the traffic. Route policies can match a given route policy entry and continue searching for other matches within the same route policy. The process can stop when the first complete match is found and executes the action defined in the entry, either to accept or reject packets that match the criteria or proceed to the next entry. You can specify matching criteria based on sourceor destination. You can also provide more matching conditions by specifying criteria such as: Prefix list A named list of prefixes. From criteria source IP address and destination (for example, a destination IP multicast group address) SAS E OS Routing Protocols Guide Page 279

14 Configuring Route Policies Default Action Behavior The default action specifies how packets are to be processed when a policy related to the route is not explicitly configured. The following default actions are applied in the event that: A route policy does not specify a matching condition, all the routes being compared with the route policy are considered to be matches. A packet does not match any policy entries, then the next policy is evaluated. If a match does not occur then the last entry in the last policy is evaluated. If no default action is specified, the default behavior of the protocol controls whether the routes match or not. If a default action is defined for one or more of the configured route policies, then the default action is handled as follows: The default action can be set to all available action states including accept, reject, nextentry, and next-policy. If the action states accept or reject, then the policy evaluation terminates and the appropriate result is returned. If a default action is defined and no matches occurred with the entries in the policy, then the default action is used. If a default action is defined and one or more matches occurred with the entries of the policy, then the default action is not used. Denied IP Prefixes The following IP address prefixes are not allowed by the routing protocols and the Route Table Manager and are not be populated within the forwarding table: /8 or longer /8 or longer /4 or longer /4 or longer Any other prefixes that need to be filtered can be filtered explicitly using route policies. When you want unique behaviors to control route characteristics. For example, change the route preference. Page SAS E OS Routing Protocols Guide

15 Route Policies Configuration Notes This section describes route policy configuration caveats. General When configuring policy statements, the policy statement name must be unique SAS E OS Routing Protocols Guide Page 281

16 Configuration Notes Page SAS E OS Routing Protocols Guide

17 Route Policies Configuring Route Policies with CLI This section provides information to configure route policies using the command line interface. Topics in this section include: Route Policy Configuration Overview on page 296 When to Create Routing Policies on page 296 Policy Evaluation on page 298 Configuring Route Policy Components on page 304 Creating a Route Policy on page 306 Beginning the Policy Statement on page 305 Configuring an Entry on page 308 Route Policy Configuration Management Tasks on page SAS E OS Routing Protocols Guide Page 295

18 Route Policy Configuration Overview Route Policy Configuration Overview Route policies allow the configuration of IGMP group membership reports filtering rules. When to Create Routing Policies Route policies are created in the config>router context. There are no default route policies. Each route policy must be explicitly created and applied. A route policy impacts the flow of packets within and through the router. Route policies can be created to control: To filter IGMP membership reports from specific hosts and/or specific multicast groups. Before a route policy is applied, analyze the policy s purpose and be aware of the results (and consequences) when packets match the specified criteria and the associated actions and default actions, if specified, are executed. Membership reports can be filtered based on a specific source address. Page SAS E OS Routing Protocols Guide

19 Route Policies Policy Evaluation Routing policy statements can consist of as few as one or several entries. The entries specify the matching criteria. The packet fields are compared to the first entry in the policy statement. If it matches, the specified entry action is taken, either accepted or rejected. If the action is to accept or reject the route, that action is taken and the evaluation of the route ends. If the route does not match the first entry, the route is compared to the next entry (if more than one is configured) in the policy statement. If there is a match with the second entry, the specified action is taken. If the action is to accept or reject the route, that action is taken and the evaluation of the route ends, and so on. Each route policy statement can have a default-action clause defined. If a default-action is defined for one or more of the configured route policies, then the default actions should be handled in the following ways: The process stops when the first complete match is found and executes the action defined in the entry. If the packet does not match any of the entries, the system executes the default action specified in the policy statement. Figure 16 depicts an example of the route policy process. Route policies can also match a given route policy entry and continue to search for other entries within either the same route policy or the next route policy by specifying the next-entryoption in the entry s action command SAS E OS Routing Protocols Guide Page 297

20 Route Policy Configuration Overview ROUTE/ PACKET POLICY-STATEMENT 274 DEFAULT ACTION ENTRY 1 matches ENTRY ACTION: ACCEPT OR REJECT ENTRY 20 matches ACCEPT OR REJECT ENTRY 30 matches ACCEPT OR REJECT no match POLICY-STATEMENT 275 DEFAULT ACTION ENTRY 1 matches ENTRY ACTION: ACCEPT OR REJECT ENTRY 2 matches ACCEPT OR REJECT ENTRY 3 matches ACCEPT OR REJECT no match DEFAULT ACTION SPECIFIED? yes PERFORM DEFAULT ACTION no PERFORM ACTION SPECIFIED BY PROTOCOL Figure 16: Route Policy Process Example Page SAS E OS Routing Protocols Guide

21 Route Policies Basic Configurations This section provides information to configure route policies and configuration examples of common tasks. The minimal route policy parameters that need to be configured are: Policy statement with the following parameters specified: At least one entry Entry action Following is a sample route policy configuration: A:ALA-B>config>router>policy-options# info A:ALA-B>config>router>policy-options#info prefix-list "host" prefix /8 longer prefix-list "group" prefix /32 exact policy-statement "block-igmp" description "Reject-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host" action next-entry entry 2 from group-address "group" action reject default-action accept policy-statement "permit-igmp" description "Accept-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host3" group-address "group3" action accept default-action reject A:ALA-B>config>router>policy-options# 7210 SAS E OS Routing Protocols Guide Page 299

22 Configuring Route Policy Components Configuring Route Policy Components Use the CLI syntax displayed below to configure: Creating a Route Policy on page 306 Beginning the Policy Statement on page 305 Configuring an Entry on page 308 Page SAS E OS Routing Protocols Guide

23 Route Policies Beginning the Policy Statement Use the following CLI syntax to begin a policy statement configuration. In order for a policy statement to be complete an entry must be specified (see Configuring an Entry on page 308). CLI Syntax: config>router>policy-options begin policy-statement name description text The following error message displays when the you try to modify a policy options command without entering begin first. A:ALA-B>config>router>policy-options# policy-statement allow all MINOR: CLI The policy-options must be in edit mode by calling begin before any changes can be made. The following example displays policy statement configuration command usage. These commands are configured in the config>router context. Example: config>router# policy-options policy-options# begin There are no default policy statement options. All parameters must be explicitly configured SAS E OS Routing Protocols Guide Page 301

24 Configuring Route Policy Components Creating a Route Policy To enter the mode to create or edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include: The commit command saves changes made to route policies during a session. The abort command discards changes that have been made to route policies during a session. The following error message displays when the you try to modify a policy options command without entering begin first. A:ALA-B>config>router>policy-options# policy-statement allow all MINOR: CLI The policy-options must be in edit mode by calling begin before any changes can be made. A:ALA-B>config>router>policy-options# info # # Policy # policy-options begin policy-statement "allow all" description "General Policy" A:ALA-B>config>router>policy-options# Page SAS E OS Routing Protocols Guide

25 Route Policies Configuring a Default Action Specifying a default action is optional. The default action controls those packets not matching any policy statement entries. If no default action is specified for the policy, then the action associated with the protocol to which the routing policy was applied is performed. A policy statement must include at least one entry (see Configuring an Entry on page 308). To enter the mode to create or edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include: The commit command saves changes made to route policies during a session. The abort command discards changes that have been made to route policies during a session SAS E OS Routing Protocols Guide Page 303

26 Configuring Route Policy Components Configuring an Entry An entry action must be specified. The other parameters in the entry action context are optional. Refer to the Route Policy Command Reference on page 315 for the commands and syntax. The following example displays entry parameters and includes the default action parameters which were displayed in the previous section. A:ALA-B>config>router>policy-options# info prefix-list "host" prefix /8 longer prefix-list "group" prefix /32 exact policy-statement "block-igmp" description "Reject-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host" action next-entry entry 2 from group-address "group" action reject default-action accept A:ALA-B>config>router>policy-options# A:ALA-B>config>router>policy-options# info prefix-list "host" prefix /8 longer prefix-list "group" prefix /32 exact A:ALA-B>config>router>policy-options# Page SAS E OS Routing Protocols Guide

27 Route Policies Route Policy Configuration Management Tasks This section discusses the following route policy configuration management tasks: Editing Policy Statements and Parameters on page 313 Deleting an Entry on page 314 Deleting a Policy Statement on page 314 Editing Policy Statements and Parameters Route policy statements can be edited to modify, add, or delete parameters. To enter the mode to edit route policies, you must enter the begin keyword at the config>router> policyoptions prompt. Other editing commands include: The commit command saves changes made to route policies during a session. The abort command discards changes that have been made to route policies during a session. The following example displays a changed configuration: A:ALA-B>config>router>policy-options# info prefix-list "host" prefix /8 longer prefix-list "group1" prefix /32 exact policy-statement "block-igmp" description "Reject-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host" action next-entry entry 2 from group-address "group1" action reject default-action accept A:ALA-B>config>router>policy-options# 7210 SAS E OS Routing Protocols Guide Page 305

28 Route Policy Configuration Management Tasks Deleting an Entry Use the following CLI syntax to delete a policy statement entry: CLI Syntax: config>router>policy-options begin commit abort policy-statement name no entry entry-id The following example displays the commands required to delete a policy statement entry. Example: config>router>policy-options# begin policy-options# policy-statement "1" policy-options>policy-statement# no entry 4 policy-options>policy-statement# commit Deleting a Policy Statement Use the following CLI syntax to delete a policy statement: CLI Syntax: config>router>policy-options begin commit abort no policy-statement name The following example displays the commands required to delete a policy statement. Example: config>router>policy-options# begin policy-options# no policy-statement 1 policy-options# commit Page SAS E OS Routing Protocols Guide

29 Route Policies Route Policy Command Reference Command Hierarchies Route Policy Configuration Commands on page 315 Show Commands on page 318 Route Policy Configuration Commands config [no] router [no] policy-options begin commit abort [no] policy-statement name default-action {accept next-entry reject} no default-action description description-string no description [no] entry entry-id action {accept next-entry reject} no action description description-string no description [no] from host-ip prefix-list-name no host-ip host-ip prefix-list-name no host-ip prefix-list name [name...(up to 5 max)] no prefix-list source-address ip-address no source-address 7210 SAS E OS Routing Protocols Guide Page 315

30 Route Policy Command Reference config [no] router [no] policy-options [no] prefix-list name prefix ip-prefix/prefix-length [exact longer through length prefix-lengthrange length1-length2] no prefix [ipv-prefix/prefix-length] [exact longer through length prefixlength-range length1-length2] Show Commands show router policy [name prefix-list name admin] Page SAS E OS Routing Protocols Guide

31 Route Policies Route Policy Command Reference Generic Commands abort Syntax Context Default abort config>router>policy-options This command is required to discard changes made to a route policy. none begin Syntax Context Description Default begin config>router>policy-options This command is required in order to enter the mode to create or edit route policies. none commit Syntax Context Description Default commit config>router>policy-options This command is required to save changes made to a route policy. none 7210 SAS E OS Routing Protocols Guide Page 319

32 Route Policy Command Reference description Syntax Context Description Default Parameters description string no description config>router>policy-options>policy-statement config>router>policy-options>policy-statement>entry This command creates a text description which is stored in the configuration file to help identify the content of the entity. The no form of the command removes the string from the configuration. none string The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. Page SAS E OS Routing Protocols Guide

33 Route Policies Route Policy Options policy-options Syntax Context Description Default [no] policy-options config>router This command enables the context to configure route policies. Route policies are used for IGMP group membership report filtering. The no form of the command deletes the route policy configuration. none 7210 SAS E OS Routing Protocols Guide Page 321

34 Route Policy Command Reference Route Policy Prefix Commands prefix-list Syntax Context Description Default Parameters [no] prefix-list name config>router>policy-options This command creates a context to configure a prefix list to use in route policy entries. The no form of the command deletes the named prefix list. none name The prefix list name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. prefix Syntax Context Description Parameters [no] prefix ip-prefix/prefix-length { [exact longer through length ] [prefix-length-range length1-length2 ] } no prefix [ipv-prefix/prefix-length] [exact longer through length prefix-length-range length1- length2] config>router>policy-options>prefix-list This command creates a prefix entry in the route policy prefix list. The no form of the command deletes the prefix entry from the prefix list. ip-prefix The IP prefix for prefix list entry in dotted decimal notation. Values ipv4-prefix: a.b.c.d (host bits must be 0) ipv4-prefix-length: 0 32 exact Specifies the prefix list entry only matches the route with the specified ip-prefix and prefix mask (length) values. longer Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix mask length values greater than the specified mask. through length Specifies the prefix list entry matches any route that matches the specified ip-prefix and has a prefix length between the specified length values inclusive. Values 0 32 prefix-length-range length1 - length2 Specifies a route must match the most significant bits and have a prefix length with the given range. The range is inclusive of start and end values. Values 0 32, length2 > length1 Page SAS E OS Routing Protocols Guide

35 Route Policies Route Policy Entry Match Commands entry Syntax Context Description Default Parameters entry entry-id no entry config>router>policy-options>policy-statement This command creates the context to edit route policy entries within the route policy statement. Multiple entries can be created using unique entries. The 7210 SAS OS s the filter when the first match is found and executes the action specified. For this reason, entries must be sequenced correctly from most to least explicit. An entry does not require matching criteria defined (in which case, everything matches) but must have at least define an action in order to be considered complete. Entries without an action are considered incomplete and will be rendered inactive. The no form of the command removes the specified entry from the route policy statement. none entry-id The entry ID expressed as a decimal integer. An entry-id uniquely identifies match criteria and the corresponding action. It is recommended that multiple entries be given entry-ids in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries. Values from Syntax Context Description [no] from config>router>policy-options>policy-statement>entry This command creates the context to configure policy match criteria based on the packet's source IP address or the destination multicast group address. If no condition is specified, all route sources are considered to match. The no form of the command deletes the source match criteria for the route policy statement entry SAS E OS Routing Protocols Guide Page 323

36 Route Policy Command Reference group-address Syntax Context Description Default Parameters group-address prefix-list-name no group-address config>router>policy-options>policy-statement>entry>from This command specifies the multicast group-address prefix list containing multicast group-addresses that are imbedded in the join or prune packet as a filter criterion. The prefix list must be configured prior to entering this command. Prefix lists are configured in the config>router>policy-options>prefix-list context. The no form of the command removes the criterion from the configuration. no group-address prefix-list-name The prefix-list name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. The prefix-list-name is defined in the config>router>policy-options>prefix-list context. host-ip Syntax Context Description Default Parameters host-ip prefix-list-name config>router>policy-options>policy-statement>entry>from This command specifies a prefix list host IP address as a match criterion for the route policy-statement entry. no host-ip prefix-list-name The prefix-list name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. The prefix-list-name is defined in the config>router>policy-options>prefix-list context. policy-statement Syntax Context Description [no] policy-statement name config>router>policy-options This command creates the context to configure a route policy statement. Route policy statements enable appropriate processing of IGMP group membership reports received from hosts. The processing action taken is determined by the action associated with the entries configured in the policy statement. The policy-statement is a logical grouping of match and action criteria. The no form of the command deletes the policy statement. Page SAS E OS Routing Protocols Guide

37 Route Policies Default Parameters no policy-statement No route policy statements are defined. name The route policy statement name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. prefix-list Syntax Context Description Default Parameters prefix-list name [name...up to 5 max] no prefix-list config>router>policy-options>policy-statement>entry>from This command configures a prefix list as a match criterion for a route policy statement entry. If no prefix list is specified, any network prefix is considered a match. The prefix lists specify the network prefix (this includes the prefix and length) a specific policy entry applies. A maximum of five prefix names can be specified. The no form of the command removes the prefix list match criterion. no prefix-list Matches any network prefix. name The prefix list name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. source-address Syntax Context Description Default Description Parameters source-address ip-address no source-address config>router>policy-options>policy-statement>entry>from This command specifies the source address that is embedded in the join or prune packet as a filter criterion. The no form of the command removes the criterion from the configuration. none This command specifies a multicast data source address as a match criterion for this entry. ip-address The IP prefix for the IP match criterion in dotted decimal notation SAS E OS Routing Protocols Guide Page 325

38 Route Policy Command Reference Route Policy Action Commands action Syntax Context Description Default Parameters action {accept next-entry reject} no action config>router>policy-options>policy-statement>entry This command creates the context to configure actions to take for routes matching a route policy statement entry. This command is required and must be entered for the entry to be active. Any route policy entry without the action command will be considered incomplete and will be inactive. The no form of the command deletes the action context from the entry. no action No action is defined. accept Specifies packets matching the entry match criteria will be accepted and processed appropriately. next-entry Specifies that the actions specified would be taken and then policy evaluation would continue with next policy entry (if any others are specified). reject Specifies packets matching the entry match criteria would be rejected. default-action Syntax Context Description Default default-action {accept next-entry reject} no default-action config>router>policy-options>policy-statement This command enables the context to configure actions for packets that do not match any route policy statement entries when the accept parameter is specified. The default action clause can be set to all available action states including: accept, reject, next-entry and next-policy. If the action states accept or reject then the policy evaluation terminates and the appropriate result is returned. If a default action is defined and no match(es) occurred with the entries in the policy then the default action clause is used. If a default action is defined and one or more matches occurred with the entries of the policy then the default action is not used. The no form of the command deletes the default-action context for the policy statement. no default-action No default action is specified. Page SAS E OS Routing Protocols Guide

39 Route Policies Parameters accept Specifies packets matching the entry match criteria will be accepted and processed appropriately. next-entry Specifies that the actions specified would be taken and then policy evaluation would continue with next policy entry (if any others are specified). reject Specifies packets matching the entry match criteria would be rejected.a 7210 SAS E OS Routing Protocols Guide Page 327

40 Route Policy Command Reference Page SAS E OS Routing Protocols Guide

41 Route Policies Show Commands policy Syntax Context Description Parameters Output policy [name prefix-list [name] admin] show>router This command displays configured policy statement information. policy name Displays information similar to the info command for a specific policy-statement. If a name is provided, the matching policy-statement displays. If no statement name is specified, a list of all policies statements and descriptions display. prefix-list name Displays the prefix lists configured in the route policy. admin If the keyword admin is included, the entire policy option configuration displays, including any un-committed configuration changes. This command is similar to the info command. Route Policy Output The following table describes route policy output fields. Label Description Policy Description Policies Displays a list of route policy names. Displays the description of each route policy. The total number of policies configured. The following route policy commands are displayed with different command parameter options: show router policy on page 344 show router policy admin on page 344 Sample Output The show router policy command displays all configured route policies. *A:7210-2# show router policy =============================================================================== Route Policies =============================================================================== Policy Description block-igmp Reject-Reports-From-Specific-Group-And-Host permit-igmp Accept-Reports-From-Specific-Group-And-Host Policies : 2 =============================================================================== *A:7210-2# show router policy 7210 SAS E OS Routing Protocols Guide Page 343

42 Show Commands The show router policy admin command is similar to the info command which displays information about the route policies and parameters. *A:7210-2# show router policy admin prefix-list "host" prefix /8 longer prefix-list "group" prefix /32 exact policy-statement "block-igmp" description "Reject-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host" action next-entry entry 2 from group-address "group" action reject default-action accept policy-statement "permit-igmp" description "Accept-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host1" group-address "group1" action accept default-action reject *A:7210-2#... A:ALA-1# show router policy admin Page SAS E OS Routing Protocols Guide

43 Route Policies The show router policy name command displays information about a specific route policy. *A:7210-2# show router policy permit-igmp description "Accept-Reports-From-Specific-Group-And-Host" entry 1 from host-ip "host1" group-address "group1" action accept default-action reject *A:7210-2# The show router policy prefix-list command, lists the prefix-lists configured in the route policy. *A:7210-2# show router policy prefix-list ================================== Prefix Lists ================================== Prefix List Name host group Num Prefix Lists: 2 ================================== *A:7210-2# 7210 SAS E OS Routing Protocols Guide Page 345

44 Show Commands Page SAS E OS Routing Protocols Guide

45 Standards and Protocol Support Standards Compliance IEEE 802.1d Bridging IEEE 802.1p/Q VLAN Tagging IEEE 802.1w Rapid Spanning Tree Protocol IEEE 802.1x Port Based Network Access Control IEEE 802.1ad Provider Bridges IEEE 802.1ag Service Layer OAM IEEE 802.3ah Ethernet in the First Mile IEEE BaseT IEEE 802.3ad Link Aggregation IEEE 802.3ah Ethernet OAM IEEE 802.3u 100BaseTX IEEE 802.3z 1000BaseSX/LX Protocol Support DIFFERENTIATED SERVICES RFC 2474 Definition of the DS Field the IPv4 and IPv6 Headers (Rev) RFC 2597 Assured Forwarding PHB Group (rev3260) RFC 2598 An Expedited Forwarding PHB RFC 3140 Per-Hop Behavior Identification Codes TCP/IP RFC 768 UDP RFC 1350 The TFTP Protocol (Rev. RFC 791 IP RFC 792 ICMP RFC 793 TCP RFC 826 ARP RFC 854 Telnet RFC 1519 CIDR RFC 1812 Requirements for IPv4 Routers RFC 2347 TFTP option Extension RFC 2328 TFTP Blocksize Option RFC 2349 TFTP Timeout Interval and Transfer Size option RADIUS RFC 2865 Remote Authentication Dial In User Service RFC 2866 RADIUS Accounting SSH draft-ietf-secsh-architecture.txt SSH Protocol Architecture draft-ietf-secsh-userauth.txt SSH Authentication Protocol draft-ietf-secsh-transport.txt SSH Transport Layer Protocol draft-ietf-secsh-connection.txt SSH Connection Protocol draft-ietf-secsh- newmodes.txt SSH Transport Layer Encryption Modes TACACS+ draft-grant-tacacs-02.txt NETWORK MANAGEMENT ITU-T X.721: Information technology- OSI-Structure of Management Information ITU-T X.734: Information technology- OSI-Systems Management: Event Report Management Function M.3100/3120 Equipment and Connection Models TMF 509/613 Network Connectivity Model RFC 1157 SNMPv1 RFC 1215 A Convention for Defining Traps for use with the SNMP RFC 1907 SNMPv2-MIB RFC 2011 IP-MIB RFC 2012 TCP-MIB RFC 2013 UDP-MIB RFC 2096 IP-FORWARD-MIB RFC 2138 RADIUS RFC 2571 SNMP-FRAMEWORKMIB RFC 2572 SNMP-MPD-MIB RFC 2573 SNMP-TARGET-&- NOTIFICATION-MIB RFC 2574 SNMP-USER-BASED- SMMIB RFC 2575 SNMP-VIEW-BASEDACM- MIB RFC 2576 SNMP-COMMUNITY-MIB RFC 2665 EtherLike-MIB RFC 2819 RMON-MIB RFC 2863 IF-MIB RFC 2864 INVERTED-STACK-MIB RFC 3014 NOTIFICATION-LOGMIB RFC 3164 Syslog RFC 3273 HCRMON-MIB RFC 3411 An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks RFC Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) RFC Simple Network Management Protocol (SNMP) Applications RFC User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) RFC SNMP MIB draft-ietf-disman-alarm-mib-04.txt IANA-IFType-MIB IEEE8023-LAG-MIB Proprietary MIBs TIMETRA-CHASSIS-MIB.mib TIMETRA-CLEAR-MIB.mib TIMETRA-DOT3-OAM-MIB.mib TIMETRA-FILTER-MIB.mib TIMETRA-GLOBAL-MIB.mib TIMETRA-IEEE8021-CFM-MIB.mib TIMETRA-LAG-MIB.mib TIMETRA-LOG-MIB.mib TIMETRA-MIRROR-MIB.mib TIMETRA-NTP-MIB.mib TIMETRA-OAM-TEST-MIB.mib TIMETRA-PORT-MIB.mib TIMETRA-QOS-MIB.mib TIMETRA-SAS-GLOBAL-MIB.mib TIMETRA-SAS-PORT-MIB.mib TIMETRA-SAS-QOS-MIB.mib TIMETRA-SAS-SYSTEM-MIB.mib TIMETRA-SCHEDULER-MIB.mib TIMETRA-SECURITY-MIB.mib TIMETRA-SERV-MIB.mib TIMETRA-SUBSCRIBER-MGMT- MIB.mib TIMETRA-SYSTEM-MIB.mib TIMETRA-TC-MIB.mib TIMETRA-VRTR-MIB.mib Standards and Protocols Page 45

46 Standards and Protocols Page 46 Standards and Protocols

47 INDEX R Route policies overview 12 policy evaluation 19 policy statements 13 configuring beginning 23 command reference 29 creating a route policy 24 default action 25 entry 26 management tasks 27 overview SAS E OS Routing Protocols Guide Page 47

48 Index Page SAS E OS Routing Protocols Guide