Getting Started With Alliedware Plus: Feature Overview and Configuration Guide
Getting Started With Alliedware Plus: Feature Overview and Configuration Guide
Introduction
This guide introduces a number of commonly-used management features of the AlliedWare PlusTM
Operating System (OS).
However, feature support and implementation varies between products. For more information, see
the following documents:
These documents are available from the above links on our website at alliedtelesis.com.
Most of this guide applies for versions 5.4.4 onwards, but automatic IP address assignment on
start-up applies from version 5.4.7-0.4 onwards.
Contents
Introduction .........................................................................................................................................1
Products and software version that apply to this guide ...............................................................1
Passwords.........................................................................................................................................25
How to Change the Password ....................................................................................................25
How to set strong passwords .....................................................................................................26
How to add and remove users....................................................................................................27
Pre-encrypted passwords...........................................................................................................29
Viewing voltage, fan status, power supply, alarm status, and temperature ...............................31
Viewing the serial number...........................................................................................................31
How to Easily Locate the Device in a Server Room (Find Me) ..........................................................48
Start-up Process
From software version 5.4.7-0.4 onwards, unconfigured devices automatically receive a
management IP address on start-up. When your device is started without any configuration, IPv4
and IPv6 addresses are automatically applied to the Ethernet-based management interface.
Your device must be factory new or unconfigured for automatic address assignment to occur.
This means you can use SSH to manage your device remotely instead of locally.
Unconfigured (factory-new)
If your device is factory new it is considered unconfigured because none of the following
configuration files exist in the root directory of external media:
.config
.config_backup
.cfg files
Configured
Otherwise your device is considered configured. Your device may have an existing configuration
or it could have been pre-configured (for example, Firewalls are pre-configured). You can use the
command erase factory-default if you want to manually return it to an unconfigured state, so
that automatic address assignment can occur.
For more information about erasing the factory default, see How to Return to the Factory
Defaults.
Management interfaces
The management interface depends on the interface ports available on your device.
eth0 labelled NET MGMT vlan1 if there is no NET MGMT the first eth port to go link-up, for
example the AR2010V
If the management interface is vlan1, then your device waits until vlan1 has gone into a STP
forwarding state.
Loop Protection is enabled on devices that support it. Some devices (e.g. AR-Series Firewalls)
do not support Loop Protection, so will not include the loop-protection configuration.
DHCP and DHCPv6 clients are enabled and their processes started.
If your device obtains an address from DHCP or DHCPv6, then the IP address is assigned.
If your device does not obtain an IPv4 address via DHCP within 10 seconds, then it applies
the class B IPv4 link-local address 169.254.42.42/16. Then the IPv4 DHCP client is disabled.
You can manage your device by using SSH to connect to the IPv4 or IPv6 address that has been
assigned to the management interface. You will need to ensure your management computer is
configured with an IP/IPv6 address within the same subnet as the management IP address on
the device. The following commands are configured:
no service telnet
service ssh
ssh server allow-users manager
loop-protection loop-detect fast-block ldf-interval 1
interface <management-interface>
ip address dhcp
ipv6 address dhcp
or,
Note: For security reasons a password change is strongly recommended after the IP address is
assigned.
How to Login
You can choose one of the following options to login to your device:
Use the console to login to your device if you have cable access via the local Console Port.
Use SSH to login to your device via a Management Interface Port if you do not have access
via the Console Port, or if you want to manage your device remotely.
Use the firewall GUI if you want to manage your device using web access.
1. Connect the local management cable (with DB-9 connector) provided from your device to the
management computer.
From the PuTTY Configuration dialog enter the following basic options:
Enter the Serial line, for example COM3. To find the Serial line from Microsoft Windows,
go to Device Manager> Ports (COM @ LPT).
Change the Speed (console baud rate) if necessary, for example to 115200. The default
baud rate is 9600. See your product’s Installation Guide for the correct baud rate.
Caution On IE200 and IE300 Series switches, we do not recommend changing the baud rate. The
bootloader on these switches always runs at 9600 Baud. If you change the baud rate, you
will lose access to the bootloader.
By default the AlliedWare Plus OS supports VT100 compatible terminals on the console
port. This means that the terminal size is 80 columns by 24 rows.
Username: manager
Password: friend
Your device logs you into User Exec mode. From User Exec mode, you can perform high-
level diagnostics (some show commands, ping, traceroute, for example), start sessions
(Telnet, SSH), and change mode.
2. The management computer must be connected to the same network as the device.
3. Connect your device into the network via the management interface.
4. Power up your device. If your device is factory new (unconfigured) and you want it to receive
an IP address automatically, wait approximately 30 seconds after the management port has
gone link-up for this to happen. For details see Automatic IP address assignment.
From the PuTTY Configuration dialog enter the following basic options:
Select the SSH button and enter the Host Name (or IP address), for example
10.33.22.33.
Click Yes if you receive the following PuTTY Security Alert Warning message:
This message can be bypassed because it is referring to the host key not matching the
cache.
The GUI also supports a DHCP server, interface management, VLAN management, file
management, system tools, a CLI window and a dashboard for network monitoring. The
dashboard shows interface and firewall traffic, system and environmental information, and the
security monitoring widget lets you view and manage rules and security features. The complete
AlliedWare Plus feature-set can be configured using the firewalls built-in industry standard
Command Line Interface (CLI). The firewall and its graphical management and monitoring
functionality will increase with subsequent releases.
If your firewall is new and unused, it will already have the GUI installed from the factory, and the
IP address 192.168.1.1 on vlan1, and 172.16.0.1/24 on eth1, and 128.0.0.1/24 on eth2 and the
HTTP service enabled. Connect to any switch port and browse to 192.168.1.1 to begin.
Multiple users can Telnet/SSH and issue commands using the User Exec mode and the
Privileged Exec mode. However, only one user is allowed to use the Configure mode at a time.
This prevents multiple users from issuing configuration commands simultaneously.
User
Command mode
Exec mode
Privileged
Exec mode
configure terminal
Global
Configuration
mode
interface
[interface name]
Interface Other
mode sub-modes
User Exec User Exec mode is the mode you log into on the device. It lets you perform high-level diagnostics
mode (show commands, ping, traceroute, for example), start sessions (Telnet, SSH), and change
mode.
Privileged Privileged Exec mode is the main mode for monitoring—for example, running show commands
Exec mode and debugging. From Privileged Exec mode, you can do all the commands from User Exec mode
plus many system commands.
To change from User Exec to Privileged Exec mode, enter the command:
awplus> enable
Global From Global Configuration mode, you can configure most aspects of the device.
Configuration
mode
To change from Privileged Exec to Global Configuration mode, enter the command:
Interface From Interface Configuration mode, you can configure the settings of one or more specified
Configuration interfaces.
mode
To change from Global Configuration mode to Interface Configuration mode, enter the command:
Router From Router Configuration mode, you can configure routing using BGP, IP, IPv6, OSPF, RIP, or
Configuration VRRP.
mode
To change from Global Configuration mode to Router Configuration mode, enter the command:
VLAN From VLAN Database mode, you can create and configure VLANs.
Database
mode
To change from Global Configuration mode to VLAN Database mode, enter the command:
The following tables lists some (but not all) examples of the lower-level modes:
Class map QoS classes, which isolate and name specific traffic (first enable QoS globally awplus(config-cmap)#
flows (classes) from all other traffic. with mls qos enable)
class-map name
Ping poll Ping polling, which checks whether specified ping-poll number awplus(config-ping-poll)#
devices are reachable or not.
Policy map QoS policies, a collection of user-defined QoS (first enable QoS globally awplus(config-pmap)#
classes and the default class. with mls qos enable)
policy-map name
Policy map class The QoS actions to take on a class-map, and which (in Policy map mode) awplus(config-pmap-c)#
class-maps to associate with a QoS policy. class name
This mode is a sub-mode of Policy map mode.
Route map Route maps, which select routes to include or route-map name awplus(config-route-map)#
exclude from the device’s routing table and/or route deny|permit entry-number
advertisements.
Trigger Triggers, which run configuration scripts in response trigger number awplus(config-trigger)#
to events.
Some protocols have commands in both Global Configuration mode and lower-level
configuration modes. For example, to configure MSTP, you use:
Interface Configuration mode to associate the instances with the appropriate ports.
User
Command mode
Exec mode
Privileged
Exec mode
end
or Ctrl+Z
or Ctrl+C exit
Global
Configuration
mode
exit
Sub-modes
awplus(config-if)# exit
awplus(config)#
awplus(config-if)# end
awplus#
awplus# exit
awplus>
However, you can run Privileged Exec commands without changing mode, by using the
command:
You cannot use the ? help to find out command syntax when using the do command.
Example To display information about the IP interfaces when in Global Configuration mode, enter the
command:
Output 1: Example output after entering the command do show ip int brief
Command Abbreviations
The AlliedWare Plus CLI contains a number of abbreviations for its commands.
For example, the show interface command can be entered in the abbreviated form shown
below:
awplus# sh in vlan100
the prompt:
this will list all commands available in the mode you are in.
this will list parameters that can come next in the partial command.
Note: The AlliedWare Plus OS only displays one screenful of text at a time, with the prompt
“--More--” at the end of each screenful. Press the space bar to display the next screenful
or the Q key to return to the command prompt.
Example To see which commands are available in Privileged Exec mode, enter “?” at the Privileged Exec
mode command prompt:
awplus# ?
Exec commands:
activate Activate a script
cd Change the current working directory
clear Reset functions
clock Manage clock
configure Enter configuration mode
copy Copy from one file to another
...
Example To see which show commands that start with “i” are available in Privileged Exec mode, enter “?”
after show i:
awplus# show i?
Examples To use the ? help to work out the syntax for the clock timezone command, enter the following
sequence of commands:
awplus> enable
awplus# configure terminal
awplus(config)# clock ?
The above example demonstrates that the ? help only indicates what you can type next. For
commands that have a series of parameters, like clock timezone, the ? help does not make the
number of parameters obvious.
Completing keywords
To complete keywords, type the Tab key after part of the command.
If only one keyword matches the partial command, the AlliedWare Plus OS fills in that keyword. If
multiple keywords match, it lists them.
Examples In this example we use Tab completion in successive steps to build the complete command
show ip dhcp snooping. We have included “<Tab>” to show where to type the Tab key — this is
not displayed on screen.
awplus#show ip <Tab>
access-list dhcp dhcp-relay domain-list domain-name filter
forwarding igmp interface mroute name-server prefix-list
route rpf rrp sockets source traffic
awplus#show ip d<Tab>
dhcp dhcp-relay domain-list domain-name
Output 6: Example output after entering the show ip dhcp <Tab> command
Output 7: Example output after entering the show ip dhcp s<Tab> command
awplus# interface
% Incomplete command.
% Invalid input detected at '^' marker—this indicates that the device could not process the
command you entered. The device also prints the command and marks the first invalid character
by putting a '^' under it. Note that you may get this error if you enter a command in the wrong
mode, as the following output shows.
interface port1.0.1
^
% Invalid input detected at '^' marker.
% Unrecognized command—when you try to use ? help and get this message, it indicates that
the device can not provide help on the command because it does not recognize it. This means
the command does not exist, or that you have entered it in the wrong mode, as the following
output shows.
awplus# interface ?
% Unrecognized command
Note: The AlliedWare Plus OS does not tell you when commands are successful. If it does not
display an error message, you can assume the command was successful.
This searches the running-config for the first instance of word and begins the display from that
line.
Note: The show running-config command works in all modes except User Exec mode.
Default settings
When the device initially started up with the AlliedWare Plus OS, it applied default settings and
copied these defaults dynamically into its running-config.
turns on jumbo frame support for all ports on devices with the jumboframe command.
SSH is enabled.
enables the device to look up domain names (but for domain name lookups to work, you have
to configure a DNS server).
turns off Layer 3 multicast packet switching in the switch’s hardware (on Layer 3 switches).
This prevents Layer 3 multicast from flooding the switch’s CPU in its default state as a Layer
2 switch.
sets the maximum number of ECMP routes, on devices that support ECMP.
turns on RSTP on all ports. Note that the ports are not set to be edge ports.
sets all the switch ports to access mode. This means they are untagged ports, suitable for
connecting to hosts.
allocates all the routing table memory space to IPv4 and IPv6 routes on devices that support
IPv6 routing.
For more information about start-up files, see "How to Save and Boot from the Current
Configuration" on page 23. An example default config, with explanations of the meanings of the
commands, is shown below:
After logging in, enter Privileged Exec mode by using the command:
awplus> enable
This section describes how to change an IP address on the default VLAN (vlan1) management
interface.
After logging in, enter Privileged Exec mode by using the command:
awplus> enable
The output looks similar to this (note that this example already has an address assigned):
save the configuration to the device’s default configuration file (called “default.cfg”). By
default, the device uses that file at start-up.
create a new configuration file and set the device to use the new configuration file at start-up.
The parameter startup-config is a short-cut for the current boot configuration file, which will be
the default configuration file unless you have changed it, as described in the next section.
Note: that you can save the file onto Flash memory, or an SD card or USB device. The default is
Flash. For details about file names and paths, see the Configuration and File Management
Feature Overview and Configuration Guide.
Example To save the current configuration in a file called “example.cfg”, enter the command:
To run the new file’s configuration when the device starts up, enter Global Configuration mode
and enter the command:
Note that you can set the device to use a configuration file on an SD card or USB device if you
have saved the configuration file to that card or device. You can only specify that the
configuration file is on an SD card or USB device if there is a backup configuration file already
specified in Flash.
To set a backup configuration file to load if the main configuration file cannot be loaded, enter the
command:
C613-22045-00 REV G How to Save and Boot from the Current Configuration | Page 23
Getting Started with AlliedWare Plus
To set “backup.cfg” as the backup to the main configuration file, enter the command:
To see the files that the device uses at startup, enter Privileged Exec mode and enter the
command:
Boot configuration
----------------------------------------------------------------
Current software : x510-5.4.4-3.5.rel
Current boot image : flash:/x510-5.4.4-3.5.rel
Backup boot image : flash:/x510-5.4.4-3.4.rel
Default boot config: flash:/default.cfg
Current boot config: usb:/example.cfg (file exists)
Backup boot config: flash:/backup.cfg (file exists)
Step 4: Continue updating the file when you change the configuration
When you next want to save the current configuration, enter Privileged Exec mode and enter the
command:
The parameter startup-config is a short-cut for the current boot configuration file.
C613-22045-00 REV G How to Save and Boot from the Current Configuration | Page 24
Getting Started with AlliedWare Plus
Example You can set the timezone to Eastern Standard Time by entering the command:
Example You can change the login banner to “this is a new banner” by entering the command:
Note that this command also has a no parameter that lets you remove the banner altogether.
Passwords
The password can be up to 23 characters in length and include characters from up to four
categories. The password categories are:
uppercase letters: A to Z
lowercase letters: a to z
digits: 0 to 9
special symbols: all printable ASCII characters not included in the previous three categories.
The question mark ? cannot be used as it is reserved for help functionality.
You can then either specify whether the user is forced to change an expired password at the next
login, or specify whether the user is not allowed to login with an expired password. You will need
to specify a password lifetime greater than 0 before selecting either of these features. Note that
the security-password forced-change and the security-password reject-expired-pwd
commands cannot be enabled concurrently.
Password Enter the following command to specify the password lifetime in days:
lifetime
awplus(config)# security-password lifetime <0-1000>
Note that the value 0 will disable lifetime functionality and passwords will never expire. If lifetime
functionality is disabled, the security-password forced-change command and the security-
password warning command are also disabled.
Password To specify that a user is forced to change an expired password at the next login, enter the
forced change following command:
Reject expired To specify that a user is not allowed to login with an expired password, enter the following
password command:
Use other password security rules to further configure password security settings.
Password AlliedWare Plus can warn users that passwords will expire in a specified number of days. To
warning specify the number of days, enter the command:
The value 0 will disable warning functionality. The warning period must be less than, or equal to,
the password lifetime.
Password To specify the number of previous passwords that are unable to be reused, enter the command:
history
awplus(config)# security-password history <0-15>
A new password is invalid if it matches a password retained in the password history. The value 0
will disable history functionality. If history functionality is disabled, all users’ password history is
reset and all password history is lost.
Password To specify the minimum allowable password length, enter the command:
minimum
length awplus(config)# security-password minimum-length <1-23>
Password To specify the minimum number of categories that the password must contain in order to be
minimum considered valid, enter the command:
categories
awplus(config)# security-password minimum-categories <1-4>
uppercase letters: A to Z
lowercase letters: a to z
digits: 0 to 9
special symbols: all printable ASCII characters not included in the previous three categories.
The question mark ? cannot be used as it is reserved for help functionality.
To ensure password security, the minimum number of categories should align with the lifetime
selected, i.e. the fewer categories specified the shorter the lifetime specified.
How to add a user is described in "How to add and remove users" on page 27.
Display To list the configuration settings for the various security password rules, enter the command:
security
password awplus# show security-password configuration
settings
To list users’ remaining lifetime or last password change, enter the command:
Both <name> and <password> can contain any printable character and are case sensitive.
When you add a user with administrative rights, <password> will have to conform to the
following rules:
The AlliedWare Plus OS gives you a choice of privilege levels of 1-15. Level 1-6 users are limited
to User Exec mode and can only access some show commands. Level 7-14 users can access a
majority of show commands. Level 15 users have access to all show and configuration
commands.
Note that some show commands, such as show running-configuration and show startup-
configuration, are only available at privilege level 15.
For example, to add user Bob with password 123$%^, enter the command:
Removing To remove a user, enter Global Configuration mode and enter the command:
users
awplus(config)# no username <name>
Note that you can delete all users, including the user called “manager” and the user you are
logged in as. If all privilege 15 user accounts are deleted, a warning message is generated:
If all privilege level 15 user accounts are deleted, and there are no other users configured for the
device, you may have to reboot with the default configuration file.
You can also set a password for the step of moving from User Exec mode to Privileged Exec
mode. This enables users with privilege level 1-6 to access Privileged Exec mode by entering the
password.
When low-privilege-level users log in, they can access the Privileged Exec mode by entering the
enable command with the password. For example, if the password is ‘mypassword’, they would
enter:
Displaying To list the currently logged-in users, enter User Exec or Privileged Exec mode and enter the
users command:
To list all configured users, enter User Exec or Privileged Exec mode and enter the command:
Pre-encrypted passwords
The running-config output above includes the number 8 after the password parameter. This
indicates that the password is displayed in its encrypted form.
You can enter the number 8 and a pre-encrypted password on the command line. You may want
to pre-encrypt passwords if you need to load them onto devices via an insecure method (such as
HTTP, or by emailing them to remote users).
Caution Only enter the number 8 if you are entering a pre-encrypted password—otherwise, you will be
unable to log in using the password and will be unable to access the device through that
username. The next section describes why.
Testing this If you want to test the effect of this, create a new user for the test instead of using the manager
feature user (or another existing user). The test stops you from logging in as the test user, so you need to
have the manager user available to log in as. The following output shows how specifying the
number 8 puts the password into the running-config exactly as you typed it:
After entering the command above, logging in as “Bob” with a password of “friend” does not
work. This is because the device takes the password you enter (“friend”), hashes it, and
compares the hash with the string in the running-config (“friend”). The hashed value and “friend”
are not the same, so the device rejects the login.
overview information
serial number
System Name
awplus
System Contact
System Location
To display this information, enter User Exec or Privileged Exec mode and enter the command:
Stack member 1:
To do this, enter User Exec or Privileged Exec mode and enter the command:
P1FY7502C
Device name
Login banner
To change the timeout for all Telnet sessions, enter Global Configuration mode and enter the
commands:
The new timeout value only applies to new sessions, not current sessions.
awplus(config-line)# exec-timeout 30
awplus(config-line)# exec-timeout 0 30
To set the timeout to infinity, so that sessions never time out, enter either of the commands:
awplus(config-line)# no exec-timeout
awplus(config-line)# exec-timeout 0 0
my company(config)#
The name can contain hyphens and underscore characters, for example:
mycompany(config)#hostname mycompany_more_words
mycompany_more_words(config)#hostname mycompany-hyphenated
mycompany-hyphenated(config)
However, the name must be a single word, as the following example shows.
my company(config)# no hostname
awplus(config)#
Example To display “this is a new banner” when someone logs in, enter the command:
configuring the device to automatically change the time when summer-time begins and ends
Instead of manually setting the time, you can use NTP to automatically get it from another device.
To set the time and date, enter Privileged Exec mode and enter the clock set command:
where:
month is the first three letters of the month name (e.g. sep)
Example To set the time to 14:00:00 on 25 January 2015, use the command:
Example To set the timezone to Eastern Standard Time, use the command:
recurring, when you specify the week when summer-time starts and ends and each year the
device changes the time at those weeks. For example, Eastern Daylight Time (EDT) starts at
2 am on the second Sunday in March and ends at 2 am on the first Sunday in November.
date-based, when you specify the start and end dates for summer-time for a particular year.
For example, Eastern Daylight Time (EDT) starts at 2 am on Sunday, 8 March 2008 and ends
at 2 am on Sunday, 2 November 2008.
Recurring To set summer-time with recurring dates, enter Global Configuration mode and enter the clock
summer-time recurring command:
The <start-time> and <end-time> are in the form hh:mm, in 24-hour time.
Note that if you specify 5 for the week, this changes the time on the last day of the month, not the
5th week.
Date-based To set summer-time for a single year, enter Global Configuration mode and enter the clock
summer-time date command:
The <start-time> and <end-time> are in the form hh:mm, in 24-hour time.
Example For example, to configure EDT for 2015 enter the command:
awplus(config)# clock summer-time EDT date 8 Mar 2008 02:00 2 Nov 2015 02:00 60
You can put a number of AlliedWare Plus devices into Secure Mode, to make the device as
secure as possible by using the strongest encryption algorithms available. Weak hashing
functions such as MD5 and broken cryptographic algorithms such as RC2, DES, DSA, etc, are no
longer considered secure, as they can be susceptible to brute force attacks and collisions.
Secure Mode only allows you to use hashes from the SHA-2 family, and AES block cipher
algorithms instead of the weaker DES cryptographic algorithms.
Block cipher algorithms encrypt data on a per-block basis. Blocks, which are measured in bits,
determine the input of plain text and output of cipher text. So, for example, if you used AES128,
then for every 128 bits of plain text, 128 bits of cipher text are produced.
Secure Mode meets the Common Criteria standard. Common Criteria is an internationally
recognized set of guidelines for the security of information technology products.
Telnet
SSHv1
SNMPv1/v2
Algorithms that are not supported under FIPS, including MD5, RSA-1 and DSA
In Secure Mode, the web server on the device (used by the Device GUI) only accepts AES128-
SHA ciphers.
Do not enable Secure Mode if your device has an older bootloader. Instead, contact Allied
Telesis technical support for assistance.
2. Obtain the correct release file and its sha256sum file by downloading them from the Allied
Telesis Download Center. Save the files on a trusted USB device and connect the USB device
to the device.
3. Erase the device’s Flash. To do this, boot the device into the bootloader diagnostics menu,
using Ctrl-D. Select option 7 'Bootup stage 2 diagnostics menu', and then select option 4
'Erase FLASH (Filesystem only)'.
4. Then select option 0 ‘Restart’ to reboot the device. Enter the main bootloader menu by using
Ctrl-B. Select option 1 ‘Perform one-off boot from alternate source’ and then select the ‘USB’
option and the release you saved in step 1.
5. Once the device has booted up, save the release file to Flash and verify it, as described in
"How to Verify the Release File" on page 38.
6. Set the verified release as the boot release. For example, use the following commands:
awplus#configure terminal
awplus(config)#boot system x550-5.4.8-1.2.rel
8. Use the following command to confirm that the device is in secure mode:
3. Reboot the device. The device must be rebooted after Secure Mode is turned off, and ideally
Flash memory should be erased via the bootloader, as described above.
This command compares the SHA256 checksum of the release file with the correct checksum for
the file.
The correct checksum is listed in the release’s sha256sum file, which is available from the Allied
Telesis Download Center.
Caution: If the verification fails, the following error message will be generated:
“% Verification Failed”
If this happens, please delete the release file and contact Allied Telesis support.
All device models of a particular series run the same release file and therefore have the same
checksum. For example, all x930 Series switches have the same checksum.
Once the device has successfully verified the release file, it adds the crypto verify command to
the running configuration.
If the device is in secure mode, it will verify the release file every time it boots up. To do this, it
runs the crypto verify command while booting. Therefore, you need to copy the crypto verify
command to the startup configuration, by using the command:
If the crypto verify command is not in the startup configuration, the device will report a
verification error at bootup.
If there is a verification error at bootup, the device produces an error message and finishes
booting up. If this happens, run the crypto verify command after bootup finishes, to verify the
running release file. If verification of the running release file fails, delete the release file and
contact Allied Telesis support.
awplus# dir
The output lists files and directories in order of modification date, descending. It looks like this:
Note: You can specify the directory with or without a / after the directory name.
Example To display the contents of a directory called ‘example’, enter the command:
Example To display the contents of a directory in NVS called “example”, enter the command:
Example To display the contents of the file called “example.cfg”, enter the command:
awplus# pwd
For the top-level directory, the output looks like this:
flash:
Changing directories
To change to another directory, enter Privileged Exec mode and enter the command:
awplus# cd <directory-name>
To go to a directory one level higher in the directory tree, enter the command:
awplus# cd ..
awplus# cd example
To go up one level, which returns you to the top level directory, enter the command:
awplus# cd ..
awplus# cd nvs:
To change to the top-level directory on an SD card, enter the command:
awplus# cd card:
Note that the prefix for the SD card is “card” not “sdcard”. Next, you can change to other
directories in NVS memory or on the SD card, by entering the command:
awplus# cd <directory-name>
Alternatively, you can go straight from Flash to a subdirectory in the alternative file system, by
entering one of the commands:
awplus# cd nvs:<directory-name>
awplus# cd card:<directory-name>
awplus# cd flash:
Example To change to the directory within NVS called “example”, enter the command:
awplus# cd nvs:example
To go up one level, which returns you to the top-level directory of NVS memory, enter the
command:
awplus# cd ..
Example To make a directory called “example” within the Flash file system, enter the command:
Deleting directories
To delete an empty directory, enter Privileged Exec mode and enter the command:
Example To delete an empty directory called “example” from within the Flash file system, enter the
command:
Between To copy a file to another directory within the same file system, enter the command:
directories
awplus# copy <source-filename> <directory-name>/
The / after the directory name is required. Otherwise the device displays an error:
(“37: Destination file is a directory”).
The device then prompts you for the destination filename. To give the copy a new name, type the
name at the prompt. You can include directory names in the path.
To use the same filename as the original, press the Enter key (do not press the “y” key—that
names the copy “y”).
Example To put a copy of example.cfg into the example directory, enter the command:
For example, to copy from Flash to NVS when your current directory is the top-level Flash
directory, enter Privileged Exec mode and enter the command:
To copy from NVS to Flash when your current directory is the top-level Flash directory, enter the
command:
Example To copy the file “example.txt” from the directory in NVS called “example” to the top level of Flash,
enter the command:
Note: You can specify the server and filename in the command instead of waiting for prompts.
Use a format like the following:
Example To copy example.cfg to the TFTP server at 172.1.1.1, enter the command:
To edit an existing file, enter Privileged Exec mode and enter the command:
edit <filename>
edit
When you save the new file, you may need to specify the file system to store it on. For Flash, use
flash:<filename>.
Using JOE To format and manipulate text in JOE, you use control-character sequences. The following table
summarizes a few useful sequences—for details, see:
http://joe-editor.sourceforge.net/manpage.html
Save the file and exit (this prompts for a filename) Ctrl-K-X
Exit without saving the file Ctrl-C
Go to the beginning of the file Ctrl-K-U
Go to the end of the file Ctrl-K-V
Go up one screenful of text in the file Ctrl-U
Go down one screenful of text in the file Ctrl-V
Select a block of text:
Move a selected block of text Place cursor at destination then enter: Ctrl-K-M
Completely To return to factory settings, enter Privileged Executive mode and use the command:
restore
defaults awplus# erase factory-default
This command erases all data from NVS and all data from flash excluding the following:
The device is then rebooted and returned to its factory default condition as follows:
awplus>en
awplus#erase factory-default
This command will erase all NVS, all flash contents except for
the boot release, and any license files, and then reboot the switch.
Proceed ? (y/n):y
.
.
.
Loading default configuration
Warning: flash:/default.cfg does not exist, loading factory defaults.
..
done!
Received event network.configured
Restore The device dynamically adds the default settings to the running-config at start-up if the default
default file is not present. You can use this feature to completely remove your configuration and return to
configuration
the factory default configuration, without removing any other files. To do this, delete or rename
the default file and make sure no other file is set as the start-up configuration file.
Find the location of the default boot configuration file, by entering Privileged Exec mode and
entering the command:
Delete the default file when it is the current boot configuration file, by entering Privileged Exec
mode and entering either of the commands:
or
Caution Erasing startup-config deletes the current boot configuration file—it does not simply
stop the file from being the boot file.
To make sure that no other file is loaded at start-up, enter Global Configuration mode and enter
the command:
Partially To partially restore the default settings, make a configuration file that contains the settings you
restore want to keep and set this as the start-up configuration file. On start-up, the device will add the
defaults
missing settings to the running-config.
For example, to use default settings but still keep an IP address on the eth0 (NET MGMT)
management port, create a file like the following one and set it as the boot configuration file:
!
interface eth0
ip address 172.28.8.210/16
!
ip route 0.0.0.0/0 172.28.0.1
!
end
Step 1: Put the new release onto your TFTP server or your USB drive.
Step 2: If necessary, create space in the device’s Flash memory for the new release.
Note that you cannot delete the current release file. To see how much space is free, use the
command:
Step 3: Copy the new release from your TFTP server or your USB drive onto the
device.
To copy the release file from a TFTP server to Flash memory, enter Privileged Exec mode and
enter the command:
To copy the release file from a USB device, when your current directory is the top-level Flash
directory, enter the command:
On SBx8100 Series switches, you only need to copy the new release to the Active
SBx81CFC400 Control Fabric Card (CFC). If your SBx8100 system has a standby CFC installed,
the new release file, the configuration file, and all licenses are automatically synchronized from
the Active CFC.
You can set a backup release file to load if the main release file cannot be loaded. Enter the
command:
Step 6: Reboot.
Running the findme command causes the device’s LEDs to alternately flash green and amber at
a rate of 1 Hz. If the device has no amber LED, then the green LED will flash on/off at a rate of 1
Hz.
An optional interface parameter specifies one or more interfaces to flash, while an optional
member parameter specifies a particular stack member. Both these parameters are mutually
exclusive. If no interface or member parameter is specified, then all ports on the device or stack
are flashed.
An optional timeout parameter specifies the flash behavior duration. The default time is one
minute (60 seconds). Normal LED behavior is restored automatically after either the default time,
or a specified time, has elapsed or a no findme command is used.
To display only part of the output, follow the command with | and then other keywords (see
“Output modifiers” below)
To save the output to a file, follow the command with > filename
To append the output to an existing file, follow the command with >> filename
Using the ? after typing the show command displays the following information about these
tokens.
| Output modifiers
> Output redirection
>> Output redirection (append)
C613-22045-00 REV G How to Easily Locate the Device in a Server Room (Find Me) | Page 48
Getting Started with AlliedWare Plus
Output modifiers
Type the | (vertical bar) to use output modifiers.
Begin The begin parameter causes the display to begin at the first line that contains the input string.
...skipping
interface vlan1
ip address 192.168.14.1
!!
line con 0
login
line vty 0 4
login
!
end
Exclude The exclude parameter excludes all lines of output that contain the input string. In the following
output all lines containing the word “input” are excluded:
Interface vlan1
Scope: both
Hardware is Ethernet, address is 192.168.14.1
index 3 metric 1 mtu 1500 <UP,BROADCAST,RUNNING,MULTICAST>
Label switching is disabled
No Virtual Circuit configured
Administrative Group(s): None
DSTE Bandwidth Constraint Mode is MAM
output packets 4438, bytes 394940, dropped 0
output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0
collisions 0
Include The include parameter includes only those lines of output that contain the input string. In the
output below, all lines containing the word “input” are included:
C613-22045-00 REV G How to Filter and Save “show” Command Output | Page 49
Redirect The redirect parameter puts the lines of output into the specified file. If the file already exists, the
new output overwrites the file’s contents; the new output is not appended to the existing file
contents.
Output The output redirection token > puts the lines of output into the specified file. If the file already exists,
redirection the new output overwrites the file’s contents; the new output is not appended to the existing file
contents.
Append The append output token >> adds the lines of output into the specified file. The file must already
output exist, for the new output to be added to the end of the file’s contents; the new output is appended to
the existing file contents.
C613-22045-00 REV G
NETWORK SMARTER
North America Headquarters | 19800 North Creek Parkway | Suite 100 | Bothell | WA 98011 | USA | T: +1 800 424 4284 | F: +1 425 481 3895
Asia-Pacific Headquarters | 11 Tai Seng Link | Singapore | 534182 | T: +65 6383 3832 | F: +65 6383 3830
EMEA & CSA Operations | Incheonweg 7 | 1437 EK Rozenburg | The Netherlands | T: +31 20 7950020 | F: +31 20 7950021
alliedtelesis.com
© 2019 Allied Telesis, Inc. All rights reserved. Information in this document is subject to change without notice. All company names, logos, and product designs that are trademarks or registered trademarks are the property of their respective owners.