<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on the bin</title><link>https://thebin.net/tags/networking/</link><description>Recent content in Networking on the bin</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 06 Aug 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://thebin.net/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon VPC Basics</title><link>https://thebin.net/2018/08/amazon-vpc-basics/</link><pubDate>Mon, 06 Aug 2018 00:00:00 +0000</pubDate><guid>https://thebin.net/2018/08/amazon-vpc-basics/</guid><description>&lt;p&gt;For the past five weeks we have been getting deep in our Scalable Solutions series.  At Entasis we work with our customers to help them build solutions that are Scalable in design, Resilient by nature, with Performance on demand.  We feel that these three components are the pillars that all truly scalable solutions are built with.  Here is what we have gone over thus far:&lt;/p&gt;&#10;&lt;p&gt;Week 1 – &lt;a href="https://thebin.net/2018/07/amazon-route-53-basics/"&gt;Amazon Route 53 Basics&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Solaris 11: Configure IP Over Infiniband Devices</title><link>https://thebin.net/2014/12/solaris-11-configure-ip-over-infiniband-devices/</link><pubDate>Mon, 08 Dec 2014 00:00:00 +0000</pubDate><guid>https://thebin.net/2014/12/solaris-11-configure-ip-over-infiniband-devices/</guid><description>&lt;p&gt;In this article we will be going over the configuration of an infiniband interface with the IPoIB protocol on Solaris 11, specifically Solaris 11.2 (previous versions of Solaris 11 should work the same, however there have been changes in the ipadm and dladm commands).&lt;/p&gt;&#10;&lt;p&gt;Identify Infiniband Datalinks&lt;/p&gt;&#10;&lt;p&gt;First we need to identify the underlying interfaces of the infiniband interfaces.  In my case net2 and net3.&lt;/p&gt;&#10;&lt;div class="codeblock" data-lang="bash"&gt;&#10; &lt;div class="codeblock__bar"&gt;&#10; &lt;span class="codeblock__lang"&gt;bash&lt;/span&gt;&#10; &lt;button type="button" class="codeblock__copy" aria-label="Copy code"&gt;&#10; &lt;span class="codeblock__copy-label"&gt;Copy&lt;/span&gt;&#10; &lt;/button&gt;&#10; &lt;/div&gt;&#10; &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;dladm show-phys&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;LINK MEDIA STATE SPEED DUPLEX DEVICE&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;net1 Ethernet unknown &lt;span class="m"&gt;0&lt;/span&gt; unknown ixgbe1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;net0 Ethernet up &lt;span class="m"&gt;1000&lt;/span&gt; full ixgbe0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;net2 Infiniband up &lt;span class="m"&gt;32000&lt;/span&gt; unknown ibp0&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;net3 Infiniband up &lt;span class="m"&gt;32000&lt;/span&gt; unknown ibp1&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;net5 Ethernet up &lt;span class="m"&gt;1000&lt;/span&gt; full vsw0&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;Another way to confirm the infiniband interfaces is to use the show-ib command.&lt;/p&gt;</description></item><item><title>Linux KVM: Bridging a Bond on CentOS 6.5</title><link>https://thebin.net/2014/10/linux-kvm-bridging-a-bond-on-centos-6-5/</link><pubDate>Mon, 27 Oct 2014 00:00:00 +0000</pubDate><guid>https://thebin.net/2014/10/linux-kvm-bridging-a-bond-on-centos-6-5/</guid><description>&lt;p&gt;Today we are going to hop back into the KVM fray, and take a  look at using CentOS as a hypervisor., and configuring very resilient network connections to support our guests.  Of course these instructions should be valid on Red Hat Linux and Oracle Linux as well, though there is a little more to be done around getting access to the repos on those distributions…&lt;/p&gt;&#10;&lt;h2 id="enable-bonding"&gt;Enable Bonding&lt;/h2&gt;&#10;&lt;p&gt;I am assuming this is a first build for you, so this step might not be applicable, but it won’t hurt anything.&lt;/p&gt;</description></item><item><title>Solaris Networking: Datalink Multipathing Protocol</title><link>https://thebin.net/2014/05/solaris-networking-datalink-multipathing-protocol/</link><pubDate>Mon, 19 May 2014 00:00:00 +0000</pubDate><guid>https://thebin.net/2014/05/solaris-networking-datalink-multipathing-protocol/</guid><description>&lt;p&gt;In this article we are going to go over Datalink Multipathing Protocol (DLMP) available in Solaris.  DLMP is similar to IPMP, however there are some key differences, the biggest being the layer at which it operates.  DLMP operates at the datalink layer of the OSI model, while IPMP operates at the network layer.  Due to the differences in those layers DLMP opens up a lot of possibilities that were not possible with IPMP.  For example if you had a requirement for redundant networking for a service, either IPMP and DLMP would both be able to meet that requirement very well.  However if you had a requirement that the service runs inside of a zone or a logical domain then the level of work in IPMP becomes much higher.  This is because these hypervisors assign datalink devices to their guests.  Since the redundancy for IPMP is built on a level higher we need to assign multiple non-redundant interfaces to the guests and then build the interfaces and IPMP groups inside each of the guests.&lt;/p&gt;</description></item><item><title>Solaris Networking: IP Multipathing Protocol</title><link>https://thebin.net/2013/09/solaris-networking-ip-multipathing-protocol/</link><pubDate>Tue, 10 Sep 2013 00:00:00 +0000</pubDate><guid>https://thebin.net/2013/09/solaris-networking-ip-multipathing-protocol/</guid><description>&lt;p&gt;In this article we are going to go over some basics of using IPMP in Solaris.  We will discuss this on the latest versions of Solaris 10 and 11 on the SPARC platform, these instructions should also work on the x86 platform, but will be dependent on the listed version numbers, as the networking stack has changed alot of the past few minor versions of Solaris 10 and 11.&lt;/p&gt;&#10;&lt;h2 id="solaris-111"&gt;Solaris 11.1&lt;/h2&gt;&#10;&lt;p&gt;Create an IPMP Group&lt;/p&gt;</description></item><item><title>Powerconnect: Configure Link Aggregation Groups</title><link>https://thebin.net/2013/07/powerconnect-configure-link-aggregation-groups/</link><pubDate>Tue, 16 Jul 2013 00:00:00 +0000</pubDate><guid>https://thebin.net/2013/07/powerconnect-configure-link-aggregation-groups/</guid><description>&lt;p&gt;Today we will be configuring LACP to interconnect some switch stacks as part of a network upgrade.  Please keep in mind that part of configuring the LAG will result in the ports losing connectivity, so while it is not necessary to use a console cable, please keep in mind how you are connecting to the switch and if you will interrupt that connection by any of your actions, and plan accordingly.&lt;/p&gt;</description></item><item><title>Dell Powerconnect 6200: Enable SSH and Disable Telnet</title><link>https://thebin.net/2013/07/dell-powerconnect-6200-enable-ssh-and-disable-telnet/</link><pubDate>Mon, 08 Jul 2013 00:00:00 +0000</pubDate><guid>https://thebin.net/2013/07/dell-powerconnect-6200-enable-ssh-and-disable-telnet/</guid><description>&lt;p&gt;Most modern switches include the ability to use SSH as a remote communications protocol.  Here we will enable that functionality and disable telnet on the Dell Powerconnect 6248 switches.&lt;/p&gt;&#10;&lt;h2 id="enable-ssh"&gt;Enable SSH&lt;/h2&gt;&#10;&lt;p&gt;In order to enable SSH we need to generate the keys which will be used by SSH to encrypt the traffic.&lt;/p&gt;&#10;&lt;div class="codeblock" data-lang="text"&gt;&#10; &lt;div class="codeblock__bar"&gt;&#10; &lt;span class="codeblock__lang"&gt;text&lt;/span&gt;&#10; &lt;button type="button" class="codeblock__copy" aria-label="Copy code"&gt;&#10; &lt;span class="codeblock__copy-label"&gt;Copy&lt;/span&gt;&#10; &lt;/button&gt;&#10; &lt;/div&gt;&#10; &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;console&amp;gt;enable&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;console# configure&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;(config)# crypto key generate rsa&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;(config)# crypto key generate dsa&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;(config)# ip ssh server&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;(config)# exit&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;console# copy running-config startup-config&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="disable-telnet"&gt;Disable Telnet&lt;/h2&gt;&#10;&lt;p&gt;Depending on your config you might not need to disable this, but if it is enabled you should disable it.&lt;/p&gt;</description></item><item><title>Linux KVM: Ubuntu 12.10 with Openvswitch</title><link>https://thebin.net/2012/10/linux-kvm-ubuntu-12-10-with-openvswitch/</link><pubDate>Wed, 24 Oct 2012 00:00:00 +0000</pubDate><guid>https://thebin.net/2012/10/linux-kvm-ubuntu-12-10-with-openvswitch/</guid><description>&lt;p&gt;Today I am revisiting my previous post on Openvswitch on Ubuntu 12.04.  Things have changed since then.  Previously Openvswitch was relatively new and as such the userland tools (with libvirt being the one I use) didn’t support it yet, so while you could have used Openvswitch by executing the kvm processes for each VM manually.  Since this was a predictable problem the Openvswitch guys created a brcompat module, which would take the place of the bridge_utils functionality and expose Openvswitch bridges as legacy bridges.  This allowed the existing userland which already had the legacy bridge functionality builtin to continue to operate the same way.  Anyways as of libvirt 0.9.11 the native Openvswitch functionality is present and supported.  As such I am updating my documentation to include this alternate and preferred method of operation.&lt;/p&gt;</description></item><item><title>Solaris 11: DNS Client Configuration Using Svccfg</title><link>https://thebin.net/2012/05/solaris-11-dns-client-configuration-using-svccfg/</link><pubDate>Wed, 23 May 2012 00:00:00 +0000</pubDate><guid>https://thebin.net/2012/05/solaris-11-dns-client-configuration-using-svccfg/</guid><description>&lt;p&gt;In Solaris 11, alot of configurations are being moved from configuration files into the Service Management Framework.  Here we will discuss this change around the DNS client.&lt;/p&gt;&#10;&lt;h2 id="view-existing-dns-client-configuration"&gt;View Existing DNS Client Configuration&lt;/h2&gt;&#10;&lt;div class="codeblock" data-lang="bash"&gt;&#10; &lt;div class="codeblock__bar"&gt;&#10; &lt;span class="codeblock__lang"&gt;bash&lt;/span&gt;&#10; &lt;button type="button" class="codeblock__copy" aria-label="Copy code"&gt;&#10; &lt;span class="codeblock__copy-label"&gt;Copy&lt;/span&gt;&#10; &lt;/button&gt;&#10; &lt;/div&gt;&#10; &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;svccfg -s network/dns/client listprop config&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config application&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config/value_authorization astring solaris.smf.value.name-service.dns.client&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config/domain astring test.local&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config/nameserver net_address 10.0.0.152&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="update-existing-dns-client-configuration"&gt;Update Existing DNS Client Configuration&lt;/h2&gt;&#10;&lt;p&gt;Here we will update our name servers.  In this case we are replacing the original with two different addresses.&lt;/p&gt;</description></item><item><title>Solaris 11: Change Hostname Using Svccfg</title><link>https://thebin.net/2012/05/solaris-11-change-hostname-using-svccfg/</link><pubDate>Tue, 22 May 2012 00:00:00 +0000</pubDate><guid>https://thebin.net/2012/05/solaris-11-change-hostname-using-svccfg/</guid><description>&lt;p&gt;When Solaris 11 was released more configurations were moved into the service management framework, and moved out of configuration files, one of these changes was the hostname/nodename.&lt;/p&gt;&#10;&lt;p&gt;View Hostname in SMF&lt;/p&gt;&#10;&lt;p&gt;This will read back the configuration out of the SMF.&lt;/p&gt;&#10;&lt;div class="codeblock" data-lang="bash"&gt;&#10; &lt;div class="codeblock__bar"&gt;&#10; &lt;span class="codeblock__lang"&gt;bash&lt;/span&gt;&#10; &lt;button type="button" class="codeblock__copy" aria-label="Copy code"&gt;&#10; &lt;span class="codeblock__copy-label"&gt;Copy&lt;/span&gt;&#10; &lt;/button&gt;&#10; &lt;/div&gt;&#10; &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;svccfg -s system/identity:node listprop config&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config application&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config/nodename astring solaris11box&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;config/loopback astring solaris11box&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="change-hostname-in-smf"&gt;Change Hostname in SMF&lt;/h2&gt;&#10;&lt;p&gt;We have two separate settings, which need to be updated.&lt;/p&gt;</description></item><item><title>Linux-KVM: Ubuntu 12.04 with Openvswitch</title><link>https://thebin.net/2012/03/linux-kvm-ubuntu-12-04-with-openvswitch/</link><pubDate>Mon, 26 Mar 2012 00:00:00 +0000</pubDate><guid>https://thebin.net/2012/03/linux-kvm-ubuntu-12-04-with-openvswitch/</guid><description>&lt;h2 id="update-october-29-2012"&gt;UPDATE: October 29, 2012&lt;/h2&gt;&#10;&lt;p&gt;This article doesn’t work on Ubuntu 12.10, to use Ubuntu 12.10 please refer to my new article &lt;a href="http://blog.allanglesit.com/2012/10/linux-kvm-ubuntu-12-10-with-openvswitch/"&gt;here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;Openvswitch is a better way of managing your virtual networking stacks for KVM and Xen.  This can be used instead of the bridge-utils package, and has the ability to use VLANs, LACP, QoS, sFlow, and others.  In this article we will be using Ubuntu 12.04 (beta1) to configure Openvswitch to hand out networking interfaces to KVM guests.&lt;/p&gt;</description></item><item><title>Adventures in ZFS: Configuring iSCSI Targets</title><link>https://thebin.net/2012/02/adventures-in-zfs-configuring-iscsi-targets/</link><pubDate>Mon, 27 Feb 2012 00:00:00 +0000</pubDate><guid>https://thebin.net/2012/02/adventures-in-zfs-configuring-iscsi-targets/</guid><description>&lt;p&gt;The most critical thing about any storage implementation is flexibility.  This means that you need to be able to adapt your solution to changing environmental considerations.  The nice thing about a ZFS-based solution is that all of the building blocks are available.  If you want to use it as a NAS device, you can use CIFS, NFS.  If you want to provision Fibre Channel that is available too.  Even some of the more sought after SAN features are included, replication, deduplication, thin-provisioning, and many more.  Now in todays article we are going to discuss how you can go about setting up iSCSI targets.  I personally am not a fan of iSCSI (I have been bitten by the hard knee too many times), however you really can’t argue with the flexibility that is provided by being able to quickly provision storage on already existing or readily available hardware.  The best thing about this process is that it is really similar to provisioning fibre channel targets, so if you are familiar with this process (&lt;a href="http://blog.allanglesit.com/2011/08/adventures-in-zfs-configuring-fibre-channel-targets/"&gt;available here&lt;/a&gt;) then you will be able to quickly adapt to the iSCSI variation.&lt;/p&gt;</description></item><item><title>Solaris 11: Network Configuration Advanced</title><link>https://thebin.net/2011/03/solaris-11-network-configuration-advanced/</link><pubDate>Tue, 29 Mar 2011 00:00:00 +0000</pubDate><guid>https://thebin.net/2011/03/solaris-11-network-configuration-advanced/</guid><description>&lt;p&gt;In my previous post we went over the basics of configuring a network interface in Solaris 11, without using the Network Auto Magic (NWAM) which is enabled by default.  In this article we will go over some of the more advanced features which can be leveraged including VLANs, aggregation groups, and jumbo frames.&lt;/p&gt;&#10;&lt;h2 id="configure-vlan-tagging"&gt;Configure VLAN Tagging&lt;/h2&gt;&#10;&lt;p&gt;Create a VLAN, specify the VLAN id with the “-v”, then specify the interface with the “-l”, and finally create a name for the tagged interface (in this case user0 since this particular system is the user VLAN, if you have more descriptive names of your VLANs you can use them here).&lt;/p&gt;</description></item><item><title>Solaris 11: Network Configuration Basics</title><link>https://thebin.net/2011/03/solaris-11-network-configuration-basics/</link><pubDate>Mon, 28 Mar 2011 00:00:00 +0000</pubDate><guid>https://thebin.net/2011/03/solaris-11-network-configuration-basics/</guid><description>&lt;p&gt;I have been doing research for my next big series “So You Want to Learn ZFS.”  This series is basically going to be a multi-part series of How-To’s which hopefully will give you the ability to build a file server (or even a SAN) based on ZFS if you so choose.  However there are a few things that I failed to take into account.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Solaris 11 is so different from Solaris 10.&lt;/li&gt;&#10;&lt;li&gt;Solaris 11 is so different from EVERYTHING else.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;I figured that I’d be able to kind of gloss over the high points of how to get your system up and running and just dive right into the fun ZFS stuff.  So before we get into the good stuff there are some basics that we will need to go over first.  Today we will cover basic networking.&lt;/p&gt;</description></item></channel></rss>