Deployment Guide

Table Of Contents
Include specific ISIS routes in BGP.
ROUTER BGP or CONF-ROUTER_BGPv6_ AF mode
redistribute isis [level-1 | level-1-2 | level-2] [metric value] [route-map map-name]
Configure the following parameters:
level-1, level-1-2, or level-2: Assign all redistributed routes to a level. The default is level-2.
metric value: The value is from 0 to 16777215. The default is 0.
map-name: name of a configured route map.
Include specific OSPF routes in IS-IS.
ROUTER BGP or CONF-ROUTER_BGPv6_ AF mode
redistribute ospf process-id [match external {1 | 2} | match internal] [metric-type
{external | internal}] [route-map map-name]
Configure the following parameters:
process-id: the range is from 1 to 65535.
match external: the range is from 1 or 2.
match internal
metric-type: external or internal.
map-name: name of a configured route map.
Enabling Additional Paths
The add-path feature is disabled by default.
NOTE: Dell Networking recommends not using multipath and add path simultaneously in a route reflector.
To allow multiple paths sent to peers, use the following commands.
1. Allow the advertisement of multiple paths for the same address prefix without the new paths replacing any previous ones.
CONFIG-ROUTER-BGP mode
bgp add-path {send | both} path-count count bgp add-path receive
The range is from 2 to 64.
2. Allow the specified neighbor/peer group to send/ receive multiple path advertisements.
CONFIG-ROUTER-BGP mode
neighbor {ipaddress| peergroup name} add-path [send | receive| both] path-count count
NOTE:
The path-count parameter controls the number of paths that are advertised, not the number of paths that are
received.
Configuring IP Community Lists
Mmultiple methods of manipulating routing attributes are supported in the Dell Networking OS.
One attribute you can manipulate is the COMMUNITY attribute. This attribute is an optional attribute that is defined for a group
of destinations. You can assign a COMMUNITY attribute to BGP routers by using an IP community list. After you create an IP
community list, you can apply routing decisions to all routers meeting the criteria in the IP community list.
IETF RFC 1997 defines the COMMUNITY attribute and the predefined communities of INTERNET, NO_EXPORT_SUBCONFED,
NO_ADVERTISE, and NO_EXPORT. All BGP routes belong to the INTERNET community. In the RFC, the other communities are
defined as follows:
All routes with the NO_EXPORT_SUBCONFED (0xFFFFFF03) community attribute are not sent to CONFED-EBGP or EBGP
peers, but are sent to IBGP peers within CONFED-SUB-AS.
All routes with the NO_ADVERTISE (0xFFFFFF02) community attribute must not be advertised.
All routes with the NO_EXPORT (0xFFFFFF01) community attribute must not be advertised outside a BGP confederation
boundary, but are sent to CONFED-EBGP and IBGP peers.
Border Gateway Protocol IPv4 (BGPv4)
191