SlideShare ist ein Scribd-Unternehmen logo
1 von 48
Downloaden Sie, um offline zu lesen
Chassis Cluster Configuration
Chassis clustering provides network node redundancy by
grouping a pair of the same kind of supported J-series
devices or SRX-series devices into a cluster. The devices
must be running JUNOS software.

A chassis cluster takes the two SRX devices and
represents them as a single device.

 It consist of two important models that are:
1. active/active
2. active/passive
The basic active/passive chassis cluster consists of two
devices:

1. One device actively provides routing, firewall, NAT,
   VPN, and security services, along with maintaining
   control of the chassis cluster.
2. The other device passively maintains its state for
   cluster failover capabilities should the active device
   become inactive.
To create an SRX-series chassis cluster, you must
physically connect a pair of the same kind of supported
SRX-series devices back-to-back over a pair of Gigabit
Ethernet connections or a pair of 10-Gigabit Ethernet
connections.

The connection that serves as the control link must be the
built-in controller port on each device. The fabric link
connection can be a combination of any pair of Gigabit
Ethernet interfaces on the devices.
Control
 Ports




                Fabric
  Fabric Link
                 Link
  Cable
After wiring the two devices together, you use
CLI operational mode commands to enable chassis
clustering by assigning a cluster ID and node ID on each
chassis in the cluster. The cluster ID is the same on both
nodes.

To do this, you connect to the console port on the device
that will be the primary, give it a node ID, and identify the
cluster it will belong to, then reboot the system.

Now you then connect the console port to the other device,
give it a node ID, and assign it the same cluster ID you
gave to the first node, then reboot the system.
The fxp0 interfaces, when configured for active/active
operations, function like standard management interfaces
on SRX-series devices and allow network access to each
node in the cluster.

You must, however, first connect to each node through the
console port and assign a unique IP address to
each fxp0 interface.
The fabric is the data link between the nodes and is used to
forward traffic between the chassis.

Traffic arriving on a node that needs to be processed on the
other is forwarded over the fabric data link. Similarly, traffic
processed on a node that needs to exit through an interface on
the other node is forwarded over the fabric.

The fabric also provides for synchronization of session state
objects created by operations such as authentication, Network
Address Translation (NAT), Application Layer Gateways (ALGs),
and IP Security (IPsec) sessions. The fabric link can be any pair
of Gigabit Ethernet interfaces spanning the cluster.
The control interfaces provide the control link between the
two nodes in the cluster and are used for routing updates
and for control plane signal traffic, such as heartbeat and
threshold information that triggers node failover.

The control link is also used to synchronize the
configuration between the nodes. When you submit
configuration statements to the cluster, the configuration is
automatically synchronized over the control link.
1. Physically connect a pair of SRX-series devices
    together
2. Connect the initial node to the console port
3. Configure the control ports
4. Use CLI operational mode commands to enable
    clustering
5. Repeat step 2, 3 & 4 for other device
6. Configure the management interfaces on the cluster
7. Configure the cluster
8. Initiate manual failover
9. Configure conditional route advertisement over
    redundant Ethernet interfaces
10. Verify the configuration
After connecting the two devices together, you configure a
cluster ID and a node ID.

 A cluster ID identifies the cluster that the two nodes
 belong to.
 A node ID identifies a unique node within a cluster.

 You can deploy up to 15 clusters in a Layer 2 domain.
  Each cluster is defined by a cluster-id value within the
  range of 1 through 15. A device can belong to only one
  cluster at any given time. Nodes in a cluster are
  numbered 0 and 1.
To set the node IDs and cluster IDs, connect to each
device through the console port and enter the following
operational commands, then reboot the system.

Enter the cluster ID and node ID information for the first
node. If you want redundancy groups to be primary on
this node when priority settings for both nodes are the
same, make it node 0.
user@host> set chassis cluster node 0 cluster-id 1
warning: A reboot is required for chassis cluster to be
enabled
Enter the cluster ID and node ID for the other node. If you
want redundancy groups to be secondary on this node
when priority settings for both nodes are the same, make
it node1.

user@host> set chassis cluster node 1 cluster-id 1
reboot
Successfully enabled chassis cluster. Going to reboot
now.
Use the show chassis cluster status operational
command to view node status.

user@host# show chassis cluster status

When you complete the chassis cluster basic
configuration, any subsequent configuration changes you
make are automatically synchronized on both nodes.
You must assign a unique IP address to each node in
the cluster to provide network management access. This
configuration is not replicated across the two nodes.

In an SRX-series chassis cluster, the fxp0 interface is a
port on the Routing Engine (RE) card.
From the console port connection to the device you want
to designate as the primary node, in configuration mode
enter the following commands to name the node node0-
router and assign IP address 10.1.1.1/24 to it:

user@host# set groups node0 system host-name
node0-router

user@host# set groups node0 interfaces fxp0 unit 0
family inet address 10.1.1.1/24
From the console port connection to the device you want to
designate the secondary node, in configuration mode enter the
following commands to name the node node1-router and
assign IP address 10.1.1.2/24 to it:

user@host# set groups node1 system host-name node1-
router
user@host# set groups node1 interfaces fxp0 unit 0 family
inet address 10.1.1.2/24

Enter the following command in configuration mode to apply
these unique configurations to the appropriate node. This
configuration is not replicated across the two nodes.
user@host# set apply-groups
For the chassis cluster configuration, you specify the
number of redundant Ethernet interfaces that the cluster
contains and the information used to monitor the “health”
of the cluster.

You must configure the redundant Ethernet interfaces
count for the cluster in order for the redundant Ethernet
interfaces that you configure to be recognized. Use the
following command in configuration mode to define the
number of redundant Ethernet interfaces for the cluster:
user@host# set chassis cluster reth-count 3
The fabric is the back-to-back data connection between the
nodes in a cluster. Traffic on one node that needs to be
processed on the other node or to exit through an interface
on the other node passes over the fabric. Session state
information also passes over the fabric.

In an SRX-series chassis cluster, you can configure any
 pair of Gigabit Ethernet interfaces or any pair of 10-
 Gigabit interfaces to serve as the fabric between nodes.

You cannot configure filters, policies, or services on the
 fabric interface.
Enter the following commands to join ge-0/0/1 on one
node in the cluster and ge-7/0/1 on the other to form the
fabric:

{primary:node0}
user@host# set interfaces fab0 fabric-options
member-interfaces ge-0/0/1
{secondary:node1}
user@host# set interfaces fab1 fabric-options
member-interfaces ge-7/0/1
A redundancy group is an abstract entity (extracting
common features from specific object) that includes
and manages a collection of objects. A redundancy
group can be primary on only one node at a time.

Before you can create redundant Ethernet interfaces
you must create their redundancy groups.
Use the following command in configuration mode to
specify the number of gratuitous Address Resolution
Protocol (ARP) requests that an interface can send to
notify other network devices of its presence after the
redundancy group it belongs to has failed over:

{primary:node1}
user@host# set chassis cluster redundancy-group 1
gratuitous-arp-count 4
Use the following command in configuration mode to
identify an interface to be monitored by a specific
redundancy group and give it a weight. You can configure
a redundancy group to monitor any interfaces, not just
those belonging to its redundant Ethernet interfaces.

{primary:node1}
user@host# set chassis cluster redundancy-group 1
interface-monitor fe-3/1/1/1 weight 100
Use the following commands in configuration mode to
specify a redundancy group's priority for primacy on each
node of the cluster. The higher number takes precedence.

{primary:node1}
user@host# set chassis cluster redundancy-group 1
node 1 priority 100
{secondary:node0}
user@host# set chassis cluster redundancy-group 1
node 0 priority 200
Use the following command in configuration mode to
specify if a node with a better (higher) priority can initiate
a failover to become primary for the redundancy group:

{primary:node1}
user@host# set chassis cluster redundancy-group 1
preempt
A redundant Ethernet interface is a pseudo interface that
contains two physical interfaces, one from each node of
the cluster. To create a redundant Ethernet interface, you
configure the two physical interfaces independently.

You configure the rest of the configuration that pertains to
them at the level of the redundant Ethernet interface, and
each of the child interfaces inherits this configuration.
Use the following commands to bind redundant child physical
interfaces to reth1:
{primary:node1}
user@host# set interfaces ge-0/0/0 gigether-options
redundant-parent reth1
{primary:node1}
user@host# set interfaces ge-7/0/0 gigether-options
redundant-parent reth1
{primary:node1}
user@host# set interfaces fe-1/0/0 fast-ether-options
redundant-parent reth1
{primary:node1}
user@host# set interfaces fe-8/0/0 fast-ether-options
redundant-parent reth1
Use the following commands to:
Add reth 1 to redundancy group 1
Set the MTU (Maximum Transmission Unit) size to 1500
  bytes
Assign IP address 10.1.1.3/24 to reth1

{primary:node1}
user@host# set interfaces reth1 redundant-ether-options
redundancy-group 1
{primary:node1}
user@host# set interfaces reth1 unit 0 family inet mtu
1500
{primary:node1}
user@host# set interfaces reth1 unit 0 family inet address
10.1.1.3/24
Use the following command to associate reth1.0 with a
security zone named Trust. Security zone configuration is
the same for redundant Ethernet interfaces as for any
other interface.

{primary:node1}
user@host# set security zones security-zone Trust
interfaces reth1.0
Redundancy group failover is triggered by the results from
monitoring the health of interfaces that belong to the
redundancy group. When you assign a weight to an
interface to be monitored, the system monitors the
interface for availability.

If a physical interface fails, the weight is deducted from
the corresponding redundancy group's threshold. Every
redundancy group has a threshold of 255. If the threshold
hits 0, a failover is triggered. Failover is triggered even if
the redundancy group is in manual failover mode and
preempt is not enabled.
Use the following command to set interface
monitoring on ge-7/0/3:

{primary:node1}
user@host# set chassis cluster redundancy-
group 1 interface-monitor ge-7/0/3 weight 255
You can initiate a failover manually with
the request command. A manual failover bumps up the
priority of the redundancy group for that member to 255.

After a manual failover, the new primary continues in that
role until there is a failback. If there is a failback, the
manual failover is lost and state election is made based
on priority and preempt settings. A failback in manual
failover mode can occur if the primary node fails or if the
threshold of a redundancy group 0 reaches 0.
Use the show command to display the status of nodes in the
cluster:

{primary:node0}
user@host> show chassis cluster status redundancy-
group 0
Output to this command indicates that node 0 is primary.

Use the request command to trigger a failover and make node
1 the primary:

{primary:node1}
user@host> request chassis cluster failover redundancy-
group 0 node 1
Use the show command to display the new status of nodes in
the cluster.

{primary:node1}
user@host> show chassis cluster status redundancy-
group 0
Output to this command shows that node 1 is now primary.

You can reset the failover for redundancy groups using
the request command. This change is propagated across the
cluster.
{primary:node1}
user@host> request chassis cluster failover reset
redundancy-group 0 node 0
Purpose:
Display chassis cluster verification options.
Action:
From the CLI, enter the show chassis cluster ? command:
{primary:node1}
user@host> show chassis cluster ?

What it Means…?
The output shows a list of all chassis cluster verification parameters.
Verify the following information:
1. Interfaces—Displays information about chassis cluster interfaces.
2. Statistics—Displays information about chassis cluster services and
    interfaces.
3. Status—Displays failover status about nodes in a cluster.
Purpose:
Display information about chassis cluster interfaces.
Action:
From the CLI, enter the show chassis cluster
interfaces command:
{primary:node1}
user@host> show chassis cluster interfaces

What it Means…?
The output shows the state the control link between the
nodes, and provides information about the link state. The
output also shows the state of the fabric interface between the
nodes and provides information about traffic on that link.
Purpose:
Display information about chassis cluster services and
interfaces.
Action:
From the CLI, enter the show chassis cluster
statistics command:
{primary:node1}
user@host> show chassis cluster statistics

What it Means…?
The output shows the control link statistics (heartbeats
sent and received), the fabric link statistics (probes sent
and received), and the number of RTOs sent and
received for services.
Purpose:
Clear displayed information about chassis cluster services
and interfaces.
Action:
From the CLI, enter the clear chassis cluster
statistics command:
{primary:node1}
user@host> clear chassis cluster statistics

What it Means…?
Cleared control-plane statistics
Cleared data-plane statistics
Purpose:
Display chassis cluster control-plane statistics.
Action:
From the CLI, enter the show chassis cluster control-plane
statistics command:
{primary:node1}
user@host> show chassis cluster control-plane
statistics

What it Means…?
The output shows the control link statistics (heartbeats
sent and received) and the fabric link statistics (probes
sent and received).
Purpose:
Clear displayed chassis cluster control plane statistics
Action:
From the CLI, enter the clear chassis cluster control—plane
statistics command:
{primary:node1}
user@host> clear chassis cluster control—plane
statistics

What it Means…?
Cleared control-plane statistics
Purpose:
Display chassis cluster data plane statistics
Action:
From the CLI, enter the show chassis cluster data-plane
statistics command:
{primary:node1}
user@host> show chassis cluster data-plane statistics

What it Means…?
The output shows the number of RTOs sent and received
for services.
Purpose:
Clear displayed chassis cluster data plane statistics
Action:
From the CLI, enter the clear chassis cluster data-plane
statistics command:
{primary:node1}
user@host> clear chassis cluster data-plane statistics

What it Means…?
Cleared data-plane statistics
Purpose:
Display the failover status of a chassis cluster.
Action:
From the CLI, enter the show chassis cluster
status command:
{primary:node1}
user@host> show chassis cluster status

What it Means…?
The output shows the failover status of the chassis cluster
in addition to information about the chassis cluster
redundancy groups.
Purpose:
Clear the failover status of a chassis cluster.
Action:
From the CLI, enter the clear chassis cluster failover-
count command:
{primary:node1}
user@host> clear chassis cluster failover-count

What it Means…?
Cleared failover-count for all redundancy-groups
Purpose:
Display the failover status of a chassis cluster redundancy
group.
Action:
From the CLI, enter the show chassis cluster status
redundancy-group command:
{primary:node1}
user@host> show chassis cluster status redundancy-group
2

What it Means..?
The output shows state and priority of both nodes in a cluster
and indicates whether the primary has been preempted or
whether there has been a manual failover.
To upgrade a chassis cluster:

 Load the new image file on node 0.
 Perform the image upgrade without rebooting the node
  by entering:
user@host> request system software add <image_name>
 Load the new image file on node 1.
 Repeat Step 2.
 Reboot both nodes simultaneously.
To disable chassis cluster, enter the following
command:
{primary:node1}
user@host> set chassis cluster disable reboot

Successfully disabled chassis cluster. Going to reboot
now. After the system reboots, the chassis cluster is
disabled.
Chassis Cluster Configuration

Weitere ähnliche Inhalte

Was ist angesagt?

VLAN Trunking Protocol
VLAN Trunking ProtocolVLAN Trunking Protocol
VLAN Trunking ProtocolNetwax Lab
 
GRE (generic routing encapsulation)
GRE (generic routing encapsulation)GRE (generic routing encapsulation)
GRE (generic routing encapsulation)Netwax Lab
 
VXLAN BGP EVPN: Technology Building Blocks
VXLAN BGP EVPN: Technology Building BlocksVXLAN BGP EVPN: Technology Building Blocks
VXLAN BGP EVPN: Technology Building BlocksAPNIC
 
CCNA 2 Routing and Switching v5.0 Chapter 6
CCNA 2 Routing and Switching v5.0 Chapter 6CCNA 2 Routing and Switching v5.0 Chapter 6
CCNA 2 Routing and Switching v5.0 Chapter 6Nil Menon
 
CCNA ppt Day 1
CCNA ppt Day 1CCNA ppt Day 1
CCNA ppt Day 1VISHNU N
 
VRF (virtual routing and forwarding)
VRF (virtual routing and forwarding)VRF (virtual routing and forwarding)
VRF (virtual routing and forwarding)Netwax Lab
 
Bidirectional Forwarding Detection (BFD)
Bidirectional Forwarding Detection (BFD) Bidirectional Forwarding Detection (BFD)
Bidirectional Forwarding Detection (BFD) KHNOG
 
Cisco commands List for Beginners (CCNA, CCNP)
Cisco commands List for Beginners (CCNA, CCNP)Cisco commands List for Beginners (CCNA, CCNP)
Cisco commands List for Beginners (CCNA, CCNP)DH Da Lat
 
Vxlan deep dive session rev0.5 final
Vxlan deep dive session rev0.5   finalVxlan deep dive session rev0.5   final
Vxlan deep dive session rev0.5 finalKwonSun Bae
 
CCNA 2 Routing and Switching v5.0 Chapter 7
CCNA 2 Routing and Switching v5.0 Chapter 7CCNA 2 Routing and Switching v5.0 Chapter 7
CCNA 2 Routing and Switching v5.0 Chapter 7Nil Menon
 

Was ist angesagt? (20)

Vpc notes
Vpc notesVpc notes
Vpc notes
 
Router commands
Router commandsRouter commands
Router commands
 
VLAN Trunking Protocol
VLAN Trunking ProtocolVLAN Trunking Protocol
VLAN Trunking Protocol
 
GRE (generic routing encapsulation)
GRE (generic routing encapsulation)GRE (generic routing encapsulation)
GRE (generic routing encapsulation)
 
Chapter 10 - DHCP
Chapter 10 - DHCPChapter 10 - DHCP
Chapter 10 - DHCP
 
VXLAN BGP EVPN: Technology Building Blocks
VXLAN BGP EVPN: Technology Building BlocksVXLAN BGP EVPN: Technology Building Blocks
VXLAN BGP EVPN: Technology Building Blocks
 
CCNA 2 Routing and Switching v5.0 Chapter 6
CCNA 2 Routing and Switching v5.0 Chapter 6CCNA 2 Routing and Switching v5.0 Chapter 6
CCNA 2 Routing and Switching v5.0 Chapter 6
 
CCNA ppt Day 1
CCNA ppt Day 1CCNA ppt Day 1
CCNA ppt Day 1
 
EVPN Introduction
EVPN IntroductionEVPN Introduction
EVPN Introduction
 
03 ospf
03 ospf 03 ospf
03 ospf
 
Nxll26 bgp ii
Nxll26 bgp iiNxll26 bgp ii
Nxll26 bgp ii
 
VRF (virtual routing and forwarding)
VRF (virtual routing and forwarding)VRF (virtual routing and forwarding)
VRF (virtual routing and forwarding)
 
Bidirectional Forwarding Detection (BFD)
Bidirectional Forwarding Detection (BFD) Bidirectional Forwarding Detection (BFD)
Bidirectional Forwarding Detection (BFD)
 
Cisco commands List for Beginners (CCNA, CCNP)
Cisco commands List for Beginners (CCNA, CCNP)Cisco commands List for Beginners (CCNA, CCNP)
Cisco commands List for Beginners (CCNA, CCNP)
 
Vxlan deep dive session rev0.5 final
Vxlan deep dive session rev0.5   finalVxlan deep dive session rev0.5   final
Vxlan deep dive session rev0.5 final
 
Ccna command
Ccna commandCcna command
Ccna command
 
ccna networking ppt
ccna networking pptccna networking ppt
ccna networking ppt
 
HSRP ccna
HSRP ccna HSRP ccna
HSRP ccna
 
Ipsec vpn v0.1
Ipsec vpn v0.1Ipsec vpn v0.1
Ipsec vpn v0.1
 
CCNA 2 Routing and Switching v5.0 Chapter 7
CCNA 2 Routing and Switching v5.0 Chapter 7CCNA 2 Routing and Switching v5.0 Chapter 7
CCNA 2 Routing and Switching v5.0 Chapter 7
 

Ähnlich wie Chassis Cluster Configuration

ASA Firewall Interview- Questions & Answers
ASA Firewall Interview- Questions & AnswersASA Firewall Interview- Questions & Answers
ASA Firewall Interview- Questions & AnswersNetProtocol Xpert
 
Important cisco-chow-commands
Important cisco-chow-commandsImportant cisco-chow-commands
Important cisco-chow-commandsssusere31b5c
 
HA, SRX Cluster & Redundancy Groups
HA, SRX Cluster & Redundancy GroupsHA, SRX Cluster & Redundancy Groups
HA, SRX Cluster & Redundancy GroupsKashif Latif
 
CMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAM
CMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAMCMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAM
CMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAMHamesKellor
 
Basic Networking
Basic NetworkingBasic Networking
Basic NetworkingCEC Landran
 
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...Tarun Khaneja
 
Cognex In-Sight - Network Settings.pdf
Cognex In-Sight - Network Settings.pdfCognex In-Sight - Network Settings.pdf
Cognex In-Sight - Network Settings.pdfDiogoCampezatto
 
DEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENT
DEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENTDEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENT
DEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENTFelipe Prado
 
Introduction 140318015826-phpapp01
Introduction 140318015826-phpapp01Introduction 140318015826-phpapp01
Introduction 140318015826-phpapp01amit singh
 
International Journal of Computational Engineering Research(IJCER)
International Journal of Computational Engineering Research(IJCER)International Journal of Computational Engineering Research(IJCER)
International Journal of Computational Engineering Research(IJCER)ijceronline
 
VMware vSphere Networking deep dive
VMware vSphere Networking deep diveVMware vSphere Networking deep dive
VMware vSphere Networking deep diveSanjeev Kumar
 
VMware vSphere Networking deep dive
VMware vSphere Networking deep diveVMware vSphere Networking deep dive
VMware vSphere Networking deep diveVepsun Technologies
 
CCNA-lab-Manual.pdf
CCNA-lab-Manual.pdfCCNA-lab-Manual.pdf
CCNA-lab-Manual.pdfDrPreethiD1
 
manual on networking cabling with pratical guide
manual on networking cabling with pratical guidemanual on networking cabling with pratical guide
manual on networking cabling with pratical guideNuhuSamaila
 
Basic Introduction to Technology (networking).pdf
Basic Introduction to Technology (networking).pdfBasic Introduction to Technology (networking).pdf
Basic Introduction to Technology (networking).pdftthind
 

Ähnlich wie Chassis Cluster Configuration (20)

ASA Firewall Interview- Questions & Answers
ASA Firewall Interview- Questions & AnswersASA Firewall Interview- Questions & Answers
ASA Firewall Interview- Questions & Answers
 
Important cisco-chow-commands
Important cisco-chow-commandsImportant cisco-chow-commands
Important cisco-chow-commands
 
HA, SRX Cluster & Redundancy Groups
HA, SRX Cluster & Redundancy GroupsHA, SRX Cluster & Redundancy Groups
HA, SRX Cluster & Redundancy Groups
 
Dc fabric path
Dc fabric pathDc fabric path
Dc fabric path
 
CMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAM
CMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAMCMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAM
CMIT 350 FINAL EXAM CCNA CERTIFICATION PRACTICE EXAM
 
rain technology
rain technology rain technology
rain technology
 
Nic bonding
Nic bonding Nic bonding
Nic bonding
 
Basic Networking
Basic NetworkingBasic Networking
Basic Networking
 
TCP/IP 3RD SEM.2012 AUG.ASSIGNMENT
TCP/IP 3RD SEM.2012 AUG.ASSIGNMENTTCP/IP 3RD SEM.2012 AUG.ASSIGNMENT
TCP/IP 3RD SEM.2012 AUG.ASSIGNMENT
 
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...
 
Cognex In-Sight - Network Settings.pdf
Cognex In-Sight - Network Settings.pdfCognex In-Sight - Network Settings.pdf
Cognex In-Sight - Network Settings.pdf
 
lecciones ccna3
lecciones ccna3lecciones ccna3
lecciones ccna3
 
DEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENT
DEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENTDEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENT
DEF CON 23 - Ronny Bull and Jeanna Matthews - exploring layer 2 - DOCUMENT
 
Introduction 140318015826-phpapp01
Introduction 140318015826-phpapp01Introduction 140318015826-phpapp01
Introduction 140318015826-phpapp01
 
International Journal of Computational Engineering Research(IJCER)
International Journal of Computational Engineering Research(IJCER)International Journal of Computational Engineering Research(IJCER)
International Journal of Computational Engineering Research(IJCER)
 
VMware vSphere Networking deep dive
VMware vSphere Networking deep diveVMware vSphere Networking deep dive
VMware vSphere Networking deep dive
 
VMware vSphere Networking deep dive
VMware vSphere Networking deep diveVMware vSphere Networking deep dive
VMware vSphere Networking deep dive
 
CCNA-lab-Manual.pdf
CCNA-lab-Manual.pdfCCNA-lab-Manual.pdf
CCNA-lab-Manual.pdf
 
manual on networking cabling with pratical guide
manual on networking cabling with pratical guidemanual on networking cabling with pratical guide
manual on networking cabling with pratical guide
 
Basic Introduction to Technology (networking).pdf
Basic Introduction to Technology (networking).pdfBasic Introduction to Technology (networking).pdf
Basic Introduction to Technology (networking).pdf
 

Mehr von Kashif Latif

Linear Programming Application
Linear Programming ApplicationLinear Programming Application
Linear Programming ApplicationKashif Latif
 
Analysis of Variance
Analysis of VarianceAnalysis of Variance
Analysis of VarianceKashif Latif
 
Core 2 Duo Processor
Core 2 Duo ProcessorCore 2 Duo Processor
Core 2 Duo ProcessorKashif Latif
 
SRX3600 Cluster & IDP
SRX3600 Cluster & IDPSRX3600 Cluster & IDP
SRX3600 Cluster & IDPKashif Latif
 
Routing Polices And Firewall Filter
Routing Polices And Firewall FilterRouting Polices And Firewall Filter
Routing Polices And Firewall FilterKashif Latif
 
Routing Information Protocol
Routing Information ProtocolRouting Information Protocol
Routing Information ProtocolKashif Latif
 
Open Shortest Path First
Open Shortest Path FirstOpen Shortest Path First
Open Shortest Path FirstKashif Latif
 
Link Aggregation Control Protocol
Link Aggregation Control ProtocolLink Aggregation Control Protocol
Link Aggregation Control ProtocolKashif Latif
 
Label Distribution Protocol
Label Distribution ProtocolLabel Distribution Protocol
Label Distribution ProtocolKashif Latif
 
Ex8216 Core Switch
Ex8216 Core SwitchEx8216 Core Switch
Ex8216 Core SwitchKashif Latif
 
Difference Between XFP & SFP
Difference Between XFP & SFPDifference Between XFP & SFP
Difference Between XFP & SFPKashif Latif
 
Border Gateway Protocol
Border Gateway ProtocolBorder Gateway Protocol
Border Gateway ProtocolKashif Latif
 

Mehr von Kashif Latif (16)

Linear Programming Application
Linear Programming ApplicationLinear Programming Application
Linear Programming Application
 
Analysis of Variance
Analysis of VarianceAnalysis of Variance
Analysis of Variance
 
Cyber Space
Cyber SpaceCyber Space
Cyber Space
 
DHCP
DHCPDHCP
DHCP
 
Core 2 Duo Processor
Core 2 Duo ProcessorCore 2 Duo Processor
Core 2 Duo Processor
 
OSI Layers
OSI LayersOSI Layers
OSI Layers
 
SRX3600 Cluster & IDP
SRX3600 Cluster & IDPSRX3600 Cluster & IDP
SRX3600 Cluster & IDP
 
Routing Polices And Firewall Filter
Routing Polices And Firewall FilterRouting Polices And Firewall Filter
Routing Polices And Firewall Filter
 
Routing Information Protocol
Routing Information ProtocolRouting Information Protocol
Routing Information Protocol
 
Open Shortest Path First
Open Shortest Path FirstOpen Shortest Path First
Open Shortest Path First
 
MX960 Router
MX960 RouterMX960 Router
MX960 Router
 
Link Aggregation Control Protocol
Link Aggregation Control ProtocolLink Aggregation Control Protocol
Link Aggregation Control Protocol
 
Label Distribution Protocol
Label Distribution ProtocolLabel Distribution Protocol
Label Distribution Protocol
 
Ex8216 Core Switch
Ex8216 Core SwitchEx8216 Core Switch
Ex8216 Core Switch
 
Difference Between XFP & SFP
Difference Between XFP & SFPDifference Between XFP & SFP
Difference Between XFP & SFP
 
Border Gateway Protocol
Border Gateway ProtocolBorder Gateway Protocol
Border Gateway Protocol
 

Kürzlich hochgeladen

Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxraviapr7
 
NOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdf
NOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdfNOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdf
NOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdfSumit Tiwari
 
How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17Celine George
 
The Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George WellsThe Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George WellsEugene Lysak
 
How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17Celine George
 
Philosophy of Education and Educational Philosophy
Philosophy of Education  and Educational PhilosophyPhilosophy of Education  and Educational Philosophy
Philosophy of Education and Educational PhilosophyShuvankar Madhu
 
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdfMaximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdfTechSoup
 
Presentation on the Basics of Writing. Writing a Paragraph
Presentation on the Basics of Writing. Writing a ParagraphPresentation on the Basics of Writing. Writing a Paragraph
Presentation on the Basics of Writing. Writing a ParagraphNetziValdelomar1
 
Quality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICEQuality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICESayali Powar
 
3.21.24 The Origins of Black Power.pptx
3.21.24  The Origins of Black Power.pptx3.21.24  The Origins of Black Power.pptx
3.21.24 The Origins of Black Power.pptxmary850239
 
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptxSandy Millin
 
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxPISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxEduSkills OECD
 
How to Filter Blank Lines in Odoo 17 Accounting
How to Filter Blank Lines in Odoo 17 AccountingHow to Filter Blank Lines in Odoo 17 Accounting
How to Filter Blank Lines in Odoo 17 AccountingCeline George
 
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxPractical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxKatherine Villaluna
 
Patterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxPatterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxMYDA ANGELICA SUAN
 
The Singapore Teaching Practice document
The Singapore Teaching Practice documentThe Singapore Teaching Practice document
The Singapore Teaching Practice documentXsasf Sfdfasd
 
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdfP4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdfYu Kanazawa / Osaka University
 
3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx
3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx
3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptxmary850239
 
Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesMohammad Hassany
 

Kürzlich hochgeladen (20)

Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptx
 
NOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdf
NOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdfNOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdf
NOTES OF DRUGS ACTING ON NERVOUS SYSTEM .pdf
 
Personal Resilience in Project Management 2 - TV Edit 1a.pdf
Personal Resilience in Project Management 2 - TV Edit 1a.pdfPersonal Resilience in Project Management 2 - TV Edit 1a.pdf
Personal Resilience in Project Management 2 - TV Edit 1a.pdf
 
How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17How to Make a Field read-only in Odoo 17
How to Make a Field read-only in Odoo 17
 
The Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George WellsThe Stolen Bacillus by Herbert George Wells
The Stolen Bacillus by Herbert George Wells
 
How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17How to Add a New Field in Existing Kanban View in Odoo 17
How to Add a New Field in Existing Kanban View in Odoo 17
 
Philosophy of Education and Educational Philosophy
Philosophy of Education  and Educational PhilosophyPhilosophy of Education  and Educational Philosophy
Philosophy of Education and Educational Philosophy
 
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdfMaximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
Maximizing Impact_ Nonprofit Website Planning, Budgeting, and Design.pdf
 
Presentation on the Basics of Writing. Writing a Paragraph
Presentation on the Basics of Writing. Writing a ParagraphPresentation on the Basics of Writing. Writing a Paragraph
Presentation on the Basics of Writing. Writing a Paragraph
 
Quality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICEQuality Assurance_GOOD LABORATORY PRACTICE
Quality Assurance_GOOD LABORATORY PRACTICE
 
3.21.24 The Origins of Black Power.pptx
3.21.24  The Origins of Black Power.pptx3.21.24  The Origins of Black Power.pptx
3.21.24 The Origins of Black Power.pptx
 
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
 
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptxPISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
PISA-VET launch_El Iza Mohamedou_19 March 2024.pptx
 
How to Filter Blank Lines in Odoo 17 Accounting
How to Filter Blank Lines in Odoo 17 AccountingHow to Filter Blank Lines in Odoo 17 Accounting
How to Filter Blank Lines in Odoo 17 Accounting
 
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxPractical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
 
Patterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxPatterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptx
 
The Singapore Teaching Practice document
The Singapore Teaching Practice documentThe Singapore Teaching Practice document
The Singapore Teaching Practice document
 
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdfP4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
P4C x ELT = P4ELT: Its Theoretical Background (Kanazawa, 2024 March).pdf
 
3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx
3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx
3.19.24 Urban Uprisings and the Chicago Freedom Movement.pptx
 
Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming Classes
 

Chassis Cluster Configuration

  • 2. Chassis clustering provides network node redundancy by grouping a pair of the same kind of supported J-series devices or SRX-series devices into a cluster. The devices must be running JUNOS software. A chassis cluster takes the two SRX devices and represents them as a single device.  It consist of two important models that are: 1. active/active 2. active/passive
  • 3. The basic active/passive chassis cluster consists of two devices: 1. One device actively provides routing, firewall, NAT, VPN, and security services, along with maintaining control of the chassis cluster. 2. The other device passively maintains its state for cluster failover capabilities should the active device become inactive.
  • 4. To create an SRX-series chassis cluster, you must physically connect a pair of the same kind of supported SRX-series devices back-to-back over a pair of Gigabit Ethernet connections or a pair of 10-Gigabit Ethernet connections. The connection that serves as the control link must be the built-in controller port on each device. The fabric link connection can be a combination of any pair of Gigabit Ethernet interfaces on the devices.
  • 5. Control Ports Fabric Fabric Link Link Cable
  • 6. After wiring the two devices together, you use CLI operational mode commands to enable chassis clustering by assigning a cluster ID and node ID on each chassis in the cluster. The cluster ID is the same on both nodes. To do this, you connect to the console port on the device that will be the primary, give it a node ID, and identify the cluster it will belong to, then reboot the system. Now you then connect the console port to the other device, give it a node ID, and assign it the same cluster ID you gave to the first node, then reboot the system.
  • 7. The fxp0 interfaces, when configured for active/active operations, function like standard management interfaces on SRX-series devices and allow network access to each node in the cluster. You must, however, first connect to each node through the console port and assign a unique IP address to each fxp0 interface.
  • 8. The fabric is the data link between the nodes and is used to forward traffic between the chassis. Traffic arriving on a node that needs to be processed on the other is forwarded over the fabric data link. Similarly, traffic processed on a node that needs to exit through an interface on the other node is forwarded over the fabric. The fabric also provides for synchronization of session state objects created by operations such as authentication, Network Address Translation (NAT), Application Layer Gateways (ALGs), and IP Security (IPsec) sessions. The fabric link can be any pair of Gigabit Ethernet interfaces spanning the cluster.
  • 9. The control interfaces provide the control link between the two nodes in the cluster and are used for routing updates and for control plane signal traffic, such as heartbeat and threshold information that triggers node failover. The control link is also used to synchronize the configuration between the nodes. When you submit configuration statements to the cluster, the configuration is automatically synchronized over the control link.
  • 10. 1. Physically connect a pair of SRX-series devices together 2. Connect the initial node to the console port 3. Configure the control ports 4. Use CLI operational mode commands to enable clustering 5. Repeat step 2, 3 & 4 for other device 6. Configure the management interfaces on the cluster 7. Configure the cluster 8. Initiate manual failover 9. Configure conditional route advertisement over redundant Ethernet interfaces 10. Verify the configuration
  • 11. After connecting the two devices together, you configure a cluster ID and a node ID.  A cluster ID identifies the cluster that the two nodes belong to.  A node ID identifies a unique node within a cluster.  You can deploy up to 15 clusters in a Layer 2 domain. Each cluster is defined by a cluster-id value within the range of 1 through 15. A device can belong to only one cluster at any given time. Nodes in a cluster are numbered 0 and 1.
  • 12. To set the node IDs and cluster IDs, connect to each device through the console port and enter the following operational commands, then reboot the system. Enter the cluster ID and node ID information for the first node. If you want redundancy groups to be primary on this node when priority settings for both nodes are the same, make it node 0. user@host> set chassis cluster node 0 cluster-id 1 warning: A reboot is required for chassis cluster to be enabled
  • 13. Enter the cluster ID and node ID for the other node. If you want redundancy groups to be secondary on this node when priority settings for both nodes are the same, make it node1. user@host> set chassis cluster node 1 cluster-id 1 reboot Successfully enabled chassis cluster. Going to reboot now.
  • 14. Use the show chassis cluster status operational command to view node status. user@host# show chassis cluster status When you complete the chassis cluster basic configuration, any subsequent configuration changes you make are automatically synchronized on both nodes.
  • 15. You must assign a unique IP address to each node in the cluster to provide network management access. This configuration is not replicated across the two nodes. In an SRX-series chassis cluster, the fxp0 interface is a port on the Routing Engine (RE) card.
  • 16. From the console port connection to the device you want to designate as the primary node, in configuration mode enter the following commands to name the node node0- router and assign IP address 10.1.1.1/24 to it: user@host# set groups node0 system host-name node0-router user@host# set groups node0 interfaces fxp0 unit 0 family inet address 10.1.1.1/24
  • 17. From the console port connection to the device you want to designate the secondary node, in configuration mode enter the following commands to name the node node1-router and assign IP address 10.1.1.2/24 to it: user@host# set groups node1 system host-name node1- router user@host# set groups node1 interfaces fxp0 unit 0 family inet address 10.1.1.2/24 Enter the following command in configuration mode to apply these unique configurations to the appropriate node. This configuration is not replicated across the two nodes. user@host# set apply-groups
  • 18. For the chassis cluster configuration, you specify the number of redundant Ethernet interfaces that the cluster contains and the information used to monitor the “health” of the cluster. You must configure the redundant Ethernet interfaces count for the cluster in order for the redundant Ethernet interfaces that you configure to be recognized. Use the following command in configuration mode to define the number of redundant Ethernet interfaces for the cluster: user@host# set chassis cluster reth-count 3
  • 19. The fabric is the back-to-back data connection between the nodes in a cluster. Traffic on one node that needs to be processed on the other node or to exit through an interface on the other node passes over the fabric. Session state information also passes over the fabric. In an SRX-series chassis cluster, you can configure any pair of Gigabit Ethernet interfaces or any pair of 10- Gigabit interfaces to serve as the fabric between nodes. You cannot configure filters, policies, or services on the fabric interface.
  • 20. Enter the following commands to join ge-0/0/1 on one node in the cluster and ge-7/0/1 on the other to form the fabric: {primary:node0} user@host# set interfaces fab0 fabric-options member-interfaces ge-0/0/1 {secondary:node1} user@host# set interfaces fab1 fabric-options member-interfaces ge-7/0/1
  • 21. A redundancy group is an abstract entity (extracting common features from specific object) that includes and manages a collection of objects. A redundancy group can be primary on only one node at a time. Before you can create redundant Ethernet interfaces you must create their redundancy groups.
  • 22. Use the following command in configuration mode to specify the number of gratuitous Address Resolution Protocol (ARP) requests that an interface can send to notify other network devices of its presence after the redundancy group it belongs to has failed over: {primary:node1} user@host# set chassis cluster redundancy-group 1 gratuitous-arp-count 4
  • 23. Use the following command in configuration mode to identify an interface to be monitored by a specific redundancy group and give it a weight. You can configure a redundancy group to monitor any interfaces, not just those belonging to its redundant Ethernet interfaces. {primary:node1} user@host# set chassis cluster redundancy-group 1 interface-monitor fe-3/1/1/1 weight 100
  • 24. Use the following commands in configuration mode to specify a redundancy group's priority for primacy on each node of the cluster. The higher number takes precedence. {primary:node1} user@host# set chassis cluster redundancy-group 1 node 1 priority 100 {secondary:node0} user@host# set chassis cluster redundancy-group 1 node 0 priority 200
  • 25. Use the following command in configuration mode to specify if a node with a better (higher) priority can initiate a failover to become primary for the redundancy group: {primary:node1} user@host# set chassis cluster redundancy-group 1 preempt
  • 26. A redundant Ethernet interface is a pseudo interface that contains two physical interfaces, one from each node of the cluster. To create a redundant Ethernet interface, you configure the two physical interfaces independently. You configure the rest of the configuration that pertains to them at the level of the redundant Ethernet interface, and each of the child interfaces inherits this configuration.
  • 27. Use the following commands to bind redundant child physical interfaces to reth1: {primary:node1} user@host# set interfaces ge-0/0/0 gigether-options redundant-parent reth1 {primary:node1} user@host# set interfaces ge-7/0/0 gigether-options redundant-parent reth1 {primary:node1} user@host# set interfaces fe-1/0/0 fast-ether-options redundant-parent reth1 {primary:node1} user@host# set interfaces fe-8/0/0 fast-ether-options redundant-parent reth1
  • 28. Use the following commands to: Add reth 1 to redundancy group 1 Set the MTU (Maximum Transmission Unit) size to 1500 bytes Assign IP address 10.1.1.3/24 to reth1 {primary:node1} user@host# set interfaces reth1 redundant-ether-options redundancy-group 1 {primary:node1} user@host# set interfaces reth1 unit 0 family inet mtu 1500 {primary:node1} user@host# set interfaces reth1 unit 0 family inet address 10.1.1.3/24
  • 29. Use the following command to associate reth1.0 with a security zone named Trust. Security zone configuration is the same for redundant Ethernet interfaces as for any other interface. {primary:node1} user@host# set security zones security-zone Trust interfaces reth1.0
  • 30. Redundancy group failover is triggered by the results from monitoring the health of interfaces that belong to the redundancy group. When you assign a weight to an interface to be monitored, the system monitors the interface for availability. If a physical interface fails, the weight is deducted from the corresponding redundancy group's threshold. Every redundancy group has a threshold of 255. If the threshold hits 0, a failover is triggered. Failover is triggered even if the redundancy group is in manual failover mode and preempt is not enabled.
  • 31. Use the following command to set interface monitoring on ge-7/0/3: {primary:node1} user@host# set chassis cluster redundancy- group 1 interface-monitor ge-7/0/3 weight 255
  • 32. You can initiate a failover manually with the request command. A manual failover bumps up the priority of the redundancy group for that member to 255. After a manual failover, the new primary continues in that role until there is a failback. If there is a failback, the manual failover is lost and state election is made based on priority and preempt settings. A failback in manual failover mode can occur if the primary node fails or if the threshold of a redundancy group 0 reaches 0.
  • 33. Use the show command to display the status of nodes in the cluster: {primary:node0} user@host> show chassis cluster status redundancy- group 0 Output to this command indicates that node 0 is primary. Use the request command to trigger a failover and make node 1 the primary: {primary:node1} user@host> request chassis cluster failover redundancy- group 0 node 1
  • 34. Use the show command to display the new status of nodes in the cluster. {primary:node1} user@host> show chassis cluster status redundancy- group 0 Output to this command shows that node 1 is now primary. You can reset the failover for redundancy groups using the request command. This change is propagated across the cluster. {primary:node1} user@host> request chassis cluster failover reset redundancy-group 0 node 0
  • 35. Purpose: Display chassis cluster verification options. Action: From the CLI, enter the show chassis cluster ? command: {primary:node1} user@host> show chassis cluster ? What it Means…? The output shows a list of all chassis cluster verification parameters. Verify the following information: 1. Interfaces—Displays information about chassis cluster interfaces. 2. Statistics—Displays information about chassis cluster services and interfaces. 3. Status—Displays failover status about nodes in a cluster.
  • 36. Purpose: Display information about chassis cluster interfaces. Action: From the CLI, enter the show chassis cluster interfaces command: {primary:node1} user@host> show chassis cluster interfaces What it Means…? The output shows the state the control link between the nodes, and provides information about the link state. The output also shows the state of the fabric interface between the nodes and provides information about traffic on that link.
  • 37. Purpose: Display information about chassis cluster services and interfaces. Action: From the CLI, enter the show chassis cluster statistics command: {primary:node1} user@host> show chassis cluster statistics What it Means…? The output shows the control link statistics (heartbeats sent and received), the fabric link statistics (probes sent and received), and the number of RTOs sent and received for services.
  • 38. Purpose: Clear displayed information about chassis cluster services and interfaces. Action: From the CLI, enter the clear chassis cluster statistics command: {primary:node1} user@host> clear chassis cluster statistics What it Means…? Cleared control-plane statistics Cleared data-plane statistics
  • 39. Purpose: Display chassis cluster control-plane statistics. Action: From the CLI, enter the show chassis cluster control-plane statistics command: {primary:node1} user@host> show chassis cluster control-plane statistics What it Means…? The output shows the control link statistics (heartbeats sent and received) and the fabric link statistics (probes sent and received).
  • 40. Purpose: Clear displayed chassis cluster control plane statistics Action: From the CLI, enter the clear chassis cluster control—plane statistics command: {primary:node1} user@host> clear chassis cluster control—plane statistics What it Means…? Cleared control-plane statistics
  • 41. Purpose: Display chassis cluster data plane statistics Action: From the CLI, enter the show chassis cluster data-plane statistics command: {primary:node1} user@host> show chassis cluster data-plane statistics What it Means…? The output shows the number of RTOs sent and received for services.
  • 42. Purpose: Clear displayed chassis cluster data plane statistics Action: From the CLI, enter the clear chassis cluster data-plane statistics command: {primary:node1} user@host> clear chassis cluster data-plane statistics What it Means…? Cleared data-plane statistics
  • 43. Purpose: Display the failover status of a chassis cluster. Action: From the CLI, enter the show chassis cluster status command: {primary:node1} user@host> show chassis cluster status What it Means…? The output shows the failover status of the chassis cluster in addition to information about the chassis cluster redundancy groups.
  • 44. Purpose: Clear the failover status of a chassis cluster. Action: From the CLI, enter the clear chassis cluster failover- count command: {primary:node1} user@host> clear chassis cluster failover-count What it Means…? Cleared failover-count for all redundancy-groups
  • 45. Purpose: Display the failover status of a chassis cluster redundancy group. Action: From the CLI, enter the show chassis cluster status redundancy-group command: {primary:node1} user@host> show chassis cluster status redundancy-group 2 What it Means..? The output shows state and priority of both nodes in a cluster and indicates whether the primary has been preempted or whether there has been a manual failover.
  • 46. To upgrade a chassis cluster:  Load the new image file on node 0.  Perform the image upgrade without rebooting the node by entering: user@host> request system software add <image_name>  Load the new image file on node 1.  Repeat Step 2.  Reboot both nodes simultaneously.
  • 47. To disable chassis cluster, enter the following command: {primary:node1} user@host> set chassis cluster disable reboot Successfully disabled chassis cluster. Going to reboot now. After the system reboots, the chassis cluster is disabled.