Juniper BGP netscreen技术配置手册.pdf

Title: Configuring Internal Border Gateway Protocol Document Number: FW-400-002 Version: 1.0, September 28, 2002 OS Ver: Screen OS 4.0 and Cisco IOS 12.1 (5) HW Platforms this Paper Applies to: NS500/Cisco2611 Audience (Internal or E xternal): Internal Version: Ready for review Configuring Internal Border Gateway Protocol on Screen OS 4.0 Introduction This document describes how to configure internal BGP on Screen OS 4.0 to accept default routes from multiple upstream edge routers to provide route resiliency, Thus, eliminate the need to run additional protocol such as HSRP and VRRP to provide resiliency. Static routes configuration on the edge routers for internal networks are eliminated as now we can advertise these routes through the Screen OS firewall, which support dynamic routing protocol such as BGP and OSPF. The BGP configurations shown for the Cisco devices are just partial BGP configurations require to establish peer relationship with Netscreen firewall. These configurations with the Cisco devices should not be used in any of the production networks and does not represent a complete BGP routing design. The discussion of BGP configuration and design on the Netscreen and Cisco are out of the scope of this paper. This paper was written and tested base on Screen OS 4.0.0 r1 running on Netscreen 500 and Cisco IOS 12.1 (5) running on Cisco 2611 and 2610 routers. Concept Autonomous System (AS) is defined as a set of routers under a single technical administration, using Interior Gateway Protocol (IGP) and common metrics to route packets within the AS. Exterior Gateway Protocol (EGP) is use to route packets between different AS. BGP is an example of Exterior Gateway Protocol. Each AS has a unique AS number, these AS are range from 1 to 65535 where AS