Ads 468x60px

Thursday, June 26, 2014

The Difference of SFP , SFP+ and XFP

Hi Friends, After long time, I am posting new post on my blog.  Hope it will help you to clear basic understanding towards SFP modules. 

What is the difference of SFP, SFP+  and XFP
The 10G module has been developed from 300Pin. XENPAK, X2, XFP and finally achieve with the same size as SFP which can transmit 10G signals called SFP+.

SFP by virtue of its small cost and other advantages to meet the needs of high-density equipment, SFP+ has been replaced the XFP 10G modules and became the mainstream.

Let’s have look in bit more details –

  • The XFP ( 10G Gigabit Small Form factor Pluggable) is a standard for transceiver for high speed network links that use optical fiber.
  • It was defined by an industry group in year 2002, along with its interface to other electrical components which is called XFI.
  • A transceiver is a device comprising both a transmitter and a receiver, which is combined and share a common circuit.

XFP details –
  • XFP modules are hot-swappable and protocol independent.
  • XFP operates at optical wavelengths of 850nm, 1310nm or 1550 nm.
  • Principal applications include 10 Gbit /s Fibre Channel, Synchronous optical networking (SONET) at OC-192 rates, Synchronous optical networking STM-64, 10 Gbit /s Optical Transport Network (OTN) OTU-2, and parallel optics links
  • They can operate over a single wavelength or use dense wavelength-division multiplexing techniques
  • They include digital diagnostics that provide management that were added to the SFF-8472 standard
  • XFP modules use an LC fiber connector type to achieve high density.

The small form-factor pluggable (SFP) is a compact, hot-pluggable transceiver used for both telecommunication and data communications applications. It interfaces a network device mother board (for a switch, router, media converter or similar device) to a fiber optic cable. It is a popular industry format jointly developed and supported by many network component vendors.

SFP Detail

  • SFP transceivers are expected to perform at data speeds of up to five gigabits per second (5 Gbps), and possibly higher.
  • Because SFP modules can be easily interchanged, electro-optical or fiber optic networks can be upgraded and maintained more conveniently than has been the case with traditional soldered-in modules
  • Rather than replacing an entire circuit board containing several soldered-in modules, a single module can be removed and replaced for repair or upgrading. This can result in a substantial cost savings, both in maintenance and in upgrading efforts as compared to old in built modules.
  • SFP transceivers are designed to support SONET, Gigabit Ethernet, Fibre Channel, and other communications standards.
  • Due to its smaller size, SFP obsoletes the formerly ubiquitous gigabit interface converter (GBIC); the SFP is sometimes referred to as a Mini-GBIC although no device with this name has ever been defined in the MSAs.

The advantages of SFP+ modules:
  • SFP+ has a more compact form factor package than X2 and XFP
  • It can connect with the same type of XFP, X2 and XENPAK directly.
  • The cost of SFP+ is lower than XFP, X2 and XENPAK.

The differences between SFP and SFP+

They have the same size and appearance, but in different standard which SFP is based on IEEE802.3 and SFF-8472.

The connection between XFP and SFP+
  • Both of them are 10G fiber optical modules and can connect with other type of 10G modules.
  • The size of SFP+ is smaller than XFP, thus it moves some functions to motherboard, including signal modulation function, MAC, CDR and EDC.
  • XFP is based on the standard of XFP MSA
  • SFP+ is compliance with the protocol of IEEE802.3ae, SFF-8431, SFF-8432.
  • SFP+ is the mainstream design.
      Hope above information will help you.

      Thanks for reading !!!

Sunday, September 23, 2012

Maipu 1800 Testing Report for Load Balancing Scenario

Hi Friends, Below is testing report of Load balancing and back up scenario using Maipu 1800 Routers. 

  •  Maipu 1800 CPE router need to perform load balancing in between two outgoing interfaces F0 and F1
  •  If one WAN link is down, then another wan link will be primary, vice versa.
  • As the faulty link is restored, Both WAN link should do load balancing for LAN traffic.

Topology –

Description –
Load Balancing
Load balancing is based on a combination of source and destination packet information; it allows you to optimize resources by distributing traffic over multiple paths for transferring data to a destination. You configure load balancing on outbound interfaces on a per-destination or per-packet basis.

Types Load balancing – Per destination load balancing and Per packet load balancing.

Per-Destination and Per-Packet

Per-destination load balancing allows the router to distribute packets based on the destination address, and uses multiple paths to achieve load sharing. Packets for a given source-destination host pair are guaranteed to take the same path, even if multiple paths are available. For example, given two paths to the same network, all packets for destination1 on that network go over the first path, all packets for destination2 on that network go over the second path, and so on. Per-destination load balancing is enabled by default when you start the router, and is the preferred load balancing for most situations.
Per-packet load balancing allows the router to send successive data packets over paths without regard to individual hosts or user sessions. It uses the round-robin method to determine which path each packet takes to the destination. With per-packet load balancing enabled, the router sends one packet for destination1 over the first path, the second packet for (the same) destination1 over the second path, and so on. Per-packet load balancing ensures balancing over multiple links.
Although path utilization with per-packet load balancing is beneficial, packets for a given pair of source-destination hosts might take different paths. This means that per-packet load balancing can introduce reordering of packets. This load balancing method would be inappropriate for certain types of data traffic (such as voice traffic over IP) that depend on packets arriving at the destination in sequence.
Use per-packet load balancing to ensure that a path for a single source-destination pair does not get overloaded. If the bulk of data passing through parallel links is for a single pair, per-destination load balancing overloads a single link while other links have very little traffic. Enabling per-packet load balancing allows you to use alternate paths to the same busy destination.

Devices used in Testing –
Maipu 1800-22-AC

IOS Details –

Main Configuration:

interface fastethernet0
 description ### ISP1 ###
 ip address
 keepalive gateway

interface fastethernet0
 description ### ISP2 ###
 ip address
 keepalive gateway

interface vlan1
 description ### LOCAL LAN ###
 ip address

ip route
ip route

Output –
Show ip route
router#sh ip route
S [1/100] via, 0:01:10, fastethernet0
S [1/100] via, 0:01:04, fastethernet1

Notes –
  • By default per destination load balancing will work.
  • To configure per packet load balancing
    • router(config)#ip load-sharing per-packet
  • After above configuration, load balancing will work per packet basis.
  • As F0 (ISP-1) link is down, all LAN traffic will take F1 as primary path, vice versa.
  • After faulty link restored, Traffic will be again go with configured load balancing algorithm. 
d    Hope this testing report will help you in live network implementations. 
     Thanks for reading ...

Related Posts Plugin for WordPress, Blogger...