Dell PowerConnect FCS624S Configuration Guide - Page 1092

30 Filtering These commands configure a route map that matches on routes whose destination network is specified in ACL 1, and sets the next hop in the routes to the neighbor address (inbound filtering) or the local IP address of the BGP4 session (outbound filtering). Syntax: set ip next-hop peer-address The value that the software substitutes for peer-address depends on whether the route map is used for inbound filtering or outbound filtering: • When you use the set ip next-hop peer-address command in an inbound route map filter, peer-address substitutes for the neighbor IP address. • When you use the set ip next-hop peer-address command in an outbound route map filter, peer-address substitutes for the local IP address of the BGP4 session. NOTE You can use this command for a peer group configuration. Deleting a community from a BGP4 route To delete a community from a BGP4 route community attributes field, enter commands such as the following. PowerConnect(config)#ip community-list standard std_3 permit 12:99 12:86 PowerConnect(config)#route-map bgp6 permit 1 PowerConnect(config-routemap bgp6)#match ip address 1 PowerConnect(config-routemap bgp6)#set comm-list std_3 delete The first command configures a community ACL containing community numbers 12:99 and 12:86. The remaining commands configure a route map that matches on routes whose destination network is specified in ACL 1, and deletes communities 12:99 and 12:86 from those routes. The route does not need to contain all the specified communities in order for them to be deleted. For example, if a route contains communities 12:86, 33:44, and 66:77, community 12:86 is deleted. Syntax: set comm-list delete The parameter specifies the name of a community list ACL. Using a table map to set the rag value Route maps that contain set statements change values in routes when the routes are accepted by the route map. For inbound route maps (route maps that filter routes received from neighbors), this means that the routes are changed before they enter the BGP4 route table. For tag values, if you do not want the value to change until a route enters the IP route table, you can use a table map to change the value. A table map is a route map that you have associated with the IP routing table. The Layer 3 Switch applies the set statements for tag values in the table map to routes before adding them to the route table. To configure a table map, you configure the route map, then identify it as a table map. The table map does not require separate configuration. You create it simply by calling an existing route map a table map. You can have one table map. NOTE Use table maps only for setting the tag value. Do not use table maps to set other attributes. To set other route attributes, use route maps or filters. 1050 PowerConnect B-Series FCX Configuration Guide 53-1002266-01