Chapter 2 - Navigating in Cisco IOS

Navigating in Cisco IOS

Once, you have connected to your Cisco switch or router console port, and power up the device you will see some information displayed during the start of the device. If the device has no initial configuration you are presented with:

Pic. 1 - System Configuration Dialog

You can safely cancel this request as its capability to configure the device is not very impressive. Instead, you are going to do things all professionals do: command after command.

What follows is bunch of messages sent to the screen and after hitting the Enter key few times you get something like this (here is the router, but a switch would introduce itself as ... Switch>


Router>

IOS Modes (contexts)

This prompt of the device tells you in which 'context' you are, and the one above with the '>' character is known as 'user exec mode' or 'privilege level 1 mode'. You can't configure much in this mode of operation. It is designed as a 'monitoring' mode not a 'configuration' one. Also, the monitoring capability is limited. For instance, you can't see the running configuration of the device.

Type in the following command:

Router>enable

Router#

The prompt changes to '#' which is called 'privileged exec mode', 'enabled mode' or sometimes 'privilege level 15 mode'. I would like to draw your attention to two things here. Both modes of operation (or contexts, if you like) have two things in common:

1. They are used primarily to monitor the device (you will be using 'show' and 'debug' commands in those modes).
2. They are context for immediate execution of your commands. If the syntax is correct, system executes the command immediately.

Those two modes differ from one another as well:

1. User Exec Mode - is limited in terms of what information will be available.
2. Enabled Exec Mode - gives the operator ALL information (like root or Administrator account on a computer).

Question Mark 

As the commands take many attributes your best friend is the question mark '?'. This help is known as the 'context-sensitive help'. This means that depending on which context you use, while typing a question mark (?) the system is going to list the commands that can be executed in that particular mode of operation. See more in the attached video.

Configurations

In order to configure things in Cisco IOS (except for some minor changes), you must enter the 'global configuration mode' first which is characterized by the following prompt:

Router(config)#

This context can be accessed by typing the following command in the 'privileged exec mode':

Router#configure terminal

Whatever you configure this particular mode it is going to be applied to the device as a whole unit (e.g. hostname, default gateway on a switch etc.).

If you want to enter the context of the interface to configure it with some parameters like ip address, speed, duplex, description etc. , you must enter that interface from the global configuration mode like the one below:

Router(config)#interface fastethernet1/0

If you do not know what interfaces your device has, type the following command in the enabled mode:

Router#show ip interface brief

As you see, in the 'global configuration mode' I did the following actions in order to access the context of the interface:

1. Entered the interface type (here: Fast Ethernet).
2. Referenced the module number (here: 1)
3. Referenced the port number in the module 1 (here: 0)

Please, note that routers count ports starting from 0, switches starting from 1.

You'll learn other contexts as we go through numerous labs and video presentations.

Abbreviations

You don't have to type in the full words of the commands and certain attributes that follow the commands. For instance, instead of typing:

Router#configure terminal

Router(config)#

You can type:

Router#conf t

Router(config)#

As long as the abbreviation uniquely describes which command you want to use, the system has no problem accepting it.

Shortcuts And Keystrokes

When you type enough of the characters that uniquely identify the command in a given context you can use 'tab' key and the system is going to complete the command on the screen for you (just like in Linux).

I often use the following keystrokes while editing the commands:

• CTRL-z - takes the cursor back to the 'enabled exec' mode from any other context
• CTRL-a - takes the cursor to the beginning of the line
• CTRL-e - takes the cursor to the end of the line
• CTRL-k - erases everything to the right of the cursor
• CTRL-u - erases everything to the left of the cursor
• Upper Arrow or CTRL-P - displays previous command from the history buffer
• Lower Arrow or CTRL-N - displays next command from the history buffer

System keeps the record of up to ten (default) commands you typed in. You can increase/decrease the history buffer up to 256 commands.

If you want to check the history buffer size, type in:

Router#show terminal | include history

Changing the buffer size can be accomplished with the following command in the 'enabled mode'

Router#terminal history size 256

The above command  will increase the size of the history buffer to 256 commands.

If you want to see the buffer (which commands were typed) use this command:

Router#show history



*Next lesson is going to be about creating an initial configuration of our router and/or switch.

Chapter 1 - Connecting to Cisco Console Port with MINICOM

If you are a linux user user you must learn how to connect to your Cisco router or switch using roll-over cable (the cable that comes with your device).

Step1 - Installing Minicom

Linux users will use application called 'minicom'.  If you are Ubuntu user you can install it using either 'Synaptic Package Manager' or type in the following in your terminal window:

$ sudo apt-get install minicom

Once it is installed, you must configure the 'minicom' to communicate with the console port of your router/switch. 

Step 2 - Connection to Console Port

Power up your router/switch and connect the roll-over cable to your computer's serial port (DB-9) and to the 'console' port of your router/switch (RJ-45).

Step 3 - Configure Minicom

Open your Terminal window (Applications ==> Accessories ==> Terminal) and type in:

$ minicom -s

Scroll down to 'Serial Port Setup' and hit Enter:

Pic:1

Choose 'A' to set up the serial port of your computer (here the first serial port is referenced as ttyS0) so it reads as highlighted below. Then hit Enter again to accept the change:

Pic:2

Next, press 'E' and then 'C' again to access the transmission speed and change it to '9600' value (no apostrophies). You should see values like highlighted below:

Pic:3

Then hit Enter twice to get back to the first screen (Pic.1)

The last thing is to save this configuration (you can choose 'dfl' to be the default template or with some other name).

Pic. 4

If you chose 'dflp and then, 'Exit from Minicom', you can try out your work now. Type in:

$ minicom

and hit Enter

You should see the console prompt of your router/switch. If you want to leave the minicom use CTRL-A keystroke and then type 'x' and confirm you want to leave the application.

CCleaner 3.19.1721

CCleaner is a freeware system optimization, privacy and cleaning tool. It removes unused files from your system - allowing Windows to run faster and freeing up valuable hard disk space. It also cleans traces of your online activities such as your Internet history. Additionally it contains a fully featured registry cleaner. But the best part is that it's fast (normally taking less than a second to run) and contains NO Spyware or Adware! 
Cleans the following:

Internet Explorer
Firefox
Google Chrome
Opera
Safari
Windows - Recycle Bin, Recent Documents, Temporary files and Log files.
Registry cleaner
Third-party applications
100% Spyware FREE


Title: CCleaner 3.19.1721
Filename: ccsetup319.exe
File size: 3.68MB (3,862,112 bytes)
Requirements: Windows 2000 / XP / 2003 / Vista / Windows7 / XP64 / Vista64 / Windows7 64
Languages: Multiple languages
License: Freeware
Date added: May 24, 2012
Author: Piriform

Click Me To Download

====================================================

VLC Media Player 2.0.1

VLC media player is a highly portable multimedia player for various audio and video formats as well as DVDs, VCDs, and various streaming protocols without external codec or program.

It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.

VLC can play:

MPEG-1, MPEG-2 and MPEG-4 / DivX files from a hard disk, a CD-ROM drive, and so on
DVDs, VCDs, and Audio CDs
From satellite cards (DVB-S)
Several types of network streams: UDP/RTP Unicast, UDP/RTP Multicast, HTTP, RTSP, MMS, etc.
From acquisition or encoding cards (on GNU/Linux and Windows only)

Title: VLC Media Player 2.0.1
Filename: vlc-2.0.1-win32.exe
File size: 21.23MB (22,259,528 bytes)
Requirements: Windows 2000 / XP / 2003 / Vista / Windows7 / XP64 / Vista64 / Windows7 64
Languages: Multiple languages
License: Open Source
Date added: March 19, 2012
Author: VideoLAN.org


Download Link:-

http://nchc.dl.sourceforge.net/project/vlc/2.0.1/win32/vlc-2.0.1-win32.exe

______________________________________

_______________

______

How to Make Explorer Always Show the Full Path in Windows 8

How to Make Explorer Always Show the Full Path in Windows 8

In older versions of Windows the Title Bar used to display your current location in the file system. In Windows 8 this is not the default behavior, however, you can enable it if you wish to.

Display the Full Path in the Windows Explorer Title Bar

Press the Windows + E keyboard combination to open Windows Explorer and then switch over to the View tab.

On the right-hand side click on options and then select Change folder and search options from the drop-down.

When the Folder Options dialog opens, switch over to the View options.

Here you will need to tick the Display the full path in the title bar check box.

That’s all there is to it.

_________________________________________________________________

File Systems (FAT, HPFS, NTFS)

File Systems:

At the BIOS level, a disk partition contains sectors numbered 0, 1, etc. Without additional support, each partition would be one large dataset. Operating systems add a directory structure to break the partition up into smaller files, assign names to each file, and manage the free space available to create new files.

The directory structure and methods for organizing a partition is called a File System. Different File Systems reflect different operating system requirements or different performance assumptions. Unix, for example, has the convention that lower-case and uppercase are different in file names, so "sample.txt" and "Sample.txt" are two different files. DOS and the systems that descend from it (Windows 95, OS/2, and Windows NT) ignore case differences when finding file names. Some File Systems work better on small machines, others work better on large servers.

Each partition is assigned a type (in the MBR for primary partitions, in the Extended Partition directory for logical volumes). When the partition is formatted with a particular File System, the partition type will be updated to reflect this choice.

The same hard disk can have partitions with File Systems belonging to DOS, OS/2, NT, and Linux (or other Unix clones). Generally, an operating system will ignore partitions whose type ID represents an unknown file system type. It is fairly easy (given a big enough disk) to install all of the different operating systems and all of the File System types. There are a few rules to make things simple.

Each File System is described in detail in a separate section.

FAT File System:

The FAT File system is used by DOS and is supported by all the other operating systems. It is simple, reliable, and uses little storage.

VFAT:

VFAT is an alternate use of the FAT file system available in Windows 95 and Windows NT 3.5. It allows files to have longer names than the "8.3" convention adopted by DOS. VFAT stores extra information in the directory that older DOS and OS/2 systems can ignore.

HPFS:

HPFS is used by OS/2 and is supported by Windows NT. It provides better performance than FAT on larger disk volumes and supports long file names. However, it requires more memory than FAT and may not be a reasonable choice on systems with only 8 megs of RAM.

NTFS:

NTFS provides everything. It supports long file names, large volumes, data security, and universal file sharing. A departmental NT file server will probably have all its partitions formatted for NTFS. Because the other operating systems cannot use it, NTFS is less attractive on personal desktop workstations or portables.

File Systems and Disk Letters:

DOS and Windows 95 can only boot from the C: disk. Technically, the C: letter will be assigned to the first Primary Partition on the first hard disk that has a FAT file system. In no case can DOS boot from a second hard disk or a logical volume in the extended partition. However, if as the system comes up, the DOS boot sector and DOS files turn out to be on the second Primary Partition on the first hard disk, then this will not be a problem so long as the first partition has a non-FAT file system. DOS simply ignores primary partitions that are formatted for other operating systems.

Some people exploit this feature. They put an HPFS or NTFS file system on the first Primary Partition, and a FAT file system on the second. This can produce confusion. When the other operating system boots up, it will now assign letter C: to its first partition, and the disk that DOS calls "C:" will become "D:" on the other system. If the two systems share application programs, it becomes very difficult to configure INI files as the drive letter keeps changing back and forth. It is a simpler and safer strategy to accept the view that the first Primary Partition on the first hard disk should be formatted with the FAT file system and should be the C: drive in every operating system.

Choosing a File System:

The performance problems with FAT have been greatly reduced by various strategies to use Cache memory and to periodically DEFRAG the disk. FAT is the only system fully supported by DOS and Windows 95. It is also a perfectly acceptable choice under Windows NT and OS/2. FAT systems require the least memory and are the best choice on small machines.

Although it is simpler to manage a few larger volumes, FAT performance degrades with volume size. The distance between the directory and the data increases the disk movement, and larger allocation units waste space. A good rule of thumb would limit FAT volumes to a maximum of 255 megabytes.

FAT proven to be quite reliable and is fairly immune to damage. When the system crashes, FAT can "misplace" disk space that was being allocated to a file. CHKDSK (or Microsoft's newer SCANDISK) will recover the missing space. Less frequently a really serious error could leave the same sector of disk space assigned to two different files. Such "crosslinked" files are damaged, and once this occurs the entire volume is suspect. The preferred recovery would be to back everything up, reformat the volume, and restore the data. Crosslinked files could be produced by a damaged operating system, or by a hardware problem in the disk subsystem itself.

HPFS is supported by OS/2 and Windows NT. Although it is not officially supported by DOS or Windows 95, there are shareware drivers (such as AMOS3) that can provide these systems with at least Read-Only access to HPFS files. Since OS/2 does not support VFAT, it cannot use long file names on a FAT volume. Many OS/2 software packages require long file names. An OS/2 system with enough memory and disk space should have at least one HPFS volume to support such packages.

Only Windows NT can use data on an NTFS volume. NTFS is required to provide full security on an NT File Server, and to support Macintosh datasets. On desktop workstations that run other operating systems as well as NT, NTFS is probably more trouble than it is worth.

A good general principle is to put FAT volumes first on a disk, then HPFS, and finally NTFS. All the systems will see the FAT volumes and will assign them disk letters. With device drivers for DOS, all the system will see the HPFS volumes as well. The NTFS volumes will only be available to Windows NT and will be ignored by the other systems.

___________________________________________________________

End-of-Sale and End-of-Life Announcement for the Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches

Cisco announces the end-of-sale and end-of-life dates for the Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches. The last day to order the affected product(s) is January 30, 2013. Customers with active service contracts will continue to receive support from the Cisco Technical Assistance Center (TAC) as shown in Table 1 of the EoL bulletin.

Table 1 describes the end-of-life milestones, definitions, and dates for the affected product(s). Table 2 lists the product part numbers affected by this announcement. For customers with active and paid service and support contracts, support will be available until the termination date of the contract, even if this date exceeds the Last Date of Support shown in Table 1.

Please note that the list price of some of the products listed in this announcement may increase in the next 12 months.

Table 1. End-of-Life Milestones and Dates for the Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches.

Milestone	Definition	Date
End of Life Announcement Date	The date the document that announces the end-of-sale and end-of-life of a product is distributed to the general public.	January 31, 2012
End-of-Sale Date	The last date to order the product through Cisco point-of-sale mechanisms. The product is no longer for sale after this date.	January 30, 2013
Last Ship Date: Hardware	The last-possible ship date that can be requested of Cisco and/or its contract manufacturers. Actual ship date is dependent on lead time.	April 30, 2013
End of SW Maintenance Releases Date: Hardware	The last date that Cisco Engineering may release any final software maintenance releases or bug fixes. After this date, Cisco Engineering will no longer develop, repair, maintain, or test the product software.	January 30, 2014
End of Routine Failure Analysis Date: Hardware	The last-possible date a routine failure analysis may be performed to determine the cause of hardware product failure or defect.	January 30, 2014
End of New Service Attachment Date: Hardware	For equipment and software that is not covered by a service-and-support contract, this is the last date to order a new service-and-support contract or add the equipment and/or software to an existing service-and-support contract.	January 30, 2014
End of Vulnerability/Security Support: OS Software	The last date that Cisco Engineering may release a planned maintenance release or scheduled software remedy for a security vulnerability issue.	January 30, 2016
End of Service Contract Renewal Date: Hardware	The last date to extend or renew a service contract for the product.	April 30, 2017
Last Date of Support: Hardware	The last date to receive service and support for the product. After this date, all support services for the product are unavailable, and the product becomes obsolete.	January 31, 2018

HW = Hardware OS SW = Operating System Software App. SW = Application Software

Table 2. Product Part Numbers Affected by This Announcement

End-of-Sale Product Part Number	Product Description	Replacement Product Part Number	Replacement Product Description	Additional Information
WS-C3560E-12SD-E	Catalyst 3560E 12 SFP+2*10GE(X2), IPS s/w	WS-C3750X-12S-E	Catalyst 3750X 12 Port GE SFP IP Services	-
WS-C3560E-12SD-E=	Catalyst 3560E 12SD Spare Chassis, IPS s/w, No Power Supplies	WS-C3750X-12S-E	Catalyst 3750X 12 Port GE SFP IP Services	-
WS-C3560E-12SD-S	Catalyst 3560E 12 SFP+2*10GE(X2), IPB s/w	WS-C3750X-12S-S	Catalyst 3750X 12 Port GE SFP IP Base	-
WS-C3560E-12SD-S=	Catalyst 3560E 12SD Spare Chassis, IPB s/w, No Power Supplies	WS-C3750X-12S-S	Catalyst 3750X 12 Port GE SFP IP Base	-
WS-C3560E-24PD-E	Catalyst 3560E 24 10/100/1000 PoE+2*10GE(X2), 750W, IPS s/w	WS-C3560X-24P-E	Catalyst 3560X 24 Port PoE IP Services	-
WS-C3560E-24PD-S	Catalyst 3560E 24 10/100/1000 PoE+2*10GE(X2), 750W, IPB s/w	WS-C3560X-24P-S	Catalyst 3560X 24 Port PoE IP Base	-
WS-C3560E-24TD-E	Catalyst 3560E 24 10/100/1000+2*10GE(X2), 265W, IPS s/w	WS-C3560X-24T-E	Catalyst 3560X 24 Port Data IP Services	-
WS-C3560E-24TD-S	Catalyst 3560E 24 10/100/1000+2*10GE(X2), 265W, IPB s/w	WS-C3560X-24T-S	Catalyst 3560X 24 Port Data IP Base	-
WS-C3560E-24TD-SD	Catalyst 3560E 24 10/100/1000 + 2*10GE(X2), 265W DC, IPB s/w	WS-C3560X-24T-S	Catalyst 3560X 24 Port Data IP Base	-
WS-C3560E-48PD-E	Catalyst 3560E 48 10/100/1000 PoE+2*10GE(X2), 750W, IPS s/w	WS-C3560X-48P-E	Catalyst 3560X 48 Port PoE IP Services	-
WS-C3560E-48PD-EF	Catalyst 3560E 48 10/100/1000 PoE+2*10GE(X2), 1150W, IPS s/w	WS-C3560X-48PF-E	Catalyst 3560X 48 Port Full PoE IP Services	-
WS-C3560E-48PD-S	Catalyst 3560E 48 10/100/1000 PoE+2*10GE(X2), 750W, IPB s/w	WS-C3560X-48P-S	Catalyst 3560X 48 Port PoE IP Base	-
WS-C3560E-48PD-SF	Catalyst 3560E 48 10/100/1000 PoE+2*10GE(X2), 1150W, IPB s/w	WS-C3560X-48PF-S	Catalyst 3560X 48 Port Full PoE IP Base	-
WS-C3560E-48TD-E	Catalyst 3560E 48 10/100/1000+2*10GE(X2), 265W, IPS s/w	WS-C3560X-48T-E	Catalyst 3560X 48 Port Data IP Services	-
WS-C3560E-48TD-S	Catalyst 3560E 48 10/100/1000+2*10GE(X2), 265W, IPB s/w	WS-C3560X-48T-S	Catalyst 3560X 48 Port Data IP Base	-
WS-C3560E-48TD-SD	Catalyst 3560E 48 10/100/1000 + 2*10GE(X2), 265W DC, IPB s/w	WS-C3560X-48T-S	Catalyst 3560X 48 Port Data IP Base	-
WS-C3560G-24PS-E	Catalyst 3560 24 10/100/1000T PoE + 4 SFP + IPS Image	WS-C3560X-24P-E	Catalyst 3560X 24 Port PoE IP Services	-
WS-C3560G-24PS-S	Catalyst 3560 24 10/100/1000T PoE + 4 SFP + IPB Image	WS-C3560X-24P-S	Catalyst 3560X 24 Port PoE IP Base	-
WS-C3560G-24TS-E	Catalyst 3560 24 10/100/1000T + 4 SFP + IPS Image	WS-C3560X-24T-E	Catalyst 3560X 24 Port Data IP Services	-
WS-C3560G-24TS-S	Catalyst 3560 24 10/100/1000T + 4 SFP + IPB Image	WS-C3560X-24T-S	Catalyst 3560X 24 Port Data IP Base	-
WS-C3560G-48PS-E	Catalyst 3560 48 10/100/1000T PoE + 4 SFP + IPS Image	WS-C3560X-48P-E	Catalyst 3560X 48 Port PoE IP Services	-
WS-C3560G-48PS-S	Catalyst 3560 48 10/100/1000T PoE + 4 SFP + IPB Image	WS-C3560X-48P-S	Catalyst 3560X 48 Port PoE IP Base	-
WS-C3560G-48TS-E	Catalyst 3560 48 10/100/1000T + 4 SFP + IPS Image	WS-C3560X-48T-E	Catalyst 3560X 48 Port Data IP Services	-
WS-C3560G-48TS-S	Catalyst 3560 48 10/100/1000T + 4 SFP + IPB Image	WS-C3560X-48T-S	Catalyst 3560X 48 Port Data IP Base	-
WS-C3750E-24PD-E	Catalyst 3750E 24 10/100/1000 PoE+2*10GE(X2), 750W, IPS s/w	WS-C3560X-24P-E	Catalyst 3560X 24 Port PoE IP Services	-
WS-C3750E-24PD-S	Catalyst 3750E 24 10/100/1000 PoE+2*10GE(X2), 750W, IPB s/w	WS-C3750X-24P-S	Catalyst 3750X 24 Port PoE IP Base	-
WS-C3750E-24TD-E	Catalyst 3750E 24 10/100/1000+2*10GE(X2), 265W, IPS s/w	WS-C3750X-24T-E	Catalyst 3750X 24 Port Data IP Services	-
WS-C3750E-24TD-S	Catalyst 3750E 24 10/100/1000+2*10GE(X2), 265W, IPB s/w	WS-C3750X-24T-S	Catalyst 3750X 24 Port Data IP Base	-
WS-C3750E-24TD-SD	Catalyst 3750E 24 10/100/1000 + 2*10GE(X2), 265W DC, IPB s/w	WS-C3750X-24T-S	Catalyst 3750X 24 Port Data IP Base	-
WS-C3750E-48PD-E	Catalyst 3750E 48 10/100/1000 PoE+2*10GE(X2), 750W, IPS s/w	WS-C3750X-48P-E	Catalyst 3750X 48 Port PoE IP Services	-
WS-C3750E-48PD-EF	Catalyst 3750E 48 10/100/1000 PoE+2*10GE(X2), 1150W, IPS s/w	WS-C3750X-48PF-E	Catalyst 3750X 48 Port Full PoE IP Services	-
WS-C3750E-48PD-S	Catalyst 3750E 48 10/100/1000 PoE+2*10GE(X2), 750W, IPB s/w	WS-C3750X-48P-S	Catalyst 3750X 48 Port PoE IP Base	-
WS-C3750E-48PD-SF	Catalyst 3750E 48 10/100/1000 PoE+2*10GE(X2), 1150W, IPB s/w	WS-C3750X-48PF-S	Catalyst 3750X 48 Port Full PoE IP Base	-
WS-C3750E-48TD-E	Catalyst 3750E 48 10/100/1000+2*10GE(X2), 265W, IPS s/w	WS-C3750X-48T-E	Catalyst 3750X 48 Port Data IP Services	-
WS-C3750E-48TD-S	Catalyst 3750E 48 10/100/1000+2*10GE(X2), 265W, IPB s/w	WS-C3750X-48T-S	Catalyst 3750X 48 Port Data IP Base	-
WS-C3750E-48TD-SD	Catalyst 3750E 48 10/100/1000 + 2*10GE(X2), 265W DC, IPB s/w	WS-C3750X-48T-S	Catalyst 3750X 48 Port Data IP Base	-
WS-C3750G-12S-E	Catalyst 3750 12 SFP + IPS Image	WS-C3750X-12S-E	Catalyst 3750X 12 Port GE SFP IP Services	-
WS-C3750G-12S-S	Catalyst 3750 12 SFP + IPB Image	WS-C3750X-12S-S	Catalyst 3750X 12 Port GE SFP IP Base	-
WS-C3750G-12S-SD	Catalyst 3750 12 SFP DC powered + IPB Image	WS-C3750X-12S-S	Catalyst 3750X 12 Port GE SFP IP Base	-
WS-C3750G-24PS-E	Catalyst 3750 24 10/100/1000T PoE + 4 SFP + IPS Image	WS-C3750X-24P-E	Catalyst 3750X 24 Port PoE IP Services	-
WS-C3750G-24PS-S	Catalyst 3750 24 10/100/1000T PoE + 4 SFP + IPB Image	WS-C3750X-24P-S	Catalyst 3750X 24 Port PoE IP Base	-
WS-C3750G-24T-E	Catalyst 3750 24 10/100/1000T + IPS Image	WS-C3750X-24T-E	Catalyst 3750X 24 Port Data IP Services	-
WS-C3750G-24T-S	Catalyst 3750 24 10/100/1000T + IPB Image	WS-C3750X-24T-S	Catalyst 3750X 24 Port Data IP Base	-
WS-C3750G-24TS-E1U	Catalyst 3750 24 10/100/1000T + SFP 4 + IPB image 1RU	WS-C3750X-24T-E	Catalyst 3750X 24 Port Data IP Services	-
WS-C3750G-24TS-S1U	Catalyst 3750 24 10/100/1000T + SFP 4 + IPB image 1RU	WS-C3750X-24T-S	Catalyst 3750X 24 Port Data IP Base	-
WS-C3750G-48PS-E	Catalyst 3750 48 10/100/1000T PoE + 4 SFP + IPS Image	WS-C3750X-48P-E	Catalyst 3750X 48 Port PoE IP Services	-
WS-C3750G-48PS-S	Catalyst 3750 48 10/100/1000T PoE + 4 SFP + IPB Image	WS-C3750X-48P-S	Catalyst 3750X 48 Port PoE IP Base	-
WS-C3750G-48TS-E	Catalyst 3750 48 10/100/1000T + 4 SFP + IPS Image	WS-C3750X-48T-E	Catalyst 3750X 48 Port Data IP Services	-
WS-C3750G-48TS-S	Catalyst 3750 48 10/100/1000T + 4 SFP + IPB Image	WS-C3750X-48T-S	Catalyst 3750X 48 Port Data IP Base	-

*More information can be found on Cisco's announcement page.