Follow this blog Administration + Create my blog
Cisco & Cisco Network Hardware News and Technology

LICENSING on Cisco 2960/3560/3750 Series

August 31 2015 , Written by Cisco & Cisco Router, Network Switch Published on #Cisco License

In this article, we will talk about the licensing issue on the Cisco 2900/3500/3700, including the main Cisco catalyst switches---Cisco 2960-S, 3560X/3750-X. You will read these main contents in this article:

  • License
  • Temporary License
  • 2960/2960-S
  • 3560/3750, 3560-G/3750-G, 3560-V2/3750-V2
  • 3560-E / 3750-E
  • 3560-X / 3750-X
  • Installing Software Licenses Using CLI
  • Removing Software Licenses Using CLI
  • License Installation on Switch Stacks.
  • List of Commands


These are the 3 feature sets available on 3K platform of switches

  • LAN Base: Enterprise access Layer 2 switching features.
  • IP Base: Enterprise access Layer 3 switching features.
  • IP Services: Advanced Layer 3 switching (IPv4 and IPv6) features

(IP Services has all the feature sets that Advipservices had; advipservices is End Of Sale: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps7077/eol_c51_519629.html)

Cisco 3560-E and 3750-E Series support the IP Base and IP Services feature sets

Catalyst 3560-X and 3750-X Series support the LAN Base, IP Base, and IP Services feature sets.

The software licenses are not affected by Cisco IOS software upgrades. A software license applies only to a specific feature set. A switch can have more than one software license, but you can enable only one license at a time.

-Software Activation is a feature that is preinstalled on the switch, which allows you to install the software license for a feature set.

-This Software Activation License is unique to a specific device. In other words, licenses are locked to the switch's unique device identifier(UDI).

-A unique device identifier is made up of two components: the product ID (PID) and serial number (SN). Serial number is an 11-digit number that uniquely identifies a device. The product ID identifies the type of device. This information can be found using the "show license udi" command on the switch CLI. So when you request for a license on the switch, the first thing that you need to have is this "UDI" of the device

Switch# show license udi

Device# PID SN UDI


*2 WS-C3750E-48PD-S CAT1033R1XU WS-C3750E-48PD-S:CAT1033R1XU

5 WS-C3750E-48PD-S CAT1033R1KF WS-C3750E-48PD-S:CAT1033R1KF

Temporary License

- A temporary software license is limited to a usage period (around 60 days). After the usage period expires, the switch continues to use the temporary software license until it is restarted. Before it restarts, warning messages state the switch is running the feature set without a valid license. After the switch restarts, the switch uses a valid software license based on the hierarchy (ipservices>ipbase>lanbase). If the switch does not have a valid license, it uses the IP base software license.

Switch#show license
Index 1 Feature: ipservices
       Period left: 8  weeks 4  days    <<<<<<< Limited usage period
        License Type: Evaluation
        License State: Active, Not in Use, EULA not accepted
        License Priority: None
        License Count: Non-Counted
Index 2 Feature: ipbase
        Period left: Life time
        License Type: Permanent
        License State: Active, In Use
        License Priority: Medium
        License Count: Non-Counted

Here is the link that you could use to request for a temporary license:


Note: On this link you should give the correct UDI of the switch (use "show license udi")

Cisco 2960/2960-S

Catalyst 2960 and 2960S switches run one of these images:

1. The LAN base software image: which provides enterprise-class intelligent services such as ACLs and QoS features. On a Catalyst 2960-S switch, stacking is also supported.

2. The LAN Lite image: This image provides reduced functionality.

Catalyst 2960S image ships with universal image that includes cryptographic functionality. The software image on the switch is either the LAN base or LAN Lite image, depending on the switch model.

How to determine which image your switch is running on 2960?

i. Switches running the LAN Lite image do not support the FlexStack module. They do not have a FlexStack module slot on the rear of the switch.(more on FlexStack: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps6406/white_paper_c11-578928.html)

ii. On the front of the switch, the label in the top right corner ends in –S if the switch model runs the LAN Lite image.

iii. Enter the show version privileged EXEC command. The line that shows the product ID also ends in either –L (if running the LAN base image) or –S (if running the LAN Lite image). For example, WS-C2960S-48PD-L is running LAN base; WS-C2960S-24TS-S is running LAN Lite image.

Cisco 3560/3750, 3560G/3750G, 3560V2/3750V2

Catalyst 3750 and 3560 switches run feature-specific software releases and do not support software activation. The Catalyst 3560 switch is supported by either the IP base image or the IP services image. Hence the show license command doesn't work.

3560G#show license
% Invalid input detected at '^' marker.
3560G#show license ?
% Unrecognized command

Cisco 3560E / 3750E

Catalyst 3750-E and 3560-E switches run the universal software image that has the Cisco IOS code for multiple feature sets (ipbase & ipservices). To enable a specific feature set, you must use the software activation feature to install the software license for that feature set. Catalyst 3750-E and 3560-E switches support either the noncryptographic or the cryptographic(k9 image) universal software image.

They support two software feature sets: IP Base and IP Services

Beginning with Cisco IOS Release 12.2(46)SE, the switches support these features:

- Temporary software licenses

- Rehosting a software license

- Cisco License Call Home


If the switch is running a software image earlier than Cisco IOS 12.2(46)SE, to run IP base feature - remove the IP services license from the switch, save the switch running configuration, and reload the switch. If the switch is running Cisco IOS Release 12.2(46)SE or later, enter thelicense boot level ipbase privileged EXEC command, save the switch running configuration, and reload the switch.

- If all the licenses are installed on the switch, the switch uses the highest license level, the IP services feature set.

Cisco 3560X / 3750X

Catalyst 3750-X/3560-X system is also loaded with a universal Cisco IOS Software image. Universal Cisco IOS Software images contain all Cisco IOS Software features. The level of Cisco IOS Software functionality available is determined by the combination of one (or more) licenses installed on the device. They support three software feature sets: LAN Base, IP Base, and IP Services.


For the Cisco Catalyst 3750-X/3560-X Series, in addition to universalk9 images, there are also images with the universalk9-npedesignation in the image name. The reason for this alternate image type is that some countries have import regulations that require that the device does not support any strong data-plane crypto functionality, such as IEEE 802.1AE, in any form. To satisfy the import requirements of those countries, this universal image does not support any strong payload encryption (that is, it is of the nonpayload encryption type).

Installing Software Licenses Using CLI

Step1: Log in to the switch by using the console port, the Ethernet management port, or a Telnet session.

Step2: copy license file onto the flash: device from the tftp server.

Step3: Install the license on the switch with the following command in the privilege mode:

license install file-sys:file-sys//lic-location

Once the license gets installed a log message similar to this should be seen: "%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Next reboot level = ipservices and License = ipservices"


Switch#license install flash:FDO1229V28R_20100704203238635.lic
     Installing licenses from "flash:FDO1229V28R_20100704203238635.lic"
     Extension licenses are being installed in the device with
     UDI "WS-C3560E-48PD-S:FDO1229V28R" for the following features:
Feature Name: ipservices
    You hereby  acknowledge  and  agree that  the  product feature  license
     is terminable and that the product  feature  enabled  by  such  license
     may  be  shut  down or  terminated by  Cisco  after  expiration of  the
     applicable  term  of  the license  (e.g., 30-day  trial  period). Cisco
     reserves the  right to terminate or shut down  any such product feature
     electronically  or by  any other  means available. While alerts or such
     messages  may  be provided, it is  your sole  responsibility to monitor
     your terminable  usage of any  product  feature enabled by  the license
     and to ensure that your systems and  networks are prepared for the shut
     down of the product feature. You acknowledge  and agree that Cisco will
     not have any liability  whatsoever for  any damages, including, but not
     limited to, direct, indirect, special, or consequential damages related
     to any product  feature  being shutdown or terminated. By clicking  the
     "accept" button  or typing "yes" you are  indicating  you have read and
     agree to be bound by all the terms provided herein.
     ACCEPT? (yes/[no]): yes
     1/1 licenses were successfully installed
     0/1 licenses were existing licenses
     0/1 licenses were failed to install
     5w2d: %LICENSE-6-EULA_ACCEPTED: EULA for feature ipservices 1.0 has been accepted. UDI=WS-C3560E-48PD-S:FDO1229V28R;     StoreIndex=-1:UNKNOWN License Store
     5w2d:  %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c3560e  Next reboot level = ipservices and License =     ipservices

Step4: The license is installed once you have accepted the EULA, but to enable the feature set after installing the license, you need to reload the device. Before reloading the device, the next license boot level of the switch has to be changed, use the following command to do so:

(In config mode) - license boot level license-level [switch switch-num]

If the show license all command displays the license as "Active, Not in Use, EULA not accepted," you can use the license boot level command to enable the license and accept the end-user license agreement (EULA).

Step5: Verify if the new license was installed:

- show version | in License|license

Switch#show ver | in license|License
     License Level: ipservices
     License Type: Evaluation
     Next reload license Level: ipservices

- show license detail (it’s very important to check if the EULA is accepted or not from the command).

Switch#show license det
     Index: 1        Feature: ipservices                     Version: 1.0
             License Type: Evaluation
             License State: Active, In Use
                 Evaluation total period: 8  weeks 4  days
                 Evaluation period left: 8  weeks 3  days
                 Expiry date: Apr 30 1993 00:00:25
             License Priority: Low
             License Count: Non-Counted
             Store Index: 0
             Store Name: Evaluation License Storage
     Index: 2        Feature: ipbase                            Version: 1.0
             License Type: Permanent
             License State: Active, Not in Use
             License Priority: Medium
             License Count: Non-Counted
             Store Index: 0
             Store Name: Primary License Storage

The above mentioned commands are sufficient for troubleshooting purposes, however there are other commands as well that might help under different circumstances:

- show license feature

Switch#show license feature
Feature name             Enforcement  Evaluation  Clear Allowed  Enabled
advipservices                 yes               yes              yes            yes
ipservices                       yes               yes              yes            no
ipbase                              no                 no               yes            no

(use this command to check the allowed features on the switch, as you can see this command gives you some more detail about what you could do with these features on the switch & each feature's its status)

- show license udi .
Switch#show license udi
Device#   PID                             SN                             UDI
*0        WS-C3560E-48PD-S      FDO1229V28R     WS-C3560E-48PD-S:FDO1229V28R

(this command displays the Unique Device Identifier for each switch - which can be used during license generation. If you do not provide the correct UDI while requesting for a license (from TAC OR from the license portal), then you will not be able to install that license on the switch)

Removing Software Licenses Using CLI

In software releases earlier than Cisco IOS Release 12.2(46)SE, you have the license clear license-level [switch switch-num] privileged EXEC command. Use the license-level parameter to specify the software license to remove. Use the switch switch-num parameter to specify the stack member. The switch switch-num option is supported only on Catalyst 3750-E switches.

In Cisco IOS Release 12.2(46)SE or later, if the software license is in use (active):

  • •a. Enter the “license boot level license-level” global configuration command to specify a license level different from the current one.
  • •b. Restart the switch to enable new software license.
  • •c. Enter the license clear license-level [switch switch-num] privileged EXEC command to remove previous software license.
·         Switch#license clear ipservices
·         Feature: ipservices
·             1   License Type: Evaluation
·                 License State: Active, Not in Use, EULA accepted
·                     Evaluation total period: 8  weeks 4  days
·                     Evaluation period left: 0  minute  0  second
·                 License Addition: Additive
·                 License Count: Non-Counted
·                 Comment:
·                 Store Index: 1
·                 Store Name: Primary License Storage
·         Are you sure you want to clear? (yes/[no]): yes
·         Switch#
·         5w2d:  %LICENSE-6-REMOVE: Feature ipservices 1.0 was removed from this device.  UDI=WS-C3560E-48PD-S:FDO1229V28R; StoreIndex=1:Primary License Storage
·         Backing up and saving software license information—Enter the license save {credential url | url} privileged EXEC command.

License Installation on Switch Stack



List of Commands

  • Show license [all/detail]
  • Show license udi
  • Show version | in license|License
  • Show license feature
  • License install flash:filename.lic
  • License boot level feature-set
  • License clear license-level (ex: license clear ipservices)

Reference from https://supportforums.cisco.com/document/69361/licensing-290035003700

More about Cisco’s Licensing

Cisco ONE Software Licensing Program

How to Upgrade the License from IP Base to IP Services on 3750-X Stack?

Cisco Licenses on Cisco ISR G2

Cisco 800 Series Licensing Options

Read more

GRE tunnel vs. IPsec tunnel

August 14 2015 , Written by Cisco & Cisco Router, Network Switch Published on #Cisco & Cisco Network

In the article How to Configure a GRE Tunnel?” we talked about what tunneling is and how to configure a GRE Tunnel…In this article we continue to say something about the GRE tunnel and IPsec tunnel—what are the differences?

Encapsulating a packet for secure transportation on the network can be done using either GRE or IPsec protocols. This tip explains under what circumstances each protocol works best.

Generic Routing Encapsulation (GRE), defined by RFC 2784, is a simple IP packet encapsulation protocol. GRE is used when IP packets need to be sent from one network to another, without being parsed or treated like IP packets by any intervening routers.

For example, in Mobile IP, a mobile node registers with a Home Agent. When the mobile node roams to a new network, it registers with a Foreign Agent there. Whenever IP packets addressed to the mobile node are received by the Home Agent, they can be relayed over a GRE tunnel to the Foreign Agent for delivery. It does not matter how the Home Agent and Foreign Agent communicate with each other -- hops in between just pass along the GRE packet. Only the GRE tunnel endpoints -- the two Agents -- actually route the encapsulated IP packet.

The IP Security (IPsec) Encapsulating Security Payload (ESP), defined by RFC 2406, also encapsulates IP packets. However, it does so for a different reason: To secure the encapsulated payload using encryption. IPsec ESP is used when IP packets need to be exchanged between two systems while being protected against eavesdropping or modification along the way.

For example, in a site-to-site VPN, a source host in network "A" transmits an IP packet. When that packet reaches the edge of network "A" it hits a VPN gateway. VPN gateway "A" encrypts the private IP packet and relays it over an ESP tunnel to a peer VPN gateway at the edge of network "B." VPN gateway "B" then decrypts the packet and delivers it to the destination host. Like GRE, it doesn't really matter how the two VPN gateways communicate with each other -- hops in between just pass along the ESP packet. But unlike GRE, someone at those hops could not possibly look at or change the encapsulated IP packet, even if they wanted to. That's because cryptographic algorithms have been applied to scramble the IP packet and detect any modification or replay.

Use GRE where IP tunneling without privacy is required -- it's simpler and thus faster. But, use IPsec ESP where IP tunneling and data privacy are required -- it provides security features that are not even attempted by GRE.


  • IPsec stands for Internet Protocol Security while GRE stands for Generic Routing Encapsulation.
  • IPsec is the primary protocol of the Internet while GRE is not.
  • GRE can carry other routed protocols as well as IP packets in an IP network while IPSec cannot.
  • IPsec offers more security than GRE does because of its authentication feature.

More Related Topics

Tips & Examples: Configuring a GRE Tunnel

Read more

Configuring WCCP? GRE Redirection in WCCP Creates New Tunnel Interfaces

August 11 2015 , Written by Cisco & Cisco Router, Network Switch Published on #Networking, #Data Center

The WCCP (Web Cache Communication Protocol) was initially designed as a component of IOS whose purpose was to intercept HTTP traffic traversing a router and redirects that traffic to a local cache with the aim of reducing access times to web sites and conserving wide area bandwidth. Typically the packets are redirected from their destination web server on the Internet to a content engine that is local to the client. In some WCCP deployment scenarios, redirection of traffic may also be required from the web server to the client. WCCP enables you to integrate content engines into your network infrastructure. With the introduction of WCCPv2 the scope of the protocol widened to include traffic types other than HTTP allowing the protocol to be used as a more general interception mechanism. In WCCPv2 clients specify the nature of the traffic to be intercepted and forwarded to external devices which are then in a position to provide services, based upon the traffic type, such as WAN optimisation and application acceleration.

Cisco IOS Release 12.1 and later releases allow the use of either WCCP Version 1 (WCCPv1) or Version 2 (WCCPv2).

WCCP VRF Support

The WCCP VRF Support feature enhances the existing WCCPv2 protocol by implementing support for virtual routing and forwarding (VRF).

The WCCP VRF Support feature allows service groups to be configured on a per VRF basis in addition to those defined globally.

Along with the service identifier, the VRF of WCCP protocol packets arriving at the router is used to associate cache-engines with a configured service group.

The interface on which redirection is applied, the interface which is connected to cache engine, and the interface on which the packet would have left if it had not been redirected must be in the same VRF.

In Cisco IOS Release 12.2(33) SRE, this feature is supported only on Cisco 7200 NPE-G2 and Cisco 7304-NPE-G100 routers.

Configuring WCCP

Until you configure a WCCP service using the ip wccp {web-cache | service-number} global configuration command, WCCP is disabled on the router. The first use of a form of the ip wccp command enables WCCP. By default WCCPv2 is used for services, but you can use WCCPv1 functionality instead. To change the running version of WCCP from Version 2 to Version 1, or to return to WCCPv2 after an initial change, use the ip wccp version command in global configuration mode.

If a function is not allowed in WCCPv1, an error prompt will be printed to the screen. For example, if WCCPv1 is running on the router and you try to configure a dynamic service, the following message will be displayed: "WCCP V1 only supports the web-cache service." The show ip wccp EXEC command will display the WCCP protocol version number that is currently running on your router.

Using the ip wccp web-cache password command, you can set a password for a router and the content engines in a service group. MD5 password security requires that each router and content engine that wants to join a service group be configured with the service group password. The password can consist of up to eight characters. Each content engine or router in the service group will authenticate the security component in a received WCCP packet immediately after validating the WCCP message header. Packets failing authentication will be discarded.


1. enable

2. configure terminal

3. ip wccp version {1 | 2}

4. ip wccp [vrf vrf-name] {web-cache | service-number} [group-address group-address] [redirect-list access-list] [group-list access-list] [password password [0| 7]]

5. interface type number

6. ip wccp [vrf vrf-name] {web-cache | service-number} redirect {out | in}

7. exit

8. interface type number

9. ip wccp redirect exclude in

Tunnel Interfaces

In IOS versions where WCCP is VRF aware, such as 15.0M and 15.1T, the use of GRE redirection will result in some new tunnel interfaces appearing. On the ASR platform these tunnel interfaces are also present from IOS XE release 2.5 onwards (although VRF support within WCCP on the ASR platform is not present until IOS XE release 3.1).

Examples of the new tunnel interfaces are shown below:

Router#show ip wccp summary
WCCP version 2 enabled, 3 services

Service     Clients   Routers   Assign      Redirect   Bypass    
-------     -------   -------   ------      --------   ------    
Default routing table (Router Id:
web-cache   1         1         HASH        GRE        GRE       
61          1         1         HASH        GRE        GRE       
62          1         1         HASH        GRE        GRE       

Router#show ip interface brief | include Tun
Tunnel0            YES unset  up                    up     
Tunnel1            YES unset  up                    up     
Tunnel2            YES unset  up                    up     
Tunnel3            YES unset  up                    up     

The tunnels are created automatically to process outgoing GRE encapsulated traffic for WCCP. They appear when a cache engine connects and requests GRE redirection. They're not created directly by WCCP, but indirectly via a tunnel API. WCCP has no direct knowledge of these tunnel interfaces, but knows enough to cause packets to be redirected to them. This results in the appropriate encapsulation being applied, after which the packet is then sent to the cache engine. Note that these interfaces are not used in connection with incoming WCCP GRE return packets.

There is one tunnel created per service group that is using GRE redirection, plus one additional tunnel to provide an IP address to allow the other tunnel group interfaces to be unnumbered but still enabled for IPv4. Some information about the tunnels is shown with the command show tunnel groups wccp, although this is unlikely to be useful to the end-user other than to confirm the connection between the tunnels and WCCP.

Router#show tunnel groups wccp             
 WCCP : service group 0 in "Default", ver v2, assgnmnt: hash-table
   intf: Tunnel0, locally sourced
 WCCP : service group 317 in "Default", ver v2, assgnmnt: hash-table
   intf: Tunnel3, locally sourced
 WCCP : service group 318 in "Default", ver v2, assgnmnt: hash-table
   intf: Tunnel2, locally sourced
Router#show tunnel interface t0
   Mode:multi-GRE/IP, Destination UNKNOWN, Source
   Application ID 2: WCCP : service group 0 in "Default", ver v2, assgnmnt: hash-table
   Linestate - current up
   Internal linestate - current up, evaluated up
Router#show tunnel interface t1
   Mode:multi-GRE/IP, Destination UNKNOWN, Source
   Application ID 2: unspecified
   Linestate - current up
   Internal linestate - current up, evaluated up
Router#show tunnel interface t2
   Mode:multi-GRE/IP, Destination UNKNOWN, Source
   Application ID 2: WCCP : service group 318 in "Default", ver v2, assgnmnt: hash-table
   Linestate - current up
   Internal linestate - current up, evaluated up
Router#show tunnel interface t3
   Mode:multi-GRE/IP, Destination UNKNOWN, Source
   Application ID 2: WCCP : service group 317 in "Default", ver v2, assgnmnt: hash-table
   Linestate - current up
   Internal linestate - current up, evaluated up

Note that service group number shown above is the internal tunnel representation of the WCCP service group number. Group 0 is the web-cache service, but for dynamic services subtract 256 to convert to the WCCP service group number. For interfaces used for redirection, the source address shown is the WCCP router ID.

Information relating to the connected cache engines and encapsulation, including software packet counters, can be seen with the command "show adjacency <tunnel-interface> ...":

Router#show adjacency t0              
Protocol Interface                 Address
IP       Tunnel0         
Router#show adjacency t0 encapsulation
Protocol Interface                 Address
IP       Tunnel0         
  Encap length 28
  Provider: TUNNEL
  Protocol header count in macstring: 3
    HDR 0: ipv4
       dst: static,
       src: static,
      prot: static, 47
       ttl: static, 255
        df: static, cleared
      per packet fields: tos ident tl chksm
    HDR 1: gre
      prot: static, 0x883E
      per packet fields: none
    HDR 2: wccpv2
       dyn: static, cleared
      sgID: static, 0
      per packet fields: alt altB priB
Router#show adjacency t0 detail
Protocol Interface                 Address
IP       Tunnel0         
                                   connectionid 1
                                   0 packets, 0 bytes
                                   epoch 0
                                   sourced in sev-epoch 1
                                   Encap length 28
                                   Tun endpt
                                   Next chain element:
                                    IP adj out of Ethernet0/0, addr
Router#show adjacency t0 internal
Protocol Interface                 Address
IP       Tunnel0         
                                   connectionid 1
                                   0 packets, 0 bytes
                                   epoch 0
                                   sourced in sev-epoch 1
                                   Encap length 28
                                   Tun endpt
                                   Next chain element:
                                    IP adj out of Ethernet0/0, addr
                                    parent oce 0x4BC76A8
                                    frame originated locally (Null0)
                                   L3 mtu 17856
                                   Flags (0x2808C4)
                                   Fixup enabled (0x40000000)
                                         GRE WCCP redirection
                                   HWIDB/IDB pointers 0x55A13E0/0x35F5A80
                                   IP redirect disabled
                                   Switching vector: IPv4 midchain adj oce
                                   IP Tunnel stack to in Default (0x0)
                                    nh tracking enabled:
                                    IP adj out of Ethernet0/0, addr
                                   Adjacency pointer 0x4BC74D8

For more information on configuring WCCP, please refer to the following document:


Related Information

Common WAAS/WCCP issues on interactions with Security Devices

Troubleshooting Prepositioning on WAAS 4.1.1 and above

Topic from https://supportforums.cisco.com/document/60636/gre-redirection-wccp-creates-new-tunnel-interfaces

More Cisco and IT...Networking Topics you can visit: http://blog.router-switch.com/

Read more

How to Stack Cisco 3750E and 3750X Switches?

August 7 2015 , Written by Cisco & Cisco Router, Network Switch Published on #Cisco Switches - Cisco Firewall

The issue: “There are two Cisco 3750 switches: WS-C3750E-48PD-SF and WS-C3750X-48PF-L. Both have universal IOS. So can we make the stacking of these two Cisco switches?”

How to STACK the Cisco 3750E and 3750X one? Firstly, we should know the license the two 3750s have. Well, the switch 3750E has IP Base license and the 3750X has LAN Base license. In fact, the 3750E and the 3750x-LAN base are not compatible to stack.

Cisco 3750x LanBase can only stack with other LanBase. 3750x IPBase can stack with any other 3750 (with the exeption of 3750x lanbase and some older 3750 with 16 Mb of memory)

So we need to have a license upgrade the 3750x from lanbase to ipbase and then they are able to stack with each other.

It is a license thing: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps6406/data_sheet_c78-584733.html "The Cisco Catalyst 3750-X Series Switches with LAN Base feature set can only stack with other Cisco Catalyst 3750-X Series LAN Base switches. A mixed stack of LAN Base switch with IP Base or IP Services features set is not supported."

A Cisco 3750 switch can be stacked with any other model of Cisco 3750 switches but 3750X to

Participate IP services feature set enabled otherwise Basic routing functions, including static routing and the Routing Information Protocol (RIP) will be in use.


In stacking 3750, 3750G or 3750X IOS should be identical.


This discussion you can read here…


More Related Topics

How to Upgrade the License from IP Base to IP Services on 3750-X Stack?

Cisco Switch Stacking Using a Couple of Cisco Catalyst 3650

Cisco 3750 Stacking Configuration

Read more