29.04.2019 Views

OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuration Files Overview<br />

Working With Configuration Files<br />

Configuration Files Overview<br />

Instead of using CLI commands entered at a workstation, you can configure the switch using an ASCIIbased<br />

text file. You may type CLI commands directly into a text document to create a configuration file<br />

that will reside in your switch’s /flash directory. Configuration files are created in the following ways:<br />

• You may create, edit, and view a file using a standard text editor (such as MS WordPad or Notepad) on<br />

a workstation. The file can then be uploaded to the switch’s /flash file directory.<br />

• You can invoke the switch’s CLI configuration snapshot command to capture the switch’s current<br />

configuration into a text file. This causes a configuration file to be created in the switch’s /flash directory.<br />

• You can use the switch’s text editor to create or edit a configuration file located in the switch’s /flash<br />

file directory.<br />

Applying Configuration Files to the <strong>Switch</strong><br />

Once you have a configuration file located in the switch’s file system you must load the file into running<br />

memory to make it run on the switch. You do this by using configuration apply command.<br />

You may apply configuration files to the switch immediately, or you can specify a timer session. In a timer<br />

session, you schedule a file to be applied in the future at a specific date and time or after a specific period<br />

of time has passed (like a countdown). Timer sessions are very useful for certain management tasks, especially<br />

synchronized batch updates.<br />

• For information on applying a file immediately, refer to “Setting a File for Immediate Application” on<br />

page 5-4.<br />

• For information on applying a file at a specified date and time, refer to “Setting an Application Session<br />

for a Date and Time” on page 5-4.<br />

• For information on applying a file after a specified period of time has elapsed, refer to “Setting an<br />

Application Session for a Specified Time Period” on page 5-5.<br />

Verifying a Timed Session<br />

To verify that a timed session is running, use the show configuration status command. The following<br />

displays where the timed session was set using the configuration apply qos_pol at 11:30 october 31<br />

syntax.<br />

-> show configuration status<br />

File configuration : scheduled at 11:30 october 31<br />

Note. Only one session at a time can be scheduled on the switch. If two sessions are set, the last one will<br />

overwrite the first. Before you schedule a timed session you should use the show configuration status<br />

command to see if another session is already running.<br />

The following displays where the timed session was set on March 10, 2002 at 01:00 using the<br />

configuration apply group_config in 6:10 syntax.<br />

-> show configuration status<br />

File configuration : scheduled at 03/10/02 07:10<br />

page 5-6 Omni<strong>Switch</strong> <strong>AOS</strong> Release 8 <strong>Switch</strong> <strong>Management</strong> <strong>Guide</strong> May 2014

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!