<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6531917183095493893</id><updated>2011-10-29T08:11:59.811-07:00</updated><category term='queue'/><category term='high-end routers'/><category term='Capex'/><category term='Telco'/><category term='Mobile Data Services'/><category term='CRS-1'/><category term='opex'/><category term='QoS'/><category term='CRS-3'/><category term='SP'/><category term='FP-140'/><category term='LTE'/><category term='internet'/><category term='MPLS'/><category term='line-rate'/><category term='MSC-40G'/><category term='Cisco'/><category term='FP-40'/><category term='MSC-140'/><title type='text'>Various thougts on TCP/IP networks</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://networkersedge.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6531917183095493893/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://networkersedge.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Networkers ASD</name><uri>http://www.blogger.com/profile/07314516798767345387</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>2</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6531917183095493893.post-4207007376859998019</id><published>2011-10-29T02:32:00.000-07:00</published><updated>2011-10-29T02:32:49.391-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='LTE'/><category scheme='http://www.blogger.com/atom/ns#' term='MSC-40G'/><category scheme='http://www.blogger.com/atom/ns#' term='high-end routers'/><category scheme='http://www.blogger.com/atom/ns#' term='SP'/><category scheme='http://www.blogger.com/atom/ns#' term='internet'/><category scheme='http://www.blogger.com/atom/ns#' term='FP-140'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><category scheme='http://www.blogger.com/atom/ns#' term='line-rate'/><category scheme='http://www.blogger.com/atom/ns#' term='Cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='MSC-140'/><category scheme='http://www.blogger.com/atom/ns#' term='queue'/><category scheme='http://www.blogger.com/atom/ns#' term='opex'/><category scheme='http://www.blogger.com/atom/ns#' term='CRS-3'/><category scheme='http://www.blogger.com/atom/ns#' term='Telco'/><category scheme='http://www.blogger.com/atom/ns#' term='QoS'/><category scheme='http://www.blogger.com/atom/ns#' term='Capex'/><category scheme='http://www.blogger.com/atom/ns#' term='CRS-1'/><category scheme='http://www.blogger.com/atom/ns#' term='FP-40'/><title type='text'>Snapshot: Transition of Line Card of High-End Router</title><content type='html'>&lt;div class="MsoNormal" style="text-align: justify;"&gt;Here I would like to  give a snapshot of development, transition and trends of high-end  router ecosystem lightly. I will not go in detail on the product itself  as it will produce a very lengthy and too technical document.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;b style="mso-bidi-font-weight: normal;"&gt;MSC-40G&lt;/b&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;When  Cisco Systems released their ultimate carrier-class high-end router  product, which was CRS-1 router, it came with one choice of line card  (forwarding), which is MSC-40G. We know that in distributed router  architecture, line card can be viewed as ‘autonomous system’ in terms of  forwarding since they are the one who do the job mostly. They act as  the real building block of the system and dictate the system real  capacity. It is not uncommon that the price of line card is more  expensive than the chassis itself.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;The  MSC-40G came with high forwarding capability. The key numbers are: 40G  line rate forwarding capacity, 256 K queuing and 65 Mpps processing  capabilities. &amp;nbsp;These figures allow transmission of 64B packet size  line-rate @40G with many services turned-on. It also allows terminating  thousands of subscribers each with multiple QoS queues. &amp;nbsp;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;The  early and subsequent adopters of Cisco CRS-1 are major Telco player and  big ISP. The Telcos were experiencing the 3GPP R4 implementation (Nb  over IP, split arch, etc) that requires the processing of relatively  small IP packet with stringent High Availability requirements, while the  ISPs &amp;nbsp;were looking for fulfillment of tremendous bandwidth demand.  CRS-1 were the ultimate choices of the customer when they went for Cisco  solution.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;b style="mso-bidi-font-weight: normal;"&gt;FP-40&lt;/b&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;Four  years later, Cisco came with newer line card for CRS-1 families, which  is FP-40 (Forwarding Processor-40). This line card comes with smaller  processing capabilities compared to MSC-40. It has only 8 queue per port  and 45 Mpps processing speed. With this number we will not be able to  do 64B packet size @40G anymore like on MSC. There are other limitations  on number of interfaces supported as well as licenses required to  enable certain level of features and scale. And of course, the price  justifies this decrease because it is only roughly 20% to 25% of  equivalent MSC-40 counterpart for delivering 40G capacity per line card.  &lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;Original  purpose of FP-40 was for internet peering and thin or light MPLS core  and edge. We know that for Internet router, we don’t need many queues  and also the internet traffic in average has bigger size (300 B and  above where 800 Bytes is common). QoS implementation in Internet router  is somewhat limited and in many occasion the big trunk is just only  configured without any sub interface and no QoS at all. With much lower  price tag, this line card justifies better to suite more competitive ISP  environment.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;The same  things applicable for what Cisco refers to ‘thin core’. This supposed to  be an IP/MPLS core network with fewer requirements on number of  interfaces, queues and line rate capabilities. While the network can  span big, but the requirements imposed are relatively small the network  can be viewed as ‘thin core’.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;Thus,  with introduction of FP-40 Cisco improves its product competitiveness  on Telco and Service Provider market and can match customer requirements  better. Customer now also has better Capex/Opex when they shop this  type of router. It is undeniable that many implementation of CRS-1 with  MSC-40 line card, the utilization is low and the scalability ceiling is  never or far away to be hit by network demand. Thus, waste of resources  is avoided by putting the FP-40 instead of MSC-40 on places within  network wherever applicable. The key here is wise or properly matching  real customer requirements and improving Capex and Opex efficiency  better.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;b style="mso-bidi-font-weight: normal;"&gt;FP-140 and MSC-140&lt;/b&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;Later,  during the battle of 100G race, Cisco released newer product on CRS  family that is called CRS-3 in 2010. This newer product has 3.5 bigger  capacities per slot than its predecessor and has a lot of improvements,  both in control plane and forwarding including power as well. &lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;The  new line card is called FP-140 and MSC-140. As the names implies, the  cards have 140G bandwidth capacity. The notable difference is that Cisco  keep &lt;b style="mso-bidi-font-weight: normal;"&gt;8 queues&lt;/b&gt; per port on FP-140 and &lt;b style="mso-bidi-font-weight: normal;"&gt;256 K queues&lt;/b&gt;  on MSC-40 plus several license based features activation. &amp;nbsp;The price  tag follows this parity where FP-140 is much cheaper than MSC-140.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;One of the key things here related to our previous discussion is the changes in IP/MPLS &lt;b style="mso-bidi-font-weight: normal;"&gt;design ‘theme’&lt;/b&gt;.  The MSC families are now pushed to the edge and the remaining portion  of the network can rely on FP line card. This means that, only  high-density customer facing will use MSC, while any P-facing interfaces  on PE, and all P interfaces can use FP (in most case). This is because  even if we have many customer or CE connected on the edge (many sub  interfaces) with multiple QoS on each of it (that can call for thousands  of individual queues, thus requires MSC), the uplink will rely on much  smaller queues requirement. For example, if the SP or Telco define 4  queues per sub interface or subscriber (best effort, data, control and  voice/video) and it has let’s say 1000 customers (thus totaling 4000  queue required on the edge facing card), but when the packet is  transport to the core it will be aggregated to only 4 queues. Thus, we  can safely introduce FP based line card in the rest of the network  including P router other than CE facing line card.&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;This  redefinition of design approach gives more competitive network  infrastructure for SP and Telcos. This combination improves Telco and SP  spending better than before since they can wisely chose better and  proper use of the FP and MSC combination of line card without easily  overrun by future requirements. Some points of the network can be MSC  based, FP-only based or proper mix among them. &lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;&lt;b style="mso-bidi-font-weight: normal;"&gt;Future Look&lt;/b&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="text-align: justify;"&gt;With  tremendous growth of data, voice and video, the bigger capacity pipe is  required on the network. The pressure for Service Providers and Telco  to monetize their investment with lower cost of spending must be  translated by any networking vendor with more innovative product. The  proliferation of coming LTE and mobile broadband will determine the  shape of high end networking product. The limit of higher-end line card  (256 K queues’ and capabilities of 64 B line rate, etc) seems still high  enough, then the battle to produce much lighter line card with lower  cost will continue faster than opposite direction.&lt;/div&gt;&lt;script type="text/javascript"&gt;  var _gaq = _gaq || [];  _gaq.push(['_setAccount', 'UA-26650148-1']);  _gaq.push(['_trackPageview']);  (function() {    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);  })();&lt;/script&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6531917183095493893-4207007376859998019?l=networkersedge.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://networkersedge.blogspot.com/feeds/4207007376859998019/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://networkersedge.blogspot.com/2011/10/snapshot-transition-of-line-card-of.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6531917183095493893/posts/default/4207007376859998019'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6531917183095493893/posts/default/4207007376859998019'/><link rel='alternate' type='text/html' href='http://networkersedge.blogspot.com/2011/10/snapshot-transition-of-line-card-of.html' title='Snapshot: Transition of Line Card of High-End Router'/><author><name>Networkers ASD</name><uri>http://www.blogger.com/profile/07314516798767345387</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></entry><entry><id>tag:blogger.com,1999:blog-6531917183095493893.post-332059070898254815</id><published>2011-10-29T01:01:00.000-07:00</published><updated>2011-10-29T02:26:53.767-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Mobile Data Services'/><category scheme='http://www.blogger.com/atom/ns#' term='LTE'/><category scheme='http://www.blogger.com/atom/ns#' term='Telco'/><category scheme='http://www.blogger.com/atom/ns#' term='Capex'/><title type='text'>The Merging of the Two Worlds : Telco and ISP convergence</title><content type='html'>This is another stories on router line card again...&lt;br /&gt;&lt;br /&gt;In the past, there are different approach used to design network for pure ISP and for Telco MPLS network. The ISP here means either pure Internet Service Provider or internet&amp;nbsp; part of big Telco network. While the Telco MPLS network means MPLS infrastructure for supporting GSM or CDMA operation.&lt;br /&gt;&lt;br /&gt;The ISP usually requires less requirements compared to the Telco counterpart in terms of redundancy, packet processing capabilities, as well as pricing.&lt;br /&gt;In terms of redundancy, for example, the ISP can tolerate two router in mated-pair redundant Routing Engine or Supervisor Engine. This means they just rely on box redundancy should one router fails, where router A can fail-over to Router B in case of failure or maintenance. Meanwhile, the Telco will push for both router (box) redundancy as well as Routing Engine / Supervisor Engine redundancy on each router. Thus, should one router engine fail, they can fail-over to its redundant Supervisor before going to fail-over to mated-pair box.&lt;br /&gt;&lt;br /&gt;In terms of packet processing capability, the internet router (the ISP one), can sustain line rate processing at higher packet size (300B, 500B, 800B, etc) while the Telco tends to make it line rate at smaller packet size (64 B for example). This is due to average internet traffic size is bigger than average voice traffic.&lt;br /&gt;Thus, when Telco start moving their GSM/CDMA traffic over IP, they tends to make perfect for everything with highest capability as possible.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The only part which ISP router demands more than Telco MPLS router may be on routing table size. Definitely ISP router needs to support full Internet routing tables while the average telco with 40M customers for example may only need to support 5000 entires of IGP in their routing table as requirement.&lt;br /&gt;&lt;br /&gt;The other side to look at it is from financial or economic perspective. The Telco are CAPEX intensive environment. A moderate Telco with 50 Million subscriber can spend&amp;nbsp; more than one billion USD per year for all their telco needs (cell site, land acquisition, L1 infrastructure, radio, PS Core, CS core, etc). Out of that 1 Billion USD, may be less than 5 percents are allocated to IP part (the routers and switches). Thus, the impact of saving on redundancy and line card are not really significant and the money is there basically. Meanwhile, ISP business are quite budget sensitive, where the cost are much smaller as well the revenue and does not have the luxury of that Telco counterpart. Their cost is easier to be mapped, for example for router, link and access-distribution. Thus, saving in router will impact their P&amp;amp;L more than the Telco part.&lt;br /&gt;&lt;br /&gt;ISP is pure IP since the beginning, while the Telco were TDM minded from the start. Thus, when the Telco were moving to IP, a lot of questions were raised whether the IP can provide TDM level of robustness and high availability. It is undeniable that a lot of resistance happened against the migration to IP, which pushed the Telco IP implementation to be as solid and as robust as possible to match the quality requirements.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;The booming of Data and Video (non voice)&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The proliferation of mobile broadband world-wide the push the data traffic to increase exponentially. This is fueled by many factor such as social networks, handset capacity, 3G services, etc. This phenomena leaves Telco in difficult situation s:&lt;br /&gt;- the data (non voice) traffic increased significantly that requires more bandwidth and associated infrastructure&lt;br /&gt;- but, the revenue from the data does not commensurate the traffic&lt;br /&gt;While the Telco still rely on voice traffic as the major part of their revenue components, the Telco operator has no choice to the data part. Despite data revenue typically are still small, they have to cope with it like it or not. Thus, they are forced to &lt;b&gt;optimize &lt;/b&gt;the investment&amp;nbsp; on infrastructure to support data and at the same time &lt;b&gt;maximize&lt;/b&gt; the effort to monetize the data services.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The optimization of the data services now force the Telco to leave the luxurious router specification they used in the past. They now become as budgetary constraint as ISP when dealing with router investment. The correct responds from the vendor now is to create more affordable line card or model that will fit with this new requirements. The line card scale limit is pushed down and the price is becoming much more affordable now.&lt;br /&gt;&lt;br /&gt;There are many approach by the telco to accommodate this&amp;nbsp; growth. One of the approach is to put investment on the growing part which is the data. In this way, the Telco split the network to accommodate the data and the network to accommodate the voice. While the data part comes with less stringent requirements, they can safely choose less powerful line card for this purpose.&lt;br /&gt;&lt;br /&gt;In summary, there are transition happens inside the Telco networks to match their new growth and data services. This transition as if merge the ISP and Telco design in terms of line card requirements. We are not talking about the LTE yet, still 2G/3G networks but still this part design transition should be addressed properly to improve overall service offering to the customer.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;script type="text/javascript"&gt;  var _gaq = _gaq || [];  _gaq.push(['_setAccount', 'UA-26650148-1']);  _gaq.push(['_trackPageview']);  (function() {    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);  })();&lt;/script&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6531917183095493893-332059070898254815?l=networkersedge.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://networkersedge.blogspot.com/feeds/332059070898254815/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://networkersedge.blogspot.com/2011/10/merging-of-two-worlds.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6531917183095493893/posts/default/332059070898254815'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6531917183095493893/posts/default/332059070898254815'/><link rel='alternate' type='text/html' href='http://networkersedge.blogspot.com/2011/10/merging-of-two-worlds.html' title='The Merging of the Two Worlds : Telco and ISP convergence'/><author><name>Networkers ASD</name><uri>http://www.blogger.com/profile/07314516798767345387</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></entry></feed>
