Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options]Description
Specify the routing device’s IP address.
The router identifier is used by BGP and OSPF to identify the routing device from which a packet originated. The router identifier usually is the IP address of the local routing device. If you do not configure a router identifier, the IP address of the first interface to come online is used. This is usually the loopback interface. Otherwise, the first hardware interface with an IP address is used.
Note:
We strongly recommend that you configure the router identifier under the [edit routing-options] hierarchy level to avoid unpredictable behavior if the interface address on a loopback interface changes.
You must configure a router-id in order for BGP and OSPF to function in a routing instance. Use the show route instance detail command to display the router-id value for a routing instance. If the router-id is 0.0.0.0, then the routing instance has no router-id.
For more information about the router identifier in OSPF, see Example: Configuring an OSPF Router Identifier.
Note:
If you run OSPF for IPv6 or BGP for IPv6 in a routing instance, you must configure an IPv4 router identifier (router-id) in the routing instance itself. In other words, the IPv4 router-id in the main routing instance is not inherited by other routing instances. Even if you run only IPv6 OSPF or BGP in a routing instance, the IPv4 router-id must be configured because OSPF and BGP, even when used exclusively with IPv6, use the IPv4 router-id for handshaking. If you do not configure the IPv4 router-id in the IPv6 OSPF or BGP routing instance, then the IPv6 protocols will use invalid IPv4 address 0.0.0.0 and the adjacencies and connections will fail.
When you configure a router ID with an IP address that differs from the BGP local address for EVPN routing instances, you must also configure a policy that exports the local IP address for BGP routes. This ensures that EVPN traffic will be properly routed. For more information on exporting BGP routes, see Basic BGP Routing Policies.
Options
address—IP address of the routing device.
Default: Address of the first interface encountered by Junos OS
Starting in Junos OS Release 20.4R1, you can establish a BGP connection with the BGP identifier that is a 4-octet, unsigned, and non-zero integer and it needs to be unique only within the Autonomous System (AS) per RFC6286, Autonomous-System-Wide Unique BGP Identifier for BGP-4
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.
A) | When there are multiple routes available to the same network with different route types, routers use this order of preference (from highest to lowest): 1. Intra-area routes. 2. Inter-area routes. 3. External Type-1 routes. 4. External Type-2 routes. |
B) | If there are multiple routes to a network with the same route type, the OSPF metric calculated as cost based on the bandwidth is used for selecting the best route. The route with the lowest value for cost is chosen as the best route. |
C) | If there are multiple routes to a network with the same route type and cost, it chooses all the routes to be installed in the routing table, and the router does equal cost load balancing across multiple paths. |
For more information refer to:
View more Cisco How-To Tutorials
//www.BradReese.ComBrad Reese is research manager at BradReese.Com, advancing the careers of 600,000-plus certified individuals in the growing Cisco Career Certification Program.
Copyright © 2008 IDG Communications, Inc.