Open-E DSS V7 Synchronous Volume Replication over a LANopen-e
The document provides step-by-step instructions for setting up synchronous volume replication between two Open-E DSS servers over a local area network. It involves configuring hardware, networking, creating logical volumes on the source and destination nodes, setting up replication between the volumes, and creating a replication task to synchronize data from the source to destination volume. The status of replication can be monitored by checking the replication tasks in the DSS management interface.
This document provides a step-by-step guide for setting up active-passive iSCSI failover between two Open-E DSS V7 nodes (node-a and node-b). The steps include: 1) configuring the hardware and network settings for each node; 2) creating volume groups and iSCSI volumes for data replication on each node; 3) configuring volume replication between the nodes; 4) creating iSCSI targets on each node; 5) configuring failover settings; and 6) testing the failover functionality. Key aspects involve replicating iSCSI volumes from the active node-a to the passive node-b, and configuring virtual IP addresses and targets on each node for seamless failover
The document provides step-by-step instructions for setting up an active-active load balanced iSCSI high availability cluster without bonding between two Open-E DSS V7 nodes (node-a and node-b). The key steps include:
1. Configuring the hardware for each node including network interfaces and IP addresses.
2. Configuring volumes, volume replication between each node's volumes to enable data synchronization, and starting the replication tasks.
3. Creating iSCSI targets on each node to expose the replicated volumes and enable failover.
Open-E DSS V7 Synchronous Volume Replication over a LANopen-e
The document provides step-by-step instructions for setting up synchronous volume replication between two Open-E DSS servers over a local area network. It involves configuring hardware, networking, creating logical volumes on the source and destination nodes, setting up replication between the volumes, and creating a replication task to synchronize data from the source to destination volume. The status of replication can be monitored by checking the replication tasks in the DSS management interface.
This document provides a step-by-step guide for setting up active-passive iSCSI failover between two Open-E DSS V7 nodes (node-a and node-b). The steps include: 1) configuring the hardware and network settings for each node; 2) creating volume groups and iSCSI volumes for data replication on each node; 3) configuring volume replication between the nodes; 4) creating iSCSI targets on each node; 5) configuring failover settings; and 6) testing the failover functionality. Key aspects involve replicating iSCSI volumes from the active node-a to the passive node-b, and configuring virtual IP addresses and targets on each node for seamless failover
The document provides step-by-step instructions for setting up an active-active load balanced iSCSI high availability cluster without bonding between two Open-E DSS V7 nodes (node-a and node-b). The key steps include:
1. Configuring the hardware for each node including network interfaces and IP addresses.
2. Configuring volumes, volume replication between each node's volumes to enable data synchronization, and starting the replication tasks.
3. Creating iSCSI targets on each node to expose the replicated volumes and enable failover.
This document provides instructions for installing Oracle Database 11g Release 2 on Linux. It begins with hardware and software requirements, then describes configuring the Linux kernel by setting parameters for shared memory, semaphores, file handles, and IP ports. It also covers creating UNIX groups and the Oracle software owner user. The instructions are presented in steps that minimize complexity to accomplish the installation.
This document provides requirements and kernel parameter settings for installing Oracle9i Release 1 (9.0.1) on HP-UX 11.0 (64-bit). It outlines the minimum memory, disk space, operating system patches, and other software needed. The kernel parameter settings specified are the minimum required to run Oracle9i with a single database instance. The document also provides links to Oracle documentation and contains sections on documentation, installation issues, product issues, and post-installation issues related to Oracle9i.
This document provides instructions for installing an Oracle 11gR2 RAC database using raw devices on an AIX system. It discusses hardware and network requirements including configuring shared storage using HACMP. It provides details on installing Oracle Clusterware and database software, and creating the database. Key steps include preparing the system, installing Grid Infrastructure, installing the database software, and using DBCA or manual methods to create the database.
GoldenGate is a replication utility that provides flexible data propagation between databases. It consists of extract, replicat, and data pump processes that access trail files containing change data. An extract process mines source database redo logs and writes changes to trail files. A replicat process reads from trail files and applies changes to target database tables. The demo will show two scenarios for replicating data from a Windows source database to a Linux target database using different GoldenGate configuration methods.
Schema replication using oracle golden gate 12cuzzal basak
This document provides instructions for configuring asynchronous schema replication between an Oracle source database and target database using Oracle GoldenGate 12c. It outlines the necessary steps which include:
1. Enabling supplemental logging and archivelog mode on both databases.
2. Installing the GoldenGate software and starting the Manager processes on both systems.
3. Configuring the Extract, Data Pump, and Replicate processes to replicate the BASAK schema and tables from the source PDBORCL to the target PRIPDB database.
4. Starting the Extract, Data Pump, and Replicate jobs to begin the replication process and ensure the BASAK schema and tables are synchronized between the source and target databases.
The document describes migrating database files from the "+DATA01" disk group to the new "+DATA02" disk group. It involves creating the new disk group, identifying database file locations, copying files to the new disk group using RMAN backups, and switching the database to use the new disk group.
Oracle goldengate 11g schema replication from standby databaseuzzal basak
GoldenGate can replicate database schemas between an Oracle source and target database. It was configured to replicate the SCOTT schema from a source Oracle 11gR2 database in standby mode to a target Oracle 11gR2 database. The key steps included enabling supplemental logging on the source, setting up the GoldenGate user and processes on both databases, and defining the extract, pump and replicate processes to copy data and DDL changes from the source to the target schema.
The document summarizes new features in Oracle Database 12c Recovery Manager (RMAN). Key points include: RMAN now supports pluggable databases and allows point-in-time recovery of individual pluggable databases. It also enables running SQL statements and recovering individual tables from backups. Active duplicate operations in RMAN utilize backup sets for more efficient cross-platform restores of databases.
The document discusses setting up a Hadoop cluster with CentOS 6.5 installed on multiple physical servers. It describes the process of installing CentOS via USB, configuring basic OS settings like hostname, users, SSH, firewall. It also covers configuring network settings, Java installation and enabling passwordless SSH login. The document concludes with taking server snapshots for backup/recovery and installing Hadoop services like HDFS, Hive etc using Cloudera Express on the cluster.
This document discusses using sampling to diagnose buffer busy wait issues in an Oracle database. It provides an example of using the v$session_wait view to identify the specific buffer busy wait type, file, and block number involved. This allows finding the impacted object and SQL statement. The example identifies an insert statement on a table with a single freelist as the cause. It recommends adding more freelists to improve concurrency for inserts on that table.
This document describes how to install Oracle 10g RAC on Linux using NFS for shared storage. Key steps include:
1. Installing Oracle Enterprise Linux on two nodes and configuring networking and prerequisites.
2. Setting up NFS shares on one node for shared file systems and disks.
3. Installing the Oracle Clusterware software and configuring the two-node cluster.
The document provides instructions for setting up a backup from a DSS V6 data server to an attached tape drive. The key steps include: 1) Configuring hardware and volume groups, 2) Creating NAS volumes and snapshots, 3) Configuring the backup to use the tape drive by defining pools, tasks, and schedules, and 4) Performing backups that store data from network shares on labeled tapes according to the defined configuration.
This document provides information on using Perl to interact with and manipulate databases. It discusses:
- Using the DBI module to connect to databases in a vendor-independent way
- Installing Perl modules like DBI and DBD drivers to connect to specific databases like Postgres
- Preparing the Postgres database environment, including initializing and starting the database
- Using the DBI handler and statements to connect to and execute queries on the database
- Retrieving and manipulating database records through functions like SELECT, adding new records, etc.
The document provides code examples for connecting to Postgres with Perl, executing queries to retrieve data, and manipulating the database through operations like inserting new records. It focuses on
The document describes setting up a clustered ONTAP environment. It includes creating a cluster called "netappu" with nodes at locations "NetAppU" and adding various licenses. It also outlines configuring cluster network and management interfaces, setting up a Vserver for administration, enabling storage failover, and completing cluster node setup.
The document provides instructions for installing Zenworks on a Linux server. It describes downloading and installing required software like SUSE Linux, Java, eDirectory, ConsoleOne, and Zenworks. It then provides step-by-step instructions for configuring eDirectory by creating a new tree, server, and administrator. Finally, it notes that Zenworks Server 7.2 can be installed by mounting the ISO, navigating to the folder, and running the installer.
This document provides release notes for Oracle9i Release 1 (9.0.1) for Linux Intel from June 2001. It outlines system requirements, kernel parameters, installation issues, and other product-related issues. Key topics covered include requirements for memory, swap space, disk space, processors, and software. It also provides minimum recommended kernel parameter settings for shared memory and semaphores.
The document provides step-by-step instructions to install Oracle Database 12c. It details downloading the software, checking system requirements, installing prerequisite packages and configuring OS parameters like memory, ports and users. The instructions then cover running the installer, configuring the listener using NetCA and creating a database instance using DBCA.
This document discusses creating agile Unix command line tools using Python. It recommends using the optparse and subprocess modules for option handling and system calls. It provides examples of a multi-threaded ping sweep tool, integrating configuration files, and distributing tools as Python eggs with an entry point. References for further information on SNMP, Scapy, and Storm are also included.
Red Hat Storage Day Seattle: Why Software-Defined Storage MattersRed_Hat_Storage
The document discusses the benefits of software-defined storage over traditional storage approaches. It argues that software-defined storage uses standard hardware and open source software, providing flexibility, scalability, and lower costs compared to proprietary appliances or public cloud storage. It also describes Red Hat's portfolio of software-defined storage solutions, including Ceph and Gluster, which leverage open source technologies to power a variety of enterprise workloads.
This document provides instructions for installing Oracle Database 11g Release 2 on Linux. It begins with hardware and software requirements, then describes configuring the Linux kernel by setting parameters for shared memory, semaphores, file handles, and IP ports. It also covers creating UNIX groups and the Oracle software owner user. The instructions are presented in steps that minimize complexity to accomplish the installation.
This document provides requirements and kernel parameter settings for installing Oracle9i Release 1 (9.0.1) on HP-UX 11.0 (64-bit). It outlines the minimum memory, disk space, operating system patches, and other software needed. The kernel parameter settings specified are the minimum required to run Oracle9i with a single database instance. The document also provides links to Oracle documentation and contains sections on documentation, installation issues, product issues, and post-installation issues related to Oracle9i.
This document provides instructions for installing an Oracle 11gR2 RAC database using raw devices on an AIX system. It discusses hardware and network requirements including configuring shared storage using HACMP. It provides details on installing Oracle Clusterware and database software, and creating the database. Key steps include preparing the system, installing Grid Infrastructure, installing the database software, and using DBCA or manual methods to create the database.
GoldenGate is a replication utility that provides flexible data propagation between databases. It consists of extract, replicat, and data pump processes that access trail files containing change data. An extract process mines source database redo logs and writes changes to trail files. A replicat process reads from trail files and applies changes to target database tables. The demo will show two scenarios for replicating data from a Windows source database to a Linux target database using different GoldenGate configuration methods.
Schema replication using oracle golden gate 12cuzzal basak
This document provides instructions for configuring asynchronous schema replication between an Oracle source database and target database using Oracle GoldenGate 12c. It outlines the necessary steps which include:
1. Enabling supplemental logging and archivelog mode on both databases.
2. Installing the GoldenGate software and starting the Manager processes on both systems.
3. Configuring the Extract, Data Pump, and Replicate processes to replicate the BASAK schema and tables from the source PDBORCL to the target PRIPDB database.
4. Starting the Extract, Data Pump, and Replicate jobs to begin the replication process and ensure the BASAK schema and tables are synchronized between the source and target databases.
The document describes migrating database files from the "+DATA01" disk group to the new "+DATA02" disk group. It involves creating the new disk group, identifying database file locations, copying files to the new disk group using RMAN backups, and switching the database to use the new disk group.
Oracle goldengate 11g schema replication from standby databaseuzzal basak
GoldenGate can replicate database schemas between an Oracle source and target database. It was configured to replicate the SCOTT schema from a source Oracle 11gR2 database in standby mode to a target Oracle 11gR2 database. The key steps included enabling supplemental logging on the source, setting up the GoldenGate user and processes on both databases, and defining the extract, pump and replicate processes to copy data and DDL changes from the source to the target schema.
The document summarizes new features in Oracle Database 12c Recovery Manager (RMAN). Key points include: RMAN now supports pluggable databases and allows point-in-time recovery of individual pluggable databases. It also enables running SQL statements and recovering individual tables from backups. Active duplicate operations in RMAN utilize backup sets for more efficient cross-platform restores of databases.
The document discusses setting up a Hadoop cluster with CentOS 6.5 installed on multiple physical servers. It describes the process of installing CentOS via USB, configuring basic OS settings like hostname, users, SSH, firewall. It also covers configuring network settings, Java installation and enabling passwordless SSH login. The document concludes with taking server snapshots for backup/recovery and installing Hadoop services like HDFS, Hive etc using Cloudera Express on the cluster.
This document discusses using sampling to diagnose buffer busy wait issues in an Oracle database. It provides an example of using the v$session_wait view to identify the specific buffer busy wait type, file, and block number involved. This allows finding the impacted object and SQL statement. The example identifies an insert statement on a table with a single freelist as the cause. It recommends adding more freelists to improve concurrency for inserts on that table.
This document describes how to install Oracle 10g RAC on Linux using NFS for shared storage. Key steps include:
1. Installing Oracle Enterprise Linux on two nodes and configuring networking and prerequisites.
2. Setting up NFS shares on one node for shared file systems and disks.
3. Installing the Oracle Clusterware software and configuring the two-node cluster.
The document provides instructions for setting up a backup from a DSS V6 data server to an attached tape drive. The key steps include: 1) Configuring hardware and volume groups, 2) Creating NAS volumes and snapshots, 3) Configuring the backup to use the tape drive by defining pools, tasks, and schedules, and 4) Performing backups that store data from network shares on labeled tapes according to the defined configuration.
This document provides information on using Perl to interact with and manipulate databases. It discusses:
- Using the DBI module to connect to databases in a vendor-independent way
- Installing Perl modules like DBI and DBD drivers to connect to specific databases like Postgres
- Preparing the Postgres database environment, including initializing and starting the database
- Using the DBI handler and statements to connect to and execute queries on the database
- Retrieving and manipulating database records through functions like SELECT, adding new records, etc.
The document provides code examples for connecting to Postgres with Perl, executing queries to retrieve data, and manipulating the database through operations like inserting new records. It focuses on
The document describes setting up a clustered ONTAP environment. It includes creating a cluster called "netappu" with nodes at locations "NetAppU" and adding various licenses. It also outlines configuring cluster network and management interfaces, setting up a Vserver for administration, enabling storage failover, and completing cluster node setup.
The document provides instructions for installing Zenworks on a Linux server. It describes downloading and installing required software like SUSE Linux, Java, eDirectory, ConsoleOne, and Zenworks. It then provides step-by-step instructions for configuring eDirectory by creating a new tree, server, and administrator. Finally, it notes that Zenworks Server 7.2 can be installed by mounting the ISO, navigating to the folder, and running the installer.
This document provides release notes for Oracle9i Release 1 (9.0.1) for Linux Intel from June 2001. It outlines system requirements, kernel parameters, installation issues, and other product-related issues. Key topics covered include requirements for memory, swap space, disk space, processors, and software. It also provides minimum recommended kernel parameter settings for shared memory and semaphores.
The document provides step-by-step instructions to install Oracle Database 12c. It details downloading the software, checking system requirements, installing prerequisite packages and configuring OS parameters like memory, ports and users. The instructions then cover running the installer, configuring the listener using NetCA and creating a database instance using DBCA.
This document discusses creating agile Unix command line tools using Python. It recommends using the optparse and subprocess modules for option handling and system calls. It provides examples of a multi-threaded ping sweep tool, integrating configuration files, and distributing tools as Python eggs with an entry point. References for further information on SNMP, Scapy, and Storm are also included.
Red Hat Storage Day Seattle: Why Software-Defined Storage MattersRed_Hat_Storage
The document discusses the benefits of software-defined storage over traditional storage approaches. It argues that software-defined storage uses standard hardware and open source software, providing flexibility, scalability, and lower costs compared to proprietary appliances or public cloud storage. It also describes Red Hat's portfolio of software-defined storage solutions, including Ceph and Gluster, which leverage open source technologies to power a variety of enterprise workloads.
Swift Architecture and Practice, by Alex YangHui Cheng
The document discusses the principles, architecture, and practice of Swift object storage at SinaAppEngine. It describes how Swift provides high reliability through consistent hashing, replication across multiple zones, and an eventual consistency model. It outlines SinaAppEngine's implementation of Swift for storage, including authentication, quotas, and domain remapping. Problems addressed include improving replication efficiency and SQLite performance as well as controlling rsync bandwidth. The document provides an overview of how Swift storage works at scale.
Fundamentals of building a Restful API with Django and django-rest-framework. Intended for new developers interested in developing a REST API for their applications. Basic knowledge of Python is nice to have, but the concepts are transferable.
Presented at Vancouver Python Day 2013.
Project Presentation. Gives a good overview of the various software defined technologies and quality attributes. I am looking for sales jobs at high tech companies. My profile is on LinkedIn if you need to contact me. I appreciate feedback and comments on this presentation.
Microservices with Swagger, Flask and DockerDhilipsiva DS
The document discusses Microservices with Swagger, Flask and Docker. It provides an overview of the OpenAPI Specification (formerly known as the Swagger Specification), which is a specification for machine-readable interface files for describing, producing, consuming, and visualizing RESTful web services. It then discusses using Swagger for API-first development and documentation and demonstrates building a sample API using Connexion with Swagger, Flask and Docker.
Software Defined anything (SDx) is a movement toward promoting a greater role for software systems in controlling different kinds of hardware - more specifically, making software more "in command" of multi-piece hardware systems and allowing for software control of a greater range of devices.
Software Defined Everything (SDx) includes
Software Defined Networks (SDN)
Software Defined Computing (SDC)
Software Defined Storage (SDS)
Software Defined Data Centers (SDDC)
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011Stephen Foskett
The notion that Fibre Channel is for data centers and iSCSI is for SMB’s and workgroups is outdated. Increases in LAN speeds and the coming of lossless Ethernet position iSCSI as a good fit for the data center. Whether your organization adopts FC or iSCSI depends on many factors like current product set, future application demands, organizational skill-set and budget. In this session we will discuss the different conditions where FC or IsCSI are the right fit, why you should use one and when to kick either to the curb.
Agenda:
------------------------------------------------------------------
OpenStack 101: a Quick introduction to OpenStack & how it operates
Paul Roberts, Principal Solutions Architect at Mirantis
Abstract:
Are you new to OpenStack? Are you looking to get a quick introduction to OpenStack and how it operates - then our session is a do not miss event! Mirantis will do a walk thru of OpenStack for those with little to no experience with OpenStack. Join us if you want to understand the purpose of OpenStack and its ecosystem, as well as if you want to learn more about the OpenStack architecture.
Bio:
Paul Roberts, lead speaker, has spent the last decade engineering and implementing large scale infrastructure and security architectures for organizations of all sizes - ranging from startup to Fortune 500. In the past, he was instrumental in architecting Carpathia Hosting's federal and commercial cloud offerings, while also playing a key role in the on–boarding of customer's applications. Today, Paul is a Principal Solutions Architect at Mirantis helping customers navigate through the cloud ecosystem by designing and architecting various OpenStack powered initiatives.
REST Coder: Auto Generating Client Stubs and Documentation for REST APIsHiranya Jayathilaka
An introduction to REST Coder. REST Coder is a collection of tools for auto generating client stubs and API docs for RESTful Web services. Currently REST Coder supports auto generating client stubs in Python and JS, and auto generating API docs in HTML and Sphinx.
The document discusses building REST APIs in Flask. It introduces REST concepts and how Flask supports REST. Validation of resources can be done with Trafaret. The document demonstrates creating API resources with Flask extensions that support validation, authentication decorators, and modeling SQL Alchemy classes. Future work includes adding filtering, caching, throttling and customizing fields for modeled resources.
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...Innovecs
On Saturday, 12 of April, regular quarterly meeting of Tech Hangout Community took place in Creative Space 12, the cultural and educational center based in Kiev! The event was held under the motto «One day of inspiring talks on Web Back-End». This time Python, Ruby and PHP developers gathered to make peace and learn the Force.
*TECH HANGOUT COMMUNITY was found in 2012 by the developers for the developers for knowledge and experience sharing. Such meetings are the part of Innovecs Educational Project that actively develops sphere of internal trainings and knowledge exchange program among professionals. This Initiative was born within the walls of Innovecs and has proved to be extremely popular and high-demand. In a short period of time it gained its own Facebook group with more than 90 members, blog with more than 40 posts and constant quarterly external meeting of Tech hangout community with more than 80 participants. The concept of the event proposes a 30-minute report on the topic previously defined, and the discussion in a roundtable session format.
Join to discuss - https://www.facebook.com/groups/techhangout/
The document discusses the need for abstractions in networking to simplify network control and management. It argues that networking currently lacks fundamental abstractions, unlike other fields like programming. Three key abstractions are needed: 1) a flexible forwarding model, 2) a state distribution abstraction through a global network view, and 3) separating detailed configuration. These abstractions form the basis of Software-Defined Networking (SDN) and help address its scalability and evolvability. A Network Operating System (NOS) is also proposed to manage the distributed state and communicate with forwarding elements.
Slides of my talk I gave @ PyRE.it in ReggioEmilia about developing a Rest Api in Python using a little bit of Flask and SqlAlchemy.
www.pyre.it
www.alessandrocucci.it/pyre/restapi
The document discusses the evolution of a server from Apache to Lighttpd to Nginx. Nginx provided significant performance improvements, reducing server load from over 26 to 0.3 while supporting over 4 million views per day. Nginx has a learning curve but simpler configurations that are easier to read and more flexible than previous solutions. It also works well with PHP-FPM for fast PHP processing and allows easy deployment and configuration of new CakePHP and PHP sites.
Open stack architecture overview-meetup-6-6_2013Mirantis
This document provides an overview of OpenStack architecture and components. It discusses the goals of OpenStack, including understanding its purpose, ecosystem, definition, history, and projects. It describes the logical architecture and components of OpenStack like Nova, Glance, Swift, Cinder, Quantum, Keystone, and Horizon. It explains how a virtual machine provisioning request flows through different OpenStack components.
Keystone is the OpenStack identity service that provides user, project and service catalog management. It implements the OpenStack Identity API. Keystone has four internal services - Identity, Token, Catalog and Policy. It uses a pluggable backend architecture that allows different storage backends. Keystone provides authentication for users and services in OpenStack and maps users to their authorized projects and roles.
This document provides an overview of software-defined storage (SDS) concepts and discusses several SDS solutions from major vendors. It defines SDS and explains how adding a control layer allows for visibility, communication, and allocation of storage resources. Benefits highlighted include efficiency, automation, flexibility, scalability, reliability and cost savings. Specific SDS products are then profiled from vendors such as EMC, HP, IBM, NetApp, VMware, Coraid, DataCore, Dell, Hitachi, Pivot3, and RedHat.
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...LF Events
Fujitsu applies OpenStack for providing hybrid cloud service.
In this presentation, Miyashita will introduce learning from real practice of providing highly
available hybrid cloud service with OpenStack Neutron.
He will talk issues and solutions which Fujitsu faced through providing
hybrid(public/private) cloud service.
- How to build multiple OpenStack-based datacenters for public cloud with high availability
- How to build hybrid cloud environment(Connecting public cloud and on-premise datacenters)
- High available functionality spanning multiple datacenters(ex.loadbalancing service, security group)
This presentation was delivered at LinuxCon Japan 2016 by Kazuhiro Miyashita
Anatomy of neutron from the eagle eyes of troubelshoortersSadique Puthen
This document summarizes the anatomy of OpenStack Neutron through examples of real-life troubleshooting scenarios. It explores four examples: security group rules not being effective, instances not getting IP addresses from DHCP, floating IP connections randomly failing, and slow provider network communications. For each example, it explains the root cause found by understanding Neutron's architecture and packet flows, and describes the troubleshooting steps taken such as examining logs, monitoring processes, and using tools like tcpdump. The goal is to demonstrate Neutron anatomy and troubleshooting methods rather than just state the problems and solutions.
This document provides steps to configure multipath I/O (MPIO) on an Open-E DSS V6 system with VMware ESXi 4.x and a Windows 2008 virtual machine. It requires two network cards in both systems connected to a switch. The steps include configuring the DSS V6 as an iSCSI target with two IP addresses, creating two vmkernel ports on the ESXi host connected to different network cards, adding the DSS as two iSCSI targets, enabling round robin path selection, and installing the Windows VM to test I/O performance using Iometer.
Cisco Configuration Professional allows for the configuration of site-to-site IPsec VPN tunnels between two Cisco IOS routers. The document provides an example configuration using static routes that establishes an IPsec tunnel between Router A and Router B. The configuration is performed using Cisco Configuration Professional on each router and specifies the IKE and IPsec proposals, transform sets, and traffic to be protected between the 10.10.10.0 and 10.20.10.0 networks. Show commands are included to verify the tunnel is successfully established and traffic is being encrypted and decrypted.
This document summarizes a workshop on network automation tools including Chef and Zero Touch Provisioning.
The agenda includes demonstrating ZTP to boot three bare metal switches, using Chef to orchestrate the baseline configuration of two switches and enforce configuration statements, creating a VXLAN tunnel between two leaf switches using Cisco's CVX, and starting an Opendaylight controller to configure Openflow on switches.
The workshop will require some Virtualbox experience and a notebook with at least 4GB RAM and 10GB storage. Software needed includes Virtualbox, Hypervisor, and virtualization solutions. Attendees should be DevOps engineers interested in the network side of DevOps.
The workshop will prepare VMs, demonstrate
The document describes how to configure a Linux machine as a router to connect two subnets. It provides instructions to enable IP forwarding and configure the network interfaces using temporary and permanent methods.
The summary is:
- Enable IP forwarding and configure the network interfaces of two Ethernet cards using ifconfig to set up routing temporarily
- Use netconf to configure the interfaces and routing permanently by editing settings, accepting changes, and rebooting to confirm the configuration persists
- Install traffic generator programs on end stations to test routing of UDP and TCP packets between subnets going through the router
NETMAX TECHNOLOGIES provides network training, software training, and embedded systems support and consultancy. Courses include CCNA, CCNP, Red Hat Linux, Windows, C, C++, Java, .NET, and microcontroller training. It uses NAT to allow private networks to connect to the internet using a limited number of public IP addresses. Static NAT maps a private IP to a public IP in a 1:1 ratio. Dynamic NAT maps private IPs to public IPs from a pool. Overloading NAT maps multiple private IPs to one public IP using port addressing.
Network topology is the topological structure of a system and might be portrayed physically or sensibly. It is an utilization of chart hypothesis wherein conveying gadgets are demonstrated as hubs and the associations between the gadgets are displayed as connections or lines between the hubs.
Openstack 3 node setup using RDO on top of RHEL 7.
Complete steps which will give you more convenience to work on top of Openstack without any installation issues.
Implementation of cisco wireless lan controller (multiple wla ns)IT Tech
This document provides guidance on implementing a Cisco Wireless LAN Controller to support multiple wireless LANs for a customer requiring guest and employee networks. It describes the necessary configurations including:
1. Creating VLANs and interfaces on the controller and core switches for management, AP management, guest, and employee networks.
2. Configuring wireless LANs, SSIDs, security, and assigning them to the proper interfaces.
3. Configuring RADIUS authentication and accounting servers.
The document aims to complement Cisco's documentation and provide lessons learned from a practical implementation.
The document discusses the benefits of using Istio service mesh to connect microservices. Istio provides a standard sidecar proxy that handles tasks like load balancing, failure recovery, metrics collection, and traffic management for microservices. It also provides interfaces to configure and manage policies separately from application code. This allows clear separation between application development and operations tasks like routing, monitoring, and access control configuration.
The document discusses the benefits of using Istio service mesh to connect microservices. Istio provides a standard sidecar proxy that handles tasks like load balancing, failure recovery, metrics collection, and traffic management for microservices. It also provides interfaces to configure and manage policies separately from application code. This allows clear separation between application development and operations tasks like routing, monitoring, and access control configuration.
Mikro tik site to site eoip tunnel with i psecUttam Ds
This document provides instructions for configuring a site-to-site EoIP VPN tunnel with IPsec between two MikroTik routers to connect two private networks. It involves:
1) Configuring basic settings like IP addresses, DNS, and NAT on each router
2) Creating an EoIP tunnel interface on each router with matching IDs and IPsec secrets
3) Assigning IP addresses to the tunnel interfaces
4) Adding static routes on each router to allow communication between the LANs over the tunnel
This document outlines the planning and implementation of a VOIP system using Asterisk on Linux. It includes network diagrams, server and client specifications, and steps for installing Asterisk on CentOS and configuring extensions, trunks, and outbound routes in the Asterisk web interface. Tests of internal and external calls between softphones on Linux and Windows clients are also described. The goal is to provide a free solution for making calls over an internal network and to external networks to reduce calling costs.
This document provides instructions for configuring Ubiquiti Rocket M2 access points as main and sub nodes in a wireless network. It describes connecting the devices, setting their IP addresses and wireless settings through a web interface, updating firmware, and testing the connection. Troubleshooting tips are also included such as rebooting devices, backing up and restoring configurations, and resetting to factory defaults.
OAM 3G Network Ericsson discusses operation and maintenance of Ericsson's 3G radio access network. Session 1 covers the OSS, EMAS and other tools used for network operation. Session 2 discusses commissioning radio base stations, replacing modules, backing up network nodes, and upgrading base station capacity. Key tools include OSS, EMAS, element manager and scripts for configuration tasks. Proper planning, tools and procedures are needed for tasks like commissioning, module replacement, backups and hardware upgrades.
CCNA: Connecting Networks SA Exam
Lab 13 CCNA: Connecting Networks
CSIS 430 – Weeks 1 - 4
Hands-On Skills Assessment
Topology
Complete the assessment in Packet Tracer and document and fill in the blanks. Submit this file and the pka file in Week 8 Lab 13, Points will not be given for incomplete Steps.
Assessment Objectives
Part 1: Initialize Devices (2 points, 5 minutes)
Part 2: Configure Device Basic Settings (8 points, 20 minutes)
Part 3: Configure PPP Connections (7 points, 20 minutes)
Part 4: Configure NAT (4 points, 15 minutes)
Part 5: Monitor the Network (6 points, 15 minutes)
Part 6: Configure Frame Relay (7 points, 20 minutes)
Part 7: Configure a GRE VPN Tunnel (6 points, 20 minutes)
Scenario
In this Skills Assessment (SA) you will create a small network. You must connect the network devices and configure those devices to support various WAN protocols. This will require that you reload the routers before starting your configuration of the next WAN protocol. The assessment has you save your basic device configurations to flash prior to implementing a WAN protocol to allow you to restore these basic configurations after each reload.
The first WAN protocol you will configure is Point-to-Point Protocol (PPP) with CHAP authentication. You will also configure Network Address Translation (NAT), and network monitoring protocols during this phase of the assessment. After your instructor has signed off on this phase, you will reload the routers and configure Frame Relay. After the Frame Relay part is complete, and has been signed off by your instructor, you will reload the routers and configure a GRE VPN tunnel. Network configurations and connectivity will be verified throughout the assessment by using common CLI commands.
Required Resources
3 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
3 PCs (Windows 7, Vista, or XP with terminal emulation program, such as Tera Term.
Console cable to configure the Cisco IOS devices via the console ports
Ethernet and Serial cables as shown in the topology
Initialize Devices
Total points: 2
Time: 5 minutes
Initialize and reload routers.
Erase the startup configurations and reload the devices.
Task
IOS Command
Points
Erase the startup-config file on all routers.
erase startup-config
(1 point)
Reload all routers.
reload
(1 point)
Points: __________ of 2
Configure Device Basic Settings
Total points: 8
Time: 20 minutes
Configure PCs.
Assign static IPv4 address information (IP address, subnet mask, default gateway) to the three PCs in the topology. Refer to the Topology diagram to obtain the IP address information.
Configuration Item or Task
Specification
Points
Configure static IPv4 address information on PC-A.
IP Address: 192.168.11.3
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.11.1
1
Configure static IPv4 address information on PC-B.
IP Address: 192.168.22.3
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.22.1
Configure static IPv4 address information on PC ...
Similar to Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding) (20)
The document provides information on how snapshots work in Open-E software. Snapshots allow creating an exact copy of a logical volume at a point in time, while the original data continues to be available. The snapshot is implemented using copy-on-write, where changed blocks are copied to reserved space before being overwritten. This allows mounting snapshots read-only to access past versions of data. The document discusses snapshot configuration, advantages like non-disruptive backups, and disadvantages like decreased write speeds with many active snapshots.
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...open-e
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.
Open-E DSS V6 How to Setup iSCSI Failover with XenServeropen-e
The document provides instructions for setting up DSS V6 iSCSI failover with XenServer using multipath, which includes configuring hardware settings and IP addresses on both nodes, creating volumes and targets on the primary and secondary nodes, setting up volume replication between the nodes, and configuring multipath on the XenServer storage client. Key steps are configuring the secondary node as the replication destination, then the primary node as the replication source, and setting up iSCSI failover and a virtual IP for the replicated volume.
Open-E DSS Synchronous Volume Replication over a WANopen-e
This document provides a step-by-step guide to setting up synchronous volume replication over a WAN between two systems using Open-E DSS. It requires configuring hardware including two servers connected over a WAN. It then outlines 6 steps to set up the replication including 1) hardware configuration, 2) configuring DSS servers on the WAN, 3) configuring the destination node, 4) configuring the source node, 5) creating the replication task, and 6) checking replication status. Diagrams and explanations of each step in the configuration process are provided.
The document provides instructions for backing up data from a DSS V6 server to an attached tape library. The 4-step process includes: 1) configuring hardware and logical volumes, 2) creating NAS shares and snapshots, 3) configuring backup tasks and schedules to alternate between tape pools on odd and even weeks, and 4) setting up a restore task to recover data from backup tapes. When completed, the backup and restore processes are automated to run on a weekly schedule and maintain multiple versions of backed up data on tapes.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Things to Consider When Choosing a Website Developer for your Website | FODUUFODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
2. Open-E DSS V7 Active-Active iSCSI Failover
TO SET UP ACTIVE-ACTIVE ISCSI FAILOVER, PERFORM THE
FOLLOWING STEPS:
1.
Hardware configuration
2.
Network Configuration:
• Set server hostnames and Ethernet ports on both nodes (node-a, node-b)
3.
Configure the node-b:
• Create a Volume Group, iSCSI Volume
• Configure Volume Replication mode (destination and source mode) – define remote mode of binding, create Volume Replication
task and start the replication task
4.
Configure the node-a:
• Create a Volume Group, iSCSI Volume
• Configure Volume Replication mode (source and destination mode), create Volume Replication task and start the replication
task.
5.
Create targets (node-a and node-b)
6.
Configure Failover (node-a and node-b)
7.
Start Failover Service
8.
Test Failover Function
9.
Run Failback Function
www.open-e.com
2
3. Open-E DSS V7 Active-Active iSCSI Failover
Storage client 1
1. Hardware Configuration
Storage client 2
IP:192.168.0.101
eth0
IP:192.168.21.101 (MPIO 1)
IP:192.168.22.101 (MPIO 2)
IP:192.168.1.107 (Ping Node)
eth1
eth1
IP:192.168.31.101 (MPIO 1)
IP:192.168.32.101 (MPIO 2)
eth2
eth2
IP:192.168.0.102
eth0
Data Server (DSS1)
Switch 1
IP Address:192.168.0.220
RAID System 1
IP:192.168.0.220
Please use external tool to
monitor failures in connections
between switches.
eth0
Storage Client Access, Multipath
Auxiliary connection (Heartbeat)
(eth1, eth2)
Resources Pools and Virtual IP Addresses:
Node-a 192.168.21.100; iSCSI Target 0
Node-b 192.168.22.100; iSCSI Target 1
Storage Client Access, Multipath
Auxiliary connection (Heartbeat)
IP:192.168.2.220
(eth3, eth4)
Volume Replication,
Auxilliary connection (Heartbeat)
IP:192.168.5.220
Volume Groups (vg00)
iSCSI volumes (lv0000, lv0001)
iSCSI targets
node-b
Switch 2
IP Address:192.168.0.221
RAID System 2
Note:
Port used for WEB GUI management
bond1
(MPIO 1) IP:192.168.31.102
(MPIO 2) IP:192.168.32.102
(Ping Node) IP:192.168.2.107
RSTP/Port Trunk
IP:192.168.1.220
IP:192.168.21.102
IP:192.168.22.102
Data Server (DSS2)
node-a
bond0
(MPIO 1)
(MPIO 2)
eth5
Note:
Resources Pools and Virtual IP Addresses:
Node-a 192.168.31.100; iSCSI Target 0
Node-b 192.168.32.100; iSCSI Target 1
It is strongly recommended to use direct point-to-point and if possible 10GbE
connection for the volume replication. Optionally Round-Robin-Bonding with 1GbE
or 10GbE ports can be configured for the volume replication. The volume
replication connection can work over the switch, but the most reliable is a direct
connection.
iSCSI Failover/Volume Replication (eth5)
Port used for WEB GUI management
eth0
IP:192.168.0.221
Storage Client Access, Multipath
Auxiliary connection (Heartbeat)
(eth1, eth2)
IP:192.168.1.221
Storage Client Access, Multipath,
Auxiliary connection (Heartbeat)
(eth3, eth4)
IP:192.168.2.221
bond1
Volume Replication ,
Auxilliary connection (Heartbeat)
eth5
IP:192.168.5.221
Volume Groups (vg00)
iSCSI volumes (lv0000, lv0001)
iSCSI targets
NOTE:
To prevent switching loops, it's recommended to use RSTP (802.1w) or Port Trunking on network switches used to build A-A Failover network topology.
www.open-e.com
bond0
3
4. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
2. Network Configuration
IP Address:192.168.0.221
After logging on to the
Open-E DSS V7 (node-b), please
go to SETUP and choose the
"Network interfaces" option.
In the Hostname box, replace the
"dss" letters in front of the numbers
with "node-b" server, in this
example "node-b-59979144" and
click the apply button (this will
require a reboot).
www.open-e.com
4
5. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
2. Network Configuration
IP Address:192.168.0.221
Next, select eth0 interface and in
the IP address field, change the
IP address from 192.168.0.220 to
192.168.0.221
Then click apply (this will restart
network configuration).
www.open-e.com
5
6. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
2. Network Configuration
IP Address:192.168.0.221
Once again, select Interfaces and
in the "Create new bond
interface" function check two
boxes with eth1 and eth2. Next, in
the field Create select a bonding
mode. In this example select New
balance-alb.
Next, in the field Adress IP enter
192.168.1.221 and in the Netmask
field enter 255.255.255.0
Afterwards, click the create button
and confirm this action by clicking
the yes button.
www.open-e.com
6
7. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
2. Network Configuration
IP Address:192.168.0.221
Again, in the "Create new bond
interface" function check two
boxes with eth3 and eth4. Next, in
the field Create select a bonding
mode. In this example select New
balance-alb.
Next, in the Address IP field enter
192.168.2.221 and in the Netmask
field enter 255.255.255.0
Afterwards, click the create button
and confirm this action by clicking
the yes button.
www.open-e.com
7
8. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
2. Network Configuration
IP Address:192.168.0.221
Next, select eth5 interface and in
the IP address field, change the
IP address from 192.168.5.220 to
192.168.5.221 and click the apply
button.
www.open-e.com
8
9. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
2. Network Configuration
IP Address:192.168.0.220
After logging in to node-a, please
go to SETUP and choose the
"Network interfaces" option.
In the Hostname box, replace the
"dss" letters in front of the numbers
with "node-a" server, in this
example "node-a-39166501"and
click apply (this will require a
reboot).
www.open-e.com
9
10. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
2. Network Configuration
IP Address:192.168.0.220
Next, select Interfaces and in the
"Create new bond interface"
function check two boxes with eth1
and eth2. Next, in the field Create
select a bonding mode. In this
example select New balance-alb.
In the field Adress IP enter
192.168.1.220 and in the Netmask
field enter 255.255.255.0
Afterwards, click the create button
and confirm this action by clicking
the yes button.
www.open-e.com
10
11. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
2. Network Configuration
IP Address:192.168.0.220
Again in the "Create new bond
interface" function check two
boxes with eth3 and eth4. Next, in
the field Create select a bonding
mode. In this example select New
balance-alb.
Next, in the field Adress IP enter
192.168.2.220 and in the Netmask
field enter 255.255.255.0
Afterwards, click the create button
and confirm this action by clicking
the yes button.
www.open-e.com
11
12. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
Under CONFIGURATION, select
"Volume manager", then click on
"Volume groups".
In the Unit manager function
menu, add the selected physical
units (Unit MD0 or other) to create
a new volume group (in this case,
vg00) and click the apply button.
www.open-e.com
12
13. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
Select the appropriate volume
group (vg00) from the list on the
left and create a new iSCSI
volume of the required size.
Please set 2 logical volumes in the
Active-Active option.
The 1st logical volume (lv0000)
will be a destination of the
replication process on node-b.
Next, check the box Use volume
replication.
After assigning an appropriate
amount of space for the iSCSI
volume, click the apply button
www.open-e.com
13
14. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
Next, create the 2nd logical
volume on the node-b. Logical
volume (lv0001) will be the source
of the replication process on this
node.
Next, check the box Use volume
replication.
After assigning an appropriate
amount of space for the iSCSI
volume, click the apply button.
www.open-e.com
14
15. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
2 logical iSCSI Volume Block I/O
are now configured.
iSCSI volume (lv0000) is set to destination
iSCSI volume (lv0001) is set to source
www.open-e.com
15
16. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
Under CONFIGURATION, select
"Volume manager" and then click
on "Volume groups".
Add the selected physical units
(Unit S001 or other) to create a
new volume group (in this case,
vg00) and click apply button.
Volume Groups (vg00)
www.open-e.com
16
17. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
Select the appropriate volume
group (vg00) from the list on the
left and create a new iSCSI
volume of the required size.
Please set 2 logical volumes in the
Active-Active option.
The 1st logical volume (lv0000)
will be a source of the replication
process on the node-a.
Next, check the box for "Use
volume replication"
After assigning an appropriate
amount of space to the iSCSI
volume, click the apply button.
NOTE:
The source and destination volumes must be of
identical size.
www.open-e.com
17
18. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
Next, create the 2nd logical
volume on the node-a. Logical
volume (lv0001) will be a
destination of the replication
process on this node.
Next, check the box for "Use
volume replication".
After assigning an appropriate
amount of space to the iSCSI
volume, click the apply button.
NOTE:
The source and destination volumes must be of
identical size.
www.open-e.com
18
19. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
2 logical iSCSI Volume Block I/O
are now configured.
iSCSI volume (lv0000) is set to source
iSCSI volume (lv0001) is set to destination
www.open-e.com
19
20. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
Now, on the node-b, go to
"Volume replication".
Within Volume replication mode
function, check the Destination
box for lv0000 and check the
Source box for lv0001.
Then, click the apply button.
In the Hosts binding function,
enter the IP address of node-a (in
our example, this would be
192.168.5.220), enter node-a
administrator password and click
the apply button.
NOTE:
The remote node IP Address must be on the same
subnet in order for the replication to communicate.
VPN connections can work providing you are not
using a NAT. Please follow example:
• node-a:
192.168.5.220
• node-b:
192.168.5.221
www.open-e.com
20
21. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
Next, on the node-a, go to
"Volume replication".
Within Volume replication mode
function, check the Source box
for lv0000 and check the
Destination box for lv0001.
Next, click the apply button.
www.open-e.com
21
22. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
In the Create new volume
replication task, enter the task
name in the Task name field, then
click on the
button.
In the Destination volume field,
select the appropriate volume (in
this example, lv0000).
In the Bandwidth for SyncSource
(MB) field you must change the
value. In the example, 35MB is
used. Next, click the create button.
NOTE:
The "Bandwidth for SyncSource (MB)" need to be
calculated based on available Ethernet Network
throughput and number of replication tasks and the
limitation factor (about 0.7).
For example: 1 Gbit Ethernet and 2 replication tasks
(assuming 1 Gbit provides about 100 MB/sec sustained
network throughput)
• Bandwidth for SyncSource (MB): = 0.7 * 100/ 2 = 35
For example: 10 Gbit Ethernet and 10 replication tasks
(assuming 10 Gbit provides about 700 MB/sec sustained
network throughput)
• Bandwidth for SyncSource (MB): = 0.7 * 700/10 = 49
www.open-e.com
22
23. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
Now, in the Replication task
manager function, click the
corresponding "play" button to start
the Replication task on the node-a.
www.open-e.com
23
24. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
In the Replication tasks manager
window, you may view information
about currently running replication
tasks.
When a task is started, a date and
time will appear.
www.open-e.com
24
25. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
4. Configure the node-a
IP Address:192.168.0.220
You can check the status of
Volume Replication anytime in
STATUS → "Tasks" → "Volume
Replication" menu.
Click on the
button, located
next to a task name (in this case
Mirror_0000) 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 iSCSI Logical Volume.
www.open-e.com
25
26. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
Next, go to the node-b.
Within Create new volume
replication task, enter the task
name in the Task name field, then
click on the
button.
In the Destination volume field,
select the appropriate volume (in
this example, lv0001).
As in the node-a, in the Bandwidth
for SyncSource (MB) field you
must change the value. In our
example 35 MB is used. Next click
the create button.
www.open-e.com
26
27. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
3. Configure the node-b
IP Address:192.168.0.221
In the Replication tasks manager
function, click the corresponding
"play" button to start the
Replication task on the node-b:
Mirror_0001.
In this box you can find information
about currently running replication
tasks.
When a task is started a date and
time will appear.
www.open-e.com
27
28. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
5. Create new target on the node-b
IP Address:192.168.0.221
Choose CONFIGURATION, "iSCSI
target manager" and "Targets"
from the top menu.
In the Create new target function,
uncheck the box Target Default
Name.
In the Name field, enter a name for
the new target and click apply to
confirm.
iSCSI targets
NOTE:
Both systems must have the same Target name.
www.open-e.com
28
29. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
5. Create new target on the node-b
IP Address:192.168.0.221
Next, you must set the 2nd target.
Within the Create new target
function, uncheck the box Target
Default Name.
In the Name field, enter a name for
the 2nd new target and click apply
to confirm.
iSCSI targets
NOTE:
Both systems must have the same Target name.
www.open-e.com
29
30. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
5. Create new target on the node-b
IP Address:192.168.0.221
After that, select target0 within the
Targets field.
To assign appropriate volume to
the target (iqn.2013-06:mirror-0
→ lv0000) and click attach button
located under Action.
NOTE:
Volumes on both sides must have the same SCSI ID and
LUN# for example: lv0000 SCSI ID on node-a = lv0000
SCSI ID on node-b.
In this case before clickling the attach button please
copy the SCSI and LUN# from this node.
www.open-e.com
30
31. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS2)
node-b
5. Create new target on the node-b
IP Address:192.168.0.221
Next, select target1 within the
Targets field.
To assign appropriate volume to
the target (iqn.2013-06:mirror-1
→ lv0001) and click attach button
located under Action.
NOTE:
Both systems must have the same SCSI ID and LUN#
www.open-e.com
31
32. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
5. Create new target on the node-a
IP Address:192.168.0.220
On the node-a, choose
CONFIGURATION, "iSCSI target
manager" and "Targets" from the
top menu.
Within the Create new target
function, uncheck the box Target
Default Name.
In the Name field, enter a name for
the new target and click apply to
confirm.
iSCSI targets
NOTE:
Both systems must have the same Target name.
www.open-e.com
32
33. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
5. Create new target on the node-a
IP Address:192.168.0.220
Next, you must set the 2nd target.
In the Create new target function,
uncheck the box Target Default
Name.
In the Name field, enter a name for
the 2nd new target and click apply
to confirm.
iSCSI targets
NOTE:
Both systems must have the same Target name.
www.open-e.com
33
34. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
5. Create new target on the node-a
IP Address:192.168.0.220
Select the target0 within the
Targets field.
To assign appropriate volume to
the target (iqn.2013-06:mirror-0
→ lv0000) and click attach button
located under Action.
NOTE:
Before clicking the attach button again, please
paste the SCSI ID and LUN# (previously copied)
from the node-b.
www.open-e.com
34
35. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
5. Create new target on the node-a
IP Address:192.168.0.220
Select the target1 within the
Targets field.
To assign appropriate volume to
the target (iqn.2013-06:mirror-1
→ lv0001) and click attach button
located under Action.
NOTE:
Before clicking the attach button again, please
copy & paste the SCSI ID and LUN#
from the node-b.
www.open-e.com
35
36. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
On the node-a, go to SETUP and
select "Failover".
In the Auxiliary paths function,
select the 1st New auxiliary path
on the local and remote node and
click the add new auxiliary path
button.
www.open-e.com
36
37. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
In the Auxiliary paths function,
select the 2nd New auxiliary path
on the local and remote node and
click the add new auxiliary path
button.
www.open-e.com
37
38. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
In the Ping nodes function, enter
two ping nodes.
In the IP address field enter IP
address and click the add new
ping node button (according to the
configuration in the third slide).
In this example, IP address of the
first ping node is: 192.168.1.107
and the second ping node:
192.168.2.107
www.open-e.com
38
39. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
Next, go to the Resources Pool
Manager function (on node-a
resources) and click the add
virtual IP button. After that, enter
Virtual IP, (in this example
192.168.21.100 according to the
configuration in the third slide) and
select two appropriate interfaces
on local and remote nodes. Then,
click the add button.
www.open-e.com
39
40. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
Now, still on node-a resources
(local node) enter the next Virtual
IP address. Click add virtual IP
enter Virtual IP, (in this example
192.168.31.100), and select two
appropriate interfaces on the local
and remote nodes. Then, click the
add button.
www.open-e.com
40
41. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
Then, go to node-b resources and
click the add virtual IP button
again and enter the Virtual IP (In
this example 192.168.22.100
according to the configuration in
the third slide) and select two
appropriate interfaces on the local
and remote nodes. Then, click the
add button.
www.open-e.com
41
42. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
Now, still on node-b resources,
click the add virtual IP button and
enter the next Virtual IP, (in this
example 192.168.32.100,
according to the configuration in
the third slide) and select two
appropriate interfaces on the local
and remote nodes. Then, click the
add button.
www.open-e.com
42
43. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
Now you have 4 Virtual IP
addresses configured on two
interfaces.
www.open-e.com
43
44. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
When you are finished with setting
the virtual IP, go to the iSCSI
resources tab on the local node
resources and click the add or
remove targets button.
After moving the target mirror-0
from Available targets to Targets
already in cluster, click the apply
button.
www.open-e.com
44
45. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
Next, go to the iSCSI resources
tab on the remote node resources
and click the add or remove
targets button.
After moving the target mirror-1
from Available targets to Targets
already in cluster , click the apply
button.
www.open-e.com
45
46. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
6. Configure Failover
IP Address:192.168.0.220
After that, scroll to the top of the
Failover manager function.
At this point, both nodes are ready
to start the Failover.
In order to run the Failover service,
click the start button and confirm
this action by clicking the start
button again.
NOTE:
If the start button is grayed out, the setup has not been
completed.
www.open-e.com
46
47. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
7. Start Failover Service
IP Address:192.168.0.220
After clicking the start button,
configuration of both nodes is
complete.
NOTE:
You can now connect with iSCSI Initiators. The first
storage client, in order to connect to target0 please setup
multipath with following IP on the initiator side:
192.168.21.101 and 192.168.31.101. In order to connect
to target1 please setup multipath with following IP on the
initiator side: 192.168.22.101 and 192.168.32.101.
For the next storage client please setup multipath
accordingly: for access to target0: 192.168.21.102,
192.168.31.102 and for access to target1:
192.168.22.102, 192.168.32.102.
www.open-e.com
47
48. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
8. Test Failover Function
IP Address:192.168.0.220
In order to test Failover,
go to the Resources pool
manager function.
Then, in the local node resources,
click on the move to remote node
button and confirm this action by
clicking the move button.
www.open-e.com
48
49. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
8. Test Failover Function
IP Address:192.168.0.220
After performing this step, the
status for local node resources
should state "active on node-b
(remote node)" and the
Synchronization status should
state "synced".
www.open-e.com
49
50. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
9. Run Failback Function
IP Address:192.168.0.220
In order to test failback, click the
move to local node button in the
Resources pool manager box for
local node resources and confirm
this action by clicking the move
button.
www.open-e.com
50
51. Open-E DSS V7 Active-Active iSCSI Failover
Data Server (DSS1)
node-a
9. Run Failback Function
IP Address:192.168.0.220
After completing this step, the
status for node-a resources should
state "active on node-a (local
node)" and the Synchronization
status should state "synced".
Then, you can apply the same
actions for node-b resources.
NOTE:
The Active-Active option allows configuring resource
pools on both nodes and makes it possible to run some
active volumes on node-a and other active volumes on
node-b. The Active-Active option is enabled with the
TRIAL mode for 60 days or when purchasing the
Active-Active Failover Feature Pack. The ActivePassive option allows configuring a resource pool only
on one of the nodes. In such a case, all volumes are
active on a single node only.
The configuration and testing
of Active-Active iSCSI Failover
is now complete.
www.open-e.com
51