> - Download PDFs
> - redistribute

> # redistribute

> #### Syntax

> The options available vary depending on the routing protocol context; that is, on whether you are configuring BGP, DVMRP, IS-IS, OSPF, or RIP.

> For BGP:

> redistribute { fromProtocol | [ ospf match internal [ external [ 1 | 2 ] ] |
> ospf match external [ 1 | 2 ] [ internal ] ] } [ metric absoluteValue |
> route-map mapTag | weight wtValue ]*

> no redistribute { fromProtocol | [ ospf match internal [ external [ 1 | 2 ] ] |
> ospf match external [ 1 | 2 ] [ internal ] ] } [ metric [ absoluteValue ] |
> route-map [ mapTag ] | weight [ wtValue ] ]*

> For DVMRP:

> [ no ] redistribute fromProtocol [ route-map mapTag ]

> For IS-IS:

> redistribute { fromProtocol | static ip |
> [ ospf match internal [ external [ 1 | 2 ] ] |
> ospf match external [ 1 | 2 ] [ internal ] ] } [ level-1 | level-1-2 | level-2 |
> metric absoluteValue | metric-type { external | internal } |
> route-map mapTag ]*

> no redistribute { fromProtocol | static ip |
> [ ospf match internal [ external [ 1 | 2 ] ] |
> ospf match external [ 1 | 2 ] [ internal ] ] } [ level-1 | level-1-2 | level-2 |
> metric [ absoluteValue ] | metric-type [ external | internal ] | route-map [ mapTag ] ]*

> For OSPFv2:

> redistribute { fromProtocol | ospf match internal }
> [ metric-type { 1 | 2 } | metric absoluteValue | route-map mapTag | tag tagValue ]*

> no redistribute { fromProtocol | ospf match internal }
> [ metric-type [ 1 | 2 ] | metric [ absoluteValue ] | route-map [ mapTag ] |
> tag [ tagValue ] ]*

> redistribute ospf
> { match internal external [ 1 | 2 ] | match external [ 1 | 2 ] [ internal ] }
> [ metric absoluteValue | route-map mapTag | tag tagValue ]*

> no redistribute ospf
> { match internal external [ 1 | 2 ] | match external [ 1 | 2 ] [ internal ] }
> [ metric [ absoluteValue ] | route-map [ mapTag ] | tag [ tagValue ] ]*

> For OSPFv3:

> redistribute { fromProtocol | ospf match internal } | metric-type { 1 | 2 }
> [ metric absoluteValue | tag tagValue | route-map mapTag ]*

> no redistribute { fromProtocol | ospf match internal } | metric-type [ 1 | 2 ]
> [ metric [ absoluteValue ] | tag [ tagValue ] | route-map [ mapTag ] ]*

> [ no ] redistribute ospf
> { match internal external [ 1 | 2 ] | match external [ 1 | 2 ] [ internal ] }
> [ metric [ absoluteValue ] | route-map [ mapTag ] | tag [ tagValue ] ]*

> For RIP:

> redistribute { fromProtocol | ospf match internal [ external [ 1 | 2 ] ] |
> ospf match external [ 1 | 2 ] [ internal ] } [ metric absoluteValue |
> route-map mapTag ]*

> no redistribute { fromProtocol | ospf match internal } [ external [ 1 | 2 ] ] |
> ospf match external [ 1 | 2 ] [ internal ] } [ metric [ absoluteValue ] |
> route-map [ mapTag ] ]*

> #### Release Information

> Command introduced before JUNOSe Release 7.1.0.

> #### Description

> Redistributes routes from one routing domain into another routing domain. For DVMRP, only routes that appear in the RPF table can be redistributed. The no version ends redistribution of information.

> #### Options

> - fromProtocol—Source protocol from which routes are being redistributed; default value is no source protocol defined
>   - access—Redistributes access-server routes (framed routes sourced by AAA)
>   - access-internal—Redistributes internal host routes to directly connected clients
>   - bgp—Routes sourced from BGP protocol
>   - connected—Routes that are established automatically when IP is enabled on an interface (non-multicast routing protocols). For routing protocols such as OSPF and IS-IS, these routes are redistributed as external to the AS. When you specify the connected keyword, only those connected networks that are configured on an interface that is not configured to run IS-IS will be redistributed. For DVMRP, specifying this keyword redistributes routes that are established automatically in the RPF table when another multicast routing protocol, such as PIM, is enabled on an interface.
>   - dvmrp—Routes sourced from DVMRP
>   - isis—Routes sourced from IS-IS
>   - ospf—Routes sourced from OSPF
>   - rip—Routes sourced from RIP
>   - static—Redistributes static routes
> - static ip—Redistributes static routes for IS-IS
> - ospf match—Determines what type(s) of routes to redistribute from OSPF; all OSPF routes are redistributed if you do not specify a type
>   - internal—Redistributes OSPF internal routes
>   - external 1—Redistributes OSPF external routes of metric-type 1
>   - external 2—Redistributes OSPF external routes of metric-type 2
> - absoluteValue—Metric that is applied to all routes from the source protocol, in the range 0–4294967295; in BGP this value is the MED, which defaults to the IGP metric of the redistributed route
> - mapTag—String of up to 32 alphanumeric characters that specifies a route map applied to all routes from the source protocol; all routes are redistributed if you do not specify a route map
> - wtValue—Administrative weight (relative importance) for routes redistributed into the protocol; a number, in the range 0–65535
> - level-1—Specifies the redistribution of routes into only IS-IS level 1
> - level-1-2—Specifies the redistribution of routes into both IS-IS level 1 and level 2
> - level-2—Specifies the redistribution of routes into only IS-IS level 2; this is the default behavior
> - metric-type—Specifies the OSPF or IS-IS metric type for all routes from the source protocol

>   For routes redistributed into IS-IS:

>   - metric-type external—Only the metric of the route itself is considered for comparison
>   - metric-type internal—Both the metric of the route and the cost to the router that advertised the route are considered for comparison; this is the IS-IS default

>   For routes redistributed into OSPF:

>   - metric-type 1—Cost of the external routes is equal to the sum of all internal costs and the external cost
>   - metric-type 2—Cost of the external routes is equal to the external cost alone; this is the OSPF default
> - tagValue—Tag that is applied to all routes from the source protocol, in the range 0–4294967295
> - *—Indicates that one or more parameters can be repeated multiple times in a list in the command line

> #### Mode

> Address Family Configuration, Router Configuration

> #### Updated: 2009-04-17

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.