In this example we will assume that BGP is configured on the peering router with IP address 1.1.1.1, as autonomous system number (ASN) 6000. For any routing configuration, static or dynamic, a default routing instance called default-instance must be defined in the SSR configuration. The BGP configuration exists in the routing configuration container within the SSR data model. Refer to the Element Reference section of our documentation for a better understanding about basics of the SSR data model. The running SSR system should already include configuration for basic platform functionality (e.g., router, node, device-interface, network-interface) and basic SSR modeling configuration (e.g., tenants, services, etc.). This section presumes that you have a running SSR system and wants to add configuration to support BGP. In this configuration guide we will also discuss a SSR-specific feature referred to as "BGP over SVR" (or BGPoSVR), which combines the power of Secure Vector Routing with the rich feature set of the BGP protocol. Learning routes from BGP simplifies enterprise configuration and integration with Secure Vector Routing. BGP can also be used for routing within an autonomous system as an interior gateway protocol when doing so it is referred to as iBGP. BGP makes routing decisions based on paths and network policies although historically mainly seen in service provider networks, it is now gaining acceptance in large enterprise networks. The Border Gateway Protocol (BGP) is a standard exterior gateway protocol developed for exchanging routing and reachability information between Autonomous Systems, a collection of IP routing prefixes managed by a single administrative entity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |