This article identifies resources for understanding, configuring and verifying the "High availability or Chassis cluster" (in Juniper's term) on Juniper's SRX 1500 Series firewall. You can use this article as a reference to configuring the chassis cluster on your SRX firewalls. This configuration has been tested and proven to be working as expected. I hope this help you.
Chassis clustering provides redundancy by grouping two SRX devices into a cluster. The cluster represents the devices as a single device. The basic chassis cluster consists of one active device providing services and one passive device maintaining state for failover. To create a chassis cluster, two SRX devices must be physically connected via control and fabric links, then clustering must be enabled by assigning cluster IDs and node IDs to each device.
This document provides an overview of Juniper Networks' high availability and security capabilities for its SRX series firewall and security gateway products. It discusses the SRX architecture including components like IOC, NPC, and SPC cards. It then covers key high availability features like active/active and active/standby redundancy, data and control path separation, load sharing, data synchronization, and stateful failover. The document also reviews troubleshooting techniques, in service software upgrade processes, and a list of features supported by ISSU for different Junos releases.
High availability clusters use redundant systems and components to minimize downtime from failures. An SRX cluster provides redundancy by grouping two SRX devices to act as a single device. Key components include the control plane, data plane, and redundancy groups. The control plane ensures only one configuration between nodes. Redundancy groups contain objects that fail over together if monitoring detects failures.
This document provides an overview of the SRX JUMP STATION, which is a collection of quick start guides for configuring Juniper SRX firewalls. The purpose is to help users with ScreenOS experience transition to using JUNOS-based SRX firewalls. It assumes some basic JUNOS knowledge and provides examples of commands for common tasks. Navigation links and chapter buttons guide users through topics like login, interfaces, routing, security policies, VPNs, clustering, and more. Additional documentation sources are also referenced for more in-depth information or training.
EtherChannel allows linking multiple network interfaces together to form a single logical channel with increased bandwidth and redundancy. There are two methods for configuring EtherChannel - manually by ensuring port compatibility across switches, or dynamically using either Cisco's PAgP or the IEEE standard LACP protocol to automatically negotiate channel formation. Troubleshooting tools like "show etherchannel summary" can verify EtherChannel configuration and status.
This document is the Junos OS Logical Systems Configuration Guide for Release 11.1. It includes copyright information for Juniper Networks and various third party software included in the product. It also includes a revision history, year 2000 compliance statement, and end user license agreement governing the use of the software.
In this presentation, e will discuss AirWave 10, a new software build that lets us streamline code, add performance, clustering. Check out the webinar recording where this presentation was used: http://community.arubanetworks.com/t5/Network-Management/Technical-Webinar-Introduction-to-AirWave-10/td-p/454762
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
Chassis clustering provides redundancy by grouping two SRX devices into a cluster. The cluster represents the devices as a single device. The basic chassis cluster consists of one active device providing services and one passive device maintaining state for failover. To create a chassis cluster, two SRX devices must be physically connected via control and fabric links, then clustering must be enabled by assigning cluster IDs and node IDs to each device.
This document provides an overview of Juniper Networks' high availability and security capabilities for its SRX series firewall and security gateway products. It discusses the SRX architecture including components like IOC, NPC, and SPC cards. It then covers key high availability features like active/active and active/standby redundancy, data and control path separation, load sharing, data synchronization, and stateful failover. The document also reviews troubleshooting techniques, in service software upgrade processes, and a list of features supported by ISSU for different Junos releases.
High availability clusters use redundant systems and components to minimize downtime from failures. An SRX cluster provides redundancy by grouping two SRX devices to act as a single device. Key components include the control plane, data plane, and redundancy groups. The control plane ensures only one configuration between nodes. Redundancy groups contain objects that fail over together if monitoring detects failures.
This document provides an overview of the SRX JUMP STATION, which is a collection of quick start guides for configuring Juniper SRX firewalls. The purpose is to help users with ScreenOS experience transition to using JUNOS-based SRX firewalls. It assumes some basic JUNOS knowledge and provides examples of commands for common tasks. Navigation links and chapter buttons guide users through topics like login, interfaces, routing, security policies, VPNs, clustering, and more. Additional documentation sources are also referenced for more in-depth information or training.
EtherChannel allows linking multiple network interfaces together to form a single logical channel with increased bandwidth and redundancy. There are two methods for configuring EtherChannel - manually by ensuring port compatibility across switches, or dynamically using either Cisco's PAgP or the IEEE standard LACP protocol to automatically negotiate channel formation. Troubleshooting tools like "show etherchannel summary" can verify EtherChannel configuration and status.
This document is the Junos OS Logical Systems Configuration Guide for Release 11.1. It includes copyright information for Juniper Networks and various third party software included in the product. It also includes a revision history, year 2000 compliance statement, and end user license agreement governing the use of the software.
In this presentation, e will discuss AirWave 10, a new software build that lets us streamline code, add performance, clustering. Check out the webinar recording where this presentation was used: http://community.arubanetworks.com/t5/Network-Management/Technical-Webinar-Introduction-to-AirWave-10/td-p/454762
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
The document describes configuration labs for various routing protocols and technologies:
- It includes labs for static route configuration, RIP v1/v2, EIGRP, OSPF, route redistribution, switch configuration, VLANs, VTP, STP, and routing between VLANs.
- Frame relay labs cover basic configuration, static maps, routing protocols in Frame Relay networks, point-to-point and multi-point subinterfaces.
- Other labs cover PPP authentication, NAT, ACLs, IPv6, and more. The labs provide instructions to configure the protocols and verify their operation in sample network topologies.
Introduction to nexux from zero to HeroDhruv Sharma
The document provides information about Cisco Nexus switches, including the Nexus 7000 and 7700 series switches. It describes the key components of Nexus switches like chassis, I/O modules, supervisor engines, and fabric modules. It also compares different Nexus 7000 and 7700 chassis models in terms of specifications like slots, bandwidth, switching capacity, and port density. Additionally, it discusses some differences between Nexus switches and Cisco Catalyst switches, such as licensing requirements, user accounts, NX-OS image structure, and use of port profiles instead of macros. Finally, it provides an overview of features supported on Nexus switches like virtual device contexts (VDCs).
The document provides release notes for new and modified commands in the ArubaOS 6.3 command-line interface. It lists over 40 new commands, including commands for AirGroup configuration, AP image preloading, Lync traffic prioritization, and centralized licensing. It also describes modifications made to a few existing commands, such as adding new parameters to the aaa authentication commands.
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 provides useful CLI commands for various functions on an Aruba network including:
- Enabling logging to troubleshoot processes like DHCP or user authentication.
- Checking interface, AP, and radio status and statistics.
- Viewing ARM neighbor reports and scan times.
- Examining user authentication details, roles, and dot1x configuration.
- Checking client connection details, data rates, and troubleshooting high retry counts or errors.
The document defines parameters for RX antenna supervision in an RBS including Class 1 and Class 2 fault limits, supervision window time, and minimum number of samples. It provides explanations of what each parameter controls and recommends values. Setting the parameters incorrectly could result in incorrect or missed fault reporting. The Define Antenna Supervision dialog allows configuration of these parameters by selecting values or using defaults.
The document provides setup instructions for deploying and configuring an Aruba Instant wireless network. It describes how to set up the initial access point which will run the virtual controller software. Additional access points will automatically inherit settings from the virtual controller. The instructions also cover creating basic employee and guest wireless networks with options for security, client IP assignment, and access controls. The process involves a simple four step configuration for each network's basic info, IP settings, security, and access rules.
The Aruba Network Rightsizing Best Practices Guide provides an overview of network rightsizing. Network rightsizing is a network capacity planning and cost optimization strategy based on the principle that wired and wireless LANs should be sized and structured to meet current and future demand. After explaining the principles of network rightsizing and how it can benefit your organization, the methodology for analyzing and planning a rightsized network will be discussed. Finally, you will learn how to implement a rightsized yet scalable Aruba 802.11n network.
To learn more, visit us at http://www.arubanetworks.com/wlan. Join the discussion at https://community.arubanetworks.com
In this presentation, we will discuss how Virtual Switching Framework (VSF) allows supported switches connected to each other through Ethernet connections (copper or fibre) to behave like a single chassis switch. Check out the webinar recording where this presentation was used: http://community.arubanetworks.com/t5/Controllerless-Networks/Technical-Webinar-Virtual-Switching-Framework-ArubaOS-Switch/td-p/445696
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
The document provides commands for the MoShell interface used to manage various network elements in a UMTS radio access network, including the radio network controller (RNC), radio network explorer/installer (RXI), and radio base station (RBS). The commands can be used to view status information, configure parameters, and troubleshoot issues relating to cells, modules, boards, interfaces, alarms, software, and other components on the RNC, RXI, and RBS.
In this presentation, we will cover ArubaOS' Cluster Manager, a combination of multiple managed devices working together to provide high availability to all the clients and ensure service continuity when a failover occurs. Check out the webinar recording where this presentation was used:
http://community.arubanetworks.com/t5/Wireless-Access/Technical-Webinar-Recording-Slides-ArubaOS-Cluster-Manager/td-p/297761
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
Juniper SRX Quickstart 12.1R3 by Thomas SchmidtNam Nguyen
This document provides an overview and introduction to using SRX firewalls with JUNOS. It includes sections on login procedures, CLI basics, switching capabilities, and interface configuration. The document is intended for users familiar with ScreenOS who are new to JUNOS and need guidance on common tasks and commands.
This document provides instructions for installing and configuring a Remote Access Point (RAP) using an Aruba controller. It describes setting up the firewall to allow communication between the RAP and controller, creating a new RAP virtual AP profile with the correct VLAN and IP addressing, adding the RAP to the whitelist, and troubleshooting connectivity issues. The goal is to allow remote users to access the corporate network by connecting to the RAP using the same SSID and authentication as on-site.
IS-IS is an interior gateway protocol that uses link-state routing and SPF algorithms to calculate the shortest path. It supports both CLNP and IP and has three routing levels - level 1 for intra-area routing, level 2 for inter-area routing, and level 1/2 routers that connect levels 1 and 2. There are three types of IS-IS routers: level 1 that exchange intra-area topology, level 2 that exchange inter-area topology, and level 1/2 that act as border routers between levels 1 and 2.
In this presentation, we will run through some Rogue AP troubleshooting scenarios and best practices. The agenda covers Rogue AP Detection, classification techniques and containment, wired containment and wireless containment without Tarpit. Check out the webinar recording where this presentation was used:
http://community.arubanetworks.com/t5/Aruba-Instant-Cloud-Wi-Fi/Technical-Webinar-Recording-Slides-ArubaOS-Rogue-AP/m-p/289230
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
Hot Standby Router Protocol (HSRP) is a Cisco proprietary redundancy protocol for establishing a faulttolerant default gateway, and has been described in detail in RFC 2281.
The protocol establishes a framework between network routers in order to achieve default gateway
failover if the primary gateway becomes inaccessible, in close association with a rapid-converging
routing protocol like EIGRP or OSPF. By multicasting packets, HSRP sends its hello messages to the
multicast address 224.0.0.2 (all routers) for version 1, or 224.0.0.102 for version 2, using UDP port 1985,
to other HSRP-enabled routers, defining priority between the routers.
- OSPF is a link-state routing protocol that is more scalable than RIP. It builds a complete "map" of the network to avoid routing loops.
- OSPF uses link-state advertisements and flooding to exchange routing information between routers. It elects a designated router and backup designated router to optimize this exchange.
- Routers using OSPF establish neighbor relationships, synchronize their link-state databases, and calculate the shortest path to all known destinations using an algorithm on the link-state database.
This document provides an overview of Juniper's service and support offerings across the network lifecycle. It describes Juniper Care, Juniper Care Plus, professional services, education services, and support from the Juniper Technical Assistance Center (JTAC). Juniper Care includes technical support and software upgrades. Juniper Care Plus provides advanced support with proactive monitoring. Professional services help customers assess, design, deploy, and optimize their networks. Education services offer product training through instructor-led and online courses. JTAC provides technical support 24/7 through multiple support centers worldwide.
The document describes configuration labs for various routing protocols and technologies:
- It includes labs for static route configuration, RIP v1/v2, EIGRP, OSPF, route redistribution, switch configuration, VLANs, VTP, STP, and routing between VLANs.
- Frame relay labs cover basic configuration, static maps, routing protocols in Frame Relay networks, point-to-point and multi-point subinterfaces.
- Other labs cover PPP authentication, NAT, ACLs, IPv6, and more. The labs provide instructions to configure the protocols and verify their operation in sample network topologies.
Introduction to nexux from zero to HeroDhruv Sharma
The document provides information about Cisco Nexus switches, including the Nexus 7000 and 7700 series switches. It describes the key components of Nexus switches like chassis, I/O modules, supervisor engines, and fabric modules. It also compares different Nexus 7000 and 7700 chassis models in terms of specifications like slots, bandwidth, switching capacity, and port density. Additionally, it discusses some differences between Nexus switches and Cisco Catalyst switches, such as licensing requirements, user accounts, NX-OS image structure, and use of port profiles instead of macros. Finally, it provides an overview of features supported on Nexus switches like virtual device contexts (VDCs).
The document provides release notes for new and modified commands in the ArubaOS 6.3 command-line interface. It lists over 40 new commands, including commands for AirGroup configuration, AP image preloading, Lync traffic prioritization, and centralized licensing. It also describes modifications made to a few existing commands, such as adding new parameters to the aaa authentication commands.
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 provides useful CLI commands for various functions on an Aruba network including:
- Enabling logging to troubleshoot processes like DHCP or user authentication.
- Checking interface, AP, and radio status and statistics.
- Viewing ARM neighbor reports and scan times.
- Examining user authentication details, roles, and dot1x configuration.
- Checking client connection details, data rates, and troubleshooting high retry counts or errors.
The document defines parameters for RX antenna supervision in an RBS including Class 1 and Class 2 fault limits, supervision window time, and minimum number of samples. It provides explanations of what each parameter controls and recommends values. Setting the parameters incorrectly could result in incorrect or missed fault reporting. The Define Antenna Supervision dialog allows configuration of these parameters by selecting values or using defaults.
The document provides setup instructions for deploying and configuring an Aruba Instant wireless network. It describes how to set up the initial access point which will run the virtual controller software. Additional access points will automatically inherit settings from the virtual controller. The instructions also cover creating basic employee and guest wireless networks with options for security, client IP assignment, and access controls. The process involves a simple four step configuration for each network's basic info, IP settings, security, and access rules.
The Aruba Network Rightsizing Best Practices Guide provides an overview of network rightsizing. Network rightsizing is a network capacity planning and cost optimization strategy based on the principle that wired and wireless LANs should be sized and structured to meet current and future demand. After explaining the principles of network rightsizing and how it can benefit your organization, the methodology for analyzing and planning a rightsized network will be discussed. Finally, you will learn how to implement a rightsized yet scalable Aruba 802.11n network.
To learn more, visit us at http://www.arubanetworks.com/wlan. Join the discussion at https://community.arubanetworks.com
In this presentation, we will discuss how Virtual Switching Framework (VSF) allows supported switches connected to each other through Ethernet connections (copper or fibre) to behave like a single chassis switch. Check out the webinar recording where this presentation was used: http://community.arubanetworks.com/t5/Controllerless-Networks/Technical-Webinar-Virtual-Switching-Framework-ArubaOS-Switch/td-p/445696
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
The document provides commands for the MoShell interface used to manage various network elements in a UMTS radio access network, including the radio network controller (RNC), radio network explorer/installer (RXI), and radio base station (RBS). The commands can be used to view status information, configure parameters, and troubleshoot issues relating to cells, modules, boards, interfaces, alarms, software, and other components on the RNC, RXI, and RBS.
In this presentation, we will cover ArubaOS' Cluster Manager, a combination of multiple managed devices working together to provide high availability to all the clients and ensure service continuity when a failover occurs. Check out the webinar recording where this presentation was used:
http://community.arubanetworks.com/t5/Wireless-Access/Technical-Webinar-Recording-Slides-ArubaOS-Cluster-Manager/td-p/297761
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
Juniper SRX Quickstart 12.1R3 by Thomas SchmidtNam Nguyen
This document provides an overview and introduction to using SRX firewalls with JUNOS. It includes sections on login procedures, CLI basics, switching capabilities, and interface configuration. The document is intended for users familiar with ScreenOS who are new to JUNOS and need guidance on common tasks and commands.
This document provides instructions for installing and configuring a Remote Access Point (RAP) using an Aruba controller. It describes setting up the firewall to allow communication between the RAP and controller, creating a new RAP virtual AP profile with the correct VLAN and IP addressing, adding the RAP to the whitelist, and troubleshooting connectivity issues. The goal is to allow remote users to access the corporate network by connecting to the RAP using the same SSID and authentication as on-site.
IS-IS is an interior gateway protocol that uses link-state routing and SPF algorithms to calculate the shortest path. It supports both CLNP and IP and has three routing levels - level 1 for intra-area routing, level 2 for inter-area routing, and level 1/2 routers that connect levels 1 and 2. There are three types of IS-IS routers: level 1 that exchange intra-area topology, level 2 that exchange inter-area topology, and level 1/2 that act as border routers between levels 1 and 2.
In this presentation, we will run through some Rogue AP troubleshooting scenarios and best practices. The agenda covers Rogue AP Detection, classification techniques and containment, wired containment and wireless containment without Tarpit. Check out the webinar recording where this presentation was used:
http://community.arubanetworks.com/t5/Aruba-Instant-Cloud-Wi-Fi/Technical-Webinar-Recording-Slides-ArubaOS-Rogue-AP/m-p/289230
Register for the upcoming webinars: https://community.arubanetworks.com/t5/Training-Certification-Career/EMEA-Airheads-Webinars-Jul-Dec-2017/td-p/271908
Hot Standby Router Protocol (HSRP) is a Cisco proprietary redundancy protocol for establishing a faulttolerant default gateway, and has been described in detail in RFC 2281.
The protocol establishes a framework between network routers in order to achieve default gateway
failover if the primary gateway becomes inaccessible, in close association with a rapid-converging
routing protocol like EIGRP or OSPF. By multicasting packets, HSRP sends its hello messages to the
multicast address 224.0.0.2 (all routers) for version 1, or 224.0.0.102 for version 2, using UDP port 1985,
to other HSRP-enabled routers, defining priority between the routers.
- OSPF is a link-state routing protocol that is more scalable than RIP. It builds a complete "map" of the network to avoid routing loops.
- OSPF uses link-state advertisements and flooding to exchange routing information between routers. It elects a designated router and backup designated router to optimize this exchange.
- Routers using OSPF establish neighbor relationships, synchronize their link-state databases, and calculate the shortest path to all known destinations using an algorithm on the link-state database.
This document provides an overview of Juniper's service and support offerings across the network lifecycle. It describes Juniper Care, Juniper Care Plus, professional services, education services, and support from the Juniper Technical Assistance Center (JTAC). Juniper Care includes technical support and software upgrades. Juniper Care Plus provides advanced support with proactive monitoring. Professional services help customers assess, design, deploy, and optimize their networks. Education services offer product training through instructor-led and online courses. JTAC provides technical support 24/7 through multiple support centers worldwide.
- The document summarizes Juniper's strategy and initiatives for 2016 in Central and Eastern Europe. It discusses the region's success in 2015, with Juniper being the choice for high-performance networks.
- The 2016 strategy involves building "One Team Juniper" aligned across countries and verticals. It aims to optimize coverage, develop channels, and engage customers proactively.
- Key priorities for 2016 include leveraging the full portfolio value, positioning security and data center solutions, and educating partners and customers. The goal is continued momentum building on 2015 success.
The document provides information about virtual machine extensions (VMX) on Juniper Networks routers. It discusses hardware virtualization concepts including guest virtual machines running on a host machine. It then describes the different types of virtualization including fully virtualized, para-virtualized, and hardware-assisted. The rest of the document goes into details about the VMX product, architecture, forwarding model, and performance considerations for different use cases.
The document provides information on Juniper SRX platform updates, including:
1) vSRX updates - The virtual firewall platform now supports up to 80G FW throughput on a single server and 100G vSRX was announced. Support for VMware 5.5+SRIOV and features parity with physical SRX firewalls.
2) Physical SRX updates - New SRX3xx and SRX550 series for branches up to 500 users. The SRX1500 provides high performance networking and security for enterprise edge and data center edge. The SRX5400 supports advanced software security services.
3) Software updates - Sky ATP cloud-based malware analysis and SRX User Identity REST API.
The document provides an agenda for the Juniper Day 2016 campus event in Prague. It discusses upcoming trends in campus LANs including 2.5 and 5 Gbps Ethernet standards, Juniper's new Fusion architecture approach, and new EX switching series products like the EX9200, EX4300, EX3400 and EX2300 that support these trends and Juniper's Fusion Enterprise solution. It also covers timelines for multi-gigabit adoption and Junos Fusion capabilities for unifying campus networks.
A corporate network is designed to connect the main office in New York with branches in New Delhi, Bangalore, and Jamshedpur. Various protocols are used within and between the offices for effective communication. In New York, two multilayer switches use inter-VLAN routing and PAT to connect local PCs and the main branch. The New Delhi branch uses VLANs and PAT to separate departments between two floors. Bangalore uses VTP between a server and two client switches to define VLANs for departments. Jamshedpur employs HSRP between two switches for high availability and a PAT router to connect to the frame relay.
20151222_Interoperability with ML2: LinuxBridge, OVS and SDNSungman Jang
The document discusses interoperability between OpenStack Networking (Neutron) and different layer 2 networking technologies like LinuxBridge, Open vSwitch (OVS), and Software-Defined Networking (SDN) using the Modular Layer 2 (ML2) plugin framework. It provides background on LinuxBridge and OVS, describes the expected scenario of using ML2 with LinuxBridge and OVS mechanism drivers and type drivers like flat, VLAN, GRE, and VXLAN. It also briefly discusses the role of the ML2 plugin and mechanism drivers in code.
The document discusses integrating OpenStack Networking (Neutron) with Software Defined Networking (SDN) controllers. It describes how Neutron can use an SDN controller like ONOS instead of traditional mechanism drivers like Open vSwitch. The key components that would need to be modified are the mechanism driver, service plugin, and configuration. Five virtual machines or host machines running specific OpenStack and ONOS services are also needed to demonstrate the integration between Neutron and an SDN controller.
VyOS now supports VXLAN interfaces which allow multiple L2 segments to be multiplexed over a single physical network. VXLAN uses encapsulation to transport Ethernet frames over IP. The VNI field in VXLAN headers maps frames to different L2 segments. VyOS VXLAN interfaces can be configured and used like physical interfaces for routing, bridging, and protocols like OSPF. However, attributes like the VNI and multicast group cannot be changed after interface creation without deleting and recreating the interface.
VMworld 2016: vSphere 6.x Host Resource Deep DiveVMworld
1. This document provides an overview and agenda for a presentation on vSphere 6.x host resource deep dive topics including compute, storage, and network.
2. It introduces the presenters, Niels Hagoort and Frank Denneman, and provides background on their expertise.
3. The document outlines the topics to be covered under each section, including NUMA, CPU cache, DIMM configuration, I/O queue placement, driver considerations, RSS and NetQueue scaling for networking.
1. The document provides instructions for configuring inband and outband network administration (NA) on a ZXDSL 9210 device. This includes setting IP addresses, routes, VLANs, SNMP settings, and testing the connection.
2. It also describes how to configure basic Ethernet and ADSL user services on the device by adding user ports to VLANs, setting PVIDs, and optionally creating line and alarm profiles.
3. The configuration is saved before testing the network connectivity with ping commands.
Eigrp on a cisco asa firewall configuration3Anetwork com
The document discusses configuring EIGRP routing on a Cisco ASA firewall. It describes setting up interfaces, IP addressing, and EIGRP routing on the ASA and two routers. The ASA separates an internal, DMZ, and external network, and redistributes a default static route into EIGRP. Configuration is verified by showing EIGRP neighbors, routes, and that the routers have learned routes from all connected networks.
This document provides instructions for CCNP Switch Lab 1. It describes the lab equipment which consists of a switch pod with a multilayer distribution switch, two layer 2 access switches, and cables. Students will each manage their own individual pod. The physical topology is explained and configurations like hostname, passwords, interfaces are demonstrated. Commands used in the lab like 'write erase' and 'delete flash:vlan.dat' are listed. Example outputs of show commands are also provided.
Four switches have been installed with redundant uplinks between access and distribution layers. Spanning tree removes redundant links, running a separate instance for each VLAN. To reduce CPU load, MST is configured to group VLANs into instances. MST is enabled on all switches and the MST region name "CISCO" and revision number 1 are applied. VLANs 20-50 are assigned to instance 1 and VLANs 80 and 100 to instance 2, with others remaining in the default instance 0.
Four switches have been installed with redundant uplinks between access and distribution layers. Spanning tree removes redundant links to prevent loops. The document describes configuring Multiple Spanning Tree (MST) on the switches to group VLANs into instances to reduce CPU load from multiple spanning tree calculations. MST is configured by assigning VLANs 20-50 to instance 1 and VLANs 80,100 to instance 2 while the rest remain in the default instance 0. Identical MST configurations must be applied to all switches for proper operation.
This document summarizes a method for deploying a datacenter using infrastructure as code principles. Key steps include:
1. Generating device configurations from YAML data files and Jinja2 templates using the Jerikan tool. Jerikan compiles configurations directly from the source of truth.
2. Integrating Jerikan and Ansible together - Jerikan generates the Ansible inventory and Ansible deploys the full configurations in an idempotent way.
3. Managing the YAML data files and Jinja2 templates in a Git repository to allow review and validation of changes through merge requests before deployment.
This approach aims to provide an automated, auditable and reproducible method for deploying an entire datacenter from a version controlled
System Device Tree & Lopper
The document discusses using a System Device Tree (S-DT) and the open source Lopper tool to simplify hardware resource allocation and configuration across multiple operating systems and firmware. An S-DT describes all hardware resources that can later be divided into partitions or domains. Lopper takes an S-DT as input, prunes it to generate traditional device trees for each domain, and handles address mapping and other transformations. The document outlines ongoing work to specify shared resource allocation, bus firewall configuration, and integration with RemoteProc in the S-DT to further standardize the process.
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...Tarun Khaneja
This document provides a summary of a presentation on CCNA (Cisco Certified Network Associate). It was trained by Ravinder Kumar from Gurukul Technical Institute and submitted by Tarun Khaneja with roll number 2110045 and contact number 09034406598. The presentation introduces CCNA and discusses networking types and applications. It also covers networking devices, subnetting, routing protocols like RIP, EIGRP, OSPF, ACLs, VLANs, and inter-VLAN routing. Configuration examples are provided for EIGRP and RIP routing on the same network.
The document discusses the Cisco Catalyst 6500 series chassis and components. It provides details on the different chassis models, supervisor engines, line cards, and modules available. It also covers features like redundant power supplies, Route Processor Redundancy, EtherChannels, Unidirectional Link Detection, and Flex Links.
Apache Cassandra operations have the reputation to be simple on single datacenter deployments and / or low volume clusters but they become way more complex on high latency multi-datacenter clusters with high volume and / or high throughout: basic Apache Cassandra operations such as repairs, compactions or hints delivery can have dramatic consequences even on a healthy high latency multi-datacenter cluster.
In this presentation, Julien will go through Apache Cassandra mutli-datacenter concepts first then show multi-datacenter operations essentials in details: bootstrapping new nodes and / or datacenter, repairs strategy, Java GC tuning, OS tuning, Apache Cassandra configuration and monitoring.
Based on his 3 years experience managing a multi-datacenter cluster against Apache Cassandra 2.0, 2.1, 2.2 and 3.0, Julien will give you tips on how to anticipate and prevent / mitigate issues related to basic Apache Cassandra operations with a multi-datacenter cluster.
Apache Cassandra operations have the reputation to be simple on single datacenter deployments and / or low volume clusters but they become way more complex on high latency multi-datacenter clusters with high volume and / or high throughout: basic Apache Cassandra operations such as repairs, compactions or hints delivery can have dramatic consequences even on a healthy high latency multi-datacenter cluster.
In this presentation, Julien will go through Apache Cassandra mutli-datacenter concepts first then show multi-datacenter operations essentials in details: bootstrapping new nodes and / or datacenter, repairs strategy, Java GC tuning, OS tuning, Apache Cassandra configuration and monitoring.
Based on his 3 years experience managing a multi-datacenter cluster against Apache Cassandra 2.0, 2.1, 2.2 and 3.0, Julien will give you tips on how to anticipate and prevent / mitigate issues related to basic Apache Cassandra operations with a multi-datacenter cluster.
About the Speaker
Julien Anguenot VP Software Engineering, iland Internet Solutions, Corp
Julien currently serves as iland's Vice President of Software Engineering. Prior to joining iland, Mr. Anguenot held tech leadership positions at several open source content management vendors and tech startups in Europe and in the U.S. Julien is a long time Open Source software advocate, contributor and speaker: Zope, ZODB, Nuxeo contributor, Zope and OpenStack foundations member, his talks includes Apache Con, Cassandra summit, OpenStack summit, The WWW Conference or still EuroPython.
This chapter describes how to configure VLANs on Cisco 7600 series routers. It discusses VLAN default configurations, guidelines for VLAN configuration, and how to configure VLANs. It also provides an overview of how VLANs work, including different VLAN types and ranges.
This document provides a summary of a presentation on CCNA (Cisco Certified Network Associate). It includes:
1. An introduction to CCNA, which stands for Cisco Certified Network Associate and provides information about networking, its types and applications. Networking is important for communication and resource sharing.
2. Descriptions of different types of networking including LAN, MAN, and WAN. It also lists common networking devices like LAN cards, bridges, hubs, switches, and routers.
3. Overviews of topics covered in CCNA including subnetting, supernetting, Classless Interdomain Routing (CIDR), the differences between hubs and switches, what routers are used for,
The document discusses important show commands for Cisco routers and switches. It provides a cheat sheet of the most useful show commands including show running-config, show version, show ip route, show interfaces, show cdp neighbors, and show clock. Each command is briefly described in terms of the key information it displays about the device, interfaces, configurations, or network.
The document evaluates Lustre 2.9 and OpenStack for providing isolated POSIX file systems to tenants in OpenStack, finding that Lustre 2.9 allows uid mapping that can isolate tenants while maintaining high performance, and that physical and virtual Lustre routers can route traffic between tenants effectively albeit with some increased east-west traffic with virtual routers.
Similar to Juniper Chassis Cluster Configuration with SRX-1500s (20)
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...TechSoup
Whether you're new to SEO or looking to refine your existing strategies, this webinar will provide you with actionable insights and practical tips to elevate your nonprofit's online presence.
THE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...indexPub
The recent surge in pro-Palestine student activism has prompted significant responses from universities, ranging from negotiations and divestment commitments to increased transparency about investments in companies supporting the war on Gaza. This activism has led to the cessation of student encampments but also highlighted the substantial sacrifices made by students, including academic disruptions and personal risks. The primary drivers of these protests are poor university administration, lack of transparency, and inadequate communication between officials and students. This study examines the profound emotional, psychological, and professional impacts on students engaged in pro-Palestine protests, focusing on Generation Z's (Gen-Z) activism dynamics. This paper explores the significant sacrifices made by these students and even the professors supporting the pro-Palestine movement, with a focus on recent global movements. Through an in-depth analysis of printed and electronic media, the study examines the impacts of these sacrifices on the academic and personal lives of those involved. The paper highlights examples from various universities, demonstrating student activism's long-term and short-term effects, including disciplinary actions, social backlash, and career implications. The researchers also explore the broader implications of student sacrifices. The findings reveal that these sacrifices are driven by a profound commitment to justice and human rights, and are influenced by the increasing availability of information, peer interactions, and personal convictions. The study also discusses the broader implications of this activism, comparing it to historical precedents and assessing its potential to influence policy and public opinion. The emotional and psychological toll on student activists is significant, but their sense of purpose and community support mitigates some of these challenges. However, the researchers call for acknowledging the broader Impact of these sacrifices on the future global movement of FreePalestine.
This presentation was provided by Racquel Jemison, Ph.D., Christina MacLaughlin, Ph.D., and Paulomi Majumder. Ph.D., all of the American Chemical Society, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
How Barcodes Can Be Leveraged Within Odoo 17Celine George
In this presentation, we will explore how barcodes can be leveraged within Odoo 17 to streamline our manufacturing processes. We will cover the configuration steps, how to utilize barcodes in different manufacturing scenarios, and the overall benefits of implementing this technology.
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Gender and Mental Health - Counselling and Family Therapy Applications and In...
Juniper Chassis Cluster Configuration with SRX-1500s
1. JUNIPER CHASSIS CLUSTER CONFIGURATION WITH
SRX-1500S
This article identifies resources for understanding, configuring and verifying the "High availability or Chassis
cluster" (in Juniper's term) on Juniper's SRX 1500 Series firewall.
You can use this article as a reference to configuring the chassis cluster on your SRX firewalls. This
configuration has been tested and proven to be working as expected. I hope this help you.
SUMMARY:
• Juniper SRX-1500 Chassis Cluster Configuration Template
• Deep dive of Chassis Cluster Configuration on SRX-1500
1) Pre-requisite
a) Understand The control link (Control Plane)
b) Understand The Fabric link (Data Plane)
2) Enable the cluster mode
a) Understand Cluster ID
b) Understand Cluster Node
3) Verify that chassis cluster was successful by running
4) Configure management interfaces (fxp0) for each of the nodes.
a) Understand Slot Numbering with the SRX-1500 Chassis Cluster
5) Configure the Fabric links in the cluster
6) Configure the Redundancy Groups 0 and 1
a) Understand Redundancy group
7) Configure interface monitoring
a) Understand Interface monitoring
8) Enable and apply Redundancy Ethernet interfaces
a) Understand Redundant Ethernet Interface
9) Configure Redundancy Ethernet interfaces
• Verification Commands
Ashutosh Patel
CCIE #52560
Network Security Architect
https://www.linkedin.com/in/patelashutosh
2. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 2
Juniper Networks SRX Series Services Gateways can be configured to operate in cluster mode, where a
pair of devices can be connected together and configured to operate as a single node, providing device,
interface, and service level redundancy. Let’s get started.
JUNIPER SRX-1500 CHASSIS CLUSTER CONFIGURATION TEMPLATE
You can use this template as a quick reference if you don’t want to read through the whole article. In this
example I am using two zones only (Outside and Inside).
*** On primary device (node0): From Operational mode
> set chassis cluster cluster-id 1 node 0 reboot
*** On secondary device (node1): From Operational mode
> set chassis cluster cluster-id 1 node 1 reboot
-------------------------------------------------------------------------
*** On primary device (node0): From Configuration mode
set groups node0 system host-name SRX1500-HOSTNAME
set groups node0 system backup-router <Management-Gateway-IP>
set groups node0 system backup-router destination <Management-Network>
set groups node0 interfaces fxp0 description MGMT
set groups node0 interfaces fxp0 unit 0 family inet address <Management IP>
set groups node1 system host-name SRX1500-HOSTNAME
set groups node1 system backup-router <Management -Gateway-IP>
set groups node1 system backup-router destination <Management-Network>
set groups node1 interfaces fxp0 description MGMT
set groups node1 interfaces fxp0 unit 0 family inet address <Management IP>
set apply-groups "${node}"
set interfaces fab0 fabric-options member-interfaces ge-0/0/11
set interfaces fab1 fabric-options member-interfaces ge-7/0/11
set chassis cluster redundancy-group 0 node 0 priority 100
set chassis cluster redundancy-group 0 node 1 priority 1
set chassis cluster redundancy-group 1 node 0 priority 100
set chassis cluster redundancy-group 1 node 1 priority 1
set chassis cluster redundancy-group 1 interface-monitor ge-0/0/0 weight 255
set chassis cluster redundancy-group 1 interface-monitor ge-0/0/1 weight 255
set chassis cluster redundancy-group 1 interface-monitor ge-7/0/0 weight 255
3. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 3
set chassis cluster redundancy-group 1 interface-monitor ge-7/0/1 weight 255
set chassis cluster reth-count <No. of Interface>
set interfaces ge-0/0/0 gigether-options redundant-parent reth0
set interfaces ge-7/0/0 gigether-options redundant-parent reth0
set interfaces ge-0/0/1 gigether-options redundant-parent reth1
set interfaces ge-7/0/1 gigether-options redundant-parent reth1
set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 unit <VLAN> description Outside
set interfaces reth0 unit <VLAN> family inet address <Outside IP/Mask>
set security zone security-zone OUTSIDE interfaces reth0.<VLAN-ID>
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 vlan-tagging
set interfaces reth1 unit <VLAN> vlan-id <VLAN>
set interfaces reth1 unit <VLAN> description Inside
set interfaces reth1 unit <VLAN> family inet address <Inside IP/Mask>
set security zone security-zone INSIDE interfaces reth1.<VLAN-ID>
DEEP DIVE OF CHASSIS CLUSTER CONFIGURATION ON SRX-1500
1. PRE-REQUISITE
• Same hardware and software required (In this case, we have two SRX 1500 running 15.1X49-
D50 code)
o Make sure, both units are the same model, running the same code version and have
the same modules installed
• Physically connect two devices together to create the control and fabric links.
o On SRX 1500, There is a dedicated HA Control port; Connect both HA control ports from
respective devices together to form control link
o In this example, I used last unused port (e.g. Ge-0/0/11) for Fabric link; Connect both Ge-
0/0/11 from respective devices together to form Fabric link
o NOTE: Clustered SRXs share the same IP address for an individual interface
4. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 4
This is how both SRX-1500s are cabled, and this article this diagram can be used as a reference.
1A. THE CONTROL LINK (CONTROL PLANE)
• is used to synchronize the kernel state between the two REs (using daemon called ksyncd)
• is used to send hello messages between them (using daemon called jsrpd)
• is used to synchronize configuration
• is always in an active/backup state. This means only one RE (Route-Engines) can be the master
of the cluster’s configuration and state. If the primary RE fails, the secondary takes over for it.
1B. THE FABRIC LINK (DATA PLANE)
• is used for state synchronization. The state of sessions and services is shared between the two
devices. Sessions are the state of the current set of traffic that is going through the SRX, and
services are other items such as the VPN, IPS, and ALGs.
• operates in active/active mode. so it is possible for traffic to ingress the cluster on one node and
egress from the other node.
2. ENABLE THE CLUSTER MODE
• Set the devices into cluster mode with the following command and reboot the devices.
• Note: this is an operational mode and not a configure mode command. (run it from > and not #)
*** On primary device (node0):
> set chassis cluster cluster-id 1 node 0 reboot
5. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 5
*** On secondary device (node1):
> set chassis cluster cluster-id 1 node 1 reboot
2A. CLUSTER ID
• A cluster is identified by a cluster ID (cluster-id) specified as a number from 1 through 255.
• Cluster ID greater than 15 can only be set when the fabric and control link interfaces are connected
back-to-back.
• Setting a cluster ID to 0 is equivalent to disabling a cluster.
• Each cluster must share a unique identifier among all of its members.
• also used when determining MAC addresses for the redundant Ethernet interfaces.
2B. CLUSTER NODE
• is identified by a node ID (node) specified as a number from 0 to 1.
• is the unique identifier for a device within a cluster.
• Setting the node number distinguishes which SRX is which. Regardless of failover state, node 0
will always remain node 0 and node 1 will always be node 1. The firewalls can take turns being
primary and secondary.
3. VERIFY THAT CHASSIS CLUSTER WAS SUCCESSFUL BY RUNNING
root@lab_SRX1500> show chassis cluster status
Cluster ID: 1
Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 1
node0 1 primary no no
node1 1 secondary no no
Now that we have the chassis cluster completed, we can start with the configuration. We can do the entire
configuration on the primary node0 and anything that is committed on the primary node0 will be copied onto
the secondary node1.
4. CONFIGURE MANAGEMENT INTERFACES (FXP0) FOR EACH OF THE NODES.
This will allow us to have remote SSH access onto each node.
set groups node0 system host-name SRX1500-HOSTNAME
6. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 6
set groups node0 system backup-router <Management-Gateway-IP>
set groups node0 system backup-router destination <Management Network>
set groups node0 interfaces fxp0 description MGMT
set groups node0 interfaces fxp0 unit 0 family inet address <Management IP>
set groups node1 system host-name SRX1500-HOSTNAME
set groups node1 system backup-router <Management-Gateway-IP>
set groups node1 system backup-router destination <Management Network>
set groups node1 interfaces fxp0 description MGMT
set groups node1 interfaces fxp0 unit 0 family inet address <Management IP>
set apply-groups "${node}"
• The backup-router configuration is required for management of the Standby Unit only (either node0
and node1).
• Do NOT configure a default route as the backup-router destination. Also, these routes should match
the static routes that point to the Management Gateway in the cluster configuration:
o the standby unit will use the backup router configuration
o the active unit will use the static routes in the configuration.
• NOTE: Adding the command set apply-groups “${node}” is mandatory, as it ensures that the node
specific configuration is only committed on that specific node
4A. UNDERSTAND SLOT NUMBERING WITH THE SRX-1500 CHASSIS CLUSTER
• The SRX-1500 can have maximum of 6 FPC slots. After the devices are connected as a cluster,
the slot numbering on one device changes and thus the interface numbering will change.
• When connected in cluster mode, the standby unit’s interfaces will be +1 more than the max number
of FPC slots in the primary.
• In this case the primary interfaces will be ge-0/0/0 to ge-0/0/15 and the secondary will be ge-7/0/0
to ge-7/0/15. This is very important to understand.
7. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 7
5. CONFIGURE THE FABRIC LINKS IN THE CLUSTER
set interfaces fab0 fabric-options member-interfaces ge-0/0/11
set interfaces fab1 fabric-options member-interfaces ge-7/0/11
6. CONFIGURE THE REDUNDANCY GROUPS 0 AND 1
set chassis cluster redundancy-group 0 node 0 priority 100
set chassis cluster redundancy-group 0 node 1 priority 1
set chassis cluster redundancy-group 1 node 0 priority 100
set chassis cluster redundancy-group 1 node 1 priority 1
6A. REDUNDANCY GROUP
• Is a collection of resources that need to fail over between the two devices. Primary on one device
and backup on another peer.
• Only one node at a time can be responsible for a redundancy group; however, a single node can
be the primary node for any number of redundancy groups.
• The default redundancy group is group 0. Redundancy group 0 represents the control plane (RE
failover).
o The node that is the master over redundancy group 0 has the active RE.
• Redundancy group 1 or greater represents the data plane. A data plane redundancy group contains
one or more redundant Ethernet interfaces.
o Each member of the cluster has a physical interface bound into a reth.
o The active node’s physical interface will be active and the backup node’s interface will be
passive and will not pass traffic.
7. CONFIGURE INTERFACE MONITORING
set chassis cluster redundancy-group 1 interface-monitor ge-0/0/0 weight 255
set chassis cluster redundancy-group 1 interface-monitor ge-0/0/1 weight 255
set chassis cluster redundancy-group 1 interface-monitor ge-7/0/0 weight 255
set chassis cluster redundancy-group 1 interface-monitor ge-7/0/1 weight 255
7A. INTERFACE MONITORING
• This will check the health and physical status of the each of the interfaces.
8. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 8
• Interface monitoring can be used to trigger a fail-over in the event link status on an interface goes
down.
• By default, interface monitoring has a threshold of 255, once this number is reached the
redundancy group priority will be changed to ‘0’ for the specific node.
• If one or more interfaces monitored fail, the redundancy group will fail over to another node.
• Note: interface monitoring is not recommended for redundancy-group 0.
8. ENABLE AND APPLY REDUNDANCY ETHERNET INTERFACES
set chassis cluster reth-count 2
set interfaces ge-0/0/0 gigether-options redundant-parent reth0
set interfaces ge-7/0/0 gigether-options redundant-parent reth0
set interfaces ge-0/0/1 gigether-options redundant-parent reth1
set interfaces ge-7/0/1 gigether-options redundant-parent reth1
Note: In this example, I am only provisioning two reth interfaces, that's why I have used reth-count 2. One
for OUTSIDE and the other for INSIDE zone but do provision them as per the requirements.
8A. REDUNDANT ETHERNET INTERFACE
• The Reth interface is a logical aggregated interface that allows port bundling between the nodes.
• Once the reth number has been applied, you will be able to assign the physical interfaces.
9. CONFIGURE REDUNDANCY ETHERNET INTERFACES
In this example, both interfaces are configured as Trunk port.
set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 vlan-tagging
set interfaces reth0 unit <VLAN> vlan-id <VLAN>
set interfaces reth0 unit <VLAN> description Outside
set interfaces reth0 unit <VLAN> family inet address <Outside IP/Mask>
set security zone security-zone OUTSIDE interfaces reth0.<VLAN-ID>
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 vlan-tagging
9. ASHUTOSH PATEL https://www.linkedin.com/in/patelashutosh 9
set interfaces reth1 unit <VLAN> vlan-id <VLAN>
set interfaces reth1 unit <VLAN> description Inside
set interfaces reth1 unit <VLAN> family inet address <Inside IP/Mask>
set security zone security-zone INSIDE interfaces reth1.<VLAN-ID>
NOTE: As redundancy group 0 is control plane; Make sure to configure both reth interfaces in redundancy
group 1. Also, as stated earlier, Clustered SRXs share the same IP address for an individual interface. With
that said, you will not require a separate interface configuration for the secondary device.
VERIFICATION COMMANDS
• show chassis cluster status
• show chassis cluster interfaces
• show chassis cluster statistics
• show chassis cluster control-plane statistics
• show chassis cluster data-plane statistics
• show chassis cluster status redundancy-group 1
THANK YOU.
I hope you like this technical article.
Feel free to send me any questions or concerns on my linked-in message.