2013年3月21日星期四

Cisco Catalyst 6500 Supervisor 2T Technical Highlights – Will Sup2T Stop You From Buying Nexus?

Supervisor 2T engine for the Catalyst 6500E chassis. The Sup2T is a boost to keep the 6500′s legs running a little longer. I think of the 2T as a product enabling customers with a large 6500 investment to put off the inevitable migration to the Nexus platform. The 2T, by all accounts, is the end of the development roadmap for the 6500. My understanding is that the 2T takes the 6500 chassis as far as it can scale in terms of packet forwarding performance.

With the advent of the Nexus 7009, I doubt we’ll see yet another replacement 6500 chassis model (like we saw the “E” some years back). The Nexus uptake has been reasonably good for most Cisco shops, and the Nexus 7009 form factor takes away the physical space challenges faced by those previously considering the 7010 as a forklift upgrade for the widely deployed 6509. In my mind, it makes sense for Cisco to focus their Catalyst development efforts on the Catalyst 4500 line for access and campus deployments, with Nexus products running NX-OS for core routing services and data center fabric. Could I be wrong? Sure. If Cisco announced a new 6500E “plus” chassis that can scale higher, than that would reflect a customer demand for the product that I personally don’t see happening. Most of the network engineering community is warming up to the Nexus gear and NX-OS.

That baseline established,Cisco is selling the Sup2T today. What does it bring to the table? Note that anything in italics is lifted directly from the Cisco architecture document referenced below in the “Links” section.
  • Two Terabit (2080 Gbps) crossbar switch fabric. That’s where the “2T” comes from. These sups are allowing for forwarding performance up to 2 Tbps. Of course, as with previous supervisor engines, the aggregate throughput of the chassis depends on what line cards you deploy in the chassis. That old WS-X6148A you bought several years ago isn’t imbued with magical forwarding powers just because you pop a 2T into the chassis.
  • The Supervisor 2T is designed to operate in any E-Series 6500 chassis. The Supervisor 2T will not be supported in any of the earlier non E-Series chassis. You know that non-E 6500 chassis running Sup720s you love so much? Gotta go if you want to upgrade to a 2T (to which I ask the question if you’re considering this…why not Nexus 7009 instead?)
  • As far as power requirements, note the following:
    • The 6503-E requires a 1400 W power supply and the 6504-E requires a 2700 W power supply, when a Supervisor 2T is used in each chassis.
    • While the 2500 W power supply is the minimum-sized power supply that must be used for a 6, 9, and 13-slot chassis supporting Supervisor 2T, the current supported minimum shipping power supply is 3000 W.
  • Line cards are going to bite you; backwards compatibility is not what it once was. There’s a lot of requirements here, so take note.
    • The Supervisor 2T provides backward compatibility with the existing WS-X6700 Series Linecards, as well as select WS-X6100 Series Linecards only.
    • All WS-X67xx Linecards equipped with the Central Forwarding Card (CFC) are supported in a Supervisor 2T system, and will function in centralized CEF720 mode.
    • Any existing WS-X67xx Linecards can be upgraded by removing their existing CFC or DFC3x and replacing it with a new DFC4 or DFC4XL. They will then be operationally equivalent to the WS-X68xx linecards but will maintain their WS-X67xx identification.
    • There is no support for the WS-X62xx, WS-X63xx, WS-X64xx, or WS-X65xx Linecards.
    • Due to compatibility issues, the WS-X6708-10GE-3C/3CXL cannot be inserted in a Supervisor 2T system, and must be upgraded to the new WS-X6908-10GE-2T/2TXL.
    • The Supervisor 2T Linecard support also introduces the new WS-X6900 Series Linecards. These support dual 40 Gbps fabric channel connections, and operate in distributed dCEF2T mode.

To summarize thus far, a legacy 6500 chassis will need to be upgraded to a 6500E. Many older series line cards are not supported at all, or will require a DFC upgrade. Power supplies are a consideration, although the base requirements are not egregious. Therefore, moving to a 2T will require a good bit of technical and budgetary planning to get into a Sup2T. I suspect that for the majority of customers, this will not be a simple supervisor engine swap.

This diagram from Cisco shows the hardware layout of the Sup2T, focusing on all the major junction points a packet or frame could crossed through depending on ingress point, required processing, and egress point.


There are two main connectors here to what Cisco identifies as two distinct backplanes: the fabric connector, and the shared bus connector. The fabric connector provides the high-speed connectors for the newer line cards, such as the new 6900 series with the dual 40Gbps connections mentioned above. The shared bus connector supports legacy cards (sometimes referred to as “classic” cards), that is linecards with no fabric connection, but rather connections to a bus shared with similarly capable cards.

The crossbar switch fabric is where the throughput scaling comes from. Notice that Cisco states there are “26 x 40″ fabric channels in the diagram. That equates to the 2080Gbps Cisco’s talking about. The crossbar switch fabric on the Supervisor 2T provides 2080 Gbps of switching capacity. This capacity is based on the use of 26 fabric channels that are used to provision data paths to each slot in the chassis. Each fabric channel can operate at either 40 Gbps or 20 Gbps, depending on the inserted linecard. The capacity of the switch fabric is calculated as follows: 26 x 40 Gbps = 1040 Gbps; 1040 Gbps x 2 (full duplex) = 2080 Gbps.

“Full-duplex” means that what we’re really getting is 1Tbps in one direction, and 1Tbps in the other direction. The marketing folks are using weasel words to say that the Sup2T is providing a 2 terabit fabric. This marketing technique is neither new nor uncommon in the industry when describing speeds and feeds, but it is something to keep in mind in whiteboard sessions, especially if you’re planning a large deployment with specific data rate forwarding requirements.
Now here’s a strange bit. While the crossbar fabric throughput is described in the context of full-duplex, the 80Gbps per-slot is not. The 80 Gbps per slot nomenclature represents 2 x 40 Gbps fabric channels that are assigned to each slot providing for 80 Gbps per slot in total. If marketing math were used for this per slot capacity, one could argue that the E-Series chassis provides 160 Gbps per slot.

Moving onto the control-plane functions of the Sup2T, we run into the new MSFC5. The MSFC5 CPU handles Layer 2 and Layer 3 control plane processes, such as the routing protocols, management protocols like SNMP and SYSLOG, and Layer 2 protocols (such as Spanning Tree, Cisco Discovery Protocol, and others), the switch console, and more. The MSFC5 is not compatible with any other supervisor. The architecture is different from previous MSFC’s, in that while previous MSFC’s sported a route processor and a switch processor, the MSFC5 combines these functions into a single CPU.


The diagram also show a “CMP”, which is a feature enhancement of merit. The CMP is the “Connectivity Management Processor,” and seems to function like an iLO port. Even if the route processor is down on the Sup2T, you can still access the system remotely via the CMP. The CMP is a stand-alone CPU that the administrator can use to perform a variety of remote management services. Examples of how the CMP can be used include: system recovery of the control plane; system resets and reboots; and the copying of IOS image files should the primary IOS image be corrupted or deleted. Implicitly, you will have deployed an out-of-band network or other remote management solution to be able to access the CMP, but the CMP enhances our ability to recover a borked 6500 from far away.

The PFC4/DFC4 comprise the next major component of the Sup2T. The PFC4 rides as a daughter card on the supervisor, and is the hardware slingshot that forwards data through the switch. The DFC4 performs the same functions only it rides on a linecard, keeping forwarding functions local to the linecard, as opposed to passing it through the fabric up to the PFC4.

The majority of packets and frames transiting the switch are going to be handled by the PFC, including IPv4 unicast/multicast, IPv6 unicast/multicast, Multi-Protocol Label Switching (MPLS), and Layer 2 packets. The PFC4 also performs in hardware a number of other functions that could impact how a packet is fowarded. This includes, but is not limited to, the processing of security Access Control Lists (ACLs), applying rate limiting policies, quality of service classification and marking, NetFlow flow collection and flow statistics creation, EtherChannel load balancing, packet rewrite lookup, and packet rewrite statistics collection.


The PFC performs a large array of functions in hardware, including the following list I’m lifting from Cisco’s architecture whitepaper.
  • Layer 2 functions:
    • Increased MAC Address Support – a 128 K MAC address table is standard.
    • A bridge domain is a new concept that has been introduced with PFC4. A bridge domain is used to help scale traditional VLANs, as well as to scale internal Layer 2 forwarding within the switch.
    • The PFC4 introduces the concept of a Logical Interface (LIF), which is a hardware-independent interface (or port) reference index associated with all frames entering the forwarding engine.
    • Improved EtherChannel Hash – etherchannel groups with odd numbers of members will see a better distribution across links.
    • VSS support – it appears you can build a virtual switching system right out of the box with the Sup2T. There does not seem to be a unique “VSS model” like in the Sup720 family.
    • Per Port-Per-VLAN – this feature is designed for Metro Ethernet deployments where policies based on both per-port and per- VLAN need to be deployed.
  • Layer 3 functions. There’s a lot here, and rather than try to describe them all, I’m just going to hit the feature names here, grouped by category. You can read in more detail in the architecture document I link to below.
    • Performance: Increased Layer 3 Forwarding Performance
    • IPv6: uRPF for IPv6, Tunnel Source Address Sharing, IPv6 Tunnelling
    • MPLS/WAN: VPLS, MPLS over GRE, MPLS Tunnel Modes, Increased Support for Ethernet over MPLS Tunnels, MPLS Aggregate Label Support, Layer 2 Over GRE
    • Multicast: PIM Register Encapsulation/De-Encapsulation for IPv4 and IPv6, IGMPv3/MLDv2 Snooping
    • Netflow: Increased Support for NetFlow Entries, Improved NetFlow Hash, Egress NetFlow, Sampled NetFlow, MPLS NetFlow, Layer 2 Netflow, Flexible NetFlow
    • QoS: Distributed Policing, DSCP Mutation, Aggregate Policers, MicroflowPolicers
    • Security: Cisco TrustSec (CTS), Role-Based ACL, Layer 2 ACL, ACL Dry Run, ACL Hitless Commit, Layer 2 + Layer 3 + Layer 4 ACL, Classification Enhancements, Per Protocol Drop (IPv4, IPv6, MPLS), Increase in ACL Label Support, Increase in ACL TCAM Capacity, Source MAC + IP Binding, Drop on Source MAC Miss, RPF Check Interfaces, RPF Checks for IP Multicast Packets

So, do you upgrade to a Sup2T? It depends. The question comes down to what you need more: speed or features. The Sup2T is extending the life of the 6500E chassis with speed and a boatload of features. That said, you can’t scale the Cisco 6500 to the sort of 10Gbps port density you can a Nexus. Besides, most of the features found on a 6500 aren’t going to be used by most customers. If your 6500 is positioned as a core switch, then what you really need is the core functionality of L2 and L3 forwarding to be performed as quickly as possible with minimal downtime. To me, the place to go next is the Nexus line if that description of “core” is your greatest need.

If instead you need a super-rich feature set, then the question is harder to answer. The Nexus has a ways to go before offering all of the features the Catalyst does. That’s not to say that all a Nexus offers is throughput. True, NX-OS lacks the maturity of IOS, but it offers stability better than IOS-SX and features that most customers need.

In some ways, I’m making an unfair comparison. Nexus7K and Cat6500 have different purposes, and solve different problems. But for most customers, I think either platform could meet the needs. So if you’re looking for a chassis you can leave in the rack for a very long time, it’s time to look seriously at Nexus, rejecting it only if there’s some specific function it lacks that you require. If the Nexus platform can’t solve all of your problems, then you probably have requirements that are different from merely “going faster”. The 6500/Sup2T may make sense for you.

---Original reading from packetpushers.net

The Supervisor 2T provides 2-terabit system performance for 80Gbps switching capacity per slot on all Catalyst 6500 E-Series Chassis. As a result, you can:
  • Maintain investment protection through backward compatibility
  • Deliver scalability and performance improvements such as distributed forwarding (dCEF) 720Mpps with the fourth-generation Policy Feature Card (PFC4)
  • Support future 40Gbps interface and nonblocking 10Gbps modules
  • Enable new applications and services with hardware accelerated VPLS, Layer 2 over mGRE for Network Virtualization
  • Take advantage of integrated Connectivity Management Processor (CMP) for improved out-of-band management.

More Related Cisco Catalyst 6500 Supervisor 2T Review:

2013年3月19日星期二

How to Configure PPP on Cisco Router?



What is PPP?
Point-to-Point connection is one of the most common types of WAN connection. PPP connections are used to connect LANs to service provider WANs, and to connect LAN segments within an organization network. A LAN-to-WAN point-to-point connection is also referred to as a serial connection or leased-line connection, because the lines are leased from a carrier (usually a telephone company) and are dedicated for use by the company leasing the lines.

Simply, when you establish a connection to your ISP (Internet Service Provider) through a modem. The connection between the ISP and you make up two points on the network. Therefore, the protocol that is used for establishing this connectivity between the two of you is the Point-to-Point Protocol or the PPP.
Note:The default serial encapsulation method when you connect two Cisco routers is HDLC. This means, Cisco HDLC can only work with other Cisco devices. However, when you need to connect to a non-Cisco router, you should use PPP encapsulation. This is one of many advantages to using PPP it is not proprietary.

PPP can be used over twisted pair, fibre-optic lines, and satellite transmission. PPP provides transport over ATM, Frame Relay, ISDN and optical links. For security, PPP allows you to authenticate or secure connections using either Password Authentication Protocol (PAP) or the more effective Challenge Handshake Authentication Protocol (CHAP).
PPP is used to carry out the following functions
  • Data Encapsulations: this is a method used to encapsulate multi-protocol datagrams. Different network-layer protocols are simultaneously transported and encapsulated over the same link, the flexibility of the PPP design enables it to be compatible to most supporting network devices.
  • Link Control Protocol: The LCP is used to establish, configure, and test the data link connection. It’s flexible in handling different sizes of packets, detect a looped-back link, configuration errors, and terminate the link.
  • Network Control Protocol: NCP is used for establishing and configuring different Network layer protocols. PPP enables the simultaneous use of multiple Network layer protocols.  Some of the more familiar NCPs are:
u      Internet Protocol Control Protocol
u      AppleTalk Control Protocol
u      Novell IPX Control Protocol
u      Cisco Systems Control Protocol
u      SNA Control Protocol
u      Compression Control Protocol.


How to configure PPP on Cisco Router
You can configure point-to-point encapsulation, software compression, link quality monitoring, load balancing across links (multilinks) on R1, R2 and R3 serial interface below.

Before you actually configure PPP on a serial interface, we will look at the commands and the syntax of these commands as shown below. This series of examples shows you how to configure PPP and some of the options.


1. How to enable PPP on an Interface
To set PPP as the encapsulation method used by a serial or ISDN interface, use the encapsulation ppp interface configuration command.

The following example enables PPP encapsulation on serial interface 0/0/0:
R1#config t
R1(config)#interface se 0/0/0
R1(config-if)#encapsulation ppp
R1(config-if)#end

The encapsulation ppp command has no arguments, however, you must first configure the router with an IP routing protocol (RIP, EIGRP or OSPF) to use PPP encapsulation. You should recall that if you do not configure PPP on a Cisco routers, the default encapsulation for serial interfaces is HLDC.

2. How to configure Compression
You can configure point-to-point software compression on serial interfaces after you have enabled PPP encapsulation. Because this option invokes a software compression process, it can affect system performance. If the traffic already consists of compressed files (.zip, .tar, or .mpeg, for example), do not use this option.

To configure compression over PPP, enter the following commands:
R1(config)#interface serial 0/0/0
R1(config-if)#encapsulation ppp
R1(config-if)#compress [predictor | stac]
R1(config-if)#end

3. How to configure Link Quality Monitoring
One of the primary functions of LCP when establishing a PPP session includes testing of a link to determine whether the link quality is sufficient to use Layer 3 protocols. The command ppp quality {percentage} ensures that the link meets the quality requirement you set; otherwise, the link closes down.

How Link Percentage is calculated
The percentages are calculated for both incoming and outgoing directions. The outgoing quality is calculated by comparing the total number of packets and bytes sent to the total number of packets and bytes received by the destination node. The incoming quality is calculated by comparing the total number of packets and bytes received to the total number of packets and bytes sent by the destination node.

If the link quality percentage is not maintained, the link is deemed to be of poor quality and is taken down. Link Quality Monitoring (LQM) implements a time lag so that the link does not bounce up and down.

Use the configuration commands below to monitor the data traffic on the link and avoids frame looping:
R1(config)#interface serial 0/0/0
R1(config-if)#encapsulation ppp
R1(config-if)#ppp quality 80
R1(config-if)#end
Use the no ppp quality command to disable LQM.

4. How to Configure Load Balancing Across Links (MultiLinks)
Multilink PPP (also referred to as MP, MPPP, MLP, or Multilink) provides a method for spreading traffic across multiple physical WAN links while providing packet fragmentation and reassembly, proper sequencing, multivendor interoperability, and load balancing on inbound and outbound traffic.

MPPP allows packets to be fragmented and sends these fragments simultaneously over multiple point-to-point links to the same remote address. The multiple physical links come up in response to a user-defined load threshold. MPPP can measure the load on just traffic into the network, or on just traffic going out, but not on the combined load of both inbound and outbound traffic.

Use the following commands to perform load balancing across multiple links:
R1#config t
R1(config)#interface se0/0/0
R1(config-if)#encapsulation ppp
R1(config-if)#ppp multilink
R1(config-if)#end

The multilink command has no arguments. To disable PPP multilink, use the no ppp multilink command

---Original guide from orbit-computer-solutions.com
NOTE: 1900 cisco power supply, 1941 cisco router power supply, 1921 cisco power supply, 1900 cisco accessory power

2013年3月14日星期四

Main Network Hardware’s Difference--- Integrated Devices, Router, Network Switch & Firewall



If you are used to working with home networking gear, you will beused to an integrated device that “does it all”. On a home network, you may have one box that is a cable/DSL modem, router, firewall, switch, and wireless access point all in one. It is amazing all the functions they can fit into one box.

If you are studying Cisco networking and learning about how businesses use these devices, you may be wondering why there is so much importance on the differences between a switch, router, firewall, and other network devices. If the home user can have all these devices combined into one, why doesn’t the business user do this as well? So, now, here we try to find out what the main differences between these network devices.

Integrated devices
Just like home devices, business devices have become more and more consolidated over time but not to the extent that the home devices have. Network administrators in a business network are more comfortable having separate devices and even like the idea. This is because network administrators like to be able to isolate problems down to a certain device and they like to be able to know the performance capabilities of every device. If you use an integrated router, switch, and firewall all into one device, troubleshooting, managing, and understanding the performance capabilities of that device gets complicated. I’m not saying that this isn’t done. You can buy a big & expensive, chassis-based, Cisco 6500 series switch and have almost all these functions on different blades of the switch. This may be fine for a larger business with a group of administrators but to a medium size business and a single network administrator, many times, this is a scary thought.

Keep in mind that for a medium or large size business, these integrated home devices won’t work because they don’t offer all the features required. The standalone routers, switches, and firewalls have many more features than these integrated devices do.

But what is the difference between these devices anyway? Let’s cover the three most popular devices. 

Router
A router is a hardware device and has the function of routing packets between networks. A router works at Layer 3 of the OSI model – the Network Layer. This is the layer that the IP protocol works at. Most routers today are IP routers that examine the source and destination IP addresses of each packet, look up the destination of the packet in the router’s IP routing table, and route that packet on its way. In the event that the destination is not listed in the routing table, the router will either send the packet to a default router (if it has one) or drop the packet. Routers are usually used to connect a local area network to a wide-area network (a LAN to a WAN) but can also be used to segment large local area networks (LAN’s).

Routers prevent broadcasts. Another way of saying this is that routers form a broadcast domain. So, if your network is being deluged by IP broadcasts, you need to subnet your network into two or more smaller networks. Those networks would be connected by a router and that router wouldn’t allow broadcast traffic to flow between subnets.

Routers use routing dynamic protocols like OSPF, RIP, or BGP to learn routes from other routers. Router can also use static routes that are entered by the administrator.

Routers replace the Ethernet MAC address of the source device with their own MAC address when they send a packet out an interface. When the response to that packet comes back, the new source of the packet is sending the response to the destination of the router. The router receives this, replaces the source address, changes the destination address to the original address, and sends the packet back to the original sender. This is a complex topic that we could spend a whole article covering so this is only meant to provide the most basic understanding of how this works.

To show the routing table on the router, use the show ip route command. Here is an example of what a routing table looks like on a router:

Switch
A switch is a hardware device that works at Layer 2 of the OSI model – data link. The data link layer is where the Ethernet protocol works.

A switch switches Ethernet frames by keeping a table of what MAC addresses have been seen on what switch port. The switch uses this table to determine where to send all future frames that it receives. In Cisco terminology, this table is called the CAM table (content addressable memory). In general, the proper term for this table is the bridge forwarding table. If a switch receives a frame with a destination MAC address that it does not have in its table, it floods that frame to all switch ports. When it receives a response, it puts that MAC address in the table so that it won’t have to flood next time.

A switch is a high-speed multiport bridge. This is why bridges are no longer needed or manufactured. Switches do what bridges did faster and cheaper. Most routers can also function as bridges.

You might be asking how a hub fits into this mix of devices. A hub is a multiport repeater. In other words, anything that comes in one port of a hub is duplicated and sent out all other ports of the hub that have devices attached. There is no intelligence to how a hub functions. A switch is a vast improvement over a hub in terms of intelligence, for many reasons. The most important of those reasons is how the bridge forwarding table works. Intelligent (smart) switches have made hubs obsolete because they can do more at the same cost of a dumb hub. For this reason, hubs are rarely used or sold any longer.

To see this bridge forwarding table (CAM table) on a Cisco switch just type: show mac-address-table

Here is an example:

Firewall
A firewall is used to protect more secure network from a less secure network. Generally, firewalls are used to protect your internal/private LAN from the Internet.

A firewall generally works at layer 3 and 4 of the OSI model. Layer 3 is the Network Layer where IP works and Layer 4 is the Transport Layer, where TCP and UDP function. Many firewalls today have advanced up the OSI layers and can even understand Layer 7 – the Application Layer.

There are a variety of different types of firewalls and we won’t go into that in this article so let’s just talk about the most popular type of firewall – a stateful packet inspection (SPI) hardware firewall. An example of a SPI hardware firewall is a Cisco PIX firewall. This is a dedicated appliance and it looks a lot like a Cisco router.

A SPI firewall is stateful because it understands the different states of the TCP (transmission control protocol) protocol. It knows what is coming and what it going and keeps track of it all. Thus, if a packet tried to come in but it wasn’t requested, the firewall knows that and drops it.

What we have learned about the Network Hardware’s Difference: Integrated Devices, Router, Network Switch & Firewall:
  • Routers work at Layer 3 and route IP packets between networks.
  • Routers are used to connect a LAN to a WAN (such as your small network to the Internet) but they can also be used to connect segments of a large LAN that has been subnetted into smaller segments.
  • Routers route packets based on information in the IP routing table. You can see this table with the show ip route command on a Cisco router.
  • Switches work at Layer 2 and switch Ethernet frames. Switches connect multiple devices on a local area network (LAN).
  • Switches keep a table of Ethernet MAC addresses called a CAM Table or a Bridge forwarding table. You can see this table with the show mac-address-tablecommand on a Cisco switch.
  • Firewalls work at Layers 3 and 4 but some can also work at higher layers.
  • Most firewalls can keep track of the states of TCP to prevent unwanted traffic from the Internet from entering your private LAN.
---Original tip resources from petri.co.il

More Network Hardware Tips:

2012年10月11日星期四

How to Celebrate Your 10th Anniversary? Router-Siwtch.com


Router-switch.com is ten years old, happy 10th Anniversary! It is a vital phase for all router-switch.com staff in 2012. How to celebrate its 10th anniversary? What Router-switch.com Prepared for Its tenth birthday to thank its regulars and new clients? Let’s have a look!

Router-switch.com, ten years old, happy birthday! 2012 marks the tenth anniversary of router-switch.com, which is an exciting moment for all router-switch’s staff and clients.

What Router-switch.com Prepared for Its 10th Anniversary?

In 2012, router-switch.com welcomes its 10th anniversary. For router-switch.com, it has been a worldwide leading Cisco supplier during the past 10 years. To celebrate 10 years, it prepares big gifts for its regulars and new clients, such as Cisco AIR-AP1131AG-A-K9, limited edition T-shirts and 20PC U disk. Some popular Cisco products(including Cisco routers: Cisco 2900&3900 Routers, Cisco switches: Catalyst 3560x Series, Cisco Catalyst 3750x Series, Catalyst 3560V2/3750V2Cisco firewall, Cisco Access Points and network cards) will have big discounts (up to 75% off).The activity date is from September to October. Wow, if you wanna buy Cisco equipment, don’t miss it.

Router-switch.com has become a world’s leading Cisco supplier over the past ten years with the help of its staff and customers. To celebrate its 10 years, router-switch.com offers some activities for all the old and new clients, for example, big discount (save up to 75% off) for the popular Cisco items (including Catalyst 3560x Series, Cisco Catalyst 3750x Series, Catalyst 3560V2/3750V2, Cisco 2900 & 3900 Routers, Network Cards, etc.), fill out a simple survey to win a big gift (Cisco AIR-AP1131AG-A-K9, limited edition T-shirts and 20PC U disk). The activity date is from September. 01. 2012 to October. 31. 2012. Wow, if you are a Cisco buyer, don’t miss this chance. Let’s join the party to celebrate the 10th birthday together. 

2012年3月14日星期三

How Cisco Resellers and Retailers Benefit From Wholesale Cisco

For Cisco resellers, wholesale Cisco network hardware from some Cisco suppliers like Routerswitch.com is a better choice than purchasing single one from retailers.

One of the main reasons for buying wholesale Cisco equipment is that you get to save money. Held at the cost of buying in bulk is less because you can get a bigger discount for network hardware you bought or get the VIP service for wholesale customers.

If you are looking for an effective way to save money without compromising the quality of Cisco network hardware that you buy, wholesale Cisco hardware is a great choice. You know, most Cisco suppliers provide wholesale service for clients who want to buy certain CISCO items, offering biggest discount, free shipping, earlier delivery, etc.

Nowadays, due to fast development of internet, and to make shopping more convenient and easier, online store is a smart choice to select Cisco network hardware you need. Because they list detailed purchasing guide, preferential price and full info of every cisco item, which can help you buy cheaper Cisco equipment.

All in all, wholesaling CISCO network hardware (such as Cisco routers, especially for business and enterprises, Cisco switches: Catalyst 2960, 3560, 3750, 4500 and 6500, Cisco firewall: Cisco ASA 5500 series) benefit you more, biggest discount, competitive price, VIP service, free shipping, special gift, earlier delivery, etc. all these are only for wholesalers. So if necessary, wholesale Cisco network equipment is the best choice for reseller.

More related to Cisco online store

Router-switch.com is a world’s leading supplier of all the popular Cisco used network hardware sat best wholesale prices, specializing in wholesale Cisco routers, wholesale Cisco switches, wholesale Cisco firewall security, Cisco IP Phones VoIP, and variety in wholesale wireless AP, modules &cards for Cisco routers and switches, etc. And you can also directly buy Cisco network hardware through router-switch.com. More info of types, price, shipment, payment, guarantee, you can visit official website: http://www.router-switch.com/ to check.

2012年1月16日星期一

How to Configure a VLAN Cisco Router

VLANs help to organize large networks.
Configure a VLAN on a Cisco Router by using a sub interface. CISCO2811-AC-IP The sub interface commands allow you to specify that the interface should encapsulate frames according to the IEEE 802.1Q standard. You can also specify a VLAN number.

Instructions
1
 Use the name and password given to you by your system administrator to log in.
Log on the router and enter enable mode using the standard user name and password assigned to you by your system administrator. Enter an enable password if required.

2
 Identify which interface will have VLANs.
Identify which physical interface will connect to the switch and which VLAN number is in use. It is possible that more than one interface will connect to VLANs. Record each interface and the VLAN numbers that will connect to it. As an example, let's assume VLAN 25 and 26 will connect to interface Fastethernet 0/0 and VLAN 78 will connect to Fastethernet 0/1.

3. Enter configuration mode by typing "configure terminal". The prompt will change from "Router#" to "Router(config)#".

4. Create or edit a subinterface. Type "interface fastethernet 0/0.1". CISCO2811-DC The prompt will change to "Router(config-subif)#". The "1" following a period after the interface number is the subinterface number. This command will create the subinterface if it does not exist or allow you to edit subinterface 1 if it does exist.

5. Configure the subinterface with IEEE 802.1Q encapsulation and enter one of the VLAN numbers. Use the command "encapsulation dot1Q 25" to set this subinterface to handle VLAN 25.

6
 The addresses for each VLAN will come from the network design.
Enter the IP address for this VLAN. Each router virtual interface will need a unique IP address as designed in your IP address layout. For example, enter the command "ip address 192.168.1.254 255.255.255.0". Both the address and the mask should come from your IP address design.
o    7
Enter "exit" to return to the main configuration prompt of "Router(config)#"

8. Configure the remaining subinterfaces on all required physical interfaces. Use the same commands but substitute the VLAN numbers and IP address from your network plan. In this example, enter "interface fastethernet 0/0.2", "encapsulation dot1Q 26", "ip address 192.168.26.254 255.255.255.0" and "exit" to configure the second VLAN. The last VLAN in our example would be entered using the command "interface fastethernet 0/1.1", "encapsulation dot1Q 76", CISCO2811-V/K9 "ip address 192.168.76.254 255.255.255.0", "exit". When all information is entered type "end" to exit configuration mode.

9. Verify the configuration by typing "show run" at the router enable prompt of "Router#". Make sure the commands were typed in correctly and the addresses and VLAN numbers match the numbers in your plan.

10
 Don't forget to save the configuration changes.
Save the configuration by entering the command "copy running-config startup-config".

Tips & Warnings
•    The commands shown here are spelled out in long form so they may be more easily understood. A proficient Cisco operator would abbreviate the commands.
•    For example, "configure terminal" would be abbreviated to "conf t"; "interface would be abbreviated to "int"; "fastethernet" would be abbreviated to "f"; "running-config" would be abbreviated to "run" and "startup-config" C2811-VSEC/K9 would be abbreviated to "start".
•    An alternative to the command "copy run start" is "wr me", meaning "write memory."
•    Remember that the changes you make take effect immediately.
•    Be certain you are editing the subinterface.
•    Deleted subinterfaces may not actually disappear until the the next reload.

2011年12月20日星期二

Cisco Catalyst 3560 v2 Series Switches, Most Popular in Cisco Catalyst 3560 Series

The Cisco Catalyst 3560 v2 Seriesis the next-generation energy-efficient Layer 3 fast Ethernet switches. This new series of switches supports Cisco EnergyWise technology, which enables cisco catalyst 3560x 24t s companies to measure and manage power consumption of network infrastructure and network-attached devices, thereby reducing their energy costs and their carbon footprint.
Cisco3560 v2 Series switch consumes less power than its predecessors and is the ideal access layer switch for enterprise, retail, and branch-office environments, as it maximizes productivity and investment protection by enabling a unified network for data, voice, and video.
Key Features of used cisco 3560 switch in india Series
• Lower power consumption than its predecessors
• Backward compatible - uses the same Cisco IOS® Software image as the 3560 series and has the same feature set
• Full EnergyWise support to monitor energy consumption of network infrastructure and implement energy saving programs to reduce energy costs
• Compatible with Cisco Redundant Power System (RPS) 2300
• All units have a uniform depth of 11.9 inches for better cable management
•Preconfigurable with the Cisco IOS Software release at the time of ordering
• IPv6 routing included in the IP Services feature set
• DC powered stand-alone model
About ws c3560x 24t s datasheet port Switch Configurations
3560V2-24TS (hot): 24 Ethernet 10/100 ports and 2 Small Form-Factor Pluggable (SFP)-based Gigabit Ethernet ports; 1 rack unit (RU)
3560V2-48TS (hot): 48 Ethernet 10/100 ports and 4 SFP-based Gigabit Ethernet ports; 1RU
3560V2-24PS (hot): 24 Ethernet 10/100 ports with PoE and 2 SFP-based Gigabit Ethernet ports; 1 RU
3560V2-48PS (hot): 48 Ethernet 10/100 ports with PoE and 4 SFP-based Gigabit Ethernet ports; 1RU
3560V2-24TS-SD: 24 Ethernet 10/100 ports and 2 SFP-based Gigabit Ethernet ports; 1RU, DC power supply
Price and Availability
Where to buy a cost-effective switch 3560 layer 3? RouterSwitch.con is here, which can provide all items of ws c3560x 48t l datasheet at very competitive prices.
Contact details: Email: cisco@router-switch.com (Sales Inquiries)
 webmaster@router-switch.com (Technical Inquiries)
Tel:+852-3755-6766 (Hong Kong)
Fax: +852-3050-1066 (Hong Kong)
Address:7/F, Sino Centre, 582-592 Nathan Road, Mongkok Kowloon HongKong
Country:Hong Kong
Live Chat:Use the Live Chatonline our sales representatives.
MSN:cisco@router-switch.com
Notes: Cisco Catalyst 3560-E Series Switches
http://www.router-switch.com/Price-cisco-switches-cisco-switch-catalyst-3560_c22?page=3
Cisco Catalyst 3560-X Series Switches
http://www.router-switch.com/Price-cisco-switches-cisco-switch-catalyst-3560_c22?page=2