The document summarizes suggestions for migrating to 4-byte AS numbers in BGP. It discusses upgrading routers in a network in stages, beginning with either border routers, route reflectors, or iBGP clients. While this approach is acceptable, operational issues still need to be considered, such as how to handle AS paths if a border router does not support 4-byte AS numbers. The document provides examples of different upgrading strategies and considerations for various common BGP configurations.
The BIRD Internet Routing Daemon project began in 1998 as a university seminar project. It is an open source routing software and hardware alternative to Quagga/Zebra. BIRD supports many routing protocols including RIP, OSPF, BGP, and more. It is portable, has IPv4 and IPv6 support, and powerful configuration and filtering capabilities. The current stable version is 1.6.3, while version 2.0 introduces major changes like integrated IPv4 and IPv6 support. BIRD is deployed widely and the developers welcome community testing and feedback to help guide future development.
The document discusses several methods for transitioning from IPv4 to IPv6 networks, including dual stack operation, tunneling, and Network Address Translation - Protocol Translation (NAT-PT). Dual stack allows nodes to operate using both IPv4 and IPv6 simultaneously. Tunneling involves encapsulating IPv6 packets inside IPv4 packets to allow IPv6 traffic to transit IPv4 networks. NAT-PT performs translation between IPv6 and IPv4 packets to allow communication between separate IPv4 and IPv6 networks.
BGP Techniques for Network Operators, by Philip Smith.
A presentation given at APRICOT 2016’s BGP Techniques for Network Operators (Part 1 and 2) sessions on 23 February 2016.
This document provides an overview and introduction to the Border Gateway Protocol (BGP). It discusses key concepts of BGP including how it allows networks to advertise routes to each other using attributes like AS paths, next hop, and local preference. The document also covers multihoming techniques without and with BGP, and how BGP attributes like MED are used for traffic engineering.
Slides supporting the "Computer Networking: Principles, Protocols and Practice" ebook. The slides can be freely reused to teach an undergraduate computer networking class using the open-source ebook.
This document discusses advanced topics related to BGP routing protocols. It covers scaling iBGP to large networks using techniques like route reflectors and confederations. Route reflectors allow a network to be divided into clusters with designated routers reflecting routes between clusters, reducing the full iBGP mesh. This improves scaling by lowering configuration and resource overhead on each router. The document also examines how iBGP and the BGP decision process interact with the IGP to determine optimal routes and influence traffic flow.
Interested knowing BGP convergence number for ISP Peering solutions. Learn from IPInfusion's OcNOS BGP test report.
Build your disaggregated Network using IPInfusion's OcNOS.
CodiLime Tech Talk - Adam Kułagowski: IPv6 - introductionCodiLime
IPv6 was created to address the limited address space of IPv4 as global IPv4 address allocation was running out. Some of the key differences between IPv4 and IPv6 include IPv6's significantly larger 128-bit address space compared to IPv4's 32-bit addresses, as well as changes to areas like packet headers, fragmentation, and neighbor discovery. Transition technologies like dual stack, NAT64, and DS-Lite were developed to help transition from IPv4 to IPv6, while ensuring IPv6 connectivity even for networks and devices that still use IPv4. Fully enabling IPv6 requires changes to network infrastructure like firewalls, routers, and switches to support the new protocol.
The BIRD Internet Routing Daemon project began in 1998 as a university seminar project. It is an open source routing software and hardware alternative to Quagga/Zebra. BIRD supports many routing protocols including RIP, OSPF, BGP, and more. It is portable, has IPv4 and IPv6 support, and powerful configuration and filtering capabilities. The current stable version is 1.6.3, while version 2.0 introduces major changes like integrated IPv4 and IPv6 support. BIRD is deployed widely and the developers welcome community testing and feedback to help guide future development.
The document discusses several methods for transitioning from IPv4 to IPv6 networks, including dual stack operation, tunneling, and Network Address Translation - Protocol Translation (NAT-PT). Dual stack allows nodes to operate using both IPv4 and IPv6 simultaneously. Tunneling involves encapsulating IPv6 packets inside IPv4 packets to allow IPv6 traffic to transit IPv4 networks. NAT-PT performs translation between IPv6 and IPv4 packets to allow communication between separate IPv4 and IPv6 networks.
BGP Techniques for Network Operators, by Philip Smith.
A presentation given at APRICOT 2016’s BGP Techniques for Network Operators (Part 1 and 2) sessions on 23 February 2016.
This document provides an overview and introduction to the Border Gateway Protocol (BGP). It discusses key concepts of BGP including how it allows networks to advertise routes to each other using attributes like AS paths, next hop, and local preference. The document also covers multihoming techniques without and with BGP, and how BGP attributes like MED are used for traffic engineering.
Slides supporting the "Computer Networking: Principles, Protocols and Practice" ebook. The slides can be freely reused to teach an undergraduate computer networking class using the open-source ebook.
This document discusses advanced topics related to BGP routing protocols. It covers scaling iBGP to large networks using techniques like route reflectors and confederations. Route reflectors allow a network to be divided into clusters with designated routers reflecting routes between clusters, reducing the full iBGP mesh. This improves scaling by lowering configuration and resource overhead on each router. The document also examines how iBGP and the BGP decision process interact with the IGP to determine optimal routes and influence traffic flow.
Interested knowing BGP convergence number for ISP Peering solutions. Learn from IPInfusion's OcNOS BGP test report.
Build your disaggregated Network using IPInfusion's OcNOS.
CodiLime Tech Talk - Adam Kułagowski: IPv6 - introductionCodiLime
IPv6 was created to address the limited address space of IPv4 as global IPv4 address allocation was running out. Some of the key differences between IPv4 and IPv6 include IPv6's significantly larger 128-bit address space compared to IPv4's 32-bit addresses, as well as changes to areas like packet headers, fragmentation, and neighbor discovery. Transition technologies like dual stack, NAT64, and DS-Lite were developed to help transition from IPv4 to IPv6, while ensuring IPv6 connectivity even for networks and devices that still use IPv4. Fully enabling IPv6 requires changes to network infrastructure like firewalls, routers, and switches to support the new protocol.
Equinix IP Address Renumbering in Singapore and SydneyAPNIC
Equinix IP Address Renumbering in Singapore and Sydney, by Vijay Sethuraman.
A presentation given at APRICOT 2016’s Peering Forum (3) session on 23 February 2016.
The document discusses configuring port aggregation on a network device. It describes establishing a logical port using the interface port-aggregator command before aggregating physical ports to it using the aggregator-group command. It also covers using static or LACP aggregation modes and choosing a load balancing method like src-mac to distribute traffic across the aggregated ports. Supervising and controlling the port aggregation process is also mentioned.
The document contains five case studies on Border Gateway Protocol (BGP). It begins by explaining how BGP works, including the differences between external BGP (eBGP) and internal BGP (iBGP). It then provides instructions on enabling and configuring BGP, forming BGP neighbors, and using loopback interfaces and multihop eBGP. The remaining sections describe various BGP attributes and techniques.
PLNOG 7: Rafał Szarecki - MPLS in an advanced versionPROIDEA
This document discusses MPLS and its benefits including improved route lookup times, traffic engineering capabilities, high availability, and increased scalability. It describes how MPLS provides high availability through techniques like avoiding failures, congestion, capacity planning, and traffic engineering. The document also covers MPLS label distribution protocols, how MPLS can help with failures through techniques like loop-free alternates and pre-computed backup paths, and characteristics of fast reroute which provides protection of MPLS traffic engineering (TE) label switched paths (LSPs).
This document discusses configuring per-VRF tunnel selection on Cisco IOS-XR. The goal is to direct different VRF traffic (CN and IN) over specific tunnels by modifying the BGP next-hop. A route-policy is used to change the BGP next-hop for certain VRFs and neighbors. Static routes are then configured to map the new next-hops to the appropriate tunnels. After applying the policy and static routes, show commands confirm the different VRF traffic is now using the intended tunnels. The document provides notes on applying the policy and potential backup mechanisms.
Policy-Based Routing (PBR) allows network administrators to override the default routing behavior and specify how traffic should be routed based on matching criteria. PBR uses route-maps to match packets and set the next-hop. Route-maps contain match and set clauses - match clauses define the conditions to match packets, and set clauses define the action to take for matched packets such as specifying the next-hop router. Network administrators configure PBR by defining route-maps with match and set statements, applying the route-map to an interface with the ip policy command.
The document discusses using the OpenDaylight BGP speaker to handle different types of routes including:
1. Link-state routes from IS-IS or OSPF that are advertised via BGP-LS and used to create a link-state topology.
2. IPv4 and IPv6 routes that are learned and advertised across domains.
3. Flowspec routes that function similar to OpenFlow rules but can leverage the BGP route reflector infrastructure with actions encoded as BGP communities.
The document outlines how to configure the BGP speaker through RESTCONF to handle these different routes and advertise them, and provides demos of using it for BGP-LS/PCEP, advertising IPv4
This document provides an overview and comparison of the algorithms, phases, and commonalities of modern concurrent garbage collectors in HotSpot, including G1, Shenandoah, and Z GC. It begins with laying the groundwork on stop-the-world vs concurrent collection and heap layout. It then introduces the key differences between the three collectors in their marking, barrier, and compaction approaches. The goal of the document is to provide a technical introduction and high-level differences between these concurrent garbage collectors.
The document discusses using TCP/IP for high-performance computing and describes how TCP performance is impacted by factors like round-trip time, bandwidth limitations, and window size. It provides measurements of bandwidth over TCP for different round-trip times and explains TCP congestion control algorithms and how they influence transmission speed.
CMAF live Ingest protocol and DASH live ingest as developed by DASH Industry forum for uplink (push based) CMAF, DASH and HLS. With CMAF live ingest you can upload CMAF content and archive it or package it on the fly to HLS and/or DASH
The document discusses inter-domain routing and the Border Gateway Protocol (BGP). BGP allows different autonomous systems (AS) that operate independently to exchange routing and reachability information. Each AS abstracts its internal network as a single node and exchanges prefix reachability information with neighboring ASes. BGP selects the best path for each prefix based on attributes like AS path length and relationships between ASes.
PLNOG 3: Ela Jasińska - From the Earth to the Moon From a Quagga-based Route...PROIDEA
This document summarizes the results of testing the OpenBGPd routing software on a route server. Testing included establishing over 1000 BGP sessions, announcing and withdrawing thousands of routes, and measuring CPU, memory, and buffer usage under increasing load. Initial issues found were fixed, including problems with IPv6 withdraw messages and per-peer routing tables. The tests helped identify and address scaling limitations in order to use OpenBGPd for a high performance route server.
This document provides an overview of Asterisk, an open source IP PBX system, comparing it to Opensips and describing some of its key features and functions. Asterisk can be used as a SIP B2BUA, gateway to connect various protocols, and media server for tasks like IVR, music on hold, call parking, and transcoding. It has an easy to learn configuration but only supports IPv4 and UDP transport. The document also covers Asterisk configuration files, dialplan syntax, use of macros and variables, and the AstDB database.
The document discusses interior routing protocols and provides an example configuration of OSPF. It introduces interior routing and the types of interior routing protocols. It then describes OSPF as a link-state routing protocol that is commonly used and provides an example network diagram and OSPF configurations for PE and core routers to advertise networks and exchange routing information within an ISP's network.
Gemification plan of Standard Library on RubyHiroshi SHIBATA
The document discusses plans to extract standard Ruby libraries into gems to improve maintenance. It notes libraries have been extracted as default or bundled gems, with different maintenance policies. Benefits include easier bugfixes and new features, but concerns include complex dependencies, need for cross-platform support, and ensuring gems do not conflict with standard libraries. It provides statistics on libraries extracted in Ruby 2.4 and 2.5 and discusses ongoing work like OpenSSL extraction and addressing naming conflicts.
Noisy information transmission through molecular interaction networksMichael Stumpf
The document discusses cellular decision making processes and how reliably information is transmitted from a cell's environment to its nucleus. It examines how signal transduction networks process and transmit signals, and how intrinsic and extrinsic noise can distort the signal transmission. Some counterintuitive results are observed, such as noise overwhelming the signal or inducing apparent correlations, which reflect the interplay between network dynamics and multiple noise sources. The document also explores modeling intrinsic noise using stoichiometric matrices to represent molecular reactions and species changes.
If you are new to the internet or have been a long-time user but would like to know more about how it works, this class is for you! Do you have a website or are you just starting to think about getting one? Whether you are going to hire a professional firm or go it alone, this course will cover everything you need to get started!
Equinix IP Address Renumbering in Singapore and SydneyAPNIC
Equinix IP Address Renumbering in Singapore and Sydney, by Vijay Sethuraman.
A presentation given at APRICOT 2016’s Peering Forum (3) session on 23 February 2016.
The document discusses configuring port aggregation on a network device. It describes establishing a logical port using the interface port-aggregator command before aggregating physical ports to it using the aggregator-group command. It also covers using static or LACP aggregation modes and choosing a load balancing method like src-mac to distribute traffic across the aggregated ports. Supervising and controlling the port aggregation process is also mentioned.
The document contains five case studies on Border Gateway Protocol (BGP). It begins by explaining how BGP works, including the differences between external BGP (eBGP) and internal BGP (iBGP). It then provides instructions on enabling and configuring BGP, forming BGP neighbors, and using loopback interfaces and multihop eBGP. The remaining sections describe various BGP attributes and techniques.
PLNOG 7: Rafał Szarecki - MPLS in an advanced versionPROIDEA
This document discusses MPLS and its benefits including improved route lookup times, traffic engineering capabilities, high availability, and increased scalability. It describes how MPLS provides high availability through techniques like avoiding failures, congestion, capacity planning, and traffic engineering. The document also covers MPLS label distribution protocols, how MPLS can help with failures through techniques like loop-free alternates and pre-computed backup paths, and characteristics of fast reroute which provides protection of MPLS traffic engineering (TE) label switched paths (LSPs).
This document discusses configuring per-VRF tunnel selection on Cisco IOS-XR. The goal is to direct different VRF traffic (CN and IN) over specific tunnels by modifying the BGP next-hop. A route-policy is used to change the BGP next-hop for certain VRFs and neighbors. Static routes are then configured to map the new next-hops to the appropriate tunnels. After applying the policy and static routes, show commands confirm the different VRF traffic is now using the intended tunnels. The document provides notes on applying the policy and potential backup mechanisms.
Policy-Based Routing (PBR) allows network administrators to override the default routing behavior and specify how traffic should be routed based on matching criteria. PBR uses route-maps to match packets and set the next-hop. Route-maps contain match and set clauses - match clauses define the conditions to match packets, and set clauses define the action to take for matched packets such as specifying the next-hop router. Network administrators configure PBR by defining route-maps with match and set statements, applying the route-map to an interface with the ip policy command.
The document discusses using the OpenDaylight BGP speaker to handle different types of routes including:
1. Link-state routes from IS-IS or OSPF that are advertised via BGP-LS and used to create a link-state topology.
2. IPv4 and IPv6 routes that are learned and advertised across domains.
3. Flowspec routes that function similar to OpenFlow rules but can leverage the BGP route reflector infrastructure with actions encoded as BGP communities.
The document outlines how to configure the BGP speaker through RESTCONF to handle these different routes and advertise them, and provides demos of using it for BGP-LS/PCEP, advertising IPv4
This document provides an overview and comparison of the algorithms, phases, and commonalities of modern concurrent garbage collectors in HotSpot, including G1, Shenandoah, and Z GC. It begins with laying the groundwork on stop-the-world vs concurrent collection and heap layout. It then introduces the key differences between the three collectors in their marking, barrier, and compaction approaches. The goal of the document is to provide a technical introduction and high-level differences between these concurrent garbage collectors.
The document discusses using TCP/IP for high-performance computing and describes how TCP performance is impacted by factors like round-trip time, bandwidth limitations, and window size. It provides measurements of bandwidth over TCP for different round-trip times and explains TCP congestion control algorithms and how they influence transmission speed.
CMAF live Ingest protocol and DASH live ingest as developed by DASH Industry forum for uplink (push based) CMAF, DASH and HLS. With CMAF live ingest you can upload CMAF content and archive it or package it on the fly to HLS and/or DASH
The document discusses inter-domain routing and the Border Gateway Protocol (BGP). BGP allows different autonomous systems (AS) that operate independently to exchange routing and reachability information. Each AS abstracts its internal network as a single node and exchanges prefix reachability information with neighboring ASes. BGP selects the best path for each prefix based on attributes like AS path length and relationships between ASes.
PLNOG 3: Ela Jasińska - From the Earth to the Moon From a Quagga-based Route...PROIDEA
This document summarizes the results of testing the OpenBGPd routing software on a route server. Testing included establishing over 1000 BGP sessions, announcing and withdrawing thousands of routes, and measuring CPU, memory, and buffer usage under increasing load. Initial issues found were fixed, including problems with IPv6 withdraw messages and per-peer routing tables. The tests helped identify and address scaling limitations in order to use OpenBGPd for a high performance route server.
This document provides an overview of Asterisk, an open source IP PBX system, comparing it to Opensips and describing some of its key features and functions. Asterisk can be used as a SIP B2BUA, gateway to connect various protocols, and media server for tasks like IVR, music on hold, call parking, and transcoding. It has an easy to learn configuration but only supports IPv4 and UDP transport. The document also covers Asterisk configuration files, dialplan syntax, use of macros and variables, and the AstDB database.
The document discusses interior routing protocols and provides an example configuration of OSPF. It introduces interior routing and the types of interior routing protocols. It then describes OSPF as a link-state routing protocol that is commonly used and provides an example network diagram and OSPF configurations for PE and core routers to advertise networks and exchange routing information within an ISP's network.
Gemification plan of Standard Library on RubyHiroshi SHIBATA
The document discusses plans to extract standard Ruby libraries into gems to improve maintenance. It notes libraries have been extracted as default or bundled gems, with different maintenance policies. Benefits include easier bugfixes and new features, but concerns include complex dependencies, need for cross-platform support, and ensuring gems do not conflict with standard libraries. It provides statistics on libraries extracted in Ruby 2.4 and 2.5 and discusses ongoing work like OpenSSL extraction and addressing naming conflicts.
Noisy information transmission through molecular interaction networksMichael Stumpf
The document discusses cellular decision making processes and how reliably information is transmitted from a cell's environment to its nucleus. It examines how signal transduction networks process and transmit signals, and how intrinsic and extrinsic noise can distort the signal transmission. Some counterintuitive results are observed, such as noise overwhelming the signal or inducing apparent correlations, which reflect the interplay between network dynamics and multiple noise sources. The document also explores modeling intrinsic noise using stoichiometric matrices to represent molecular reactions and species changes.
If you are new to the internet or have been a long-time user but would like to know more about how it works, this class is for you! Do you have a website or are you just starting to think about getting one? Whether you are going to hire a professional firm or go it alone, this course will cover everything you need to get started!
Network and TCP performance relationship workshopKae Hsu
The document discusses TCP performance factors and techniques to improve TCP performance in network environments. It covers TCP operation principles, factors that impact TCP performance like packet loss, out-of-order packets, and congestion. It also discusses approaches to improve performance through the network like reducing packet loss and congestion, and through appliances like TCP offloading and optimization to reduce system resource usage.
This document outlines test scenarios for 4-byte autonomous system numbers (ASNs) in BGP. It discusses: 1) an overview of 4-byte ASNs including the original 2-byte encoding and expanded 4-byte encoding; 2) BGP capabilities for advertising support of 4-byte ASNs; 3) updates to the AS_PATH and AS_AGGREGATOR attributes to support 4-byte ASNs; 4) new optional AS4_PATH and AS4_AGGREGATOR attributes to carry 4-byte ASNs; and 5) proposed test scenarios involving different combinations of 2-byte and 4-byte ASNs traveling through each other and being aggregated.
Rawnet Lightning Talk - 'What is an idea & how do you create them?'Rawnet
This document discusses what ideas are and how to generate them. It defines an idea as a new combination of old elements. It then provides five exercises to help generate ideas: thinking laterally, drawing the problem and solution, challenging assumptions, considering parallel worlds, and reverse thinking. The document outlines a five stage process for developing an idea: 1) gather raw material, 2) digest the material, 3) undergo unconscious processing, 4) have an "A-ha" moment of insight, and 5) test the idea in reality. Finally, it emphasizes looking for connections between facts and allowing ideas to incubate unconsciously as keys to developing new ideas.
How internet works and how messages are transferred in Internetpagetron
An infographic from http://pagetron.com explains how an email travels through the internet from a user's device connected to their internet service provider's network through routers and optical backbones to reach a mail server like Yahoo mail, where the email is stored and then loaded to the user's computer when they access their email through a web browser.
This document summarizes the history of bots and botnets, how botnets are controlled and used for criminal activities like DDoS attacks and spamming, and the large harms they cause. It discusses how botnets can include millions of compromised systems and generate huge amounts of attack traffic to bring down websites. The document also outlines approaches for detecting and mitigating botnets, including using darknets and honeypots to analyze anomalous traffic and identify infected systems.
FEGTS IP Training - Network Diagnostic IntroductionKae Hsu
This document provides an agenda and overview for an IP network diagnostic training session. The training will cover network diagnostic concepts, hostname resolution verification using nslookup and dig, network connection verification using ping and traceroute, and application condition verification. It includes examples of using these tools and concepts like ICMP packets, TTL, and troubleshooting network reachability. The goal is for students to understand basic network troubleshooting principles and tools.
How To Process And Solve Network Security In ISPKae Hsu
This document discusses security issues and solutions for Internet service providers (ISPs). It covers:
1. Implementing security on the control plane and data plane from both physical and logical positions. This includes securing routers, routing information, and event logging.
2. Examples of control plane security include router access control lists, authenticated routing protocols, route validation databases, and limiting route prefixes.
3. Data plane security focuses on preventing unauthorized packet flows and denial of service attacks on the ISP network.
The document discusses using semantic technologies like XML, RDF, and OWL to represent data on the web in a structured format that is accessible to machines. It describes two main approaches for accessing semantic data on the deep web: ontology plug-in search and deep web service annotation. Both approaches require a semantic web crawler or bot to harvest concepts from deep web forms and iteratively link them to build enriched ontologies that define domain terms and relationships to provide machine-interpretable meaning.
Web Components allow developers to create reusable custom elements that encapsulate HTML, CSS, and JavaScript. They include four specifications: HTML Imports for including and reusing HTML documents; Shadow DOM for encapsulating styles and scripts; Custom Elements for defining new types of HTML elements; and HTML Templates for declaring chunks of reusable markup. These specifications enable more modular and reusable component-based web development.
This document summarizes a presentation on supporting IPv6 with software defined networking (SDN) and network functions virtualization (NFV). It defines SDN as separating the control plane and data plane in networks to allow for programmable, automated configuration changes. OpenFlow is described as an SDN protocol. NFV aims to virtualize network functions to run on virtual machines. Current carrier-grade NAT (CGNAT) solutions are hardware-based, while SDN/NFV could allow for a virtualized CGNAT with benefits like dynamic load adjustment and disaster recovery. The future of networking is predicted to involve open source SDN controllers and virtual switches running on commercial and open source platforms.
The document discusses CDNs and their evolution. It describes how early CDNs used server farms and caching to improve performance. Modern CDNs now use global server load balancing to distribute content across many locations worldwide. CDNs work by caching content at edge servers close to users to improve response times. This raises issues for ISPs, as DNS responses and traffic patterns may be impacted. The document considers both challenges CDNs pose for ISPs and potential aggressive strategies ISPs could employ to handle CDN traffic.
Stingray SG- solution for internet service providers Liubov Belousova
This document discusses the Stingray Service Gateway, an all-in-one network solution. It provides key roles of the Stingray including DPI server for traffic prioritization, BNG server for subscriber management, and carrier grade NAT server. It also lists the available hardware platforms ranging from 6G to 120G and their specifications. The software features of the Stingray are outlined, including traffic analysis, lawful interception, and additional modules. Useful materials for learning more about the Stingray are provided at the end.
The document provides an overview of the Border Gateway Protocol (BGP). It discusses BGP concepts such as autonomous systems, path attributes, and the BGP protocol operation. Key points include that BGP establishes peering sessions to exchange routing information, uses route attributes like AS path, next hop, and communities to determine the best path, and supports techniques like route reflection and confederation to improve scalability in large networks.
BGP Bugs, Hiccups and weird stuff: Issues seen by RT-BGP ToolkitAPNIC
The document discusses the "Real-Time BGP Toolkit", which collects BGP routing data from networks worldwide in real-time and stores the full history. This allows analyzing routing behaviors, detecting issues like hijacks. The toolkit found some BGP implementation bugs still present, like broken 4-byte AS support and misconfigured AS numbers. It encourages networks to check their BGP tables and configurations to address such issues.
bgp features presentation routing protocleBadr Belhajja
BGP is used to route between autonomous systems (AS). It uses TCP for reliable connections between routers in different ASes. BGP has features like route aggregation, route filtering with prefix lists and route maps, and attributes like AS path, local preference, and MED that influence path selection. BGP elects the best path based on criteria like shortest AS path, lowest origin code, and closest IGP neighbor.
This document contains five case studies on BGP configuration and operation. It provides an overview of key BGP concepts like iBGP and eBGP, establishing BGP neighbors, using route maps, and load balancing with eBGP multihop. The case studies demonstrate how to configure features like route redistribution, filtering, route reflection, and route dampening.
Route reflectors allow a transit autonomous system to avoid a full iBGP mesh by acting as a centralized point for iBGP routes. Route reflectors modify the split horizon rules to propagate iBGP learned routes to iBGP peers, eliminating the need for full iBGP mesh. Redundant route reflectors are used to prevent single points of failure. Route reflector clusters are defined to prevent routing loops that could occur with redundant route reflectors.
What would you do if you had access to all the routing data from the Internet? In this talk, we will introduce a new framework for collecting, storing, and parsing routing data in a way that can be made available to network engineers and application developers through a simple and clean REST API. This API presents a new opportunity for network engineers to understand, visualize, and analyze their network in a way consistent with today’s software engineering practices.
BGP Scanner - Isolario BGP-MRT Data Reader C Library and ToolAPNIC
The document discusses BGP route collectors and tools for parsing BGP routing data in MRT format. It introduces the BGP Scanner tool, a highly optimized C library and command line tool for reading and filtering BGP routing data in MRT format. Benchmarks show that BGP Scanner outperforms other tools by being up to 50x faster and using less memory. The document also provides installation instructions and links to documentation for BGP Scanner and other MRT parsing tools.
The document provides information about Border Gateway Protocol (BGP). It discusses BGP basics including terminology, protocol operation, message types, and configuration of BGP peers. Specific topics covered include BGP neighbor and peer relationships, route attributes, and route advertisement between autonomous systems.
An Overview of Border Gateway Protocol (BGP)Jasim Alam
BGP is the exterior gateway protocol that connects autonomous systems on the internet. It uses distance vector routing and TCP to establish connections between routers in different autonomous systems to exchange routing and reachability information. BGP messages advertise routing prefixes, paths, and policies between autonomous systems. Routers maintain BGP routing tables containing routes and their attributes to determine the best paths for traffic. As the number of autonomous systems and routing entries has increased, challenges around scaling the routing system remain an area of ongoing work.
PLNOG 6: Rafał Szarecki - Routing w Sieci - Praktyczne aspekty implementacji ...PROIDEA
This document discusses several aspects of implementing the BGP routing protocol, including:
1. BGP is commonly used not just for routing between autonomous systems but also within a single AS, such as for VPN services.
2. Using route reflectors in internal BGP configurations can reduce the number of required iBGP sessions compared to a full mesh but may cause some suboptimal routing. Proper design is needed to minimize this.
3. There are various approaches to configuring route reflectors such as dedicated routers, shared infrastructure, and redundancy schemes to ensure optimal paths and exit resilience. Memory and CPU optimizations are also important to consider.
I walk through What is BGP, Why BGP and BGP Attributes, Path Selection, Use Case of BGP, iBGP, eBGP, CCNP Routing, Multi Homing
What is BGP?
Why BGP?
BGP Peer Relationships
Configuration of BGP
BGP attributes and Path Selection
BGP use cases
EIGRP is a proprietary routing protocol developed by Cisco that uses a composite metric and has fast convergence properties. It functions as a hybrid of distance-vector and link-state routing protocols, sending subnet mask and VLSM information in updates. EIGRP forms neighbor relationships through periodic hello messages and establishes three key tables - Neighbor, Topology, and Routing - to store neighbor, route, and best path information. It utilizes five packet types and reliable transport to efficiently share routing updates.
PLNOG15: BGP New Advanced Features - Piotr WojciechowskiPROIDEA
This document provides an overview of new advanced BGP features including BGP Graceful Shutdown, BGP Additional Paths, support for multiple sourced paths per redistributed route, BGP Accumulated IGP Metric, and BGP FlowSpec. It describes each feature, how it works, and its configuration. The presenter is a senior network engineer and CCIE with experience designing networks and leading a large Cisco community.
The document provides an introduction and overview of the Border Gateway Protocol version 4 (BGP 4). It discusses key BGP concepts like path vector routing, route aggregation, autonomous system types, classless inter-domain routing, and exterior routes. The document also covers BGP operations, configuration, troubleshooting, and differences between Juniper and Cisco implementations.
Part 10 : Routing in IP networks and interdomain routing with BGPOlivier Bonaventure
This document discusses routing in IP networks and interdomain routing with BGP. It begins by covering intradomain routing protocols like RIP and OSPF, then discusses interdomain routing and the exterior gateway protocol BGP. BGP allows domains to exchange routing information and select paths between domains while applying each domain's routing policies.
IP routing is used to forward packets between networks using IP addresses. Routers use routing protocols like BGP and OSPF to learn about network reachability and maintain routing tables to know where to forward packets. BGP is used between autonomous systems to exchange routing and reachability information, prioritizing paths based on attributes like AS path length, local preference, and MED. Interior routing protocols like OSPF are used within an autonomous system.
This document discusses various techniques for IPv6 transition and coexistence with IPv4, including:
- Dual-stack which allows simultaneous support of both IPv4 and IPv6.
- Tunnels which encapsulate IPv6 packets in IPv4 packets to provide IPv6 connectivity through IPv4 networks.
- Translation techniques like NAT64 which allow communication between IPv4-only and IPv6-only nodes.
BGP is a path-vector routing protocol used between autonomous systems (ASes) on the internet to exchange routing and reachability information. It works by having each AS share information about available routes and their paths through other ASes with their neighboring ASes. This document provides an overview of how BGP operates, including how routes are selected and exported based on policies, the use of attributes to share routing information, and some common issues with BGP like convergence and security concerns that can arise from policy routing.
Similar to 4byte As Number Migration Suggestion (20)
The document discusses how the Internet works at a high level. It covers Internet topology, elements like IP addresses, autonomous systems, routers and switches. It describes routing protocols used within and between autonomous systems. It also discusses Internet security, MPLS, and how routing is performed between Internet service providers.
Redundant Internet service provision - customer viewpointKae Hsu
The document discusses redundant internet service provision from the customer's viewpoint. It covers the requirement for redundancy, different types including backup, load-sharing and multihoming. It also discusses the challenges for service providers in providing redundant services, such as needing new equipment and routing architectures. Solutions for customers are explored, as well as other issues like MPLS VPNs. The next challenges in the area are also noted.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and how new technologies like FTTX are replacing older ones. It also discusses more robust multihoming approaches that maintain redundancy and distribution without requiring BGP or own IP blocks, like using the same protocol across connections without own blocks.
The document discusses recommendations for multihoming, load balancing, and load sharing approaches for end users. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and FTTX. It also discusses more robust multihoming options that maintain redundancy and balance traffic across connections without requiring BGP or own IP blocks, like using the same dynamic routing protocol across all ISP connections.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches for end users. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and FTTX. It also discusses more advanced multihoming options using BGP with independently assigned IP addresses to achieve redundancy and connection resiliency without requiring end users to manage BGP protocols or obtain their own IP blocks. Simpler approaches that maintain benefits without those requirements are preferable.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and how new technologies like FTTX are replacing older ones. It also discusses more robust multihoming options that maintain redundancy and balance traffic across connections without requiring BGP or own IP blocks. The preferred approaches provide benefits like lower cost and complexity while preserving resiliency.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
1. 11th TWNIC IP Open Policy Meeting
2008/11/12, Taipei
4-Byte AS Number Migration Suggestion
2. Agenda
• Quickly Recap
• Assumptions before implementation
• Common BGP deployments
• 4-byte AS number implementation
• Operational issues
• Summary
2008/11/12, Taipei 2
3. Quickly Recap
• Changes in BGP 4-byte AS:
– New BGP capability advertisement
• Capability code: 65
• Capability length: 4
– Attribute update
• AS_PATH attribute carry 4 byte AS
• AGGREGATOR attribute carry 4 byte AS
– New attribute
• Add AS4_PATH attribute
– optional, transitive
– Construct from AS_PATH attribute by 4-byte AS enabled router when face to 2-
byte AS only router
• Add AS4_AGGREGATOR attribute
– optional, transitive
– Construct from AGGREGATOR attribute by 4-byte AS enabled router when face
to 2-byte AS only router
2008/11/12, Taipei 3
4. Quickly Recap
• Limitations:
– NEW BGP speaker need a 2 byte AS to peer with the OLD BGP
speaker.
• No-mappable 4 byte AS can use “23456” as 2 byte AS
– AS4_PATH is not compatible with:
• AS_CONFED_SEQUENCE
• AS_CONFED_SET
• Must use mappable 4 byte member ASN during the migration
– i.e. 0.64512 ~ 0.65535
• Other considerations
– BGP community handling
• Current AS encoding method in BGP community should be updated
• ref: draft-rekhter-as4octet-ext-community-03.txt
– Netflow statistics
• Netflow version 9 support 4-byte AS number
2008/11/12, Taipei 4
5. Quickly Recap
» From “4-Byte AS Numbers, The view from the Old BGP world, p21” by Geoff
Huston, APNIC
2008/11/12, Taipei 5
6. Quickly Recap
• AS4_PATH example
– 193.5.68.0/23
– Attribute Type/Length/Value
• Attribute Type (2 octets)
– 0xe0 => optional, transitive
– 0x11 => AS4_PATH (TYPE CODE 17)
• Attribute Length (Variable)
• AS Path Segments (Variable), which includes
– Segment Type (1 octet)
» 0x02 => AS Sequence
– Segment Length (1 octet)
» 0x03 => AS numbers in the AS Sequence
– Value (Variable)
» 0x00 00 1a ae => 6830 (The AS who generated the AS4_PATH)
» 0x00 00 22 36 => 8758
» 0x00 03 00 0d => 3.13
2008/11/12, Taipei 6
7. Quickly Recap
• AS4_PATH example
– 195.47.195.0/24
– Attribute Type/Length/Value
• Attribute Type (2 octets)
– 0xe0 => optional, transitive
– 0x11 => AS4_PATH (TYPE CODE 17)
• Attribute Length (Variable)
• AS Path Segments (Variable), which includes
– Segment Type (1 octet)
» 0x02 => AS Sequence
– Segment Length (1 octet)
» 0x01 => AS numbers in the AS Sequence
– Value (Variable)
» 0x00 03 00 10 => 3.16 (The AS who generated the AS4_PATH)
2008/11/12, Taipei 7
8. Quickly Recap
• AS4_PATH example
– 2001:7fb:ff00::/48
– Attribute Type/Length/Value
• Attribute Type (2 octets)
– 0xe0 => optional, transitive
– 0x11 => AS4_PATH (TYPE CODE 17)
• Attribute Length (Variable)
• AS Path Segments (Variable), which includes
– Segment Type (1 octet)
» 0x02 => AS Sequence
– Segment Length (1 octet)
» 0x03 => AS numbers in the AS Sequence
– Value (Variable)
» 0x00 00 04 65 => 1125 (The AS who generated the AS4_PATH)
» 0x00 03 00 05 => 3.5
» 0x00 00 31 6e => 12654
2008/11/12, Taipei 8
9. Quickly Recap
» From “4-Byte AS Numbers, The view from the Old BGP world, p23” by Geoff
Huston, APNIC
2008/11/12, Taipei 9
10. Quickly Recap
» From “4-Byte AS Numbers, The view from the Old BGP world, p24” by Geoff
Huston, APNIC
2008/11/12, Taipei 10
11. Assumptions before implementation
• Everyone (uplink ISP, peering ISP, transit customers and yourself)
– enable BGP
– has at least one 2 bytes ASN before 2 byte ASN exhausting
• Following common BGP deployments are considered:
– Only border routers enable BGP
– All routers enable BGP and full-mesh with each other
– All routers enable BGP and implement Route-Reflector
– All routers enable BGP with BGP confederation
– There are more than one AS in the same ISP domain
2008/11/12, Taipei 11
12. Common BGP deployment
• Only border routers enable BGP
eBGP session
iBGP session Your BGP domain
eBGP session in conf. BGP
2008/11/12, Taipei 12
13. Common BGP deployment
• All routers enable BGP and full-mesh with each other
eBGP session
iBGP session Your BGP domain
eBGP session in conf. BGP
2008/11/12, Taipei 13
14. Common BGP deployment
• All routers enable BGP and implement Route-Reflector
eBGP session
iBGP session Your BGP domain
eBGP session in conf. BGP
RR
RR
2008/11/12, Taipei 14
15. Common BGP deployment
• All routers enable BGP with BGP confederation
eBGP session
iBGP session Your BGP domain
eBGP session in conf. BGP
2008/11/12, Taipei 15
16. Common BGP deployment
• There are more than one AS in the same ISP domain
eBGP session
iBGP session Your BGP domain
eBGP session in conf. BGP
2008/11/12, Taipei 16
17. 4-byte AS number implementation
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 2-byte 2-byte
2-byte 2-byte 2-byte 2-byte
• What we have to do?
– Arrange a perfect plan first
– Upgrade the router operating system (ROS) then
• What is the safe implementation approach?
– from border router?
– from Route-Reflector?
• Route-Reflector is so important, it seems not a good choice to upgrade
Route-Reflector first
– from iBGP client?
2008/11/12, Taipei 17
18. 4-byte AS number implementation
• Example 1-1-1
– Your partner is NOT 4-byte AS ready yet
• 1st: You upgrade your border router ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 2-byte 2-byte
2-byte 4-byte 2-byte 2-byte
2008/11/12, Taipei 18
19. 4-byte AS number implementation
• Example 1-1-2
– Your partner is NOT 4-byte AS ready yet
• 1st: You upgrade your border router ROS
• 2nd: You upgrade your iBGP client ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 2-byte 2-byte
2-byte 4-byte 2-byte 4-byte
2008/11/12, Taipei 19
20. 4-byte AS number implementation
• Example 1-1-3
– Your partner is NOT 4-byte AS ready yet
• 1st: You upgrade your border router ROS
• 2nd: You upgrade your iBGP client ROS
• 3rd: You upgrade your Route-Reflector ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 4-byte 4-byte
2-byte 4-byte 4-byte 4-byte
2008/11/12, Taipei 20
21. 4-byte AS number implementation
• Example 1-2-1
– Your partner is NOT 4-byte AS ready yet
• 1st: You upgrade your iBGP client ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 2-byte 2-byte
2-byte 2-byte 2-byte 4-byte
2008/11/12, Taipei 21
22. 4-byte AS number implementation
• Example 1-2-2
– Your partner is NOT 4-byte AS ready yet
• 1st: You upgrade your iBGP client ROS
• 2nd: You upgrade your border router ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 2-byte 2-byte
2-byte 4-byte 2-byte 4-byte
2008/11/12, Taipei 22
23. 4-byte AS number implementation
• Example 1-2-3
– Your partner is NOT 4-byte AS ready yet
• 1st: You upgrade your iBGP client ROS
• 2nd: You upgrade your border router ROS
• 3rd: You upgrade your Route-Reflector ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
2-byte 2-byte 4-byte 4-byte
2-byte 4-byte 4-byte 4-byte
2008/11/12, Taipei 23
24. 4-byte AS number implementation
• Example 2-1-1
– Your partner is 4-byte AS ready
• 1st: You upgrade your border router ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
4/2-byte 4-byte 2-byte 2-byte
4-byte 4-byte 2-byte 2-byte
2008/11/12, Taipei 24
25. 4-byte AS number implementation
• Example 2-1-2
– Your partner is 4-byte AS ready
• 1st: You upgrade your border router ROS
• 2nd: You upgrade your iBGP client ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
4/2-byte 4-byte 2-byte 2-byte
4-byte 4-byte 2-byte 4-byte
2008/11/12, Taipei 25
26. 4-byte AS number implementation
• Example 2-1-3
– Your partner is 4-byte AS ready
• 1st: You upgrade your border router ROS
• 2nd: You upgrade your iBGP client ROS
• 3rd: You upgrade your Route-Reflector ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
4/2-byte 4-byte 4-byte 4-byte
4-byte 4-byte 4-byte 4-byte
2008/11/12, Taipei 26
27. 4-byte AS number implementation
• Example 2-2-1
– Your partner is 4-byte AS ready
• 1st: You upgrade your iBGP client ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
4/2-byte 2-byte 2-byte 2-byte
4-byte 2-byte 2-byte 4-byte
2008/11/12, Taipei 27
28. 4-byte AS number implementation
• Example 2-2-2
– Your partner is 4-byte AS ready
• 1st: You upgrade your iBGP client ROS
• 2nd: You upgrade your border router ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
4/2-byte 4-byte 2-byte 2-byte
4-byte 4-byte 2-byte 4-byte
2008/11/12, Taipei 28
29. 4-byte AS number implementation
• Example 2-2-3
– Your partner is 4-byte AS ready
• 1st: You upgrade your iBGP client ROS
• 2nd: You upgrade your border router ROS
• 3rd: You upgrade your Route-Reflector ROS
border Route-Reflector iBGP client
eBGP iBGP iBGP
4/2-byte 4-byte 4-byte 4-byte
4-byte 4-byte 4-byte 4-byte
2008/11/12, Taipei 29
30. Summary
• It is fine to upgrade ROS no matter
– from border router, iBGP client then Route-Reflector
– from iBGP client, border router then Route-Reflector
• Thank you
• But…..
Are they still good
approaches when consider
operational issues?
2008/11/12, Taipei 30
31. Operational issues
• AS-PATH issues on border router
– AS-PATH is a very important attribute for BGP policy design
• Allow or deny BGP routes
• Set local preference
• Set BGP community
– If the border router did not support 4-byte AS number, we can NOT
handle 4-byte AS BGP routes by AS-PATH attribute
• Can NOT permit/deny BGP routes by AS path information
– Old ROS can not recognize AS4_PATH attribute either
• Can NOT set BGP local preference on border router by AS path information
• Can NOT set BGP community on border router by AS path information
2008/11/12, Taipei 31
32. Operational issues
• Upgrade Router Operating System issues
– It is not a easy work
• Heavy loading in testing the new ROS
• Much different from patch/upgrade personal computer OS
– Upgrade ROS then reboot router impact the network and SLA
• Especially in those network environments without appropriate redundant
design
• Higher SLA requirement is a challenge: 99.99% even 99.999%
– With a serious, detail plan, upgrade all router ROS will spend many
months even more than one year.
• Upgrade processes are risky
• Any un-conditional network event will postpone the scheduled upgrade
process
– Upgrade ROS guide in operation:
• DON’T TOUCH YOUR ROS UNLESS YOU HAVE TO!!!!!
2008/11/12, Taipei 32
33. Summary
• If we want to consider the operational issues, to upgrade border
router ROS first is a better approach
– The AS-PATH handling will not be a problem anymore
– It is fine to upgrade border router only
• Old BGP router will NOT be confused by duplicate AS23456
• We can reboot the router for serious ROS bug-fix patch only rather than just
4-byte AS upgrade
– After the border router, the upgrade sequence could be considered by
• (option) other eBGP router in the same autonomous domain
• (option) CONFED border router
• (option) iBGP client
• (option) Route-Reflector
2008/11/12, Taipei 33
34. Reference
• TWNIC OPM
– 8th OPM
• 4 byte ASN的現況
• 4-byte ASNs Test Scenarios
– 6th OPM
• BGP Support for Four-octet AS Number Space
• RFC
– RFC4271 - “A Border Gateway Protocol 4 (BGP-4)”
– RFC4893 - “BGP Support for Four-octet AS Number Space”
• NANOG
– NANOG 39; “4-Byte AS Numbers, The view from the Old BGP world” by
Geoff Huston, APNIC
• IETF draft
– Four-octet AS Specific BGP Extended Community
2008/11/12, Taipei 34