Cisco NX-OS/IOS Configuration Fundamentals Comparison - Revision history

Kepacell at 17:48, 24 January 2011

2011-01-24T17:48:09Z

← Older revision		Revision as of 17:48, 24 January 2011
Line 173:		Line 173:
	!width="225" align="left" style="background:#99CCFF;" \|'''Cisco NX-OS'''		!width="225" align="left" style="background:#99CCFF;" \|'''Cisco NX-OS'''
	!width="225" align="left" style="background:#99CCFF;" \|'''Cisco IOS Software'''		!width="225" align="left" style="background:#99CCFF;" \|'''Cisco IOS Software'''
-	!width="~~450~~" align="left" style="background:#99CCFF;" \|'''Command Description'''	+	!width="475" align="left" style="background:#99CCFF;" \|'''Command Description'''
	\|-		\|-
	\|'''show running-config'''\|\| show running-config \|\| Displays the running configuration		\|'''show running-config'''\|\| show running-config \|\| Displays the running configuration

Kepacell at 21:52, 6 January 2011

2011-01-06T21:52:41Z

← Older revision		Revision as of 21:52, 6 January 2011
Line 41:		Line 41:
	* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.		* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.
	* The '''show tech''' command accepts several options that will display information for a specific feature.		* The '''show tech''' command accepts several options that will display information for a specific feature.
-	* The NX-OS has a configuration checkpoint/rollback feature that should be used when making changes to a production network.	+	* The NX-OS has a configuration checkpoint/rollback feature that should be used when making changes to a production network. A checkpoint configuration can be saved in EXEC mode with the global <b>checkpoint</b> command and the rollback procedure can be executed with the <b>rollback</b> command.

Kepacell at 01:58, 5 January 2011

2011-01-05T01:58:25Z

← Older revision		Revision as of 01:58, 5 January 2011
Line 17:		Line 17:
	* By default, the <b>admin</b> user has <b>network-admin</b> rights that allow full read/write access. Additional users can be created with very granular rights to permit or deny specific CLI commands.		* By default, the <b>admin</b> user has <b>network-admin</b> rights that allow full read/write access. Additional users can be created with very granular rights to permit or deny specific CLI commands.
	* The Cisco NX-OS has a Setup Utility that allows a user to specify the system defaults, perform basic configuration, and apply a pre-defined Control Plane Policing (CoPP) security policy.		* The Cisco NX-OS has a Setup Utility that allows a user to specify the system defaults, perform basic configuration, and apply a pre-defined Control Plane Policing (CoPP) security policy.
-	* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.	+	* The Cisco NX-OS uses a feature based license model. An Enterprise Services, Advanced Services, Transport Services, Scalable Feature and Enhanced Layer 2 license is required depending on the features required. Additional licenses may be required in the future.
-	* A 120 day license grace period is supported for testing, but features are automatically removed from the running configuration after the expiration date is reached.	+	* A 120 day license grace period is supported for testing, but features are automatically removed from the running configuration after the expiration date is reached. Some features such as Cisco Trustsec that require an Advanced Services license cannot be configured with a grace period.
	* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.		* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.
	* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.		* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.
-	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log ~~in for~~ the ~~first time You~~ are in the default VDC (VDC 1).	+	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log into the console port, you are in the default VDC (VDC 1).
-	* The Cisco NX-OS has two preconfigured VRF instances by default (management, default). The management VRF is applied to the supervisor module out-of-band Ethernet port (mgmt0), and the default VRF instance is applied to all other I/O module Ethernet ports.	+	* The Cisco NX-OS has two preconfigured VRF instances by default (management, default). The management VRF is applied to the supervisor module out-of-band Ethernet port (mgmt0), and the default VRF instance is applied to all other I/O module Ethernet ports. The mgmt0 port is the only port permitted in the management VRF instance and cannot be assigned to another VRF instance.
	* SSHv2 server/client functionality is enabled by default. TELNET server functionality is disabled by default. (The TELNET client is enabled by default and cannot be disabled.)		* SSHv2 server/client functionality is enabled by default. TELNET server functionality is disabled by default. (The TELNET client is enabled by default and cannot be disabled.)
-	* VTY and Auxiliary port configurations do not show up in the default configuration unless a parameter is modified (The Console port is included in the default configuration). The VTY port supports 32 simultaneous sessions and the timeout is disabled by default for all three port types.	+	* VTY and Auxiliary port configurations do not show up in the default configuration unless a parameter is modified (The Console port is included in the default configuration). The VTY port supports 32 simultaneous sessions and the timeout is disabled by default for all three port types
		+	* The Console and VTY ports always prompt the user for a username/password pair for authentication before granting access to the CLI. The Cisco IOS applies the <b>login</b> command to the Console and VTY ports by default to enable password authentication (If the <b>no login</b> command is applied, a user can gain access without a password.).
		+	* A user can execute <b>show</b> commands in configuration mode without using the <b>do</b> command as in Cisco IOS Software.
		+	* When executing a <b>show</b> command, a user has several more options when using the pipe (<b>\|</b>) option such as <b>grep</b> for parsing the output, <b>perl</b> for activating a script, and <b>xml</b> to format the output for network management applications.


Line 33:		Line 36:

	* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.		* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.
-	* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.	+	* The license grace-period can be disabled without any impact if the proper license is installed for a feature within the 120 day grace period.
		+	* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration. Some features such as LaCP and vPC will not allow you to disable the feature if they are configured.
	* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables. The boot variables determine what version of NX-OS is loaded when the system is powered on. (The kickstart and system boot variables have to be configured for the same NX-OS version.)		* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables. The boot variables determine what version of NX-OS is loaded when the system is powered on. (The kickstart and system boot variables have to be configured for the same NX-OS version.)
	* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.		* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.
	* The '''show tech''' command accepts several options that will display information for a specific feature.		* The '''show tech''' command accepts several options that will display information for a specific feature.
		+	* The NX-OS has a configuration checkpoint/rollback feature that should be used when making changes to a production network.


Line 130:		Line 135:
	!width="475" align="left" style="background:#ED9121;" \|<font color="white">'''Cisco IOS Software enables TELNET by default.'''		!width="475" align="left" style="background:#ED9121;" \|<font color="white">'''Cisco IOS Software enables TELNET by default.'''
	!width="475" align="left" style="background:#99CCFF;" \|'''feature telnet'''		!width="475" align="left" style="background:#99CCFF;" \|'''feature telnet'''
		+	\|-
		+	\|<font size = "3">'''Configuring the Console Timeout'''</font>
		+	\|-
		+	{\| border="0" cellpadding="2" cellspacing="6"
		+	!width="475" align="left" style="background:#ED9121;" \|<font color="white">'''line console 0
		+	exec-timeout 15 0
		+
		+	login'''
		+	!width="475" align="left" style="background:#99CCFF;" \|'''line console
		+	exec-timeout 15'''
	\|-		\|-
	\|<font size = "3">'''Configuring the VTY Timeout and Session Limit'''</font>		\|<font size = "3">'''Configuring the VTY Timeout and Session Limit'''</font>
Line 135:		Line 150:
	{\| border="0" cellpadding="2" cellspacing="6"		{\| border="0" cellpadding="2" cellspacing="6"
	!width="475" align="left" style="background:#ED9121;" \|<font color="white">'''line vty 0 9		!width="475" align="left" style="background:#ED9121;" \|<font color="white">'''line vty 0 9
		+	session-limit 10
		+
	exec-timeout 15 0		exec-timeout 15 0

Line 166:		Line 183:
	\|'''show interface'''\|\| show interface \|\| Displays the status for all of the interfaces		\|'''show interface'''\|\| show interface \|\| Displays the status for all of the interfaces
	\|-		\|-
-	\|'''show interface ethernet''' <x/x>''\|\| show interface <''int type''> \|\| Displays the status for a specific interface	+	\|'''show interface ethernet''' <i><x/x></i>''\|\| show interface <''<i>int type</i>''> \|\| Displays the status for a specific interface
		+	\|-
		+	\|'''show interface mgmt 0'''\|\| - \|\| Displays the status for the mgmt interface
	\|-		\|-
	\| <font color="white"> - \|\| <font color="white"> - \|\| <font color="white"> -		\| <font color="white"> - \|\| <font color="white"> - \|\| <font color="white"> -
Line 189:		Line 208:
	\|-		\|-
	\|'''show environment temperature'''\|\| show environment temperature \|\| Displays environment data		\|'''show environment temperature'''\|\| show environment temperature \|\| Displays environment data
		+	\|-
		+	\| <font color="white"> - \|\| <font color="white"> - \|\| <font color="white"> -
		+	\|-
		+	\|<b>show feature</b>\|\| - \|\| Displays the features and routing processes enabled
	\|-		\|-
	\| <font color="white"> - \|\| <font color="white"> - \|\| <font color="white"> -		\| <font color="white"> - \|\| <font color="white"> - \|\| <font color="white"> -

Kepacell at 15:48, 13 September 2010

2010-09-13T15:48:58Z

← Older revision		Revision as of 15:48, 13 September 2010
Line 21:		Line 21:
	* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.		* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.
	* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.		* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.
-	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log in for the first time You are in the default VDC(1).	+	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log in for the first time You are in the default VDC (VDC 1).
	* The Cisco NX-OS has two preconfigured VRF instances by default (management, default). The management VRF is applied to the supervisor module out-of-band Ethernet port (mgmt0), and the default VRF instance is applied to all other I/O module Ethernet ports.		* The Cisco NX-OS has two preconfigured VRF instances by default (management, default). The management VRF is applied to the supervisor module out-of-band Ethernet port (mgmt0), and the default VRF instance is applied to all other I/O module Ethernet ports.
	* SSHv2 server/client functionality is enabled by default. TELNET server functionality is disabled by default. (The TELNET client is enabled by default and cannot be disabled.)		* SSHv2 server/client functionality is enabled by default. TELNET server functionality is disabled by default. (The TELNET client is enabled by default and cannot be disabled.)

Kepacell at 15:47, 13 September 2010

2010-09-13T15:47:04Z

← Older revision		Revision as of 15:47, 13 September 2010
Line 21:		Line 21:
	* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.		* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.
	* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.		* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.
-	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log in for the first time You are in the default VDC.	+	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log in for the first time You are in the default VDC(1).
	* The Cisco NX-OS has two preconfigured VRF instances by default (management, default). The management VRF is applied to the supervisor module out-of-band Ethernet port (mgmt0), and the default VRF instance is applied to all other I/O module Ethernet ports.		* The Cisco NX-OS has two preconfigured VRF instances by default (management, default). The management VRF is applied to the supervisor module out-of-band Ethernet port (mgmt0), and the default VRF instance is applied to all other I/O module Ethernet ports.
	* SSHv2 server/client functionality is enabled by default. TELNET server functionality is disabled by default. (The TELNET client is enabled by default and cannot be disabled.)		* SSHv2 server/client functionality is enabled by default. TELNET server functionality is disabled by default. (The TELNET client is enabled by default and cannot be disabled.)

Kepacell at 15:45, 13 September 2010

2010-09-13T15:45:19Z

← Older revision		Revision as of 15:45, 13 September 2010
Line 34:		Line 34:
	* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.		* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.
	* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.		* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.
-	* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables. The boot variables determine what version of NX-OS is loaded ~~with~~ the system is powered on. (The kickstart and system boot variables have to be configured for the same NX-OS version.)	+	* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables. The boot variables determine what version of NX-OS is loaded when the system is powered on. (The kickstart and system boot variables have to be configured for the same NX-OS version.)
	* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.		* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.
	* The '''show tech''' command accepts several options that will display information for a specific feature.		* The '''show tech''' command accepts several options that will display information for a specific feature.

Kepacell at 15:44, 13 September 2010

2010-09-13T15:44:45Z

← Older revision		Revision as of 15:44, 13 September 2010
Line 34:		Line 34:
	* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.		* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.
	* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.		* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.
-	* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables.	+	* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables. The boot variables determine what version of NX-OS is loaded with the system is powered on. (The kickstart and system boot variables have to be configured for the same NX-OS version.)
	* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.		* The '''show running-config''' command accepts several options, such as OSPF, BGP, etc… that will display the runtime configuration for a specific feature.
	* The '''show tech''' command accepts several options that will display information for a specific feature.		* The '''show tech''' command accepts several options that will display information for a specific feature.

Kepacell at 15:39, 13 September 2010

2010-09-13T15:39:51Z

← Older revision		Revision as of 15:39, 13 September 2010
Line 15:		Line 15:
	* When you first log into the NX-OS, you go directly into EXEC mode.		* When you first log into the NX-OS, you go directly into EXEC mode.
	* Role Based Access Control (RBAC) determines a user’s permissions by default. NX-OS 5.0(2a) introduced privilege levels and two-stage authentication using an enable secret that can be enabled with the global <b>feature privilege</b> configuration command.		* Role Based Access Control (RBAC) determines a user’s permissions by default. NX-OS 5.0(2a) introduced privilege levels and two-stage authentication using an enable secret that can be enabled with the global <b>feature privilege</b> configuration command.
-	* By default, the admin user has network-admin rights that allow full read/write access. Additional users can be created with very granular rights to permit or deny specific CLI commands.	+	* By default, the <b>admin</b> user has <b>network-admin</b> rights that allow full read/write access. Additional users can be created with very granular rights to permit or deny specific CLI commands.
	* The Cisco NX-OS has a Setup Utility that allows a user to specify the system defaults, perform basic configuration, and apply a pre-defined Control Plane Policing (CoPP) security policy.		* The Cisco NX-OS has a Setup Utility that allows a user to specify the system defaults, perform basic configuration, and apply a pre-defined Control Plane Policing (CoPP) security policy.
	* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.		* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.

Kepacell at 15:38, 13 September 2010

2010-09-13T15:38:34Z

← Older revision		Revision as of 15:38, 13 September 2010
Line 19:		Line 19:
	* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.		* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.
	* A 120 day license grace period is supported for testing, but features are automatically removed from the running configuration after the expiration date is reached.		* A 120 day license grace period is supported for testing, but features are automatically removed from the running configuration after the expiration date is reached.
-	* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… ~~via~~ the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.	+	* The Cisco NX-OS has the ability to enable and disable features such as OSPF, BGP, etc… using the '''feature''' configuration command. Configuration and verification commands are not available until you enable the specific feature.
	* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.		* Interfaces are labeled in the configuration as '''Ethernet'''. There aren’t any speed designations.
	* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log in for the first time You are in the default VDC.		* The Cisco NX-OS supports Virtual Device Contexts (VDCs), which allow a physical device to be partitioned into logical devices. When you log in for the first time You are in the default VDC.

Kepacell at 15:37, 13 September 2010

2010-09-13T15:37:52Z

← Older revision		Revision as of 15:37, 13 September 2010
Line 15:		Line 15:
	* When you first log into the NX-OS, you go directly into EXEC mode.		* When you first log into the NX-OS, you go directly into EXEC mode.
	* Role Based Access Control (RBAC) determines a user’s permissions by default. NX-OS 5.0(2a) introduced privilege levels and two-stage authentication using an enable secret that can be enabled with the global <b>feature privilege</b> configuration command.		* Role Based Access Control (RBAC) determines a user’s permissions by default. NX-OS 5.0(2a) introduced privilege levels and two-stage authentication using an enable secret that can be enabled with the global <b>feature privilege</b> configuration command.
-	* By default, the ~~'''~~admin~~'''~~ user has ~~'''~~network-admin~~'''~~ rights that allow full read/write access.	+	* By default, the admin user has network-admin rights that allow full read/write access. Additional users can be created with very granular rights to permit or deny specific CLI commands.
	* The Cisco NX-OS has a Setup Utility that allows a user to specify the system defaults, perform basic configuration, and apply a pre-defined Control Plane Policing (CoPP) security policy.		* The Cisco NX-OS has a Setup Utility that allows a user to specify the system defaults, perform basic configuration, and apply a pre-defined Control Plane Policing (CoPP) security policy.
	* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.		* The Cisco NX-OS uses a feature based license model. An Enterprise or Advanced Services license is required depending on the features required. Additional licenses may be required in the future.
Line 32:		Line 32:


-	* The default administer user is predefined as admin. An admin user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.	+	* The default administer user is predefined as <b>admin</b>. An <b>admin</b> user password has to be specified when the system is powered up for the first time, or if the running configuration is erased with the <b>write erase</b> command and system is repowered.
	* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.		* If you remove a feature with the global <b>no feature</b> configuration command, all relevant commands related to that feature are removed from the running configuration.
	* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables.		* The NX-OS uses a kickstart image and a system image. Both images are identified in the configuration file as the kickstart and system boot variables.

← Older revision		Revision as of 17:48, 24 January 2011
Line 173:		Line 173:
	!width="225" align="left" style="background:#99CCFF;" \|'''Cisco NX-OS'''		!width="225" align="left" style="background:#99CCFF;" \|'''Cisco NX-OS'''
	!width="225" align="left" style="background:#99CCFF;" \|'''Cisco IOS Software'''		!width="225" align="left" style="background:#99CCFF;" \|'''Cisco IOS Software'''
-	!width="~~450~~" align="left" style="background:#99CCFF;" \|'''Command Description'''	+	!width="475" align="left" style="background:#99CCFF;" \|'''Command Description'''
	\|-		\|-
	\|'''show running-config'''\|\| show running-config \|\| Displays the running configuration		\|'''show running-config'''\|\| show running-config \|\| Displays the running configuration