Network Automation provides IT administrators and network operators significant benefits. This solution guide
describes an approach to build data centers using Layer3 BGP routing protocol.
It also summarizes on some design philosophies for data center and why E-BGP is better suited.
■ Large-scale data center requirements
■ Large-scale data center topologies
■ Large-scale data center routing
■ EBGP-routed large-scale Clos topology-based data cente
Modern processors are faster than memory
So Processors may waste time for accessing memory
Its purpose is to make the main memory appear to the processor to be much faster than it actually is
- Defined the specifications and designed an architecture of the MSDAP chip that performs convolution of two signals in least possible area & power.
- Implemented a RTL model of the MSDAP chip which consists of a Controller, ALU, Memories and Serial communication Unit.
- Synthesized the design in Synopsys Design Vision and functionality was verified using the Modelsim
- Final physical design was generated using the IC Compiler.
Modern processors are faster than memory
So Processors may waste time for accessing memory
Its purpose is to make the main memory appear to the processor to be much faster than it actually is
- Defined the specifications and designed an architecture of the MSDAP chip that performs convolution of two signals in least possible area & power.
- Implemented a RTL model of the MSDAP chip which consists of a Controller, ALU, Memories and Serial communication Unit.
- Synthesized the design in Synopsys Design Vision and functionality was verified using the Modelsim
- Final physical design was generated using the IC Compiler.
Implementation of High Reliable 6T SRAM Cell Designiosrjce
Memory can be formed with the integration of large number of basic storing element called cells.
SRAM cell is one of the basic storing unit of volatile semiconductor memory that stores binary logic '1' or '0' bit.
Modified read and write circuits were proposed in this paper to address incorrect read and write operations in
conventional 6T SRAM cell design available in open literature. Design of a new highly reliable 6T SRAM cell
design is proposed with reliable read, write operations and negative bit line voltage (NBLV). Simulations are
carried out using MENTOR GRAPHICS
in this ppt a types of BUS and bus arbitration have been explained with the help of providing some practical example. that make easy of the students to understand.
IOSR Journal of Electronics and Communication Engineering(IOSR-JECE) is an open access international journal that provides rapid publication (within a month) of articles in all areas of electronics and communication engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in electronics and communication engineering. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
Cache Design for an Alpha MicroprocessorBharat Biyani
Fine tuned the cache hierarchy of an Alpha microprocessor for three individual benchmarks namely GCC,ANAGRAM and GO by modifying various cache design parameters like cache levels, cache types ( in case of more than one level of cache), sizes, associativity, block sizes and block replacement policy. compared the performance of individual benchmarks for different configurations based on CPI and COST function.
AFFECT OF PARALLEL COMPUTING ON MULTICORE PROCESSORScscpconf
Our main aim of research is to find the limit of Amdahl's Law for multicore processors, to make number of cores giving more efficiency to overall architecture of the CMP(Chip Multi
Processor a.k.a. Multicore Processor). As it is expected this limit will be in the architecture of Multicore Processor, or in the programming. We surveyed the architecture of the Multicore
processors of various chip manufacturers namely INTEL™, AMD™, IBM™ etc., and the various techniques there followed in, for improving the performance of the Multicore
Processors. We conducted cluster experiments to find this limit. In this paper we propose an alternate design of Multicore processor based on the results of our cluster experiment.
Affect of parallel computing on multicore processorscsandit
Our main aim of research is to find the limit of Amdahl's Law for multicore processors, to make
number of cores giving more efficiency to overall architecture of the CMP(Chip Multi
Processor a.k.a. Multicore Processor). As it is expected this limit will be in the architecture of
Multicore Processor, or in the programming. We surveyed the architecture of the Multicore
processors of various chip manufacturers namely INTEL™, AMD™, IBM™ etc., and the
various techniques there followed in, for improving the performance of the Multicore
Processors.
We conducted cluster experiments to find this limit. In this paper we propose an alternate design
of Multicore processor based on the results of our cluster experiment.
Implementation of High Reliable 6T SRAM Cell Designiosrjce
Memory can be formed with the integration of large number of basic storing element called cells.
SRAM cell is one of the basic storing unit of volatile semiconductor memory that stores binary logic '1' or '0' bit.
Modified read and write circuits were proposed in this paper to address incorrect read and write operations in
conventional 6T SRAM cell design available in open literature. Design of a new highly reliable 6T SRAM cell
design is proposed with reliable read, write operations and negative bit line voltage (NBLV). Simulations are
carried out using MENTOR GRAPHICS
in this ppt a types of BUS and bus arbitration have been explained with the help of providing some practical example. that make easy of the students to understand.
IOSR Journal of Electronics and Communication Engineering(IOSR-JECE) is an open access international journal that provides rapid publication (within a month) of articles in all areas of electronics and communication engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in electronics and communication engineering. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
Cache Design for an Alpha MicroprocessorBharat Biyani
Fine tuned the cache hierarchy of an Alpha microprocessor for three individual benchmarks namely GCC,ANAGRAM and GO by modifying various cache design parameters like cache levels, cache types ( in case of more than one level of cache), sizes, associativity, block sizes and block replacement policy. compared the performance of individual benchmarks for different configurations based on CPI and COST function.
AFFECT OF PARALLEL COMPUTING ON MULTICORE PROCESSORScscpconf
Our main aim of research is to find the limit of Amdahl's Law for multicore processors, to make number of cores giving more efficiency to overall architecture of the CMP(Chip Multi
Processor a.k.a. Multicore Processor). As it is expected this limit will be in the architecture of Multicore Processor, or in the programming. We surveyed the architecture of the Multicore
processors of various chip manufacturers namely INTEL™, AMD™, IBM™ etc., and the various techniques there followed in, for improving the performance of the Multicore
Processors. We conducted cluster experiments to find this limit. In this paper we propose an alternate design of Multicore processor based on the results of our cluster experiment.
Affect of parallel computing on multicore processorscsandit
Our main aim of research is to find the limit of Amdahl's Law for multicore processors, to make
number of cores giving more efficiency to overall architecture of the CMP(Chip Multi
Processor a.k.a. Multicore Processor). As it is expected this limit will be in the architecture of
Multicore Processor, or in the programming. We surveyed the architecture of the Multicore
processors of various chip manufacturers namely INTEL™, AMD™, IBM™ etc., and the
various techniques there followed in, for improving the performance of the Multicore
Processors.
We conducted cluster experiments to find this limit. In this paper we propose an alternate design
of Multicore processor based on the results of our cluster experiment.
Paper describes optimization of bandwidth using dynamic creation and deletion of MPLS LSPs all managed by the router.
Builds on a unique concept to automatically manage and elastically grow and contract LSPs
Implementation of coarse-grain coherence tracking support in ring-based multi...ed271828
As the number of processors in multiprocessor system-on-chip devices continues to increase, the complexity required for full cache coherence support is often unwarranted for application-specific designs. Bus-based interconnects are no longer suitable for larger-scale systems, and the logic and storage overhead associated with the use of a complex packet-switched network and directory-based cache coherence may be undesirable in single-chip systems. Unidirectional rings are a suitable alternative because they offer many properties favorable to both on-chip implementation and to supporting cache coherence. Reducing the overhead of cache coherence traffic is, however, a concern for these systems. This thesis adapts two filter structures that are based on principles of coarse-grained coherence tracking, and applies them to a ring-based multiprocessor. The first structure tracks the total number of blocks of remote data cached by all processors in a node for a set of regions, where a region is a large area of memory referenced by the upper bits of an address. The second structure records regions of local data whose contents are not cached by any remote node. When used together to filter incoming or outgoing requests, these structures reduce the extent of coherence traffic and limit the transmission of coherent requests to the necessary parts of the system. A complete single-chip multiprocessor system that includes the proposed filters is designed and implemented in programmable logic for this thesis. The system is composed of nodes of bus-based multiprocessors, and each node includes a common memory, two or more pipelined 32-bit processors with coherent data caches, a split-transaction bus with separate lines for requests and responses, and an interface for the system-level ring interconnect. Two coarse-grained filters are attached to each node to reduce the impact of coherence traffic on the system. Cache coherence within the node is enforced through bus snooping, while coherence across the interconnect is supported by a reduced-complexity ring snooping protocol. Main memory is globally shared and is physically distributed among the nodes. Results are presented to highlight the system's key implementation points. Synthesis results are presented in order to evaluate hardware overhead, and operational results are shown to demonstrate the functionality of the multiprocessor system and of the filter structures.
#VirtualDesignMaster 3 Challenge 3 – James Brownvdmchallenge
While things on Mars have been going well, since we now have multiple options for our infrastructure, the fact remains that we are working on the colonization of a foreign planet.
Efficient Data Center Virtualization with QLogic 10GbE Solutions from HPJone Smith
QLogic 10GbE network solutions from HP delivers significant operational savings, high performance, reduced management complexity and improved scalability for virtualized data center deployments.
This project is concerned with the
design of SoC for detecting and correcting the error which may occur in the memory unit due to
radiation in LEO (Lower Earth Orbit) and due to stuck-at faults in memory unit in space station.
The error free data is feed to the predestined processor using the serial communication protocol
(UART) and perform its function specified in the data input which is sent from the ground station.
Presentation:
Time synchronization is one of the key imperatives of communications infrastructure. Real time persistence and near real time data processing are becoming essential to serve enhanced user experience in many industries. In this presentation, Dhiman Chowdhury will present sync plane design constructs for time aware non-deterministic networks across industry verticals.
Note: This presenation was shared at Open Compute Project (OCP) Time Appliance Project (TAP).
About Dhiman:
Dhiman Deb Chowdhury manages Product Management and Strategic Marketing for Protempis (formerly Trimble’s Time and Frequency division). Prior to joining Trimble, Dhiman served as vice President of Product Marketing redefining edge networking and open networking and expanding IPI global presence. At Delta Electronics, Dhiman was instrumental to whitebox products and technology venture “Agema System''. He advocated open networking, network cloudification and whitebox solutions for different industry verticals as a thought leader. In this role, Dhiman oversaw the technology strategy and development of Agema open networking product solutions. Prior to joining Delta Electronics, Inc., Dhiman worked as Director of Technical Program (R&D) at Allied Telesis, Inc where defined and developed technology strategy, products and services for enterprise and service providers networks. In 2004, he spearheaded the development of Industry’s first residential VoIP gateway at Netgear where he started service provider product lines. Prior to this, he was a member of Nortel’s technology leadership team working as a principal architect to define protocol, product and technology. At Nortel, Dhiman participated in the development of Industry’s first hybrid VoIP Routing Systems.
Dhiman has authored several technology books and written many scholarly articles. His recent publication “Nextgen Network Synchronization” provides a comprehensive overview of sync plane design for various network infrastructure and applications across industry verticals. Subsequently, some of his technology books on Unified and high-speed internetworking are continued to be reference handbooks for undergraduate studies globally. Dhiman studied Doctor of Business Administration (DBA) at The Robert Gordon University (RGU) and MBA at University of Liverpool. Dhiman is an avid blogger on technology and a Philanthropist.
Precise time synchronization is critical for 4G and 5G networks whether it is legacy deployment, 5G OpenRAN, Cloud Native 5G or Enterprise 5G deployments utilizing midband 5G spectrum, e.g. CBRS.
The Presentation goes over different network scenarios and present precise synchronization solutions for each.
Synchronization is essential for fusion of vision and sensors from machine vision to Autonomous vehicle. For the latter, time sync must be within certain error budget. Please view this infographics for more details.
The fifth generation (5G) technologies ushering in a new era of digital transformation across industries. With the promise of extreme bandwidth ( nearly 100 times faster than 4G),
ultra-low latency, high levels of security and reliability, 5G holds the promise to transform industries in ways we’re just
beginning to comprehend. The 5G technologies will change the way we connect, consume information and work. More importantly, it brings new capabilities to businesses, enabling them to deliver ground breaking solutions that reach across societies. This whitepaper provides a brief discussion on 5G technologies and importance of precise synchronization to enable 5G technologies for business transformation.
Time is everywhere but it's implementation in #5G is not easy. Unlike #4G, #TDD is more common in 5G especially in mid-bands [ #3.5Ghz (CBRS) and #Sub6Ghz ] to higher bands (as in mmWave) spectrums and also in spectrum overlays. TDD provides #spectrum efficiency but requires precision time synchronization.
Read this article to learn more about 5G synchronization challenges and how to address it.
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.
World's First Disaggregated 5G-Ready Mobile backhaul SolutionDhiman Chowdhury
SKY Brazil is one of the largest Pay TV provider in Brazil with 5Million+ subscribers created world’s first disaggregated 5G-ready Fixed Wireless Access (FWA) network using IPInfusion’s disaggregated PE Solution to serve 35K broadband subscribers.
This infographics provides a a glimpse of how the deployment was done.
IP Infusion Application Note for 4G LTE Fixed Wireless AccessDhiman Chowdhury
SKY Brazil is one of the largest Pay TV provider in Brazil with 5Million+ subscribers created world’s first disaggregated 5G-ready Fixed Wireless Access (FWA) network using IPInfusion’s disaggregated Cell Site Gateway Solution to serve 35K broadband subscribers.
Learn how the deployment was done, read this application note to know more about the usecase and OcNOS configurations.
There is an ominous rumbling in the internet about 768K day, some even termed it internet doomsday others called it “Y2K” of internet. The fear is justified given the experience of wide spread internet outage during 512K day when internet BGP table size exceeded 512,000 routes. The 512K day caused havoc and many routers simply exhausted of TCAM (Ternary content-addressable memory) size and were unable to process certain routes leaving parts of internet unreachable. The same issue seems possible this year again when internet routes exceeds 768K routes.
IP Infusion worked with the London Internet Exchange (LINX) to create world's first disaggregated network for transport peering. The network is essentially a extended DCN (Data Center Network) with ip routing as underlay and VxLAN as overlay. The EVPN control plane effectively managing over transport from end to end.
The fundamental architecture, configuration and protocol suits that build such network is now available in a micro pod. IP Infusion branded such extensible micro-pod as “DC-BOX” or data center network in a bundle. The DC-BOX accelerates the move to next generation data center architectures with open networking switches. This pre-configured ready-to-deploy bundle delivers carrier-grade performance with the benefits of disaggregation. This presentation depicts various use cases for the DC-BOX in telecom, data center, Internet Exchange Point, Cloud Services and service providers networks.
IPI DC-BOX, a ready-to-deploy data center in a
bundle, uses OcNOS™ carrier-grade network
operating system to build next generation data
centers with the benefits of disaggregation.
Targeted DC Architectures:
1. Leaf and Spine
2. CLOS Fabric
3. Mobile Edge Computing
4. Internet Exchange Point (IXP)
World's First Dsiaggregated Networks for Internet Exchange Point (IXP)Dhiman Chowdhury
This infrographics summarizes deployment of whitebox powered by IPInfusion's OcNOS in the World's First Dsiaggregated Network for Internet Exchange Point (IXP). The London Internet Exchange (LINX) build this completely disaggregated network using EVPN technology from IPInfusion. This inforgraphics is prepared by Dhiman Deb Chowdhury.
Interoperability Showcase: Eantc tested IPInfusion software with 21 other ven...Dhiman Chowdhury
EANTC conducted interoperability tests for 21 vendors including ipinfusion, cisco, juniper and Ericsson etc for MPLS, segment routing and EVPN level of interoprabilities. The test shows IPInfusion's OcNOS interworking with major networking software and/or equipment vendors.
Intel and IP Infusion Deliver Deterministic NFV PerformanceDhiman Chowdhury
IP Infusion's VirNOS virtual networking solutions combines Intel performance technology with proven control plane to offer stable performance. VirNOS is also integrated with the Data Plane Development Kit (DPDK), a library of drivers for fast packet processing. DPDK is a Linux Foundation Project for which Intel is among the leading members.
The VirNOS data plane is extremely modular, featuring flexible NFV infrastructure for both control plane (NFVI-C) and for the
user plane (NFVI-U). The NFVI-U offers hardware abstraction and packet handling services, with plug-in modules for SDKs and different network cores. On top of that, IP Infusion has introduced VNFs as a Service, allowing the user to customize IP/MPLS switching and routing services as well as VxLAN and NvGRE services. For SDN environments, VirNOS also features OpenFlow switching alongside the IP capabilities via an OpenFlow Agent and connectivity to a centralized OpenFlow controller.
The Intelligent Mesh: Bringing together converging forces to enable NextGen I...Dhiman Chowdhury
As the backbone of the digital revolution, Information Communication Technology (ICT) infrastructure is evolving from disparate systems towards more integrated, efficient and intelligent solutions. This technological advent blurring the line between physical and digital world: from network systems to digital endpoint for physical interconnect, intelligent mesh is shaping the world bringing new possibilities while empowering us with great understanding of our physical world.
In this presentation, Dhiman Deb Chowdhury from Delta Electronics will discuss the end to end ICT solutions depicting trends and transformations educating audience on various infrastructures: data center, telecom and enterprise.
The presentation will be furnished in two parts: first, trends of intelligent digital interconnect will be discussed with emphasis on data center, telecom and enterprise infrastructures sharing experience of serving global customers and helping audience to realize the potential for their own ICT undertakings. Secondly, the presentation will bring together converging forces from networks to discrete endpoints sharing topologies from power distribution to network systems depicting customers the choices of systems and technologies available for their ICT infrastructure transformation. While Part one of this presentation is educational in nature, Part II will be more vendor specific which illustrates Delta’s firm commitment to drive technology in such direction assisting ICT infrastructure professionals to make the right decision and maximize business value for the long term.
Ethernet technology made significant progress in recent years ushering a new era of terabit transport. It has now achieved 400GbE per link speed and leaping towards 800GbE. Such trend will shape the future of networks allowing hyperscale data centers, cloud and service providers to offer more service and less worry on bandwidth. It would be interesting to know what future holds. Read this article to learn more about 400GbE and the possibilities it brings.
As the backbone of the digital revolution, Information Communication Technology (ICT) infrastructure is evolving from disparate systems towards more integrated, open, efficient and intelligent solutions. While this advancement is to some extent piecemeal given the limitations of various systems and lack of open community initiatives at all level, we at Delta are committed and working towards integrated, open and efficient Smart ICT infrastructure systems bringing best of the breed technologies to help customers maximize their business values.
In this presentation, Dhiman Chowdhury from Delta will discuss the end to end ICT infrastructure topologies from power distribution to network systems depicting customers the choices of systems and technologies available for their ICT infrastructure transformation. While this presentation includes forward-looking statements from vendor-specific solutions, it is also our firm commitment to drive technology in such direction and will assist ICT infrastructure professionals to make the right decision and maximize business value for the long term.
Wireless-fiber convergence: Ethernet at Fronthaul creating new possibilities ...Dhiman Chowdhury
Front-haul Mobile Networks is undergoing rapid changes that separates RF block from baseband unit making it possible for long distance deployment of baseband units. This is just the prelude for more robust transformation to occur. Once such possibility is transforming fronthaul with Ethernet paving the way for higher bandwidth and easier adoption of 5G.
This article discusses changes in RRH to BBU connectivity technology known as D-ROF and discusses ruse of Ethernet in D-ROF and possibility of using whitebox for front-haul mobile networks.
Cloud computing is increasingly becoming critical part of IT solutions. This presentation series is intended to provide guidance for the selection, integration and implementation of private cloud. In part-I, readership will learn essentials about private cloud and the presentation will serve as the prelude towards extensive learning about “private cloud” including strategy, planning/process, testing and deployment of the private cloud product.
I hope this presentation series will provide adequate information on “private cloud” empowering IT professionals and CIOs to make better and educated decisions.
Balancing continued economic progress and conservation of our biosphere is the challenge of our time. It’s a dilemma of the anthropocene epoch. Without corporation to the mix, our endeavor is fruitless. Increasingly, corporations have adopted prescriptive, piecemeal and mechanistic environmental management techniques as a response to sustainability discourse. However, in light of the complexity, uncertainty, ambiguity and dynamic nature inherent in the sustainability challenge, at some bifurcation point in the organizational change process, these prescriptive and piecemeal solutions may not adequately account for the emerging multiple levels of environmental, social and financial conflict. A paradigm shift is thus essential: a behavioral change is thus called for. This presentation provides an explanation to the issue and a formulation to tackle challenge head-on: a behavioral competence that builds viable, equitable and responsible corporation resolving issues of sustainable business and sustainable world.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
4. 4
Solution Guide
Chapter 1
Data Center Overview
Network Automation provides IT administrators and network operators significant benefits. This solution guide
describes an approach to build data centers using Layer3 BGP routing protocol.
It also summarizes on some design philosophies for data center and why E-BGP is better suited.
■■ Large-scale data center requirements
■■ Large-scale data center topologies
■■ Large-scale data center routing
■■ EBGP-routed large-scale Clos topology-based data center
Large-Scale Data Center Requirements
The design of large-scale data centers is driven by operational simplicity and network stability. Operational
simplicity and network stability ensures easier manageability and therefore reduced operational expenses.
From the network design aspect, the requirements are:
■■ Ability to accommodate the variable-application bandwidth and strict latency requirements.
■■ Ability to handle the increased east-west (server-to-server) traffic within the data center due to massive
data replication between clusters and virtual machine migrations.
■■ Traffic-Engineering with application load balancing. The network infrastructure should itself perform
controlled per-hop traffic engineering.
■■ Minimize CAPEX and incorporate vendor diversity by using a simple, interoperable routing protocol with a
minimal set of features.
■■ A design to minimize OPEX by keeping the failure domain at the lowest level in the network hierarchy.
Large-Scale Data Center Topologies
A traditional tree-based (upside down) topology with a three-layer hierarchy of core, aggregation and access
layer can be used in a data center design. This approach is suited if the majority of the traffic is entering
and leaving (north-south) the data center. An increase in bandwidth requirements then can be addressed by
upgrading the device line cards or port density. However with the current trend of increasing server-to-server
(east-west) traffic, scaling these networks horizontally is expensive or impossible at times.
A Clos network (leaf and spine) is a horizontally scalable topology where every leaf node is connected to
every other spine. The topology can be extended to different stages for scaling. Clos networks are fully non-
blocking and load balancing is inherent in the topology itself as all available paths are ECMP. Clos networks
are ideal for the current requirements of a large-scale data center.
Large-Scale Data Center Routing
Layer 2-only routing was used in a traditional tree-based data center topology. Traditional layer-2 protocols
such as STP do not give bi-sectional bandwidth, whereas recent developments such as TRILL, SPB have
selected vendor support.
However, a hybrid of layer 2 /layer 3 can be used to limit the size of failure domain and scale up the data
center. Layer 3 routing can be used in tier 1 (core) and layer 2 in tier 3 (access). Tier 2 can be based on either
layer 2 or layer 3. A hybrid model has the advantage of seamless Virtual Machine mobility and requires less
IP subnets for the data center. Although this design can scale-up, it is difficult and complex to manage the
different protocols.
5. 5
Solution Guide
A layer 3 only design simplifies the network and improves network stability and scalability, as well as
localizing the failure domain (confined to the L2 broadcast domain). Seamless virtual mobility can be achieved
in a L3 only based data center by using L2 overlay networks. From experiment and analysis, External BGP
(EBGP) is considered ideal compared to IGPs due to the following [See Reference]:
■■ Less complex protocol, simple state machine
■■ Information flooding overhead is less, no frequent updates unlike IGPs
■■ Network failure recovery is very fast. Although BGP convergence is slower than IGP, in a Clos topology
with ECMP links, the failure is masked as soon as an alternate path is found.
■■ Failure domain is minimized in a Clos topology with EBGP. Some of the failures are local/hidden/not
propagated if the failed link was not selected/advertised as the best path among the ECMP paths by the
BGP speaker. The failures, where all devices have to withdraw some prefixes or update the ECMP groups
in the FIB, are very limited and in those failures the failed link/node does not impact the re-convergence
process.
■■ Administrator can define the application traffic path. BGP provides services like prefix distribution, prefix
filtering, traffic engineering, traffic tagging, and multi-vendor stability better than other IGPs.
■■ Easier to troubleshoot.
EBGP-Routed CLOS Topology-Based Data Center
EBGP-routed CLOS topology is considered the best choice for laying the IP fabric in a data center because
of the horizontal scalability feature of Clos topology and the ease of use and services provided by EBGP
especially prefix-filtering, prefix distribution, and traffic engineering which are required extensively in a
data center.
Configuration Guidelines
Configuration guidelines for laying IP fabric using EBGP efficiently are as follows:
■■ Run all EBGP sessions over single-hop point-to-point links.
■■ Use private Autonomous System Numbers (ASNs) (64512-65534) to avoid ASN conflicts.
■■ Give all tier 1 (core) devices a single ASN.
■■ Give all tier 2 devices in the same cluster the same unique ASN. A cluster or pod is a group of tier 2 (spine
switches) + tier 3 switches (ToR/leaf) + servers.
■■ Give every tier 3 (ToR) device in a cluster a unique ASN.
■■ Reuse tier-3 ASNs across clusters. Configure tier-3 devices with the BGP “allowas-in” feature to allow route
learning of prefixes from the same ASNs in other clusters.
■■ Announce server subnets on tier-3 devices via BGP without using route summarization on tier-2 and tier-1
devices.
■■ Use edge clusters (pods) for external connectivity. Each edge cluster consists of border routers (tier-2) and WAN
routers (tier-3). Give each WAN router a unique public ASN to connect the data center to the external world.
■■ For border routers, remove private ASNs before sending the information to WAN routers by configuring
border routers with the “remove-private-AS” BGP feature.
■■ To relax the BGP ECMP criteria for AS paths, configure BGP “as-path multipath-relax” on all routers/
switches. This way, an equal cost path with a different AS PATH, but the same AS PATH length is also
considered an equal cost path (ECMP).
6. 6
Solution Guide
■■ For faster failure detection, configure the BGP session with BFD.
■■ To avoid recurring BPG update/selection for a single failure through all peers or BGP update message
dispersion on a particular speaker, use BGP update groups. The BGP update group feature processes an
update once and sends it to a group of neighbors that share a common outbound policy. The BGP RIB is
scanned every time for each peer to apply the outbound filter.
■■ To avoid micro routing loops, configure tier-2 and tier-1 with static discard or null routes rather than a default
route. Routing loops can happen when a tier-2 device has lost all its learned prefixes, but has a default
route to a tier-1 device and that tier-1 device still has a route back to the tier-2 device.
EBGP Data Center Design using OcNOS
Figure-1 shows a minimal representation that encompasses all the elements in a layer 3 data center.
The number of ECMPs in the data center is equal to the number of cores (tier-1 switches).
Figure 1. IP fabric using EBGP
TOR 1 TOR 2
Spine Tier 2
Cluster/Pod
TOR 3 TOR 1 TOR 2 TOR 3
Internet
WAN Routers
External Cluster/Pod
Border Router
Core Tier 1
Tier 3
7. 7
Solution Guide
Figure 2 shows the Autonomous System Number (ASN) allocation scheme used in the data center. The WAN
routers are assigned a public ASN, which connects the data center to external world. The tier-3 ASNs per
ToR are reused across the clusters.
Figure 2: ASN allocation in an EBGP-based data center
TOR 1 TOR 2
ASN 64601 ASN 64602
TOR 3 TOR 1 TOR 2 TOR 3
Internet
ASN 101ASN 100
ASV 64603
External Cluster
ASN 65534
R11 R12 R13 R14
Cluster 1 Cluster 2
ASN65500
ASN65501
ASN65502
ASN65500
ASN65501
ASN65502
8. 8
Solution Guide
Chapter 2
Configuration
ToR (Leaf node)
Command Purpose
Step 1 (config)#interface xe1 Enter interface mode.
Step 2 (config-if)#ip address 32.1.0.3/24 Configure ip address on the Interface
Step 3 (config-if)#exit Exit interface mode.
Step 4 (config)#interface xe2 Enter interface mode.
Step 5 (config-if)#exit Exit interface mode.
Step 6 (config)#router bgp 65500 Configure the EBGP routing process with private ASN
Step 7 (config-router)#max-paths ebgp 8 Exit interface mode.
Step 8 (config-router)#neighbor 32.1.0.2
remote-as 64601
Configure maximum EBGP ECMP that can be installed in
BGP.
Step 9 (config-router)#neighbor 32.1.0.2
fall-over bfd
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote private ASN
Step 10 (config-router)#neighbor 32.1.0.2
allowas-in
Configure BFD for the BGP session for faster failure
detection.
Step 11 (config-router)#neighbor 32.2.0.2
remote-as 64601
Configure “allowas-in” for the neighbor to accept routes
with same ASN learned over this neighbor
Step 12 (config-router)#neighbor 32.2.0.2
fall-over bfd
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote private ASN
Step 13 (config-router)#neighbor 32.2.0.2
allowas-in
Configure BFD for the BGP session for faster failure
detection.
Step 14 (config-router)#exit Configure “allowas-in” for the neighbor to accept routes
with same ASN learned over this neighbor
Step 15 (config-router)#exit Exit Router mode.
Tier-2 (Spine node)
Command Purpose
Configure the interfaces
Step 1 (config)#interface xe1 Enter interface mode.
Step 2 (config-if)#ip address 32.1.0.2/24 Configure ip address on the interface
Step 3 (config-if)#exit Exit interface mode.
Step 4 (config)#interface xe46 Enter interface mode.
Step 5 (config-if)#ip address 32.3.0.2/24 Configure an IP address on the interface
Step 6 (config)#interface xe47 Enter interface mode.
Step 7 (config-if)#ip address 32.4.0.2/24 Configure an IP address on the interface
Step 8 (config)#interface xe48 Enter interface mode.
Step 9 (config-if)#ip address 21.1.0.2/24 Configure an IP address on the interface
Step 10 (config)#interface xe46 Enter interface mode.
Step 11 (config-if)#ip address 21.2.0.2/24 Configure an IP address on the interface
Step 12 (config)#router bgp 64601 Configure the eBGP routing process with private ASN
9. 9
Solution Guide
Command Purpose
Configure BGP on the router
Step 13 (config-router)#bgp bestpath as-path
multipath-relax
Configure “as-path multipath-relax” to relax the AS-PATH
exact match (if AS-PATH length are same) criteria for BGP
ECMP
Step 14 (config-router)#max-paths ebgp 8 Configure maximum EBGP ECMP that can be installed
in BGP.
Step 15 (config-router)#neighbor 32.1.0.3
remote-as 65000
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 16 (config-router)#neighbor 32.1.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 17 (config-router)#neighbor 32.3.0.3
remote-as 65001
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 18 (config-router)#neighbor 32.3.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 19 (config-router)#neighbor 32.4.0.3
remote-as 65002
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 20 (config-router)#neighbor 32.1.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 21 (config-router)#neighbor 21.1.0.1
remote-as 65534
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 22 (config-router)#neighbor 21.1.0.1
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 23 (config-router)#neighbor 21.2.0.1
remote-as 65534
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 24 (config-router)#neighbor 21.2.0.1
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 25 (config-router)#exit Exit Router mode.
Tier-2 (Spine node) cont.
10. 10
Solution Guide
Tier-3 (Core node)
Command Purpose
Configure the interfaces
Step 1 (config)#interface xe1 Enter interface mode.
Step 2 (config-if)#ip address 21.1.0.1/24 Configure ip address on the interface
Step 3 (config-if)#exit Exit interface mode.
Step 4 (config)#interface xe46 Enter interface mode.
Step 5 (config-if)#ip address 21.5.0.1/24 Configure an IP address on the interface
Step 6 (config)#interface xe49 Enter interface mode.
Step 7 (config-if)#ip address 41.1.0.1/24 Configure an IP address on the interface
Step 8 (config)#interface xe50 Enter interface mode.
Step 9 (config-if)#ip address 41.5.0.1/24 Configure an IP address on the interface
Configure BGP on the router
Step 10 (config)#router bgp 65534 Configure the eBGP routing process with private ASN
Step 11 (config-router)#bgp bestpath
as-path multipath-relax
Configure “as-path multipath-relax” to relax the AS-PATH
exact match (if AS-PATH length are same) criteria for
BGP ECMP
Step 12 (config-router)#max-paths ebgp 8 Configure maximum EBGP ECMP that can be installed
in BGP.
Step 13 (config-router)#neighbor 21.1.0.2
remote-as 64601
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 14 (config-router)#neighbor 21.1.0.2
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 15 (config-router)#neighbor 21.5.0.3
remote-as 64602
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 16 (config-router)#neighbor 21.5.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 17 (config-router)#neighbor 41.1.0.3
remote-as 64603
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 18 (config-router)#neighbor 41.1.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 19 (config-router)#neighbor 41.5.0.3
remote-as 64603
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 20 (config-router)#neighbor 41.5.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 21 (config-router)#exit Exit BGP mode
11. 11
Solution Guide
Command Purpose
Configure the interfaces
Step 1 (config)#interface xe1 Enter interface mode.
Step 2 (config-if)#ip address 41.1.0.2/24 Configure an IP address on the interface
Step 3 (config-if)#exit Exit interface mode.
Step 4 (config)#interface xe46 Enter interface mode.
Step 5 (config-if)#ip address 41.2.0.2/24 Configure an IP address on the interface
Step 6 (config)#interface xe47 Enter interface mode.
Step 7 (config-if)#ip address 41.3.0.2/24 Configure an IP address on the interface
Step 8 (config)#interface xe48 Enter interface mode.
Step 9 (config-if)#ip address 41.4.0.2/24 Configure an IP address on the interface
Step 10 (config)#interface xe49 Enter interface mode.
Step 11 (config-if)#ip address 51.1.0.2/24 Configure an IP address on the interface
Step 12 (config)#interface xe50 Enter interface mode.
Step 13 (config-if)#ip address 51.3.0.2/24 Configure an IP address on the interface
Step 14 (config)#router bgp 64603 Configure the eBGP routing process with private ASN
Step 15 (config-router)#bgp bestpath
as-path multipath-relax
Configure “as-path multipath-relax” to relax the AS-PATH
exact match (if AS-PATH length are same) criteria for
BGP ECMP
Step 16 (config-router)#max-paths ebgp 8 Configure maximum EBGP ECMP that can be installed in BGP.
Step 17 (config-router)#neighbor 41.1.0.1
remote-as 65534
Configure the EBGP neighbor over the connected interface
using the neighbor IP and remote ASN
Step 18 (config-router)#neighbor 41.1.0.1
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 19 (config-router)#neighbor 41.2.0.1
remote-as 65534
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 20 (config-router)#neighbor 41.2.0.1
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 21 (config-router)#neighbor 41.3.0.1
remote-as 65534
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 22 (config-router)#neighbor 41.3.0.1
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 23 (config-router)#neighbor 41.4.0.1
remote-as 65534
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 24 (config-router)#neighbor 41.4.0.1
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 25 (config-router)#neighbor 51.1.0.3
remote-as 100
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Configure BGP on the router
Step 26 (config-router)#neighbor 51.1.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 27 (config-router)#neighbor 51.1.0.3
remove-private-AS
Configure “remove –private-AS” to remove the private ASNs
for the routes advertised to this neighbor.
Step 28 (config-router)#neighbor 51.3.0.3
remote-as 101
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Tier 2 (Border router)
12. 12
Solution Guide
Command Purpose
Configure BGP on the router
Step 29 (config-router)#neighbor 51.3.0.3
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 30 (config-router)#neighbor 51.3.0.3
remove-private-AS
Configure “remove –private-AS” to remove the private ASNs
for the routes advertised to this neighbor.
Step 31 (config-router)#exit Exit BGP mode
Tier-3 (WAN router)
This is a partial list and does not contain the Internet configuration.
Command Purpose
Configure the interfaces
Step 1 (config)#interface xe1 Enter interface mode.
Step 2 (config-if)#ip address 51.1.0.3/24 Configure an IP address on the interface
Step 3 (config-if)#exit Exit interface mode.
Step 4 (config)#interface xe46 Enter interface mode.
Step 5 (config-if)#ip address 51.2.0.3/24 Configure an IP address on the interface
Configure BGP on the router
Step 6 (config)#router bgp 100 Configure the eBGP routing process with public ASN
Step 7 (config-router)#max-paths ebgp 8 Configure maximum EBGP ECMP that can be installed in
BGP.
Step 8 (config-router)#neighbor 51.1.0.2
remote-as 64603
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 9 (config-router)#neighbor 51.1.0.2
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 10 (config-router)#neighbor 51.3.0.2
remote-as 64603
Configure the EBGP neighbor over the connected
interface using the neighbor IP and remote ASN
Step 11 (config-router)#neighbor 51.3.0.2
fall-over bfd
Configure BFD for the BGP session for faster failure
detection.
Step 12 (config-router)#exit Exit BGP mode
Other Configurations
You must repeat similar configurations for all ToR, spine, core, border, and WAN devices as well.
Tier 2 (Border router) Cont.
13. 13
Solution Guide
Validation
Use the show ip bgp command to validate the output at each node.
Consider the following case: for application load balancing and high availability/reliability, two similar
application servers can be placed at two clusters. For users accessing the application server through the
Internet, the access to the server is load balanced and failure of one of the application servers does not
impact the accessibility. The following is the output at various nodes for a subnet, such as:
■■ 70.70.70.1 (application server) at ToR1 in cluster 1 and cluster 2
■■ 80.80.80.1 at ToR 1 cluster 1
■■ 90.90.90.1 at ToR 1 cluster 2
ToR 1 Cluster 1
ToR 1 Cluster 2
15. 15
Solution Guide
WAN Router WR1 External Cluster
Conclusion
OcNOS with EBGP routing is a highly scalable, simple and flexible way of laying IP fabric in a data center.
The data center can be easily scaled for:
■■ Higher computing needs by adding more clusters.
■■ Higher performance and redundancy by adding more cores
■■ Higher uplink speeds by adding more external/edge clusters.
References
Use of BGP for routing in large scale data centers:
https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-09
16. 16
Solution Guide
Appendix A: Configuring the Data
Center through NetConf
This appendix shows how to configure a data center through NetConf. This section contains XML payloads
which can be used by any NetConf client to send configurations to OcNOS devices.
The configurations below in XML are communicated via RPC messages from the NetConf client to the
NetConf server.
This document uses the yang-cli which is part of open source OpenYumaMaster which and is preinstalled on
a ZebM-enabled OcNOS ONIE package as a NetConf client.
Pre-requisite
Refer to Yangcli Operations section of the NetConf User Guide and perform these operations first:
1. Establish Connection
2. Load Modules
Once the above operations are complete, edit-config operation can be performed with XML payloads using
the command:
yangcli ocnos@Hostname> edit-config config=@/<path-to-xml-file>/<xml-file>.xml
Save the below xml payloads as an .xml file in any desired location. Make sure that each XML payload starts
with <vr xmlns=”<namespace>”> and ends with </vr>.
TOR (leaf node)
TOR.xml
This table shows the XML to configure an IP address:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/
ZebOS”>
namespace of the ZebOS module
<vrId>0</vrId> Vrid
<interface>
<ifName>xe49</ifName>
<ipAddr>50.52.1.1/24</ipAddr>
</interface>
<interface>
<ifName>ge2</ifName>
<ipAddr>50.54.1.1/24</ipAddr>
</interface>
Configure the interfaces which are connected to the
SPINE routers.
This payload configures the IP address of the
interfaces xe49 and ge2.
</vr> Close namespace for the ZebOS module
17. 17
Solution Guide
This is an example of the XML payload to be sourced in the yang CLI to configure an interface IP addresses:
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”>
<vrId>0</vrId>
<interface>
<ifName>xe49</ifName>
<ipAddr>50.52.1.1/24</ipAddr>
</interface>
<interface>
<ifName>ge2</ifName>
<ipAddr>50.54.1.1/24</ipAddr>
</interface>
</vr>
This table shows the XML to configure BGP attributes:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/
ZebOS”>
Namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<bgp>
<bgpAs>64602</bgpAs>
Open BGP tag.
Configure the BGP AS number.
<multipathRelax>1</multipathRelax>
<vrfName>default</vrfName>
Configure “as-path multipath-relax” to
relax the AS-PATH criteria for BGP ECMP
<multipath>
<bgpType>ebgp</bgpType>
<multipathType>
<multipathsNum>8</ multipathsNum>
</multipathType>
</multipath>
Configure maximum EBGP ECMP that can be
installed in BGP.
<bgpPeer>
<peerAddr>50.52.1.2</peerAddr>
<allowAsNum>3</allowAsNum>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>64902</peerAs>
</bgpPeer>
Configure BGP peer with AS 64902 and peer
address 50.52.1.2
Enable BFD for link failure detection
Configure “allowas” in for the neighbor to
accept routes with same ASN learned over this
neighbor
<bgpPeer>
<peerAddr>50.54.1.2</peerAddr>
<allowAsNum>3</allowAsNum>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>64902</peerAs>
</bgpPeer>
Configure BGP peer with AS 64902 and peer
address 50.54.1.2
Configure “allowas” in for the neighbor to
accept routes with same ASN learned over this
neighbor
Enable BFD for link failure detection.
<bgpRedistList>
<redistType>connected</redistType>
</bgpRedistList>
<bgpRedistList>
<redistType>ospf</redistType>
</bgpRedistList>
Redistribute the connected and OSPF routes
</bgp> Close BGP tag.
</vr> Close namespace for the ZebOS module
18. 18
Solution Guide
Tier-2 (spine node)
SPINE.xml
This table shows the XML to configure IP addresses:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<interface>
<ifName>xe49/1</ifName>
<ipAddr>50.52.1.2/24</ipAddr>
</interface>
<interface>
<ifName>xe49/2</ifName>
<ipAddr>52.31.1.1/24</ipAddr>
</interface>
Configure the interfaces which are connected
to the SPINE routers.
This payload configures the IP address of the
interfaces xe49/1 and xe49/2.
</vr> Close namespace for the ZebOS module
This table shows the XML to configure BGP attributes:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<bgp>
<bgpAs>64902</bgpAs>
Open BGP tag.
Configure the BGP AS number.
<multipathRelax>1</multipathRelax>
<vrfName>default</vrfName>
Configure “as-path multipath-relax” to relax the
AS-PATH criteria for BGP ECMP
<multipath>
<bgpType>ebgp</bgpType>
<multipathType>
<multipathsNum>8</multipathsNum>
</multipathType>
</multipath>
Configure maximum EBGP ECMP that can be
installed in BGP.
<bgpRedistList>
<redistType>connected</redistType>
</bgpRedistList>
Redistribute the connected routes
<bgpPeer>
<peerAddr>50.52.1.1</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>64601</peerAs>
</bgpPeer>
Configure BGP peer with AS 64602 and peer
address 50.52.1.1
Enable BFD for link failure detection.
<bgpPeer>
<peerAddr>52.31.1.2</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>65501</peerAs>
</bgpPeer>
Configure BGP peer with AS 65501 and peer
address 52.31.1.2
Enable BFD for link failure detection.
</bgp> Close BGP tag.
</vr> Close namespace for the ZebOS module
19. 19
Solution Guide
Tier-3 (core node)
CORE.xml
This table shows the XML to configure IP addresses:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<interface>
<ifName>xe1</ifName>
<linkStatus>1</linkStatus>
<ipLabel>NULL</ipLabel>
<ipAddr>52.31.1.2/24</ipAddr>
</interface>
<interface>
<ifName>ge8</ifName>
<linkStatus>0</linkStatus>
<ipLabel>NULL</ipLabel>
<ipAddr>31.22.1.1/24</ipAddr>
</interface>
Configure the interfaces that are connected to
the spine routers.
This payload configures the IP address of the
interfaces xe1 and ge8.
</vr> Close namespace for the ZebOS module
This table shows the XML to configure BGP attributes:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<bgp>
<bgpAs>65501</bgpAs>
Open BGP tag.
Configure the BGP AS number.
<multipathRelax>1</multipathRelax>
<vrfName>default</vrfName>
Configure “as-path multipath-relax” to relax
the AS-PATH criteria for BGP ECMP
<multipath>
<bgpType>ebgp</bgpType>
<multipathType>
<multipathsNum>8</multipathsNum>
</multipathType>
</multipath>
Configure maximum EBGP ECMP that can
be installed in BGP.
<bgpRedistList>
<redistType>connected</redistType>
</bgpRedistList>
Redistribute the connected routes
<bgpPeer>
<peerAddr>52.31.1.1</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>64902</peerAs>
</bgpPeer>
Configure BGP peer with AS 64902 and peer
address 52.31.1.1
Enable BFD for link failure detection.
<bgpPeer>
<peerAddr>31.22.1.2</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>65503</peerAs>
</bgpPeer>
Configure BGP peer with AS 65503 and peer
address 31.22.1.2
Enable BFD for link failure detection.
</bgp> Close BGP tag.
</vr> Close namespace for the ZebOS module
20. 20
Solution Guide
Tier-2 (Border Router)
This table shows the XML to configure IP addresses:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<interface>
<ifName>ge7</ifName>
<ipAddr>53.22.1.2/24</ipAddr>
</interface>
<interface>
<ifName>ge6</ifName>
<ipAddr>31.22.1.2/24</ipAddr>
</interface>
<interface>
<ifName>ge2</ifName>
<ipAddr>23.22.1.1/24</ipAddr>
</interface>
Configure the interfaces which are connected
to the SPINE routers.
This payload configures the IP address of the
interface ge7, ge6 and ge2.
</vr> Close namespace for the ZebOS module
This table shows the XML to configure BGP attributes:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<bgp>
<bgpAs>65503</bgpAs>
Open BGP tag
Configure the BGP AS number.
<multipathRelax>1</multipathRelax>
<vrfName>default</vrfName>
Configure “as-path multipath-relax” to relax
the AS-PATH criteria for BGP ECMP
<multipath>
<bgpType>ebgp</bgpType>
<multipathType>
<multipathsNum>8</multipathsNum>
</multipathType>
</multipath>
Configure maximum EBGP ECMP that can be
installed in BGP.
<bgpRedistList>
<redistType>connected</redistType>
</bgpRedistList>
Redistribute the connected routes
<bgpPeer>
<peerAddr>53.22.1.1</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>64902</peerAs>
</bgpPeer>
Configure BGP peer with AS 64902 and peer
address 52.31.1.1
Enable BFD for link failure detection.
<bgpPeer>
<peerAddr>31.22.1.2</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>65503</peerAs>
</bgpPeer>
Configure BGP peer with AS 65503 and peer
address 31.22.1.2
Enable BFD for link failure detection.
<bgpPeer>
<peerAddr>23.22.1.2</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>65502</peerAs>
<peerRemovePvtAs>1</peerRemovePvtAs>
</bgpPeer>
Configure BGP peer with AS 65502 and peer
address 23.22.1.2
Enable BFD for link failure detection.
Configure remove-private-as for 23.22.1.2 peer
</bgp> Close BGP tag.
</vr> Close namespace for the ZebOS module
21. 21
Solution Guide
Tier-3 (WAN Router) –Partial -Does Not Contain the Internet Configuration
This table shows the XML to configure an IP address:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<interface>
<ifName>ge1/1/1</ifName>
<ipAddr>22.23.1.2/24</ipAddr>
</interface>
Configure the interfaces that are connected to
the SPINE routers.
This payload configures the IP address of the
interface ge1/1/1.
</vr> Close namespace for the ZebOS module
This table shows the XML to configure BGP attributes:
XML Payload Description
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”> Enter namespace of the ZebOS module
<vrId>0</vrId> Enter Vrid
<bgp>
<bgpAs>65502</bgpAs>
Open BGP tag
Configure the BGP AS number.
<bgpRedistList>
<redistType>connected</redistType>
</bgpRedistList>
Redistribute the connected routes
<bgpPeer>
<peerAddr>22.23.1.1</peerAddr>
<bgpPeerBfd>1</bgpPeerBfd>
<peerAs>65503</peerAs>
</bgpPeer>
Configure BGP peer with AS 64902 and peer
address 52.31.1.1
Enable BFD for link failure detection.
</bgp> Close BGP tag.
</vr> Close namespace for the ZebOS module
Similar configurations must be repeated for all TORs, spines, cores, and border routers.
Appendix B: NetConf User Guide
This document describes managing OcNOS devices using NetConf.
This document is intended for network administrators and other engineering professionals who configure and
manage devices running OcNOS.
There are three different northbound applications in OcNOS (CLI , NetConf, and SNMP). All the northbound
applications are text-based, with each command usually associated to a specific task.
OcNOS NetConf supports transactions as described in Transactions.
22. 22
Solution Guide
NetConf Quick Start
The NetConf protocol defines a simple mechanism through which a network device can be managed,
configuration information can be retrieved, and new configuration data can be uploaded.
NetConf uses a simple RPC-based mechanism to communicate between a client and a server. The client can be
a script or application typically running as part of a network manager. The server is usually a network device.
A NetConf session is the logical connection between a network administrator or network configuration application
and a network device. A device must support at least one NetConf session and can support multiple sessions.
Global configuration attributes can be changed during any session and the effects are visible in all sessions. The
candidate and running and startup configuration are shared across all the sessions.
Note: A limited number of protocol modules are supported through NetConf. A detailed list is in the NetConf command reference.
NetConf Clients
You can use any NetConf client application to manage the device using Yang modules. These client
applications require a Yang module which you downlaod from:
https://github.com/IPInfusion/OcNOS/tree/1.2
This application establishes a secure connection with the daemon running on the device to perform
commands and send system responses.
There are different NetConf client applications. In this document, OpenYuma’s yangcli application is used to
show NetConf operations.
Refer to the standard Yangcli operations at:
https://github.com/OpenClovis/OpenYuma/blob/master/netconf/doc/yuma_docs/openyuma-yangcli-manual.odt
The NetConf operations get-config and get return large amounts of data. To improve the readability of the
output, the subtree filter based sget-config and sget operations are used in this document.
Install Yangcli
Check out the git repository, compile and install OpenYuma components. Refer to the README for more
details.
Download Yang files
Download the Yang files from the website:
https://github.com/IPInfusion/OcNOS/tree/1.2
Copy the files to /usr/share/yuma/modules/netconfcentral on the host machine where the client application
runs. This system path only works with OpenYuma’s Yangcli client application. If you are running a different
client application, follow the respective reference document to copy the Yang files to the appropriate location.
Creating User Accounts
User level access control applies to all NetConf operations. The table below describes access levels for
different user types and commands to create different type of user account
Account type Access Command
User Read username <user name> role network-user password
<password>
Operator All, except full configuration store
level change.
username <user name> role network-operator
password <password>
Admin All username <user name> role network-admin password
<password>
23. 23
Solution Guide
You must login into the device using network administrator account to create new user accounts. These are
the steps:
[root@localhost ~]# ssh ocnos@10.12.45.253
ocnos@10.12.45.253’s password:
Last login: Wed Jun 15 21:27:39 2016
OcNOS version 1.2.0.179-OCNOS-DC-IPBASE-ZEBM IPIRouter 06/14/16 21:30:36
OcNOS>en
OcNOS#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
OcNOS(config)#username netuser role network-user password Abc@6789
OcNOS(config)#username netoperator role network-operator password Abc@6789
OcNOS(config)#username netadmin role network-admin password Abc@6789
After creating the account, use the write command to write the configured data into persistent storage as
described in Copy Running Configuration to Startup
OcNOS(config)#write
Building configuration...
[OK]
The NetConf operations for different user account types are shown in Supported Operations.
Yangcli Operations
Establish Connection
These are the steps to establish a connection between the NetConf client and the server that is running on
the device.
# yangcli server=<ip _ address> user=<user _ name> password=<password>
ip _ address: Address of the device to be managed
user _ name & password: User account detail for authentication
The interactive version of this command is shown below:
# yangcli
yangcli> connect
Enter string value for leaf <user>
yangcli:connect> <user _ name>
Enter string value for leaf <server>
yangcli:connect> <ip _ address>
Enter string value for leaf <password>
yangcli:connect> <password>
Load Modules
The load command loads a YANG module into the server. This command is not part of the RFC and is only
supported by the Yang client.
The ZebOS module is the parent for all protocol modules supported in OcNOS. This module includes all the
sub modules. Therefore, loading this module is mandatory to start managing the device. Here is the portion of
ZebOS.yang file that includes other sub modules.
module ZebOS {
namespace “http://www.ipinfusion.com/CMLSchema/ZebOS”;
prefix “ZebOS”;
include nsmLACP;
include oamBfd;
24. 24
Solution Guide
include bridge;
include ospf;
include vlan;
include mstp;
include layer2LACP;
include bgp;
include vr;
include vrf;
include interface;
include lldpv2;
include ospf6;
include rib;
include vlaninterface;
...
}
> load ZebOS
RPC Data Reply 1 for session 1:
rpc-reply {
mod-revision 2015-10-08
}
After using the load command, you can also use the mgrload command to keep the current session
synchronized with the server.
> mgrload ZebOS
Load module ‘ZebOS’ OK
Configure the Device
Configuration details are placed in an XML file and sent to the netconfd server. You must refer to the Yang file
to prepare the XML based configuration file with the correct hierarchy. If the hierarchy is not correct, yangcli
throws an error.
One portion of the BGP protocol module Yang model is presented below. This module is a sub-module for the
parent ZebOS yang module.
submodule bgp {
belongs-to ZebOS { prefix ZebOS; }
include interface;
include vrf;
import cml _ data _ types {
prefix cml _ data _ types;
}
revision “2015-04-25” {
description “Revised on 2015-04-25.”; }
grouping bgp-grouping {
list bgp {
description “bgp”;
config true;
key “bgpAs”;
leaf vrId {
mandatory false;
type leafref {
path “/vr/vrId”;
}
} // END of vrId definition.
...
leaf keepAlive {
mandatory false;
25. 25
Solution Guide
type cml _ data _ types:CML _ UINT16 _ T {
range “0..65535”;
}
default “30”;
config true;
} // END of keepAlive definition.
leaf holdTime {
mandatory false;
type cml _ data _ types:CML _ UINT16 _ T {
range “0..65535”;
}
default “90”;
config true;
} // END of holdTime definition.
...
} // END of bgpDebug-grouping definition.
Based on the hierarchy in the Yang module. the following XML file named bgp.xml is created with the
configuration data. The bgp.xml file is referenced in the edit-config operation specified below.
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”>
<vrId>0</vrId>
<bgp>
<bgpAs>100</bgpAs>
<keepAlive>60</keepAlive>
<holdTime>180</holdTime>
</bgp>
</vr>
Use this command to globally set or reset the keepalive and holdtime values for all the neighbors.
yangcli ocnos@10.12.45.253> edit-config config=@/root/bgp.xml
Filling container /edit-config/input/target:
RPC OK Reply 15 for session 1:
Retrieve Candidate Configuration
Candidate configuration datastore is used to hold configuration data that can be manipulated without
impacting the device’s current configuration. The candidate configuration is a full configuration data set that
serves as a work place for creating and manipulating configuration data. Additions, deletions, and changes
can be made to this data to construct the desired configuration data.
>sget-config /vr/bgp source=candidate
Filling list /vr/bgp:
RPC Data Reply 1 for session 2:
rpc-reply {
data {
vr {
bgp 100 {
bgpAs 100
holdTime 180
keepAlive 60
vrfName default
}
}
}
}
26. 26
Solution Guide
Commit Candidate Configuration
A <commit> operation MAY be performed at any time that causes the device’s running configuration to be set
to the value of the candidate configuration.
yangcli ocnos@10.12.45.253> commit
RPC OK Reply 16 for session 1:
Retrieve Running Configuration
Configuration data is the set of writable data that is required to transform a system from its initial default state
into its current state. You can use the get-config operation to fetch the running configuration data.
>sget-config /vr/bgp source=running
Filling list /vr/bgp:
RPC Data Reply 1 for session 2:
rpc-reply {
data {
vr {
bgp 100 {
bgpAs 100
holdTime 180
keepAlive 60
vrfName default
}
}
}
}
Retrieve Running Configuration and State Data
State data is the additional data on a system that is not configuration data such as read-only status
information and collected statistics. You can use the get operation to fetch a protocol module’s running
configuration and state data.
>sget /vr/bgp
rpc-reply {
data {
vr {
bgp 100 {
bgpAs 100
holdTime 180
keepAlive 60
vrfName default
bgpTableVersion 0
ntwkPrefixCount 0
ibgpMetric 0
pathAttrBest 0
clusterList fill _ value
routerRunIpAddr fill _ value
bgpShowTypeStr fill _ value
bgpShowType 0
rfdMaxPenaltyCeil 0
rfdMinPenaltyFloor 0
dampeningStr 0
rfdCbStr 0
27. 27
Solution Guide
ibgpMetric 0
}
}
}
}
Copy Running Configuration to Startup
NetConf supports startup options, so if you have configured the device and want to retain the configuration
after a device reboot, copy the running configuration into startup configuration. The yangcli command is:
> copy-config source=running target=startup
The equivalent OcNOS command is
# write
Error Messages
NetConf operations return protocol, management layer, and protocol module errors. The example below
depicts an error returned by a protocol module.
Copy the content below into bgp_err.xml.
<vr xmlns=”http://www.ipinfusion.com/CMLSchema/ZebOS”>
<vrId>0</vrId>
<bgp>
<bgpAs>1</bgpAs>
<keepAlive>300</keepAlive>
<holdTime>200</holdTime>
</bgp>
</vr>
Execute the following command and commit the changes
yangcli tbyran@10.12.45.253> edit-config config=@/root/bgp _ err.xml
Filling container /edit-config/input/target:
RPC OK Reply 12 for session 1:
yangcli tbyran@10.12.45.253> commit
mgr _ rpc: got invalid reply on session 1 (invalid XPath expression syntax)
RPC Error Reply 13 for session 1:
rpc-reply {
rpc-error {
error-type protocol
error-tag
error-severity warning
error-app-tag general-warning
error-path ‘RPC operation failed’
error-message ‘%% Hold time should be greater than the keepalive time’
error-info {
error-number 4294962411
}
}
}
Transactions
OcNOS supports transaction-oriented configuration management. Transactions are created implicitly by edit-
config operations; commit and discard-changes operations close or terminate the transactions. Successive
edit-config operations are placed in the same transaction.
28. 28
Solution Guide
Discard Changes
Discard the transaction or candidate configuration changes.
yangcli ocnos@10.12.45.253> sget-config /vr/ospf source=candidate
Filling list /vr/ospf:
mgr _ rpc: got invalid reply on session 1 (missing index component)
RPC Data Reply 14 for session 2:
rpc-reply {
data {
vr {
ospf 0 {
ospfProcessId 0
ospfShutDown true
}
ospf 200 {
ospfProcessId 200
}
}
}
}
yangcli ocnos@10.12.45.253> discard-changes
RPC OK Reply 15 for session 2:
yangcli ocnos@10.12.45.253> sget-config /vr/ospf source=candidate
Filling list /vr/ospf:
mgr _ rpc: got invalid reply on session 1 (missing index component)
RPC Data Reply 16 for session 2:
rpc-reply {
data {
vr {
ospf 0 {
ospfProcessId 0
ospfShutDown true
}
}
}
}
Commit
Commit the transaction or candidate configuration changes.
yangcli ocnos@10.12.45.253> create /vr/ospf
Filling list /vr/ospf:
Filling key leaf /vr/ospf/ospfProcessId:
Enter int32 value for leaf <ospfProcessId>
yangcli ocnos@10.12.45.253:create> 500
Filling key leaf /vr/vrId:
Enter uint32 value for leaf <vrId>
yangcli ocnos@10.12.45.253> 0
RPC OK Reply 17 for session 2:
yangcli ocnos@10.12.45.253> commit
RPC OK Reply 18 for session 2:
29. 29
Solution Guide
yangcli ocnos@10.12.45.253> sget-config /vr/ospf source=running
Filling list /vr/ospf:
mgr _ rpc: got invalid reply on session 1 (missing index component)
RPC Data Reply 19 for session 2:
rpc-reply {
data {
vr {
ospf 0 {
ospfProcessId 0
ospfShutDown true
}
ospf 500 {
ospfProcessId 500
}
}
}
}
Save Point
OcNOS supports the savepoint feature. A savepoint is a snapshot of the device current state. You can switch
the device state to any savepoint at any time.
This example creates two savepoints HT180 and HT300
■■ HT180 has holdTime set to 180
■■ HT300 has holdTime set to 300
yangcli ocnos@10.12.45.253> create
create create-savepoint create-subscription
yangcli ocnos@10.12.45.253> create-savepoint
Enter string value for leaf <savepointName>
yangcli ocnos@10.12.45.253:create-savepoint> HT180
RPC OK Reply 4 for session 2:
yangcli ocnos@10.12.45.253> edit-config config=@/root/bgp _ ht.xml
Filling container /edit-config/input/target:
RPC OK Reply 5 for session 2:
yangcli ocnos@10.12.45.253> commit
RPC OK Reply 6 for session 2:
yangcli ocnos@10.12.45.253> sget-config /vr/bgp source=running
Filling list /vr/bgp:
mgr _ rpc: got invalid reply on session 1 (missing index component)
RPC Data Reply 7 for session 2:
rpc-reply {
data {
vr {
bgp 100 {
bgpAs 100
holdTime 300
keepAlive 60
30. 30
Solution Guide
vrfName default
}
}
}
}
yangcli ocnos@10.12.45.253> create-savepoint HT300
RPC OK Reply 8 for session 2:
Roll Back
This example shows rolling back the configuration. First, notice the current value of the holdTime attribute:
yangcli ocnos@10.12.45.253> sget-config /vr/bgp source=running
Filling list /vr/bgp:
mgr _ rpc: got invalid reply on session 1 (missing index component)
RPC Data Reply 10 for session 2:
rpc-reply {
data {
vr {
bgp 100 {
bgpAs 100
holdTime 180
keepAlive 60
vrfName default
}
}
}
}
Now roll back to savepoint HT300 and note the value of holdTime attribute.
yangcli ocnos@10.12.45.253> rollback-transaction HT300
RPC OK Reply 11 for session 2:
yangcli ocnos@10.12.45.253> sget-config /vr/bgp source=running
Filling list /vr/bgp:
mgr _ rpc: got invalid reply on session 1 (missing index component)
RPC Data Reply 12 for session 2:
rpc-reply {
data {
vr {
bgp 100 {
bgpAs 100
holdTime 300
keepAlive 60
vrfName default
}
}
}
}
Supported Operations
All the NetConf operations are captured based on the capability. Hence, any operation falling in multiple
31. 31
Solution Guide
capability are documented separately.
Note: Capability “base:1.0” supports candidate and running configuration store.
Capability Operation User Role Supported
(Yes/No)
Comments
:base:1.0 <get> User, Operator,
Admin
Yes
:base:1.0 <get> with subtree
filter
User, Operator,
Admin
Yes
:base:1.0 <get-config> User, Operator,
Admin
Yes
:base:1.0 get-config
source=<target>
User, Operator,
Admin
Yes
:base:1.0 <get-config> with
subtree filter
User, Operator,
Admin
Yes
:base:1.0 <edit-config> <target>
as parameter
Operator, Admin Yes Running configuration as
target is not supported
because writtable-
running capability is not
supported
:base:1.0 <edit-config> <config>
as parameter
Operator, Admin Yes
:base:1.0 <edit-config>:
<merge>
Operator, Admin Yes
:base:1.0 <edit-config>:
<replace>
Operator, Admin Yes
:base:1.0 <edit-config>:
<create>
Operator, Admin Yes
:base:1.0 <edit-config>:
<delete>
Operator, Admin Yes
:base:1.0 <edit-config>:
<remove>
Operator, Admin Yes
Capability Operation User Role Supported
(Yes/No)
Comments
:base:1.0 <edit-config>: <none> Operator, Admin Yes
:base:1.0 <edit-config>: <error-
option > as stop-on-
error
Operator, Admin No
:base:1.0 <edit-config>: <error-
option > as continue-
on-error
Operator, Admin No
32. 32
Solution Guide
:rollback-on-
error:1.0
<edit-config>: <error-
option > as rollback-
on-error
Operator, Admin Partial By default, this is the
behavior. So there is no
need to pass this error-
option.
:validate: 1.1 <edit-config>: <test-
option >
Operator, Admin No By default configuration
entries are validated
and stored, hence
this operation and its
parameters are not
handled. External
configuration store
validation is not
supported (i.e URL).
:base:1.0 <copy-config> : <
target> <source>
Operator, Admin Yes
:base:1.0 <lock> : < target> Operator, Admin Yes Candidate configuration
lock is not supported.
:base:1.0 <unlock> : < target> Operator, Admin Yes Candidate configuration
unlock is not supported
:base:1.0 <close-session> close
current session
User, Operator,
Admin
Yes
:base:1.0 <kill-session> : Close
other session
User, Operator,
Admin
Yes
:base:1.0 subtree filtering User, Operator,
Admin
Yes
:Startup:1.0 get-config
<source=startup>
User, Operator,
Admin
Yes
:Startup:1.0 copy-config
<source=startup>
Admin No
:Startup:1.0 copy-config
<target=startup>
Admin Partial Running to startup copy
is supported.
:Startup:1.0 lock <startup> Admin Yes
:Startup:1.0 unlock <startup> Admin Yes
Capability Operation User Role Supported
(Yes/No)
Comments
:Startup:1.0 validate
<source=startup>
Admin No Always configuration
entries are validated
and stored, but
external configuration
store validation is not
supported.
:Startup:1.0 delete-config Admin Yes
33. 33
Solution Guide
:url:1.0 URL capability User, Operator,
Admin
No Not supported
:with-defaults <get> User, Operator,
Admin
Partial By default, “report-all”
functionality is supported
when with-default
option is passed. Other
options (explicit, tagged,
explicit-tagged) are not
supported
:with-defaults <get-config> User, Operator,
Admin
Partial By default, “report-all”
functionality is supported
when with-default
option is passed. Other
options (explicit, tagged,
explicit-tagged) are not
supported
:confirmed-
commit
<commit> <confirmed> Operator, Admin Yes
:confirmed-
commit
<commit> <confirmed>
<persist>
Operator, Admin Yes