These are notes from a “Elephants and Mice” on elephant flow detection and mitigation in software switches. The result of tests demonstrate that integration between overlay and underlay networks has value. This solution uses low cost networking components and highlights some competitive positioning against Cisco ACI.
The post Elephant Detection in Virtual Switches & Mitigation in Hardware appeared first on EtherealMind.
For best article visual quality, open [minipost] How to fix MySQL lost table description from .frm files after emergency migration of /var/lib/mysql directly at NetworkGeekStuff.
In May 2014, networkgeekstuff.com got a small problem when the hosting BeagleBone Black went dead and the old Raspberry PI environment was on that point already used for another project. I was forced to migrate quickly to a virtual server hosting company that I use. Actually it was a performance boost and quick quick, my MySQL and Apache migration scripts for backup recovery made the transition in ~2 hours. But last week I noticed that my MySQL backup system had troubles with two WordPress tables.
The MySQLdump was telling me that two tables do not exist with this message:
root@gserver:~/scripts/tachicoma_remote_backup# mysqldump -h localhost -u mysqlbackuper -p<removed> wordpressikdata > wordpressikdata.sql
mysqldump: Got error: 1146: Table ‘wordpressikdata.wp_rfr2b_options‘ doesn’t exist when using LOCK TABLES
root@gserver:~/scripts/tachicoma_remote_backup# mysqldump -h localhost -u mysqlbackuper -p<removed> wordpressikdata > wordpressikdata.sql
mysqldump: Got error: 1146: Table ‘wordpressikdata.wp_rfr2b_options‘ doesn’t exist when using LOCK TABLES
But when I looked at /var/lib/mysql/wordpressikdata, the files for these tables are there, and show tables showed these tables as well.
mysql> show Continue reading
sed -i 's/localhost.localdomain/postfix-relay.marget.com/' /etc/sysconfig/network yum install -y nfs-utils wget tcpdump unzip autofs
service rpcbind start
service autofs restart
ln -s /net/my_nfs_server/path/to/CentOS/ /CentOS
cp /etc/yum.repos.d/CentOS-Media.repo Continue reading
I <3 the Opscode Bento project. I use the Amazon S3 hosted images for pretty much all of my Vagrant boxes. When I started to use RHEL, I didn't want to make an exception... Fortunately Bento allows you to build your own RHEL, OSX or Windows boxes using Packer. This is how I built my RHEL 6.4 x64 box, but this process should work for any other box you want to build manually...
I <3 the Opscode Bento project. I use the Amazon S3 hosted images for pretty much all of my Vagrant boxes. When I started to use RHEL, I didn't want to make an exception... Fortunately Bento allows you to build your own RHEL, OSX or Windows boxes using Packer. This is how I built my RHEL 6.4 x64 box, but this process should work for any other box you want to build manually...
I <3 the Opscode Bento project. I use the Amazon S3 hosted images for pretty much all of my Vagrant boxes. When I started to use RHEL, I didn't want to make an exception... Fortunately Bento allows you to build your own RHEL, OSX or Windows boxes using Packer. This is how I built my RHEL 6.4 x64 box, but this process should work for any other box you want to build manually...
If you are on OSX, you can install Packer using Homebrew:
brew tap homebrew/binary
brew install packer
If not, you can follow the instructions on the Packer's website
Clone bento and add your RHEL Server ISO
https://github.com/opscode/bento.git
cd bento/packer
mkdir iso
#cp your rhel-server iso here... it should be named rhel-server-6.5-x86_64-dvd.iso
packer build -only=virtualbox-iso -var 'mirror=file:///`pwd`/iso' rhel-6.5-x86_64.json
This takes a little while so go and get some coffee...
cd ..
vagrant box add rhel65x64 builds/virtualbox/opscode_rhel-6.5_chef-provisionerless.box
Then to test it, create a new Vagrant image that uses the new rhel65x64 image
cd <a tmp dir>
vagrant init
sed -i '' 's/config.vm.box = "base"/config.vm.box = "rhel65x64"/g' Vagrantfile
vagrant up
vagrant ssh
vagrant destroy
@dave_tucker
The third and final episode in the very popular series on where we attempt to discover what really happens inside your network device.
Although software will be at heart of network innovation for the enxt decade, it will still run on hardware and it's time to expose the internals of our network hardware and understand the hardware architecture inside a typical device. Many people are surprised to find that CPUs, memory, storage and buses are similar to computers while the forwarding engines are rather spectacularly different.
The post Show 190 – The Silicon Inside Your Network Device – Part 3 appeared first on Packet Pushers Podcast and was written by Greg Ferro.
Customer Premises Equipment (CPE) devices have always been a pain point for the service providers. One, they need to be installed in large large numbers (surely you remember the truck rolls that need to be sent out), and second, and more importantly, they get complex and costlier with time. As services and technology evolve, these need to be replaced with something more uglier and meaner than what existed before. In a large network, managing all the CPEs — right from the configuration, activation, monitoring, upgrading and efficiently adding more services – in itself becomes a full time job (and not the one with utmost satisfaction i must add).
ETSI’s Use case #2 describes how the CPE device can be virtualized. The idea is to replace the physical CPEs with all the services it supports on an industry standard server that is and cheaper and easier to manage. Doing this can reduce the number and complexity of the CPE devices that need to be installed at the customer sites.
The jury is still out on the specific functions that can be moved out of the CPE. Clearly, what everybody agrees to is a need for a device that will physically connect the customer to the network. Continue reading
By Matt Bing & Dave Loftus
Arbor Networks’ ASERT has recently discovered a new malware family that combines several techniques to steal payment card information. Dubbed Soraya, meaning “rich,” this malware uses memory scraping techniques similar to those found in Dexter to target point-of-sale terminals. Soraya also intercepts form data sent from web browsers, similar to the Zeus family of malware. Neither of these two techniques are new, but we have not seen them used together in the same piece of malware.
Initialization
Soraya begins by injecting itself as a thread on several system processes, including the Windows Shell explorer.exe. The malware maintains persistence by writing a copy of itself into the AppData directory with the name servhost.exe, and setting itself to execute with the registry key HKCUSOFTWAREMicrosoftWindowsCurrentVersionRunWinServHost.
New processes launched from the infected explorer.exe shell, notably web browsers, will have Soraya code injected. The malware does this by hooking calls to the ntdll.dll!NtResumeThread() function, which is responsible for process initialization. The function ntdll!NtQueryDirectoryFile() is also hooked to hide displaying the servhost.exe file. Both of these techniques are similar to functionality found in the Zeus family of malware.
Memory Scraping
One thread Continue reading
Packet Pushers Greg Ferro and Ethan Banks recently sat down with Arpit Joshipura, VP of Product Management for Dell Networking and J.R. Rivers, CEO of Cumulus Networks, to discuss their recent historic announcement to make Open Networking solutions available to consumers worldwide.
The post PQ Show 31 – Dell, Cumulus Networks and the Open Networking Revolution – Sponsored appeared first on Packet Pushers Podcast and was written by Greg Ferro.
This post represents the solution and explanation for quiz-23. The quiz shows a scenario where the network engineer has to configure Low Latency Queuing (LLQ) for some traffic that will be encrypted into an IPsec tunnel. This article presents QoS Pre-Classify and other solutions to the problem...
I don’t think I’m going to give a direct review of Cisco Live US this year. The conference was great with lots of stuff going on, but I really can’t contribute any more than the vast library of other posts on the subject. What I will do, though, is give my take on where I think the conference is headed. These are all my thoughts and have little to do with reality in some cases.
Social Events Passes. My wife had one of these this year, and it worked very well for meatspace networking and seeing the sites. So did Bob. And many others. This was the trendy thing to do this year, and it was successful for sure. I didn’t hear a single “I wish I could have seen that session” at all thanks to everything being available online afterward. Next year, I predict that a good number of attendees in my circles will opt for the cheaper pass; I would say 40% or so of the group will do so. After all, we go to see people and exchange ideas. Traditional learning can come when you get home.
Host City. San Francisco’s a great city (as others say…not me) Continue reading
You may get A referral was returned from the server. when launching Digitally signed applications like Mumble on windows.
This is normally caused by the Digital Signature expiring. You can check
 |
| Figure 1: Rise of merchant silicon |
 |
| Figure 2: Fabric: A Retrospective on Evolving SDN |
 |
| Table 1: Edge vs Fabric Functionality |
The Basic Question >>Why an IGP is necessary to support IBGP and why SYNC is necessary b/w IGP and IBGP .
Lets take rule of SYNCHRONIZATION
A BGP router with synchronization enabled will not advertise its iBGP learned routes to its eBGP peers unless it has learned or verified this route on its routing table through an IGP.
In above Topology ,
R1 R2 R3 R4 are running OSPF as IGP
R1 and R2 are IBGP Peer
R1 R5 and R2 R6 are Ebgp peer respectively.
Lets Have the config of each router
======================================================================
CONFIGURATION
=====================R1=====================
int fas1/0
no sh
ip add 9.9.15.1 255.255.255.0
!
int fas0/0
no sh
ip add 9.9.14.1 255.255.255.0
!
int lo0
ip add 9.9.0.1 255.255.255.255
!
router ospf 9
router-id 9.9.0.1
network 9.9.14.1 0.0.0.0 area 0
network 9.9.0.1 0.0.0.0 area 0
=====================R2=====================
int fas1/0
no sh
ip add 9.9.26.2 255.255.255.0
!
int fas0/1
ip add 9.9.23.2 255.255.255.0
no sh
!
int lo0
ip Continue reading
