Reference Guide

6 Thu Apr 20 19:47:16 UTC 2017 terminal length 0
7 Thu Apr 20 19:47:18 UTC 2017 terminal datadump
8 Thu Apr 20 19:47:20 UTC 2017 %abc
9 Thu Apr 20 19:47:22 UTC 2017 switchshow
10 Thu Apr 20 19:47:24 UTC 2017 cmsh
11 Thu Apr 20 19:47:26 UTC 2017 show version
12 Thu Apr 20 19:47:28 UTC 2017 cmsh
13 Thu Apr 20 19:47:30 UTC 2017 show version
14 Thu Apr 20 19:47:32 UTC 2017 show system
15 Fri Apr 21 12:35:31 UTC 2017 BIOS 3.20.0.3
• Enter clear command-history to clear the trace messages displayed in show command-history.
OS10# clear command-history
• Check the show command-history to verify that the trace messages are cleared.
• Enter show system from EXEC mode to view the system status information.
OS10#show system
Node Id : 1
MAC : 34:17:18:19:20:21
Number of MACs : 0
Up Time : 1 week 4 days 08:08:17
-- Unit 1 --
Status : up
System Identifier : 1
Down Reason :
System Location LED : off
Required Type : S4048
Current Type : S4048
Hardware Revision :
Software Version : 10.3.9999E(X)
Physical Ports : 48x10GbE, 6x40GbE
BIOS : 3.21.0.4
System CPLD : 15
Master CPLD : 12
Slave CPLD : 5
-- Power Supplies --
PSU-ID Status Type AirFlow Fan Speed(rpm) Status
----------------------------------------------------------------
1 fail
2 up AC REVERSE 1 14720 up
-- Fan Status --
FanTray Status AirFlow Fan Speed(rpm) Status
----------------------------------------------------------------
1 up REVERSE 1 13063 up
2 13063 up
2 up REVERSE 1 13020 up
2 12977 up
3 up NORMAL 1 13085 up
2 13063 up
Candidate conguration
When you enter OS10 conguration commands in the transaction-based conguration mode, changes do not take eect immediately and
are stored in the candidate conguration. The conguration changes become active on the network device only after you commit the
changes with the commit command. Changes in the candidate conguration are validated and applied to the running conguration.
The candidate conguration allows you to avoid introducing errors during an OS10 conguration session. You can make changes and then
check them before committing them to the active, running conguration on the network device.
Getting Started
33