Hybrid Versus Native
Anyone who configured a Catalyst switch during the last 10 years encountered the Catalyst OS interface and its series of set, clear, and show commands. Switches running Catalyst OS must rely upon a separate version of Cisco IOS to support any Layer 3 or router functions if a Router Switch Module (RSM) or Multilayer Switch Feature Card (MSFC) is installed. Therefore, the term hybrid became popular to describe a Catalyst switch running both Catalyst OS for Layer 2 functions, and Cisco IOS for Layer 3 functions. Although Catalyst switches account for more than 50% of the Cisco total sales volume each year, Cisco is known best as a company that makes high-speed routers. As a result, the look and feel of the traditional Cisco IOS interface became available for switches as an alternative to the hybrid look and feel. This alternative is dubbed native to indicate the look and feel of the original Cisco IOS applied to a switching platform. The next section of this chapter provides an overview of the look and feel of a Catalyst 6500 series switch running hybrid software, followed by a an overview of the look and feel of a Catalyst 6500 running native software.
The Look and Feel of Hybrid Software
As previously mentioned, the Catalyst OS relies primarily on a series of set, clear, and show commands for configuration. Chapter 6, "Understanding Multilayer Switching," and Chapter 8, "Understanding Quality of Service on Catalyst 6500," include detailed examples of configurations using the Catalyst OS. Only basic configurations sufficient to illustrate the general look and feel of each operating system are provided in this chapter. After a console connection is created into a switch running the Catalyst OS, issuing the help or ? command displays the available commands in user mode. Example 5-1 shows the top level of help available in user mode by issuing the ? command. Any of the commands displayed in Example 5-1 can be followed by a ? parameter to obtain detailed help on that command.
Example 5-1. Help in User Mode in Catalyst OS
Console> ?
cd Set default flash device
dir Show list of files on flash device
enable Enable privileged mode
help Show this help screen
history Show contents of history substitution buffer
l2trace Layer2 trace between hosts
ping Send echo packets to hosts
pwd Show default flash device
quit Exit from the Admin session
session Tunnel to ATM or Router module
set Set commands, use 'set help' for more info
show Show commands, use 'show help' for more info
traceroute Trace the route to a host
verify Verify checksum of file on flash device
wait Wait for x seconds
whichboot Which file booted
For example, a session ? command can be issued to obtain detailed help on the session command.
The help output in Example 5-1 indicates the show command is available from user mode, so the first thing to do is determine what type of switch is being used and which versions of software are running. This is accomplished with the show version command (see Example 5-2).
Example 5-2. Output of show version Command
Console> show version WARNING: This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. WS-C6513 Software, Version NmpSW: 8.1(3) Copyright (c) 1995-2003 by Cisco Systems NMP S/W compiled on Oct 10 2003, 13:09:37 System Bootstrap Version: 7.7(1) System Boot Image File is 'bootflash:cat6000-sup720k9.8-1-3.bin' System Configuration register is 0x10f Hardware Version: 1.0 Model: WS-C6513 Serial #: TSC073602JS PS1 Module: WS-CAC-2500W Serial #: ART0725E0RV Mod Port Model Serial # Versions --- ---- ------------------- ----------- -------------------------------------- 1 16 WS-X6516A-GBIC SAL0734K96L Hw : 1.0 Fw : 7.2(1) Sw : 8.1(3) 7 2 WS-SUP720-BASE SAD0734007W Hw : 2.3 Fw : 7.7(1) Fw1: 8.1(3) Sw : 8.1(3) Sw1: 8.1(3) 15 1 WS-SUP720 SAD073305H8 Hw : 1.5 Fw : 12.2(17a)SX1 Sw : 12.2(17a)SX1 DRAM FLASH NVRAM Module Total Used Free Total Used Free Total Used Free ------ ------- ------- ------- ------- ------- ------- ----- ----- ----- 7 524288K 360393K 163895K 65536K 14706K 50830K 2048K 249K 1799K Uptime is 0 day, 0 hour, 6 minutes
The show version output in Example 5-2 indicates the platform is a Catalyst 6513 with a Supervisor 720, running Catalyst OS version 8.1(3). The show version indicates there is a module 15, running IOS version 12.2(17a)SX1. Because this chassis only supports 13 physical modules, module 15 is a logical number representing the MSFC3 daughterboard on the Supervisor 720. If a second Supervisor 720 were installed, a module 16 would also be listed. This configuration represents a hybrid implementation using both Catalyst OS and IOS. The output of the show version command in Example 5-2 indicates there is an MSFC version 3 in module 15 on the switch. Modules 15 and 16 on the Catalyst 6500 series are "virtual" and are reserved for the MSFC. Module 15 is used by the MSFC integrated into the first Supervisor, while module 16 is used by the MSFC integrated into a second Supervisor, if installed.
With Catalyst OS, Ethernet connections are called ports and are Layer 2-only connections. A list of available ports can be obtained using the show port command. The show port command has a number of optional parameters, including the capability to specify an entire module or a specific port on a module. (See Example 5-3.)
Example 5-3. Output of show port 1/1 Command
Console> show port 1/1
* = Configured MAC Address
Port Name Status Vlan Duplex Speed Type
----- -------------------- ---------- ---------- ------ ----- ------------
1/1 disable 1 full 1000 No Connector
Port Security Violation Shutdown-Time Age-Time Max-Addr Trap IfIndex
----- -------- --------- ------------- -------- -------- -------- -------
1/1 disabled shutdown 0 0 1 disabled 12
Port Num-Addr Secure-Src-Addr Age-Left Last-Src-Addr Shutdown/Time-Left
----- -------- ----------------- -------- ----------------- ------------------
1/1 0 - - - - -
Port Flooding on Address Limit
----- -------------------------
1/1 Enabled
Port Broadcast-Limit Multicast Unicast Total-Drop Action
-------- --------------- --------- ------- -------------------- ------------
1/1 - - - 0 drop-packets
Port Send FlowControl Receive FlowControl RxPause TxPause
admin oper admin oper
----- -------- -------- --------- --------- ---------- ----------
1/1 desired off off off 0 0
Port Status Channel Admin Ch
Mode Group Id
----- ---------- -------------------- ----- -----
1/1 disable auto silent 3 0
Port Status ErrDisable Reason Port ErrDisableTimeout Action on Timeout
---- ---------- ------------------- ---------------------- -----------------
1/1 disable - Enable No Change
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize
----- ---------- ---------- ---------- ---------- ---------
1/1 0 0 0 0 0
Port Single-Col Multi-Coll Late-Coll Excess-Col Carri-Sen Runts Giants
----- ---------- ---------- ---------- ---------- --------- --------- ---------
1/1 0 0 0 0 0 0 0
Port Last-Time-Cleared
----- --------------------------
1/1 Sun Oct 30 2003, 22:33:34
Idle Detection
----------------
Because all ports in Catalyst OS are Layer 2 only, an Internet Protocol (IP) address cannot be assigned directly to this port, and no IP or other Layer 3 protocol information is displayed in the show port 1/1 output.
The Catalyst OS relies on set and clear commands to change parameters. In contrast, the Cisco IOS relies on only the command word to enable a command, and the no parameter to disable the command. Just like with Cisco IOS, Catalyst OS requires the user be in enable mode to make any changes to the switch configuration. By default, no console or enable password are set. The user enters enable mode by issuing the enable command at the console prompt, and pressing enable because no password has yet been established (see Example 5-4).
Example 5-4. Entering Enable Mode
Console> enable
Enter password:
Console> (enable)
Because a blank enable password is not a best practice, a set enablepass command is issued, allowing the password to be changed (see Example 5-5). This is in contrast to the enable password or enable secret commands that would be issued in Cisco IOS.
Example 5-5. Setting the Enable Password
Console> (enable) set enablepass
Enter old password:
Enter new password:
Retype new password:
Password changed.
Console> (enable)
After the password is changed, a console password can be established by issuing the set password command (see Example 5-6). Cisco IOS, on the other hand, uses the line con 0 command to access the console configuration, and a simple password command to change the password.
Example 5-6. Setting the Console Password
Console> (enable) set password
Enter old password:
Enter new password:
Retype new password:
Password changed.
Console> (enable)
The set system name command updates the system with a new device name (see Example 5-7).
Example 5-7. Setting the System Name
Console> (enable) set system name SW1 System name set. SW1> (enable)
Unlike Cisco IOS, Catalyst OS supports a command called show system, which provides general system information ranging from the specified location of the device, to the status of the power supplies (see Example 5-8).
Example 5-8. Output of show system Command
SW1> (enable) show system PS1-Status PS2-Status ---------- ---------- ok none Fan-Status Temp-Alarm Sys-Status Uptime d,h:m:s Logout ---------- ---------- ---------- -------------- --------- ok off ok 0,02:21:41 20 min PS1-Type PS2-Type -------------------- -------------------- WS-CAC-2500W none Modem Baud Backplane-Traffic Peak Peak-Time ------- ----- ----------------- ---- ------------------------- disable 9600 0% 0% Sun Nov 30 2003, 22:33:50 PS1 Capacity: 2331.00 Watts (55.50 Amps @42V) System Name System Location System Contact CC ------------------------ ------------------------ ------------------------ --- SW1 Cisco Lab David Barnes Fab Chan Speed Input Output -------- ----- ----- ------ 0 8G 0% 0% 1 n/a 0% 0% 2 n/a 0% 0% 3 n/a 0% 0% 4 20G 0% 0% 5 n/a 0% 0% 6 n/a 0% 0% 7 n/a 0% 0% 8 n/a 0% 0% 9 n/a 0% 0% 10 n/a 0% 0% 11 n/a 0% 0% 12 n/a 0% 0% 13 n/a 0% 0% 14 n/a 0% 0% 15 n/a 0% 0% 16 n/a 0% 0% 17 n/a 0% 0% Core Dump Core File ------------------------ ----------------------- disabled disk0:crashinfo System Logging Host File Interval -------------- --------------- ----------------------------------- -------- Disabled - tftp:sysinfo 1440 Index System Command ----- ---------------------------------------------------------- Syslog Dump Syslog File ------------------------ ----------------------- disabled disk0:sysloginfo SW1> (enable)
Example 5-8 indicates the switch resides in the Cisco Lab, a single 2500 watt power supply is installed, and the 16-port Gigabit Ethernet card installed in slot 1 has only a single 8-Gbps connection into the Switch Fabric. To obtain similar information from Cisco IOS, a combination of show environment and show controller commands would be required.
Another difference between Catalyst OS and IOS command-line interfaces is in the way the configuration of a device is displayed. Anyone familiar with Cisco IOS has used the show running-config command to display the running configuration of a router. Routers utilize both a saved configuration and a running configuration. Changes made to a router's configuration are not committed to memory until a copy or write memory command is issued. Catalyst OS uses the show config command to display the configuration of a switch, and no concept of a saved configuration and a separate running configuration exists. Any changes entered at the command line in Catalyst OS are automatically saved. With the introduction of Catalyst OS version 6.3(1) and later, a show running-config command was introduced. Example 5-9 shows the optional parameters for the show running-config command in Catalyst OS.
Example 5-9. show running-config Options for Catalyst OS
SW1 (enable) show running-config ?
all Show default and non-default runtime config
qos Show QoS configuration
system Show system configuration
<mod> Module number
In contrast to Cisco IOS, the show running-config command in Catalyst OS only displays commands that have changed from their default values. The addition of the all optional parameter displays all configuration commands including the defaults.
The output from the show tech-support command is typically the first thing requested by the Cisco Technical Assistance Center when beginning troubleshooting. The show tech-support command, long available in Cisco IOS, was finally introduced in Catalyst OS 5.3(1). For versions prior to Catalyst OS 5.3(1), a combination of various show commands is required to gather the same information. Example 5-10 shows the optional parameters for the show tech-support command in Catalyst OS.
Example 5-10. show tech-support Options for Catalyst OS
SW1 (enable) show tech-support ?
config Show Tech-Support information using config option
memory Show Tech-Support information using memory option
mistp-instance Show MISTP information for Tech-support
mst Show MST information for Tech-support
module Show module information for Tech-Support
port Show port information for Tech-Support
vlan Show vlan information for Tech-Support
When setting up a Catalyst switch in hybrid mode, Layer 3 functionality is provided by a Router Switch Module (RSM), Router Switch Feature Card (RSFC), or some version of Multilayer Switch Feature Card (MSFC). These Layer 3 devices cannot be configured from the Catalyst OS command line. Configuration of these modules requires accessing the device directly by using the session command.
Connecting to the command-line interface of the MSFC3 is as simple as issuing a session command from the Catalyst OS command line, as shown in Example 5-11.
Example 5-11. Connecting to the MSFC
SW1> (enable) session 15
Trying Router-15...
Connected to Router-15.
Escape character is '^]'.
SW1-MSFC3>
After a session is established to the MSFC3 on SW1, standard IOS commands can be issued to configure the router. Issuing an exit command returns the device back to the Catalyst OS command-line interface.
In hybrid mode, the individual Ethernet ports configurable from the Catalyst OS cannot be viewed or modified by the MSFC. Layer 3 routing is accomplished by creating VLAN interfaces on the MSFC that correspond to the VLANs created in the Catalyst OS. In Example 5-12, all the ports on module 1 are set to VLAN 10 using the set vlan command.
Example 5-12. Configuring Port VLAN Membership on Module 1
SW1> (enable) set vlan 10 1/1-1/16
VLAN Mod/Ports
---- -----------------------
10 1/1-16
At this point, all ports on module 1 are members of VLAN 10, but no Layer 3 routing functionality is set up on the MSFC. After accessing the MSFC by again issuing the session 15 command, a Layer 3 VLAN interface can be configured using the interface VLAN 10 command. To issue the interface command, the user must first be in enable and config terminal modes. Example 5-13 shows VLAN 10 being configured on the MSFC3 in SW1.
Example 5-13. Configuring VLAN 10 on the MSFC3
SW1-MSFC3>enable Password: SW1-MSFC3#config t Enter configuration commands, one per line. End with CNTL/Z. SW1-MSFC3(config)#interface vlan10 SW1-MSFC3(config-if)#end SW1-MSFC3#
After the VLAN 10 interface is configured, it can be viewed by issuing a show interface command, as in Example 5-14.
Example 5-14. Output of show interface on VLAN 10
SW1-MSFC3#show interface vlan10
Vlan10 is administratively down, line protocol is down
Hardware is Cat6k RP Virtual Ethernet, address is 000d.662c.64fc (bia 000d.662
c.64fc)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 packets output, 0 bytes, 0 underruns
0 output errors, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
By default, the interface is administratively down and no Layer 3 address is assigned. In Example 5-15, an IP address is assigned and the interface is enabled.
Example 5-15. Assigning an IP Address to VLAN 10
SW1-MSFC3#config terminal Enter configuration commands, one per line. End with CNTL/Z. SW1-MSFC3(config)#interface vlan10 SW1-MSFC3(config-if)#ip address 10.10.10.1 255.255.255.0 SW1-MSFC3(config-if)#no shut
After the IP address is configured and the interface is enabled, the switch will recognize that ports 1/1 through 1/16 are assigned to VLAN 10 via the Catalyst OS interface and VLAN 10 will come up. (See Example 5-16.)
Example 5-16. show interface Output for VLAN 10
SW1-MSFC3#show interface vlan10
Vlan10 is up, line protocol is up
Hardware is Cat6k RP Virtual Ethernet, address is 000d.662c.64fc (bia 000d.662 c.64fc)
Internet address is 10.10.10.1/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 packets output, 0 bytes, 0 underruns
0 output errors, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
At this point, the VLAN 10 interface is processing traffic for any device connected to a port assigned to VLAN 10. Catalyst switches in a hybrid setup require at least one Layer 2 port to be assigned to the same VLAN as the Layer 3 VLAN interface before it can be enabled.
The Look and Feel of Native
With the introduction of Cisco IOS 12.0(7)XE, the familiar command-line interface look and feel from the Cisco popular line of routers became available for the Catalyst 6500 platform. As previously mentioned, this IOS for switches is commonly referred to as native IOS. One of the most noticeable differences in the look and feel between Catalyst OS and native IOS running on a switch is the way connections are treated. With Catalyst OS, Ethernet connections are called ports, and with native IOS, those same connections are called interfaces. Example 5-3, earlier in the chapter, displayed the output of a show port command for port 1/1. Example 5-17 shows the output from the show interface command for the same Gigabit Ethernet connection running native IOS 12.1(13)E9.
Example 5-17. show interface gigabitethernet 1/1 Command Output
SW1#show interface gigabitethernet 1/1
GigabitEthernet1/1 is administratively down, line protocol is down (disabled)
Hardware is C6k 1000Mb 802.3, address is 0001.c9db.8814 (bia 0001.c9db.8814)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Full-duplex mode, link type is autonegotiation, media type is SX
output flow-control is unsupported, input flow-control is unsupported, 1000Mb/s
Clock mode is auto
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Most of the information displayed using both the show port command in the Catalyst OS and show interface in native IOS is the same, with only a few exceptions; the primary difference is in the formatting of the output.
Unlike the hybrid configuration, only a single interface exists for configuring connections, and each Ethernet connection can be configured as a switched port (Layer 2) or a routed interface (Layer 3). By default, each connection defaults to being a Layer 3 routed interface and is shut down. Configuring the interface for Layer 3 routing is as simple as assigning an IP address and enabling the interface. (See Example 5-18.)
Example 5-18. Configuring IP on a Gigabit Interface
SW1#config terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)#interface gigabitethernet 1/1 SW1(config-if)#ip address 10.10.10.1 255.255.255.0 SW1(config-if)#no shutdown SW1(config-if)#end SW1#
Now that the interface is configured with an IP address, a quick check of the interface can be accomplished with the show interface gigabitethernet 1/1 command, as demonstrated in Example 5-19.
Example 5-19. Output of show interface gigabitethernet 1/1 Command
SW1#show interface gigabitethernet 1/1
GigabitEthernet1/1 is up, line protocol is up
Hardware is C6k 1000Mb 802.3, address is 000b.fc38.540a (bia 000b.fc38.540a)
Internet address is 10.10.10.1/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex mode, link type is autonegotiation, media type is SX
output flow-control is unsupported, input flow-control is unsupported, 1000Mb/s
Clock mode is auto
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:02:14, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
L2 Switched: ucast: 3 pkt, 1230 bytes - mcast: 0 pkt, 0 bytes
L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 0 pkt, 0 bytes
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Example 5-20 shows the configuration of GigabitEthernet interface 1/1.
Example 5-20. GigabitEthernet 1/1 Running Configuration
SW1#show run interface gigabitethernet 1/1
Building configuration...
Current configuration : 87 bytes
!
interface GigabitEthernet1/1
ip address 10.10.10.1 255.255.255.0
end
The same Gigabit Ethernet interface can be configured as a switched port with a few simple configuration commands. First, a VLAN is created to contain the switch port. In Example 5-21, as in the Catalyst OS configuration, VLAN 10 is used.
Example 5-21. Creating VLAN 10 in Native Mode
SW1#config terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)#vlan 10 SW1(config-vlan)#end SW1#
Issuing a switchport command puts the interface into a Layer 2-only mode. This command must be issued before any additional switchport commands can be issued. The switchport mode access command configures the port as an access port and prevents the port from becoming a trunk. The switchport access command allows the assignment of a VLAN. In this case, VLAN 10 is assigned to GigabitEthernet 1/1. (See Example 5-22.) Issuing a no switchport command on the interface removes all Layer 2 configuration and returns the interface to a Layer 3 configuration.
Example 5-22. Configuring a Layer 2 Switch Port
SW1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)#interface gigabitethernet 1/1 SW1(config-if)#switchport SW1(Config-if)#switchport mode access SW1(config-if)#switchport access vlan 10 SW1(Config-if)#no shutdown SW1(config-if)#end SW1#
When using native to configure multiple connections as switch ports, Layer 3 routing of those switch ports is accomplished using VLAN interfaces in the same way as with hybrid.
A comparison between the look and feel of hybrid and native is illustrated by contrasting the configuration of VLAN Trunking Protocol (VTP) in both environments in Table 5-1.
Catalyst OS | Cisco IOS Software |
|---|---|
SW1# set vtp domain Cisco SW1#set vtp mode server SW1#set vlan 10 name Lab SW1#set vlan 10 1/1 ? 16 | SW1#configure terminal SW1(config)#vtp mode server SW1(config)#vtp domain Cisco SW1(config)#vlan 10 SW1(config-vlan)#name Lab SW1(config)#interface range fastethernet 1/1 ? 16 SW1(config-if-range)#switchport SW1(config-if-range)#switchport mode access SW1(config-if-range)#switchport access vlan 10 |
Table 5-2 shows a list of commonly used commands and their syntax in both Catalyst OS and Cisco IOS for Catalyst switches.
Catalyst OS | Cisco IOS Software |
|---|---|
reset system | reload |
session | remote-login |
set system name | hostname |
set test diaglevel | diagnostic level |
set boot config-register | config-register |
set boot system flash | boot system flash |
set module power down/up | power enable module |
set port disable | shutdown (interface mode) |
set port duplex | duplex |
set port flowcontrol send [desired | off |on] | flowcontrol send [desired | off | on] |
set port flowcontrol receive [desired | off |on] | flowcontrol receive [desired | off | on] |
set port negotiation <mod/port> enable/disable | speed nonegotiate |
set port speed | speed |
set cam | mac-address-table |
set port jumbo | mtu 921 |
set port channel | channel-group <group> mode (interface mode) |
set trunk (default mode is auto) | switchport mode trunk (VLAN database command) |
set udld | udld |
set vlan <vlan id> port | switchport switchport mode access switchport access vlan <> |
set vtp | vtp |
set spantree backbonefast | spanning-tree backbonefast |
set spantree enable/disable | spanning-tree vlan |
set spantree portfast | spanning-tree portfast |
set qos enable | mls qos |
set port dot1qtunnel | switchport mode dot1qtunnel |
show cam dynamic | show mac-address-table dynamic |
show channel info or show port channel | show etherchannel summary |
show mac | show interface counters |
show port <slot/port> | show interface <type slot/port> |
show mls cef | show mls cef |
show port | show interface status |
show port capabilities | show interface capabilities |
show span | show monitor |
show spantree | show spanning-tree |
show qos | show mls qos |
show trace | show debugging |
show trunk or show port trunk | show interfaces trunk |
show udld | show udld |
show vlan | show vlan |
show vtp domain | show vtp status |
clear cam | clear mac-address-table |
Choosing Between Hybrid and Native
A very common question posed to Cisco is "Should I run in a hybrid or native configuration?" The answer is, "it depends." Although there is no wrong answer, the choice should be influenced by a number of considerations. Are personnel responsible for configuring and maintaining the switch more familiar with one interface or another? If personnel are already familiar with configuring Cisco routers, but not switches using Catalyst OS, native might be a better choice. As of the writing of this text, some differences in feature support exist between hybrid and native, with more software features typically available in hybrid. On the other hand, some of the newest Cisco modules for platforms such as the Catalyst 6500 and some of the newest Cisco switches such as the 4500 series run only on native.
The Cisco official position on hybrid versus native is that eventually feature parity will exist between both types of software, and that even switches without Layer 3 routing capabilities, such as a Catalyst 6500 without an MSFC, will be able to run native. Although native appears to be becoming more popular because of the capability to have one look and feel of interface to learn and support, Cisco is committed to developing and supporting Catalyst OS for many, many years to come. As a result, many companies have both hybrid and native switches in their networks, and a choice between the types of software comes down to current hardware and/or feature support. As of this writing Table 5-3 compares the feature support between Catalyst OS and native IOS on the Cisco flagship switching platform, the Catalyst 6500.
Software Feature | Catalyst OS | Cisco IOS |
|---|---|---|
VLAN ranges: up to 4096 VLAN SVIs (Layer 3 VLAN interfaces) | x | x |
Inter-VLAN routing | x | x |
4096 Layer 2 VLANs | x | x |
Private VLANs | x | x |
Dynamic VLANs | x | |
Trunking: IEEE 802.1q, ISL | x | x |
DTP, VTP | x | x |
VTPv3 | x | |
IEEE 802.1q tunneling | x | x |
Layer 2 Protocol tunneling | x | x |
Spanning Tree: PortFast, UplinkFast, BackboneFast, BPDU Guard, PRRST+, PVRST | x | x |
IEEE 802.1s and 802.1w | x | |
Jumbo frames | x | x |
EtherChannel, Port Aggregation Protocol (PAgP) | x | x |
EtherChannel, IEEE 802.3ad (LACP) | x | x |
Local and Remote Span (RSPAN) | x | x |
Multicast Services: PIM, IGMP snooping, RGMP | x | x |
QoS Marking, Policing, Scheduling | x | x |
QoS ACLs | x | x |
Routing ACLs | x | x |
VLAN ACLs | x | x |
Cisco IOS Server Load Balancing | x | |
Broadcast suppression | x | x |
Protocol filtering, Cisco IOS support on Supervisor Engine 1A systems only | x | x |
Port security | x | x |
IEEE 802.1X | x | x |
Time Domain Reflectometer (TDR) | x | x |
AutoQoS | x | |
ARP Inspection | x | |
Network-Based Application Recognition (NBAR) | x | x |
User-Based Rate Limiting | x | |
Cisco Discovery Protocol | x | x |
NetFlow Data Export (NDE) | x | x |
Unidirectional Link Detection (UDLD) | x | x |
Voice VLAN ID (VVID) and inline power for Cisco IP Phones | x | x |
Supervisor redundancy and failover | x | x |
Stateful Supervisor Switchover | x | |
Multiprotocol Label Switching (MPLS), EoMPLS, MPLS VPN | x | |
Distributed Cisco Express Forwarding (dCEF) | x |
Refer to Cisco.com for a current list of hardware and feature support in Catalyst OS and Cisco IOS for Catalyst switches.
