The document provides step-by-step instructions for configuring NAS (NFS) failover over a LAN using Open-E DSS. It describes setting up two servers with mirrored volumes, so that if the primary server fails, operations can fail over to the secondary server. The steps include 1) configuring the network interfaces and bonding on each server, 2) creating mirrored volumes and configuring replication on the primary and secondary servers, and 3) enabling NFS and sharing the volume to allow access from clients. This configuration provides data redundancy and high availability over a local network.
Seven years ago at LCA, Van Jacobsen introduced the concept of net channels but since then the concept of user mode networking has not hit the mainstream. There are several different user mode networking environments: Intel DPDK, BSD netmap, and Solarflare OpenOnload. Each of these provides higher performance than standard Linux kernel networking; but also creates new problems. This talk will explore the issues created by user space networking including performance, internal architecture, security and licensing.
Most of this session will focus on Kernel Module Programming. We will briefly talk about the interaction of different layers of operating system from userspace to kernel space. Starting from simple Hello World kernel modules, we will learn the development of more sophisticated modules related to device drivers and interrupt handlers. We will also briefly touch upon the shell scripts and how they can be used to extract system level information. Since, this will be a hands on session, attendees are expected to try the examples on their machines. Basic understanding of operating systems and C programming is expected for the tutorial.
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...Jim St. Leger
Thomas Monjalon, 6WIND, presents on where/how to use DPDK, the DPDK ecosystem, and the DPDK.org community.
Thomas is the community maintainer of DPDK.org.
Serial ATA (SATA) is a computer bus interface that connects host bus adapters to mass storage devices such as hard disk drives and optical drives. Serial ATA replaces the older AT Attachment standard (later referred to as Parallel ATA or PATA), offering several advantages over the older interface: reduced cable size and cost (seven conductors instead of 40 or 80), native hot swapping, faster data transfer through higher signalling rates, and more efficient transfer through an (optional) I/O queuing protocol.
Seven years ago at LCA, Van Jacobsen introduced the concept of net channels but since then the concept of user mode networking has not hit the mainstream. There are several different user mode networking environments: Intel DPDK, BSD netmap, and Solarflare OpenOnload. Each of these provides higher performance than standard Linux kernel networking; but also creates new problems. This talk will explore the issues created by user space networking including performance, internal architecture, security and licensing.
Most of this session will focus on Kernel Module Programming. We will briefly talk about the interaction of different layers of operating system from userspace to kernel space. Starting from simple Hello World kernel modules, we will learn the development of more sophisticated modules related to device drivers and interrupt handlers. We will also briefly touch upon the shell scripts and how they can be used to extract system level information. Since, this will be a hands on session, attendees are expected to try the examples on their machines. Basic understanding of operating systems and C programming is expected for the tutorial.
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...Jim St. Leger
Thomas Monjalon, 6WIND, presents on where/how to use DPDK, the DPDK ecosystem, and the DPDK.org community.
Thomas is the community maintainer of DPDK.org.
Serial ATA (SATA) is a computer bus interface that connects host bus adapters to mass storage devices such as hard disk drives and optical drives. Serial ATA replaces the older AT Attachment standard (later referred to as Parallel ATA or PATA), offering several advantages over the older interface: reduced cable size and cost (seven conductors instead of 40 or 80), native hot swapping, faster data transfer through higher signalling rates, and more efficient transfer through an (optional) I/O queuing protocol.
Oracle Database Appliance RAC in a box Some Strings AttachedFuad Arshad
Oracle Database Appliance is an engineered system that is geared towards Small and Medium businesses but has all the bells and whistles for enterprise deployments. This talk will focus on Oracle Database Appliance deployment as a consolidation platform as well as as a development platform for rapidly deploying databases. We will talk about the Deployment process , the patching process and the best practices built into The Oracle Database Appliance. We will also talk about the DBA's role for managing the ODA as well as security considerations
FIWARE Lab architecture, an open point to start the installation of a new regionFernando Lopez Aguilar
Description of the different configurations that you can use in order to install a new OpenStack node, including the minimum requirements of capacity of the hosts and the distribution of services per each host.
Practice and challenges from building IaaSShawn Zhu
It is an invited presentation for NCSC2012 (China National Conference on Social Computing) on cloud computing from industry.
It summarized what we learn on developing and operating an Infrastructure as a Service in a highly scalable manner. The service described inside the corporation is kind of dogfood that engineers work with in their daily work.
A Xen MIPS port implementation will be presented. In particular, major techniques used for cpu and memory para-virtualization on top of xen and linux will be presented. The major changes in xen hypervisor, xen tools and linux will be illustrated. The challenges, main issues we faced and solutions we applied will be discussed. Overall porting status and next steps will also be discussed.
Waupaca County and Trempealeau County have both been running ArcGIS server (AGS) web mapping applications since late 2007. The two Counties worked together throughout the implementation process. They hope to share how to plan for an AGS implementation and potential pitfalls to avoid. The session is intended to be a starting point for users planning to implement AGS web mapping applications. Topics covered will be relevant
to software versions 9.2 and 9.3.
Strata + Hadoop World 2012: HDFS: Now and FutureCloudera, Inc.
Hadoop 1.0 is a significant milestone in being the most stable and robust Hadoop release tested in production against a variety of applications. It offers improved performance, support for HBase, disk-fail-in-place, Webhdfs, etc over previous releases. The next major release, Hadoop 2.0 offers several significant HDFS improvements including new append-pipeline, federation, wire compatibility, NameNode HA, further performance improvements, etc. We describe how to take advantages of the new features and their benefits. We also discuss some of the misconceptions and myths about HDFS.
Using Linux OS stack to transform your Linux Mission Critical Applications into the Active-Active Stretched Cluster Storage with the very high performance NVMe-oF protocol. The slide deck also illustrates various failure scenarios at Networking and Storage levels, down to the very details of how Cluster RAID1 behave in those failure cases.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Assuring Contact Center Experiences for Your Customers With ThousandEyes
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported by Open-E ® DSS™
1. Step-by-Step Guide to
NAS (NFS) Failover
over a LAN (with unicast)
Supported by Open-E ® DSS™
Software Version: DSS ver. 6.00 up65
Presentation updated: March 2011
2. NAS (NFS) Failover over a LAN
Open-E DSS NAS (NFS) Failover is a fault tolerance process via NAS volume replication, that creates
mirrored data volumes.
• Data is copied in real-time, and every change is immediately mirrored from the primary server to the secondary storage server.
• In case of a failure, scheduled maintenance of the primary server, or loss of the primary data source, failover automatically
switches operations to the secondary storage server, so processes can be continued as usual.
www.open-e.com 2
3. NAS (NFS) Failover over a LAN
VOLUME REPLICATION WITH FAILOVER BETWEEN TWO SYSTEMS
WITHIN ONE LAN
Recommended Resources
• Key Hardware (two systems)
x86 compatible
RAID Controller with Battery Backup Unit
HDD‘s
Network Interface Cards
Ping Node (ping node it is any permanently (24/7) available host in the network. In particular
case the ping node function can be performed by the server storing the data on the failover
volume).
• Software
Open-E DSS V6, 2 units
Benefits
• Eliminate business disruption
• Data Redundancy over a LAN
• Switch Redundancy
Disadvantages
• High cost of solution
• Natural disasters (earthquake, fire, flood...) can destroy local systems
www.open-e.com 3
4. NAS (NFS) Failover over a LAN
• Data is written and read to System 1 (primary)
• Data is continually replicated to System 2 (secondary)
RAID System 1 RAID System 2
Primary Secondary
Heartbeat
Volume Replication
PING NODEs
Control Write Data
Read Data
www.open-e.com 4
5. NAS (NFS) Failover over a LAN
• In case system malfunction or power failure or lost network connection of the System1 (primary), the
server will send an e-mail Notification to the administrator.
• After a few seconds Automatic Failover is executed and users are switched to System 2 (secondary).
RAID System 1 RAID System 2
Primary Secondary
X
Heartbeat
PING NODEs
Control Write Data
Read Data
www.open-e.com 5
6. NAS (NFS) Failover over a LAN
• After switching, the replicated volume
is available on System 2 (secondary)
RAID System 1 RAID System 2
Primary Secondary
X
PING NODEs
Write Data
Read Data
www.open-e.com 6
7. NAS (NFS) Failover over a LAN
TO SET UP NAS (NFS) FAILOVER, PERFORM THE FOLLOWING STEPS:
1. Hardware configuration:
• Settings server names, ethernet ports and bonding on secondary and primary node
2. Configure the Secondary node:
• Create a Volume Group, NAS Volume
• Configure Volume Replication mode (destination mode) – settings mirror IP address
• NFS settings
3. Configure the Primary node
• Create a Volume Group, NAS Volume
• Configure Volume Replication mode (source mode) – settings mirror IP address, creating Volume Replication task and start
replication task.
• NFS settings,
• Create and settings new share on primary node.
4. Configure Failover (primary and secondary node)
5. Select services used in Failover
6. Configure virtual IP and Auxiliary connection
7. Start Failover Service
8. Test Failover Function
9. Run Failback Function
www.open-e.com 7
8. NAS (NFS) Failover over a LAN
Hardware Requirements:
To run the Volume Replication with Failover, two DSS systems 1. Hardware Configuration
are required. Both servers must be located and working in the
Local Area Network. See below configurations for examples:
PING NODEs
IP Address : 192.168.2.106; 192.168.2.107
Data Server (DSS1) Data Server (DSS2)
Primary node Secondary node
IP Address:192.168.0.220 IP Address:192.168.0.221
Control
Switch 1
RAID System 1 RAID System 2
Switch 2
Primary Secondary
Port used for WEB GUI management Port used for WEB GUI management
IP:192.168.0.220 eth0 eth0 IP:192.168.0.221
Volume Replication , Optional: Volume Replication ,
Auxiliary connection (Heartbeat) This path can be Auxiliary connection (Heartbeat)
IP:192.168.1.220 eth1 directly point-to-point eth1 IP:192.168.1.221
connected eth1 to eth1
Client Storage Access, Client Storage Access,
Auxiliary connection (Heartbeat)
(without the switch).
Auxiliary connection (Heartbeat)
bond0 IP:192.168.2.220 (eth2, eth3) (eth2, eth3) IP:192.168.2.221 bond0
Bonding IP Bonding IP
Volume Groups (vg00)
Volume Groups (vg00)
Virtual IP Address:192.168.10.230
NAS volume (lv00) NFS Failover/Volume Replication (eth1) NAS volume (lv00)
Share (data) Share (data)
www.open-e.com 8
9. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 1. Hardware Configuration
IP Address:192.168.0.221
After logging on the DSS V6
please go to „SETUP” tab,
„network” and „Interfaces”. In
„Server name” function enter
Server name, in this example
„dss2” and click apply button.
(All connections will be
restarted)
www.open-e.com 9
10. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 1. Hardware Configuration
IP Address:192.168.0.221
Next select eth0 interface and
change IP Address from
192.168.0.220 in field IP address
to 192.168 .0.221, and click apply
button. (This will restart network
configuration).
www.open-e.com 10
11. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 1. Hardware Configuration
IP Address:192.168.0.221
Next select eth1 interface and
change IP address from
192.168.1.220 in field IP address
to 192.168 .1.221 and click apply
button.
www.open-e.com 11
12. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 1. Hardware Configuration
IP Address:192.168.0.221
Again select „Interfaces” and in
Create new bond interface
function check two boxes with eth2
and eth3. In field Create select
bonding mode. In this example
select New balance-rr.
Next enter IP Address in field
Adress IP 192.168 .2.221,
Netmask, and click create button.
www.open-e.com 12
13. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 1. Hardware Configuration
IP Address:192.168.0.221
After reloading page on the dss2
server you have configured bond0.
Setting of the network interfaces on
the secondary node is finished.
www.open-e.com 13
14. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 1. Hardware Configuration
IP Address:192.168.0.220
After logging on the primary
node please go to „SETUP”
tab, „network” and
„Interfaces”. In „Server name”
function enter Server name. In
this example enter dss1 and
click apply button. (All
connection will be restarted).
www.open-e.com 14
15. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 1. Hardware Configuration
IP Address:192.168.0.220
Again select „Interfaces” and in
Create new bond interface
function check two boxes with eth2
and eth3. In field Create select
mode for bonding. In this example
selected New balance-rr..
Next enter IP Address in field
Address IP 192.168 .2.220,
Netmask, and click create button.
www.open-e.com 15
16. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 1. Hardware Configuration
IP Address:192.168.0.220
After reloading page on the dss1
server you have configured
bond0. Setting of the network
interfaces on the secondary node is
finished.
www.open-e.com 16
17. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 2. Configure the Secondary node
IP Address:192.168.0.221
Under the
„CONFIGURATION” tab,
select „volume manager” and
next Vol. Groups.
Volume Groups (vg00)
In Unit manager function add
the selected physical units
(Unit S000 or other) to create a
new volume group (in this case,
vg00) and click apply button
www.open-e.com 17
18. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 2. Configure the Secondary node
IP Address:192.168.0.221
Select the appropriate volume
group (vg00) from the list on the
left and create a new NAS
volume of the required size.
This logical volume will be the
destination of the replication
process.
Next check the box with Use
volume replication
After assigning an appropriate
amount of space for the NAS
volume, click the apply button
www.open-e.com 18
19. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 2. Configure the Secondary node
IP Address:192.168.0.221
The destination NAS Volume is
now configured.
NAS volume (lv0000)
www.open-e.com 19
20. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 2. Configure the Secondary node
IP Address:192.168.0.221
Now, select the Vol.
replication and check the box
under Destination and click the
apply button
Next, under Mirror Server IP
function, enter the IP address of
the Primary node (in our
example, this would be
192.168.1.220) and click the
apply button
NOTE:
The Mirror server IP Address must be on the same
subnet in order for the replication to communicate.
VPN connections can work if you are not using a
NAT. Please follow example:
•Source: 192.168.1.220
•Destination: 192.168.1.221
www.open-e.com 20
21. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 2. Configure the Secondary node
IP Address:192.168.0.221
Choose „CONFIGURATION”,
and „NAS settings” from the
menu on the secondary node
In the NAS settings function,
check the box Use NFS, click
apply to confirm.
www.open-e.com 21
22. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Under the „CONFIGURATION”
tab, select „volume manager”
and next „Vol. Groups”
Add the selected physical units
(Unit MD0 or other) to create a
new volume group (in this case,
vg00) and click apply button
Volume Groups (vg00)
www.open-e.com 22
23. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Select the appropriate volume
group (vg00) from the list on the
left and create a new NAS
volume of the required size.
This logical volume will be the
source of the replication
process
Next , check box Use volume
replication
After assigning an appropriate
amount of space for the NAS
volume, click the apply button
NOTE:
The source and destination volumes must be of
identical size.
www.open-e.com 23
24. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
The source NAS Volume is now
configured.
NAS volume (lv0000)
www.open-e.com 24
25. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Now, select Vol. replication,
and check the box under
Source and click the apply
button
Next , under Mirror Server IP
function, enter the IP address of
the Secondary node (in our
example this would be
192.168.1.221) and click the
apply button
www.open-e.com 25
26. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Enter the task name in field
Task name next click on the
button
In the Destination volume
field select the appropriate
volume (in this example,
lv0000) and click create to
confirm
www.open-e.com 26
27. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Now, in the Replication task
manager function, click on
button under to start the
Replication task on the Primary
node
www.open-e.com 27
28. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
In the Replication tasks
manager function information
is available about the current
running replication task.
www.open-e.com 28
29. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Under the „STATUS” tab,
select „tasks” and Volume
Replication
Click on the button with
task name (in this case
MirrorTask) to display detailed
information on the current
replication task
NOTE:
Please allow the replication task to complete
similar to above with status being “Consistent”
before writing to the NAS Logical Volume via NFS.
www.open-e.com 29
30. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Choose „CONFIGURATION”,
and „NAS settings” from the
menu
In the NAS settings function,
check the box Use NFS, click
apply to confirm.
www.open-e.com 30
31. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
Next, choose
„CONFIGURATION”, „NAS
resources” and „Shares” from
the menu.
Enter share name in field
„Name” and click apply to
confirm.
www.open-e.com 31
32. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 3. Configure the Primary node
IP Address:192.168.0.220
In the NFS share acces
function, check the box Use
NFS, and click apply to
confirm.
www.open-e.com 32
33. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 4. Configure Failover
IP Address:192.168.0.220
Next choose „SETUP”,
„network”, end select Failover
on the primary node.
In the Failover configuration
function, check the box Enable
Failover functionality. Select
Network connection mode (in
this example Unicast) and
select Network interface for
unicast (bond0). Next enter
the Secondary node IP and the
Ping Node IP (must be on the
same subnet) and click the
apply button.
www.open-e.com 33
34. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 4. Configure Failover
IP Address:192.168.0.221
Now, select Failover on the
secondary node
Now, in Failover
configuration function , check
the box Enable Failover
functionality. Select Network
connection mode (in this
example Unicast) and select
Network interface for unicast
(bond0). After choose
Secondary node on localhost
enter Primary node IP address
and click the apply button
www.open-e.com 34
35. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 5. Configure Virtual IP and Auxillary connection
IP Address:192.168.0.220
Now, select the bond0 within
Failover. In the Virtual IP
Settings function check box
Enable virtual IP and enter IP
address, Netmask, Broadcast,
and click the apply button.
By setting the address of the
secondary node in a Failover
configuration, automatic
detection of the interface for
communication. This step is
necessary to complement the
destination IP address used in
unicast.
NOTE:
There need to be at least two auxiliary connections. The interface with
the virtual IP can also serve as one of the auxiliary connections. Please
set the Virtual IP Address in a different network subnet then the
physical IP Address. To have additional Failover systems, please set
this pair in a different network subnet from the other Failover systems. If
the virtual IP must be in the same network subnet, there will be extra
configuration steps required. Please refer to other document which
describe configuration with static routing.
www.open-e.com 35
36. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 5. Configure Virtual IP and Auxillary connection
IP Address:192.168.0.220
Now, select the eth1 within
Failover.
In the Auxiliary connection
function check box Use this
network interface to
communicate between the
nodes next enter IP address for
Unicast remote IP and click the
apply button.
www.open-e.com 36
37. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 5. Configure Virtual IP and Auxillary connection
IP Address:192.168.0.221
Choose, „SETUP” and
„network” and „Interfaces”
from the menu
Now, select the bond0 within
Failover.
In the Virtual IP Settings
function check the box Enable
virtual IP and enter IP
address, Netmask, Broadcast,
and click the apply button.
By setting the address of the
primary node in a Failover
configuration, automatic
detection of the interface for
communication. This step is
necessary to complement the
destination IP address used in
unicast.
www.open-e.com 37
38. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 5. Configure Virtual IP and Auxillary connection
IP Address:192.168.0.221
Now, select the eth1 within
Failover.
In the Auxiliary connection
function check box Use this
network interface to
communicate between the
nodes next enter IP address for
Unicast remote IP and click the
apply button.
www.open-e.com 38
39. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 6. Select services used in Failover
IP Address:192.168.0.220
Now, in Failover services
function (on primary node),
uncheck the box with iSCSI,
then check box witch NFS, and
click the apply button
NOTE:
Selecting NFS in Failover service will reduce the
access to shares on volumes used in Failover
Tasks to NFS access only. Activating Failover
Service will automatically deactivate all other
services for those shares.
www.open-e.com 39
40. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 7. Start Failover Service
IP Address:192.168.0.220
Next, in the Failover Tasks
function, move the Failover
Tasks to be used for the failover
service to the Failover Tasks
area clicking button and
click apply
www.open-e.com 40
41. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 7. Start Failover Service
IP Address:192.168.0.220
At this point both nodes are
ready to start the Failover
service
www.open-e.com 41
42. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 7. Start Failover Service
IP Address:192.168.0.220
After clicking the start button
configuration of both nodes will
be complete
NOTE:
You can now mount the NFS client computers.
www.open-e.com 42
43. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 7. Start Failover Service
IP Address:192.168.0.220
After start Failover, check the
status in Failover status
function. All must read OK
NAS Failover/Volume Replication
www.open-e.com 43
44. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 7. Start Failover Service
IP Address:192.168.0.220
In the Task status, (after
clickling button) the
destination volumes must be
consistent.
NAS Failover/Volume Replication
www.open-e.com 44
45. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 8. Test Failover Function
IP Address:192.168.0.220
In order to test Failover in
Manual Failover, function,
click on the Manual failover
button.
www.open-e.com 45
46. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 8. Test Failover Function
IP Address:192.168.0.220
After clicking on the Manual
failover button, primary node
enters suspend mode
www.open-e.com 46
47. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 8. Test Failover Function
IP Address:192.168.0.220
The Failover status function
shows the Global status of the
primary node. Status service is
in suspend mode and the node
is inactive.
www.open-e.com 47
48. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 8. Test Failover Function
IP Address:192.168.0.221
In Failover status function
Global status shows the status
of the secondary node. The
service status is degraded and
Node status is active.
www.open-e.com 48
49. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 9. Run Failback Function
IP Address:192.168.0.221
In order to run Failback in
Failover manager function click
on the Sync volumes button
first.
www.open-e.com 49
50. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 9. Run Failback Function
IP Address:192.168.0.221
After synchronization the task
status of the destination volume
must be Consistent
www.open-e.com 50
51. NAS (NFS) Failover over a LAN
Data Server (DSS2)
Secondary node 9. Run Failback Function
IP Address:192.168.0.221
In order to return the active
server state to the Primary
server click on the Failback
button
www.open-e.com 51
52. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 9. Run Failback Function
IP Address:192.168.0.220
After clicking on Failback
button (in Failover manager
function on Secondary node)
Primary node is now active.
www.open-e.com 52
53. NAS (NFS) Failover over a LAN
Data Server (DSS1)
Primary node 9. Run Failback Function
IP Address:192.168.0.220
Primary node is active again
and ready for Failover.
Failover/Volume Replication
The configuration and testing of
NAS Failover/Failback is now
complete.
www.open-e.com 53