Dell S6000 FTOS 9.0(2.0) Command Line Reference Guide for the System - Page 251

peer-group-name Enter the name of the peer group to remove the private AS numbers Defaults Disabled (that is, private AS number are not removed). Command Modes ROUTER BGP Usage Information Applies to EBGP neighbors only. You must configure your system to accept 4-Byte formats before entering a 4-Byte AS Number. If the AS-PATH contains both public and private AS number or contains AS numbers of an EBGP neighbor, the private AS numbers are not removed. If a confederation contains private AS numbers in its AS-PATH, the software removes the private AS numbers only if they follow the confederation numbers in the AS path. Private AS numbers are 64512 to 65535 (2-Byte). Command History Version 9.0.2.0 Version 8.3.11.1 Version 7.8.1.0 Introduced on the S6000. Introduced on the Z9000. Introduced support on S-Series neighbor route-map s z S6000 Apply an established route map to either incoming or outbound routes of a BGP neighbor or peer group. Syntax neighbor {ip-address | peer-group-name} route-map map-name {in | out} To remove the route map, use the no neighbor {ip-address | peer-group-name} route-map map-name {in | out} command. Parameters ip-address peer-group-name map-name in out Enter the IP address of the neighbor in dotted decimal format. Enter the name of the peer group. Enter the name of an established route map. If the Route map is not configured, the default is deny (to drop all routes). Enter the keyword in to filter inbound routes. Enter the keyword out to filter outbound routes. Defaults Not configured. Command Modes ROUTER BGP Usage When you apply a route map to outbound routes, only routes that match at least one section of the route Information map are permitted. If you identify a peer group by name, the peers in that peer group inherit the characteristics in the Route map used in this command. If you identify a peer by IP address, the Route map overwrites either the inbound or outbound policies on that peer. Border Gateway Protocol | 251