<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DEUHSX4zeSp7ImA9WhRUF0s.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420</id><updated>2012-01-28T07:57:18.081-08:00</updated><category term="Data Center" /><category term="KMIP" /><category term="Mobiles" /><category term="VXLAN" /><category term="p2p" /><category term="ipsec" /><category term="java" /><category term="cloud computing" /><category term="Security Key Life Cycle" /><category term="WAN optimization" /><category term="Multi-tenancy" /><category term="ForCES" /><category term="IPS" /><category term="programming" /><category term="LSN" /><category term="qos" /><category term="Mult" /><category term="PCIe" /><category term="Application Delivery Controller" /><category term="open source" /><category term="ddos" /><category term="3gpp" /><category term="UTM" /><category term="SDN" /><category term="jericho" /><category term="openflow" /><category term="wireless" /><category term="Server Load Balancing" /><category term="KMS" /><category term="Multicore" /><category term="Validation" /><category term="nginx" /><category term="LTE" /><category term="Offload" /><category term="TM" /><category term="GTP" /><category term="SAMLv2" /><category term="Virtualization" /><category term="NetAccess" /><category term="firewall" /><category term="OMA" /><category term="pentest" /><category term="ipv6" /><category term="LISP" /><category term="tr-069" /><title>Random technical bits and thoughts</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://netsecinfo.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>175</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/RandomTechnicalBitsAndThoughts" /><feedburner:info uri="randomtechnicalbitsandthoughts" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>RandomTechnicalBitsAndThoughts</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;CkQMSHo5eyp7ImA9WhRUEko.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-7815132785379426249</id><published>2012-01-22T14:13:00.000-08:00</published><updated>2012-01-22T14:13:09.423-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-22T14:13:09.423-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="UTM" /><category scheme="http://www.blogger.com/atom/ns#" term="NetAccess" /><title>IP Fragmentation versus TCP segmentation</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/7815132785379426249/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=7815132785379426249" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7815132785379426249?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7815132785379426249?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/ci_f9bDBfkw/ip-fragmentation-versus-tcp.html" title="IP Fragmentation versus TCP segmentation" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Ethernet Controllers are increasingly becoming more intelligent with every generation of NICs.  Intel and Broadcom have added many features in Ethernet NIC chips in recent past.  Multicore SoC vendors are adding large number of features into Ethernet IO hardware blocks.

TCP GRO (Generic Receive Offload - It used to be called Large Receive offload too) and GSO  (Generic Segmentation Offload and 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/luP1Ct00UCsrhbZny49-0mKVQzw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/luP1Ct00UCsrhbZny49-0mKVQzw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/luP1Ct00UCsrhbZny49-0mKVQzw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/luP1Ct00UCsrhbZny49-0mKVQzw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/ci_f9bDBfkw" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2012/01/ip-fragmentation-versus-tcp.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUHSX86cSp7ImA9WhRUF0s.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-7959016998574288213</id><published>2012-01-21T15:07:00.000-08:00</published><updated>2012-01-28T07:57:18.119-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-28T07:57:18.119-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="SAMLv2" /><title>SAMLv2 mini-tutorial and some good resources</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/7959016998574288213/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=7959016998574288213" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7959016998574288213?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7959016998574288213?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/6XnumoDqUhw/samlv2-and-some-good-resources.html" title="SAMLv2 mini-tutorial and some good resources" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Why SAML  (Security Assertion Markup Language)?

Single Sign-On:  Many organizations have multiple intranet servers with web front end.  Though all servers interact with common authentication database such as LDAP, SQL databases,  each server used to take authentication credentials from employee.  That is, if employee logs into server1 and then goes to server2 employees are expected to provide 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/c2h9DIX3eB_DVjFxZWD4v-vtqmE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/c2h9DIX3eB_DVjFxZWD4v-vtqmE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/c2h9DIX3eB_DVjFxZWD4v-vtqmE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/c2h9DIX3eB_DVjFxZWD4v-vtqmE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/6XnumoDqUhw" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2012/01/samlv2-and-some-good-resources.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUDQXc6eip7ImA9WhRUEUo.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-4326758683056502491</id><published>2012-01-21T12:04:00.000-08:00</published><updated>2012-01-21T12:04:30.912-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-21T12:04:30.912-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="IPS" /><category scheme="http://www.blogger.com/atom/ns#" term="UTM" /><title>Need for Pattern Matching Accelerators in UTM devices</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/4326758683056502491/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=4326758683056502491" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/4326758683056502491?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/4326758683056502491?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/z8PUV1eCCSY/need-for-pattern-matching-accelerators.html" title="Need for Pattern Matching Accelerators in UTM devices" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Network security term typically refers to Threat prevention and Security on the wire.

Threat protection is normally achieved with multiple security technologies.  Basic protection is achieved from firewall technology.  IDS/IPS (Intrusion Detection/Prevention System),  Anti-Virus, Web application firewalls are some of the security technologies that are increasingly being used to protect networks 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/lf2gFFwPgFYxFNy5xvzx1ZKtpSQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lf2gFFwPgFYxFNy5xvzx1ZKtpSQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/lf2gFFwPgFYxFNy5xvzx1ZKtpSQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lf2gFFwPgFYxFNy5xvzx1ZKtpSQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/z8PUV1eCCSY" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2012/01/need-for-pattern-matching-accelerators.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkEFQX09fyp7ImA9WhRWFEU.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-871751204191465510</id><published>2011-12-31T22:02:00.000-08:00</published><updated>2012-01-01T23:16:50.367-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-01T23:16:50.367-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="VXLAN" /><category scheme="http://www.blogger.com/atom/ns#" term="LISP" /><title>Locator and Identifier Seperation Protocol  (LISP) - One more tunnel protocol</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/871751204191465510/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=871751204191465510" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/871751204191465510?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/871751204191465510?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/Yi5L0H513Pw/locator-and-identifier-seperation.html" title="Locator and Identifier Seperation Protocol  (LISP) - One more tunnel protocol" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">
In 2012, I think that there would be focus on two technologies in network infrastructure market - SDN and  LISP (Locator and Identifier Separation Protocol).  LISP work is going on for few years and it seems to be talked about quite often in recent past.

Why LISP?

The reasons for LISP is detailed very well in the RFC 4984.  Some points of RFC 4984 are worth noting down and I am mentioned them 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/oNHtvu5II-PjhPZCU5OWUx4RlIM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/oNHtvu5II-PjhPZCU5OWUx4RlIM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/oNHtvu5II-PjhPZCU5OWUx4RlIM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/oNHtvu5II-PjhPZCU5OWUx4RlIM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/Yi5L0H513Pw" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/locator-and-identifier-seperation.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8NSHo7fip7ImA9WhRXFUQ.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-2144737792903643657</id><published>2011-12-19T19:42:00.001-08:00</published><updated>2011-12-22T15:01:39.406-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-22T15:01:39.406-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>Table Centric Processing  and Openflow</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/2144737792903643657/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=2144737792903643657" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2144737792903643657?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2144737792903643657?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/nOUkT_wDozY/table-centric-processing-and-openflow.html" title="Table Centric Processing  and Openflow" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">Software in  Embedded network appliances consists of multiple entities - Management Plane (MP), Control Plane (CP) and Data Plane (DP).  Some examples of network appliances include routers, switches,  load balancers,  security devices and WAN Optimization devices etc.. 

MP entity typically consists of management engines such as CLI,  GUI Engines and Persistent storage Engines.

CP is mainly 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/TK8e0U6JKsQurg6VRuTJKo9JRQA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TK8e0U6JKsQurg6VRuTJKo9JRQA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/TK8e0U6JKsQurg6VRuTJKo9JRQA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TK8e0U6JKsQurg6VRuTJKo9JRQA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/nOUkT_wDozY" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/table-centric-processing-and-openflow.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QDQH0_fip7ImA9WhRXE0k.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-3000588396454517051</id><published>2011-12-19T16:36:00.000-08:00</published><updated>2011-12-19T16:36:11.346-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-19T16:36:11.346-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="VXLAN" /><title>VXLAN (Virtual eXtensible LAN) - Virtual Data Centers - Tutorial</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/3000588396454517051/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=3000588396454517051" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/3000588396454517051?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/3000588396454517051?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/JTLx2Cvg91A/vxlan-virtual-extensible-lan-virtual.html" title="VXLAN (Virtual eXtensible LAN) - Virtual Data Centers - Tutorial" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>2</thr:total><content type="html">VMWare with contributions from Cisco, Citrix, Broadcom, Arista networks released IETF VXLAN draft which is a protocol to enable multiple L2 virtual networks over a physical infrastructure.  Please find that draft here.

Draft document clearly defines the problem statement and how the VXLAN is solves the problems.  I will not repeat all of them here. Some important background points are mentioned 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/IDf-RZsMOmKPVqcfGAN4I0gGqOg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IDf-RZsMOmKPVqcfGAN4I0gGqOg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/IDf-RZsMOmKPVqcfGAN4I0gGqOg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IDf-RZsMOmKPVqcfGAN4I0gGqOg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/JTLx2Cvg91A" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/vxlan-virtual-extensible-lan-virtual.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEARn0_fip7ImA9WhRXEUs.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-7363739649551192180</id><published>2011-12-15T21:38:00.001-08:00</published><updated>2011-12-17T16:20:47.346-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-17T16:20:47.346-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>Embrane - Is this SDN Play?</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/7363739649551192180/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=7363739649551192180" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7363739649551192180?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7363739649551192180?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/mBVfTPsZo2c/embrane-is-this-sdn.html" title="Embrane - Is this SDN Play?" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">Recently, I came across a company called Embrane while doing some google search on  SDN.  Then I saw a press release that Embrane made a product release announcement. I thought I would check this out and see how far it goes in SDN.  I had gone through the whitepaper published in Embrane website.  If you are interested,  you can find that paper here.

My understanding of Embrane solution:

When I 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/SaT3CizPc1zdkKfS2MYOHeZ1u2E/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SaT3CizPc1zdkKfS2MYOHeZ1u2E/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/SaT3CizPc1zdkKfS2MYOHeZ1u2E/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SaT3CizPc1zdkKfS2MYOHeZ1u2E/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/mBVfTPsZo2c" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/embrane-is-this-sdn.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUACRH8zeyp7ImA9WhRQFk4.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-4053981239796191059</id><published>2011-12-11T11:58:00.000-08:00</published><updated>2011-12-11T12:02:45.183-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-11T12:02:45.183-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>Software Defined Networking - Java Role</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/4053981239796191059/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=4053981239796191059" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/4053981239796191059?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/4053981239796191059?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/grXc4x9RnG4/software-defined-networking-java-role.html" title="Software Defined Networking - Java Role" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Controller component of Openflow based SDN is supposed to have most of the  networking intelligence.  One might have gathered by this time that the SDN is expected to provide programmability of network devices rather than simple configurability.  SDN Controller component is going to be complex entity in SDN. Software Engineering principles tell us that complexity is only manageable with 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3tbKXYR4xlvqDgmAdw3AALeeMuw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3tbKXYR4xlvqDgmAdw3AALeeMuw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/3tbKXYR4xlvqDgmAdw3AALeeMuw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3tbKXYR4xlvqDgmAdw3AALeeMuw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/grXc4x9RnG4" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/software-defined-networking-java-role.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak4BQXY7fCp7ImA9WhRQE0o.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-4479623851298122207</id><published>2011-12-07T23:18:00.000-08:00</published><updated>2011-12-08T13:15:50.804-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-08T13:15:50.804-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><category scheme="http://www.blogger.com/atom/ns#" term="ForCES" /><title>ForCES (Forwarding and Control Element Separation) and Openflow 1.1 -  Contrasting them</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/4479623851298122207/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=4479623851298122207" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/4479623851298122207?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/4479623851298122207?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/EnlL-okQCNw/forces-forwarding-and-control-element.html" title="ForCES (Forwarding and Control Element Separation) and Openflow 1.1 -  Contrasting them" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><content type="html">At very high level, both ForCES and Openflow protocols separate Control plane and Data plane.  Both protocols are intended to drive Software Defined Networking.

Some terminology differences:

Software Driven Networking versus Software Defined Networking :  Both are same, but different terms are used.  ForCES uses Software Driven Networking.  Openflow is created in the context of Software Defined
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ymN8wIOWPFwFgcUFtVlELC9qPZE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ymN8wIOWPFwFgcUFtVlELC9qPZE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ymN8wIOWPFwFgcUFtVlELC9qPZE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ymN8wIOWPFwFgcUFtVlELC9qPZE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/EnlL-okQCNw" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/forces-forwarding-and-control-element.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEFRHkzeip7ImA9WhRQEk4.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-942022007920524718</id><published>2011-12-04T15:32:00.001-08:00</published><updated>2011-12-06T22:00:15.782-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-06T22:00:15.782-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>Openflow 1.1 protocol tutorial</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/942022007920524718/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=942022007920524718" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/942022007920524718?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/942022007920524718?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/Vm1345XJbP0/openflow-11-protocol-tutorial.html" title="Openflow 1.1 protocol tutorial" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Openflow protocol is a TCP/SSL based protocol between controllers and switches.  Switch is expected to initiate a connection to the Controller.  For each datapath instance, switch device is expected to make a connection.  If the switch supports X number of datapaths (instances), then X number of connections are established.

As you might have guessed by this time,  Openflow is a protocol that 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/g-N8uO7Pfgvz5gkSUY8uFbHSfok/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/g-N8uO7Pfgvz5gkSUY8uFbHSfok/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/g-N8uO7Pfgvz5gkSUY8uFbHSfok/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/g-N8uO7Pfgvz5gkSUY8uFbHSfok/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/Vm1345XJbP0" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/openflow-11-protocol-tutorial.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C04BQnk6fip7ImA9WhRQEE4.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-2875146687689420498</id><published>2011-12-04T12:52:00.000-08:00</published><updated>2011-12-04T12:52:33.716-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-04T12:52:33.716-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="GTP" /><category scheme="http://www.blogger.com/atom/ns#" term="LTE" /><category scheme="http://www.blogger.com/atom/ns#" term="3gpp" /><category scheme="http://www.blogger.com/atom/ns#" term="ipsec" /><category scheme="http://www.blogger.com/atom/ns#" term="wireless" /><title>Dual Stack Support in LTE eNodeB - Technical bit</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/2875146687689420498/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=2875146687689420498" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2875146687689420498?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2875146687689420498?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/lWkCZLmYfpE/dual-stack-support-in-lte-enodeb.html" title="Dual Stack Support in LTE eNodeB - Technical bit" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">This technical bit summarizes the type of functionality expected out of Dual stack in user plane of eNodeB.

Introduction

eNodeB connects to UE on Air interface side  and connect to multiple types of devices in the core network over backhaul network.  It communicates with MME,  S1 Gateways via Security Gateways.

GTP-U layer is the relay module which transfers the packets to/from UE to wireless 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Y7ixYlMhhXMWFwrjLmwPn2lLsDo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Y7ixYlMhhXMWFwrjLmwPn2lLsDo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Y7ixYlMhhXMWFwrjLmwPn2lLsDo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Y7ixYlMhhXMWFwrjLmwPn2lLsDo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/lWkCZLmYfpE" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/12/dual-stack-support-in-lte-enodeb.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkEFQn4zeip7ImA9WhRRFkw.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-1277472184922126730</id><published>2011-11-29T03:49:00.000-08:00</published><updated>2011-11-29T15:50:13.082-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-29T15:50:13.082-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>Software Defined Networking Trend - Winners</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/1277472184922126730/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=1277472184922126730" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/1277472184922126730?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/1277472184922126730?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/WqbuM8YbQxc/software-defined-networking-trend.html" title="Software Defined Networking Trend - Winners" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">It is not given that the SDN is going to be successful, though there are very high chances of it due to push from Network operators.  Unlike earlier efforts, some vendors have resigned to the fact that SDN will become successful and have/are-having products ready in the market.

Let us see who would be the winners if SDN picks up.


Certainly Network Operators/Service Providers/Data Center 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tLlLa19Lppp7RlY86r3trHRNX_k/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tLlLa19Lppp7RlY86r3trHRNX_k/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tLlLa19Lppp7RlY86r3trHRNX_k/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tLlLa19Lppp7RlY86r3trHRNX_k/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/WqbuM8YbQxc" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/11/software-defined-networking-trend.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUASHYzeCp7ImA9WhRRFEk.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-7888953818383866696</id><published>2011-11-27T16:28:00.000-08:00</published><updated>2011-11-27T18:44:09.880-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-27T18:44:09.880-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>My views on SDN (Software Defined Networking) phases</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/7888953818383866696/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=7888953818383866696" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7888953818383866696?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7888953818383866696?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/o3tlEsV62bY/my-views-on-sdn-software-defined.html" title="My views on SDN (Software Defined Networking) phases" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">In my last post, I have talked about the need for SDNs.  I wanted to give my views on how SDN is going to play out in the market place.

Phase 1 -  Openflow based Data path implementations (Hybrid implementation)

Device Side:  Many L2 and L3 switch  vendors are providing Openflow1.0  based implementation in their switches.  Almost all these devices continue to support existing L2/L3 switching 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jlqxyENhWTmj0HE16zmd-r6QppY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jlqxyENhWTmj0HE16zmd-r6QppY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jlqxyENhWTmj0HE16zmd-r6QppY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jlqxyENhWTmj0HE16zmd-r6QppY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/o3tlEsV62bY" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/11/my-views-on-sdn-software-defined.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYCQ3kzcCp7ImA9WhRRFEk.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-300825548661995392</id><published>2011-11-27T10:21:00.000-08:00</published><updated>2011-11-27T18:42:42.788-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-27T18:42:42.788-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="SDN" /><category scheme="http://www.blogger.com/atom/ns#" term="openflow" /><title>Software Defined Networking (SDN)</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/300825548661995392/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=300825548661995392" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/300825548661995392?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/300825548661995392?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/9APosNBNlnw/software-defined-networking-sdn.html" title="Software Defined Networking (SDN)" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Before going into the details of SDN,  it is required to revisit the current networks and different network devices within the network.   Then this post talks about the problems associated with network devices as seen by service providers and network operators.  I try to describe how SDNs are expected to solve the issues faced by network operators.  

Current Networks

Current Networks consists 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/kQCeIOJfyJbUslgszQMeRpFkomU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/kQCeIOJfyJbUslgszQMeRpFkomU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/kQCeIOJfyJbUslgszQMeRpFkomU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/kQCeIOJfyJbUslgszQMeRpFkomU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/9APosNBNlnw" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/11/software-defined-networking-sdn.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04ERH04eyp7ImA9WhdXEk8.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-214253008937982557</id><published>2011-07-30T02:02:00.000-07:00</published><updated>2011-08-24T16:51:45.333-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-24T16:51:45.333-07:00</app:edited><title>Key-Value Store using Memcached  - Microservers &amp; Embedded Multicore processors</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/214253008937982557/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=214253008937982557" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/214253008937982557?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/214253008937982557?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/Ccshb-D-zdg/key-value-store-using-memcached.html" title="Key-Value Store using Memcached  - Microservers &amp; Embedded Multicore processors" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">  
What is Microserver?

It is explained multiple ways in the Industry.  Intel defines it as ""We define it as any server with a large number of nodes, usually with a  single socket or multiple low-power processors and shared  infrastructure,".   Serverwatch article on Microservers - small footprint, powerful punch article characterizes it as "The difference between microservers and server  
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/VIZXWt72gpZuEdLDKm82jqJbD48/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/VIZXWt72gpZuEdLDKm82jqJbD48/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/VIZXWt72gpZuEdLDKm82jqJbD48/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/VIZXWt72gpZuEdLDKm82jqJbD48/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/Ccshb-D-zdg" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/07/key-value-store-using-memcached.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMBRX85eip7ImA9WhZWF04.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-6949091831129310607</id><published>2011-04-18T21:39:00.000-07:00</published><updated>2011-05-18T10:07:34.122-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-05-18T10:07:34.122-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><title>Hibernate Versus JDBC</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/6949091831129310607/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=6949091831129310607" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/6949091831129310607?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/6949091831129310607?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/n5_YZJ9Zlqc/hibernate-versus-jdbc.html" title="Hibernate Versus JDBC" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Long back I worked on a project in Java, Centralized Management System, to  manage multiple networking devices.  At that time  I remember having a  big debate on whether to use Hibernate for Java Object persistence or use JDBC directly.  We have finally decided to use Hibernate at that time.

I happened to come across this link which talks about 'when to use Hibernate' and also provides 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/W90srgL24hVw2eOP5UfOKENt63w/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/W90srgL24hVw2eOP5UfOKENt63w/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/W90srgL24hVw2eOP5UfOKENt63w/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/W90srgL24hVw2eOP5UfOKENt63w/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/n5_YZJ9Zlqc" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/04/hibernate-versus-jdbc.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YARHY7eSp7ImA9WhdTE04.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-5077843074099615284</id><published>2011-04-17T08:10:00.000-07:00</published><updated>2011-07-10T14:59:05.801-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-10T14:59:05.801-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Multi-tenancy" /><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><title>Cloud Multi-Tenancy Support - Authentication, Authorization and Auditing requirements</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/5077843074099615284/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=5077843074099615284" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/5077843074099615284?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/5077843074099615284?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/uS6ylCRu-eM/cloud-multi-tenancy-support.html" title="Cloud Multi-Tenancy Support - Authentication, Authorization and Auditing requirements" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Authentication and Authorization requirements are common in any web based applications.  Authentication is the process by which the application takes the user credentials, typically using 'log-in' forms and checks the existence of user by checking against user databases (LDAP,  RDBMS, RADIUS etc..).    Authorization is the process in which application allows the access to different parts of 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/qNio13BjdOdN_PTlAZFUIiY2k0I/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qNio13BjdOdN_PTlAZFUIiY2k0I/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/qNio13BjdOdN_PTlAZFUIiY2k0I/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qNio13BjdOdN_PTlAZFUIiY2k0I/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/uS6ylCRu-eM" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/04/cloud-multi-tenancy-support.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkAESHwzeip7ImA9WhZTFkg.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-2114913616517256874</id><published>2011-03-20T12:51:00.000-07:00</published><updated>2011-03-20T12:51:49.282-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-20T12:51:49.282-07:00</app:edited><title>Experience with installing VMware Server 2.0 on windows 7</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/2114913616517256874/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=2114913616517256874" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2114913616517256874?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2114913616517256874?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/roC-hfeClLI/experience-with-installing-vmware.html" title="Experience with installing VMware Server 2.0 on windows 7" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">I was helping a friend to install Ubuntu 10.10 Linux on Windows 7 using VMware server 2.0.

I  had few hiccups, but finally could do it.
Installation of VMware Server was a breeze.  No issue found in downloading and installing.  Just follow the instructions given in VMware site. 
After VMware Server was installed, you would see few entries  at "Start"  of windows 7,  All Programs-&amp;gt;VMWare-&amp;gt;VMware 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/1z2dwwGO6XPpRIIinwT9jEZFgJ4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1z2dwwGO6XPpRIIinwT9jEZFgJ4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/1z2dwwGO6XPpRIIinwT9jEZFgJ4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1z2dwwGO6XPpRIIinwT9jEZFgJ4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/roC-hfeClLI" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/03/experience-with-installing-vmware.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A08FQng4cSp7ImA9Wx9aGUo.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-534718780919935566</id><published>2011-03-12T17:30:00.000-08:00</published><updated>2011-03-12T17:30:13.639-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-12T17:30:13.639-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="firewall" /><category scheme="http://www.blogger.com/atom/ns#" term="UTM" /><title>IGMP Filtering - Developer tips</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/534718780919935566/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=534718780919935566" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/534718780919935566?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/534718780919935566?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/aP4QBMPfEqk/igmp-filtering-developer-tips.html" title="IGMP Filtering - Developer tips" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>3</thr:total><content type="html">IGMP protocol allows hosts to report their interest in Multicast address membership with adjacent routers.  These adjacent routers in turn propagate the consolidate membership with upstream routers using PIM-SM or using IGMP proxy functionality. 

IGMP protocol sits right on top of IP layer, at the same level as ICMP, UDP and TCP.  IGMPv1 and IGMPv2 protocols are older protocols to IGMPv3.  
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/qLf7YGv2z-TLFeHz1aA7DMpuOKY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qLf7YGv2z-TLFeHz1aA7DMpuOKY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/qLf7YGv2z-TLFeHz1aA7DMpuOKY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qLf7YGv2z-TLFeHz1aA7DMpuOKY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/aP4QBMPfEqk" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/03/igmp-filtering-developer-tips.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEAGSXg4eCp7ImA9Wx9aGUg.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-8830436662617541579</id><published>2011-02-05T09:25:00.000-08:00</published><updated>2011-03-12T09:58:48.630-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-12T09:58:48.630-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><category scheme="http://www.blogger.com/atom/ns#" term="UTM" /><title>Clustering of devices with traffic distribution by L2 Switch - One limitation &amp; Mitigation</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/8830436662617541579/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=8830436662617541579" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8830436662617541579?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8830436662617541579?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/i_T4ZaGjr9Y/clustering-of-devices-with-traffic.html" title="Clustering of devices with traffic distribution by L2 Switch - One limitation &amp; Mitigation" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">In my last post on "Data Center/Enterprises Clustering of Devices"  I discussed on how L2 switches are enabling device equipment vendors to provide cluster solution to take up the increasing load on the networks.  Many L2 switches are capable of analyzing multiple different types of  layer 2 headers to get to the inner IP packet and use inner IP packet source and destination IP address fields to 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/D19ACShY76OH9sDZBZ8nNiVxiGQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/D19ACShY76OH9sDZBZ8nNiVxiGQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/D19ACShY76OH9sDZBZ8nNiVxiGQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/D19ACShY76OH9sDZBZ8nNiVxiGQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/i_T4ZaGjr9Y" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/02/clustering-of-devices-with-traffic.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUIDSXYzfSp7ImA9WhRXFEk.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-8393146863573178260</id><published>2011-02-03T22:43:00.000-08:00</published><updated>2011-12-20T20:59:38.885-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-20T20:59:38.885-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="UTM" /><category scheme="http://www.blogger.com/atom/ns#" term="Multicore" /><title>Data Center/Enterprises - Clustering of Network devices</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/8393146863573178260/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=8393146863573178260" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8393146863573178260?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8393146863573178260?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/UyK_BxkqxY4/data-centerenterprises-clustering-of.html" title="Data Center/Enterprises - Clustering of Network devices" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Throughput requirements of Data center/Enterprise network equipment are going up with increased traffic in data centers and Enterprises.  In addition,  computational requirements of network equipment are also going up.  Some examples of why more computation power is required.
 Intrusion Detection/Prevention now requires almost 3 - 4 times the  computation power on per Mbps of traffic than what 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/GqlDi1KzHx4_vd6YLd1gUXjyDSk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GqlDi1KzHx4_vd6YLd1gUXjyDSk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/GqlDi1KzHx4_vd6YLd1gUXjyDSk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GqlDi1KzHx4_vd6YLd1gUXjyDSk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/UyK_BxkqxY4" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/02/data-centerenterprises-clustering-of.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkADQ3w4eSp7ImA9Wx9bEkk.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-8536194049013910636</id><published>2011-01-08T14:59:00.000-08:00</published><updated>2011-02-20T15:32:52.231-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-20T15:32:52.231-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="Offload" /><title>Data Center Equipment &amp; Offload card requirements</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/8536194049013910636/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=8536194049013910636" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8536194049013910636?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8536194049013910636?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/BDsTxHUHTZs/data-center-equipment-offload-card.html" title="Data Center Equipment &amp; Offload card requirements" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">I  have been attending some web conferences focusing on Data Center equipment.  From last few years,  there are more and more discussions on offloading some processing out of current data center equipment. Before getting details on offload functions,  it is good to revisit some of data center equipment.

Data centers, whether they are private, public or cloud,  have following equipment.

L2/L3 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/CcUI6i8ZQ39BfLUFOcqj5UctHYE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CcUI6i8ZQ39BfLUFOcqj5UctHYE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/CcUI6i8ZQ39BfLUFOcqj5UctHYE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CcUI6i8ZQ39BfLUFOcqj5UctHYE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/BDsTxHUHTZs" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2011/01/data-center-equipment-offload-card.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQNSXwzcSp7ImA9Wx9bEUk.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-7245622313679389830</id><published>2010-12-30T20:12:00.000-08:00</published><updated>2011-02-19T12:46:38.289-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-19T12:46:38.289-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Data Center" /><category scheme="http://www.blogger.com/atom/ns#" term="Multicore" /><title>What are Traffic Monitoring Enabler Switches?</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/7245622313679389830/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=7245622313679389830" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7245622313679389830?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/7245622313679389830?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/rScjKRXWJnM/what-are-traffic-monitoring-enabler.html" title="What are Traffic Monitoring Enabler Switches?" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">There is increasing trend of  Traffic Monitoring Enabler Switches (TMES) in Enterprise, Data Center and Service provider environments.

Need for TMES:

Traffic monitoring devices are increasingly becoming requirement for networks in Enterprise, Data Center and Service provider environments.  There are multiple types of monitoring devices are being deployed in networks.
Traffic Monitoring for 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/IAoBL5nOr8siCZFrPpbSy6_No10/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IAoBL5nOr8siCZFrPpbSy6_No10/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/IAoBL5nOr8siCZFrPpbSy6_No10/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IAoBL5nOr8siCZFrPpbSy6_No10/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/rScjKRXWJnM" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2010/12/what-are-traffic-monitoring-enabler.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8HRXg_fyp7ImA9Wx9XEE0.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-2722073799885356180</id><published>2010-12-26T13:08:00.000-08:00</published><updated>2011-01-02T13:47:14.647-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-02T13:47:14.647-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><category scheme="http://www.blogger.com/atom/ns#" term="Multicore" /><title>User space Packet processing applications - Execution Engine  differences with processors</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/2722073799885356180/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=2722073799885356180" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2722073799885356180?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/2722073799885356180?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/aFL9Fqn5U0U/user-space-packet-processing_26.html" title="User space Packet processing applications - Execution Engine  differences with processors" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Please read this post to understand Execution Engine.

Many processors with descriptor based IO devices have their own interrupts.  For each device, there is corresponding UIO device.  Hence software poll based EE provides 'file descriptor' based interface to register, deregister and get hold of indication through callbacks.  EE applications are expected to read the packets from the the hardware 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/6b1tCOX0qsn9dojVZOBwHWwceNU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6b1tCOX0qsn9dojVZOBwHWwceNU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/6b1tCOX0qsn9dojVZOBwHWwceNU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6b1tCOX0qsn9dojVZOBwHWwceNU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/aFL9Fqn5U0U" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2010/12/user-space-packet-processing_26.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkcCR347fip7ImA9Wx9QGU4.&quot;"><id>tag:blogger.com,1999:blog-7423916798868500420.post-8241412509351293307</id><published>2010-12-19T22:07:00.000-08:00</published><updated>2011-01-01T18:07:46.006-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-01T18:07:46.006-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><category scheme="http://www.blogger.com/atom/ns#" term="Multicore" /><title>User space Packet processing applications - Execution Engine</title><link rel="replies" type="application/atom+xml" href="http://netsecinfo.blogspot.com/feeds/8241412509351293307/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7423916798868500420&amp;postID=8241412509351293307" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8241412509351293307?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7423916798868500420/posts/default/8241412509351293307?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/RandomTechnicalBitsAndThoughts/~3/_sGS81B5rEY/user-space-packet-processing.html" title="User space Packet processing applications - Execution Engine" /><author><name>Srini</name><uri>http://www.blogger.com/profile/10768905151790759421</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">If you plan to port your data plane network processing application from Linux kernel space to user space,  first thing you would think is how you can port your software to user space with minimal changes to your software.  Execution Engine is the first thing one would think of.

Many kernel based networking applications don't create their own threads.  They work with the threads which are already
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/aULSDKifrLT1aHXdXSO74-lTFME/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/aULSDKifrLT1aHXdXSO74-lTFME/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/aULSDKifrLT1aHXdXSO74-lTFME/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/aULSDKifrLT1aHXdXSO74-lTFME/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/RandomTechnicalBitsAndThoughts/~4/_sGS81B5rEY" height="1" width="1"/&gt;</content><feedburner:origLink>http://netsecinfo.blogspot.com/2010/12/user-space-packet-processing.html</feedburner:origLink></entry></feed>

