Juniper WLC 100
Juniper WLC 100
Juniper WLC 100
Release
7.5
July 2011
Trademarks
Juniper Networks, the Juniper Networks logo, NetScreen, NetScreen Technologies, the NetScreen logo,
NetScreen-Global Pro, ScreenOS, and GigaScreen are registered trademarks of Juniper Networks, Inc. in
the United States and other countries.
The following are trademarks of Juniper Networks, Inc.: ERX, ESP, E-series, Instant Virtual Extranet,
Internet Processor, J2300, J4300, J6300, J-Protect, J-series, J-Web, JUNOS, JUNOScope, JUNOScript,
JUNOSe, M5, M7i, M10, M10i, M20, M40, M40e, M160, M320, M-series, MMD, NetScreen-5GT,
NetScreen-5XP, NetScreen-5XT, NetScreen-25, NetScreen-50, NetScreen-204, NetScreen-208,
NetScreen-500, NetScreen-5200, NetScreen-5400, NetScreen-IDP 10, NetScreen-IDP 100,
NetScreen-IDP 500, NetScreen-Remote Security Client, NetScreen-Remote VPN Client, NetScreen-SA
1000 Series, NetScreen-SA 3000 Series, NetScreen-SA 5000 Series, NetScreen-SA Central Manager,
NetScreen Secure Access, NetScreen-SM 3000, NetScreen-Security Manager, NMC-RX, SDX, Stateful
Signature, T320, T640, T-series, and TX Matrix. All other trademarks, service marks, registered
trademarks, or registered service marks are the property of their respective owners. All specifications are
subject to change without notice. Juniper Networks assumes no responsibility for any inaccuracies in this
document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this
publication without notice
Disclaimer
All statements, specifications, recommendations, and technical information are current or planned as of
the date of the publication of this document. They are reliable as of the time of this writing and are
presented without warranty of any kind, expressed or implied. In an effort to continuously improve the
product and add features, Juniper Networks reserves the right to change any specifications contained in
this document without prior notice of any kind.
This command reference explains Mobility System Software (MSS) command line interface (CLI)
commands that you enter on a Mobility Exchange to configure and manage the Juniper Networks
Mobility System wireless LAN (WLAN).
Read this reference if you are a network administrator responsible for managing Mobility Exchange (MX)
switches and Mobility Point (MP) access points in a network.
RingMaster Quick Start Guide Instructions for installing and configuring RingMaster services.
RingMaster Planning Guide Instructions for planning, deploying, and managing the entire
WLAN with the RingMaster tool suite. Read this guide to learn how to plan wireless services.
RingMaster Management Guide Instructions for managing and monitoring your WLAN using
the RingMaster tool suite and how to optimize and manage your WLAN.
Installation
Juniper Mobility Exchange Hardware Installation Guide Instructions and specifications for
installing an MX.
JuniperMobility System Software Quick Start Guide Instructions for performing basic setup of
secure (802.1X) and guest (WebAAA) access, and for configuring a Mobility Domain for
roaming
Juniper Indoor Mobility Point Installation Guide Instructions and specifications for installing an
MP access point and connecting it to an MX.
Juniper Outdoor Mobility Point Installation Guide Instructions and specifications for installing
outdoor access points and connecting to an MX.
Juniper Regulatory Information Important safety instructions and compliance information that
you must read before installing Juniper Networks products.
Configuration and Management
Caution: This situation or condition can lead to data loss or damage to the product or other property
Hypertext Links
Hypertext links appear in Blue. For example, this is a link to END USER LICENSE AGREEMENT.
Convention
Description
Example
Fixed-width text
like this
terminal screen.
[edit]
root@# set system domain-name
domain-name
| (pipe symbol)
broadcast | multicast
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
; (semicolon)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the
documentation. Send e-mail to [email protected] with the following:
Document URL or title
Page number if applicable
Software version
Your name and company
Documentation Feedback
c.
Product purchase documents, paper or electronic user documentation, and/or the particular
licenses purchased by Customer may specify limits to Customers use of the Software. Such limits
may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions,
calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or
require the purchase of separate licenses to use particular features, functionality, services,
applications, operations, or capabilities, or provide throughput, performance, configuration,
bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may
restrict the use of the Software to managing certain kinds of networks or require the Software to be
used only in conjunction with other specific Software.Customers use of the Software shall be
subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customers right to use the Software expires 30 days after
download, installation or use of the Software. Customer may operate the Software after the 30-day
trial period only if Customer pays for a license to do so. Customer may not extend or create an
additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only
to manage access to Customers enterprise network. Specifically, service provider customers are
expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software
to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein
to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the
Customer to, and Customer agrees not to and shall not: (a) modify, unbundle, reverse engineer, or
create derivative works based on the Software; (b) make unauthorized copies of the Software (except
as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software, in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in
any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of
the Software to any third party, including as may be embedded in Juniper equipment sold in the
secondhand market; (f) use any locked or key-restricted feature, function, service, application,
operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from
Juniper, even if such feature, function, service, application, operation, or capability is enabled without a
key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the Software
in any manner that extends or is broader than the uses purchased by Customer from Juniper or an
authorized Juniper reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded
Software (or make it available for use) on Juniper equipment that the Customer did not originally
purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or
benchmarking of the Software to any third party without the prior written consent of Juniper; or (l) use
the Software in any manner other than as expressly provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this
Agreement. Upon request by Juniper, Customer shall furnish such records to Juniper and certify its
compliance with this Agreement.
10
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the
confidential property of Juniper. As such, Customer shall exercise all reasonable commercial efforts to
maintain the Software and associated documentation in confidence, which at a minimum includes
restricting access to the Software to Customer employees and contractors having a need to use the
Software for Customers internal business purposes.
7. Ownership. Juniper and Junipers licensors, respectively, retain ownership of all right, title, and interest
(including copyright) in and to the Software, associated documentation, and all copies of the Software.
Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or interest in the
Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall
be as set forth in the warranty statement that accompanies the Software (the Warranty Statement).
Nothing in this Agreement shall give rise to any obligation to support the Software. Support services
may be purchased separately. Any such support shall be governed by a separate, written support
services agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE
LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR
JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES
ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR
JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY
STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL
WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR
OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT
THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL
OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO
INTRUSION OR ATTACK. In no event shall Junipers or its suppliers or licensors liability to Customer,
whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid
by Customer for the Software that gave rise to the claim, or if the Software is embedded in another
Juniper product, the price paid by Customer for such other product. Customer acknowledges and
agrees that Juniper has set its prices and entered into this Agreement in reliance upon the disclaimers
of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk
between the Parties (including the risk that a contract remedy may fail of its essential purpose and
cause consequential loss), and that the same form an essential basis of the bargain between the
Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall
result in automatic termination of the license granted herein. Upon such termination, Customer shall
destroy or return to Juniper all copies of the Software and related documentation in Customers
possession or control.
11
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be
responsible for paying Taxes arising from the purchase of the license, or importation or use of the
Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to
Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or
modified. All payments made by Customer shall be net of any applicable withholding tax. Customer will
provide reasonable assistance to Juniper in connection with such withholding taxes by promptly:
providing Juniper with valid tax receipts and other required documentation showing Customers
payment of any withholding taxes; completing appropriate applications that would reduce the amount
of withholding tax to be paid; and notifying and assisting Juniper in any audit or tax proceeding related
to transactions hereunder. Customer shall comply with all applicable tax laws and regulations, and
Customer will promptly pay or reimburse Juniper for all costs and damages related to any liability
incurred by Juniper as a result of Customers non-compliance or delay with its responsibilities herein.
Customers obligations under this Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of
any United States and any applicable foreign agency or authority, and not to export or re-export the
Software or any direct product thereof in violation of any such restrictions, laws or regulations, or
without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customers
ability to export the Software without an export license.
12. Commercial Computer Software. The Software is commercial computer software and is provided
with restricted rights. Use, duplication, or disclosure by the United States government is subject to
restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4, FAR
12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request,
Juniper shall provide Customer with the interface information needed to achieve interoperability
between the Software and another independently created program, on payment of applicable fee, if
any. Customer shall observe strict obligations of confidentiality with respect to such information and
shall use such information in compliance with any applicable terms and conditions upon which Juniper
makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any
supplier of Juniper whose products or technology are embedded in (or services are accessed by) the
Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor
shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain
third party software may be provided with the Software and is subject to the accompanying license(s),
if any, of its respective owner(s). To the extent portions of the Software are distributed under and
subject to open source licenses obligating Juniper to make the source code for such portions publicly
available (such as the GNU General Public License (GPL) or the GNU Library General Public
License (LGPL)), Juniper will make such source code portions (including Juniper modifications, as
appropriate) available upon request for a period of up to three years from the date of distribution. Such
request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA
94089, ATTN: General Counsel. You may obtain a copy of the GPL at
http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html .
12
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without
reference to its conflicts of laws principles. The provisions of the U.N. Convention for the International
Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the
Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and
federal courts within Santa Clara County, California. This Agreement constitutes the entire and sole
agreement between Juniper and the Customer with respect to the Software, and supersedes all prior
and contemporaneous agreements relating to the Software, whether oral or written (including any
inconsistent terms contained in a purchase order), except that the terms of a separate written
agreement executed by an authorized Juniper representative and Customer shall govern to the extent
such terms are inconsistent or conflict with terms contained herein. No modification to this Agreement
nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the
party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such
invalidity shall not affect the validity of the remainder of this Agreement. This Agreement and
associated documentation has been written in the English language, and the Parties agree that the
English version will govern. (For Canada: Les parties aux prsents confirment leur volont que cette
convention de mme que tous les documents y compris tout avis qui s'y rattach, soient redigs en
langue anglaise. (Translation: The parties confirm that this Agreement and all related documentation is
and will be in the English language)).
13
14
Access Commands
Use access commands to control access to the Mobility Software System (MSS) (CLI). This chapter
presents access commands alphabetically. Use the following table to locate commands in this chapter
based on their use.
Access Privileges
enable on page 15
set enablepass on page 16
disable on page 15
quit on page 16
disable
Usage Changes the CLI session from enabled mode to restricted access.
Syntax disable
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Examples The following command restricts access to the CLI for the current session:
WLC# disable
WLC>
See Also enable on page 15
enable
Usage Places the CLI session in enabled mode, which provides access to all commands required
for configuring and monitoring the system.
Syntax enable
Access All.
History Introduced in MSS 1.0.
Usage MSS displays a password prompt to challenge you with the enable password. To enable a
session, your or another administrator must have configured the enable password to this WLC
with the set enablepass command.
Examples The following command plus the enable password provides enabled access to the CLI
for the current sessions:
WLC> enable
Enter password: password
WLC#
See Also
set enablepass on page 16
Copyright 2011, Juniper Networks, Inc.
15
quit
Usage Exit from the CLI session.
Syntax quit
Defaults None.
Access All.
History Introduced in MSS 1.0.
Examples To end your session, type the following command:
WLC> quit
set enablepass
Usage Sets the password that provides enabled access (for configuration and monitoring) to the
MX switch.
After typing the set enablepass command, press Enter. If you are entering the first enable
password on this MX, press Enter at the Enter old password prompt. Otherwise, type the old
password. Then type a password of up to 32 alphanumeric characters with no spaces, and reenter
it at the Retype new password prompt.
Caution: Be sure to use a password that you can remember. If you lose the enable password,
the only way to restore it returns the WLC to the default settings and erases the configuration.
16
Access Commands
enable on page 15
17
18
New
Configuration
quickstart on page 24
Auto-Config
Run Scripts
Display
System Identification
Updated
New
Updated
Updated
Updated
Updated
Help
help on page 22
History
history on page 23
clear history on page 20
Updated
License
Technical Support
Copyright 2011, Juniper Networks, Inc.
banner motd ^^
See Also
set banner motd on page 27
show banner motd on page 38
clear history
Usage Deletes the command history buffer for the current CLI session.
Syntax clear history
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples To clear the history buffer, type the following command:
WLC# clear history
success: command buffer was flushed.
See Also history on page 23
clear prompt
Usage Resets the system prompt to its previously configured value. If the prompt was not
configured previously, this command resets the prompt to the default.
Syntax clear prompt
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To reset the prompt, type the following command:
wildebeest# clear prompt
success: change accepted.
20
WLC#
See Also set prompt on page 30. (For information about default prompts, see Command
Prompts on page 25.)
clear run
Usage Clear the rule associated with scriptname.
Syntax clear run scriptfilename
Defaults None
Access Enabled
History Added in MSS 7.1.
Examples To clear the script, runmem, use the following command:
WLC# clear run runmem
success: change accepted.
clear system
Clears the system configuration of the specified information.
Caution: If you change the IP address, any currently configured Mobility Domain operations
cease. You must reset the Mobility Domain.
countrycode
idle-timeout
Resets the number of seconds a CLI management session can remain idle
to the default value (3600 seconds).
ip-address
location
WLC-secret
name
Resets the name of the WLC to the default system name, which is
WLC-mm-nnnnnn, where mm is the model number and nnnnnn is the
last 6 digits of the switchs MAC address.
Defaults None.
Access Enabled.
21
History
Version 1.0
Command introduced.
Version 4.1
Version 7.1
Version 7.3
Examples To clear the location of the WLC, type the following command:
WLC# clear system location
success: change accepted.
See Also
set system contact on page 32
set system countrycode on page 32
set system idle-timeout on page 36
set system ip-address on page 36
set system location on page 37
show config on page 605
show system on page 41
help
Usage Displays a list of commands that can be used to configure and monitor the WLC.
Syntax help
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples Use this command to see a list of available commands. If you have restricted access,
you see fewer commands than if you have enabled access. To display a list of CLI commands
available at the enabled access level, type the following command at the enabled access level:
WLC# help
Commands:
------------------------------------------------------------------------
22
backup
clear
Clear,
commit
copy
crypto
delete
Delete url
dir
disable
exit
help
history
install
ldap-ping
load
logout
monitor
md5
md5 filename
mkdir
monitor
ping
quickstart
quit
radping
reset
restore
rfping
Rfping operations
rmdir
rollback
run
save
storage
set
show
telnet
traceroute
uninstall
upgrade
history
Usage Displays the command history buffer for the current CLI session.
Syntax history
Defaults None.
Access All.
23
quickstart
Runs a script that interactively helps you configure a new WLC.
(For more information, see the Mobility System Software Quick Start Guide.)
Caution: The quickstart command is for configuration of a new WLC only. After prompting you
for verification, the command erases the WLC configuration before continuing. If you run this
command on a WLC with a configuration, the configuration is erased. In addition, error messages
such as Critical AP Notice for directly connected MPs can appear.
24
set auto-config
Usage Enables an WLC switch to contact a RingMaster server for its configuration.
A network administrator at the corporate office can preconfigure the switch in a RingMaster
network plan. The switch configuration must have a name for the switch, the model must be
WLCR-2, and the serial number must match the switchs serial number. The configuration should
also include all other settings required for the deployment, including MP configuration, SSIDs, AAA
settings, and so on.
When the RingMaster server in the corporate network receives the configuration request, the
server looks in the currently open network plan for a WLC configuration with the same model and
serial number as the one in the configuration request.
If the network plan contains a configuration with a matching model and serial number,
RingMaster sends the configuration to the WLC and restarts the WLC. The WLC boots using
the configuration received from RingMaster.
If the network plan does not have a configuration with a matching model and serial number, a
verification warning appears in RingMaster. The warning lists the WLC serial number and IP
address. The network administrator can upload the WLC into the network plan, configure WLC
parameters, and deploy the configuration to the WLC.
To use the auto-config option with a new (unconfigured) WLCR-2, insert a paperclip or similar
object into the WLCR-2 factory reset hole to press the switch. The factory reset switch must be
held for about 3 seconds while the factory reset LED (the right LED above port 1) is lit. Normally,
this LED remains solidly lit for 3 seconds after power on. However, when the factory reset switch is
pressed, the LED flashes for 3 seconds instead.
If you want another WLC model to be able to access a RingMaster server for a configuration, you
also must preconfigure the WLC with the following information:
IP address
Default router (gateway) address
Domain name and DNS server address
You can enable the WLC to use the MSS DHCP client to obtain this information from a DHCP
server in the local network where the WLC is deployed. Alternatively, you can statically configure
the information.
The IP address and DNS information are configured independently. You can configure the
combination of settings that work with the network resources available at the deployment site. The
following examples show some of the combinations you can configure.
Syntax set auto-config {enable | disable}
enable
disable
Defaults The auto-config option is automatically enabled on an unconfigured WLCR-2 when the
factory reset switch is pressed during power on. However, auto-config is disabled by default on
other models.
25
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following commands stage an WLC to use the auto-config option. The network
where the WLC is installed has a DHCP server, so the WLC is configured to use a MSS DHCP
client to obtain an IP address, default router address, DNS domain name, and DNS server IP
addresses.
1. Configure a VLAN:
WLC8# set vlan 1 port 7
success: change accepted.
2. Enable the DHCP client on VLAN 1:
WLC# set interface 1 ip dhcp-client enable
success: change accepted.
3. Enable the auto-config option:
WLC# set auto-config enable
success: change accepted.
4. Save the configuration changes:
WLC# save config
success: configuration saved.
See Also
crypto generate key on page 478
crypto generate self-signed on page 481
save config on page 601
set interface dhcp-client on page 114
set vlan port on page 83
26
enable
disable
Delimiting character that begins and ends the prompt message; for example,
double quotes ().
message
Defaults None.
Access Enabled.
History Introduced in MSS Version 6.0.
Examples To enable the prompt for the MOTD banner, type the following command:
WLC# set banner acknowledge enable
success: change accepted.
To set Do you agree? as the text to be displayed following the MOTD banner, type the following
command:
WLC# set banner acknowledge message Do you agree?
success: change accepted.
After these commands are entered, when the user logs on, the MOTD banner is displayed,
followed by the text Do you agree? If the user enters y, then the login proceeds. If not, then the
user is disconnected.
Quotation marks can be used in the message if they are enclosed by delimiting characters. For
example, to set the text Do you agree? (including the quotation marks) as the text to be displayed
following the MOTD banner, type the following command:
WLC# set banner acknowledge message "Do you agree?"
success: change accepted.
See Also
set banner motd on page 27
clear banner motd on page 20
show banner motd on page 38
Delimiting character that begins and ends the message; for example, double
quotes ().
text
Defaults None.
Copyright 2011, Juniper Networks, Inc.
27
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To create a banner that says Meeting @ 4:00 p.m. in Conference Room #3, type the
following command:
WLC# set banner motd "Meeting @ 4:00 p.m. in Conference Room #3"
success: motd changed.
See Also
set banner acknowledge on page 26
clear banner motd on page 20
show banner motd on page 38
set confirm
Usage Enables or disables the display of confirmation messages for commands that might have a
large impact on the network.
This command remains in effect for the duration of the session, until you enter an exit or quit
command, or until you enter another set confirm command.
Usage
Syntax set confirm {on | off}
on
off
set length
Usage Defines the number of lines of CLI output to display between paging prompts. MSS
displays the set number of lines and waits for you to press any key to display another set, or type
q to quit the display.
Use this command if the output of a CLI command is greater than the number of lines allowed by
default for a terminal type.
28
Number of lines of text to display between paging prompts. You can specify
0 and from 10 to 512. The 0 value disables the paging prompt action
entirely.
Command introduced.
Version 6.0
Version 7.0
Examples To set the number of lines displayed to 100, type the following command:
WLC# set length 100
success: screen length for this session set to 100
set license
Usage Installs an upgrade or feautre license key on an WLC.
The WLC-200 and WLC-216 can boot and manage up to 32 MPs by default. You can increase the
MP support to 64, 96, or 128 MPs, by installing one or more activation keys. You can install a
32-MP upgrade, 64-MP upgrade, or 96-MP upgrade. If you have already installed a 32-MP or
64-MP upgrade, you can still install additional upgrades.
The entire upgrade matrix is available in the Release Notes for the latest released MSS version.
Syntax set license activation-key
activation-key
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 2.0
Command deprecated.
29
Version 3.1
Version 7.1
Examples To install an activation key for an additional 80 MPs, type the following command:
WLC# set license 3B02-D821-6C19-CE8B-F20E
success: license accepted
See Also show license on page 39
set prompt
Usage Changes the CLI prompt for the WLC to a string you specify.
When you first log in for the initial configuration of the WLC, the CLI provides an
WLC-mm-nnnnnn> prompt. After you become enabled by typing enable and giving a suitable
password, the WLC-mm-nnnnnn# prompt is displayed.
If you use the set system name command to change the default system name, MSS uses that
name in the prompt, unless you also change the prompt with set prompt.
Syntax set prompt string
string
Defaults The factory default for the WLC name is WLC-mm-nnnnnn, where mm is the model
number and nnnnnn is the last 6 digits of the 12-digit system MAC address.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following example sets the prompt from WLC to happy_days:
WLC# set prompt happy_days
success: change accepted.
happy_days#
See Also
clear prompt on page 20
set system name on page 38
show config on page 605
set run
Usage Sets the timing for scripts to automatically run on the WLC.
Use this command to run scripts in *.txt format that automatically run the specified commands
configured in the file.
30
To execute a script at a specified minute of a specified hour or every hour, in a specified day or
every week-day or everyday, use the interval specification format day, hour, and minute. For
example, to run a script every weekday at 18:15, use the format Wk1815. To run every Monday at
5 minutes after the hour,use the format, MoAll05. To run a script everyday at midnight, use the
format Any0000.
To run a script every X hours, use the format dayHrint/HHh. To run a script every X minutes, use
the format DayHrint/MMm. For example, to run a script every week day between 3-6 a.m.
excluding 6: a.m., use the format Wk03-06/01h.
Syntax set run scriptname on [interval intervalspec | startup | shutdown]
scriptname
intervalspec
startup
shutdown
Defaults None
Access Enabled
History Added in MSS 7.1
Examples To run a script called runmem every Saturday at 5 p.m. use the following command:
WLC# set run runmem sa1800
success: change accepted.
Defaults None
Access Enabled
History Added in MSS 7.1.
Examples To set the console timeout to 120 seconds (2 minutes), use the following command:
WLC# set system console-timeout 120
success: change accepted.
31
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced.
MSSVersion 7.3
Examples The following command sets the system contact information to [email protected]:
MX-20#set system contact [email protected]
success: change accepted.
See Also
clear system on page 21
set system location on page 37
set system name on page 38
show system on page 41
Two-letter code for the country of operation for the WLC. You can specify
one of the codes listed in Table 2.
32
Country
Code
Algeria
DZ
Argentina
AR
Anguilla
AI
Australia
AU
Austria
AT
BA
Code
Belgium
BE
Bulgaria
BG
Bahrain
BH
Bolivia
BO
Botswana
BW
Brazil
BR
Belize
BZ
Canada
CA
Chile
CL
China
CN
Colombia
CO
Costa Rica
CR
Cote DIvoire
CI
Croatia
HR
Cyprus
CY
Czech Republic
CZ
Denmark
DK
Dominica
DM
Dominican Republic
DO
Ecuador
EC
El Salvador
SV
Egypt
EG
Estonia
EE
Finland
FI
France
FR
Germany
DE
Greece
GR
Grenada
GD
Guatemala
GT
Guam
GU
Honduras
HN
Hong Kong
HK
Hungary
HU
Iceland
IS
India
IN
Indonesia
ID
Ireland
IE
Israel
IL
Italy
IT
Jamaica
JM
33
Code
Japan
JP
Jordan
JO
Kazakhstan
KZ
Kenya
KE
KN
Kuwait
KW
Cayman Islands
KY
Latvia
LV
Lebanon
LB
Liechtenstein
LI
Lithuania
LT
St. Lucia
LC
Liechtenstein
LI
Luxembourg
LU
MK
Republic of
34
Malaysia
MY
Malta
MT
Mauritius
MU
Mexico
MX
Monserrat
MS
Morocco
MA
Namibia
NA
Netherlands
NL
New Zealand
NZ
Nigeria
NG
Norway
NO
Oman
OM
Pakistan
PK
Panama
PA
Paraguay
PY
Peru
PE
Philippines
PH
Poland
PL
Portugal
PT
Puerto Rico
PR
Qatar
QA
Romania
RO
Russia
RU
Saudi Arabia
SA
Code
Serbia
CS
Singapore
SG
Slovakia
SK
Slovenia
SI
South Africa
ZA
South Korea
KR
Spain
ES
Sri Lanka
LK
Sweden
SE
Switzerland
CH
Taiwan
TW
Tanzania
TZ
Thailand
TH
East Timor
TP
TT
Tunisia
TN
Turkey
TR
Ukraine
UA
AE
United Kingdom
GB
United States
US
Uruguay
UY
Venezuela
VE
Vietnam
VN
VC
US Virgin Islands
VI
Zambia
ZM
Zimbabwe
ZW
Command introduced
Version 1.1
New country codes added: AE, AU, BR, CN, CZ, ES, GR, HK, HU, KR, IL,
IN, LI, WLC, MY, NZ, PL, SA, SG, SI, SK, TH, TW, ZA
Version 6.2
New country codes added: BH, BO, BW, CL, CO CR, CI, HR, CY, DM, DO,
EC, SV, EG, EE, GD, GT, HN, ID, JM, JO, KZ, KE, KN, KW, KY, LV, LB, LI,
LT, LC, MU, MS, MA, NA, NG, OM, PK, PA, PY, PE, PH, PR, RO, RU, CS,
LK, TZ, TT, TN, TR, UA, UY, VE, VN, VC, ZM, and ZW.
35
Examples To set the country code to Canada, type the following command:
MX-20#set system country code CA
success: change accepted.
See Also show config on page 605
Number of seconds a CLI management session can remain idle before MSS
terminates the session. You can specify from 0 to 86400 seconds (one day).
If you specify 0, the idle timeout is disabled.
seconds
Command introduced.
Version 7.0
Examples The following command sets the idle timeout to 1800 seconds (one half hour):
WLC# set system idle-timeout 1800
success: change accepted.
See Also
clear system on page 21
show system on page 41
Warning: Any currently configured Mobility Domain operations cease if you change the IP address. If
you change the address, you must reset the Mobility Domain.
36
ip-addr
Defaults None.
Access Enabled.
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced.
Usage You can include spaces in the system location string, but cannot exceed 256 characters.
To view the system location string, type the show system command.
Examples To store the location of the WLC in the configuration, type the following command:
WLC# set system location first-floor-bldg3
success: change accepted.
See Also
clear system on page 21
set system contact on page 32
set system name on page 38
show system on page 41
37
Defaults By default, the system name and command prompt have the same value. The factory
default for both is WLC-mm-nnnnnn, where mm is the model number and nnnnnn is the last 6 digits
of the 12-digit system MAC address.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following example sets the system name to a name that identifies the WLC switch:
WLC# set system name WLC-bldg3
success: change accepted.
WLC-bldg3#
See Also
clear system on page 21
set prompt on page 30
set system contact on page 32
set system location on page 37
show system on page 41
38
show license
Usage Displays information about the license key(s) currently installed on an WLC.
Syntax show license keys
Defaults None.
Access All.
History
Version 1.0
Command introduced.
Version 2.0
Current session count and Last sent alert time fields removed.
Version 3.1
Version 7.0
: 0321300013
Installed
Active
show load
Usage Changes to the show load command allows you to obtain instantaneous CPU and
memory load information in a more useful format. In addition, more information is provided that
may assist with troubleshooting the WLC on the network.
The following information is displayed:
System CPU load
Summary data displayed:
Last second (also called instant load)
Last minute
Last 5 minutes
Last hour
Last day
Last three days
Historical values drawn as a graph, showing peaks and averages:
Last minute
Last hour
Copyright 2011, Juniper Networks, Inc.
39
Command introduced.
Version 6.2
Usage To display the CPU load recorded from the time the WLC was booted, as well as from the
previous time the show load command was run, type the following command:
Examples
WLCR2_desk# show load cpu
Period
Usage
-------------------Last second:
2%
Last minute:
2%
Last 5 minutes: 2%
Last hour:
2%
Last day:
1%
Last 3 days:
33141%
40
|70
|60
|50
|40
|30
|20
^
^^
^|10
************************************************************|<5
6----5----5----4----4----3----3----2----2----1----1----5----0--0
The overall field shows the CPU load as a percentage from the time the WLC was booted. The
delta field shows CPU load as a percentage from the last time the show load command was
entered.
See Also show system on page 41
show system
Usage Displays system information.
Syntax show system
Defaults None.
Access Enabled.
41
History
Version 1.0
Command introduced
Version 2.0
Version 3.0
Version 4.0
License field removed. To display license information, use the show license
command.
Version 7.0
WLC
System Name:
WLC-bldg3
System Countrycode: US
System Location:
first-floor-bldg3
System Contact:
System IP:
192.168.12.7
00:0B:0E:00:04:30
========================================================================
=======
Boot Time:
2003-11-07 15:45:49
Uptime:
13 days 04:29:10
========================================================================
=======
Fan status:
Temperature: temp1 ok
temp2 ok
temp3 ok
PSU Status:
Memory:
97.04/744.03 (13%)
42
Description
Product Name
MX model number.
System Name
System name (factory default, or optionally configured with set system name).
System Countrycode
Country-specific 802.11 code required for MP operation (configured with set system
countrycode).
System Location
System Contact
System IP
Common interface, source, and default IP address for the MX, in dotted decimal notation
(configured with set system ip-address).
System Secret
Number of seconds MSS allows a CLI management session (console, Telnet, or SSH) to
remain idle before terminating the session. (The system idle timeout can be configured using
the set system idle-timeout command.)
System MAC
MX media access control (MAC) machine address set at the factory, in 6-byte hexadecimal
format.
Boot Time
Uptime
Number of days, hours, minutes, and seconds that the MX has been operating since its last
restart.
Fan status
Temperature
PSU Status
Memory
Current size (in megabytes) of nonvolatile memory (NVRAM) and synchronous dynamic
RAM (SDRAM), plus the percentage of total memory space in use, in the following format:
NVRAM size /SDRAM size (percent of total)
Total power that the MX is currently supplying to directly connected MPs, in watts.
See Also
clear system on page 21
set system contact on page 32
set system countrycode on page 32
set system idle-timeout on page 36
Copyright 2011, Juniper Networks, Inc.
43
show tech-support
Usage Provides an in-depth snapshot of the status of the WLC, which includes details about the
boot image, the version, ports, and other configuration values. This command also displays the
last 100 log messages.
Enter this command before calling the Juniper Networks Technical Assistance Center (TAC). See
Contacting the Technical Assistance Center on page 315 for more information
Syntax show tech-support [file [subdirname/]filename]
[subdirname/]filename
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
See Also
show boot on page 604
show config on page 605
show license on page 39
show system on page 41
show version on page 607
44
Port Commands
Use port commands to configure and manage individual ports and load-sharing port groups. This chapter
presents port commands alphabetically. Use the following table to locate commands in this chapter based
on their use.
Port Type
set port type ap on page 61
Updated
set ap on page 53
Updated
State
Speed
Autonegotiation
PoE
SNMP
Port Groups
Port Mirroring
Statistics
45
clear ap
Usage Removes a Distributed MP.
Warning: When you clear a Distributed MP, MSS ends user sessions that are using the MP.
auto
fdb
Defaults None.
Access Enabled.
History
MSS Version 2.0
Command introduced.
Port Commands
clear port-group
Usage Removes a port group.
Syntax clear port-group name name
name name
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command clears port group server1:
WLC# clear port-group name server1
success: change accepted.
See Also
set port-group on page 56
show port-group on page 64
List of physical ports. MSS disables the copper interface and reenables the
fiber interface on all the specified ports.
Defaults The GBIC (fiber) interface is enabled, and the copper interface is disabled, by default.
Access Enabled.
History
MSS Version 4.0
Command introduced.
Deprecated.
Usage This command applies only to the WLC-400. This command does not affect a link that is
already active on the port.
Examples The following command disables the copper interface and reenables the fiber interface
on port 2:
WLC-400# clear port media-type name
See Also
set port media-type(deprecated) on page 57
show port media-type (deprecated) on page 65
47
port-list
Defaults None.
Access Enabled.
Warning: When you clear a port, MSS ends user sessions that are using the port.
48
Port Commands
List of physical ports. MSS resets and removes the configuration from all the
specified ports.
Defaults The cleared port becomes a network port but is not placed in any VLANs.
Access Enabled.
History Introduced in MSS Version 1.0.
Table 4.Network Port Defaults
Port Parameter
Setting
VLAN membership
None.
Although the command changes a port to a network port, the command does not place
the port in any VLAN. To use the port in a VLAN, you must add the port to the VLAN.
802.1X
No authorization.
Port groups
None.
(IGMP) snooping
Access point and radio parameters
Not applicable
Not applicable
49
packets
receive-errors
transmit-errors
collisions
receive-etherstats
Spacebar
Esc
Exits the monitor. MSS stops displaying the statistics and displays a new command
prompt.
Clears the statistics counters for the currently displayed statistics type. The counters
begin incrementing again.
Examples The following command starts the port statistics monitor beginning with octet statistics
(the default):
WLC# monitor port counters
As soon as you press Enter, MSS clears the window and displays statistics at the top of the
window.
Port
Status
Tx Octets
Rx Octets
========================================================================
=======
50
Port Commands
Up
27965420
34886544
...
To cycle the display to the next set of statistics, press the Spacebar. In this example, packet
statistics are displayed next:
Port
Status
NonUnicast
Rx Unicast
Rx NonUnicast
Tx Unicast
Tx
========================================================================
=======
1
Up
54620
68318
62144
62556
...
Table 6 describes the port statistics displayed by each statistics option. The Port and Status fields
are displayed for each option.
51
Field
Description
Port
Status
Rx Octets
octets
packets
Rx Unicast
Rx NonUnicast
Tx Unicast
receive-errors
Rx Crc
Number of frames received by the port that had the correct length but
contained an invalid frame check sequence (FCS) value. This statistic
includes frames with misalignment errors.
Rx Error
Rx Short
Number of frames received by the port that were fewer than 64 bytes long.
Rx Overrun
Number of frames received by the port that were valid but were longer than
detected an error.
1518 bytes. This statistic does not include jumbo packets with valid CRCs.
transmit-errors
Tx Crc
Number of frames transmitted by the port that had the correct length but
contained an invalid FCS value.
Tx Short
Number of frames transmitted by the port that were fewer than 64 bytes
Tx Fragment
Total number of frames transmitted that were less than 64 octets long and
long.
had invalid CRCs.
collisions
Tx Abort
Single Coll
Multiple Coll
Excessive Coll
Total Coll
receive-etherstats Rx 64
52
Rx 127
Number of packets received that were from 65 through 127 bytes long.
Rx 255
Number of packets received that were from 128 through 255 bytes long.
Rx 511
Number of packets received that were from 256 through 511 bytes long.
Rx 1023
Number of packets received that were from 512 through 1023 bytes long.
Rx 1518
Number of packets received that were from 1024 through 1518 bytes long.
Port Commands
Field
Description
transmit-etherstat
Tx 64
Tx 127
Number of packets transmitted that were from 65 through 127 bytes long.
Tx 255
Number of packets transmitted that were from 128 through 255 bytes long.
Tx 511
Number of packets transmitted that were from 256 through 511 bytes long.
Tx 1023
Number of packets transmitted that were from 512 through 1023 bytes
long.
Tx 1518
Number of packets transmitted that were from 1024 through 1518 bytes
long.
reset port
Usage Resets a port by toggling the link state and Power over Ethernet (PoE) state.
The reset command disables the port link and PoE (if applicable) for at least 1 second, then reenables
them. This behavior is useful for forcing an MP that is connected to two MX switches to reboot over the link
to the other WLC.
Syntax reset port port-list
List of physical ports. MSS resets all the specified ports.
port-list
Defaults None.
Access Enabled.
set ap
Usage Configures an MP, either directly connected to the MX or indirectly connected through an
intermediate Layer 2 or Layer 3 network.
Informational Note: Before configuring a Distributed MP, you must use the set system countrycode command to
set the IEEE 802.11 country-specific regulations on the MX switch. See set system countrycode on page 32.
53
apnum
serial-id serial-ID
Radio type:
11a802.11a
11b802.11b
11g802.11g
11na802.11na
11ng802.11ng
This option applies only to single-radio models.
Defaults The default vales are the same as the defaults for the set port type ap command.
Access Enabled.
History
Version 2.0
Command introduced
Version 2.1
54
Port Commands
Version 3.0
Version 3.2
Version 4.1
Version 6.0
Version 7.0
Version 7.1
Version 7.3
Examples The following command configures MP 1 for MP model MP-372 with serial-ID 0322199999:
WLC# set ap 1 serial-id 0322199999 model mp-372
success: change accepted.
The following command removes MP 1:
WLC# clear ap 1
This will clear specified AP devices. Would you like to continue? (y/n) [n]y
See Also
clear ap on page 46
clear port type on page 48
set port type ap on page 61
set system countrycode on page 32
set port
Usage Administratively disables or reenables a port.
A port that is administratively disabled cannot send or receive packets. This command does not affect the
link state of the port.
55
disable
port-list
List of physical ports. MSS disables or reenables all the specified ports.
set port-group
Usage Configures a load-sharing port group. All ports in the group function as a single logical link.
Do not use dashes or hyphens in a port group name. If you do, MSS does not display or save the port
group.
You can configure up to 16 ports in a port group, in any combination of ports. The port numbers do not
need to be contiguous and you can use 10/100 Ethernet ports and gigabit Ethernet ports in the same port
group.
After adding a port to a port group, you cannot configure port parameters on the individual port. Instead,
change port parameters on the entire group. Specify the group name instead of an individual port name or
number in port configuration commands.
To add or remove ports in a group that is already configured, change the mode to off, add or remove the
ports, then change the mode to on.
Syntax set port-group name group-name port-list mode {on | off}
name group-name
Alphanumeric string of up to 255 characters, with no spaces. The port group name
must start with a letter.
port-list
List of physical ports. All the ports you specify are configured together as a single
logical link.
State of the group. Use on to enable the group or off to disable the group. The group
is enabled by default.
56
Port Commands
Examples The following command configures a port group named server1 containing ports 1 through 5,
and enables the link:
WLC# set port-group name server1 1-5 mode on
success: change accepted.
The following commands disable the link for port group server1, change the list of ports in the group, and
reenable the link:
WLC# set port-group name server1 1-5 mode off
success: change accepted.
WLC# set port-group name server1 1-4,7 mode on
success: change accepted.
See Also
clear port-group on page 47
show port-group on page 64
List of physical ports. MSS sets the preference on all the specified ports.
rj45
Defaults The GBIC (fiber) interface is enabled, and the copper interface is disabled, by default.
Access Enabled.
History
Version 4.0
Command introduced.
Version 7.1
Command deprecated.
57
The WLC can have one port mirroring pair (one source port and one observer port) at a time. The source
port can be a network port, MP access port, or wired authentication port. However, the observer port must
be a network port, and cannot be a member of any VLAN or port group.
Syntax set port mirror source-port observer observer-port
source-port
Number of the port whose traffic you want to analyze. You can specify only one port.
observer-port
Number of the port to copy the traffic from the source port.
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.2.
Examples The following command sets port 2 to monitor port 1 traffic:
WLC# set port 1 observer 2
See Also
clear port mirror on page 48
show port mirror on page 66
name name
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command sets the name of port 17 to adminpool:
WLC# set port 17 name adminpool
success: change accepted.
See Also
clear port name on page 48
show port status on page 68
58
Port Commands
It is recommended that you do not configure the mode of an WLC port so that one side of the link is set to
autonegotiation while the other side is set to full-duplex. Although MSS allows this configuration, it can
cause slow throughput on the link. The slow throughput occurs because the side that is configured for
autonegotiation falls back to half-duplex. A stream of large packets sent to an WLC port with this
configuration can cause forwarding on the link to stop.
Syntax set port negotiation port-list {enable | disable}
port-list
List of physical ports. MSS disables or reenables autonegotiation on all the specified
ports.
enable
disable
List of physical ports. MSS disables or reenables PoE on all the specified ports.
enable
disable
Defaults PoE is disabled on network and wired authentication ports. The state on MP ports depends on
whether you enabled or disabled PoE when setting the port type. See set port type ap on page 61.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command disables PoE on ports 7 and 9, which are connected to an MP:
WLC# set port poe 7,9 disable
59
If you are enabling power on these ports, they must be connected only to
approved PoE devices with the correct wiring. Do you wish to continue? (y/n)
[n]y
The following command enables PoE on ports 7 and 9:
WLC# set port poe 7,9 enable
If you are enabling power on these ports, they must be connected only to
approved PoE devices with the correct wiring. Do you wish to continue? (y/n)
[n]y
See Also
set port type ap on page 61
set port type wired-auth on page 62
List of physical ports. MSS sets the port speed on all the
specified ports.
10
100
1000
10000
auto
60
Port Commands
Command introduced.
Version 7.0
Examples The following command sets the port speed on ports 1, 7 through 11, and 14 to
10 Mbps and sets the operating mode to full-duplex:
WLC# set port speed 1,7-11,14 10
enable
disable
61
timeout
tag-list
One or more numbers between 1 and 4094 that subdivide a wired authentication
port into virtual ports.
num
last-resort
none
Denies authentication and prohibits the user from accessing the network over this
port.
web-portal
Serves the user a web page from the WLC nonvolatile storage for secure login to the
network.
Defaults The default tag-list is null (no tag values). The default number of sessions is 1. The default
fallthru authentication type is none. The default idle-timeout is 300 seconds.
Access Enabled.
History
Version 1.0
Command introduced.
Version 2.0
Maximum number of sessions increased from 16. You can specify as many as you
need. (There is no specific maximum.)
Version 3.0
Options added to change the fallthru authentication type. This is the authentication
type that MSS uses if the user does not support 802.1X and is not authenticated by
MAC authentication.
Version 4.0
Version 7.1
Usage You cannot set a port type if the port is a member of a port VLAN. To remove a port from a VLAN,
use the clear vlan command. To reset a port as a network port, use the clear port type command.
When you change port type, MSS applies default settings appropriate for the port type. Table 7 lists the
default settings that MSS applies when you set a port type to ap.
62
Port Commands
For 802.1X clients, wired authentication works only if the clients are directly attached to the wired
Table 7.Wired Authentication Port Defaults
Port Parameter
Setting
VLAN membership
Removed from all VLANs. You cannot assign an MP access port to a VLAN. MSS
automatically assigns MP access ports to VLANs based on user traffic.
Not applicable
802.1X
Port groups
Not applicable
IGMP snooping
1 (one).
None.
authentication port, or are attached through a hub that does not block forwarding of packets from the
client to the PAE group address (01:80:c2:00:00:03). Wired authentication works in accordance with
the 802.1X specification, which prohibits a client from sending traffic directly to an authenticator MAC
address until the client is authenticated. Instead of sending traffic to the authenticator MAC address,
the client sends packets to the PAE group address. The 802.1X specification prohibits networking
devices from forwarding PAE group address packets, because this would make it possible for multiple
authenticators to acquire the same client.
For non-802.1X clients, who use MAC authentication, WebAAA, or last-resort authentication, wired
authentication works if the clients are directly attached or indirectly attached.
Examples The following command sets port 10 for a wired authentication user:
WLC# set port type wired-auth 10
success: change accepted
Examples The following command sets port 7 for a wired authentication user and specifies a maximum
of three simultaneous user sessions:
WLC# set port type wired-auth 7 max-sessions 3
success: change accepted
See Also
clear port type on page 48
set port type ap on page 61
63
packets
receive-errors
transmit-errors
collisions
receive-etherstats
List of physical ports. If you do not specify a port list, MSS displays statistics
for all ports.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Usage You can specify one statistic type with the command.
Examples The following command shows octet statistics for port 3:
WLC> show port counters octets port 3
Port
Status
Rx Octets
Tx Octets
=============================================================================
3
Up
27965420
34886544
This commands output has the same fields as the monitor port counters command. For descriptions of
the fields, see Table 6 on page 52.
See Also
clear port counters on page 46
monitor port counters on page 49
show port-group
Displays port group information.
Syntax show port-group [name group-name]
name group-name
Defaults None.
Access All.
History
64
Version 1.0
Command introduced.
Version 4.2
Option all removed for simplicity. You can display information for all groups by
entering the command without specifying a group name.
Port Commands
Examples The following command displays the configuration of port group server2:
WLC# show port-group name server2
Port group: server2 is up
Ports:
15, 17
Description
Port group
Ports
See Also
clear port-group on page 47
set port-group on page 56
port-list
Defaults None.
Access All.
History Introduced in MSS Version 4.0.
Version 4.0
Command introduced.
Version 7.1
Command deprecated.
Media Type
===========================================================
1
GBIC
RJ45
GBIC
GBIC
65
Description
Port
Port number.
Preference
Preference setting:
GBICThe GBIC (fiber) interface is enabled.
RJ45The RJ-45 (copper) interface is enabled.
See Also
clear port media-type (deprecated) on page 47
set port media-type(deprecated) on page 57
port-list
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays PoE information for all ports on a 22-port MX:
WLC# show port poe
Link
Port
66
Name
Port
Status
PoE
Type
PoE
config
Draw(Watts)
Copyright 2011, Juniper Networks, Inc.
Port Commands
==============================================================================
1
up
disabled
off
down
disabled
off
down
disabled
off
down
disabled
off
down
disabled
off
down
disabled
off
down
disabled
off
down
disabled
off
up
MP
enabled
1.44
10
10
up
disabled
off
11
11
down
disabled
off
12
12
down
disabled
off
13
13
down
disabled
off
14
14
down
disabled
off
15
15
down
disabled
off
16
16
down
disabled
off
17
17
down
disabled
off
18
18
down
disabled
off
19
19
down
disabled
off
20
20
down
disabled
off
21
21
down
disabled
invalid
22
22
down
disabled
invalid\
Description
Port
Port number.
Name
Port name. If the port does not have a name, the port number is listed.
Link status
Port type
Port type:
MPThe port is an MP access port.
- (The port is not an MP access port.)
PoE config
PoE state:
enabled
disabled
PoE Draw
67
port-list
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays information for all ports on a 22-port MX switch:
WLC# show port status
Port
Name
Admin
Oper
Config
Actual
Type
Media
==============================================================================
68
1 1
10/100BaseTx
up
up
auto
100/full
network
2 2
10/100BaseTx
up
down
auto
network
3 3
10/100BaseTx
up
down
auto
network
4 4
10/100BaseTx
up
down
auto
network
5 5
10/100BaseTx
up
down
auto
network
6 6
10/100BaseTx
up
down
auto
network
7 7
10/100BaseTx
up
down
auto
network
8 8
10/100BaseTx
up
down
auto
network
9 9
10/100BaseTx
up
up
auto
100/full
ap
10 10
10/100BaseTx
up
up
auto
100/full
network
11 11
10/100BaseTx
up
down
auto
network
12 12
10/100BaseTx
up
down
auto
network
Port Commands
13 13
10/100BaseTx
up
down
auto
network
14 14
10/100BaseTx
up
down
auto
network
15 15
10/100BaseTx
up
down
auto
network
16 16
10/100BaseTx
up
down
auto
network
17 17
10/100BaseTx
up
down
auto
network
18 18
10/100BaseTx
up
down
auto
network
19 19
10/100BaseTx
up
down
auto
network
20 20
10/100BaseTx
up
down
auto
network
21 21
connector
up
down
auto
network
no
22 22
connector
up
down
auto
network
no
Description
Port
Port number.
Name
Port name. If the port does not have a name, the port number is listed.
Admin
Oper
Actual
Type
Port type:
apMP port
networkNetwork port
waWired authentication port
69
Description
Media
Link type:
10/100BaseTX10/100BASE-T.
GBIC1000BASE-SX or 1000BASE-LX GBIC.
1000BaseT1000BASE-T.
No connectorGBIC slot is empty.
See Also
clear port type on page 48
set port on page 55
set port name on page 58
set port negotiation on page 58
set port speed on page 60
set port type ap on page 61
set port type wired-auth on page 62
70
Port Commands
71
72
Port Commands
73
74
VLAN Commands
Use virtual LAN (VLAN) commands to configure and manage parameters for individual port
VLANs on network ports, and to display information about clients roaming within a mobility
domain. This chapter presents VLAN commands alphabetically. Use the following table to locate
commands in this chapter based on use.
Creation
Ports
Restriction of Client
Layer 2 Forwarding
Tunnel Affinity
FDB Entries
clear fdb
Deletes an entry from the forwarding database (FDB).
75
Clears permanent entries. A permanent entry does not age out and remains
in the database even after a reboot, reset, or power cycle. You must specify
a VLAN name or number with this option.
static
Clears static entries. A static entry does not age out, but is removed from the
database after a reboot, reset, or power cycle. You must specify a VLAN
name or number with this option.
system
Clears system entries from the FDB. You must specify a VLAN name or
number with this option.
dynamic
mac-addr
Clears MAC addresses from the FDB. You must specify a MAC address in
the format a:b:c:d:e:f or a-b-c-d-e-f.
port port-list
Clears dynamic entries that match destination ports in the port list. You are
not required to specify a VLAN name or number with this option.
vlan vlan-id
tag tag-value
VLAN tag value that identifies a virtual port. If you do not specify a tag value,
MSS deletes only entries that match untagged interfaces. Specifying a tag
value deletes entries that match only the specified tagged interface.
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced.
Usage You can delete forwarding database entries based on entry type, port, or VLAN. A VLAN
name or number is required for deleting permanent or static entries.
Examples The following command clears all static forwarding database entries that match VLAN
blue:
WLC# clear fdb static vlan blue
success: change accepted.
The following command clears all dynamic forwarding database entries that match all VLANs:
WLC# clear fdb dynamic
success: change accepted.
76
VLAN Commands
The following command clears all dynamic forwarding database entries that match ports 3 and 5:
WLC# clear fdb port 3,5
success: change accepted.
See Also
set fdb on page 80
show fdb on page 85
permit-mac
mac-addr
[mac-addr]
List of MAC addresses. MSS no longer allows clients in the VLAN to send
traffic to the MAC addresses at Layer 2.
all
Defaults If you do not specify a list of MAC addresses or all, all addresses are removed.
Access Enabled.
History Introduced in MSS Version 4.1.
Usage If you clear all MAC addresses, Layer 2 forwarding is no longer restricted in the VLAN.
Clients within the VLAN can communicate directly.
There can be a slight delay before functions such as pinging between clients become available
again after Layer 2 restrictions are lifted. Even though packets are passed immediately once Layer
2 restrictions are gone, it can take 10 seconds or more for upper-layer protocols to update their
ARP caches and regain their functionality.
To clear the statistics counters without removing any MAC addresses, use the clear security
l2-restrict counters command instead.
Examples The following command removes MAC address aa:bb:cc:dd:ee:ff from the list of
addresses that clients in VLAN abc_air are allowed to send traffic at Layer 2:
WLC# clear security l2-restrict vlan abc_air permit-mac
aa:bb:cc:dd:ee:ff
success: change accepted.
See Also
clear security l2-restrict counters on page 78
set security l2-restrict on page 81
show security l2-restrict on page 89
77
all
Defaults If you do not specify a VLAN or all, counters for all VLANs are cleared.
Access Enabled.
History Introduced in MSS Version 4.1.
Usage To clear MAC addresses from the list of addresses that clients are allowed to send data,
use the clear security l2-restrict command instead.
Examples The following command clears Layer 2 forwarding restriction statistics for VLAN
abc_air:
WLC# clear security l2-restrict counters vlan abc_air
success: change accepted.
See Also
clear security l2-restrict on page 77
set security l2-restrict on page 81
show security l2-restrict on page 89
clear vlan
Removes physical or virtual ports from a VLAN or removes a VLAN entirely.
Warning: When you remove a VLAN, MSS completely removes the VLAN from the configuration and also
removes all configuration information for that VLAN. If you want to remove only a specific port from the VLAN,
make sure you specify the port number in the command.
When you remove a VLAN, MSS completely removes the VLAN from the configuration and also removes
all configuration information for that VLAN. If you want to remove only a specific port from the VLAN, make
sure you specify the port number in the command.
Syntax clear vlan vlan-id [port port-list [tag tag-value]]
vlan-id
port port-list
List of physical ports. MSS removes the specified ports from the VLAN. If
you do not specify a list of ports, MSS removes the VLAN entirely.
tag tag-value
Tag number that identifies a virtual port. MSS removes only the specified
virtual port from the specified physical ports.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
78
VLAN Commands
Usage If you do not specify a port-list, the entire VLAN is removed from the configuration.
Informational Note: You cannot delete the default VLAN but you can remove ports from it. To remove
ports from the default VLAN, use the port port-list option.
clear vlan-profile
Removes a VLAN profile or individual entries from a VLAN profile.
Syntax clear vlan-profile profile-name [vlan vlan-name]
profile-name
vlan-name
Defaults None.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage A VLAN profile lists the VLANs that locally switch traffic by MPs where the VLAN profile is
applied. Use this command to remove individual VLANs from a VLAN profile, or to remove an
entire VLAN profile. If you remove all of the entries from a VLAN profile, the VLAN profile is
removed.
If a VLAN profile is changed so that traffic that had been tunneled to an WLC is now locally
switched by MPs, or vice-versa, the sessions of clients associated with the MPs where the VLAN
profile is applied are terminated, and the clients must re-associate with the MPs.
Examples The following command removes the entry for VLAN red from VLAN profile locals:
WLC# clear vlan-profile locals vlan red
Copyright 2011, Juniper Networks, Inc.
79
WLC#
The following command removes VLAN profile locals:
WLC# clear vlan-profile locals
WLC#
See Also
set ap local-switching vlan-profile on page 280
set vlan-profile on page 84
show vlan-profile on page 92
set fdb
Adds a permanent or static entry to the forwarding database.
Syntax set fdb {perm | static} mac-addr port port-list
vlan vlan-id [tag tag-value]
perm
Adds a permanent entry. A permanent entry does not age out and remains in
the database even after a reboot, reset, or power cycle.
static
Adds a static entry. A static entry does not age out, but is removed from the
database after a reboot, reset, or power cycle.
mac-addr
Destination MAC address of the entry. Use colons to separate the octets (for
example, 00:11:22:aa:bb:cc).
port port-list
List of physical destination ports for which to add the entry. A separate entry
is added for each port you specify.
vlan vlan-id
tag tag-value
VLAN tag value that identifies a virtual port. You can specify a number from
1 through 4093. If you do not specify a tag value, an entry is created for an
untagged interface only. If you specify a tag value, an entry is created only
for the specified tagged interface.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You cannot add a multicast or broadcast address as a permanent or static FDB entry.
Examples The following command adds a permanent entry for MAC address 00:11:22:aa:bb:cc on
ports 3 and 5 in VLAN blue:
WLC# set fdb perm 00:11:22:aa:bb:cc port 3,5 vlan blue
success: change accepted.
The following command adds a static entry for MAC address 00:2b:3c:4d:5e:6f on port 1 in the
default VLAN:
WLC# set fdb static 00:2b:3c:4d:5e:6f port 1 vlan default
80
VLAN Commands
VLAN name or number. The timeout period change applies only to entries
that match the specified VLAN.
age seconds
Value for the timeout period, in seconds. You can specify a value from 0
through 1,000,000. If you change the timeout period to 0, aging is disabled.
mode
{enable | disable}
permit-mac mac-addr
[mac-addr]
81
Usage You can specify multiple addresses by listing them on the same command line or by
entering multiple commands. To change a MAC address, use the clear security l2-restrict
command to remove it, and then use the set security l2-restrict command to add the correct
address.
Restriction of client traffic does not begin until you enable the permitted MAC list. Use the mode
enable option with this command.
Examples The following command restricts Layer 2 forwarding of client data in VLAN abc_air to
the default routers with MAC address aa:bb:cc:dd:ee:ff and 11:22:33:44:55:66:
WLC# set security l2-restrict vlan abc_air mode enable permit-mac
aa:bb:cc:dd:ee:ff 11:22:33:44:55:66
success: change accepted.
See Also
clear security l2-restrict on page 77
clear security l2-restrict counters on page 78
show security l2-restrict on page 89
name
Defaults VLAN 1 is named default by default. No other VLANs have default names.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You must assign a name to a VLAN (other than the default VLAN) before you can add
ports to the VLAN.
It is recommended that you do not use the name default. This name is already used for VLAN 1. It
is also recommended that you do not rename the default VLAN.
You cannot use a number as the first character in the VLAN name. It is recommended that you do
not use the same name with different capitalizations for VLANs. For example, do not configure two
separate VLANs with the names red and RED.
VLAN names are case-sensitive for RADIUS authorization when a client roams to an WLC. If the
switch is not configured with the VLAN of the client, but is configured with a VLAN with the same
spelling but different capitalization, authorization for the client fails. For example, if the client is on
VLAN red but the WLC to which the client roams has VLAN RED instead, RADIUS authorization
fails.
Examples The following command assigns the name marigold to VLAN 3:
WLC# set vlan 3 name marigold
success: change accepted.
82
VLAN Commands
port port-list
tag tag-value
Tag value that identifies a virtual port. You can specify a value from 1
through 4093.
Defaults By default, no ports are members of any VLANs. An MX cannot forward traffic on the
network until you configure VLANs and add network ports to the VLANs.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You can combine this command with the set port name command to assign the name and
add the ports at the same time.
If you do not specify a tag value, the MX sends untagged frames for the VLAN. If you do specify a
tag value, the WLC sends tagged frames only for the VLAN.
If you do specify a tag value, it is recommended to use the same value as the VLAN number. MSS
does not require the VLAN number and tag value to be the same but it can be required by devices
from other vendors.
Examples The following command assigns the name beige to VLAN 11 and adds ports 1 through
3 to the VLAN:
WLC# set vlan 11 name beige port 1-3
success: change accepted.
The following command adds port 16 to VLAN beige and assigns tag value 86 to the port:
WLC# set vlan beige port 16 tag 86
success: change accepted.
See Also
clear vlan on page 78
set vlan name on page 82
show vlan config on page 91
83
affinity
Preference of this WLC for forwarding user traffic for the VLAN. You can
specify a value from 1 through 10. A higher number indicates a greater
preference.
Defaults Each VLAN on a WLC network port has an affinity value of 5 by default.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage Increasing a WLC affinity value increases the preferability of the WLC for forwarding user
traffic for the VLAN.
If more than one MX has the highest affinity value, MSS randomly selects one of the switches for
the tunnel.
Examples The following command changes the VLAN affinity for VLAN beige to 10:
WLC# set vlan beige tunnel-affinity 10
success: change accepted.
See Also
show roaming vlan on page 89
show vlan config on page 91
set vlan-profile
Configures entries in a VLAN profile that can be applied to an MP for local switching.
Syntax set vlan-profile profile-name vlan vlan-name [mode
{overlay|local-switching} [tag tag-value]
profile-name
vlan-name
Name of a VLAN.
mode
tag-value
Optional tag value associated with the VLAN. When this value is set, it is
used as the 802.1Q tag for the VLAN.
Defaults If local switching is enabled on an MP, but no VLAN profile is configured, then a default
VLAN profile is used. The default VLAN profile includes a single VLAN named default that is
untagged.
Access Enabled.
History Introduced in MSS Version 6.0.
84
Version 6.0
Command introduced.
Version 7.1
VLAN Commands
Usage A VLAN profile consists of a list of VLANs and tags. When a VLAN profile is applied to an
MP, traffic for the VLANs specified in the VLAN profile is locally switched by the MP instead of
being tunneled back to an WLC.
You enter a separate set vlan-profile command for each VLAN you want to add to the VLAN
profile. A VLAN profile can contain up to 128 entries.
Examples The following command adds an entry for VLAN red to VLAN profile locals:
WLC# set vlan-profile locals vlan red
success: change accepted.
See Also
set ap local-switching vlan-profile on page 280
clear vlan-profile on page 79
show vlan-profile on page 92
show fdb
Displays entries in the forwarding database.
Syntax show fdb [mac-addr-glob [vlan vlan-id]]
show fdb {perm | static | dynamic | system | all} [port port-list | vlan vlan-id]
mac-addr-glob
vlan vlan-id
perm
Displays permanent entries. A permanent entry does not age out and
remains in the database even after a reboot, reset, or power cycle.
static
Displays static entries. A static entry does not age out, but is removed from
the database after a reboot, reset, or power cycle.
dynamic
system
Displays system entries. A system entry is added by MSS. For example, the
authentication protocols can add entries for wired and wireless
authentication users.
all
Displays all entries in the database, or all the entries that match a particular
port or ports or a particular VLAN.
port port-list
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Usage To display the entire forwarding database, enter the show fdb command without options.
To display only a portion of the database, use optional parameters to specify the types of entries to
display.
Copyright 2011, Juniper Networks, Inc.
85
Examples The following command displays all entries in the forwarding database:
WLC# show fdb all
* = Static Entry. + = Permanent Entry. # = System Entry.
VLAN TAG
Type]
Destination Ports
[Protocol
00:01:97:13:0b:1f
aa:bb:cc:dd:ee:ff
00:0b:0e:02:76:f5
[ALL]
[ALL]
[ALL]
Destination Ports
[Protocol
00:01:97:13:0b:1f
[ALL]
00:0b:0e:02:76:f5
[ALL]
Description
VLAN
VLAN number.
TAG
VLAN tag value. If the interface is untagged, the TAG field is blank.
CoS
Type of entry. The entry types are explained in the first row of the command output.
This Class of Service (CoS) value is not associated with MSS quality of service (QoS)
features.
Destination Ports
MX port associated with the entry. A WLC sends traffic to the destination MAC address
through this port.
Protocol Type
Displayed
See Also
clear fdb on page 75
set fdb on page 80
86
VLAN Commands
VLAN name or number. If you do not specify a VLAN, the aging timeout
period for each VLAN is displayed.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays the aging timeout period for all VLANs:
WLC# show fdb agingtime
VLAN 2 aging time = 600 sec
VLAN 1 aging time = 300 sec
Because the forwarding database aging timeout period can be configured on an individual VLAN
basis, the command lists the aging timeout period for each VLAN separately.
See Also set fdb agingtime on page 81
Lists the number of permanent entries. A permanent entry does not age out
and remains in the database even after a reboot, reset, or power cycle.
static
Lists the number of static entries. A static entry does not age out, but is
removed from the database after a reboot, reset, or power cycle.
dynamic
vlan vlan-id
VLAN name or number. Entries are listed for only the specified VLAN.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command lists the number of dynamic entries that the forwarding
database contains:
WLC# show fdb count dynamic
Total Matching Entries = 2
See Also show fdb on page 85
87
peer ip-addr
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 4.0
Station Address
VLAN
State
10.10.10.5
violet
Up
Description
User Name
Name of the user. This is the name used for authentication. The name resides in a RADIUS
server database or the local user database on an MX.
Station Address
VLAN
Name of the VLAN that the RADIUS server or MX local user database assigned the user.
State
88
VLAN Commands
192.168.14.2
vlan-eng
192.168.14.4
vlan-fin
192.168.14.2
vlan-it
192.168.14.4
vlan-it
192.168.14.2
vlan-pm
192.168.14.2
vlan-sm
192.168.14.2
vlan-tp
192.168.14.4
vlan-tp
192.168.14.2
Description
VLAN
VLAN name.
WLC
Affinity
Preference of this WLC for forwarding user traffic for the VLAN. A
higher number indicates a greater preference.
See Also
show roaming station on page 87
show vlan config on page 91
all
89
Defaults If you do not specify a VLAN name or all, information is displayed for all VLANs.
Access Enabled.
History Introduced in MSS Version 4.1.
Examples The following command shows Layer 2 forwarding restriction information for all VLANs:
WLC# show security l2-restrict
VLAN Name
En Drops
Permit MAC
Hits
2 vlan-2
0 00:0b:0e:02:53:3e
5947
00:30:b6:3e:5c:a8
0 04:04:04:04:04:04
Description
VLAN
VLAN number.
Name
VLAN name.
En
Drops
Number of packets dropped because the destination MAC address is not one of the
addresses listed under Permit MAC.
Permit MAC
MAC addresses that clients in the VLAN are allowed to send traffic at Layer 2.
Hits
Number of packets with the source MAC address of a client in this VLAN, and the
destination MAC address was one of those listed under Permit MAC.
See Also
clear security l2-restrict on page 77
clear security l2-restrict counters on page 78
set security l2-restrict on page 81
show tunnel
Displays the tunnels from the WLC where you type the command.
Syntax show tunnel
Defaults None.
Access Enabled
History Introduced in MSS Version 1.0.
Examples To display all tunnels from an MX to other switches in the Mobility Domain, type the
following command.
WLC# show tunnel
VLAN
90
Local Address
Remote Address
State
Port
LVID
RVID
VLAN Commands
192.168.14.2
192.168.14.4
DORMANT
1024
4096
Description
VLAN
VLAN name.
Local Address
IP address of the local end of the tunnel. This is the WLC IP address where you enter
Remote Address
IP address of the remote end of the tunnel. This is the system IP address of another
the command.
MX in the mobility domain.
State
Tunnel state:
Up
Dormant
Port
LVID
RVID
VLAN name or number. If you do not specify a VLAN, information for all
VLANs is displayed.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays information for VLAN burgundy:
WLC# show vlan config burgundy
Admin
VLAN Name
VLAN
Tunl
Port
Tag
State
Up
Up
5
2
none Up
none Up
none Up
none Up
91
11
none Up
t:10.10.40.4
none Up
Description
VLAN
VLAN number.
Name
VLAN name.
Admin Status
VLAN State
Tunl Affin
Port
Member port of the VLAN. The port can be a physical port or a virtual port.
Physical ports are 10/100 Ethernet or gigabit Ethernet ports on the switch, and are
listed by port number.
Virtual ports are tunnels to other switches in a mobility domain, and are listed as
follows: t:ip-addr, where ip-addr is the system IP address of the MX switch at the
other end of the tunnel.
This field can include MP access ports and wired authentication ports, because MSS
dynamically adds these ports to a VLAN when handling user traffic for the VLAN.
Tag
Port State
See Also
clear vlan on page 78
set vlan name on page 82
set vlan port on page 83
set vlan tunnel-affinity on page 83
show vlan-profile
Displays the contents of the VLAN profiles configured on the WLC. A VLAN profile lists the VLANs
that traffic is locally switched by MPs with the VLAN profile.
Syntax show vlan-profile [profile-name]
profile-name
Defaults If a profile-name is not specified, the contents of all VLAN profiles configured on the WLC
switch are displayed.
Access All.
History Introduced in MSS Version 6.0.
92
VLAN Commands
Examples The following command displays the contents of VLAN profile locals:
WLC# show vlan-profile locals
vlan-profile: locals
AP list: 1,2,3
Vlan Name
Tag
---------
---
blue
none
red
45
ap numbers: 67
Table 18 describes the fields in the show vlan-profile output.
Table 18.Output for show vlan-profile
Field
Description
vlan-profile
Vlan Name
Mode
ap numbers
The index numbers of the APs where this VLAN profile is applied.
See Also
set ap local-switching vlan-profile on page 280
clear vlan-profile on page 79
set vlan-profile on page 84
93
94
QoS Settings
Updated
Updated
clear qos
Resets the WLC mapping of Differentiated Services Code Point (DSCP) values to internal QoS
values.
The WLC internal QoS map ensures that prioritized traffic remains prioritized while transiting the
WLC. An WLC uses the QoS map to do the following:
Classify inbound packets by mapping the DSCP values to one of eight internal QoS values
Classify outbound packets by marking the DSCP values based on the WLC internal QoS values
Syntax clear qos
[cos-to-dscp-map [from-qos] | dscp-to-cos-map [from-dscp]| [flow sip-data]|
[traffic-class voip-data]]
cos-to-dscp-map
[from-qos]
Resets the mapping between the specified internal QoS value and the
DSCP values with which MSS marks outbound packets.
QoS values are from 0 to 7.
dscp-to-cos-map
[from-dscp]
Resets the mapping between the specified range of DSCP values and
internal QoS value with which MSS classifies inbound packets.
95
flow
sip-data
traffic-class
voip-data
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.1.
MSS Version 4.1
Introduced
Usage To reset all mappings to the default values, use the clear qos command without the
optional parameters.
Examples The following command resets all QoS mappings:
WLC# clear qos
success: change accepted.
The following command resets the mapping used to classify packets with DSCP value 44:
WLC# clear qos dscp-to-qos-map 44
success: change accepted.
clear qos-profile
Clears a QoS profile from the configuration.
Syntax clear qos-profile profile-name
Defaults None
Access Enabled
History Introduced in MSS Version 6.2.
Examples To clear a QoS profile with the profile name, best_voice, from the MSS configuration,
use the following command:
WLC# clear qos-profile best_voice
success: change accepted
96
level
dscp dscp-value
DSCP value. You can specify the value as a decimal number. Valid
values are 0 to 63.
DSCP range. You can specify the values as decimal numbers. Valid
decimal values are 0 to 63.
To specify a range, use the following format: 40-56. Specify the lower
number first.
cos level
97
set qos-profile
Configures QoS parameters to apply to multiple clients.
Syntax set qos-profile profile-name [access-category background | best effort
| video | voice]|[cos static-cos-value][max-bandwidth
max-bw-kb][use-client-dscp enable | disable] trust-client-dscp [enable |
disable]
profile-name
access-category
background
best-effort
video
voice
Mark QoS traffic with a specific CoS value from 0 to 7.
cos
static-cos-value
max-bandwidth
max-bw-kb
trust-client-dscp
{enable|disable }
Configure the bandwidth for the QoS profile. You can configure it as 1 to
100000 Kbps with 0 as unlimited bandwidth.
Allows the WLC to use the client DSCP for radio ingress traffic and ignore
WMM.
Defaults None
Access Enabled
History Command introduced in MSS Version 6.2.
Version 6.2
98
Command introduced.
Version 7.1
Version 7.3
show qos
Displays the WLC QoS settings.
Syntax show qos [default]
default
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.1.
Examples The following command displays the default QoS settings:
WLC# show qos default
Ingress QoS Classification Map (dscp-to-cos)
Ingress DSCP
CoS Level
========================================================================
00-09
10-19
20-29
30-39
40-49
50-59
60-63
========================================================================
=======
Egress DSCP
56
Egress ToS byte
0xE0
16
24
32
40
48
0x00
0x20
0x40
0x60
0x80
0xA0
0xC0
99
TOS
hex
dec
precedence
tos
hex
----------------------------------------------0
0x00
0x00
0x01
0x04
0x02
0x08
0x3f
252
0xfc
14
...
63
100
IP Services Commands
Use IP services commands to configure and manage IP interfaces, management services, the
Domain Name Service (DNS), Network Time Protocol (NTP), aliases, and to ping a host or trace a
route. This chapter presents IP services commands alphabetically. Use the following table to
locate commands in this chapter based on their use.
IP Interface
New
Updated
New
IP Route
Updated
Telnet Management
HTTPS Management
DNS
101
IP Alias
NTP
ARP
SNMP
Updated
102
IP Services Commands
Telnet client
Traceroute
DHCP server
clear interface
Removes an IP interface.
Syntax clear interface vlan-id ip
vlan-id
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage If the interface you want to remove is configured as the system IP address, removing the
address can interfere with system tasks using the system IP address, including the following:
Mobility domain operations
Topology reporting for dual-homed MPs
Default source IP address used in unsolicited communications such as AAA accounting reports
and SNMP traps
Examples The following command removes the IP interface configured on VLAN mauve:
WLC# clear interface mauve ip
success: cleared ip on vlan mauve
See Also
set interface on page 113
set interface status on page 117
show interface on page 149
ipaddr
Defaults None
Copyright 2011, Juniper Networks, Inc.
103
Access Enabled
History Added in MSS 7.1
Examples To clear 172.21.25.1 on the VLAN fast1 from the security destination, use the following
command:
WLC# clear interface fast1 ip security destination 172.21.25.1
success: change accepted.
clear ip alias
Removes an alias, which is a string that represents an IP address.
Syntax clear ip alias name
name
Alias name.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command removes the alias server1:
WLC# clear ip alias server1
success: change accepted.
See Also
set ip alias on page 117
show ip alias on page 150
104
IP Services Commands
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command removes DNS server 10.10.10.69 from an MX configuration:
WLC# clear ip dns server 10.10.10.69
success: change accepted.
See Also
clear ip dns domain on page 104
set ip dns on page 118
set ip dns domain on page 118
set ip dns server on page 119
show ip dns on page 151
clear ip route
Removes a route from the IP route table.
Syntax clear ip route {default | ip-addr mask | ip-addr/mask-length} default-router
default
Default route.
default is an alias for IP address 0.0.0.0/0.
ip-addr mask
ip-addr/mask-length
default-router
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 1.1
mask and /mask-length options added. These options are required in MSS
version 1.1.
default-router option added, because MSS 1.1 supports multiple routes to
the same destination. This option is required in MSS version 1.1.
105
Examples The following command removes the route to destination 10.10.10.68/24 through router
10.10.10.1:
WLC# clear ip route 10.10.10.68/24 10.10.10.1
success: change accepted.
See Also
set ip route on page 121
show ip route on page 153
clear ip telnet
Resets the Telnet server TCP port number to the default value. An MX listens for Telnet
management traffic on the Telnet server port.
Syntax clear ip telnet
Defaults The default Telnet port number is 23.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command resets the TCP port number for Telnet management traffic to its
default:
WLC# clear ip telnet
success: change accepted.
See Also
set ip https server on page 120
set ip telnet on page 124
set ip telnet server on page 125
show ip https on page 152
show ip telnet on page 154
all
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command removes NTP server 192.168.40.240 from an MX
configuration:
WLC# clear ntp server 192.168.40.240
106
IP Services Commands
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command clears community string setswitch2:
WLC# clear snmp community name setswitch2
success: change accepted.
See Also
set snmp community on page 127
107
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command clears notification profile snmpprof_rfdetect:
WLC# clear snmp notify profile snmpprof_rfdetect
success: change accepted.
See Also
set snmp notify profile on page 129
show snmp notify profile on page 157
notify-target-id
Defaults None.
Access Enabled.
Command introduced.
108
IP Services Commands
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command clears SNMPv3 user snmpmgr1:
WLC# clear snmp usm snmpmgr1
success: change accepted.
See Also
set snmp usm on page 138
show snmp usm on page 158
clear summertime
Clears the summertime setting from an WLC.
Syntax clear summertime
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To clear the summertime setting from an WLC, type the following command:
WLC# clear summertime
success: change accepted.
See Also
clear timezone on page 110
set summertime on page 142
set timedate on page 143
set timezone on page 144
show summertime on page 158
show timedate on page 159
show timezone on page 159
109
Warning: Clearing the system IP address disrupts the system tasks that use the address.
clear timezone
Clears the time offset for the WLC real-time clock from Coordinated Universal Time (UTC). UTC is also
know as Greenwich Mean Time (GMT).
Syntax clear timezone
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To return the WLC real-time clock to UTC, type the following command:
WLC# clear timezone
success: change accepted.
See Also
Syntax clear summertime on page 109
set summertime on page 142
set timedate on page 143
set timezone on page 144
show summertime on page 158
110
IP Services Commands
ping
Tests IP connectivity between an MX and another device. MSS sends an Internet Control
Message Protocol (ICMP) echo packet to the specified device and listens for a reply packet.
Syntax ping host [count num-packets] [dnf] [flood] [interval time]
[size size][tos tos]
[user count num-packets] [dnf] [flood] [interval time] [size size][tos tos]]
host
count num-packets
dnf
flood
interval time
size size
tos tos
Set the tos byte in the IP header. You can specify an integer from 0 to
255.
user
Defaults
count5.
dnfDisabled.
interval100 (one tenth of a second)
size56.
Access Enabled.
History
Version 1.0
Command introduced.
111
Version 3.0
Version 7.0
set arp
Adds an ARP entry to the ARP table.
Syntax set arp {permanent | static | dynamic} ip-addr mac-addr
permanent
Adds a permanent entry. A permanent entry does not age out and remains in the
database even after a reboot, reset, or power cycle.
static
Adds a static entry. A static entry does not age out, but the entry does not remain in
the database after a reboot, reset, or power cycle.
dynamic
Adds a dynamic entry. A dynamic entry is automatically removed if the entry ages
out, or after a reboot, reset, or power cycle.
ip-addr
mac-addr
MAC address to map to the IP address. Use colons to separate the octets (for
example, 00:11:22:aa:bb:cc).
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command adds a static ARP entry that maps IP address 10.10.10.1 to MAC
address 00:bb:cc:dd:ee:ff:
WLC# set arp static 10.10.10.1 00:bb:cc:dd:ee:ff
success: added arp 10.10.10.1 at 00:bb:cc:dd:ee:ff on VLAN 1
See Also
set arp agingtime on page 113
112
IP Services Commands
Number of seconds an entry can remain unused before MSS removes the entry. You
can specify from 0 through 1,000,000. To disable aging, specify 0.
set interface
Configures an IP interface on a VLAN.
Syntax set interface vlan-id ip {ip-addr mask | ip-addr/mask-length}
vlan-id
ip-addr mask
ip-addr/mask-length
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You can assign one IP interface to each VLAN.
113
If an interface is already configured on the specified VLAN, this command replaces the interface. If
you replace an interface in use as the system IP address, replacing the interface can interfere with
system tasks that use the system IP address, including the following:
Mobility domain operations
Topology reporting for dual-homed MPs
Default source IP address used in unsolicited communications such as AAA accounting reports
and SNMP traps
Examples The following command configures IP interface 10.10.10.10/24 on VLAN default:
WLC# set interface default ip 10.10.10.10/24
success: set ip address 10.10.10.10 netmask 255.255.255.0 on vlan
default
The following command configures IP interface 10.10.20.10 255.255.255.0 on VLAN mauve:
WLC# set interface mauve ip 10.10.20.10 255.255.255.0
success: set ip address 10.10.20.10 netmask 255.255.255.0 on vlan mauve
See Also
clear interface on page 103
set interface status on page 117
show interface on page 149
enable
disable
Defaults The DHCP client is enabled by default on an unconfigured WLCR-2 when the factory
reset switch is pressed and held during power on.
The DHCP client is disabled by default on all other WLC models, and is disabled on an WLCR-2 if
it is already configured, or the factory reset switch is not pressed and held during power on.
Access Enabled.
History Introduced in MSS Version 4.0.
Usage You can enable the DHCP client on one VLAN only. You can configure the DHCP client on
more than one VLAN, but the client can be active on only one VLAN.
MSS also has a configurable DHCP server. (See set interface dhcp-server on page 115.) You
can configure a DHCP client and DHCP server on the same VLAN, but only the client or the server
can be enabled. The DHCP client and DHCP server cannot both be enabled on the same VLAN at
the same time.
114
IP Services Commands
Examples The following command enables the DHCP client on VLAN corpvlan:
WLC# set interface corpvlan ip dhcp-client enable
success: change accepted.
See Also
clear interface on page 103
show dhcp-client on page 146
show interface on page 149
enable
disable
start ip-addr1
stop ip-addr2
Command introduced
115
Version 5.0
Usage By default, all addresses except the host address of the VLAN, the network broadcast
address, and the subnet broadcast address are included in the range. If you specify the range, the
start address must be lower than the stop address, and all addresses must be in the same subnet.
The IP interface of the VLAN must be within the same subnet but is not required to be within the
range.
Specification of the DNS domain name, DNS servers, and default router are optional. If you omit
one or more of these options, the MSS DHCP server uses oath values configured elsewhere on
the switch:
DNS domain nameIf this option is not set with the set interface dhcp-server command
dns-domain option, the MSS DHCP server uses the value set by the set ip dns domain
command.
DNS serversIf these options are not set with the set interface dhcp-server command
primary-dns and secondary-dns options, the MSS DHCP server uses the values set by the
set ip dns server command.
Default routerIf this option is not set with the set interface dhcp-server command
default-router option, the MSS DHCP server can use the value set by the set ip route
command. A default route configured by set ip route can be used if the route is in the DHCP
client subnet. Otherwise, the MSS DHCP server does not specify a router address.
Examples The following command enables the DHCP server on VLAN red-vlan to serve
addresses from the 192.168.1.5 to 192.168.1.25 range:
WLC# set interface red-vlan ip dhcp-server enable start 192.168.1.5 stop
192.168.1.25
success: change accepted.
See Also
set ip dns domain on page 118
set ip dns server on page 119
show dhcp-server on page 147
IP Services Commands
Usage IPSec is a general purpose internet security protocol, and can be used for protecting layer
4 protocols, including both TCP and UDP. IPSec has an advantage over SSL and other methods
because the application does not need to be designed to use IPSec like other higher-layer protocol
that must beincorporated into the design of an application.
Examples To set the IPSec parameters, use the following command:
WLC# set interface 1 ip security destination 192.168.1.100 spi 200
encrypt-algo aes-cbc thisistheencrkey auth-algo hmac -sha1
theauthenticationkey
To enable the IPSec parameters, use the following command:
WLC# set interface <int id> ip security destination <dst_addr>
<enable|disable>
up
down
set ip alias
Configures an alias, which maps a name to an IP address. You can use aliases as shortcuts in CLI
commands.
Syntax set ip alias name ip-addr
name
ip-addr
Defaults None.
117
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command configures the alias HR1 for IP address 192.168.1.2:
WLC# set ip alias HR1 192.168.1.2
success: change accepted.
See Also
clear ip alias on page 104
show ip alias on page 150
set ip dns
Enables or disables DNS on an MX.
Syntax set ip dns {enable | disable}
enable
Enables DNS.
disable
Disables DNS.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
118
IP Services Commands
Usage To override the default domain name when entering a hostname in a CLI command, enter
a period at the end of the hostname. For example, if the default domain name is example.com,
enter chris. if the fully qualified hostname is chris and not chris.example.com.
Aliases take precedence over DNS. When you enter a hostname, MSS checks for an alias with
that name first, before using DNS to resolve the name.
Examples The following command configures the default domain name example.com:
WLC# set ip dns domain example.com
Domain name changed
See Also
clear ip dns domain on page 104
clear ip dns server on page 105
set ip dns on page 118
set ip dns server on page 119
show ip dns on page 151
primary
Defines the server as the primary server that MSS always consults first for
resolving DNS queries.
secondary
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You can configure an MX to use one primary DNS server and up to five secondary DNS
servers.
Examples The following commands configure an MX to use a primary DNS server and two
secondary DNS servers:
WLC# set ip dns server 10.10.10.50/24 primary
success: change accepted.
WLC# set ip dns server 10.10.20.69/24 secondary
success: change accepted.
WLC# set ip dns server 10.10.30.69/24 secondary
success: change accepted.
See Also
clear ip dns domain on page 104
Copyright 2011, Juniper Networks, Inc.
119
aaa
Defaults None
Access Enabled
History Introduced in MSS 7.1
Warning: If you disable the HTTPS server, Web View access to the WLC is disabled.
disable
Command introduced
Version 3.2
IP Services Commands
set ip route
Adds a static route to the IP route table.
Syntax set ip route {default | ip-addr mask | ip-addr/mask-length} default-router metric
Default route. An MX uses the default route if an explicit route is not available
for the destination.
default
IP address and subnet mask for the route destination, in dotted decimal
notation (for example, 10.10.10.10 255.255.255.0).
ip-addr/mask-length
default-router
metric
Cost for using the route. You can specify a value from 0 through
2,147,483,647. Lower-cost routes are preferred over higher-cost routes.
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 1.1
Usage MSS can use a static route only if a direct route in the route table resolves the static route. MSS
adds routes with next-hop types Local and Direct when you add an IP interface to a VLAN, if the VLAN is
available. If one of the added routes can resolve the static route, MSS can use the static route.
Before you add a static route, use the show interface command to verify that the WLC has an IP interface
in the same subnet as the next-hop router. If not, the VLAN:Interface field of the show ip route command
output shows that the route is down.
You can configure a maximum of 4 routes per destination. This includes default routes, which have
destination 0.0.0.0/0. Each route to a given destination must have a unique router address. When the route
table contains multiple default or explicit routes to the same destination, MSS uses the route with the
lowest cost. If two or more routes to the same destination have the lowest cost, MSS selects the first route
in the route table.
121
When you add multiple routes to the same destination, MSS groups the routes and lists them from
lowest cost at the top of the group to highest cost at the bottom of the group. If you add a new
route with the same destination and cost as a route already in the table, MSS places the new route
at the top of the group of routes with the same cost.
Examples The following command adds a default route that uses default router 10.5.4.1 and gives
the route a cost of 1:
WLC# set ip route default 10.5.4.1 1
success: change accepted.
The following commands add two default routes, and configure MSS to always use the route
through 10.2.4.69 when the MX interface to that default router is up:
WLC# set ip route default 10.2.4.69 1
success: change accepted.
WLC# set ip route default 10.2.4.17 2
success: change accepted.
The following command adds an explicit route from an MX to any host on the 192.168.4.x subnet
through the local router 10.5.4.2, and gives the route a cost of 1:
WLC# set ip route 192.168.4.0 255.255.255.0 10.5.4.2 1
success: change accepted.
The following command adds another explicit route, using CIDR notation to specify the subnet
mask:
WLC# set ip route 192.168.5.0/24 10.5.5.2 1
success: change accepted.
clear ip route on page 105
show interface on page 149
show ip route on page 153
disable
122
IP Services Commands
See Also
clear snmp trap receiver on page 109
set port trap on page 61
set snmp community on page 127
set snmp trap on page 138
set snmp trap receiver on page 138
show snmp configuration on page 156
set ip ssh
Changes the TCP port number on which an MX listens for Secure Shell (SSH) management traffic.
Warning: If you change the SSH port number from an SSH session, MSS immediately ends the session. To
open a new management session, you must configure the SSH client to use the new TCP port number.
port-num
Warning: If you disable the SSH server, SSH access to the MX is also disabled.
disable
123
Command introduced
Version 2.1
Usage SSH requires an SSH authentication key. You can generate one or allow MSS to generate
one. The first time an SSH client attempts to access the SSH server on an WLC, the WLC
automatically generates a 1024-byte SSH key. If you want to use a 2048-byte key instead, use the
crypto generate key ssh 2048 command to generate one.
The maximum number of SSH sessions supported on an MX is eight. If Telnet is also enabled, the
WLC can have up to eight Telnet or SSH sessions, in any combination, and one Console session.
See Also
crypto generate key on page 478
set ip ssh on page 123
set ip ssh server on page 123
set ip ssh server on page 123
set ip telnet
Changes the TCP port number that an MX listens for Telnet management traffic.
Warning: If you change the Telnet port number from a Telnet session, MSS immediately ends the session. To
open a new management session, you must Telnet to the switch with the new Telnet port number.
Warning:
124
IP Services Commands
Warning: If you disable the Telnet server, Telnet access to the MX is also disabled.
disable
Command introduced
Version 2.1
Usage The maximum number of Telnet sessions supported on an MX is eight. If SSH is also enabled, the
WLC can have up to eight Telnet or SSH sessions, in any combination, and one console session.
Examples The following command enables the Telnet server on an MX:
WLC# set ip telnet server enable
success: change accepted.
See Also
clear ip telnet on page 106
set ip https server on page 120
set ip telnet on page 124
show ip https on page 152
show ip telnet on page 154
set ntp
Enables or disables the NTP client on an MX.
Syntax set ntp {enable | disable}
enable
disable
125
Usage If NTP is configured on a system whose current time differs from the NTP server time by more than
10 minutes, convergence of the WLC time can take many NTP update intervals. It is recommended that
you set the time manually to the NTP server time before enabling NTP to avoid a significant delay in
convergence.
Examples The following command enables the NTP client:
WLC# set ntp enable
success: NTP Client enabled
See Also
clear ntp server on page 106
clear ntp update-interval on page 107
set ntp server on page 126
set ntp update-interval on page 126
show ntp on page 155
ip-addr
Defaults None.
Access Enabled.
Number of seconds between queries. You can specify from 16 through 1024 seconds.
Copyright 2011, Juniper Networks, Inc.
IP Services Commands
read-only
read-notify
notify-only
read-write
notify-read-write Allows an SNMP management application using the string to get and
set object values on the switch. The WLC also can use the string to
send notifications.
Defaults None.
Access Enabled.
127
History
Version 1.0
Command introduced.
Version 3.1
Default community strings changed from public (for read-only) and private
(for read-write) to blank.
Version 4.0
Default strings removed. There are no default strings in MSS Version 4.0.
New access types added for SNMPv3:
read-notify
notify-only
notify-read-write
Usage SNMP community strings are passed as clear text in SNMPv1 and SNMPv2c. Juniper
Networks recommends that you use strings that cannot easily be guessed by unauthorized users.
For example, do not use the well-known strings public and private.
If you are using SNMPv3, you can configure SNMPv3 users to use authentication and to encrypt
SNMP data.
Examples The following command configures the read-write community good_community:
WLC# set snmp community read-write good_community
success: change accepted.
The following command configures community string switchmgr1 with access level
notify-read-write:
WLC# set snmp community name switchmgr1 notify-read-write
success: change accepted.
See Also
clear snmp community on page 107
set ip snmp server on page 122
set snmp notify target on page 133
set snmp notify profile on page 129
set snmp protocol on page 137
set snmp usm on page 138
show snmp community on page 156
128
IP Services Commands
Usage SNMPv3 is based on SNMPv1 and SNMPv2 but with the added capability of security and
administration. The Mobility System Software has a limited implementation of SNMPv3 that has two
predefined groups: Administration and Monitoring. These roles are defined as follows:
Monitoring read access for everything but SNMP security configurations and prevents write access.
Administration read access for everything and write access for the MIBs sysName, sysContact,
sysLocation.
drop | send
Specifies the action that the SNMP engine takes with regard to the
notifications you specify with notification-type or all.
129
notification-type
130
IP Services Commands
notification-type
(cont.)
ClientDynAuthorChangeSuccessTrapsGenerated when a
RADIUS client successfully dynamically changes authorization on a
RADIUS server.
ClientIPAddrChangeTrapsGenerated when the IP address for a
client changes.ClientRoamingTrapsGenerated when a client
roams.
ClusterFailureTrapsGenerated when the cluster configuration fails
on the network.
ConfigurationsSavedTrapsGenerated when a configuration is
saved on an WLC.
CounterMeasureStartTrapsGenerated when MSS begins
countermeasures against a rogue access point.
CounterMeasureStopTrapsGenerated when MSS stops
countermeasures against a rogue access point.
DeviceFailTrapsGenerated when an event with an Alert severity
occurs.
DeviceOkayTrapsGenerated when a device returns to its normal
state.
LinkDownTrapsGenerated when the link is lost on a port.
LinkUpTrapsGenerated when the link is detected on a port.
MichaelMICFailureTrapsGenerated when two Michael message
integrity code (MIC) failures occur within 60 seconds, triggering Wi-Fi
Protected Access (WPA) countermeasures.
MobilityDomainFailBackTrapsGenerated when a primary seed
returns to primary status after a failover to a secondary seed.
MobilityDomainFailOverTrapsGenerated when a secondary
mobility domain seed becomes the primary seed when a failover
occurs on the network.
MobilityDomainJoinTrapsGenerated when the WLC switch is
initially able to contact a mobility domain seed member, or can
contact the seed member after a timeout.
MobilityDomainResiliencyStatusTrapsGenerated status
information about the cluster configuration on the network.
MobilityDomainTimeoutTrapsGenerated when a timeout occurs
after an WLC switch has unsuccessfully tried to communicate with a
seed member.
131
notification-type
(cont.)
all
Defaults A default notification profile (named default) is already configured on the WLC. All notifications in
the default profile are dropped by default.
Access Enabled.
History Introduced in MSS Version 4.0.
MSS Version 4.0
Introduced command.
Examples The following command changes the action in the default notification profile from drop to send
for all notification types:
WLC# set snmp notify profile default send all
success: change accepted.
132
IP Services Commands
The following commands create notification profile snmpprof_rfdetect, and change the action to
send for all RF detection notification types:
WLC# set snmp notify profile snmpprof_rfdetect send
RFDetectAdhocUserTraps
success: change accepted.
WLC# set snmp notify profile snmp_rfdetect send
RFDetectAdhocUserDisappearTraps
success: change accepted
WLC# set snmp notify profile snmpprof_rfdetect send
RFDetectClientViaRogueWiredAPTraps
success: change accepted.
WLC# set snmp notify profile snmpprof_rfdetect send RFDetectDoSTraps
success: change accepted.
WLC# set snmp notify profile snmpprof_rfdetect send
RFDetectAdhocUserTraps
success: change accepted.
WLC# set snmp notify profile snmpprof_rfdetect send RFDetectRogueAPTraps
success: change accepted.
WLC# set snmp notify profile snmpprof_rfdetect send
RFDetectRogueDeviceDisappearTraps
success: change accepted.
See Also
clear snmp notify profile on page 108
set ip snmp server on page 122
set snmp community on page 127
set snmp notify target on page 133
set snmp protocol on page 137
set snmp usm on page 138
show snmp notify profile on page 157
133
ID for the target. This ID is local to the WLC and does not need to
correspond to a value on the target. You can specify a number from
1 to 10.
ip-addr[:udp-port-number]
IP address of the server. You also can specify the UDP port number
to send notifications to.
username
snmp-engine-id
{ip | hex hex-string}
profile profile-name
Notification profile that the SNMP user use to specify the notification
types to send or drop.
security {unsecured |
authenticated | encrypted}
Specifies the security level, and is applicable only when the SNMP
version is usm:
unsecuredMessage exchanges are not authenticated, nor are
they encrypted. This is the default.
authenticatedMessage exchanges are authenticated, but are
not encrypted.
encryptedMessage exchanges are authenticated and
encrypted.
retries num
timeout num
134
IP Services Commands
ID for the target. This ID is local to the WLC and does not need to
correspond to a value on the target. You can specify a number from 1
to 10.
ip-addr[:udp-port-number]
IP address of the server. You also can specify the UDP port number
to send notifications to.
username
profile profile-name
security {unsecured |
authenticated | encrypted}
Specifies the security level, and is applicable only when the SNMP
version is usm:
unsecuredMessage exchanges are not authenticated, nor are
they encrypted. This is the default.
authenticatedMessage exchanges are authenticated, but are not
encrypted.
encryptedMessage exchanges are authenticated and encrypted.
ID for the target. This ID is local to the WLC and does not need to
correspond to a value on the target. You can specify a number from 1
to 10.
ip-addr[:udp-port-number]
IP address of the server. You also can specify the UDP port number
to send notifications to.
community-string
Community string.
profile profile-name
Notification profile this SNMP user will use to specify the notification
types to send or drop.
retries num
timeout num
135
ID for the target. This ID is local to the WLC and does not need to
correspond to a value on the target itself. You can specify a number
from 1 to 10.
ip-addr[:udp-port-number]
IP address of the server. You also can specify the UDP port number
to send notifications to.
community-string
Community string.
profile profile-name
Notification profile this SNMP user will use to specify the notification
types to send or drop.
ID for the target. This ID is local to the WLC and does not need to
correspond to a value on the target. You can specify a number from 1
to 10.
ip-addr[:udp-port-number]
IP address of the server. You also can specify the UDP port number
to send notifications to.
community-string
Community string.
profile profile-name
Notification profile this SNMP user will use to specify the notification
types to send or drop.
Defaults The default UDP port number on the target is 162. The default minimum required security level is
unsecured. The default number of retries is 0 and the default timeout is 2 seconds.
Access Enabled.
History Introduced in MSS Version 4.0.
Usage The inform or trap option specifies whether the MSS SNMP engine expects the target to
acknowledge notifications sent to the target by the WLC . Use inform if you want acknowledgements. Use
trap if you do not want acknowledgements. The inform option is applicable to SNMP version v2c or usm
only.
Examples The following command configures a notification target for acknowledged notifications:
WLC# set snmp notify target 1 10.10.40.9 usm inform user securesnmpmgr1
snmp-engine-id ip
success: change accepted.
This command configures target 1 at IP address 10.10.40.9. The target SNMP engine ID is based on its
address. The MSS SNMP engine sends notifications based on the default profile, and requires the target
to acknowledge receiving them.
The following command configures a notification target for unacknowledged notifications:
136
IP Services Commands
SNMPv1
v2c
SNMPv2c
usm
all
enable
disable
137
Syntax set snmp usm usm-user-name snmp-engine-id {ip ip-addr | local | hex hex-string}
access {read-only | read-notify | notify-only | read-write |
notify-read-write} auth-type {none | md5 | sha} {auth-pass-phrase string |
auth-key hex-string} encrypt-type {none | des | 3des | aes} {encrypt-pass-phrase
string | encrypt-key hex-string}
138
IP Services Commands
usm-user-name
139
Defaults No SNMPv3 users are configured by default. When you configure an SNMPv3 user, the
default access is read-only, and the default authentication and encryption types are both none.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command creates USM user snmpmgr1, associated with the local SNMP
engine ID. This user can send traps to notification receivers.
WLC# set snmp usm snmpmgr1 snmp-engine-id local
success: change accepted.
140
IP Services Commands
The following command creates USM user securesnmpmgr1, which uses SHA authentication and 3DES
encryption with passphrases. This user can send informs to the notification receiver that has engine ID
192.168.40.2.
WLC# set snmp usm securesnmpmgr1 snmp-engine-id ip 192.168.40.2 auth-type sha
auth-pass-phrase myauthpword encrypt-type 3des encrypt-pass-phrase
mycryptpword
success: change accepted.
See Also
clear snmp usm on page 109
set ip snmp server on page 122
set snmp community on page 127
set snmp group on page 129
set snmp notify target on page 133
set snmp notify profile on page 129
set snmp protocol on page 137
show snmp usm on page 158
description description
141
set summertime
Offsets the real-time clock of an WLC by +1 hour and returns it to standard time for daylight
savings time or a similar summertime period.
Syntax set summertime summername [start week weekday month hour min end week weekday
month hour min]
summername
start
week
Week of the month to start or end the time change. Valid values are first,
second, third, fourth, or last.
weekday
Day of the week to start or end the time change. Valid values are sun, mon,
tue, wed, thu, fri, and sat.
month
Month of the year to start or end the time change. Valid values are jan, feb,
mar, apr, may, jun, jul, aug, sep, oct, nov, and dec.
hour
Hour to start or end the time changea value between 0 and 23 on the
24-hour clock.
min
Minute to start or end the time changea value between 0 and 59.
end
Defaults If you do not specify a start and end time, the system implements the time change
starting at 2:00 a.m. on the first Sunday in April and ending at 2:00 a.m. on the last Sunday in
October, according to the North American standard.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You must first set the time zone with the set timezone command for the offset to work
properly without the start and end values.
Configure summertime before you set the time and date. Otherwise, the summertime adjustment
of the time makes the time incorrect, if the date is within the summertime period.
Examples To enable summertime and set the summertime time zone to PDT (Pacific Daylight
Time), type the following command:
MX-20# set summertime PDT
success: change accepted
See Also
clear summertime on page 109
clear timezone on page 110
142
IP Services Commands
IP address, in dotted decimal notation. The address must be configured as part of the
MX VLANs.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You must use an address that is configured on one of the MX VLANs.
To display the system IP address, use the show system command.
Examples The following commands configure an IP interface on VLAN taupe and configure the
interface to be the system IP address:
WLC# set interface taupe ip 10.10.20.20/24
success: set ip address 10.10.20.20 netmask 255.255.255.0 on vlan taupe
WLC# set system ip-address 10.10.20.20
success: change accepted.
See Also
clear system ip-address on page 110
set interface on page 113
show system on page 41
set timedate
Sets the time of day and date on the WLC.
143
System date:
mmmmonth.
ddday.
yyyyyear.
time hh:mm:ss
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage The day of week is automatically calculated from the day that you set. The time displayed by the
CLI after you type the command might be slightly later than the time entered due to the interval between
pressing Enter and when the CLI reads and displays the new time and date.
Configure summertime before you set the time and date. Otherwise, the summertime adjustment makes
the time incorrect, if the date is within the summertime period.
Examples The following command sets the date to March 13, 2003 and time to 11:11:12:
WLC# set timedate date feb 29 2004 time 23:58:00
Time now is:
See Also
clear summertime on page 109
clear timezone on page 110
set summertime on page 142
set timezone on page 144
show summertime on page 158
show timedate on page 159
show timezone on page 159
set timezone
Sets the number of hours, and optionally, the number of minutes, that the WLC real-time clock is offset
from Coordinated Universal Time (UTC). These values are also used by Network Time Protocol (NTP), if it
is enabled.
Syntax set timezone zonename {-hours [minutes]}
144
zonename
Time zone name of up to 32 alphabetic characters. You can use a standard name or
any name you like.
Minus time to indicate hours (and minutes) to be subtracted from UTC. Otherwise,
hours and minutes are added by default.
hours
minutes
IP Services Commands
Defaults If this command is not used, then the default time zone is UTC.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To set the time zone for Pacific Standard Time (PST), type the following command:
MX-20# set timezone PST -8
Timezone is set to 'PST', offset from UTC is -8:0 hours.
See Also
clear summertime on page 109
clear timezone on page 110
set summertime on page 142
set timedate on page 143
show summertime on page 158
show timedate on page 159
show timezone on page 159
show arp
Displays the ARP table.
Syntax show arp [ip-addr]
ip-addr
IP address.
Defaults If you do not specify an IP address, the entire ARP table is displayed.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays ARP entries:
WLC# show arp
ARP aging time: 1200 seconds
Host
HW Address
VLAN
Type
State
00:0b:0e:02:76:f5
1 DYNAMIC RESOLVED
10.5.4.53
00:0b:0e:02:76:f7
1 LOCAL
RESOLVED
Description
Number of seconds a dynamic entry can remain unused before MSS removes the entry from the
ARP table.
Host
HW Address
VLAN
145
Description
Type
Entry type:
DYNAMICEntry was learned from network traffic and ages out if unused for longer than the
ARP aging timeout.
LOCALEntry for the MX MAC address. Each VLAN has one local entry for the switch MAC
address.
PERMANENTEntry does not age out and remains in the configuration even following a
reboot.
STATICEntry does not age out but is removed after a reboot.
State
Entry state:
RESOLVINGMSS sent an ARP request for the entry and is waiting for the reply.
RESOLVEDEntry is resolved.
See Also
set arp on page 112
set arp agingtime on page 113
show dhcp-client
Displays DHCP client information for all VLANs.
Syntax show dhcp-client
Defaults None.
Access All.
History Introduced in MSS Version 4.0.
Examples The following command displays DHCP client information:
WLC# show dhcp-client
Interface:
corpvlan(4)
IF_UP
Lease Allocation:
65535 seconds
Lease Remaining:
65532 seconds
IP Address:
10.3.1.110
Subnet Mask:
255.255.255.0
Default Gateway:
10.3.1.1
DHCP Server:
10.3.1.4
DNS Servers:
10.3.1.29
mycorp.com
146
Field
Description
Interface
IP Services Commands
Description
Configuration Status
DHCP State
IF_UP
IF_DOWN
Lease Allocation
Lease Remaining
IP Address
Subnet Mask
Default Gateway
Default router (gateway) IP address received from the DHCP server. If the address is
0.0.0.0, the server did not provide an address.
DHCP Server
DNS Servers
show dhcp-server
Displays MSS DHCP server information.
Syntax show dhcp-server [interface vlan-id] [verbose]
interface vlan-id
verbose
Displays configuration and status information for the MSS DHCP server.
Defaults None.
Access All.
History Introduced in MSS Version 4.0.
Examples The following command displays the addresses leased by the MSS DHCP server:
WLC# show dhcp-server
VLAN Name
(sec)
Address
MAC
Lease Remaining
10.10.20.2
00:01:02:03:04:05
1 default
2103
10.10.20.3
00:01:03:04:06:07
2 red-vlan
102
192.168.1.5
00:01:03:04:06:08
147
2 red-vlan
16789
192.168.1.7
00:01:03:04:06:09
The following command displays configuration and status information for each VLAN that the
DHCP server is configured:
WLC# show dhcp-server verbose
Interface:
0 (Direct AP)
Status:
UP
Address Range:
10.0.0.1-10.0.0.253
Interface:
default(1)
Status:
UP
Address Range:
10.10.20.2-10.10.20.254
Hardware Address:
00:01:02:03:04:05
State:
BOUND
Lease Allocation:
43200 seconds
Lease Remaining:
12345 seconds
IP Address:
10.10.20.2
Subnet Mask:
255.255.255.0
Default Router:
10.10.20.1
DNS Servers:
10.10.20.4 10.10.20.5
mycorp.com
Description
VLAN
VLAN number.
Name
VLAN name.
Address
MAC Address
MAC address of the device that holds the lease for the address.
Lease Remaining
Description
Interface
Status
148
Address Range
Hardware Address
IP Services Commands
Description
State
Lease Allocation
Lease Remaining
IP Address
Subnet Mask
Default Router
DNS Servers
Default DNS domain name included in the DHCP Offer to the client.
show interface
Displays the IP interfaces configured on the MX.
Syntax show interface [vlan-id]
vlan-id
Defaults If you do not specify a VLAN ID, interfaces for all VLANs are displayed.
Access All.
History
Version 1.0
Command introduced.
Version 4.0
Usage The IP interface table flags an address assigned by a DHCP server with an asterisk ( * ).
Examples The following command displays all the IP interfaces configured on an MX:
WLC# show interface
VLAN Name
Address
Mask
10.10.10.10
255.255.255.0
YES
Up
ipv4
2 mauve
10.10.20.10
255.255.255.0
NO
Down
ipv4
255.255.255.0
YES
Up
ipv4
4 corpvlan
*10.3.1.110
149
Description
VLAN
VLAN number
Name
VLAN name
Address
IP address
Mask
Subnet mask
Enabled
Administrative state:
YES (enabled)
NO (disabled)
State
Link state:
Up (operational)
Down (unavailable)
RIB
See Also
clear interface on page 103
set interface on page 113
set interface status on page 117
show ip alias
Displays the IP aliases configured on the MX.
Syntax show ip alias [name]
name
Alias string.
Defaults If you do not specify an alias name, all aliases are displayed.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command displays all the aliases configured on an MX:
WLC# show ip alias
Name
IP Address
--------------------
--------------------
HR1
192.168.1.2
payroll
192.168.1.3
radius1
192.168.7.2
Description
Name
Alias string.
IP Address
See Also
150
IP Services Commands
show ip dns
Displays the DNS servers used by the MX.
Syntax show ip dns
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays the DNS information:
WLC# show ip dns
Domain Name: example.com
DNS Status: enabled
IP Address
Type
----------------------------------10.1.1.1
PRIMARY
10.1.1.2
SECONDARY
10.1.2.1
SECONDARY
Description
Domain Name
DNS Status
IP Address
Type
Server type:
PRIMARY
SECONDARY
See Also
clear ip dns domain on page 104
clear ip dns server on page 105
set ip dns on page 118
set ip dns domain on page 118
set ip dns server on page 119
151
show ip https
Displays information about the HTTPS management port.
Syntax show ip https
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command shows the status and port number for the HTTPS management
interface to the MX switch:
WLC> show ip https
HTTPS is enabled
HTTPS is set to use port 443
Last 10 Connections:
IP Address
Last Connected
------------
-----------------------
------------
10.10.10.56
349
Description
HTTPS is enabled/disabled
Last 10 connections
IP Address
Last Connected
Time when the device established the HTTPS connection to the WLC.
Number of seconds since the device established the HTTPS connection to the switch.
See Also
clear ip telnet on page 106
set ip https server on page 120
set ip telnet on page 124
set ip telnet server on page 125
show ip telnet on page 154
152
IP Services Commands
show ip route
Displays the IP route table on the WLC.
Syntax show ip route [destination]
Route destination IP address, in dotted decimal notation.
destination
Defaults None.
Access All.
Proto
VLAN:Interface
1 Router
10.0.1.17
Down
0.0.0.0/ 0 Static
2 Router
10.0.2.17
vlan:2:ip
10.0.2.1/24 IP
0 Direct
10.0.2.1/32 IP
vlan:2:ip:10.0.1.1/24
0 Direct
10.0.2.255/32 IP
vlan:2:ip:10.0.1.1/24
0 Direct
224.0.0.0/ 4 IP
0 Local
vlan:2:ip
MULTICAST
Description
IP address and subnet mask of the route destination.
The 244.0.0.0 route is automatically added by MSS and supports the IGMP snooping feature.
Proto
Protocol that added the route to the IP route table. The protocol can be one of the following:
IPMSS added the route.
StaticAn administrator added the route.
Metric
153
Description
NH-Type
Next-hop type:
LocalRoute is for a local interface. MSS adds the route when you configure an IP address on
an MX.
DirectRoute is for a locally attached subnet. MSS adds the route when you add an interface
in the same subnet as the MX.
RouterRoute is for a remote destination. An MX switch forwards traffic for the destination to
the default router (gateway).
Gateway
VLAN:Interface
Destination VLAN, protocol type, and IP address of the route. Because direct routes are for local
interfaces, a destination IP address is not listed.
The destination for the IP multicast route is MULTICAST.
For static routes, the value Down means the MX does not have an interface to the destination
next-hop router. To provide an interface, configure an IP interface that is in the same IP subnet as
the next-hop router. The IP interface must be on a VLAN with the port attached to the default
router.
See Also
clear ip route on page 105
set interface on page 113
set ip route on page 121
show interface on page 149
show vlan config on page 91
show ip telnet
Displays information about the Telnet management port.
Syntax show ip telnet
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command shows the status and port number for the Telnet management interface
to the MX:
WLC> show ip telnet
Server Status
Port
---------------------------------Enabled
23
154
IP Services Commands
Description
Server Status
Port
TCP port number that the MX listens for Telnet management traffic.
See Also
clear ip telnet on page 106
set ip https server on page 120
set ip telnet on page 124
set ip telnet server on page 125
show ip https on page 152
show ntp
Displays NTP client information.
Syntax show ntp
Defaults None.
Access All.
History
Version 1.0
Command introduced
Version 2.0
Examples To display NTP information for an MX, type the following command:
WLC> show ntp
NTP client: enabled
Current update-interval: 20(secs)
Current time: Fri Feb 06 2004, 12:02:57
Timezone is set to 'PST', offset from UTC is -8:0 hours.
Summertime is enabled.
Last NTP update: Fri Feb 06 2004, 12:02:46
NTP Server
Peer state
Local State
--------------------------------------------------192.168.1.5
SYSPEER
SYNCED
155
Description
NTP client
State of the NTP client. The state can be one of the following:
Enabled
Disabled
Current update-interval
Number of seconds between queries sent by the MX to the NTP servers for updates.
Current time
System time that was current on the MX when you pressed Enter after typing the show ntp
command.
Timezone
Time zone configured on the switch. MSS offsets the time reported by the NTP server based on
the time zone.
This field is displayed only if you change the time zone.
Summertime
Summertime period configured on the switch. MSS offsets the system time +1 hour and returns it
to standard time for daylight savings time or a similar summertime period that you set.
This field is displayed only if you enable summertime.
Time when the WLC received the most recent update from an NTP server.
NTP Server
Peer state
State of the NTP session from the point of view of the NTP server:
CORRECT
REJECT
SELCAND
SYNCCAND
SYSPEER
Local state
See Also
clear ntp server on page 106
clear summertime on page 109
clear timezone on page 110
set ntp on page 125
set ntp server on page 126
set summertime on page 142
set timezone on page 144
show timezone on page 159
IP Services Commands
Access Enabled.
History Introduced in MSS Version 4.0.
See Also
clear snmp community on page 107
set snmp community on page 127
157
See Also
set snmp community on page 127
set snmp notify target on page 133
set snmp notify profile on page 129
set snmp protocol on page 137
set snmp security on page 138
set snmp usm on page 138
show snmp community on page 156
show snmp counters on page 157
show snmp notify profile on page 157
show snmp notify target on page 157
show snmp usm on page 158
show summertime
Shows an MX offset time from the real-time clock time.
Syntax show summertime
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples To display the summertime setting on an MX, type the following command:
MX-20# show summertime
Summertime is enabled, and set to 'PDT'.
Start
End
Offset : 60 minutes
Recurring : yes, starting at 2:00 am of first Sunday of April
and ending at 2:00 am on last Sunday of October.
See Also
158
IP Services Commands
show timedate
Shows the date and time of day currently set on an WLC real-time clock.
Syntax show timedate
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples To display the time and date set on an WLC real-time clock, type the following
command:
MX-20# show timedate
Sun Feb 29 2004, 23:59:02 PST
See Also
clear summertime on page 109
clear timezone on page 110
set summertime on page 142
set timedate on page 143
set timezone on page 144
show summertime on page 158
show timezone on page 159
show timezone
Shows the time offset for the real-time clock from UTC on an WLC.
Syntax show timezone
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples To display the offset from UTC, type the following command:
WLC# show timezone
Timezone set to 'pst', offset from UTC is -8 hours
See Also
Copyright 2011, Juniper Networks, Inc.
159
telnet
Opens a Telnet client session with a remote device.
Syntax telnet {ip-addr | hostname} [port port-num]
ip-addr
hostname
port port-num
TCP port number that the TCP server on the remote device listens for Telnet
connections.
Defaults MSS attempts to establish Telnet connections with TCP port 23 by default.
Access Enabled.
History Introduced in MSS Version 1.1.
Usage To end a Telnet session from the remote device, press Ctrl+t or type exit in the
management session on the remote device. To end a client session from the local device, use the
clear sessions telnet client command.
If the configuration of the MX on which you enter the telnet command has an ACL that denies
Telnet client traffic, the ACL also denies access by the telnet command.
Examples In the following example, an administrator establishes a Telnet session with another MX
and enters a command on the remote WLC:
WLC# telnet 10.10.10.90
Session 0 pty tty2.d Trying 10.10.10.90...
Connected to 10.10.10.90
Disconnect character is '^t'
Copyright (c) 2002, 2003
Juniper Networks, Inc.
Username: username
Password: password
WLC-remote> show vlan
Admin
VLAN Name
VLAN
Tunl
Port
Tag
State
IP Services Commands
1 default
Up
3 red
10 backbone
Up
Up
Up
Up
Up
none Up
21
none Up
22
none Up
When the administrator presses Ctrl+t to end the Telnet connection, the management session
returns to the local MX prompt:
WLC-remote> Session 0 pty tty2.d terminated tt name tty2.d
WLC#
See Also
clear sessions on page 527
show sessions on page 529
traceroute
Traces the route from the WLC to an IP host.
Syntax traceroute host [dnf] [no-dns] [port port-num] [queries num]
[size size] [ttl hops] [wait ms]
host
dnf
Sets the Do Not Fragment bit in the ping packet to prevent the packet from
being fragmented.
no-dns
Prevents MSS from performing a DNS lookup for each hop to the destination
host.
port port-num
queries num
size size
Probe packet size in bytes. You can specify from 40 through 1460.
ttl hops
wait ms
Defaults
dnfDisabled
no-dnsDisabled
port33434
queries3
size38
ttl30
161
wait5000
Access All.
History Introduced in MSS Version 1.0.
Usage To stop a traceroute command that is in progress, press Ctrl+C.
Examples The following example traces the route to host server1:
WLC# traceroute server1
traceroute to server1.example.com (192.168.22.7), 30 hops max, 38 byte
packets
1 engineering-1.example.com (192.168.192.206) 2 ms 1 ms 1 ms
2 engineering-2.example.com (192.168.196.204) 2 ms 3 ms 2 ms
3 gateway_a.example.com (192.168.1.201) 6 ms 3 ms 3 ms
4 server1.example.com (192.168.22.7) 3 ms * 2 ms
The first row of the display indicates the target host, the maximum number of hops, and the packet
size. Each numbered row displays information about one hop. The rows are displayed in the order
that the hops occur, beginning with the hop closest to the MX.
The row for a hop lists the total time in milliseconds for each ICMP packet to reach the router or
host, plus the time for the ICMP Time Exceeded message to return to the host.
An exclamation point (!) following any of these values indicates that the Port Unreachable
message returned by the destination has a maximum hop count of 0 or 1. This can occur if the
destination uses the maximum hop count value from the arriving packet as the maximum hop
count in its ICMP reply. The reply does not arrive at the source until the destination receives a
traceroute packet with a maximum hop count equal to the number of hops between the source and
destination.
An asterisk (*) indicates that the timeout period expired before MSS received a Time Exceeded
message for the packet.
If Traceroute receives an ICMP error message other than a Time Exceeded or Port Unreachable
message, MSS displays one of the error codes described in Table 30 instead of displaying the
round-trip time or an asterisk (*).
Table 30 describes the traceroute error messages.
Table 30.Error Messages for traceroute
Field
Description
!N
!H
!P
!F
!S
!A
162
IP Services Commands
163
164
IP Services Commands
165
166
AAA Commands
Use authentication, authorization, and accounting (AAA) commands to provide a secure network
connection and a record of user activity. Location policy commands override any virtual LAN
(VLAN) or security ACL assignment by AAA or the local MX database to help you control access
locally.
(Security ACLs are packet filters. For command descriptions, see Chapter , Security ACL
Commands, on page 453.)
This chapter presents AAA commands alphabetically. Use the following table to locate commands
in this chapter based on their use.
Authentication
New
Updated
Updated
Password Users
167
MAC Users
Web authorization
Accounting
New
Updated
Updated
Mobility Profiles
Location Policy
168
AAA Commands
clear accounting
Removes accounting services for specified wireless users with administrative access or network
access.
Syntax clear accounting {admin| console | [mac | dot1x | web | system
[ssid ssid| wired user-glob]]|last-resort | statistics | system}
{user-glob}
admin
dot1x
Users with network access through the MX. Users with network access are
authorized to use the network through either an IEEE 802.1X method or
their media access control (MAC) address.
system
user-glob
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 5.0
Version 7.0
Examples The following command removes accounting services for authorized network user Nin:
WLC# clear accounting dot1x Nin
success: change accepted.
169
See Also
set accounting {admin | console} on page 182
set accounting system on page 185
show accounting statistics on page 226
user-glob
AAA Commands
user-glob
wired
user-glob
171
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Examples The following command removes 802.1X authentication for network users with
usernames ending in @thiscorp.com who try to access SSID finance:
WLC# clear authentication dot1x ssid finance *@thiscorp.com
See Also
clear authentication admin on page 170
clear authentication console on page 171
clear authentication mac on page 172
clear authentication web on page 173
set authentication dot1x on page 190
show aaa on page 218
wired
mac-addr-glob
MAC address glob associated with the rule you are removing.
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Examples The following command removes a MAC authentication rule for access to SSID
thatcorp by MAC addresses beginning with aa:bb:cc:
172
AAA Commands
user-glob
Defaults None.
Access Enabled.
History Introduced in MSS 4.0.
Examples The following command removes the proxy rule for SSID mycorp and userglob **:
WLC# clear authentication proxy ssid mycorp **
See Also
set authentication proxy on page 198
show aaa on page 218
wired
user-glob
Defaults None.
Access Enabled.
History Introduced in MSS 3.0.
Examples The following command removes WebAAA for SSID research and userglob
temp*@thiscorp.com:
Copyright 2011, Juniper Networks, Inc.
173
all
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.1.
Version 1.1
Command introduced.
Version 7.0
Usage To determine the index numbers of location policy rules, use the show location policy
command. Removing all the ACEs from the location policy disables this function on the MX.
Examples The following command removes location policy rule 4 from an MX location policy:
WLC# clear location policy 4
success: clause 4 is removed.
See Also
set location policy on page 200
show location policy on page 228
clear mac-user
Removes a user profile from the local database on the MX for a user authenticated by a MAC
address.
(To remove a user profile in RADIUS, see the documentation for your RADIUS server.)
Syntax clear mac-user mac-address-glob
mac-address-glob
174
AAA Commands
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Version 1.0
Command introduced.
Version 7.0
Usage Deleting a MAC user profile from the database deletes the assignment of any profile
attributes to the user.
Examples The following command removes user profiles at MAC address 01:02:*
WLC# clear mac-user 01:02:*
success: change accepted.
See Also
set mac-usergroup attr on page 209
set mac-user attr on page 204
show aaa on page 218
attribute-name
Defaults None.
Access Enabled.
History .
Version 1.0
Command introduced.
Version 7.0
Examples The following command removes an access control list (ACL) from the profile of a user
at MAC address 01:02:03:04:05:06:
WLC# clear mac-user 01:02:03:04:05:06 attr filter-id
success: change accepted.
See Also
175
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 7.0
Usage Removing a MAC user from a MAC user group removes the group name from the user
profile, but does not delete the user group from the local MX database. To remove the group, use
clear mac-usergroup.
Examples The following command deletes a user profile at MAC address 01:02:03:04:05:06 from
its user group:
WLC# clear mac-user 01:02:03:04:05:06 group
success: change accepted.
See Also
clear mac-usergroup on page 176
set mac-user on page 204
show aaa on page 218
clear mac-usergroup
Removes a user group from the local database on the MX for a group of users authenticating with
a MAC address.
(To delete a MAC user group in RADIUS, see the documentation for your RADIUS server.)
Syntax clear mac-usergroup group-name
group-name
Defaults None.
Access Enabled.
176
AAA Commands
attribute-name
Name of an attribute used to authorize the MAC users in the user group
for a particular service or session characteristic. (For a list of
authorization attributes, see Table 31 on page 206.)
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage To remove the group itself, use the clear mac-usergroup command.
Examples The following command removes the members of the MAC user group eastcoasters
from a VLAN assignment by deleting the VLAN-Name attribute from the group:
WLC# clear mac-usergroup eastcoasters attr vlan-name
success: change accepted.
See Also
clear mac-usergroup on page 176
set mac-usergroup attr on page 209
show aaa on page 218
177
clear mobility-profile
Removes a Mobility Profile entirely.
Syntax clear mobility-profile mprofile-name
mprofile-name
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Examples The following command removes the Mobility Profile for user Nin:
WLC# clear mobility-profile Nin
success: change accepted.
See Also
set mobility-profile on page 210
set mobility-profile mode on page 212
show mobility-profile on page 228
clear user
Removes a user profile from the local database on the MX.
(To remove a user profile in RADIUS, see the documentation for your RADIUS server.)
Syntax clear user username
username
Username
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage Deleting the user profile from the database deletes the assignment of any profile attributes
to the user.
Examples The following command deletes the user profile for user Nin:
WLC# clear user Nin
success: change accepted.
See Also
set user on page 212
show aaa on page 218
178
AAA Commands
attribute-name
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Examples The following command removes the Session-Timeout attribute from jsmith user profile:
WLC# clear user jsmith attr session-timeout
success: change accepted.
See Also
set user attr on page 214
show aaa on page 218
Username
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage Removing the user from the group removes the group name from the user profile, but does
not delete either the user or the user group from the local MX database. To remove the group, use
clear usergroup.
Examples The following command removes the user Nin from the user group Nin is in:
WLC# clear user Nin group
success: change accepted.
See Also
clear usergroup on page 180
Copyright 2011, Juniper Networks, Inc.
179
Defaults None.
Access Enabled.
History Introduced in MSS 6.0.
Usage If a users password has expired, or the user is unable to log in within the configured limit
for login attempts, then the user is locked out of the system, and cannot gain access without the
intervention of an adminstrator. Use this command to restore access to the user.
Examples The following command restores access to user Nin, who was previously locked out of
the system:
WLC# clear user Nin lockout
success: change accepted.
See Also
set authentication minimum-password-length on page 196
set authentication password-restrict on page 197
set user on page 212
set user expire-password-in on page 215
clear usergroup
Removes a user group and its attributes from the local database on the MX for users with
passwords.
(To delete a user group in RADIUS, see the documentation for your RADIUS server.)
Syntax clear usergroup group-name
group-name
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage Removing a user group from the local MX database does not remove the user profiles of
the group members from the database.
Examples The following command deletes the cardiology user group from the local database:
WLC# clear usergroup cardiology
180
AAA Commands
attribute-name
Name of an attribute used to authorize all the users in the group for a
particular service or session characteristic. (For a list of authorization
attributes, see Table 31 on page 206.)
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Examples The following command removes the members of the user group cardiology from a
network access time restriction by deleting the Time-Of-Day attribute from the group:
WLC# clear usergroup cardiology attr time-of-day
success: change accepted.
See Also
clear usergroup on page 180
set usergroup on page 216
show aaa on page 218
set aaa-profile
Usage Creates AAA profiles and configure the authentication methods to all for authentication
chaining.
This feature allows multiple authentications for a client on the network. The most common of these
is MAC authentication and dot1x. In some cases, three authentications are required by the
network configuration.
All authentication types are supported in a chain and are allowed in any sequence except that
Web authentication must be last in the chain. Authorization is required at each step of the chain
and an attribute assigned in a previous step is replaced by the subsequent step.
181
authen-type
console
user-glob
start-stop
stop-only
method1
method2
method3
method4
AAA Commands
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Usage For network users with start-stop accounting whose records are sent to a RADIUS server,
MSS sends interim updates to the RADIUS server when the user roams.
Examples The following command issues start-and-stop accounting records at the local MX
database for administrator Natasha, when she accesses the switch using Telnet or Web View:
WLC# set accounting admin Natasha start-stop local
success: change accepted.
See Also
clear accounting on page 169
show accounting statistics on page 226
Users with network access through the MX switch who are authenticated by
802.1X.
mac
Users with network access through the MX switch who are authenticated by
MAC authentication
web
Users with network access through the MX switch who are authenticated by
WebAAA
183
ssid ssid-name
SSID name to which this accounting rule applies. To apply the rule to all
SSIDs, type any.
wired
user-glob
mac-addr-glob
A single user or set of users with access via a MAC address. Specify a MAC
address, or use the wildcard (*) character to specify a set of MAC
addresses. (For details, see MAC Address Globs on page 27.)
This option applies only when mac is specified.
start-stop
stop-only
method1
method2
method3
method4
Command introduced
Version 3.0
Usage For network users with start-stop accounting profiles whose records are sent to a RADIUS
server, MSS sends interim updates to the RADIUS server when the user roams.
Examples The following command issues stop-only records to the RADIUS server group sg2 for
network user Nin, who is authenticated by 802.1X:
184
AAA Commands
185
186
AAA Commands
Single user or set of users with administrative access over the network
through Telnet or Web View.
Specify a username, use the double-asterisk wildcard character (**) to
specify all usernames, or use the single-asterisk wildcard character (*) to
specify a set of usernames up to or following the first delimiter
charactereither an at sign (@) or a period (.). (For details, see User
Globs on page 27.)
method1
method2
method3
method4
Defaults By default, authentication is deactivated for all admin users. The default authentication
method in an admin authentication rule is local. MSS checks the local MX database for
authentication.
Access Enabled.
History
MSS 1.0
Command introduced.
MSS 7.1
187
Informational Note: The syntax descriptions for the set authentication commands are separated for
clarity. However, the options and behavior for the set authentication admin command are the same as in
previous releases.
Usage You can configure different authentication methods for different groups of users. (For
details, see User Globs, MAC Address Globs, and VLAN Globs on page 27.)
If you specify multiple authentication methods in the set authentication console command, MSS
applies them in the order that they appear in the command, with these results:
If the first method responds with pass or fail, the evaluation is final.
If the first method does not respond, MSS tries the second method, and so on.
However, if local appears first, followed by a RADIUS server group, MSS ignores any failed
searches in the local MX database and sends an authentication request to the RADIUS server
group.
Informational Note: If a AAA rule specifies local as a secondary AAA method, to be used if the RADIUS
servers are unavailable, and MSS authenticates a client with the local method, MSS starts again at the
beginning of the method list when attempting to authorize the client. This can cause unexpected delays during
client processing and can cause the client to time out before completing logon.
Examples The following command configures administrator Jose, who connects via Telnet, for
authentication on RADIUS server group sg3:
WLC# set authentication admin Jose sg3
success: change accepted.
See Also
clear authentication admin on page 170
set authentication console on page 188
set authentication dot1x on page 190
set authentication mac on page 194
set authentication web on page 199
show aaa on page 218
188
AAA Commands
user-glob
method1
method2
method3
method4
189
Access Enabled.
History Introduced in MSS 1.0.
Informational Note: The syntax descriptions for the set authentication commands are separated for
clarity. However, the options and behavior for the set authentication console command are the same as in
previous releases.
Usage You can configure different authentication methods for different groups of users. (For
details, see User Globs, MAC Address Globs, and VLAN Globs on page 27.)
If you specify multiple authentication methods in the set authentication console command, MSS
applies them in the order in which they appear in the command, with these results:
If the first method responds with pass or fail, the evaluation is final.
If the first method does not respond, MSS tries the second method, and so on.
However, if local appears first, followed by a RADIUS server group, MSS ignores any failed
searches in the local MX database and sends an authentication request to the RADIUS server
group.
Examples To set the console port so that it does not enforce username-password authentication
for administrators, type the following command:
WLC# set authentication console * none
success: change accepted.
See Also
clear authentication console on page 171
set authentication admin on page 186
set authentication dot1x on page 190
set authentication mac on page 194
set authentication web on page 199
show aaa on page 218
190
ssid
ssid-name
SSID name to which this authentication rule applies. To apply the rule to all
SSIDs, type any.
wired
AAA Commands
user-glob
bonded
191
protocol
method1
method2
method3
method4
At least one and up to four methods that MSS uses to handle authentication.
Specify one or more of the following methods in priority order. MSS applies
multiple methods in the order you enter them.
A method can be one of the following:
localUses the local database of usernames and user groups on the MX
switch for authentication.
server-group-nameUses the defined group of RADIUS servers for
authentication. You can enter up to four names of existing RADIUS server
groups as methods.
RADIUS servers cannot be used with the EAP-TLS protocol.For more information,
see Usage.
Defaults By default, authentication is unconfigured for all clients with network access through MP
ports or wired authentication ports on the MX. Connection, authorization, and accounting are also
disabled for these users.
192
AAA Commands
Command introduced
Version 2.1
Version 3.0
Usage You can configure different authentication methods for different groups of users by
globbing. (For details, see User Globs on page 27.)
You can configure a rule either for wireless access to an SSID, or for wired access through an
WLC wired authentication port. If the rule is for wireless access to an SSID, specify the SSID name
or specify any to match on all SSID names. If the rule is for wired access, specify wired instead of
an SSID name.
You cannot configure client authentication that uses both EAP-TLS protocol and one or more
RADIUS servers. EAP-TLS authentication is supported only on the local MX database.
If you specify multiple authentication methods in the set authentication dot1x command, MSS
applies them in the order in which they appear in the command, with these results:
If the first method responds with pass or fail, the evaluation is final.
If the first method does not respond, MSS tries the second method, and so on.
However, if local appears first, followed by a RADIUS server group, MSS overrides any failed
searches in the local MX database and sends an authentication request to the server group.
If the user does not support 802.1X, MSS attempts to perform MAC authentication for the user. In
this case, if the WLC configuration contains a set authentication mac command that matches the
SSID the user is attempting to access and the user MAC address, MSS uses the method specified
by the command. Otherwise, MSS uses local MAC authentication by default.
If the username does not match an authentication rule for the SSID the user is attempting to
access, MSS uses the fallthru authentication type configured for the SSID, which can be
last-resort, web-portal (for WebAAA), or none. The following command configures EAP-TLS
authentication in the local MX database for SSID mycorp and 802.1X client Geetha:
WLC# set authentication dot1x ssid mycorp Geetha eap-tls local
success: change accepted.
The following command configures PEAP-MS-CHAP-V2 authentication at RADIUS server groups
sg1 through sg3 for all 802.1X clients at example.com who want to access SSID examplecorp:
WLC# set authentication dot1x ssid examplecorp *@example.com
peap-mschapv2 sg1 sg2 sg3
success: change accepted.
See Also
clear authentication dot1x on page 171
set authentication admin on page 186
Copyright 2011, Juniper Networks, Inc.
193
SSID name to which this authentication rule applies. To apply the rule to all
SSIDs, type any.
wired
mac-addr-glob
A single user or set of users with access via a MAC address. Specify a MAC
address, or use the wildcard (*) character to specify a set of MAC
addresses. (For details, see MAC Address Globs on page 27.)
method1
method2
method3
method4
Defaults By default, authentication is deactivated for all MAC users, which means MAC address
authentication fails by default. When using RADIUS for authentication, the default password for
MAC and last-resort users is Juniper.
194
AAA Commands
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Version 7.1
Usage You can configure different authentication methods for different groups of MAC addresses
by globbing. (For details, see User Globs, MAC Address Globs, and VLAN Globs on page 27.)
If you specify multiple authentication methods in the set authentication mac command, MSS
applies them in the order in which they appear in the command, with these results:
If the first method responds with pass or fail, the evaluation is final.
If the first method does not respond, MSS tries the second method, and so on.
However, if local appears first, followed by a RADIUS server group, MSS ignores any failed
searches in the local MX database and sends an authentication request to the RADIUS server
group.
If the WLC configuration contains a set authentication mac command that matches the SSID the
user is attempting to access and the user MAC address, MSS uses the method specified by the
command. Otherwise, MSS uses local MAC authentication by default.
If the username does not match an authentication rule for the SSID the user is attempting to
access, MSS uses the fallthru authentication type configured for the SSID, which can be
last-resort, web-portal (for WebAAA), or none.
Examples To use the local MX database to authenticate all users who access the mycorp2 SSID
by their MAC address, type the following command:
WLC# set authentication ssid mycorp2 mac ** local
success: change accepted.
See Also
clear authentication mac on page 172
set authentication admin on page 186
set authentication console on page 188
set authentication dot1x on page 190
set authentication web on page 199
show aaa on page 218
195
Number of allowable login attempts for a user. You can specify a number between
0 1000. Specifying 0 causes the number of allowable login attempts to reset to
the default values.
Defaults For Telnet or SSH sessions, a maximum of 4 failed login attempts are allowed by default.
For console or network sessions, an unlimited number of failed login attempts are allowed by
default.
Access Enabled.
History Introduced in MSS 6.0.
Usage Use this command to specify the maximum number of failed login attempts allowed for a
user. If the user is unable to log in within the specified number of attempts, the user is locked out of
the system, and access must be manually restored with the clear user lockout command.
Examples To allow users a maximum of 3 attempts to log into the system, type the following
command:
WLC# set authentication max-attempts 3
success: change accepted.
See Also
clear user lockout on page 180
set authentication minimum-password-length on page 196
set authentication password-restrict on page 197
Minimum number of characters that can be in a user password. You can specify a
minimum password length between 0 32 characters. Specifying 0 removes the
restriction on password length.
AAA Commands
Access Enabled.
History Introduced in MSS 6.0.
Usage Use this command to specify the minimum length for user passwords. When this command
is configured, you cannot configure a password shorter than the specified length.
When you enable this command, MSS evaluates the passwords configured on the WLC switch
and displays a list of users whose password does not meet the minimum length restriction.
Examples To set the minimum length for user passwords at 7 characters, type the following
command:
WLC# set authentication minimum-password-length 7
warning: the following users have passwords that are shorter than the
minimum password length dan
admin
user2
goofball
success: change accepted.
See Also
clear user lockout on page 180
set authentication minimum-password-length on page 196
set user on page 212
disable
197
When you enable the password restrictions, MSS evaluates the passwords configured on the
WLC switch and displays a list of users whose password does not meet the restriction on length
and character types.
Examples To enable password restrictions on the WLC switch, type the following command:
WLC# set authentication password-restrict enable
warning: the following users have passwords that do not have atleast 2
each of upper-case letters, lower-case letters, numbers and special
characters dan
admin
user1
user2
jdoe
jsmith
success: change accepted.
See Also
set authentication minimum-password-length on page 196
set authentication max-attempts on page 196
clear user lockout on page 180
user-glob
radius-server-group
Defaults None.
Access Enabled.
History Introduced in MSS 4.0.
Usage AAA for third-party AP users has additional configuration requirements. See the
Configuring AAA for Users of Third-Party APs section in the Configuring AAA for Network
Users chapter of the Juniper Mobility System Software Configuration Guide.
198
AAA Commands
Examples The following command configures a proxy authentication rule that matches on all
usernames associated with SSID mycorp. MSS uses RADIUS server group srvrgrp1 to proxy
RADIUS requests and hence to authenticate and authorize the users.
WLC# set authentication proxy ssid mycorp ** srvrgrp1
See Also
clear authentication proxy on page 173
set radius proxy client on page 501
set radius proxy port on page 502
ssid
ssid-name
SSID name to which this authentication rule applies. To apply the rule to all
SSIDs, type any.
wired
method1
At least one and up to four methods that MSS uses to handle authentication.
Specify one or more of the following methods in priority order. MSS applies
multiple methods in the order you enter them.
method2
method3
method4
199
Defaults By default, authentication is unconfigured for all clients with network access through MP
ports or wired authentication ports on the MX switch. Connection, authorization, and accounting
are also disabled for these users.
Access Enabled.
History Introduced in MSS 3.0. Added LDAP in MSS 7.1.
Usage You can configure different authentication methods for different groups of users by
globbing. (For details, see User Globs on page 27.)
You can configure a rule either for wireless access to an SSID, or for wired access through an
WLC wired authentication port. If the rule is for wireless access to an SSID, specify the SSID name
or specify any to match on all SSID names. If the rule is for wired access, specify wired instead of
an SSID name.
If you specify multiple authentication methods in the set authentication web command, MSS
applies them in the order in which they appear in the command, with these results:
If the first method responds with pass or fail, the evaluation is final.
If the first method does not respond, MSS tries the second method, and so on.
However, if local appears first, followed by a RADIUS server group, MSS overrides any failed
searches in the local MX database and sends an authentication request to the server group.
MSS uses a WebAAA rule only under the following conditions:
The client is not denied access by 802.1X or does not support 802.1X.
The client MAC address does not match a MAC authentication rule.
The fallthru type is web-portal. (For a wireless authentication rule, the fallthru type is specified
by the set service-profile auth-fallthru command. For a wired authentication rule, the type is
specified by the auth-fall-thru option of the set port type wired-auth command.)
Examples The following command configures a WebAAA rule in the local MX database for SSID
ourcorp and userglob rnd*:
WLC# set authentication web ssid ourcorp rnd* local
success: change accepted.
See Also
clear authentication web on page 173
set authentication admin on page 186
set authentication console on page 188
set authentication dot1x on page 190
show aaa on page 218
200
AAA Commands
Denies access to the network to users with attributes that match the location
policy rule.
permit
Action optionsFor a permit rule, MSS changes the attributes assigned to the user to the
values specified by the following options:
vlan vlan-name
inacl inacl-name
outacl
outacl-name
Condition optionsMSS takes the action specified by the rule if all conditions in the rule are
met. You can specify one or more of the following conditions:
ssid operator
ssid-name
SSID with which the user is associated. The operator must be eq, which
applies the location policy rule to all users associated with the SSID.
Asterisks (wildcards) are not supported in SSID names. You must specify
the complete SSID name.
time-of-day
operator
time-of-day
Time of day that the user is allowed or denied access to the wireless
network.
eqDefines a specific timeframe.
neqDefines any other time than the specified timeframe.
201
vlan operator
vlan-glob
user operator
user-glob
Username andv condition that determines if the location policy rule applies.
Replace operator with one of the following operands:
eqApplies the location policy rule to all usernames matching user-glob.
neqApplies the location policy rule to all usernames not matching
user-glob.
For user-glob, specify a username, use the double-asterisk wildcard
character (**) to specify all usernames, or use the single-asterisk wildcard
character (*) to specify a set of usernames up to or following the first
delimiter character, either an at sign (@) or a period (.). (For details, see
User Globs on page 27.)
before
rule-number
Inserts the new location policy rule in front of another rule in the location
policy. Specify the number of the existing location policy rule. (To determine
the number, use the show location policy command.)
modify
rule-number
Replaces the rule in the location policy with the new rule. Specify the number
of the existing location policy rule. (To determine the number, use the show
location policy command.)
port port-list
List of physical port(s) that determines if the location policy rule applies.
Defaults By default, users are permitted VLAN access and assigned security ACLs according to
the VLAN-Name and Filter-Id attributes applied to the users during normal authentication and
authorization.
Access Enabled.
History
Version 1.1
Command introduced
Version 3.2
Usage Only a single location policy is allowed per MX switch. The location policy can contain up to
150 rules. Once configured, the location policy becomes effective immediately. To disable location
policy operation, use the clear location policy command.
202
AAA Commands
Conditions within a rule are ANDed. All conditions in the rule must match in order for MSS to take
the specified action. If the location policy contains multiple rules, MSS compares the user
information to the rules one at a time, in the order the rules appear in the WLC configuration file,
beginning with the rule at the top of the list. MSS continues comparing until a user matches all
conditions in a rule or until there are no more rules.
The order of rules in the location policy is important to ensure users are properly granted or denied
access. To position rules within the location policy, use before rule-number and
modify rule-number in the set location policy command, and the clear location policy
rule-number command.
When applying security ACLs:
Use inacl inacl-name to filter traffic that enters the WLC from users via an MP access port or
wired authentication port, or from the network via a network port.
Use outacl outacl-name to filter traffic sent from the switch to users via an MP access port or
wired authentication port, or from the network via a network port.
You can optionally add the suffixes .in and .out to inacl-name and outacl-name so that they
match the names of security ACLs stored in the local MX database.
Examples The following command denies network access to all users at *.theirfirm.com, causing
them to fail authorization:
WLC# set location policy deny if user eq *.theirfirm.com
The following command authorizes access to the guest_1 VLAN for all users who are not at
*.wodefirm.com:
WLC# set location policy permit vlan guest_1 if user neq *.wodefirm.com
The following command authorizes users at *.ny.ourfirm.com to access the bld4.tac VLAN instead,
and applies the security ACL tac_24 to the traffic they receive:
WLC# set location policy permit vlan bld4.tac outacl tac_24 if user eq
*.ny.ourfirm.com
The following command authorizes access to users on VLANs with names matching bld4.* and
applies security ACLs svcs_2 to the traffic they send and svcs_3 to the traffic they receive:
WLC# set location policy permit inacl svcs_2 outacl svcs_3 if vlan eq
bldg4.*
The following command authorizes users entering the network on MX ports 3 through 7 and
port 12 to use the floor2 VLAN, overriding any settings from AAA:
WLC# set location policy permit vlan floor2 if port 3-7,12
The following command places all users who are authorized for SSID tempvendor_a into VLAN
kiosk_1:
WLC# set location policy permit vlan kiosk_1 if ssid eq tempvendor_a
success: change accepted.
See Also
clear location policy on page 174
show location policy on page 228
Copyright 2011, Juniper Networks, Inc.
203
set mac-user
Configures a user profile in the local database on the MX for a user who can authenticate by a
MAC address, and optionally adds the user to a MAC user group.
(To configure a MAC user profile in RADIUS, see the documentation for your RADIUS server.)
Syntax set mac-user mac-address-glob[group group-name]
mac-addr-glob
group-name
Defaults None.
Access Enabled.
History
MSS Version 1.0
Introduced command
Usage MSS does not require MAC users to belong to user groups.
Users authenticated by MAC address are authenticated only for network access through the MX.
MSS does not support passwords for MAC users.
Examples The following command creates a user profile for a user at MAC address
01:02:03:04:05:* and assigns the user to the eastcoasters user group:
WLC# set mac-user 01:02:03:04:05:* group eastcoasters
success: change accepted.
See Also
clear mac-user on page 174
show aaa on page 218
204
AAA Commands
attribute-name value
Name and value of an attribute used to authorize the MAC user for a
particular service or session characteristic. For a list of authorization
attributes and values that you can assign to local users, see Table 31
on page 206.
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 1.1
Version 3.0
Version 5.0
Version 7.1
Usage To change the value of an attribute, enter set mac-user attr with the new value. To delete
an attribute, use clear mac-user attr.
You can assign attributes to individual MAC users and to MAC user groups. If attributes are
configured for a MAC user and also for the group the MAC user is in, the attributes assigned to the
individual MAC user take precedence for that user. For example, if the start-date attribute
configured for a MAC user is earlier than the start-date configured for the MAC user group for the
user, the MAC user network access can begin as soon as the user start-date. The MAC user does
not need to wait for the MAC user group start date.
205
Description
Valid Value(s)
encryption-type
encryption algorithm:
Encryption-Type is a Juniper
2Reserved
type is 3.
filter-id
only)
idle-timeout
mobility-profile
only)
Mobility-Profile is a Juniper
206
profile.
AAA Commands
Description
service-type
Valid Value(s)
session-timeout
users session.
only)
simultaneous-
logins
ssid
authentication.
only)
YY/MM/DD-HH:MM
network.
207
Description
Valid Value(s)
time-of-day
only)
network.
moMonday
tuTuesday
weWednesday
thThursday
frFriday
saSaturday
suSunday
wkAny day between Monday and Friday
Separate values or a series of ranges (except time
ranges) with commas (,) or a vertical bar (|). Do not
use spaces.
The maximum number of characters is 253.
For example, to allow access only on Tuesdays and
Thursdays between 10 a.m. and 4 p.m., specify the
following: time-of-day tu1000-1600,th1000-1600
time-of-day
only)
(cont.)
time-of-day wk0900-1700,sa2200-0200
(Also see the examples for set user attr on
page 214.)
You can use time-of-day in conjunction with
start-date, end-date, or both.
url
successful WebAAA.
http://www.example.com
only)
user-name
name
208
AAA Commands
Description
Valid Value(s)
vlan-name
VLAN-Name is a Juniper
only)
Examples The following command assigns input access control list (ACL) acl-03 to filter packets
from a user at MAC address 01:02:03:04:05:06:
WLC# set mac-user 01:02:03:04:05:06 attr filter-id acl-03.in
success: change accepted.
The following command restricts a user at MAC address 06:05:04:03:02:01 to network access
between 7 p.m. on Mondays and Wednesdays and 7 a.m. on Tuesdays and Thursdays:
WLC# set mac-user 06:05:04:03:02:01 attr time-of-day
mo1900-1159,tu0000-0700,we1900-1159,th0000-0700
success: change accepted.
See Also
clear mac-user attr on page 175
show aaa on page 218
209
attribute-name value
Name and value of an attribute used to authorize all MAC users in the
group for a particular service or session characteristic. (For a list of
authorization attributes, see Table 31 on page 206.)
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage To change the value of an attribute, enter set mac-usergroup attr with the new value. To
delete an attribute, use clear mac-usergroup attr.
You can assign attributes to individual MAC users and to MAC user groups. If attributes are
configured for a MAC user and also for the group of the MAC user, the attributes assigned to the
individual MAC user take precedence for that user. For example, if the start-date attribute
configured for a MAC user is earlier than the start-date configured for the MAC user group, the
MAC user network access can begin as soon as the user start-date. The MAC user does not need
to wait for the MAC user group start date.
Examples The following command creates the MAC user group eastcoasters and assigns the
group members to VLAN orange:
WLC# set mac-usergroup eastcoasters attr vlan-name orange
success: change accepted.
See Also
clear mac-usergroup attr on page 177
show aaa on page 218
set mobility-profile
Creates a Mobility Profile and specifies the MP and/or wired authentication ports on the WLC
through which any user assigned to the profile is allowed access.
Syntax set mobility-profile name name
{port {none | all | port-list}} | {ap {none | all | apnum}}
210
name
none
Prevents any user to whom this profile is assigned from accessing any MP
access point or wired authentication port on the WLC switch.
all
Allows any user to whom this profile is assigned to access all MP access
ports and wired authentication port on the WLC switch.
AAA Commands
port-list
List of MP access ports or wired authentication ports through which any user
assigned this profile is allowed access. The same port can be used in
multiple Mobility Profile port lists.
ap-num
Defaults No default Mobility Profile exists on the WLC. If you do not assign Mobility Profile
attributes, all users have access through all ports, unless denied access by other AAA servers or
by access control lists (ACLs).
Access Enabled.
History
Version 1.0
Command introduced
Version 2.0
Usage To assign a Mobility Profile to a user or group, specify it as an authorization attribute in one
of the following commands:
set user attr mobility-profile name
set usergroup attr mobility-profile name
set mac-user attr mobility-profile name
set mac-usergroup attr mobility-profile name
To enable the use of the Mobility Profile feature on the WLC switch, use the set mobility-profile
mode command.
Warning: When the Mobility Profile feature is enabled, a user is denied access if assigned a
Mobility-Profile attribute in the local WLC database or RADIUS server when no Mobility Profile of that name
exists on the WLC.
To change the ports in a profile, use set mobility-profile again with the updated port list.
Examples The following commands create the Mobility Profile magnolia, which restricts user
access to port 12; enable the Mobility Profile feature on the WLC switch; and assign the magnolia
Mobility Profile to user Jose.
WLC# set mobility-profile name magnolia port 12
success: change accepted.
WLC# set mobility-profile mode enable
success: change accepted.
WLC# set user Jose attr mobility-profile magnolia
success: change accepted.
The following command adds port 13 to the magnolia Mobility Profile (which is already assigned to
port 12):
211
disable
Specifies that all Mobility Profile attributes are ignored by the WLC.
set user
Configures a user profile in the local database on the MX for a user with a password.
(To configure a user profile in RADIUS, see the documentation for your RADIUS server.)
212
AAA Commands
encrypted
password string
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage The show config command shows the encrypted option with this command, even when
you omit the option. The encrypted option appears in the configuration because MSS
automatically encrypts the password when you create the user (unless you use the encrypted
option when you enter the password).
Although MSS allows you to configure a user password for the special last-resort guest user, the
password has no effect. Last-resort users can never access an MX in administrative mode and
never require a password.
The only valid username of the form last-resort-* is last-resort-wired. The last-resort-wired user
allows last-resort access on a wired authentication port.
Examples The following command creates a user profile for user Nin in the local database, and
assigns the password goody:
WLC# set user Nin password goody
success: User Nin created
The following command assigns the password chey3nne to the admin user:
WLC# set user admin password chey3nne
success: User admin created
The following command changes the password for Nin from goody to 29Jan04:
WLC# set user Nin password 29Jan04
See Also
clear user on page 178
show aaa on page 218
213
attribute-name value
Name and value of an attribute you are using to authorize the user for
a particular service or session characteristic. For a list of authorization
attributes and values that you can assign to network users, see
Table 31 on page 206.
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
MSS Version 1.0
Command introduced.
Usage To change the value of an attribute, enter set user attr with the new value. To delete an
attribute, use clear user attr.
You can assign attributes to individual users and to user groups. If attributes are configured for a
user and also for the group the user belongs, the attributes assigned to the individual user take
precedence for that user. For example, if the start-date attribute configured for a user is earlier
than the start-date configured for the user group the user is in, the user has network access as
soon as the user start-date. The user does not need to wait for the user group start date.
Examples The following command assigns user Tamara to VLAN orange:
WLC# set user Tamara attr vlan-name orange
success: change accepted.
The following command assigns Tamara to the Mobility Profile tulip.
WLC# set user Tamara attr mobility-profile tulip
success: change accepted.
214
AAA Commands
The following command limits the days and times when user Student1 can access the network, to
5 p.m. to 2 a.m. every weekday, and all day Saturday and Sunday:
WLC# set user Student1 attr time-of-day Wk1700-0200,Sa,Su
success: change accepted.
See Also
clear user attr on page 179
show aaa on page 218
time
How long the specified users password is valid. The amount of time
can be specified in days (for example, 30 or 30d), hours (720h), or a
combination of days and hours (30d12h).
group-name
215
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage MSS does not require users to belong to user groups.
To create a user group, user the command set usergroup.
Examples The following command adds user Hosni to the cardiology user group:
WLC# set user Hosni group cardiology
success: change accepted.
See Also
clear user group on page 179
show aaa on page 218
set usergroup
Creates a user group in the local database on the MX for users and assigns authorization
attributes for the group.
(To create user groups and assign authorization attributes in RADIUS, see the documentation for
your RADIUS server.)
Syntax set usergroup group-name attr attribute-name value
group-name
attribute-name value
Name and value of an attribute you are using to authorize all users in
the group for a particular service or session characteristic. For a list of
authorization attributes and values that you can assign to users, see
Table 31 on page 206.
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced.
Usage To change the value of an attribute, enter set usergroup attr with the new value. To delete
an attribute, use clear usergroup attr.
216
AAA Commands
time
How long the passwords for the users in the specified group are valid.
The amount of time can be specified in days (for example, 30 or 30d),
hours (720h), or a combination of days and hours (30d12h).
217
set web-portal
Globally enables or disables WebAAA on an WLC.
Syntax set web-portal {enable | disable}
enable
disable
Defaults Enabled.
Access Enabled.
History
Version 3.0
Command introduced.
Version 4.0
Usage This command disables or reenables support for WebAAA. However, WebAAA has
additional configuration requirements. For information, see the Configuring AAA for Network
Users chapter in the Juniper Mobility System Software Configuration Guide.
Examples To disable WebAAA, type the following command:
WLC# set web-portal disable
success: change accepted.
See Also
clear authentication web on page 173
set service-profile [rsn-id | wpa-ie] auth-fallthru on page 332
set user on page 212
show aaa
Deprecated command.
Syntax show aaa
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 4.0
Web Portal section added, to indicate the state of the WebAAA feature
Version 6.2
Deprecated
show mac-user
Displays a summary or verbose status relating to a specific MAC user or all MAC users.
218
AAA Commands
verbose
Defaults None
Access Enabled
History
Version 6.2
Command introduced
Group
VLAN
----------------
--------
-------
00:11:11:21:11:1
2
Guests
insecure
00:11:11:21:11:*
Guests
red
Group
VLAN
----------------
--------
-------
00:11:11:21:11:1
2
Guests
insecure
00:11:11:21:12
Group:
Guests
VLAN
insecure
Other attributes:
ssid:
Juniper
end-date:
01/08/23-12:00
idle-timeout:
120
acct-interim-interval:
180
MAC:
00:11:11:21:*
Group:
Guests
VLAN
insecure
Other attributes:
ssid:
Juniper
end-date:
01/08/23-12:00
219
idle-timeout:
120
acct-interim-interval:
180
00:11:11:21:*
Group:
Guests
VLAN
insecure
Other attributes:
ssid:
Juniper
end-date:
01/08/23-12:00
idle-timeout:
120
acct-interim-interval:
180
Table 36 describes the fields that can appear in the show mac-user output.
Table 32.show mac-user output
Field
Description
MAC
MAC address
Group
VLAN
Other attributes
ssid
end-date
idle-timeout
acct-interim-interval
show mac-usergroup
Displays summary status for all MAC usergroups or verbose status for a specific MAC usergroup.
Syntax show mac-usergroup [mac-ug-name|verbose]
mac-ug-name
verbose
Defaults None
Access Enabled
220
AAA Commands
Other
Attr. of
Group
MAC Usergroup
to Group
VLAN
------------------
--------------
------
Admin
red
Guests
insecure 4
Guests2
VLAN:
blue
Other attributes:
ssid:
Juniper
end-date:
01/08/23-12:00
idle-timeout:
120
acct-interim-interval:
180
VLAN
------------
--------
00:11:11:21:11:
12
insecure
00:11:11:21:11:
*
red
Admin
VLAN:
red
Other attributes:
ssid:
Juniper
idle-timeout:
120
acct-interim-interval:
180
Description
MAC Usergroup
221
Description
VLAN
MAC
MAC address
Group
VLAN
Other attributes
ssid
end-date
idle-timeout
acct-interim-interval
show user
Displays a summary of users configured on the WLC. For user globs, wildcards (*) are allowed at
the beginning or end of the string.
Syntax show user [name-glob|verbose]
name-glob
verbose
Defaults None
Access Enabled
History Introduced in MSS 6.2.
Examples Use the following command to display information about configured users on the WLC.
WLC# show user john* verbose
User Name
Status
Group
VLAN
--------------
------------
--------
-------
johndoe
disabled
Admin
red
johnsmith
enabled
Admin
red
guest_access
disabled
Guests
red
222
User Name
Status
Group
VLAN
--------------
------------
--------
-------
johndoe
disabled
Admin
red
johnsmith
enabled
Admin
red
AAA Commands
johndoe
Status:
disabled
Password:
iforgot(encypted)
Group:
Admin
VLAN:
red
Password-expires-in:
12 days
Other attributes:
ssid:
Juniper
end-date:
01/08/23-12:00
idle-timeout:
120
acct-interim-interval:
180
User name:
johnsmith
Status:
enabled
Password:
iforgot2(encypted)
Group:
Admin
VLAN:
red
Password-expires-in:
12 days
Other attributes:
None
User name:
guest_access
Status:
disabled
Password:
iforgot3(encypted)
Group:
Admin
VLAN:
red
Password-expires-in:
5 days
Other attributes:
ssid:
Juniper1
end-date:
01/08/20-9:00
idle-timeout:
100
acct-interim-interval:
600
johndoe
Status:
disabled
Password:
iforgot(encypted)
Group:
Admin
VLAN:
red
Password-expires-in:
12 days
Other attributes:
ssid:
Copyright 2011, Juniper Networks, Inc.
Juniper
223
end-date:
01/08/23-12:00
idle-timeout:
120
acct-interim-interval:
180
User name:
johnsmith
Status:
enabled
Password:
iforgot2(encypted)
Group:
Admin
VLAN:
red
Password-expires-in:
12 days
Other attributes:
None
Table 34 describes the fields that can appear in show user output.
Table 34.show user Output
Field
Description
User Name
Status
Password
Group
VLAN
Password-expires-in
Other attributes
show usergroup
Displays summary status for a single user group or all user groups.
Syntax show usergroup ug-name
Defaults None
Access Enabled
History Command introduced in MSS 6.2
Examples
WLC# show usergroup [<ug-name>}
Users Mapped
224
Other
Attr. of
Group
Usergroup
to Group
VLAN
------------------
--------------
------
Admin
red
Guests
red
Guests2
blue
AAA Commands
Admin
VLAN:
red
Password-expires-in:
12 days
Other attributes:
ssid:
Juniper
end-date:
01/08/23-12:00
idle-timeout:
120
acct-interim-interval:
180
VLAN
------------
--------
johndoe
red
johnsmith
red
Guests2
VLAN:
blue
Other attributes:
None
Description
Usergroup
VLAN
Password-expires-in
Other attributes:
SSID
end-date
idle-timeout
The length of time, in seconds, that a user can be idle before logging out of the network.
acct-interm-interval
User Name
VLAN
225
Description
MAC
Group
VLAN
See Also
set accounting {admin | console} on page 182
set authentication admin on page 186
set authentication console on page 188
set authentication dot1x on page 190
set authentication mac on page 194
set authentication web on page 199
Command introduced
Version 4.2
Examples To display the locally stored accounting records, type the following command:
WLC# show accounting statistics
Dec 14 00:39:48
Acct-Status-Type=STOP
Acct-Authentic=0
Acct-Multi-Session-Id=SESS-3-01f82f-520236-24bb1223
Acct-Session-Id=SESS-3-01f82f-520236-24bb1223
User-Name=vineet
AAA_ACCT_SVC_ATTR=2
Acct-Session-Time=551
Event-Timestamp=1134520788
Acct-Output-Octets=3204
Acct-Input-Octets=1691
226
AAA Commands
Acct-Output-Packets=20
Acct-Input-Packets=19
AAA_VLAN_NAME_ATTR=default
Calling-Station-Id=00-06-25-12-06-38
Nas-Port-Id=3/1
Called-Station-Id=00-0B-0E-00-CC-01
AAA_SSID_ATTR=vineet-dot1x
Dec 14 00:39:53
Acct-Status-Type=START
Acct-Authentic=0
User-Name=vineet
Acct-Multi-Session-Id=SESS-4-01f82f-520793-bd779517
Acct-Session-Id=SESS-4-01f82f-520793-bd779517
Event-Timestamp=1134520793
AAA_ACCT_SVC_ATTR=2
AAA_VLAN_NAME_ATTR=default
Calling-Station-Id=00-06-25-12-06-38
Nas-Port-Id=3/1
Called-Station-Id=00-0B-0E-00-CC-01
AAA_SSID_ATTR=vineet-dot1x
Table 37 describes the fields that can appear in show accounting statistics output.
Table 37.show accounting statistics Output
Field
Description
Acct-Status-Type
Acct-Authentic
Location where the user was authenticated (if authentication took place) for the session:
1RADIUS server
2Local MX database
User-Name
Acct-Multi-Session-Id
AAA_TTY_ATTR
Event-Timestamp
Time (in seconds since January 1, 1970) at which the event was triggered. (See
Acct-Output-Octets
227
Description
Acct-Input-Octets
Acct-Output-Packets
Acct-Input-Packets
Vlan-Name
Calling-Station-Id
Nas-Port-Id
Number of the port and radio on the MP through which the session was conducted.
Called-Station-Id
MAC address of the MP through which the client reached the network.
See Also
clear accounting on page 169
set accounting {admin | console} on page 182
show aaa on page 218
show mobility-profile
Displays the named Mobility Profile. If you do not specify a Mobility Profile name, this command
shows all Mobility Profile names and port lists on the WLC.
Syntax show mobility-profile [name]
name
Defaults None.
228
AAA Commands
Access Enabled.
History
Version 1.0
Command introduced
Version 2.0
Ports
=========================
magnolia
AP 12
See Also
clear mobility-profile on page 178
set mobility-profile on page 210
229
230
Informational Note: Juniper Networks recommends that you run the same MSS version on all the WLC
switches in a Mobility Domain and Smart Cluster.
This chapter presents Mobility Domain commands alphabetically. Use the following table to locate
commands in this chapter based on their use.
231
clear mobility-domain
Clears all Mobility Domain configuration and information from an WLC, regardless of whether the
WLC is a seed or a member of a Mobility Domain.
Syntax clear mobility-domain
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage This command has no effect if the WLC is not configured as part of a Mobility Domain.
Examples To clear a Mobility Domain from an WLC within the domain, type the following
command:
MX-20# clear mobility-domain
success: change accepted.
See Also
clear mobility-domain member on page 233
set mobility-domain member on page 235
set mobility-domain mode member seed-ip on page 236
set mobility-domain mode seed domain-name on page 238
232
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage This command has no effect if the WLC member is not configured as part of a Mobility
Domain or the current WLC is not the seed.
Examples The following command clears a Mobility Domain member with the IP address
192.168.0.1:
MX-20# clear mobility-domain member 192.168.0.1
See Also set mobility-domain member on page 235
disable
Defaults None
Access Enabled.
233
History .
MSS 7.0
Command introduced.
MSS 7.3
restore-backup-config deprecated.
Usage You must enable cluster mode on all WLCs that are members of the cluster.
Examples The following command enables cluster mode on an WLC in a mobility domain:
WLC# set cluster mode enable
success: change accepted.
required
234
key hex-bytes
Fingerprint of the public key to use for WLC-WLC security. Specify the key as
16 hexadecimal bytes. Use a colon between each byte, as in the following
example:
00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff
keyfile
Name of the file that contains the key in the above format.
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 5.0
Version 7.1
235
secondary-seed-ip-addr
key hex-bytes
Defaults None.
Access Enabled.
History Introduced in MSS 1.0
Examples The following command sets the current WLC as a nonseed member of the Mobility
Domain whose secondary seed has the IP address 192.168.1.8:
WLC# set mobility-domain mode member seed-ip 192.168.1.8
mode is: member
seed IP is: 192.168.1.8
See Also
clear mobility-domain on page 232
show mobility-domain config on page 240
236
key hex-bytes
Fingerprint of the public key to use for WLC-WLC security. Specify the key as
16 hexadecimal bytes. Use a colon between each byte, as in the following
example:
00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 5.0
Examples The following command sets the current WLC as a nonseed member of the Mobility
Domain whose seed has the IP address 192.168.1.8:
WLC# set mobility-domain mode member secondary-seed-ip 192.168.1.8
See Also
clear mobility-domain on page 232
show mobility-domain config on page 240
set mobility-domain mode secondary-seed domain-name on page 237
primary-seed-ip-addr
Defaults None.
Access Enabled.
History Introduced in MSS 6.0.
Usage You can optionally specify a secondary seed in a Mobility Domain. The secondary seed
provides redundancy for the primary seed switch in the Mobility Domain. If the primary seed
becomes unavailable, the secondary seed assumes the role of the seed WLC. This allows the
Mobility Domain to continue functioning if the primary seed becomes unavailable.
When the primary seed WLC fails, the remaining members form a Mobility Domain, with the
secondary seed taking over as the primary seed WLC.
237
If countermeasures had been in effect on the primary seed, they are stopped while the
secondary seed gathers RF data from the member switches. Once the secondary seed has
rebuilt the RF database, countermeasures can be restored.
VLAN tunnels (other than those between the member switches and the primary seed) continue
to operate normally.
Roaming and session statistics continue to be gathered, providing that the primary seed is
uninvolved with roaming.
When the primary seed is restored, the seed resumes the role of the primary seed WLC in the
Mobility Domain. The secondary seed returns to the role of a regular member of the Mobility
Domain.
Examples The following command configures this WLC as the secondary seed in a Mobility
Domain named Pleasanton:
WLC# set mobility-domain mode secondary-seed domain-name Pleasanton
mode is: secondary-seed
domain name is: Pleasanton
See Also
clear mobility-domain member on page 233
show mobility-domain on page 240
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 4.1
Usage Before you use this command, the current WLC must have an IP address set with the set
system ip-address command. After you enter this command, all Mobility Domain traffic is sent
and received from the specified IP address.
You must explicitly configure only one WLC per domain as the seed. All other WLC switches in the
domain receive their Mobility Domain information from the seed.
Examples The following command creates a Mobility Domain named Pleasanton with the current
WLC as the seed:
238
show cluster
Displays the cluster configuration and resiliency state on a Mobility Domain.
Syntax show cluster
Defaults None
Access Enabled
History Introduced in MSS 7.0.
Examples The following command displays the cluster configuration and resiliency state:
Network Resiliency Cluster Enabled
Mode
: PRIMARY-SEED
Active Seed
: YES
Network is Resilient
show cluster ap
Displays all MPs configured on cluster member.
Syntax show cluster ap
Defaults None
Access Enabled
History Introduced in MSS 7.0.
Examples The following command displays the MPs configured on a cluster member:
WLC# show cluster ap
Primary AP Manager(PAM) and Secondary AP manager(SAM) List:
Flags:L - Cluster Load Balancing; C - Connection Wait; S - Session setup
Wait
AP
PAM WLC IP
to SAM
---- ---------------------------------
SAM WLC IP
AP connected to PAM
--------------- -------------------
3
YES
192.168.254.85
192.168.254.83
YES
12
YES
192.168.254.83
192.168.254.85
YES
AP connected
239
6
YES
192.168.254.85
192.168.254.83
YES
15
YES
192.168.254.85
192.168.254.83
YES
9
YES
192.168.254.85
192.168.254.83
YES
14
YES
192.168.254.83
192.168.254.85
YES
10
YES
192.168.254.83
192.168.254.85
YES
4
YES
192.168.254.85
192.168.254.83
YES
5
YES
192.168.254.85
192.168.254.83
YES
1
YES
192.168.254.85
192.168.254.83
YES
2
YES
192.168.254.85
192.168.254.83
YES
8
YES
192.168.254.83
192.168.254.85
YES
7
YES
192.168.254.85
192.168.254.83
YES
show mobility-domain
On the seed WLC, displays the Mobility Domain status and members.
Syntax show mobility-domain
Defaults None.
Access Enabled.
240
History
Version 1.0
Command introduced
Version 7.0
Mobility1
Description
Flags
Member
IP addresses of the seed WLC and members in the Mobility Domain. * = a remote
site behind a firewall device that supports NAT.
Flags
Model
Version
See Also
clear mobility-domain on page 232
set mobility-domain member on page 235
Copyright 2011, Juniper Networks, Inc.
241
upgrade cluster
Network resiliency enhancements now allows you to perform an in-service software upgrade on a
cluster configuration.
Access Enabled
History Added in MSS 7.1
Usage The upgrade assumes that the old and new versions of MSS are 7.1 and higher.
Syntax upgrade cluster [force]
242
clear network-domain
Clears all Network Domain configuration and information from an WLC, regardless of whether the
WLC is a seed or a member of a Network Domain.
Syntax clear network-domain
Defaults None.
Access Enabled.
History Introduced in MSS 4.1.
Usage This command has no effect if the WLC is not configured as part of a Network Domain.
Examples To clear a Network Domain from an WLC within the domain, type the following
command:
MX-20# clear network-domain
243
member
Defaults None.
Access Enabled.
History Introduced in MSS 4.1.
Usage This command has no effect if the WLC is not configured as part of a Network Domain.
Examples The following command clears the Network Domain member configuration from the
WLC:
MX-20# clear network-domain mode member
success: change accepted.
The following command clears the Network Domain seed configuration from the WLC:
MX-20# clear network-domain mode seed
success: change accepted.
See Also
set network-domain mode member seed-ip on page 245
set network-domain mode seed domain-name on page 247
all
Clears the Network Domain peer configuration for all peers from the WLC.
Defaults None.
Access Enabled.
244
Defaults None.
Access Enabled.
History Introduced in MSS 4.1.
Usage This command has no effect if the WLC is not configured as part of a Network Domain, or
if the WLC is not configured as a member of a Network Domain using the specified Network
Domain seed.
Examples The following command removes the Network Domain seed with IP address
192.168.9.254 from the WLC configuration:
MX-20# clear network-domain seed-ip 192.168.9.254
success: change accepted.
See Also set network-domain mode member seed-ip on page 245
num
Preference for using the specified Network Domain seed. You can specify a
value from 1 through 10. A higher number indicates a greater preference.
245
Defaults None.
Access Enabled.
History Introduced in MSS 4.1.
Usage This command must be entered on an WLC configured as a Network Domain seed.
Examples The following command sets the WLC with IP address 192.168.9.254 as a peer of this
Network Domain seed:
WLC# set network-domain peer 192.168.9.254
success: change accepted.
See Also
clear network-domain on page 243
246
Defaults None.
Access Enabled.
History Introduced in MSS 4.1.
Usage Before you use this command, the current WLC must have an IP address set with the set
system ip-address command. After you enter this command, Network Domain traffic is sent and
received from the specified IP address.
You can configure multiple WLC switches as Network Domain seeds. If you do this, you must
identify them as peers by using the set network domain peer command.
Examples The following command creates a Network Domain named California with the current
WLC as a seed:
WLC# set network-domain mode seed domain-name California
success: change accepted.
See Also
clear network-domain on page 243
show network-domain on page 247
show network-domain
Displays the status of Network Domain seeds and members.
Syntax show network-domain
Defaults None.
Access Enabled.
History Introduced in MSS 4.1.
Examples The output of the command differs based on whether the WLC is a member of a
Network Domain or a Network Domain seed. To display Network Domain status, type the following
command:
WLC# show network-domain
On an WLC that is a Network Domain member, the following output is displayed:
WLC# show network-domain
Member Network Domain name: California
Member
State
Mode
247
UP
MEMBER
10.67.1.200
UP
SEED
On an WLC that is a Network Domain seed, information is displayed about the Network Domains
that WLC is a member, as well as Network Domain seeds with that the WLC has a peer
relationship. For example:
WLC# show network-domain
Network Domain name: California
Peer
State
--------------- ------------10.67.1.200
UP
Member
State
Mode
UP
MEMBER
Description
Peer
State
State of the connection between the WLC and the peer Network Domain seeds:
UP
DOWN
Member
State
Mode
State
Mode
See Also
clear network-domain on page 243
248
249
250
WAN
251
MP-MP Tunneling
MP-WLC security
Static IP Address
Assignment for
Distributed MPs
Radio Profile
Assignment
Updated
SSID Assignment
Radio Properties
Updated
252
Updated
Authentication and
Encryption
Updated
Updated
Updated
Updated
Updated
Updated
Updated
Updated
Updated
253
Updated
Broadcast control
Proxy ARP
Keepalives and
session timers
Transmission retries
RF Auto-Tuning
Updated
Updated
Radio State
Dual Homing
RF Load Balancing
254
Updated
Updated
255
clear ap image
Clears an AirDefense sensor software image file from the configuration on an MP.
Syntax clear ap apnum image
Index value that identifies the MP to the WLC. You can specify a value
between 1 and 9999.
ap apnum
Defaults None.
Access Enabled.
History
Version 5.0
Command introduced.
Version 6.0
Version 6.2
Usage Use this command to configure an MP that was converted to an AirDefense sensor to
revert back to an MP. When you do this, the next time the MP is booted, it becomes a Juniper
Mobility Point.
Examples
Examples The following command causes the AirDefense sensor software file to be cleared from
the configuration of MP 1:
WLC# clear ap 1 image
success: change accepted.
See Also set ap image on page 278
Index value that identifies the MP on the WLC. You can specify a value between 1
and 9999.
Defaults None.
Access Enabled.
256
History
Version 6.0
Version 6.2
Usage A VLAN profile consists of a list of VLANs and tags. When a VLAN profile is applied to an
MP, traffic for the VLANs specified in the VLAN profile is locally switched by the MP instead of
being tunneled back to an WLC.
Use this command to reset the VLAN profile used by the MP for local switching to the default
VLAN profile. Traffic that was locally switched because of an entry in the cleared VLAN profile is
tunneled to an WLC.
When clearing a VLAN profile causes traffic that was locally switched by MPs to be tunneled to an
WLC, the sessions of clients associated with the MPs with the VLAN profile are terminated, and
the clients must re-associate with the MPs.
Examples The following command clears the VLAN profile that was applied to MP 7:
WLC# clear ap 7 local-switching vlan-profile
success: change accepted.
See Also
set ap local-switching mode on page 279
set ap local-switching vlan-profile on page 280
set vlan-profile on page 84
clear ap radio
Disables an MP radio and resets it to its factory default settings.
Syntax clear ap apnum radio {1 | 2 | all}
ap apnum
Index value that identifies the MP on the WLC. You can specify a value
between 1 and 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
radio all
Defaults The clear ap radio command resets the radio to the default settings listed in Table 40
and in Table 42 on page 316.
Table 40.Radio-Specific Parameters
Parameter
Default Value
antenna-
indoors
location
Description
Location of the radio antenna.
This parameter applies only to MP models that support
external antennas.
257
Default Value
Description
antennatype
internal.
external antennas.
max-power
whichever is lower.
channel
802.11b/g6
receives traffic.
mode
disable
radio-profile
802.11 settings
radio profile.
tx-power
(dBm)
Access Enabled
History
Version 1.0
Command introduced.
Version 2.0
Version 5.0
Version 6.0
Version 6.2
Usage When you clear a radio, MSS performs the following actions:
Clears the transmit power, channel, and external antenna setting from the radio.
Removes the radio from its radio profile and places the radio in the default radio profile.
This command does not affect the PoE setting.
Examples The following command disables and resets radio 2 on the MP connected to port 3:
WLC# clear ap 3 radio 2
See Also
258
clear ap boot-configuration
Removes the static IP address configuration for a Distributed MP.
Syntax clear ap apnum boot-configuration
ap apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
Defaults None.
Access Enabled.
History
Version 4.2
Command introduced.
Version 6.0
Version 6.2
Usage When the static IP configuration is cleared for an MP, and an MP is rebooted, it uses the
standard boot process.
Examples The following command clears the static IP address configuration for MP 1.
WLC# clear ap 1 boot-configuration
This will clear specified AP devices. Would you like to continue? (y/n)
[n]y
success: change accepted.
See Also
set ap boot-configuration ip on page 269
set ap boot-configuration vlan on page 275
show ap boot-configuration on page 394
259
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
Defaults None.
Access Enabled.
History
Version 6.0
Command introduced.
Version 6.2
Usage If an MP radio has been assigned to an RF load balancing group, you can use this
command to remove the MP radio from the group.
Examples The following command clears radio 1 on MP 7 from the load balancing group to which
it had been assigned:
WLC# clear ap 7 radio 1 load-balancing group
WLC#
See Also
set load-balancing strictness on page 301
set ap radio load-balancing on page 286
set ap local-switching mode on page 279
show load-balancing group on page 399
260
clear radio-profile
Removes a radio profile or resets one of the profile parameters to the default value.
Syntax clear radio-profile name [parameter]
name
parameter
Defaults If you reset an individual parameter, the parameter is returned to the default value listed
in Table 42 on page 316.
Access Enabled.
History
Version 1.0
Command introduced.
Version 1.1
Version 3.0
Version 4.1
261
Version 4.2
Usage If you specify a parameter, the setting is reset to the default value. The settings of the other
parameters are unchanged and the radio profile remains in the configuration. If you do not specify
a parameter, the entire radio profile is deleted from the configuration. All radios that use this profile
must be disabled before you can delete the profile.
Examples The following commands disable the radios using radio profile rp1 and reset the
beaconed-interval parameter to the default value:
WLC# set radio-profile rp1 mode disable
WLC# clear radio-profile rp1 beacon-interval
success: change accepted.
The following commands disable the radios using radio profile rptest and remove the profile:
WLC# set radio-profile rptest mode disable
WLC# clear radio-profile rptest
success: change accepted.
See Also
set ap radio radio-profile on page 289
set radio-profile mode on page 316
show ap config radio on page 371
show radio-profile on page 400
clear service-profile
Removes a service profile or resets one of the profile parameters to the default value.
Syntax clear service-profile name
name
Defaults None.
Access Enabled.
History
Version 3.0
Command introduced
Version 4.2
Version 7.5
Usage If the service profile is mapped to a radio profile, you must remove it from the radio profile
first. (After disabling all radios that use the radio profile, use the clear radio-profile name
service-profile name command.)
262
Examples The following commands disable the radios using radio profile rp6, remove
service-profile svcprof6 from rp6, then clear svcprof6 from the configuration.
WLC# set radio-profile rp6 mode disable
WLC# clear radio-profile rp6 service-profile svcprof6
success: change accepted.
WLC# clear service-profile svcprof6
success: change accepted.
clear radio-profile on page 261
set radio-profile mode on page 316
show service-profile on page 404
reset ap
Restarts an MP access point.
Syntax reset ap apnum
Index value that identifies the MP on the WLC. You can specify a value
between 1 and 9999.
ap apnum
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 2.0
Version 6.0
Version 6.2
Usage When you enter this command, the MP drops all sessions and reboots.
Warning: Restarting an MP can cause data loss for users who are currently associated with the MP.
set ap auto
Creates a profile for automatic configuration of MPs.
263
Command introduced.
Version 4.2
Version 5.0
Version 7.1
Usage Table 41 lists the configurable profile parameters and the default values. The only
parameter that requires configuration is the profile mode. The profile is disabled by default. To use
the profile to configure Distributed MPs, you must enable the profile using the set ap auto mode
enable command.
The profile uses the default radio profile by default. You can change the profile using the set ap
auto radio radio-profile command. You can use set ap auto commands to change settings for
the parameters listed in Table 41. (The commands are listed in the See Also section.)
Table 41.Configurable Profile Parameters for Distributed MPs
Parameter
Default Value
MP Parameters
bias
high
blink
disable
disable (NO)
none
led-mode
disabled
local-switching
disabled
mode
disabled
persistent
none
power-mode
auto
time-out
25 seconds
tunnel-affinity
upgrade-firmware (boot-download-enable)
enable (YES)
Radio Parameters
264
default
enabled
default
Default Value
radiotype
11g
(or 11b for country codes where 802.11g is not allowed)
Examples The following command creates a profile for automatic Distributed MP configuration:
WLC# set ap auto
success: change accepted.
See Also
set ap auto mode on page 266
set ap auto persistent on page 266
set ap auto radiotype on page 267
set ap bias on page 268
set ap blink on page 269
set ap group on page 278
set ap radio auto-tune max-power on page 283
set ap radio mode on page 288
set ap radio radio-profile on page 289
set ap upgrade-firmware on page 299
265
disable
Command introduced.
Version 6.0
Usage You must use the set ap auto command to create the profile before you can enable it.
Examples The following command enables the profile for automatic Distributed MP configuration:
WLC# set ap auto mode enable
success: change accepted.
See Also
set ap auto on page 263
set ap auto persistent on page 266
set ap auto radiotype on page 267
set ap bias on page 268
set ap blink on page 269
set ap group on page 278
set ap radio auto-tune max-power on page 283
set ap radio mode on page 288
set ap radio radio-profile on page 289
set ap upgrade-firmware on page 299
266
apnum
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
all
Converts the configurations of all Auto-APs being managed by the WLC into
permanent configurations.
Defaults None.
Access Enabled.
History I
Version 4.0
Introduced command.
Version 6.0
Version 6.2
Usage To display the Distributed MP numbers assigned to Auto-MPs, use the show ap status all
command.
Examples The following command converts the configuration of Auto-AP 10 into a permanent
configuration:
WLC# set ap auto persistent 10
success: change accepted.
See Also
set ap auto on page 263
set ap auto mode on page 266
set ap auto radiotype on page 267
Radio type:
11a802.11a
11b802.11b
11g802.11g
Defaults The default radio type for models AP2750, MP-241, and MP-341, and for the 802.11b/g
radios in other models is 802.11g in regulatory domains that support 802.11g, or 802.11b in
regulatory domains that do not support 802.11g.
Access Enabled.
History
Version 4.0
Command introduced.
Version 5.0
Version 6.0
267
Usage If you set the radiotype to 11a and the MP configuration profile is used to configure a
two-radio MP model, radio 1 is configured as an 802.11b/g radio and radio 2 is configured as the
802.11a radio. Because this is the reverse of the standard configuration (where radio 1 is the
802.11a radio and radio 2 is the 802.11b/g radio), the radio 1 settings configured in the MP
configuration profile are applied to radio 2. Likewise, the radio 2 settings configured in the profile
are applied to radio 1. This behavior ensures that settings for radio 1 are always applied to the
80211a radio, regardless of the radio number.
Examples The following command sets the radio type to 802.11b:
WLC# set ap auto radiotype 11b
success: change accepted.
See Also
set ap auto on page 263
set ap auto mode on page 266
set ap auto persistent on page 266
set ap bias
Changes the bias for an MP. Bias is the priority of one MX over other MX switches for booting and
configuring the MP.
Syntax set ap apnum auto bias {high | low}
auto
high
High bias.
low
Low bias.
Command introduced.
Version 2.0
Version 4.0
Version 6.0
Usage High bias is preferred over low bias. Bias applies only to WLC switches indirectly attached
to the MP through an intermediate Layer 2 or Layer 3 network. An MP always attempts to boot on
MP port 1 first, and if an MX is directly attached on MP port 1, the MP always boots from it.
If MP port 1 is indirectly connected to WLC switches through the network, the MP boots from the
WLC with the high bias for the MP. If the bias for all connections is the same, the MP selects the
WLC that has the greatest capacity to add more active MPs. For example, if an MP is dual homed
to two WLC-400 switches, and one of the switches has 50 active MPs while the other WLC has 60
active MPs, the new MP selects the WLC that has only 50 active MPs.
268
If the boot request on MP port 1 fails, the MP attempts to boot over its port 2, using the same
process described above.
The following command changes the bias for a Distributed MP to low:
WLC# set ap 1 bias low
success: change accepted.
See Also show ap config radio on page 371
set ap blink
Enables or disables LED blink mode on an MP to make it easy to identify. When blink mode is
enabled on MP-xxx models, the health and radio LEDs alternately blink green and amber. When
blink mode is enabled on an AP2750, the 11a LED blinks on and off. By default, blink mode is
disabled.
Syntax set ap apnum blink {enable | disable}
ap apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
enable
disable
Command introduced
Version 2.0
Version 4.0
Version 6.0
Version 6.2
Version 7.1
Usage Changing the LED blink mode does not alter operation of the MP access point. Only the
behavior of the LEDs is affected.
Examples The following command enables LED blink mode on the MP access points connected
to ports 3 and 4:
WLC# set ap 3-4 blink enable
success: change accepted.
set ap boot-configuration ip
Specifies static IP address information for a Distributed MP.
269
Index value that identifies the MP on the WLC. You can specify a
value from 1 to 9999.
ip ip-addr
netmask mask-addr
gateway gateway-addr
Defaults By default MPs use DHCP to obtain an IP address, rather than a using a manually
assigned IP address.
Access Enabled.
History
Version 4.2
Command introduced.
Version 6.0
Version 6.2
Usage Normally, Distributed MPs use DHCP to obtain IP address information. In some
installations, DHCP may not be available. In this case, you can assign static IP address
information to the MP, including the MP IP address and netmask, and default gateway.
If the manually assigned IP information is incorrect, the MP uses DHCP to obtain an IP address.
Examples The following command configures MP 1 to use IP address 172.16.0.42 with a 24-bit
netmask, and use 172.16.0.20 as its default gateway:
WLC# set ap 1 boot-configuration ip 172.16.0.42 netmask 255.255.255.0
gateway 172.16.0.20
success: change accepted.
See Also
clear ap boot-configuration on page 259
set ap boot-configuration switch on page 274
set ap boot-configuration vlan on page 275
show ap boot-configuration on page 394
270
Index value that identifies the MP on the WLC. This can be a value
from 1 to 9999.
Defaults Disabled.
Access Enabled.
History Introduced in MSS .
Version 6.0
Command introduced.
Version 6.2
Usage Use this command to enable WLAN mesh services for an Mesh AP. Prior to deploying the
Mesh AP in a final untethered location, you must connect the MP to an WLC and enter this
command to configure the MP for mesh services.
Examples The following command enables WLAN mesh services for MP 7:
WLC# set ap 7 boot-configuration mesh mode enable
success: change accepted.
See Also
set ap boot-configuration mesh ssid on page 273
set service-profile mesh on page 345
show ap mesh-links on page 384
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
passphrase
An ASCII string from 8 to 63 characters long. The string can contain blanks if
you use quotation marks at the beginning and end of the string.
Defaults None.
Access Enabled.
271
History
Version 6.0
Command introduced.
Version 6.2
Usage Use this command to configure the preshared key that a Mesh AP uses to authenticate to
a Mesh Portal AP. You must connect the MP to an WLC and enter this command to configure the
MP for mesh services prior to deploying the Mesh AP in its final untethered location.
MSS converts the passphrase into a 256-bit binary number for system use and a raw hexadecimal
key to store in the WLC configuration. Neither the binary number nor the passphrase is ever
displayed in the configuration. To use PSK authentication, you must enable it and you also must
enable WPA IE or WPA2 IE. .
Examples The following command configures MP 7 to use passphrase
1234567890123<>?=+&% The quick brown fox jumps over the lazy dog when authenticating
with a Mesh Portal AP
WLC# set ap 7 boot-configuration mesh psk-phrase "1234567890123<>?=+&%
The quick brown fox jumps over the lazy dog"
success: change accepted..
See Also
set ap boot-configuration mesh ssid on page 273
set service-profile mesh on page 345
show ap mesh-links on page 384
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
hex
Defaults None.
Access Enabled.
History
272
Version 6.0
Command introduced.
Version 6.2
Usage Use this command to configure the preshared key that a Mesh AP uses to authenticate to
a Mesh Portal AP. You must connect the MP to an WLC and enter this command to configure the
MP for mesh services prior to deploying the Mesh AP to a final untethered location.
MSS converts the hexadecimal number into a 256-bit binary number for system use. MSS also
stores the hexadecimal key in the WLC configuration. The binary number is never displayed in the
configuration. To use PSK authentication, you must enable it and you also must enable WPA IE or
WPA2 IE.
Examples The following command configures MP7 to use a raw PSK to authenticate with a Mesh
Portal AP:
WLC# set ap 7 boot-configuration mesh psk-raw
c25d3fe4483e867d1df96eaacdf8b02451fa0836162e758100f5f6b87965e59d
success: change accepted.
See Also
set ap boot-configuration mesh ssid on page 273
set service-profile mesh on page 345
show ap mesh-links on page 384
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
mesh-ssid
Defaults None.
Access Enabled.
History
Version 6.0
Command introduced.
Version 6.2
Usage You must connect the MP to an WLC and enter this command to specify the mesh SSID
prior to deploying the Mesh AP in its final untethered location. When the MP is booted in an
untethered location, and determines that it has no Ethernet link to the network, it then associates
with the specified mesh-ssid.
Note that when the mesh-ssid is specified, the regulatory domain of the WLC and the power
restrictions are copied to the MP flash memory. This prevents the Mesh AP from operating outside
of regulatory limits after the AP is booted and before the AP receives a complete configuration
from the WLC. Consequently, it is important that the regulatory and antenna information specified
on the WLC actually reflects the locale where the Mesh AP is to be deployed, in order to avoid
regulatory violations.
273
Examples The following command configures MP 7 to attempt to associate with the SSID
wlan-mesh when booted in an untethered location:
WLC# set ap 7 boot-configuration mesh ssid wlan-mesh
success: change accepted.
See Also
set ap boot-configuration mesh mode on page 271
set service-profile mesh on page 345
show ap mesh-links on page 384
Index value that identifies the MP on the WLC. You can specify a
value from 1 to 9999.
switch-ip ip-addr
name name
The fully qualified domain name of the WLC that the Distributed
MP boots from. When both a name and a switch-ip are specified,
the MP uses the name.
dns ip-addr
Defaults By default MPs use the process described in Default MP Boot Process, in the Juniper
Mobility System Software Configuration Guide to boot from an WLC, instead of using a manually
specified WLC.
Access Enabled.
History
Version 4.2
Command introduced.
Version 6.0
Version 6.2
Usage When you specify a boot WLC for a distributed MP to boot from, it boots using the process
described in MP Boot Process Using Static IP Configuration, in the Juniper Mobility System
Software Configuration Guide.
When a static IP address is specified for a Distributed MP, there is no preconfigured DNS
information or DNS name for the WLC that the Distributed MP attempts to use as the boot device.
If you configure a static IP address for a Distributed MP, but do not specify a boot device, then the
WLC must be reachable via subnet broadcast.
274
Examples The following command configures Distributed MP 1 to use an WLC with address
172.16.0.21 as its boot device.
WLC# set ap 1 boot-configuration switch switch-ip 172.16.0.21 mode
enable
success: change accepted.
The following command configures Distributed MP 1 to use the WLC with the name WLCr2 as its
boot device. The DNS server at 172.16.0.1 is used to resolve the name of the WLC.
WLC# set ap 1 boot-configuration switch name WLCr2 dns 172.16.0.1 mode
enable
success: change accepted.
See Also
clear ap boot-configuration on page 259
set ap boot-configuration ip on page 269
set ap boot-configuration vlan on page 275
show ap boot-configuration on page 394
Index value that identifies the MP on the WLC. You can specify a
value from 1 to 9999.
vlan-tag tag-value
The VLAN tag value. You can specify a number from 1 4093.
mode {enable |
disable}
Defaults None.
Access Enabled.
History
Version 4.2
Command introduced.
Version 6.0
Version 6.2
Usage When this command is configured, all Ethernet frames emitted from the Distributed MP are
formatted with an 802.1Q tag with a specified VLAN number. Frames not tagged for this value and
sent to the Distributed MP are ignored.
Examples The following command configures Distributed MP 1 to use VLAN tag 100:
WLC# set ap 1 boot-configuration vlan vlan-tag 100 mode enable
275
set ap fingerprint
Verifies an MP fingerprint on an WLC. If MP-WLC security is required by an WLC, an MP can
establish a management session with the WLC only if you have verified the MP identity by
verifying the fingerprint on the WLC.
Syntax set ap apnum fingerprint fingerprint
ap apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
fingerprint
Defaults None.
Access Enabled.
History
Version 4.0
Introduced command.
Version 6.0
Version 6.2
Usage MPs are configured with an encryption key pair at the factory. The fingerprint for the public
key is displayed on a label on the back of the MP, in the following format:
RSA
aaaa:aaaa:aaaa:aaaa:
aaaa:aaaa:aaaa:aaaa
If an MP is already installed and operating, you can use the show ap status command to display
the fingerprint. The show ap config command lists the MP fingerprint only if the fingerprint has
been verified in MSS. If the fingerprint has not been verified, the fingerprint information in the
command output is blank.
Examples The following example verifies the fingerprint for Distributed MP 8:
WLC# set ap 8 fingerprint
b4:f9:2a:52:37:58:f4:d0:10:75:43:2f:45:c9:52:c3
success: change accepted.
See Also
set ap security on page 291
276
set ap force-image-download
Configures an MP to download a software image from the WLC instead of loading the locally
stored image on the MP.
Syntax set ap auto force-image-download {enable | disable}
ap auto
Configures forced image download for the MP configuration profile. (See set
ap auto on page 263.)
force-imagedownload
enable
force-imagedownload
disable
Command introduced.
Version 6.0
Usage A change to the forced image download option takes place the next time the MP is
restarted.
Even when forced image download is disabled (the default), the MP still checks with the WLC to
verify that the MP has the latest image, and to verify that the WLC is running MSS Version 5.0 or
later.
The MP loads a local image only if the WLC is running MSS Version 5.0 or later and does not have
a different MP image than the one in the MP local storage. If the WLC is not running MSS Version
5.0 or later, or the WLC has a different version of the MP image than the version in the MP local
storage, the MP loads the image from the WLC.
The forced image download option is not applicable to MP models MP-52, MP-101, and MP-122.
Examples The following command enables forced image download on Distributed MP 69:
WLC# set ap 69 force-image-download enable
success: change accepted.
See Also show ap config radio on page 371
277
set ap group
Deprecated in MSS Version 6.0. To configure RF load balancing, see set load-balancing mode
on page 300.
set ap image
Loads an AirDefense sensor software image on an MP.
Syntax set ap apnum image filename
ap apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
filename
Name of the AirDefense sensor software image file. This file is assumed to
have been copied to the WLC.
Defaults None.
Access Enabled.
History
Version 5.0
Command introduced.
Version 6.0
Version 6.2
Usage After the AirDefense sensor software is copied to the WLC, use this command to configure
an MP to load the software. When you do this, the software is transferred to the MP, which then
reboots and comes up as an AirDefense sensor.
Examples The following command causes Distributed MP 1 to load the adconvert.bin file, then
reboot as an AirDefense sensor:
WLC# set ap 1 image adconvert.bin
This will change the file a AP will boot. Would you like to continue?
(y/n) [n] y
See Also clear ap image on page 256
set ap led-mode
Allows you to set the LED behavior on an AP or APs. The setting is active after the AP receives a
configuration from the WLC. The blink command has precedence over this command.
Syntax set [apnum | apnum-range | auto] led-mode {auto | static | off}
auto
static
LEDs do not flash when traffic is on the network. All other LED behavior is
standard.
off
Defaults Auto
278
Access Enabled
History Added in MSS 7.1
Usage Used in configurations where the LED activity is undesired.
Informational Note: The following MPs do not support this command:
MP-71
MP-620
MP-622
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
enable
disable
Command introduced.
Version 6.2
Usage Local switching allows traffic for specified VLANs to be switched by the MP, instead of
tunneling traffic back to an WLC. The VLANs that perform local switching are specified in a VLAN
profile.
Local switching can be enabled on MPs connected to the WLC through an intermediate Layer 2 or
Layer 3 network. Local switching is not supported for MPs that are directly connected to an WLC.
If local switching is enabled on an MP, but no VLAN profile is configured, then a default VLAN
profile is used. The default VLAN profile includes a single VLAN named default that is not tagged.
Examples The following command enables local switching for MP 7:
WLC# set ap 7 local-switching mode enable
success: change accepted.
See Also
set ap local-switching vlan-profile on page 280
set vlan-profile on page 84
279
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
profile-name
Defaults If local switching is enabled on an MP, but no VLAN profile is configured, then a default
VLAN profile is used. The default VLAN profile includes a single VLAN named default that is not
tagged.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage A VLAN profile consists of a list of VLANs and tags. When a VLAN profile is applied to an
MP, traffic for the VLANs specified in the VLAN profile is locally switched by the MP instead of
tunneling the traffic back to an WLC.
When applying a VLAN profile causes traffic that was tunneled to an WLC to be locally switched by
MPs, or vice-versa, the sessions of clients associated with the MPs with the applied VLAN profile
are terminated, and the clients must re-associate with the MPs.
Examples The following command specifies that MP 7 use VLAN profile locals:
WLC# set ap 7 local-switching vlan-profile locals
success: change accepted.
See Also
set ap local-switching mode on page 279
clear ap local-switching vlan-profile on page 256
set vlan-profile on page 84
set ap name
Changes an MP name.
Syntax set ap apnum name name
ap apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
name
Defaults The default name of a directly attached MP is based on the port number of the MP
access port attached to the MP. For example, the default name for an MP on MP access port 1 is
MP01.
Access Enabled.
280
History
Version 1.0
Command introduced
Version 2.0
Version 4.1
Version 6.0
Version 6.2
Examples The following command changes the name of the MP on port 1 to techpubs:
WLC# set ap 1 name techpubs
success: change accepted.
See Also show ap config radio on page 371
set ap power-mode
Specifies a power mode for the AP.
Syntax set ap apnum power-mode {auto | high}
auto
high
Defaults None
Access Enabled
History Added in MSS Version 7.1
Usage This command is used mainly for MPs with 802.11n capabilities.
Examples To set an MP to use the maximum available power, use the following command:
WLC# set ap 3 power-mode high
success: change accepted.
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
radio number
281
indoors
Specifies that the external antenna is installed indoors (inside the building).
outdoors
radio 1
radio 2
antennatype
{ANT1060 | ANT1120 |
ANT1180 | internal}
antennatype
{ANT5060 | ANT5120 |
ANT5180 | internal}
282
antennatype
{ANT-1360-OUT | ANT-5360-O
UT | ANT-5060-OUT | ANT-51
20-OUT | internal}
Defaults All radios use the internal antenna by default, if the MP model has an internal antenna.
The MP-620 802.11b/g radio uses model ANT-1360-OUT by default. The MP-620 802.11a radio
uses model ANT-5360-OUT by default. The MP-262 802.11b/g radio uses model ANT1060 by
default.
Access Enabled.
History
Version 2.1
Version 3.2
Command introduced
Model numbers added for 802.11a external antennas.
Default changed to internal (except for the MP-262).
Version 4.1
Version 6.2
Usage This command applies only to radios on MP models MP-3xx and MP-620 and to the
802.11b/g radio on model MP-262.
Examples The following command configures the 802.11b/g radio on Distributed MP 1 to use
antenna model ANT1060:
WLC# set ap 1 radio 1 antennatype ANT1060
success: change accepted.
See Also show ap config radio on page 371
Index value that identifies the MP on the WLC. You can specify a
value from 1 to 9999.
ap auto
radio 1
283
radio 2
power-level
Defaults The default maximum power setting that RF Auto-Tuning can set on a radio is the
highest setting allowed for the country of operation or highest setting supported on the hardware,
whichever is lower.
Access Enabled.
History
Version 3.0
Command introduced
Version 4.0
Version 6.2
Examples The following command sets the maximum power that RF Auto-Tuning can set on radio
1 on the MP access point on port 7 to 12 dBm.
WLC# set ap 7 radio 1 auto-tune max-power 12
success: change accepted.
See Also
set radio-profile auto-tune power-config on page 306
set radio-profile auto-tune power-interval on page 307
284
ap apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
channel channel
Command introduced
Version 2.0
Version 6.0
Version 6.2
Version 7.3
Usage You can configure the transmit power of a radio on the same command line. Use the
tx-power option.
This command is not valid if dynamic channel tuning (RF Auto-Tuning) is enabled.
Examples The following command configures the channel on the 802.11a radio on the MP access
point connected to port 5:
WLC# set ap 5 radio 1 channel 36
success: change accepted.
The following command configures the channel and transmit power on the 802.11b/g radio on the
MP access point connected to port 11:
WLC# set ap 11 radio 1 channel 1 tx-power 10
success: change accepted.
See Also
set ap radio tx-power on page 290
show ap config radio on page 371
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
radio 1
285
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
enable
disable
Defaults Disabled.
Access Enabled.
History
Version 6.0
Command introduced.
Version 6.2
Usage A Mesh Portal MP can be configured to emit link calibration packets to assist with
positioning the Mesh AP. A link calibration packet is an unencrypted 802.11 management packet of
type Action. When enabled on an MP, link calibration packets are sent at a rate of 5 per second.
The MP-620 is equipped with a connector to which an external RSSI meter can be attached during
installation. When an RSSI meter is attached to an MP-620 and a calibration packet is received,
the MP-620 emits a voltage to the RSSI meter proportional to the received signal strength of the
packet. This can aid in positioning the MP-620 where it has a strong signal to the Mesh Portal AP.
Only one radio on an MP can be configured to send link calibration packets. Link calibration
packets are intended to be used only during installation of MPs; they are not intended to be
enabled on a continual basis.
Examples The following command enables link calibration packets for MP radio 1 on MP 7:
WLC# set ap 7 radio 1 link-calibration mode enable
See Also
set ap boot-configuration mesh ssid on page 273
set service-profile mesh on page 345
show ap mesh-links on page 384
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
enable
disable
286
Access Enabled.
History
Version 6.0
Command introduced.
Version 6.2
Usage By default, RF load balancing is enabled on all MP radios. Use this command to disable or
re-enable RF load balancing for the specified MP radio.
RF load balancing can also be disabled or re-enabled globally with the set load-balancing mode
command. If RF load balancing has been enabled or disabled for a specific MP radio, then the
setting for the individual radio takes precedence over the global setting, if the global setting is
load-balancing mode enabled.
Examples The following command disables RF load balancing for MP radio 1 on MP 7:
WLC# set ap 7 radio 1 load-balancing disable
See Also
set load-balancing strictness on page 301
clear ap radio load-balancing group on page 260
set ap local-switching mode on page 279
show load-balancing group on page 399
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
group name
rebalance
Command introduced.
Version 6.2
287
Usage Assigning radios to specific load balancing groups is optional. When you do this, MSS
considers them to have exactly overlapping coverage areas, rather than using signal strength
calculations to determine their overlapping coverage. MSS attempts to distribute client sessions
across radios in the load balancing group evenly. A radio can be assigned to only one group.
Examples The following command assigns MP radio 1 on MP 7 to load balancing group room1:
WLC# set ap 7 radio 1 load-balancing group room1
WLC#
See Also
set load-balancing strictness on page 301
clear ap radio load-balancing group on page 260
set ap local-switching mode on page 279
show load-balancing group on page 399
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
ap auto
Sets the radio mode for MPs managed by the MP configuration profile. (See
set ap auto on page 263.)
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
mode enable
Enables a radio.
mode sentry
mode disable
Disables a radio.
Command introduced
Version 2.0
Version 4.0
Version 6.0
Version 6.2
Usage To enable or disable one or more radios assigned to a profile, use the set ap radio
radio-profile command. To enable or disable all radios that use a specific radio profile, use the set
radio-profile command.
288
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
radio-profile
name
mode enable
Enables radios on the specified ports with the parameter settings in the
specified radio profile.
mode disable
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 2.0
Version 4.0
Version 6.0
Version 6.2
Usage When you create a new profile, the radio parameters in the profile are set to the factory
default settings.
To enable or disable all radios using a specific radio profile, use set radio-profile.
Copyright 2011, Juniper Networks, Inc.
289
Examples The following command enables radio 1 on MP 5 assigned to radio profile rp1:
WLC# set ap 5 radio 1 radio-profile rp1 mode enable
success: change accepted.
See Also
clear ap radio on page 257
set ap radio mode on page 288
set radio-profile mode on page 316
show radio-profile on page 400
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
tx-power
power-level
Defaults The default transmit power on all MP radio types is the highest setting allowed for the
country of operation or highest setting supported on the hardware, whichever is lower.
Access Enabled.
History
Version 1.0
Command introduced
Version 2.0
Version 3.0
Version 6.0
Version 6.2
Usage You also can configure a radio channel on the same command line. Use the channel
option.
290
This command is not valid if dynamic power tuning (RF Auto-Tuning) is enabled.
Examples The following command configures the transmit power on the 802.11a radio on the MP
access point connected to port 5:
WLC# set ap 5 radio 1 tx-power 10
success: change accepted.
The following command configures the channel and transmit power on the 802.11b/g radio on the
MP access point connected to port 11:
WLC# set ap 11 radio 1 channel 1 tx-power 10
success: change accepted.
See Also
set ap radio channel on page 284
show ap config radio on page 371
set ap security
Sets security requirements for management sessions between an WLC and Distributed MPs.
This feature applies to Distributed MPs only, not to directly connected MPs configured on MP
access ports.
Informational Note: The maximum transmission unit (MTU) for encrypted MP management traffic is 1498
bytes, whereas the MTU for unencrypted management traffic is 1474 bytes. Make sure the devices in the
intermediate network between the WLC switch and Distributed MP can support the higher MTU.
require
Requires all Distributed MPs to have encryption keys that have been verified
in the CLI by an administrator. If an MP does not have an encryption key or
the key has not been verified, the WLC does not establish a management
session with the MP.
optional
Allows MPs to be managed by the switch even if they do not have encryption
keys or their keys have not been verified by an administrator. Encryption is
used for MPs that support it.
none
Command introduced.
Version 6.0
291
Usage This parameter applies to all Distributed MPs managed by the WLC. If you change the
setting to required, the WLC requires Distributed MPs to have encryption keys. The WLC also
requires their fingerprints to be verified in MSS. When MP security is required, an MP can
establish a management session with the WLC only if its fingerprint has been verified by you in
MSS.
A change to MP security support does not affect management sessions that are already
established. To apply the new setting to an MP, restart the MP.
Examples The following command configures an WLC to require Distributed MPs to have
encryption keys:
WLC# set ap security require
See Also
set ap fingerprint on page 276
show ap config radio on page 371
show ap status on page 385
set ap tunnel-affinity
The MP-MP tunneling feature extends the WLC-WLC tunnel feature to allow MPs with
local-switching enabled to create and terminate client VLAN tunnels. Therefore, a VLAN is not
required on every MP.
Defaults None
Access Enabled
History Added in MSS Version 7.1.
Syntax set ap [apnum |auto] tunnel-affinity affinity
apnum
auto
tunnel-affinity
affinity
292
auto
enable
disable
Defaults This feature is disabled by default. When this configuration is changed, affected session
are dropped and then reconnected in the correct mode. If tunnel mode is enabled and local
switching is already enabled on the WLA, then overlay sessions are terminated and then
reconnected in order to establish overlay sessions. Tunnel mode only takes effect if local switching
is enabled on the WLA.
Access Enabled
History Introduced in MSS Version 7.5
Examples
To view a WLA configuration with tunnel mode enabled, use the show ap config command:
MX# show ap 4 config 4
AP 4 (AP04)
Model: WLA522
Mode:
.............
.............
Fingerprint:
Communication timeout: 25
Location:
Contact:
Vlan-profile: mesh
AP tunnel: enabled
Radio 1 (802.11g)
293
The number of the WLA to configure for WAN data path encryption.
auto
enable
disable
Defaults Data path encryption is disabled by default. It can only be enabled if the global ap
security option is set to required or optional.Data path encryption is disabled by default. It can only
be enabled if the global ap security option is set to required or optional.
Access Enabled
History Introduced in MSS Version 7.5
No data path encryption on the domain. This is the default value to allow for
backward compatibility between WLCs.
Optional
A connection may or may not have data path encryption configured. A tunnel
can be created to a peer WLC that does not support data path encryption.
Required
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples In cluster mode, the primary seed (PS) ensures that an WLA with data security enabled
is not assigned a PAM or SAM that does not support this feature. If such a WLC is not located on
the network, the WLA remains unassigned. You can display this information using the following
command:
MX# show cluster ap
Total APs: [2], APs connected to PAM: [2], APs connected to SAM: [2]
294
SAM WLC IP
AP connected to PAM
AP connected
---------------------------------------------------------------------------2
10.7.116.108
NO
3 0.0.0.0
[U]NO
10.7.116.106
YES
0.0.0.0
[U]NO
If the data path encryption configuration is changed after a WLA is operational, the change is
applied immediately. This may affect connectivity on existing sessions while the WLA and WLC
synchronize the changes on the network. If you make changes to the configuration, a warning is
displayed at the command prompt:
MX# set ap 3 remote-ap data-security mode enable
This may cause the AP to reboot, are you sure? (y/n)[n]
The following commands display the configuration of the WLAs:
MX# show ap config verbose
AP 1 (AP01)
Model:
WLA522
Mode:
remote
Bias:
high
Options:
led-auto
upgrade-firmware, data-security,
The current data security status of the WLA is displayed using the show
ap status
command:
Flag
Uptime
IP Address
Model
MAC Address
Radio 1
Radio
----------------------------------------------------------------------------
295
3
o--E
10.7.254.10
44/17
01d23h
WLA522
00:0b:0e:1a:24:40 E
1/4
To show the status of a WLA using a verbose output, use the following command:
MX# show ap status verbose
AP: 3 Name:AP03
Model: Juniper WLA522, Rev: A, Serial number: 0574100817
F/W1: 5.7
F/W2 : 5.7
S/W : 7.5.0.0
Boot S/W: 7.5.0.0
IP-addr/mask: 10.7.254.10/255.255.0.0 (DHCP,vlan NET41IP40),
Fingerprint: 8f:de:cd:8d:1e:7d:da:7b:c7:32:fe:74:57:51:af:db
Port 1 MAC: 00:0b:0e:50:11:00, link 100/full, POE: 802.3af
Port 2 MAC: 00:0b:0e:50:11:01, link: down, POE:none
State: operational (encrypted, data-encrypted)
Uptime: 3 days, 5 hours, 12 minutes, 59 seconds
Radio 1 Type: 802.11g, State: configure succeeded [Enabled]
Antenna type: INTERNAL
Every WLC publishes domain data-security information to the members of the mobility domain.
This information is used for tunnel endpoint selection by the mobility domain members. To display
information about tunnels on the network, use the following command:
MX# show tunnel
VLAN
Address
Local Address
Remote
State
Port
LVID
RVID
Ver
---------------------------------------------------------------------------green
*
1025
10.2.8.102
3584
1
10.8.116.105
Up
The state field now includes an asterisk (*) to indicate that the tunnel is encrypted.
296
During normal operation, the WLA sends announcements and pings to the WLC and receives
acknowledgements in return. If the acknowledgements are not returned within a certain period, the
WLA determines the status of the WLC. An initial evaluation period is used to confirm the outage
and the evaluation period has a range from 25 seconds, the default value, to a maximum of 5
minutes. Once outage is confirmed, the configured evaluation period determines the keepalive
interval of the pings sent to detect when the WAN link is active on the network.
Once the WAN link becomes available again, the WLA synchronizes the client session state with
the WLC and the client sessions continue to remain active until the WLC is ready to handle new
client associations.
Syntax set ap {apnum | auto} remote-ap wan-outage mode {enable | disable}
apnum
auto
enable
eval-period value
disable
Defaults The default setting is 0 (stay in outage mode indefinitely) and the range is from 0 to 120
hours (5 days). This period indicates the maximum length of time that a WLA remains in outage
mode.
Access Enabled
History Introduced in MSS Version 7.5
Examples To configure the maximum duration of a WAN outage before a WLA reboots, use this
command:
MX# set ap {apnum | auto} remote-ap wan-outage extended-timeout duration
Use a day-hour format to set the duration. For example,
MX# set ap 2 remote-ap wan-outage extended-timeout 3
The duration is three (3) days.
MX# set ap 2 remote-ap wan-outage extended-timeout 6h
The duration is six (6) hours.
When the duration has elapsed, the WLC clears all of the WLA state and session information, and
the WLA clears the session information and may reboot.
In addition to configuring the extended timeout period, you can configure a timer to periodically
check the state of the WLC connection on the network. Use the following commands to configure
this parameter:
MX# set ap {apnum | auto} remote-ap wan-outage eval-period value
To display the remote WLA configuration, type the following command:
MX# show ap config apnum
297
For example, to display the configuration of the remote WLA 5002, type the following command:
MX# show ap config 5002
AP 5002 (AP5002)
Model: WLA522
Mode: remote
Bias: high
Options: upgrade-firmware, led-auto
Connection: network
Serial number: 5002
Fingerprint:
Communication timeout: 25
Extended timeout: 2h
Evaluation timeout: 5
Location:
Contact:
Description:
Vlan-profile:
Tunnel affinity:
The status for a remote WLA in outage mode is displayed using the following command:
MX# show ap status
Flags: o= operational (219), c = configure (0), d = download (0),
b = boot (0), a = auto AP, m = mesh AP, p/P = mesh portal (ena/actv),
r = redundant (192), z = remote AP in outage, i = insecure, e =
encrypted,
u = unencrypted
Radio: E = enabled - 20MHz channel, S = sentry, W/w = enabled - 40MHz
wide channel (HTplus/HTminus), D = admin disabled, U = mesh uplink
IP Address: * = AP behind NAT
AP
Flag
2 Uptime
IP Address
Model
MAC Address
Radio 1
Radio
------------------------------------------------------------------------------5002
36/18
oz-i
10.41.43.212
03d05h
WLA522
00:0b:0e:50:02:00
1/21
5003
36/18
o--1
10.41.40.56
03d05h
WLA522
00:0b:0e:50:02:00
1/21
To show details about the status of the remote WLA, use the following command:
MX# show ap status 5002 verbose
298
set ap upgrade-firmware
Disables or reenables automatic upgrade of an MP boot firmware.
Syntax set ap auto upgrade-firmware {enable | disable}
ap auto
enable
disable
Command introduced
Version 2.0
Version 4.0
Version 6.0
Usage When the feature is enabled on an MX port, an MP connected to that port upgrades the
boot firmware to the latest version stored on the MX.
Examples The following command disables automatic firmware upgrades on the MP connected to
port 9:
WLC# set ap 9 upgrade-firmware disable
See Also show ap config radio on page 371
299
set band-preference
Configures MSS to steer clients that support both the 802.11a and 802.11b/g radio bands to a
specific radio on an MP for the purpose of RF load balancing.
Syntax set band-preference {none | 5GHz | 2GHz}
none
When a client supports both 802.11a and 802.11b/g radio bands, does not
steer the client to a specific MP radio.
5GHz
When a client supports 802.11b/g radio band, steers the client to the 5 GHz
radio.
2GHz
When a client supports both 802.11a radio bands, steers the client to the 2
GHz radio.
Defaults By default, clients are not steered to specific MP radios for RF load balancing.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage Use this command to steer clients that support both the 802.11a and 802.11b/g bands, to a
specific radio on an MP for the purpose of load balancing. This global band-preference option
controls the degree that an MP with two radios attempts to conceal one of its radios from a client
with the purpose of steering the client to the other radio.
Examples The following command steers clients that support the 802.11a band to the 802.11a
radio on an MP:
WLC# set band-preference 2GHz
See Also
set load-balancing strictness on page 301
set load-balancing mode on page 300
set ap radio load-balancing on page 286
show load-balancing group on page 399
disable
300
If RF load balancing has been enabled or disabled for a specific MP radio, then the setting for the
individual radio takes precedence over the global setting.
Examples The following command globally disables RF load balancing for all MP radios managed
by the WLC:
WLC# set load-balancing mode disable
WLC#
See Also
set load-balancing strictness on page 301
set band-preference on page 300
set ap radio load-balancing on page 286
show load-balancing group on page 399
No clients are denied service. New clients can be steered to other MPs, but
only to the extent that service can be provided to all clients.
med
Overloaded radios steer new clients to other MPs more strictly than the low
option. Clients attempting to connect to overloaded radios may be delayed
several seconds.
high
Overloaded radios steer new clients to other MPs more strictly than the med
option. Clients attempting to connect to overloaded radios may be delayed
up to a minute.
max
Defaults Low.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage When performing RF load balancing, MSS may attempt to steer clients to less-busy radios
in a load-balancing group. To do this, MSS makes MP radios with heavy client loads less visible to
new clients, causing them to associate with MP radios that have a lighter load.
Use this command to specify how strictly MSS attempts to keep the client load balanced across
the MP radios in the load-balancing group. When low strictness is specified (the default), MSS
makes heavily loaded MP radios less visible in order to steer clients to less-busy MP radios, but
ensures that even if all the MP radios in the group are heavily loaded, clients are not denied
service.
301
At the other end of the spectrum, when max strictness is specified, if an MP radio has reached the
maximum client load, MSS makes the MP invisible to new clients, and new clients attempt to
connect to other MP radios. In the event that all the MP radios in the group have reached the
maximum client load, then no new clients can to connect to the network.
Examples The following command sets the RF load balancing strictness to the maximum setting:
WLC# set load-balancing strictness max
Success: strictness set to "MAX"
See Also
set load-balancing mode on page 300
set band-preference on page 300
set ap radio load-balancing on page 286
show load-balancing group on page 399
11n channel-width-na
Defaults None
Access Enabled
History Introduced in MSS 7.0
Examples Use the following command to set the channel width to 40 MHz:
WLC# set radio-profile boardroom 11n channel-width-na 40MHz
302
The name of the radio profile to configure the 802.11a channel range.
lower-bands
Only the lower channels are available for the 802.11a radio: 36, 40, 44, 48,
52, 56, 60, or 64.
all-bands
All 802.11a channels are available for the 802.11a radio: 36. 40, 44, 48, 52,
56, 60, 64, 149, 153, 157, and 161.
Defaults lower-bands
Access Enabled
History
Version 6.0
Command introduced.
enable
disable
Command introduced.
Version 5.0
Version 6.0
Version 7.0
Usage If you disable RF Auto-Tuning for channels, MSS does not dynamically set the channels
when radios are first enabled and also does not tune the channels during operation.
Copyright 2011, Juniper Networks, Inc.
303
If RF Auto-Tuning for channels is enabled, MSS does not allow you to manually change channels.
Even when RF Auto-Tuning for channels is enabled, MSS does not change the channel on radios
that have active client sessions, unless you use the ignore-clients command.
Examples The following command disables dynamic channel tuning for radios in the rp2 radio
profile:
WLC# set radio-profile rp2 auto-tune channel-config disable
success: change accepted.
See Also
set ap radio channel on page 284
set radio-profile auto-tune channel-holddown on page 304
set radio-profile auto-tune channel-interval on page 305
set radio-profile auto-tune power-config on page 306
show radio-profile on page 400
rate
seconds
305
enable
disable
Defaults None
Access Enabled
History Introduced in MSS 6.0.
enable
Configures radios to dynamically set power levels when the MPs are started.
disable
306
seconds
Number of seconds MSS waits before changing radio power levels to adjust
to RF changes, if needed. You can specify from 1 to 65535 seconds.
307
Defaults By default, when RF Auto-Tuning of power is enabled, power settings continue change
dynamically based on network conditions.
Access Enabled.
History Introduced in MSS Version 5.0.
Usage To save this command and the static power configuration commands created when you
enter this command, save the configuration.
Examples The following command locks down the power settings for radios in radio profile rp2:
WLC# set radio-profile rp2 auto-tune power-lockdown
success: change accepted.
See Also
set ap radio auto-tune max-power on page 283
set radio-profile auto-tune channel-lockdown on page 305
set radio-profile auto-tune power-config on page 306
set radio-profile auto-tune power-interval on page 307
set radio-profile auto-tune power-ramp-interval on page 308
show radio-profile on page 400
seconds
308
Examples The following command changes the power ramp interval for radios in radio profile rp2
to 120 seconds:
WLC# set radio-profile rp2 auto-tune power-ramp-interval 120
success: change accepted.
See Also
set ap radio auto-tune max-power on page 283
set radio-profile auto-tune power-config on page 306
set radio-profile auto-tune power-interval on page 307
set radio-profile auto-tune power-lockdown on page 308
show radio-profile on page 400
interval
max-utilization
Set maximum admission control limit for background traffic. You can
configure a percentage from 1 to 100 percent.
percentage
Copyright 2011, Juniper Networks, Inc.
309
mode
policing
Defaults None
Access Enabled
History Introduced in MSS Version 7.0.
max-utilizatio Set maximum admission control limit for best effort traffic. You can configure
a percentage from 1 to 100 percent.
n
percentage
mode
policing
Defaults None
Access Enabled
Introduced in MSS Version 7.0.
max-utilization
percentage
Set maximum admission control limit for video traffic. You can
configure a percentage from 1 to 100 percent.
mode
policing
Defaults None
Access Enabled
History Introduced in MSS Version 7.0.
310
max-utilization
percentage
Set maximum admission control limit for voice traffic. You can
configure a percentage from 1 to 100 percent.
mode
policing
Defaults None
Access Enabled
History Introduced in MSS Version 7.0.
profile-name
all
rogue
none
Command introduced.
Version 4.1
Version 7.0
Examples The following command enables countermeasures in radio profile radprof3 for rogues
only:
WLC# set radio-profile radprof3 countermeasures rogue
Copyright 2011, Juniper Networks, Inc.
311
Command introduced.
Informational Note: The DTIM interval applies to both the beaconed SSID and the nonbeaconed SSID.
interval
Number of times the DTIM is transmitted after every beacon. You can enter
a value from 1 through 31.
Defaults By default, MPs send the DTIM once after each beacon.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You must disable all radios using a radio profile before you can change parameters in the
profile. Use the set radio-profile mode command.
The DTIM interval does not apply to unicast frames.
312
Examples The following command changes the DTIM interval for radio profile rp1 to 2:
WLC# set radio-profile rp1 dtim-interval 2
success: change accepted.
See Also
set radio-profile mode on page 316
show radio-profile on page 400
weighted-fair-queuing
enable
weighted-fair-queuing
disable
service-profile-name
weight
Defaults None
Access Enabled
History Introduced in MSS Version 6.2.
Examples To configure weighted queuing for a service and radio profile, use the following
command:
WLC# set radio-profile wireless weighted-fair-queuing enable weight
mp_conference 25
success: change accepted.
313
threshold
Maximum frame length, in bytes. You can enter a value from 256 through
2346.
314
time
Number of milliseconds. You can enter a value from 500 (0.5 second)
through 250,000 (250 seconds).
Defaults The default maximum receive threshold for MP radios is 2000 ms (2 seconds).
Access Enabled.
History Introduced in MSS Version 1.0.
Usage You must disable all radios that are using a radio profile before you can change
parameters in the profile. Use the set radio-profile mode command.
Examples The following command changes the maximum receive threshold for radio profile rp1 to
4000 ms:
WLC# set radio-profile rp1 max-rx-lifetime 4000
success: change accepted.
See Also
set radio-profile mode on page 316
set radio-profile mode on page 316
show radio-profile on page 400
315
enable
disable
sentry
Defaults Each radio profile has a set of properties with factory default values that you can change
with the other set radio-profile commands in this chapter. Table 42 lists the parameters controlled
by a radio profile and the default values.
Table 42.Defaults for Radio Profile Parameters
Radio Behavior When Parameter Set To Default
Parameter
Default Value
Value
active-scan
enable
auto-tune
enable
beacon-interval
100
countermeasures
Not configured
dtim-interval
frag-threshold
2346
max-rx-lifetime
2000
max-tx-lifetime
2000
preamble-length
short
qos-mode
wmm
rfid-mode
disable
316
Default Value
Value
rts-threshold
2346
service-profile
wmm-powersave
No service
profiles defined
disable
Access Enabled.
History
Version 1.0
Version 3.0
Command introduced
Parameters that no longer apply to radio profiles in MSS Version 3.0
removed:
auth-dot1x
auth-psk
beaconed-ssid
cipher-ccmp
cipher-tkip
cipher-wep104
cipher-wep40
clear-ssid
crypto-ssid
psk-phrase
psk-raw
shared-key-auth
tkip-mc-time
wep key-index
wep active-multicast-index
wep active-unicast-index
wpa-ie
auto-tune and service-profile parameters added.
317
Version 4.2
Version 5.0
Parameters added:
rfid-mode
wmm-powersave
Usage Use the command without any optional parameters to create new profile. If the radio profile
does not already exist, MSS creates a new radio profile. Use the enable or disable option to
enable or disable all the radios using a profile. To assign the profile to one or more radios, use the
set ap radio radio-profile command.
To change a parameter in a radio profile, you must first disable all the radios in the profile. After
you complete the change, you can reenable the radios.
To enable or disable specific radios without disabling all of them, use the set ap radio command.
Examples The following command configures a new radio profile named rp1:
WLC# set radio-profile rp1
success: change accepted.
The following command enables the radios that use radio profile rp1:
WLC# set radio-profile rp1 mode enable
The following commands disable the radios that use radio profile rp1, change the beacon interval,
then reenable the radios:
WLC# set radio-profile rp1 mode disable
WLC# set radio-profile rp1 beacon-interval 200
WLC# set radio-profile rp1 mode enable
The following command enables the WPA IE on MP radios in radio profile rp2:
WLC# set radio-profile rp2 wpa-ie enable
success: change accepted.
See Also
set ap radio mode on page 288
set ap radio radio-profile on page 289
show ap config radio on page 371
show radio-profile on page 400
318
long
short
Command introduced.
Version 1.1
Usage Changing the preamble length value affects only the support advertised by the radio.
Regardless of the preamble length setting (short or long), an 802.11b/g radio accepts and can
generate 802.11b/g frames with either short or long preambles.
If a client associated with an 802.11b/g radio uses long preambles for unicast traffic, the MP still
accepts frames with short preambles but does not transmit frames with short preambles. This
change also occurs if the access point overhears a beacon from an 802.11b/g radio on another
access point that indicates the radio has clients that require long preambles.
You must disable all radios that use a radio profile before you can change parameters in the
profile. Use the set radio-profile mode command.
Examples The following command configures 802.11b/g radios that use the radio profile rp_long
to advertise support for long preambles instead of short preambles:
WLC# set radio-profile rp_long preamble-length long
success: change accepted.
See Also
set radio-profile mode on page 316
show radio-profile on page 400
319
wmm
Classifies and marks traffic based on 802.1p and DSCP, and optimizes
forwarding prioritization of MP radios for Wi-Fi Multimedia (WMM).
enable
Enables data rate enforcement for the radios in the radio profile.
disable
Disables data rate enforcement for the radios in the radio profile.
320
Mandatory Valid 802.11 transmit rates that clients must support in order to associate with the
MP
Disabled Valid 802.11 transmit rates are disabled. MPs do not transmit at the disabled rates
Standard Valid 802.11 transmit rates that are not disabled and are not mandatory
By default, the rate set is not enforced, meaning that a client can associate with and transmit data
to the MP using a disabled data rate, although the MP does not transmit data back to the client at
the disabled rate.
You can use this command to enforce the data rates, which means that a connecting client must
transmit at one of the mandatory or standard rates in order to associate with the MP. When data
rate enforcement is enabled, clients transmitting at the disabled rates are not allowed to associate
with the MP.
This command is useful if you want to completely prevent clients from transmitting at disabled data
rates. For example, you can disable slower data rates so that clients transmitting at these rates do
not consume bandwidth on the channel at the expense of clients transmitting at faster rates.
Examples The following command enables data rate enforcement for radio profile rp1:
WLC# set radio-profile rp1 rate-enforcement mode enable
success: change accepted.
See Also
set service-profile transmit-rates on page 354
show ap counters on page 374
regulatory
operating
all
Defaults None
Access Enabled
History Added in MSS Version 6.2.
Examples To scan only operating channels on radio profile, gofish, use the following command:
WLC> set radio-profile gofish rf-scanning channel-scope operating
success: change accepted.
321
The radio scans once per predefined time and audits the packets on the
wireless network. The default time is 1 second.
active
The radio actively sends probes to other channels and then audits the
packets on the wireless network.
Defaults None
Access Enabled
History Added in MSS Version 6.2
Examples To configure active rf-scanning mode for radio profile gofish, use the following
command:
WLC> set radio-profile gofish rf-scanning mode active
success: change accepted.
enable
disable
threshold
Maximum frame length, in bytes. You can enter a value from 0 through 65535.
323
Defaults By default, aradio profile does not have a service profile associated with it. In this case,
the radios in the radio profile use the default settings for parameters controlled by the service
profile. Table 43 lists the parameters controlled by a service profile and the default values.
Table 43.Defaults for Service Profile Parameters
Parameter
Default Value
attr
No attributes configured
auth-dot1x
enable
none
auth-psk
disable
beacon
enable
bridging
none
cac-mode
none
profile.
14
cipher-ccmp
disable
cipher-tkip
enable
cipher-wep104
disable
cipher-wep40
disable
Does not use WEP with 40-bit keys to encrypt traffic sent to
WPA clients.
cos
dhcp-restrict
disable
Does not restrict a clients traffic to only DHCP traffic while the
client is being authenticated and authorized.
idle-client-probing
enable
keep-initial-vlan
disable
load-balancing-exempt
none
long-retry-count
324
Default Value
no-broadcast
disable
max-bw
none
mesh
none
proxy-arp
disable
none
psk-phrase
No passphrase defined
psk-raw
No preshared key
defined
disable
rsn-ie
disable
short-retry-count
ssid-name
Juniper
ssid-type
crypto
tkip-mc-time
60000
transmit-rates
802.11a:
mandatory:
6.0,12.0,24.0
mandatory rates.
beacon-rate: 6.0
multicast-rate: auto
Sends multicast data at the highest rate that can reach all
disabled: none
802.11b:
mandatory: 1.0,2.0
beacon-rate: 2.0
Accepts frames from clients at all valid data rates. (No rates
are disabled by default.)
multicast-rate: auto
disabled: none
802.11g:
mandatory:
1.0,2.0,5.5,11.0
beacon-rate: 2.0
multicast-rate: auto
disabled: none
user-idle-timeout
180
325
Default Value
web-portal-acl
portalacl
set to web-portal.
unconfigured.
web-portal-acl setting.
web-portal-form
Not configured
web-portal-logout
none
timeout
wep key-index
No keys defined
wep active-multicast-index
wep active-unicast-index
wpa-ie
disable
Access Enabled.
History Introduced in MSS Version 3.0.
Version 3.0
Command introduced.
Version 7.0
Usage You must configure the service profile before you can map it to a radio profile. You can
map the same service profile to more than one radio profile.
You must disable all radios that use a radio profile before you can change parameters in the
profile. Use the set radio-profile mode command.
Examples The following command maps service-profile wpa_clients to radio profile rp2:
WLC# set radio-profile rp2 service-profile wpa_clients
success: change accepted.
See Also
set service-profile attr on page 330
set service-profile [rsn-ie | wpa-ie] auth-dot1x on page 331
set service-profile [rsn-id | wpa-ie] auth-fallthru on page 332
set service-profile [rsn-ie | wpa-ie] auth-psk on page 333
set service-profile beacon on page 334
326
327
snoop-filter
Defaults None
Access Enabled
History Added in MSS Version 7.0.
enable
Enables U-APSD.
disable
Disables U-APSD.
328
a-mpdu-max-length
a-msdu-max-length
frame-aggregation
mode-na
mode-ng
Command introduced.
Version 7.1
timeout
Configures the length of in seconds. You can set this to a value from
20 to 300.
Defaults None
Access Enable
Copyright 2011, Juniper Networks, Inc.
329
attribute-name value
Name and value of an attribute you are using to authorize SSID users
for a particular service or session characteristic.
For a list of authorization attributes and values that you can assign to
network users, see Table 31 on page 206. All of the attributes listed in
Table 31 can be used with this command except ssid.
Defaults By default, a service profile does not have any authorization attributes set.
Access Enabled.
History Introduced in MSS 4.1.
MSS Version 4.1
Command introduced.
Usage To change the value of a default attribute for a service profile, use the set service-profile
attr command and specify a new value.
The SSID default attributes are applied in addition to any attributes supplied for the user by the
RADIUS server or the local database. When the same attribute is specified both as an SSID
default attribute and through AAA, then the attribute supplied by the RADIUS server or the local
database takes precedence over the SSID default attribute. If a location policy is configured, the
location policy rules also take precedence over SSID default attributes. The SSID default attributes
serve as a fallback when neither the AAA process, nor a location policy, provides them.
For example, a service profile might be configured with the service-type attribute set to 2. If a user
accessing the SSID is authenticated by a RADIUS server, and the RADIUS server returns the
vlan-name attribute set to orange, then that user has a total of two attributes set: service-type
and vlan-name.
If the service profile is configured with the vlan-name attribute set to blue, and the RADIUS server
returns the vlan-name attribute set to orange, then the attribute from the RADIUS server takes
precedence; the user is placed in the orange VLAN.
You can display the attributes for each connected user and if they are set through AAA or through
SSID defaults by entering the show sessions network verbose command. You can display the
configured SSID defaults by entering the show service-profile command.
Examples The following command assigns users accessing the SSID managed by service profile
sp2 to VLAN blue:
WLC# set service-prof sp2 attr vlan-name blue
330
enable
disable
Defaults When the WPA IE is enabled, 802.1X authentication of WPA clients is enabled by
default. If the WPA IE is disabled, the auth-dot1x setting has no effect.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage This command does not disable dynamic WEP for non-WPA clients. To disable dynamic
WEP for non-WPA clients, enable the WPA IE (if not already enabled) and disable the 40-bit WEP
and 104-bit WEP cipher suites in the WPA IE, if they are not already disabled.
To use 802.1X authentication for WPA clients, you also must enable the WPA IE.
If you disable 802.1X authentication of WPA clients, the only method available for authenticating
the clients is preshared key (PSK) authentication. To use this, you must enable PSK support and
configure a passphrase or key.
Examples The following command disables 802.1X authentication for WPA clients that use service
profile wpa_clients:
WLC# set service-profile wpa_clients auth-dot1x disable
success: change accepted.
See Also
Copyright 2011, Juniper Networks, Inc.
331
none
Denies authentication and prohibits the user from accessing the SSID.
The fallthru authentication type none is different from the authentication
method none you can specify for administrative access. The fallthru
authentication type none denies access to a network user. In contrast, the
authentication method none allows access to the WLC by an administrator.
(See set authentication admin on page 1186 and set authentication
console on page 1188.)
web-portal
Serves the user a web page from the WLC nonvolatile storage for secure
login to the network.
Command introduced.
Version 4.0
332
Usage The last-resort fallthru authentication type allows any user to access any SSID managed
by the service profile. This method does not require the user to provide a username or password.
Use the last-resort method only if none of the SSIDs managed by the service profile require
secure access.
The web-portal authentication type also requires additional configuration items. (See the
Configuring AAA for Network Users chapter of the Juniper Mobility System Software Users
Guide.)
Examples The following command sets the fallthru authentication type for SSIDS managed by the
service profile rnd_lab to web-portal:
WLC# set service-profile rnd_lab auth-fallthru web-portal
success: change accepted.
See Also
set web-portal on page 218
set service-profile web-portal-form on page 359
show service-profile on page 404
enable
disable
Defaults When the WPA IE is enabled, PSK authentication of WPA clients is enabled by default. If
the WPA IE is disabled, the auth-psk setting has no effect.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage This command affects authentication of WPA clients only.
To use PSK authentication, you also must configure a passphrase or key. In addition, you must
enable the WPA IE.
Examples The following command enables PSK authentication for service profile wpa_clients:
WLC# set service-profile wpa_clients auth-psk enable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie] auth-dot1x on page 331
set service-profile [rsn-ie | wpa-ie] psk-raw on page 349
set service-profile wpa-ie on page 365
333
enable
disable
334
enable
disable
Defaults None.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage WLAN mesh services can be used in a wireless bridge configuration, implementing MPs
as bridge endpoints in a transparent Layer 2 bridge. A typical application of wireless bridging is to
provide network connectivity between two buildings using a wireless link.
When wireless bridging is enabled for a service profile, the MPs with the applied service profile
serve as bridge peers. When a Mesh AP associates with a Mesh Portal AP through this service
profile, the Mesh Portal AP automatically configures the Mesh AP to operate in bridge mode.
Examples The following command enables wireless bridging on service profile sp1:
WLC# set service-profile sp1 bridging enable
success: change accepted.
See Also
set ap boot-configuration mesh ssid on page 273
set service-profile mesh on page 345
show ap mesh-links on page 384
none
session
voip-call
335
Command introduced.
Examples The following command enables session-based CAC on service profile sp1:
WLC# set service-profile sp1 cac-mode session
success: change accepted.
See Also
set service-profile cac-session on page 336
show service-profile on page 404
max-sessions
336
max-voip-calls
Defaults None
Access Enabled
History Introduced in MSS Version 7.1
Examples To set the maximum number of VoIP calls for a service profile, use the following
command:
WLC# set service-profile corpbusiness cac-voip-call 100
enable
disable
Command introduced.
Usage To use CCMP, you must also enable the WPA IE.
Examples The following command configures service profile sp2 to use CCMP encryption:
WLC# set service-profile sp2 cipher-ccmp enable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie] cipher-tkip on page 338
set service-profile [rsn-ie | wpa-ie] cipher-wep104 on page 338
set service-profile [rsn-ie | wpa-ie ] cipher-wep40 on page 339
set service-profile wpa-ie on page 365
Copyright 2011, Juniper Networks, Inc.
337
enable
disable
Defaults When RNS IE or WPA IE is enabled, you can enable TKIP encryption. It is disabled by
default.
Access Enabled.
History
MSS Version 3.0
Command introduced.
Usage To use TKIP, you must also enable the WPA IE.
Examples The following command disables TKIP encryption in service profile sp2:
WLC# set service-profile sp2 wpa-ie cipher-tkip disable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie ]cipher-ccmp on page 337
set service-profile [rsn-ie | wpa-ie] cipher-wep104 on page 338
set service-profile [rsn-ie | wpa-ie ] cipher-wep40 on page 339
set service-profile tkip-mc-time on page 354
set service-profile wpa-ie on page 365
show service-profile on page 404
338
name
enable
disable
Command introduced.
Usage To use 104-bit WEP with RSN or WPA clients, you must also enable RSN-IE or WPA IE.
When 104-bit WEP in RSN or WPA is enabled in the service profile, radios managed by a radio
profile that is mapped to the service profile can also support non-RSN or non-WPA clients that use
dynamic WEP.
To support WPA clients that use 40-bit dynamic WEP, you must enable WEP with 40-bit keys. Use
the set service-profile wpa-ie cipher-wep40 command.
Microsoft Windows XP does not support WEP with WPA. To configure a service profile to provide
dynamic WEP for XP clients, leave WPA disabled and use the set service-profile wep
commands.
To support non-WPA clients that use static WEP, you must configure static WEP keys. Use the set
service-profile wep command.
Examples The following command configures service profile sp2 to use 104-bit WEP encryption:
WLC# set service-profile sp2 wpa-ie cipher-wep104 enable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie ]cipher-ccmp on page 337
set service-profile [rsn-ie | wpa-ie] cipher-tkip on page 338
set service-profile [rsn-ie | wpa-ie ] cipher-wep40 on page 339
set service-profile wep key-index on page 364
set service-profile wpa-ie on page 365
show service-profile on page 404
enable
disable
339
Access Enabled.
History
MSS Version 3.0
Command introduced.
Usage To use 40-bit WEP with RNS or WPA clients, you must also enable RSN IE or WPA IE.
When 40-bit WEP in RSN or WPA is enabled in the service profile, radios managed by a radio
profile that is mapped to the service profile can also support non-WPA clients that use dynamic
WEP.
To support WPA clients that use 104-bit dynamic WEP, you must enable WEP with 104-bit keys in
the service profile. Use the set service-profile wpa-ie cipher-wep104 command.
Microsoft Windows XP does not support WEP with WPA. To configure a service profile to provide
dynamic WEP for XP clients, leave WPA disabled and use the set service-profile wep
commands.
To support non-WPA clients that use static WEP, you must configure static WEP keys. Use the set
service-profile wep key-index command.
Examples The following command configures service profile sp2 to use 40-bit WEP encryption:
WLC# set service-profile sp2 wpa-ie cipher-wep40 enable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie ]cipher-ccmp on page 337
set service-profile [rsn-ie | wpa-ie] cipher-tkip on page 338
set service-profile [rsn-ie | wpa-ie] cipher-wep104 on page 338
set service-profile wep key-index on page 364
set service-profile wpa-ie on page 365
show service-profile on page 404
cos
340
Usage This command applies only when static CoS is enabled. If static CoS is disabled,
prioritization is based on the QoS mode configured in the radio profile, and on any ACLs that set
CoS. (See the Configuring Quality of Service chapter of the Juniper Mobility System Software
Configuration Guide.) To enable static CoS, use the set service-profile static-cos command.
Examples The following command changes the static CoS level to 7 (voice priority):
WLC# set service-profile sp1 cos 7
success: change accepted.
See Also
set service-profile static-cos on page 353
show service-profile on page 404
enable
disable
341
timeout
Defaults None
Access Enable
History Introduced in MSS Version 7.1
enable
Enables keepalives.
disable
Disables keepalives.
342
enable
disable
enable
disable
Defaults By default, MP radios automatically perform RF load balancing for all service profiles.
Access Enabled.
History Introduced in MSS Version 6.0.
343
Usage Use this command to exempt a service profile from RF load balancing. Exempting a
service profile from RF load balancing means that if an MP radio is attempting to steer clients
away, the radio does not reduce or conceal the availability of the SSID named in the exempted
service profile. Even if a radio is withholding probe responses to manage the load, the radio does
respond to probes for an exempt SSID. Also, if an MP radio is withholding probe responses, and a
client probes for any SSID, and the radio has at least one exempt SSID, the radio responds to the
probe, but the response reveals only the exempt SSID(s).
Examples The following command exempts service profile sp3 from RF load balancing:
WLC# set service-profile sp3 load-balancing-exempt enable
success: change accepted.
See Also
set load-balancing strictness on page 301
set ap radio load-balancing on page 286
set ap local-switching mode on page 279
show load-balancing group on page 399
threshold
Number of times the radio can send the same long unicast frame. You can
enter a value from 1 through 15.
344
max-bw-kb
Defaults None
Access Enabled
History Added in MSS Version 7.0.
Usage Use this command to configure specific bandwidth requirements for a service profile. Once
configured, the service profile can be mapped to a specific radio profile.
enable
disable
Defaults None.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage Use this command to configure mesh services for a service profile. Once configured, the
service profile can then be mapped to a radio profile that manages a radio on the Mesh Portal MP,
which then allows a Mesh Portal AP to beacon a mesh services SSID to Mesh APs.
Examples The following command enables mesh services for service profile sp1:
WLC# set service-profile sp1 mesh mode enable
success: change accepted.
See Also
set ap boot-configuration mesh ssid on page 273
show ap mesh-links on page 384
345
enable
disable
Defaults The no-broadcast mode is disabled by default. (Broadcast traffic not disabled.)
Access Enabled.
History Introduced in MSS Version 4.2.
Usage To further reduce ARP traffic on a service profile, use the set service-profile proxy-arp
command to enable Proxy ARP.
Examples The following command enables the no-broadcast mode on service profile sp1:
WLC# set service-profile sp1 no-broadcast enable
success: change accepted.
See Also
set service-profile dhcp-restrict on page 341
set service-profile proxy-arp on page 347
show service-profile on page 404
346
enable
disable
rsn-ie |
wpa-ie
passphrase
An ASCII string from 8 to 63 characters long. The string can contain blanks if
you use quotation marks at the beginning and end of the string.
Defaults None
Copyright 2011, Juniper Networks, Inc.
347
Access Enabled
History Introduced in MSS Version 7.0.
rsn-ie |
wpa-ie
passphrase
An ASCII string from 8 to 63 characters long. The string can contain blanks if
you use quotation marks at the beginning and end of the string.
Defaults None.
Access Enabled.
History
MSS Version 3.0
Command introduced.
Usage MSS converts the passphrase into a 256-bit binary number for system use and a raw
hexadecimal key to store in the WLC configuration. Neither the binary number nor the passphrase
is ever displayed in the configuration.
To use PSK authentication, you must enable it and you also must enable the WPA IE.
Examples The following command configures service profile sp3 to use passphrase
1234567890123<>?=+&% The quick brown fox jumps over the lazy dog:
WLC# set service-profile sp3 wpa-ie psk-phrase "1234567890123<>?=+&% The
quick brown fox jumps over the lazy dog"
success: change accepted.
See Also
set mac-user attr on page 204
set service-profile [rsn-ie | wpa-ie] auth-psk on page 333
set service-profile [rsn-ie | wpa-ie] psk-raw on page 349
set service-profile wpa-ie on page 365
show service-profile on page 404
348
rsn-ie |
wpa-ie
hex
Defaults None.
Access Enabled.
History
MSS Version 3.0
Command introduced.
Usage MSS converts the hexadecimal number into a 256-bit binary number for system use. MSS
also stores the hexadecimal key in the WLC configuration. The binary number is never displayed
in the configuration.
To use PSK authentication, you must enable it and you also must enable RSN-IE or WPA IE.
Examples The following command configures service profile sp3 to use a raw PSK with PSK
clients:
WLC# set service-profile sp3 wpa-ie psk-raw
c25d3fe4483e867d1df96eaacdf8b02451fa0836162e758100f5f6b87965e59d
success: change accepted.
See Also
set mac-user attr on page 204
set service-profile [rsn-ie | wpa-ie] auth-psk on page 333
set service-profile [rsn-ie | wpa-ie] psk-phrase on page 348
set service-profile wpa-ie on page 365
show service-profile on page 404
349
enable
disable
Defaults Disabled.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage When the RSN IE is enabled, you vsn enable the cipher suites you want the radios to
support.
Examples The following command enables the RSN IE in service profile sprsn:
WLC# set service-profile sprsn rsn-ie enable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie] auth-dot1x on page 331
set service-profile [rsn-ie | wpa-ie] auth-psk on page 333
set service-profile [rsn-ie | wpa-ie ]cipher-ccmp on page 337
set service-profile [rsn-ie | wpa-ie] cipher-wep104 on page 338
set service-profile [rsn-ie | wpa-ie ] cipher-wep40 on page 339
show service-profile on page 404
350
profile-name
enable
disable
Defaults Disabled.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage Shared-key authentication is supported only for encrypted SSIDs. In addition, if you enable
shared-key authentication, RSN, WPA, TKIP, and CCMP must be disabled. By default, RSN, WPA,
and CCMP are already disabled, but TKIP is enabled; you must manually disable TKIP. To disable
TKIP, use the set service-profile cipher-tkip disable command.
Examples The following command enables shared-key authentication in service profile sp4:
WLC# set service-profile sp4 shared-key-auth enable
success: change accepted.
See Also
set radio-profile mode on page 316
set service-profile [rsn-ie | wpa-ie] cipher-tkip on page 338
show service-profile on page 404
threshold
Number of times a radio can send the same short unicast frame. You can
enter a value from 1 through 15.
351
ssid-name
Defaults The default SSID type is crypto (encrypted) and the default name is Juniper.
Access Enabled.
History
Version 3.0
Command introduced
Version 4.0
Examples The following command applies the name guest to the SSID managed by service profile
clear_wlan:
WLC# set service-profile clear_wlan ssid-name guest
success: change accepted.
The following command applies the name corporate users to the SSID managed by service profile
mycorp_srvcprf:
WLC# set service-profile mycorp_srvcprf ssid-name corporate users
success: change accepted.
See Also
set service-profile ssid-type on page 352
show service-profile on page 404
clear
crypto
enable
disable
Command introduced.
Command deprecated.
353
tkip-mc-time
354
profile-name
Radio type.
mandatory rate-list
11ng1.0, 2.0, 5.5, 6.0, 9.0, 11.0, 12.0, 18.0, 24.0, 36.0, 48.0, 54.0, m0, m1, m2,
m3, m4, m5, m6, m7, m8, m9, m10, m11, m12, m13, m14, m15
beacon-rate rate
Data rate of beacon frames sent by MP radios. This rate is also used
for probe-response frames.
The valid rates depend on the radio type and are the same as the
valid rates for mandatory. However, you cannot set the beacon rate
to a disabled rate.
multicast-rate
{rate | auto}
355
Command introduced.
Usage If you disable a rate, you cannot use the rate as a mandatory rate or the beacon or
multicast rate. All rates that are applicable to the radio type and that are not disabled are
supported by the radio.
Examples The following command sets 802.11a mandatory rates for service profile sp1 to 6 Mbps
and 9 Mbps, disables rates 48 Mbps and 54 Mbps, and changes the beacon rate to 9 Mbps:
WLC# set service-profile sp1 transmit-rates 11a mandatory 6.0,9.0
disabled 48.0,54.0 beacon-rate 9.0
success: change accepted.
See Also
show service-profile on page 404
set radio-profile rate-enforcement on page 320
enable
disable
Defaults Disabled.
Access Enabled.
History
MSS Version 6.0
Command introduced.
Command deprecated.
Usage If this command is enabled in the service profile, the 802.11 QoS level is ignored, and MSS
classifies QoS level of IP packets based on their DSCP value.
Examples The following command enables mapping the QoS level of IP packets based on their
DSCP value for service profile sp1:
WLC# set service-profile sp1 use-client-dscp enable
success: change accepted.
See Also
356
seconds
aclname
Name of the ACL to use for filtering Web-Portal user traffic during
authentication.
357
Defaults By default, a service profile web-portal-acl option is unset. However, when you change
the service profile auth-fallthru option to web-portal, MSS sets the web-portal-acl option to
portalacl. (MSS automatically creates the portalacl ACL the first time you set any service profile
auth-fallthru option to web-portal.)
Access Enabled.
History Introduced in MSS Version 5.0.
Usage The first time you set the service profile auth-fallthru option to web-portal, MSS sets the
web-portal-acl option to portalacl. The value remains portalacl even if you change the
auth-fallthru option again. To change the web-portal-acl value, you must use the set
service-profile web-portal-acl command.
The Web-Portal ACL applies only to users who log on using Web-Portal, and applies only during
authentication. After a Web-Portal user is authenticated, the Web-Portal ACL no longer applies.
ACLs and other user attributes assigned to the username are applied instead.
358
Examples The following command changes the Web-Portal ACL name to on service profile sp3 to
creditsrvr:
WLC# set service-profile sp3 web-portal-acl creditsrvr
success: change accepted.
See Also
set service-profile [rsn-id | wpa-ie] auth-fallthru on page 332
show service-profile on page 404
url
WLC subdirectory name and HTML page name of the login page. Specify
the full path. For example, corpa-ssid/corpa.html.
Command introduced.
Version 4.0
Usage It is recommended that you create a subdirectory for the custom page and place all of the
files for the page in that subdirectory. Do not place the custom page in the root directory of the
WLC user file area.
If the custom login page includes gif or jpg images, their path names are interpreted relative to the
directory from which the page is served.
Informational Note: To use WebAAA, the fallthru authentication type in the service profile that manages
the SSID must be set to web-portal. To use WebAAA for a wired authentication port, edit the port configuration
with the set port type wired-auth command.
The web-portal authentication type also requires additional configuration items. (See the
Configuring AAA for Network Users chapter of the Juniper Mobility System Software
Configuration Guide.)
Examples The following commands create a subdirectory named corpa, copy a custom login page
named corpa-login.html and a jpg image named corpa-logo.jpg into that subdirectory, and set the
Web login page for service profile corpa-service to corpa-login.html:
WLC# mkdir corpa
success: change accepted.
Copyright 2011, Juniper Networks, Inc.
359
Size
file:corpa-login.html
15:42:26
file:corpa-logo.jpg
15:57:11
Total:
Created
637 bytes
Aug 12 2004,
1202 bytes
Aug 12 2004,
url
Specifies the URL for the Web Portal logout feature. The URL should be of
the form https://host/logout.html.
Defaults By default, the logout URL uses the IP address of the WLC as the host part of the URL.
The host can be either an IP address or a hostname.
Access Enabled.
History Introduced in MSS Version 6.0.
360
Usage Specifying the URL for the Web Portal logout feature is useful if you want to standardize
the URL across your network. For example, you can configure the logout URL on all of the WLC
switches in the Mobility Domain as wifizone.trpz.com/logout.html, where wifizone.trpz.com
resolves to one of the WLC switches in the Mobility Domain, ideally the seed.
To log out of the network, the user can click End Session in the window, or request the logout URL
directly.
Standardizing the logout URL serves as a backup means for the user to log out in case the
pop-under window is closed inadvertently. Note that if a user requests the logout URL, he or she
must enter a username and password in order to identify the session on the WLC. The username
and password are both required to identify the session. If there is more than one session with the
same username, then requesting the logout URL does not end any session.
Examples The following command configures the Web Portal logout URL as
wifizone.trpz.com/logout.html for service profile sp1.
WLC# set service-profile sp1 web-portal-logout logout-url
https://wifizone.trpz.com/logout.html
success: change accepted.
See Also
set service-profile web-portal-logout mode on page 361
show service-profile on page 404
enable
disable
Defaults Disabled.
Access Enabled.
History Introduced in MSS Version 6.0.
Usage When Web Portal logout functionality is enabled, after a Web Portal WebAAA user is
successfully authenticated and redirected to the requested page, a pop-under window appears
behind the users browser. The window contains a button labeled End Session. When the user
clicks this button, a URL is requested that terminates the users session in the Mobility Domain.
This feature allows Web Portal users a way to manually log out of the network, instead of
automatically logging out when the Web Portal WebAAA session timeout period expires.
361
Examples The following command enables the Web Portal logout functionality for service profile
sp1.
WLC# set service-profile sp1 web-portal-logout mode enable
success: change accepted.
See Also
set service-profile web-portal-logout logout-url on page 360
show service-profile on page 404
seconds
362
num
Defaults If WEP encryption is enabled and WEP keys are defined, MP radios use WEP key 1 to
encrypt multicast frames, by default.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage Before using this command, you must configure values for the WEP keys you plan to use.
Use the set service-profile wep key-index command.
Examples The following command configures service profile sp2 to use WEP key 2 for encrypting
multicast traffic:
WLC# set service-profile sp2 wep active-multicast-index 2
success: change accepted.
See Also
set service-profile wep active-unicast-index on page 363
set service-profile wep key-index on page 364
show service-profile on page 404
num
Defaults If WEP encryption is enabled and WEP keys are defined, MP radios use WEP key 1 to
encrypt unicast frames, by default.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage Before using this command, you must configure values for the WEP keys you plan to use.
Use the set service-profile wep key-index command.
Examples The following command configures service profile sp2 to use WEP key 4 for encrypting
unicast traffic:
WLC# set service-profile sp2 wep active-unicast-index 4
success: change accepted.
363
See Also
set service-profile wep active-multicast-index on page 363
set service-profile wep key-index on page 364
show service-profile on page 404
key-index num
key value
Hexadecimal value of the key. You can enter a 10-character ASCII string
representing a 5-byte hexadecimal number or a 26-character ASCII string
representing a 13-byte hexadecimal number. You can use numbers or
letters. ASCII characters in the following ranges are supported:
0 to 9
A to F
a to f
364
enable
disable
Defaults Disabled.
Access Enabled.
History Introduced in MSS Version 3.0.
MSS Version 3.0
Command introduced.
Usage When the WPA IE is enabled, you can enable the cipher suites supported by the radios.
Examples The following command enables the WPA IE in service profile sp2:
WLC# set service-profile sp2 wpa-ie enable
success: change accepted.
See Also
set service-profile [rsn-ie | wpa-ie] auth-dot1x on page 331
set service-profile [rsn-ie | wpa-ie] auth-psk on page 333
set service-profile [rsn-ie | wpa-ie ]cipher-ccmp on page 337
set service-profile [rsn-ie | wpa-ie] cipher-tkip on page 338
set service-profile [rsn-ie | wpa-ie] cipher-wep104 on page 338
set service-profile [rsn-ie | wpa-ie ] cipher-wep40 on page 339
show service-profile on page 404
show ap 11n-counters
Displays 802.11n statistics for 802.11n MPs.
Syntax show ap 11n-counters [apnum | radio [1 | 2]]
Defaults None
Access Enabled
History Introduced in MSS Version 7.0.
365
Usage Displays channel width, data rates, HT modes, and Ethernet links for 802.11n MPs.
Examples Use the following command to display 802.11n statistics for all 802.11n MPs or a single
802.11n radio.
WLC# show ap 11n-counters 3 radio 1
AP: 9980
radio: 1
=================================
Packet stats:
Tx packets count:
999002
Rx packets count:
999001
999004
999003
999005
Client stats:
Assciated clients:
999006
11n clients:
999007
Powersave clients:
999008
SM powersave clients:
999009
A-MSDU Tx count:
999011
A-MPDU Tx count:
999017
A-MSDU Rx count:
999010
A-MPDU Rx count:
999016
999013
999019
999012
999018
999014
999020
Compound aggregates:
999022
size(bytes)
Peak
<=4k
<=8k
<=16k
<=32k
<=64k
999026
999030
999034
999038
999042
A-MPDU Rx:
999045
999025
999029
999033
999037
999041
A-MSDU Tx:
999044
999024
999028
999032
999036
999040
A-MSDU Rx:
999043
999023
999027
999031
999035
999039
subframes
Peak
<=4k
<=8k
<=16k
<=32k
<=64k
366
A-MPDU Tx:
999070
999050
999054
999058
999062
999066
A-MPDU Rx:
999069
999049
999053
999057
999061
999065
A-MSDU Tx:
999068
999048
999052
999056
999060
999064
A-MSDU Rx:
999067
999047
999051
999055
999059
999063
Client stats
size
subframes
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
Defaults None.
Access Enabled.
Copyright 2011, Juniper Networks, Inc.
367
History I
Version 6.0
Command introduced.
Version 6.2
Usage For MSS to count hits for a security ACL, you must specify hits in the set security acl
commands that define ACE rules for the ACL.
Examples To display the security ACL hits on MP 7, type the following command:
WLC# show ap acl hits 7
ACL hit-counters for AP 7
Index Counter
ACL-name
0 acl_2
0 acl_175
916 acl_123
See Also
set security acl hit-sample-rate on page 465
set security acl on page 458
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
Defaults None.
Access Enabled.
History I
Version 6.0
Command introduced.
Version 6.2
Usage This command lists only the ACLs that have been mapped on the specified MP. To list all
committed ACLs, use the show security acl info command. To list ACLs that have not yet been
committed, use the show security acl editbuffer command.
Examples To display a summary of the security ACLs mapped on MP 7, type the following
command:
WLC# show ap acl map 7
ACL
Type Class
Mapping
IP
Static In
Copyright 2011, Juniper Networks, Inc.
acl_133
IP
Static In
acl_124
IP
Static
See Also
clear security acl on page 453
commit security acl on page 456
set security acl on page 458
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
Defaults None.
Access Enabled.
History
Version 6.0
Command introduced.
Version 6.2
Usage Use this command with the help of the Juniper Technical Assistance Center (TAC) to
diagnose an ACL resource problem.
Examples To display security ACL resource usage for MP 7, type the following command:
WLC# show ap acl resource-usage 7
AP 7 mapped ACL counters
-------------------------------------------Number of rule groups
Number of rules
Number of maps
show ap arp
Displays the ARP table for a specified MP.
Syntax show ap arp apnum
apnum
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
Defaults None.
Access All.
369
History
Version 6.0
Command introduced.
Version 6.2
HW Address
VLAN
State
Type
00:0b:0e:00:04:0c
1 EXPIRED
DYNAMIC
10.5.4.53
00:0b:0e:02:76:f7
1 RESOLVED LOCAL
Description
Host
HW Address
VLAN
State
Entry state:
RESOLVINGMSS sent an ARP request for the entry and is waiting for the reply.
RESOLVEDEntry is resolved.
EXPIREDEntry is expired.
Type
Entry type:
DYNAMICEntry was learned from network traffic and ages out if unused for longer
than the ARP aging timeout.
LOCALEntry for the MX MAC address. Each VLAN has one local entry for the
switch MAC address.
PERMANENTEntry does not age out and remains in the configuration even
following a reboot.
STATICEntry does not age out but is removed after a reboot.
See Also
set ap local-switching mode on page 279
set vlan-profile on page 84
show ap config
Displays a summary of MPs configured on your network.
Syntax show ap config [verbose]
Defaults None
Access Enabled
History Introduced in MSS Version 7.0
Examples To display a summary of MPs configured on your network, enter the following
command:
370
AP Name
Model
auto
3
AP03
Mode
Radio 1 profile
Radio 2 profile
disabled
default
default
default
aaaaaaaa123456
MP-372
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Shows configuration information for radio 2. (This option does not apply to
single-radio models.)
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 1.1
Version 2.0
Version 2.1
Version 3.0
New field, antennatype, to list the external antenna model configured for the
802.11b/g radio in an MP-262.
New fields added:
auto-tune max-power
auto-tune min-client-rate
auto-tune max-retransmissions
beacon field removed
Version 4.0
371
Version 5.0
Version 6.0
Version 6.2
NO
communication timeout: 10
location:
contact:
Radio 1: type: 802.11g, mode: disabled, channel: dynamic
tx pwr: 18, profile: default
auto-tune max-power: default,
load-balance-group: ,
load-balance-enable: YES,
force-rebalance: NO,
local-switching: disabled, vlan-profile: default
Table 46 describes the fields in this display.
Table 46.Output for show ap config
372
Field
Description
Port
AP
serial-id
Description
AP model
MP model number.
bias
name
upgrade-firmware
force-image-download
State of the option to force the MP to download a software image from the WLC instead
of loading a locally stored image on the MP.
communication timeout
location
contact
Radio
Radio number. The information listed below this field applies specifically to the radio.
type
Radio type:
802.11a
802.11b
802.11g
mode
Radio state:
Enabled
Disabled
channel
Channel number.
antennatype
tx pwr
profile
Radio profile that manages the radio. Until you assign the radio to a radio profile, MSS
assigns the radio to the default radio profile.
auto-tune max-power
Maximum power level the RF Auto-Tuning feature can set on the radio.
The value default means RF Auto-Tuning can set the power up to the maximum
level allowed for the country of operation.
A specific numeric value means you or another administrator set the maximum
value.
load-balance-group
Names of the RF load-balancing groups to which the MP belongs. If the value is None,
the MP does not belong to any load balancing groups.
This field is displayed only if the MP is a member of a group.
load-balance-enable
force-rebalance
If the MP radio disassociates the client sessions and rebalances them whenever a new
MP radio is added to the RF load balancing group.
local-switching
vlan-profile
The VLAN profile the MP uses for local packet switching, indicating which VLANs are
locally switched.
373
See Also
set ap on page 53
set port type ap on page 61
set ap bias on page 268
set ap fingerprint on page 276
set ap group on page 278
set ap name on page 280
set ap upgrade-firmware on page 299
set ap radio mode on page 288
set ap radio antennatype on page 282
set ap radio channel on page 284
set ap radio radio-profile on page 289
set ap radio tx-power on page 290
show ap connection on page 395
show ap global on page 397
show ap unconfigured on page 398
show radio-profile on page 400
show ap counters
Displays MP access point and radio statistics counters.
Syntax show ap counters apnum [radio {1 | 2}]
apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
radio 1
radio 2
Shows statistics counters for radio 2. (This option does not apply to
single-radio models.)
Defaults None.
Access Enabled.
History
Version 1.0
374
Command introduced.
Version 1.1
Version 2.0
Version 4.0
Version 6.2
Version 7.1
Usage To display statistics counters and other information for individual user sessions, use the
show sessions network command.
Examples The following command shows statistics counters for Distributed MP 7:
WLC# show ap counters 7
AP: 7
radio: 1
=================================
LastPktXferRate
PktTxCount
73473
NumCntInPwrSave
MultiPktDrop
LastPktRxSigStrength
-89
MultiBytDrop
LastPktSigNoiseRatio
User Sessions
MIC Error Ct
RadioResets
375
Transmit Retries
60501
15
Noise Floor
-93
802.3 Packet Tx Ct
802.3 Packet Rx Ct 0
No Receive Descriptor
Illegal Rates
TxUniPkt
TxUniByte
TxMultiPkt
RxPkt
TxMultiByte
UndcrptPkt
RxByte
UndcrptByte
PhyErr
1.0: 1017
10170
14
8347
3964
1670
8695
5.5:
258
6.0:
51
9.0:
172
53
11.0:
17
998
35
12.0:
26
18.0:
38
24.0:
47
36.0:
48.0:
68
29
54.0:
41 11513
0 12948
Description
AP
Distributed MP number.
radio
Radio number.
LastPktXferRate
Data transmit rate, in Mbps, of the last packet received by the MP.
NumCntInPwrSave
LastPktRxSigStrength
LastPktSigNoiseRatio
Signal-to-noise ratio (SNR), in decibels (dB), of the last packet received by the MP
access point.
This value indicates the strength of the radio signal above the noise floor. For example,
if the noise floor is -88 and the signal strength is -68, the SNR is 20.
If the value is below 10, this indicates a weak signal and might indicate a problem in the
RF environment.
376
Description
Number of times a decryption error occurred with a packet encrypted with CCMP.
Occasional decryption errors do not indicate a problem.
However, steadily increasing errors or a high number of errors can indicate that data
loss is occurring in the network. Generally, this is caused by a key mismatch between a
client and the MP. To locate the client that is experiencing decryption errors (and
therefore is likely causing this counter to increment on the MP), use the show
sessions network session-id session-id command for each client on the radio. After
you identify the client that is causing the errors, disable and reenable the client
(wireless NIC).
Current power level set on the radio. If RF Auto-Tuning of power is enabled, this value
is the power set by RF Auto-Tuning. If RF Auto-Tuning is disabled, this value is the
statically configured power level.
802.3 Packet Tx Ct
Number of raw 802.3 packets transmitted by the radio. These are LocalTalk (AppleTalk)
frames. This counter increments only if LocalTalk traffic is present.
No Receive Descriptor
Number of packets for which the MP could not create a descriptor. A descriptor
describes a received packets size and its location in MP memory. The MP buffers
descriptors, and clears them during interframe spaces.
This counter increments if the MP runs out of buffers for received packets. This
condition can occur when a noise burst temporarily floods the air and the MP attempts
to buffer the noise as packets.
Buffer overruns are normal while an MP is booting. However, if they occur over an
extended period of time when the MP is fully active, this can indicate RF interference.
Illegal Rates
PktTxCount
MultiPktDrop
Number of multicast packets dropped by the radio due to a buffer overflow on the MP.
This counter increments if there is too much multicast traffic or there is a problem with
the multicast packets. Normally, this counter should be 0.
MultiBytDrop
Number of multicast bytes dropped by the radio due to a buffer overflow on the MP.
(See the description for MultiPktDrop.)
377
Description
User Sessions
MIC Error Ct
Number of times the radio received a TKIP-encrypted frame with an invalid MIC.
Normally, the value of this counter should always be 0. If the value is not 0, check the
system log for MIC error messages and contact Juniper Networks TAC.
Number of times a decryption error occurred with a packet encrypted with TKIP.
(See the description for CCMP Pkt Decrypt Err.)
RadioResets
Number of times the radio has been reset. Generally, a reset occurs as a result of RF
Number of times the radio retransmitted a unicast packet because it was not
acknowledged. The MP uses this counter to adjust the transmit data rate for a client, in
order to minimize retries.
The ratio of transmit retries to transmitted packets (TxUniPkt) indicates the overall
transmit quality. A ratio of about 1 retry to 10 transmitted packets indicates good
transmit quality. A ratio of 3 or more to 10 indicates poor transmit quality.
This counter includes unacknowledged probes. Some clients do not respond to probes,
which can make this counter artificially high.
Noise Floor
Received signal strength at which the MP can no longer distinguish 802.11 packets
from ambient RF noise. A value around -90 or higher is good for an 802.11b/g radio. A
value around -80 or higher is good for an 802.11a radio. Values near 0 can indicate RF
interference.
802.3 Packet Rx Ct
Number of raw 802.3 packets received by the radio. These are LocalTalk (AppleTalk)
frames. This counter increments only if LocalTalk traffic is present.
The counters above are global for all data rates. The counters below are for individual data rates.
If counters for lower data rates are incrementing but counters for higher data rates are not incrementing, this can indicate
poor throughput. The poor throughput can be caused by interference. If the cause is not interference or the interference
cannot be eliminated, you might need to relocate the MP in order to use the higher data rates and therefore improve
throughput.
378
TxUniPkt
TxMultiPkt
TxUniByte
TxMultiByte
RxPkt
Description
RxByte
UndcrptPkt
Number of undecryptable packets received by the radio. It is normal for this counter to
increment even in stable networks and does not necessarily indicate an attack. For
example, a client might be sending incorrect key information. However, if the counter
increments rapidly, there might be a problem in the network.
UndcrptByte
Number of undecryptable bytes received by the radio. (See the description for
UndcrptPkt.)
PhyError
Number of packets that could not be decoded by the MP. This condition can have any
of the following causes:
Collision of an 802.11 packet.
Packet whose source is too far away, thus rendering the packet unintelligible by the
time it reaches the MP.
Interference caused by an 802.11b/g phone or other source.
It is normal for this counter to be about 10 percent of the total RxByte count. It is also
normal for higher data rates to have higher Phy error counts than lower data rates.
radio: 1
================================
Current Active Calls
Cumulative
Voice Calls
Quality
BAD
Rejected
POOR
FAIR
GOOD
EXCELLENT
Accepted
-----------------------------------------------------------------------------------Calls
100
0
Percentage
0
379
Description
Cumulative Accepted
Calls
Percentage
show ap fdb
Displays the entries in a specified MP forwarding database.
Syntax show ap fdb {apnum | all | hash-utilization [apnum |all ]}
apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
all
hash-utilization
Defaults None.
Access All.
History
Version 6.0
Command introduced.
Version 6.2
0 00:0b:0e:00:04:0c
CPU
eth0
380
Field
Description
VLAN
VLAN number.
TAG
VLAN tag value. If the interface is untagged, the TAG field is blank.
Description
CoS
Type of entry. The entry types are explained in the first row of the command output.
This Class of Service (CoS) value is not associated with MSS quality of service (QoS)
features.
Destination Ports
MX port associated with the entry. An WLC sends traffic to the destination MAC
address through this port.
See Also
set ap local-switching mode on page 279
set vlan-profile on page 84
show ap qos-stats
Displays statistics for MP forwarding queues.
Syntax show ap qos-stats [apnum] [clear]
apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
clear
Defaults None.
Access Enabled.
History
Version 4.0
Command introduced.
Version 4.2
Version 5.0
Version 6.0
Version 6.2
Usage Repeating this command with the clear option at regular intervals allows you to monitor
transmission and drop rates.
Examples The following command shows statistics for the MP forwarding queues on a Distributed
MP:
WLC# show ap qos-stats 7
CoS
Tx
Queue
Rx
Rx
Tx
Tx
Tx
Tx
Tx
Kbs
Kbs
%Req
%Max
Packets
Dropped
========================================================================
=======
AP: 7
radio: 1
381
1,2
0
Background
0,3
0
BestEffort
93
4,5
0
Video
6,7
0
Voice
AP: 7
radio: 2
1,2
0
Background
0,3
0
BestEffort
127
4,5
0
Video
6,7
0
Voice
Description
CoS
Queue
Forwarding queue.
AP
Distributed MP number.
radio
Radio number.
Tx Packets
Tx Dropped
382
show ap etherstats
Displays Ethernet statistics for an Ethernet port on an MP.
Syntax show ap etherstats apnum
apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
Defaults None.
Access Enabled.
History
Version 3.0
Command introduced.
Version 6.2
Examples The following command displays Ethernet statistics for the Ethernet ports on Distributed
MP 1:
WLC# show ap etherstats 1
AP: 1
ether: 1
=================================
RxUnicast:
75432
TxGoodFrames:
55210
RxMulticast:
18789
TxSingleColl:
32
RxBroadcast:
RxGoodFrames:
94229
TxLateColl:
TxMaxColl:
RxAlignErrs:
TxMultiColl:
47
RxShortFrames:
TxUnderruns:
RxCrcErrors:
TxCarrierLoss:
RxOverruns:
TxDeferred:
RxDiscards:
AP: 1
150
ether: 2
=================================
RxUnicast:
64379
TxGoodFrames:
60621
RxMulticast:
21798
TxSingleColl:
32
RxBroadcast:
11
RxGoodFrames:
86188
TxLateColl:
TxMaxColl:
RxAlignErrs:
TxMultiColl:
12
RxShortFrames:
TxUnderruns:
RxCrcErrors:
TxCarrierLoss:
RxOverruns:
TxDeferred:
RxDiscards:
111
383
Description
RxUnicast
RxMulticast
RxBroadcast
RxGoodFrames
RxAlignErrs
Number of received frames that were both misaligned and contained a CRC error.
RxShortFrames
Number of received frames that were shorter than the minimum frame length.
RxCrcErrors
RxOverruns
RxDiscards
TxGoodFrames
TxSingleColl
TxLateColl
Number of frames that were not transmitted because they encountered a collision
outside the normal collision window.
TxMaxColl
Number of frames that were not transmitted because they encountered the maximum
allowed number of collisions. Typically, this occurs only during periods of heavy traffic
on the network.
TxMultiColl
TxUnderruns
Number of frames that were not transmitted or retransmitted due to temporary lack of
hardware resources.
TxCarrierLoss
Number of frames transmitted despite the detection of a deassertion of CRS during the
transmission.
TxDeferred
show ap group
Deprecated in MSS Version 6.0. To display information about RF load balancing, see show
load-balancing group on page 399.
show ap mesh-links
Displays information about the links an MP has to Mesh APs and Mesh Portal APs.
Syntax show ap mesh-links apnum
apnum
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
Defaults None.
Access All.
384
History
Version 6.0
Command introduced.
Version 6.2
bytes
TX:
307
44279
RX:
315
215046
Description
AP
Name
VLAN name
IP-addr
Operational Mode
Downlink Mesh-APs
Information about the Mesh APs associated with the Mesh Portal MP.
BSSID
TX
The amount of traffic (packets and bytes) transmitted to the Mesh AP.
RX
The amount of traffic (packets and bytes) received from the Mesh AP.
See Also
set ap boot-configuration mesh ssid on page 273
set service-profile mesh on page 345
show ap status
Displays MP access point and radio status information.
Syntax show ap status [[apnum | all | verbose | [radio {1 | 2}] cluster
ip-addr]]
apnum
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
all
Shows status information for all directly attached MPs and all Distributed MPs
configured on the WLC.
radio 1
385
radio 2
Shows status information for radio 2. (This option does not apply to
single-radio models.)
cluster
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 1.1
Version 2.0
Version 3.0
Version 3.2
True base MAC addresses of radios are displayed. Previously, the base MAC
address displayed for a radio was the true base MAC address plus 2.
Note that a radios base MAC address is also used as the BSSID of the first
SSID configured on the radio.
Version 4.0
Version 4.1
External antenna information added after the radio state information, to indicate
when an antenna has been detected and to indicate the configured antenna
model number.
Auto flag added to indicate operational channel or power settings that are
configured by RF Auto-Tuning.
386
Version 4.2
Radar Scan and Radar Detected flags added to indicate when the Dynamic
Frequency Selection (DFS) feature is scanning for radar or has stopped
transmitting due to detected radar. The flags apply to 802.11a radios only, and
only for country codes where DFS is used.
Version 5.0
Version 6.0
Version 6.2
Version 7.0
Version 7.1
Model
MAC Address
Radio 1 Radio 2
MP-422
The following command uses the verbose option to display all information for MPs:
WLC# show ap status verbose
Rack28-2800-112226# show ap status 9991 verbose
AP: 9991 Name: AUTO-9991
Model: Juniper MP-422, Rev: n/a, Serial number: 108
F/W1 : 1.0
F/W2 : 1.0
S/W
BOOT S/W
: 7.0.1.0.private_032408_1529_jperson
: <unknown>
387
Description
Flags
Radio
IP Address
AP
Flag
IP-addr
388
Description
Model
MP model number.
MAC Address
Radio 1
Radio 2
Uptime
Description
AP
Name
Model
MP model number
Revision number
Serial Number
Firmware versions
Software version
Boot software version
IP Address
Port 1 link:
Status
Configured duplex speed
PoE type
Port 2 link:
Stauts
Configured duplex speed
PoE type and status
State:
Uptime
Radio 1
389
Description
Radio 2
State, channel, and power information for radio 2. See Radio 1 for more information.
show ap vlan
Displays information about locally switched or tunneled VLANs.
Syntax show ap vlan apnum
apnum
Index value that identifies the MP on the WLC. You can specify a value from 1 to
9999.
all
Defaults None.
Access All.
History
Version 6.0
Command introduced.
Version 6.2
Version 7.0
Examples The following command displays information about the VLANs switched by AP 7:
WLC# show ap vlan 7
AP 7:
VLAN Name
Mode
Port
Tag
---------------- ----
1 default
local
1 none
2 red
local
radio_1
20
radio_1
21
radio_2
22
radio_1
23
4 green
5 yellow
local
tunnel
WLC_tun
radio_1
24
390
Field
Description
VLAN
VLAN number.
Name
VLAN name
Description
Mode
Whether packets for the VLAN are locally switched by the MP, or are tunneled to an
WLC, which places them on the VLAN.
Port
TAG
VLAN tag value. If the interface is untagged, none is displayed in the TAG field.
See Also
set ap local-switching mode on page 279
set vlan-profile on page 84
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
radio 1
radio 2
Shows RF attribute information for radio 2. (This option does not apply to
single-radio models.)
radio all
Defaults None.
Access Enabled.
Examples
Version 3.0
Command introduced.
Version 6.0
Version 6.2
The following command displays RF attribute information for radio 1 on the directly connected MP
access point on port 2:
WLC# show auto-tune attributes ap 2 radio 1
Auto-tune attributes for port 2 radio 1:
Noise:
Utilization:
CRC Errors count:
0
0
122
391
Description
Noise
Noise threshold on the active channel. RF Auto-Tuning prefers channels with low noise
levels over channels with higher noise levels.
Utilization
Number of multicast packets per second that a radio can send on a channel while
continuously sending fixed size frames over a period of time. The number of packets
that are successfully transmitted indicates how busy the channel is.
Number of frames received by the radio on that active channel that had CRC errors. A
high CRC error count can indicate a hidden node or co-channel interference.
Number of retransmitted packets sent from the client to the radio on the active channel.
Number of frames received by the MP radio that had physical layer errors on the active
Retransmissions can indicate that the client is not receiving ACKs from the MP radio.
channel. Phy errors can indicate interference from a non-802.11 device.
See Also
set ap radio auto-tune max-power on page 283
set radio-profile auto-tune 11a-channel-range on page 302
set radio-profile auto-tune channel-holddown on page 304
set radio-profile auto-tune channel-interval on page 305
set radio-profile auto-tune power-config on page 306
set radio-profile auto-tune power-interval on page 307
show auto-tune neighbors on page 392
show radio-profile on page 400
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
radio 1
radio 2
Shows neighbor information for radio 2. (This option does not apply to
single-radio models.)
radio all
Defaults None.
Access Enabled.
History
Version 3.0
392
Command introduced.
Version 6.0
Version 6.2
Usage For simplicity, this command displays a single entry for each Juniper radio, even if the radio
is supporting multiple BSSIDs. However, BSSIDs for third-party 802.11 radios are listed
separately, even if a radio is supporting more than one BSSID.
Information is displayed for a radio if the radio sends beacon frames or responds to probe
requests. Even if the radio SSIDs are unadvertised, Juniper radios detect the empty beacon
frames (beacon frames without SSIDs) sent by the radio, and include the radio in the neighbor list.
Examples The following command displays neighbor information for radio 1 on the directly
connected MP access point on port 2:
WLC# show auto-tune neighbors ap 2 radio 1
Total number of entries for port 2 radio 1: 5
Channel Neighbor BSS/MAC
RSSI
-46
1 00:0b:0e:00:0a:80
-78
1 00:0b:0e:00:d2:c0
-74
1 00:0b:85:06:dd:00
-50
1 00:0b:0e:00:05:c1
-72
Description
Channel
Neighbor BSS/MAC
RSSI
See Also
set ap radio auto-tune max-power on page 283
set radio-profile auto-tune 11a-channel-range on page 302
set radio-profile auto-tune channel-holddown on page 304
set radio-profile auto-tune channel-interval on page 305
set radio-profile auto-tune power-config on page 306
set radio-profile auto-tune power-interval on page 307
show auto-tune attributes on page 391
show radio-profile on page 400
393
show ap boot-configuration
Displays information about the static IP address configuration (if any) on a Distributed MP.
Syntax show ap boot-configuration apnum
apnum
Index value that identifies the MP on the WLC. You can specify a value from
1 to 9999.
Defaults None.
Access Enabled.
History I
Version 4.2
Command introduced.
Version 6.0
Version 6.2
Examples The following command displays static IP configuration information for Distributed MP
1:
WLC# show ap boot-configuration 1
Static Boot Configuration
AP: 7
IP Address:
Disabled
VLAN Tag:
Disabled
Switch:
Disabled
Mesh:
Disabled
IP Address:
Netmask:
Gateway:
VLAN Tag:
Switch IP:
Switch Name:
DNS IP:
Mesh SSID:
Mesh PSK:
Table 51 describes the fields in this display.
394
Description
AP
MP number.
IP address
VLAN Tag
Switch
Whether the Distributed MP is configured to use a manually specified WLC as the boot
Mesh
IP address
Netmask
device.
Gateway
VLAN Tag
The VLAN tag that the Distributed MP is configured to use (if any).
Switch IP
The IP address of the WLC that this Distributed MP is configured to use as its boot
device (if any).
Switch Name
The name of the WLC that this Distributed MP is configured to use as the boot device
(if any).
DNS IP
The IP address of the DNS server that the Distributed MP uses to resolve the name of
Mesh SSID
The WLAN mesh services SSID this MP is configured to use (if any)
Mesh PSK
The preshared key (PSK) the MP uses for authentication with a Mesh Portal AP (if
any).
show ap connection
Displays the system IP address of the MX that booted a Distributed MP.
Syntax show ap connection [apnum | serial-id serial-ID]
apnum
Index value that identifies the MP on the WLC. You can specify a value
from 1 to 9999.
serial-id serial-ID
Defaults None.
Access Enabled.
History I
Version 2.0
Command introduced.
Version 6.0
Version 6.2
Usage The serial-id parameter displays the active connection for the specified Distributed MP
even if that MP is not configured on this MX. If you instead use the command with the apnum
parameter or without a parameter, connection information is displayed only for Distributed MPs
configured on this WLC.
395
This command provides information only if the Distributed MP is configured on the WLC where you
entered the command. The WLC does not need to be the one that booted the MP, but it must have
the MP in the configuration. Also, the WLC that booted the MP must be in the same Mobility
Domain as the WLC where you entered the command.
If a Distributed MP is configured on this WLC (or another MX in the same Mobility Domain) but
does not have an active connection, the command does not display information for the MP. To
show connection information for Distributed MPs, use the show ap global command on one of the
switches where the MPs are configured.
Examples The following command displays information for all Distributed MPs configured on this
MX switch that have active connections:
WLC# show ap connection
Total number of entries: 2
AP Serial Id
AP IP Address
WLC IP Address
112233
10.10.2.27
10.3.8.111
0333000298
10.10.3.34
10.3.8.111
The following command displays connection information specifically for a Distributed MP with
serial ID 223344:
WLC# show ap connection serial-id 223344
Total number of entries: 1
AP Serial Id AP IP Address
WLC IP Address
223344
10.10.4.88
10.9.9.11
Description
AP
Serial Id
AP IP Address
WLC IP Address
System IP address of the MX that the MP has an active connection. This is the WLC
that the MP used for booting and configuration and is using for data transfer.
See Also
show ap config radio on page 371
show ap global on page 397
show ap unconfigured on page 398
396
show ap global
Displays connection information for Distributed MPs configured on an MX .
Syntax show ap global [apnum | serial-id serial-ID]
apnum
Index value that identifies the MP on the WLC. You can specify a
value from 1 to 9999.
serial-id serial-ID
Defaults None.
Access Enabled.
History
Version 2.0
Command introduced.
Version 6.0
Version 6.2
Usage Connections are shown only for the Distributed MPs configured on the WLC that you enter
the command, and only for the Mobility Domain of the WLC.
To show information only for Distributed MPs that have active connections, use the show ap
connection command.
Examples The following command displays connection information for all the Distributed MPs
configured on an WLC:
WLC# show ap global
Total number of entries: 8
AP Serial Id
WLC IP Address
Bias
11223344
10.3.8.111
HIGH
11223344
10.4.3.2
LOW
332211
10.3.8.111
LOW
332211
10.4.3.2
HIGH
17
0322100185
10.3.8.111
HIGH
0322100185
10.4.3.2
LOW
18
0321500120
10.3.8.111
LOW
0321500120
10.4.3.2
HIGH
397
Description
AP
Serial Id
WLC IP Address
Bias
See Also
set ap on page 53
set ap bias on page 268
show ap config radio on page 371
show ap connection on page 395
show ap unconfigured on page 398
show ap unconfigured
Displays Distributed MPs that are physically connected to the network but that are not configured
on any WLC switches.
Syntax show ap unconfigured
Defaults None.
Access Enabled.
History
Version 2.0
Command introduced.
Version 6.0
Usage This command also displays an MP that is directly connected to an WLC, if the WLC port
connected to the MP is configured as a network port instead of an MP access port, and if the
network port is a member of a VLAN.
If a Distributed MP is configured on an WLC, the MP can appear in the output until the MP is able
to establish a connection with an WLC in a Mobility Domain. After the MP establishes a
connection, the entry for the MP ages out and no longer appears in the command output.
Entries in the command output table age out after two minutes.
Examples The following command displays information for two Distributed MPs that are not
configured:
WLC# show ap unconfigured
Total number of entries: 2
398
Serial Id
Model
IP Address
Port Vlan
MP-241 10.3.8.54
default
0333001285
MP-252 10.3.8.57
vlan-eng
Description
Serial Id
Model
MP model number.
IP Address
IP address of the MP. This is the address that the MP receives from a DHCP server.
The MP uses this address to send a Find WLC message to request configuration
information from WLC switches. However, the MP cannot use the address to establish
a connection unless the MP first receives a configuration from an WLC.
Port
Port number on which this WLC received the MP Find WLC message.
VLAN
See Also
show ap connection on page 395
show ap global on page 397
all
Displays information for every load-balancing group that has a radio on this
WLC as a member.
apnum
Index value that identifies the MP on the WLC. You can specify a value from 1
to 9999.
radio {1 | 2}
Defaults None.
Access Enabled.
History
Version 6.0
Command introduced.
Version 6.2
399
Usage Use this command to display information about the RF load-balancing groups configured
on the WLC and the individual MP radios in the load-balancing groups.
Examples The following command displays information about the MP radios that are in the same
group as radio 1 on MP 3:
WLC# show load-balancing group ap 3 radio 1
Radios in the same load-balancing group as: ap3/radio1
-------------------------------------------------IP address
AP
------------------ ---10.2.28.200
Radio
Overlap
-----
-------
100/100
The following command displays information about RF load balancing group blue:
WLC# show load-balancing group blue
Load-balancing group: blue
IP address
AP
------------------ ---10.2.28.200
Radio
Clients
-----
-------
Table 62 describes the fields in displayed by the show load-balancing group command.
Table 62.Output for show load-balancing group
Field
Description
IP address
AP
MP number
Radio
Radio number
Overlap
The amount of overlapping coverage area the specified MP radio has with the MP radio
in the list. An overlap of 100/100 indicates that the MP radios have exactly the same
coverage area.
Clients
See Also
set load-balancing strictness on page 301
set ap radio load-balancing on page 286
set ap local-switching mode on page 279
show radio-profile
Displays radio profile information.
Syntax show radio-profile {profile | ?}
profile
Defaults None.
400
Access Enabled.
History
Version 1.0
Command introduced
Version 1.1
Version 3.0
Fields removed for items that are no longer managed by radio profiles:
Encrypted Network Name
Clear Network Name
Network name(s) broadcast in the wireless beacon
WEP Key 1 value
WEP Key 2 value
WEP Key 3 value
WEP Key 4 value
WEP Unicast Index
WEP Multicast Index
Shared Key Auth
WPA enabled
These items are now managed by service profiles.
New fields added:
Tune Channel
Tune Power
Tune Channel Interval
Tune Power Interval
Client Backoff Timer
Channel Holddown
Service profiles
Name of the 802.11g field changed from Allow only 802.11g clients in
802.11g networks to Allow 802.11g clients only
Version 4.0
401
Version 4.2
Version 5.0
Usage MSS contains a default radio profile. Juniper Networks recommends that you do not
change this profile but instead keep the profile for reference.
Examples The following command shows radio profile information for the default radio profile:
WLC# show radio-profile default
Beacon Interval:
1
100
Max Tx Lifetime:
2000
2000
Max Rx Lifetime:
RTS Threshold:
2346
2346
Frag Threshold:
Long Preamble:
yes
no
Tune Channel:
Tune Power:
3600
no
600
300
yes
no
DTIM Interval:
402
Description
Beacon Interval
Rate (in milliseconds) at which each MP radio in the profile advertises the beaconed
SSID.
DTIM Interval
Number of times after every beacon that each MP radio in the radio profile sends a
delivery traffic indication map (DTIM).
Max Tx Lifetime
Number of milliseconds that a frame received by a radio in the radio profile can remain
in buffer memory.
Max Rx Lifetime
RTS Threshold
Minimum length (in bytes) a frame can be for a radio in the radio profile to use the
RTS/CTS method to send the frame. The RTS/CTS method clears the air of other
traffic to avoid corruption of the frame due to a collision with another frame.
Frag Threshold
Maximum length (in bytes) a frame is allowed to be without being fragmented into
multiple frames before transmission by a radio in the radio profile.
Long Preamble
Indicates whether an 802.11b radio that uses this radio profile advertises support for
frames with long preambles only:
YESAdvertises support for long preambles only.
NOAdvertises support for long and short preambles.
Tune Channel
Tune Power
Indicates whether RF Auto-Tuning is enabled for dynamically setting and tuning power
channels.
levels.
Tune Channel Interval
Number of seconds a radio waits before increasing or decreasing its power by 1 dBm in
response to a power change from RF Auto-Tuning. After each power ramp interval, the
radio increases or decreases the power by another 1 dB until the radio reaches the
power level selected by RF Auto-Tuning.
Channel Holddown
Minimum number of seconds a radio in a radio profile must remain at its current
channel assignment before RF Auto-Tuning can change the channel.
Countermeasures
Active-Scan
RFID enabled
WMM Powersave
QoS Mode
403
Description
Service profiles mapped to this radio profile. Each service profile contains an SSID and
encryption information for that SSID.
When you upgrade from 2.x, MSS creates a default-dot1x service profile for encrypted
SSIDs and a default-clear service profile for unencrypted SSIDs. These default service
profiles contain the default encryption settings for crypto SSIDs and clear SSIDs,
respectively.
See Also
set radio-profile active-scan on page 302
set radio-profile auto-tune 11a-channel-range on page 302
set radio-profile auto-tune channel-holddown on page 304
set radio-profile auto-tune channel-interval on page 305
set radio-profile auto-tune channel-lockdown on page 305
set radio-profile auto-tune power-config on page 306
set radio-profile auto-tune power-interval on page 307
set radio-profile auto-tune power-lockdown on page 308
set radio-profile auto-tune power-ramp-interval on page 308
set radio-profile beacon-interval on page 309
set radio-profile countermeasures on page 311
set radio-profile dfs-channels on page 312
set radio-profile frag-threshold on page 313
set radio-profile max-rx-lifetime on page 314
set radio-profile mode on page 316
set radio-profile mode on page 316
set radio-profile preamble-length on page 319
set radio-profile qos-mode on page 320
set radio-profile rf-scanning mode on page 322
set radio-profile rts-threshold on page 323
set radio-profile service-profile on page 323
set radio-profile wmm-powersave on page 328
show service-profile
Displays service profile information.
Syntax show service-profile {profile-name | ?}
404
profile-name
Defaults None.
Access Enabled.
History
Version 3.0
Command introduced
Version 4.1
New fields added to indicate the configured SSID default attributes in the
service profile.
Version 4.2
405
Version 5.0
Version 6.0
Examples The following command displays information for service profile sp1:
WLC# show service-profile sp1
ssid-name:
crypto
Beacon:
no
DHCP restrict:
no
Short retry limit:
5
Auth fallthru:
no
Enforce SODA checks:
yes
no
5
ssid-type:
Proxy ARP:
No broadcast:
Long retry limit:
none
yes
Custom agent-directory:
Static COS:
0
Client DSCP:
none
CAC sessions:
180
Idle client probing:
no
Web Portal Session Timeout:
no
Web Portal ACL:
no
406
corp2
no
no
COS:
CAC mode:
14
yes
Mesh enabled:
Bridging enabled:
no
<none>
<none>
6.0
multicast rate:
2.0
multicast rate:
2.0
multicast rate:
Description
ssid-name
ssid-type
SSID type:
cryptoWireless traffic for the SSID is encrypted.
clearWireless traffic for the SSID is unencrypted.
Beacon
Proxy ARP
Indicates whether proxy ARP is enabled. When this feature is enabled, MSS answers
ARP requests on behalf of wireless clients.
DHCP restrict
Indicates whether DHCP Restrict is enabled. When this feature is enabled, MSS allows
only DHCP traffic for a new client until the client has successfully completed
authentication and authorization.
No broadcast
Indicates if broadcast restriction is enabled. When this feature is enabled, MSS sends
ARP requests and DHCP Offers and Acks as unicasts to their target clients instead of
forwarding them as broadcasts.
Number of times a radio serving the service-profiles SSID can send a short unicast
frame without receiving an acknowledgment.
407
Description
Number of times a radio serving the service-profile SSID can send a long unicast frame
without receiving an acknowledgment. A long unicast frame is a frame that is equal to
or longer than the RTS threshold.
Auth fallthru
Secondary (fallthru) encryption type when a user tries to authenticate but the WLC
managing the radio does not have an authentication rule with a userglob that matches
the username.
last-resortAutomatically authenticates the user and allows access to the SSID
requested by the user, without requiring a username and password.
noneDenies authentication and prohibits the user from accessing the SSID.
web-portalRedirects the user to a web page for login to the SSID.
Whether SODA functionality is enabled for the service profile. When SODA
functionality is enabled, connecting clients download SODA agent files, which perform
security checks on the client.
If a client is allowed access to the network after it has downloaded and run the SODA
agent security checks. When SODA functionality is enabled, and the WLC is
configured to enforce SODA checks, then a connecting client must download the
SODA agent files and pass the checks in order to gain access to the network.
The name of the ACL to be applied to the client if it fails the SODA agent checks. If no
remediation ACL is specified, then a client is disconnected from the network if it fails
the SODA agent checks.
The name of the user-specified page that the client loads upon successful completion
of the SODA agent checks. If no page is specified, then the success page is generated
dynamically.
The name of the user-specified page that the client loads if it fails SODA agent checks.
The name of the user-specified page that the client loads upon logging out of the
The name of the directory for SODA agent files on the WLC switch, if different from the
default. By default, SODA agent files are stored in a directory with the same name as
the service profile.
Static COS
Indicates whether static CoS assignment is enabled. When this feature is enabled,
MPs assign the CoS value in the COS field to all user traffic forwarded by the MP.
COS
CoS value assigned by the MP to all user traffic, if static CoS is enabled. (If static CoS
is disabled, WMM or ACLs are used to assign CoS.)
Client DSCP
If packets are classified based on client DSCP level instead of 802.11 priority.
CAC mode
CAC sessions
Maximum number of user sessions that can be active on an MP radio at one time, if the
CAC mode is session. (If the CAC mode is none, this value is not used.)
Indicates how many seconds a user session can remain idle (indicated by no user
traffic and no reply to client keepalive probes) before the session is changed to the
Disassociated state.
408
Description
When a Web Portal WebAAA session is placed in the Deassociated state, how many
seconds the session can remain in that state before being terminated automatically.
Mesh enabled
Whether WLAN mesh services are enabled for the service profile.
Name of the ACL used to filter traffic for Web Portal users associated with this service
profiles SSID while the users are being authenticated.
Bridging enabled
If the MP radios managed by this service profile are exempted (do not participate in)
RF load balancing.
Custom Web Portal Logout URL If configured, the URL that Web Portal WebAAA users can access in order to terminate
their sessions.
WEP Key 1 value
State of static WEP key number 1. Radios can use this key to encrypt traffic with static
Wired-Equivalent Privacy (WEP):
noneThe key is not configured.
presetThe key is configured.
Index of the static WEP key used to encrypt unicast traffic on an encrypted SSID.
Index of the static WEP key used to encrypt multicast traffic on an encrypted SSID.
WPA enabled
or
RSN enabled
Indicates that the Wi-Fi Protected Access (WPA) or Robust Security Network (RSN)
information element (IE) is enabled. Additional fields display the settings of other WPA
or RSN parameters:
ciphersLists the cipher suites advertised by radios in the radio profile mapped to
this service profile.
authenticationLists the authentication methods supported for WPA or RSN clients:
802.1Xdynamic authentication
PSKpreshared key authentication
TKIP countermeasures timeIndicates the amount of time (in ms) MSS enforces
countermeasures following a second message integrity code (MIC) failure within a
60-second period.
These fields are displayed only when the WPA IE or RSN IE is enabled.
409
Description
vlan-name, session-timeout,
These are examples of authorization attributes that are applied by default to a user
service-type
accessing the SSID managed by this service profile (in addition to any attributes
assigned to the user by a RADIUS server or the local database).
Attributes are listed here only if they have been configured as default attribute settings
for the service profile.
See Table
31 on page 206 for a list of authorization attributes and values that can
Defaults None.
Access Enabled.
History Introduced in MSS Version 6.0.
Examples The following command displays information about session counts for service profile
sp1:
WLC# show service-profile sp1 cac session
Service Profile
sp1
CAC Mode
SESSION
Max Sessions
14
Table 65 describes the fields in displayed by the show service-profile cac session command.
Table 65.Output for show service-profile cac session
Field
Description
Service Profile
CAC Mode
Max Sessions
The number of CAC sessions available on MPs managed by this service profile.
See Also
Copyright 2011, Juniper Networks, Inc.
411
412
STP Commands
Use Spanning Tree Protocol (STP) commands to configure and manage spanning trees on the virtual
LANs (VLANs) configured on an MX, to maintain a loop-free network. This chapter presents STP
commands alphabetically. Use the following table to locate commands in this chapter based on their
use.
STP State
Bridge Priority
Port Cost
Port Priority
Timers
Fast Convergence
Statistics
413
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage This command resets the cost in all VLANs. To reset the cost for only specific VLANs, use
the clear spantree portvlancost command.
Examples The following command resets the STP port cost on ports 5 and 6 to the default value:
MX# clear spantree portcost 5-6
success: change accepted.
See Also
clear spantree portvlancost on page 415
set spantree portcost on page 419
set spantree portvlancost on page 421
show spantree on page 424
show spantree portvlancost on page 428
List of ports. The port priority is reset to 32 (the default) on the specified ports.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage This command resets the priority in all VLANs. To reset the priority for only specific VLANs,
use the clear spantree portvlanpri command.
Examples The following command resets the STP priority on port 9 to the default:
MX# clear spantree portpri 9
success: change accepted.
See Also
414
STP Commands
all
vlan vlan-id
VLAN name or number. MSS resets the cost for only the specified VLAN.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage MSS does not change the port cost for VLANs other than the one(s) you specify.
Examples The following command resets the STP cost for port 12 in VLAN sunflower:
MX# clear spantree portvlancost 12 vlan sunflower
success: change accepted.
See Also
clear spantree portcost on page 414
set spantree portcost on page 419
set spantree portvlancost on page 421
show spantree on page 424
show spantree portvlancost on page 428
List of ports. The port priority is reset to 32 (the default) on the specified ports.
all
vlan vlan-id
VLAN name or number. MSS resets the priority for only the specified VLAN.
Defaults None.
Copyright 2011, Juniper Networks, Inc.
415
Access Enabled.
History Introduced in MSS Version 1.0.
Usage MSS does not change the port priority for VLANs other than the one(s) you specify.
Examples The following command resets the STP priority for port 20 in VLAN avocado:
MX# clear spantree portvlanpri 20 vlan avocado
success: change accepted.
See Also
clear spantree portpri on page 414
set spantree portpri on page 421
set spantree portvlanpri on page 422
show spantree on page 424
vlan vlan-id
VLAN name or number. MSS resets statistics counters for only the specified
VLAN.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command clears STP statistics counters for ports 5, 11, and 19 through
22, for all VLANs:
MX# clear spantree statistics 5,11,19-22
success: change accepted.
See Also show spantree statistics on page 429
set spantree
Enables or disables STP on one VLAN or all VLANs configured on an MX.
Syntax set spantree {enable | disable}
[{all | vlan vlan-id | port port-list vlan-id}]
416
enable
Enables STP.
disable
Disables STP.
all
STP Commands
vlan vlan-id
VLAN name or number. MSS enables or disables STP on only the specified
VLAN, on all ports within the VLAN.
port port-list
vlan-id
Port number or list and the VLAN the ports are in. MSS enables or disables
STP on only the specified ports, within the specified VLAN.
Defaults Disabled.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command enables STP on all VLANs configured on an MX:
MX# set spantree enable
success: change accepted.
The following command disables STP on VLAN burgundy:
MX# set spantree disable vlan burgundy
success: change accepted.
See Also show spantree on page 424
disable
417
all
vlan vlan-id
VLAN name or number. MSS changes the forwarding delay on only the
specified VLAN.
all
vlan vlan-id
VLAN name or number. MSS changes the interval on only the specified
VLAN.
418
STP Commands
all
vlan vlan-id
VLAN name or number. MSS changes the maximum age on only the specified
VLAN.
Defaults The default maximum age for root bridge hello packets is 20 seconds.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command changes the maximum acceptable age for root bridge hello
packets on all VLANs to 15 seconds:
MX# set spantree maxage 15 all
success: change accepted.
See Also show spantree on page 424
List of ports. MSS applies the cost change to all the specified ports.
cost cost
Numeric value. You can specify a value from 1 through 65,535. STP selects
lower-cost paths over higher-cost paths.
Defaults The default port cost depends on the port speed and link type. Table 66 lists the defaults
for STP port path cost.
Table 66.SNMP Port Path Cost Defaults
Port Speed
Link Type
1000 Mbps
19
1000 Mbps
Full Duplex
100 Mbps
19
100 Mbps
Full Duplex
18
100 Mbps
Half Duplex
19
10 Mbps
19
10 Mbps
Full Duplex
95
419
Link Type
10 Mbps
Half Duplex
100
Access Enabled.
History Introduced in MSS Version 1.0.
Usage This command applies only to the default VLAN (VLAN 1). To change the cost of a port in
another VLAN, use the set spantree portvlancost command.
Examples The following command changes the cost on ports 3 and 4 to 20:
MX# set spantree portcost 3,4 cost 20
success: change accepted.
See Also
clear spantree portcost on page 414
clear spantree portvlancost on page 415
set spantree portvlancost on page 421
show spantree on page 424
show spantree portvlancost on page 428
enable
disable
420
STP Commands
priority
value
Priority value. You can specify a value from 0 (highest) through 255 (lowest).
Defaults The default STP priority for all network ports is 128.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage This command applies only to the default VLAN (VLAN 1). To change the priority of a port
in another VLAN, use the set spantree portvlanpri command.
Examples The following command sets the priority of ports 3 and 4 to 48:
MX# set spantree portpri 3-4 priority 48
success: change accepted.
See Also
clear spantree portpri on page 414
clear spantree portvlanpri on page 415
set spantree portvlanpri on page 422
show spantree on page 424
List of ports. MSS applies the cost change to all the specified ports.
cost cost
Numeric value. You can specify a value from 1 through 65,535. STP selects
lower-cost paths over higher-cost paths.
all
vlan vlan-id
VLAN name or number. MSS changes the cost on only the specified VLAN.
Defaults The default port cost depends on the port speed and link type. (See Table 66 on
page 419.)
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command changes the cost on ports 3 and 4 to 20 in VLAN mauve:
Copyright 2011, Juniper Networks, Inc.
421
priority value
Priority value. You can specify a value from 0 (highest) through 255 (lowest).
all
vlan vlan-id
VLAN name or number. MSS changes the priority on only the specified
VLAN.
Defaults The default STP priority for all network ports is 128.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command sets the priority of ports 3 and 4 to 48 on VLAN mauve:
MX# set spantree portvlanpri 3-4 priority 48 vlan mauve
success: change accepted.
See Also
clear spantree portpri on page 414
clear spantree portvlanpri on page 415
set spantree portpri on page 421
show spantree on page 424
422
STP Commands
vlan vlan-id
VLAN name or number. MSS changes the bridge priority on only the specified
VLAN.
Defaults The default root bridge priority for the MX on all VLANs is 32,768.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command sets the bridge priority of VLAN pink to 69:
MX# set spantree priority 69 vlan pink
success: change accepted.
See Also show spantree on page 424
disable
Defaults Disabled.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage The uplink fast convergence feature is applicable to bridges acting as access switches to
the network core (distribution layer) but are not in the core themselves. Do not enable the feature
on MX switches that are in the network core.
Examples The following command enables uplink fast convergence:
MX# set spantree uplinkfast enable
success: change accepted.
See Also show spantree uplinkfast on page 433
423
show spantree
Displays STP configuration and port-state information.
Syntax show spantree [port port-list | vlan vlan-id] [active]
port port-list
List of ports. If you do not specify any ports, MSS displays STP information for
all ports.
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, MSS displays STP
information for all VLANs.
active
Defaults None.
Access All.
History
Version 1.0
Command introduced
Version 4.2
Value STP Off added for STP-State and Port-State fields. This state indicates
that STP is disabled on the port. The Disabled state is still used, but only to
indicate that the port is not forwarding traffic.
Examples The following command displays STP information for VLAN default:
MX# show spantree vlan default
VLAN
PVST+
IEEE
00-02-4a-70-49-f7
32768
19
20 sec
00-0b-0e-02-76-f7
Bridge ID Priority
32768
Vlan
Prio
Portfast
------------------------------------------------------------------
424
Forwarding
19
128
Disabled
STP Off
19
128
Disabled
Disabled
19
128
Disabled
Disabled
19
128
Disabled
Copyright 2011, Juniper Networks, Inc.
STP Commands
Disabled
19
128
Disabled
Disabled
19
128
Disabled
Disabled
19
128
Disabled
Disabled
19
128
Disabled
Description
VLAN
VLAN number.
In the current software version, the mode is always PVST+, which means Per VLAN
Spanning Tree+.
In the current software version, the type is always IEEE, which means STP is based on
the IEEE 802 standards.
Designated Root
Cumulative cost from this bridge to the root bridge. If this MX is the root bridge, then the
root cost is 0.
Bridge ID Priority
Port
Port number.
Note: Only network ports are listed. STP does not apply to MP ports or wired
authentication ports.
Vlan
VLAN ID.
425
Description
STP-State
or
BlockingThe port is not forwarding Layer 2 traffic but is listening to and forwarding
STP control traffic.
Port-State
Cost
Prio
Portfast
426
STP Commands
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Usage The command lists information separately for each VLAN.
Examples The following command shows information about blocked ports on an MX for the
default VLAN (VLAN 1):
MX# show spantree blockedports vlan default
Port
Vlan
Port-State
Cost
Prio
Portfast
-----------------------------------------------------------------------22
190
Blocking
128
Disabled
List of ports. If you do not specify any ports, MSS displays uplink fast
convergence information for all ports.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command shows uplink fast convergence information for all ports:
MX# show spantree portfast
Port
Vlan
Portfast
------------------------- ----
----------
disable
disable
disable
enable
disable
disable
disable
disable
427
10
disable
15
disable
16
disable
17
disable
18
disable
19
disable
20
disable
21
disable
22
disable
11
enable
12
disable
13
disable
14
enable
Description
Port
Port number.
VLAN
VLAN number.
Portfast
List of ports.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command shows the STP port cost of port 1:
MX# show spantree portvlancost 1
port 1 VLAN 1 have path cost 19
See Also
clear spantree portcost on page 414
clear spantree portvlancost on page 415
428
STP Commands
List of ports. If you do not specify any ports, MSS displays STP statistics for
all ports.
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, MSS displays STP
statistics for all VLANs.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Usage The command displays statistics separately for each port.
Examples The following command shows STP statistics for port 1:
MX# show spantree statistics 1
BPDU related parameters
Port 1
VLAN 1
enabled
state
Forwarding
port_id
0x8015
port_number
0x15
path cost
0x4
0(20)
designated_root
00-0b-0e-00-04-30
designated cost
0x0
designated_bridge
00-0b-0e-00-04-30
designated_port
38
top_change_ack
FALSE
config_pending
FALSE
port_inconsistency
none
0 (1)
21825 (43649)
429
0 (0)
2 (2)
1 (1)
1 (1)
inhibit loopguard
FALSE
0 (0)
INACTIVE
15
ACTIVE
INACTIVE
hold timer
INACTIVE
INACTIVE
FALSE
ieee
01-00-0c-cc-cc-cd
bridge priority
32768
00-0b-0e-12-34-56
15
topology change
FALSE
35
FALSE
00-0b-0e-02-76-f6
430
21825
STP Commands
link loading
BPDU in processing
FALSE
received_inferior_bpdu
FALSE
next state
21807
21825
curr_src_mac
00-0b-0e-00-04-30
next_src_mac
00-0b-0e-02-76-f6
Description
Port
Port number.
VLAN
VLAN ID.
state
port_id
port_number
path cost
Cost to use this port to reach the root bridge. This is part of the total path
cost (designated cost).
message age
Age of the protocol information for a port and the value of the maximum
age parameter (shown in parenthesis) recorded by the switch.
designated_root
designated cost
designated_bridge
Bridge to which this MX forwards traffic away from the root bridge.
designated_port
STP port through which this MX forwards traffic away from the root bridge.
top_change_ack
431
Description
Indicates whether a configured BPDU is to be transmitted on expiration of
the hold timer for the port.
port_inconsistency
inhibit loopguard
State of the loop guard. In the current release, the state is always FALSE.
Status of the forwarding delay timer. This timer monitors the time spent by
a port in the listening and learning states.
Status of the message age timer. This timer measures the age of the
received protocol information recorded for a port.
Status of the topology change timer. This timer determines the time period
during which configured BPDUs are transmitted with the topology change
flag set by this MX switch when it is the root bridge, after detection of a
topology change.
hold timer
Status of the hold timer. This timer ensures that configured BPDUs are not
transmitted too frequently through any bridge port.
Status of the delay root port timer, which enables fast convergence when
uplink fast convergence is enabled.
bridge priority
Value of the hello timer interval, in seconds, when this MX switch is the root
or is attempting to become the root.
432
STP Commands
Description
topology change
Time period, in seconds, during which BPDUs are transmitted with the
topology change flag set by this MX switch when it is the root bridge, after
detection of a topology change. It is equal to the sum of the switchs
maximum age and forwarding delay parameters.
MAC address of the bridge from which the MX last received a topology
change.
link loading
BPDU in processing
received_inferior_bpdu
next state
curr_src_mac
next_src_mac
VLAN name or number. If you do not specify a VLAN, MSS displays STP
statistics for all VLANs.
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command shows uplink fast convergence information for all VLANs:
MX# show spantree uplinkfast
VLAN
port
list
433
-----------------------------------------------------------------------1
1(fwd),2,3
Description
VLAN
VLAN number.
port list
Ports in the uplink group. The port that is forwarding traffic is indicated by fwd. The
other ports are blocking traffic.
434
Proxy Reporting
Pseudo-querier
Timers
Router Solicitation
Multicast Routers
Multicast Receivers
Statistics
VLAN name or number. If you do not specify a VLAN, IGMP statistics are
cleared for all VLANs.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command clears IGMP statistics for all VLANs:
Copyright 2011, Juniper Networks, Inc.
435
set igmp
Disables or reenables IGMP snooping on one VLAN or all VLANs on an MX.
Syntax set igmp {enable | disable} [vlan vlan-id]
enable
disable
vlan vlan-id
Amount of time (in tenths of a second) that the MX waits for a response to
a group-specific query after receiving a leave message for that group,
before removing the receiver that sent the leave message from the list of
receivers for the group. If there are no more receivers for the group, the
switch also sends a leave message for the group to multicast routers.
You can specify a value from 1 through 65,535.
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, the timer change
applies to all VLANs.
Defaults The default last member query interval is 10 tenths of a second (1 second).
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command changes the last member query interval on VLAN orange to 5
tenths of a second:
MX# set igmp lmqi 5 vlan orange
success: change accepted.
436
See Also
set igmp oqi on page 438
set igmp qi on page 440
set igmp mrouter on page 437
Port list. MSS adds or removes the specified ports in the list of static multicast
router ports.
enable
disable
Removes the port from the list of static multicast router ports.
disable
vlan vlan-id
437
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command enables multicast router solicitation on VLAN orange:
MX# set igmp mrsol enable vlan orange
success: change accepted.
See Also set igmp mrsol mrsi on page 438
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, MSS changes the
multicast router solicitation interval for all VLANs.
Number of seconds that the MX waits for a general query to arrive before
becoming the querier. You can specify a value from 1 through 65,535.
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, the timer change
applies to all VLANs.
438
Examples The following command changes the other-querier-present interval on VLAN orange to
200 seconds:
MX# set igmp oqi 200 vlan orange
success: change accepted.
See Also
set igmp lmqi on page 436
set igmp qi on page 440
set igmp qri on page 440
set igmp querier on page 441
set igmp mrouter on page 437
set igmp rv on page 442
disable
vlan vlan-id
439
set igmp qi
Changes the IGMP query interval timer on one VLAN or all VLANs on an MX.
Syntax set igmp qi seconds [vlan vlan-id]
qi seconds
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, the timer change
applies to all VLANs.
440
qri tenth-seconds
Amount of time (in tenths of a second) that the MX waits for a receiver to
respond to a group-specific query message before removing the receiver
from the receiver list for the group. You can specify a value from 1 through
65,535.
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, the timer change
applies to all VLANs.
Defaults The default query response interval is 100 tenths of a second (10 seconds).
Access Enabled.
History Introduced in MSS Version 1.0.
Usage The query response interval is applicable only when the MX is querier for the subnet. For
the MX to become the querier, the pseudo-querier feature must be enabled on the MX and the MX
must have the lowest IP address among all the devices eligible to become a querier. To enable the
pseudo-querier feature, use set igmp querier.
Examples The following command changes the query response interval on VLAN orange to 50
tenths of a second (5 seconds):
MX# set igmp qri 50 vlan orange
success: change accepted.
See Also
set igmp lmqi on page 436
set igmp oqi on page 438
set igmp qi on page 440
set igmp querier on page 441
set igmp rv on page 442
disable
vlan vlan-id
441
Network port list. MSS adds the specified ports to the list of static multicast
receiver ports.
enable
disable
Removes the port from the list of static multicast receiver ports.
set igmp rv
Changes the robustness value for one VLAN or all VLANs on an MX switch. Robustness adjusts
the IGMP timers to the amount of traffic loss that occurs on the network.
Syntax set igmp rv num [vlan vlan-id]
num
Robustness value. You can specify a value from 2 through 255. Set the
robustness value higher to adjust for more traffic loss.
vlan vlan-id
VLAN name or number. If you do not specify a VLAN, MSS changes the
robustness value for all VLANs.
See Also
set igmp oqi on page 438
set igmp qi on page 440
set igmp qri on page 440
show igmp
Displays IGMP configuration information and statistics for one VLAN or all VLANs.
Syntax show igmp [vlan vlan-id]
VLAN name or number. If you do not specify a VLAN, MSS displays IGMP
information for all VLANs.
vlan vlan-id
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays IGMP information for VLAN orange:
MX# show igmp vlan orange
VLAN: orange
IGMP is enabled
Proxy reporting is on
Mrouter solicitation is on
Querier functionality is off
Configuration values: qi: 125 oqi: 300 qri: 100 lmqi: 10 rvalue: 2
Multicast
router information:
Port Mrouter-IPaddr Mrouter-MAC
Type
TTL
Group
Port Receiver-IP
17
Receiver-MAC
TTL
none
none undef
443
237.255.255.255
10.10.10.11 00:02:04:06:08:0b
258
237.255.255.255
10.10.10.13 00:02:04:06:08:0d
258
237.255.255.255
10.10.10.14 00:02:04:06:08:0e
258
237.255.255.255
10.10.10.12 00:02:04:06:08:0c
258
237.255.255.255
10.10.10.10 00:02:04:06:08:0a
258
Querier information:
Querier for vlan orange
Port Querier-IP
Querier-MAC
TTL
23
IGMP vlan member ports: 10, 12, 11, 14, 16, 15, 13, 18, 17, 1, 20, 21,
2,
22, 19, 4, 6, 5, 3, 8, 7, 9
IGMP static ports: none
IGMP statistics for vlan orange:
IGMP message type Received Transmitted Dropped
----------------- -------- ----------- ------General-Queries
GS-Queries
Report V1
Report V2
Leave
Mrouter-Adv
Mrouter-Term
Mrouter-Sol
50
101
DVMRP
PIM V1
PIM V2
Topology notifications: 0
Packets with unknown IGMP type: 0
Packets with bad length: 0
Packets with bad checksum: 0
Packets dropped: 4
Table 71 describes the fields in this display.
Table 71.Output for show igmp
444
Field
Description
VLAN
Description
IGMP state.
Proxy reporting
Mrouter solicitation
Querier functionality
Pseudo-querier state.
Query interval.
Other-querier-present interval.
Robustness value.
List of multicast routers and active multicast groups. The fields containing this
information are described separately. The show igmp mrouter command shows the
same information.
Port
Number of the physical port through which the MX switch can reach the router.
Mrouter-IPaddr
Mrouter-MAC
Type
TTL
Number of seconds before this entry ages out if not refreshed. For static multicast
router entries, the time-to-live (TTL) value is undef. Static multicast router entries do not
age out.
Group
IP address of a multicast group. The show igmp receiver-table command shows the
same information as these receiver fields.
Port
Physical port through which the MX switch can reach the groups receiver.
Receiver-IP
Receiver-MAC
TTL
Number of seconds before this entry ages out if the MX does not receive a group
membership message from the receiver. For static multicast receiver entries, the TTL
value is undef. Static multicast receiver entries do not age out.
Querier information
Information about the subnet multicast querier. If the querier is another device, the
fields described below are applicable. If the querier is the MX, the output indicates how
many seconds remain until the next general query message. If IGMP snooping does
not detect a querier, the output indicates this. The show igmp querier command
shows the same information.
VLAN containing the querier. Information is listed separately for each VLAN.
Querier-IP
Querier-MAC
TTL
Number of seconds before this entry ages out if the MX does not receive a query
message from the querier.
445
Description
Physical ports in the VLAN. This list includes all network ports configured to be in the
VLAN and all ports MSS dynamically assigns to the VLAN when a user assigned to the
VLAN becomes a receiver. For example, the list can include an MP access port that is
not configured to be in the VLAN when a user associated with the MP access point on
that port becomes a receiver for a group. When all receivers on a dynamically added
port age out, MSS removes the port from the list.
IGMP statistics
Multicast message and packet statistics. These are the same statistics displayed by the
show igmp statistics command.
See Also
show igmp mrouter on page 446
show igmp querier on page 447
show igmp receiver-table on page 448
show igmp statistics on page 449
vlan vlan-id
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays the multicast routers in VLAN orange:
MX# show igmp mrouter vlan orange
Multicast routers for vlan orange
Port Mrouter-IPaddr
Mrouter-MAC
Type
TTL
33
446
Field
Description
VLAN containing the multicast routers. Ports are listed separately for each VLAN.
Port
Number of the physical port through which the MX can reach the router.
Description
Mrouter-IPaddr
Mrouter-MAC
Type
TTL
Number of seconds before this entry ages out if unused. For static multicast router
entries, the TTL value is undef. Static multicast router entries do not age out.
See Also
set igmp mrouter on page 437
show igmp mrouter on page 446
VLAN name or number. If you do not specify a VLAN, MSS displays querier
information for all VLANs.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples The following command displays querier information for VLAN orange:
MX# show igmp querier vlan orange
Querier for vlan orange
Port Querier-IP
Querier-MAC
TTL
23
The following command shows the information MSS displays when the querier is the MX:
MX# show igmp querier vlan default
Querier for vlan default:
I am the querier for vlan default, time to next query is 20
The output indicates how many seconds remain before the pseudo-querier on the switch
broadcasts the next general query report to IP address 224.0.0.1, the multicast all-systems group.
447
If IGMP snooping does not detect a querier, the output indicates this finding, as shown in the
following example:
MX# show igmp querier vlan red
Querier for vlan red:
There is no querier present on vlan red
This condition does not necessarily indicate a problem. For example, election of the querier might
be in progress.
Table 73 on page 448 describes the fields in the display when a querier other than the MX switch
is present.
Table 73.Output for show igmp querier
Field
Description
VLAN containing the querier. Information is listed separately for each VLAN.
Querier-IP
Querier-MAC
TTL
Number of seconds before this entry ages out if the MX switch does not receive a
query message from the querier.
group
group-ip-addr/mask-length
Defaults None.
Access All.
History Introduced in MSS Version 1.0.
Examples The following command displays all multicast receivers in VLAN orange:
MX# show igmp receiver-table vlan orange
VLAN: orange
Session
Port Receiver-IP
Receiver-MAC
TTL
none
none undef
10.10.10.11 00:02:04:06:08:0b
179
237.255.255.255
10.10.10.13 00:02:04:06:08:0d
179
237.255.255.255
10.10.10.14 00:02:04:06:08:0e
179
237.255.255.255
10.10.10.12 00:02:04:06:08:0c
179
237.255.255.255
10.10.10.10 00:02:04:06:08:0a
179
The following command lists all receivers for multicast groups 237.255.255.1 through
237.255.255.255, in all VLANs:
MX# show igmp receiver-table group 237.255.255.0/24
VLAN: red
Session
Port Receiver-IP
Receiver-MAC
TTL
10.10.20.19 00:02:04:06:09:0d
112
237.255.255.119
10.10.30.31 00:02:04:06:01:0b
112
VLAN: green
Session
Port Receiver-IP
Receiver-MAC
TTL
11
10.10.40.41 00:02:06:08:02:0c
12
237.255.255.255
10.10.60.61 00:05:09:0c:0a:01
111
Description
VLAN
VLAN that contains the multicast receiver ports. Ports are listed separately for each
VLAN.
Session
Port
Physical port through which the MX switch can reach the receiver.
Receiver-IP
Receiver-MAC
TTL
Number of seconds before this entry ages out if the MX does not receive a group
membership message from the receiver. For static multicast receiver entries, the TTL
value is undef. Static multicast receiver entries do not age out.
VLAN name or number. If you do not specify a VLAN, MSS displays IGMP
statistics for all VLANs.
Defaults None.
Access All.
Copyright 2011, Juniper Networks, Inc.
449
GS-Queries
Report V1
Report V2
Leave
Mrouter-Adv
Mrouter-Term
Mrouter-Sol
50
101
DVMRP
PIM V1
PIM V2
Topology notifications: 0
Packets with unknown IGMP type: 0
Packets with bad length: 0
Packets with bad checksum: 0
Packets dropped: 4
Table 75 describes the fields in this display.
Table 75.Output for show igmp statistics
Field
Description
450
Description
Received
Transmitted
Number of packets transmitted. This number includes both multicast packets originated
by the MX and multicast packets received and then forwarded by the switch.
Dropped
Topology notifications
Note: In the current software version, the value in this field is always 0.
Packets with unknown IGMP
type
Packets with bad length
checksum
Packets dropped
451
452
Name of an existing security ACL to clear. ACL names start with a letter
and are case-insensitive.
all
editbuffer-index
Number that indicates which access control entry (ACE) in the security
ACL to clear. If you do not specify an ACE, all ACEs are cleared from
the ACL.
453
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced.
Usage This command deletes security ACLs only in the edit buffer. You must use the commit
security acl command with this command to delete the ACL or ACE from the running
configuration and nonvolatile storage.
The clear security acl command deletes a security ACL, but does not stop the current filtering
function if the ACL is mapped to any virtual LANs (VLANs), ports, or virtual ports, or if the ACL is
applied in a Filter-Id attribute to an authenticated user or group of users with current sessions.
Examples The following commands display the current security ACL configuration, clear acl_133
in the edit buffer, commit the deletion to the running configuration, and redisplay the ACL
configuration to show that it no longer contains acl_133:
MX# show security acl info all
ACL information for all
set security acl ip acl_133 (hits #1 0)
--------------------------------------------------------1. deny IP source IP 192.168.1.6 0.0.0.0 destination IP any
set security acl ip acl_134 (hits #3 0)
--------------------------------------------------------1. permit IP source IP 192.168.0.1 0.0.0.0 destination IP any
enable-hits
set security acl ip acl_135 (hits #2 0)
--------------------------------------------------------1. deny IP source IP 192.168.1.1 0.0.0.0 destination IP any enable-hits
MX# clear security acl acl_133
MX# commit security acl acl_133
configuration accepted
MX# show security acl info all
ACL information for all
set security acl ip acl_134 (hits #3 0)
--------------------------------------------------------1. permit IP source IP 192.168.0.1 0.0.0.0 destination IP any
enable-hits
set security acl ip acl_135 (hits #2 0)
--------------------------------------------------------1. deny IP source IP 192.168.1.1 0.0.0.0 destination IP any enable-hits
454
See Also
clear security acl map on page 455
commit security acl on page 456
set security acl on page 458
show security acl info on page 468
Syntax clear security acl map {acl-name | all} {vlan vlan-id | port port-list
[tag tag-value] | ap apnum} {in | out}
acl-name
Name of an existing security ACL to clear. ACL names start with a letter
and are case-insensitive.
all
Removes security ACL mapping from all physical ports, virtual ports,
and VLANs on an MX switch.
vlan vlan-id
VLAN name or number. MSS removes the security ACL from the
specified VLAN.
port port-list
Port list. MSS removes the security ACL from the specified MX physical
port or ports.
tag tag-value
Tag value that identifies a virtual port in a VLAN. Specify a value from 1
through 4095. MSS removes the security ACL from the specified virtual
port.
ap apnum
in
Removes the security ACL from traffic coming into the MX.
out
Removes the security ACL from traffic going out of the MX.
Defaults None.
Access Enabled.
455
History
MSS Version 1.0
MSS
Version
1.1
MSS
Version
2.0
Command introduced
Keyword and variable tag tag-value added to delete security ACL
mapping from virtual ports
ACL names changed from case-sensitive to case-insensitive
Keyword and variable dap dap-num added to delete security ACL mapping
from Distributed MPs
Usage To clear a security ACL map, type the name of the ACL with the VLAN, physical port or
ports, virtual port tag, or Distributed MP and the direction of the packets to stop filtering. This
command deletes the ACL mapping, but not the ACL.
Examples To clear the mapping of security ACL acljoe from port 4 for incoming packets, type the
following command:
MX# clear security acl map acljoe port 4 in
clear mapping accepted
To clear all physical ports, virtual ports, and VLANs of mapped ACLs on an MX for incoming and
outgoing traffic, type the following command:
MX# clear security acl map all
success: change accepted.
See Also
clear security acl on page 453
set security acl map on page 464
show security acl map on page 470
Name of an existing security ACL to commit. ACL names must start with a
letter and are case-insensitive.
all
Defaults None.
Access Enabled.
456
History
MSS Version 1.0
Command introduced.
Usage Use the commit security acl command to save security ACLs into, or delete them from,
the permanent configuration. Until you commit the creation or deletion of a security ACL, it is
stored in an edit buffer and is not enforced. After you commit a security ACL, it is removed from the
edit buffer.
A single commit security acl all command commits the creation and/or deletion of whatever
show security acl info all editbuffer shows to be currently stored in the edit buffer.
Examples The following commands commit all the security ACLs in the edit buffer to the
configuration, display a summary of the committed ACLs, and show that the edit buffer has been
cleared:
MX# commit security acl all
configuration accepted
MX# show security acl
ACL table
ACL
Type
Class
Mapping
-----------------------
----
------
-------
acl_123
IP
Static
acl_124
IP
Static
hit-sample-rate
This command has been renamed in MSS Version 4.1. To configure the hit sample rate, see set
security acl hit-sample-rate on page 465.
457
Name of an existing security ACL to roll back. ACL names must start with
a letter and are case-insensitive.
all
Rolls back all security ACLs in the edit buffer, clearing all uncommitted
ACEs.
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced.
Examples The following commands show the edit buffer before a rollback, clear any changes in
the edit buffer to security acl_122, and show the edit buffer after the rollback:
MX# show security acl info all editbuffer
ACL edit-buffer information for all
set security acl ip acl_122 (ACEs 3, add 3, del 0, modified 0)
--------------------------------------------------------1. permit IP source IP 20.0.1.11 0.0.0.255 destination IP any
enable-hits
2. deny IP source IP 20.0.2.11 0.0.0.0 destination IP any
3. deny SRC source IP 192.168.1.234 255.255.255.255 enable-hits
MX# rollback security acl acl_122
MX# show security acl info all editbuffer
ACL edit-buffer information for all
See Also show security acl on page 466
set security acl ip acl-name {permit [cos cos] | deny} {source-ip-addr mask |
any} [before editbuffer-index | modify editbuffer-index] [hits]
458
By Layer 4 protocol
set security acl ip acl-name {permit [cos cos] | deny} ip {source-ip-addr mask |
any} {destination-ip-addr mask | any} [[precedence precedence] [tos tos] | [dscp
codepoint]] [before editbuffer-index | modify editbuffer-index] [hits]
By ICMP packets
set security acl ip acl-name {permit [cos cos] | deny} icmp {source-ip-addr
mask | any} {destination-ip-addr mask | any} [type icmp-type] [code icmp-code]
[[precedence precedence] [tos tos] | [dscp codepoint]]
[before editbuffer-index | modify editbuffer-index] [hits]
By TCP packets
set security acl ip acl-name {permit [cos cos] | deny} udp {source-ip-addr mask
| any [operator port [port2]]} {destination-ip-addr mask | any [operator port [port2]]}
[[precedence precedence] [tos tos] | [dscp codepoint]]
[before editbuffer-index | modify editbuffer-index] [hits]
By MAC Address
459
acl-name
Security ACL name. ACL names must be unique within the MX, must
start with a letter, and are case-insensitive. Specify an ACL name of up
to 32 of the following characters:
Letters a through z and A through Z
Numbers 0 through 9
Hyphen (-), underscore (_), and period (.)
Juniper Networks recommends that you do not use the same name with
different capitalizations for ACLs. For example, do not configure two
separate ACLs with the names acl_123 and ACL_123.
Note: In an ACL name, do not include the term all, default-action, map, help, or
editbuffer.
permit
cos cos
deny
protocol
source-ip-addr mask
| any
IP address and wildcard mask of the network or host from of the sent
packet. Specify both address and mask in dotted decimal notation. For
more information, see Wildcard Masks on page 27.
To match on any address, specify any or 0.0.0.0 255.255.255.255.
460
Operand and port number(s) for matching TCP or UDP packets to the
number of the source or destination port on source-ip-addr or
destination-ip-addr. Specify one of the following operands and the
associated port:
eqPackets are filtered for only port number.
gtPackets are filtered for all ports that are greater than port
number.
ltPackets are filtered for all ports that are less than port number.
neqPackets are filtered for all ports except port number.
rangePackets are filtered for ports in the range between port and
port2. To specify a port range, enter two port numbers. Enter the
lower port number first, followed by the higher port number.
(For a complete list of TCP and UDP port numbers, see
www.iana.org/assignments/port-numbers.)
destination-ip-addr mask
| any
IP address and wildcard mask of the network or host to that the packet
is sent. Specify both address and mask in dotted decimal notation. For
more information, see Wildcard Masks on page 27.
To match on any address, specify any or 0.0.0.0 255.255.255.255.
type icmp-type
code icmp-code
precedence
precedence
461
tos tos
dscp codepoint
established
For TCP packets only, applies the ACE only to established TCP
sessions and not to new TCP sessions.
before editbuffer-index Inserts the new ACE in front of another ACE in the security ACL.
Specify the number of the existing ACE in the edit buffer. Index
numbers start at 1. (To display the edit buffer, use show security acl
editbuffer.)
modify editbuffer-index Replaces an ACE in the security ACL with the new ACE. Specify the
number of the existing ACE in the edit buffer. Index numbers start at 1.
(To display the edit buffer, use show security acl editbuffer.)
hits
Tracks the number of packets that are filtered based on a security ACL,
for all mappings.
Defaults By default, permitted packets are classified based on DSCP value, which is converted
into an internal CoS value in the switchs CoS map. The packet is then marked with a DSCP value
based on the internal CoS value. If the ACE contains the cos option, this option overrides the
switchs CoS map and marks the packet based on the ACE.
Access Enabled.
History
462
Command introduced
The any option is supported for the source or destination IP address and
mask. This option is equivalent to 0.0.0.0 255.255.255.255.
The any option is shown in the configuration file as 0.0.0.0 255.255.255.255,
regardless of whether you specify any or 0.0.0.0 255.255.255.255 when you
configure the ACE.
The dscp codepoint is added. This option enables you to filter based on a
packet Differentiated Services Code Point (DSCP) value.
Usage The MX does not apply security ACLs until you activate them with the commit security
acl command and map them to a VLAN, port, or virtual port, or to a user. If the MX is reset or
restarted, any ACLs in the edit buffer are lost.
You cannot perform ACL functions that include permitting, denying, or marking with a Class of
Service (CoS) level on packets with a multicast or broadcast destination address.
The order of security ACEs in a security ACL is important. Once an ACL is active, the ACEs are
checked according to the order in the ACL. If an ACE criterion is met, the action takes place and
any ACEs that follow are ignored.
ACEs are listed in the order in which you create them, unless you move them. To position security
ACEs within a security ACL, use before editbuffer-index and modify editbuffer-index.
Examples The following command adds an ACE to security acl_123 that permits packets from IP
address 192.168.1.11/24 and counts the hits:
MX# set security acl ip acl_123 permit 192.168.1.11 0.0.0.255 hits
The following command adds an ACE to acl_123 that denies packets from IP address
192.168.2.11:
MX# set security acl ip acl_123 deny 192.168.2.11 0.0.0.0
The following command creates acl_125 by defining an ACE that denies TCP packets from source
IP address 192.168.0.1 to destination IP address 192.168.0.2 for established sessions only, and
counts the hits:
MX# set security acl ip acl_125 deny tcp 192.168.0.1 0.0.0.0 192.168.0.2
0.0.0.0 established hits
The following command adds an ACE to acl_125 that denies TCP packets from source IP address
192.168.1.1 to destination IP address 192.168.1.2, on destination port 80 only, and counts the hits:
MX# set security acl ip acl_125 deny tcp 192.168.1.1 0.0.0.0 192.168.1.2
0.0.0.0 eq 80 hits
Finally, the following command commits the security ACLs in the edit buffer to the configuration:
MX# commit security acl all
configuration accepted
See Also
clear security acl on page 453
commit security acl on page 456
Copyright 2011, Juniper Networks, Inc.
463
Syntax set security acl map acl-name {vlan vlan-id | port port-list [tag tag-list] |
ap apnum} {in | out}
acl-name
Name of an existing security ACL to map. ACL names start with a letter and
are case-insensitive.
vlan vlan-id
VLAN name or number. MSS assigns the security ACL to the specified VLAN.
port port-list
Port list. MSS assigns the security ACL to the specified physical MX port or
ports.
tag tag-list
One or more values that identify a virtual port in a VLAN. Specify a single tag
value from 1 through 4095. Or specify a comma-separated list of values, a
hyphen-separated range, or any combination, with no spaces. MSS assigns
the security ACL to the specified virtual port or ports.
ap apnum
One or more MPs, based on their connection IDs. Specify a single connection
ID, or specify a comma-separated list of connection IDs, a hyphen-separated
range, or any combination, with no spaces. MSS assigns the security ACL to
the specified MPs.
in
out
Defaults None.
Access Enabled.
History
MSS Version 1.0
MSS Version 1.1
Command introduced.
Keyword and variable tag tag-list added to allow security ACL mapping to
virtual ports.
ACL names changed from case-sensitive to case-insensitive.
Keyword and variable dap dap-num added to allow security ACL mapping to
Distributed MPs.
Usage Before you can map a security ACL, you must use the commit security acl command to
save the ACL in the running configuration and nonvolatile storage.
464
For best results, map only one input security ACL and one output security ACL to each VLAN,
physical port, virtual port, or Distributed MP to filter a flow of packets. If more than one security
ACL filters the same traffic, MSS applies only the first ACL match and ignores any other matches.
Examples The following command maps security ACL acl_133 to port 4 for incoming packets:
MX set security acl map acl_133 port 4 in
success: change accepted.
See Also
clear security acl map on page 455
commit security acl on page 456
set mac-user attr on page 204
set mac-usergroup attr on page 209
set security acl on page 458
set user attr on page 214
set usergroup on page 216
show security acl map on page 470
Command introduced
Version 4.1
Usage To view counter results for a particular ACL, use the show security acl info acl-name
command. To view the hits for all security ACLs, use the show security acl hits command.
Examples The first command sets MSS to sample ACL hits every 15 seconds. The second and
third commands display the results. The results show that 916 packets matching security acl_153
were sent since the ACL was mapped.
MX# set security acl hit-sample-rate 15
MX# show security acl info acl_153
465
ACL-name
0 acl_2
0 acl_175
916 acl_153
See Also
show security acl hits on page 468
show security acl info on page 468
Type Class
Mapping
IP
Static Port 2 In
acl_133
IP
Static Port 4 In
acl_124
IP
Static
See Also
clear security acl on page 453
commit security acl on page 456
466
Displays the ACEs in each uncommitted ACL. Without this option, only the
ACE names are listed.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To view a summary of the security ACLs in the edit buffer, type the following command:
MX# show security acl editbuffer
ACL edit-buffer table
ACL
Type Status
IP
Not committed
acl-a
IP
Not committed
To view details about these uncommitted ACLs, type the following command.
MX# show security acl info all editbuffer
ACL edit-buffer information for all
set security acl ip acl-111 (ACEs 3, add 3, del 0, modified 2)
---------------------------------------------------1. permit IP source IP 192.168.254.12 0.0.0.0 destination IP any
2. permit IP source IP 192.168.253.11 0.0.0.0 destination IP any
3. deny SRC source IP 192.168.253.1 0.0.0.255
set security acl ip acl-a (ACEs 1, add 1, del 0, modified 0)
---------------------------------------------------1. permit SRC source IP 192.168.1.1 0.0.0.0
See Also
clear security acl on page 453
commit security acl on page 456
467
ACL-name
0 acl_2
0 acl_175
916 acl_123
See Also
hit-sample-rate on page 457
set security acl on page 458
Name of an existing security ACL to display. ACL names must start with a
letter and are case-insensitive.
all
editbuffer
Displays the contents of the specified security ACL or all security ACLs that
are stored in the edit buffer after being created with set security acl. If you do
not use this parameter, only committed ACLs are shown.
Defaults None.
468
Access Enabled.
History
MSS Version
1.0
Command introduced
MSS Version
1.1
MSS Version
4.1
The acl-name | all option is no longer required; show security acl info is valid
and displays the same information as security acl info all.
The following command displays the contents of acl_123 in the edit buffer, including the committed
ACE rules 1 and 2 and the uncommit:
Syntax security acl info [acl-name | all] [editbuffer]
acl-name
Name of an existing security ACL to display. ACL names must start with a
letter and are case-insensitive.
all
editbuffer
Displays the contents of the specified security ACL or all security ACLs that
are stored in the edit buffer after being created with set security acl. If you do
not use this parameter, only committed ACLs are shown.
Examples To display the contents of all security ACLs committed on an MX, type the following
command:
MX# show security acl info
ACL information for all
set security acl ip acl_123 (hits #5 462)
--------------------------------------------------------1. permit IP source IP 192.168.1.11 0.0.0.255 destination IP any
enable-hits
2. deny IP source IP 192.168.2.11 0.0.0.0 destination IP any
set security acl ip acl_134 (hits #3 0)
--------------------------------------------------------1. permit IP source IP 192.168.0.1 0.0.0.0 destination IP any
enable-hits
set security acl ip acl_135 (hits #2 0)
--------------------------------------------------------1. deny IP source IP 192.168.1.1 0.0.0.0 destination IP any enable-hits
The following command displays the contents of acl_123 in the edit buffer, including the
committed ACE rules 1 and 2 and the uncommitted rule 3:
MX# show security acl info acl_123 editbuffer
ACL edit-buffer information for acl_123
Copyright 2011, Juniper Networks, Inc.
469
Defaults None.
Access Enabled.
History
MSS Version 1.0
Command introduced
Examples The following command displays the port to which security ACL acl_111 is mapped:
MX# show security acl map acl_111
ACL acl_111 is mapped to:
Port 4 in
See Also
clear security acl map on page 455
set security acl map on page 464
show security acl on page 466
470
: 2
: 1
: 2
: 1
: 2
: 0
: 2
: 1
Sub-chain count
: 0
: 0 (max: 512)
: 2 (max: 151)
Leaves in secondary
: 0 (max 12096)
: 1
: 0
UC switchdest
: 0
ACL resources
Port number
: 0
: 2
LUdef in use
: 5
: c8007dc
L4 global
: True
No rules
: False
Non-IP rules
: False
Root in first
: True
: False
471
Out mapping
: False
In mapping
: True
: False
No VPORT mapping
: True
Table 76 explains the fields in the show security acl resource-usage output.
Table 76.show security acl resource-usage Output
Field
Description
Number of rules
Number of chained security ACL data entries stored in the rule tree.
Longest chain of security ACL data entries stored in the rule tree.
Number of non-leaf
nodes
Uncompressed Rule
Number of security ACEs stored in the rule tree, including duplicatesACEs in ACLs applied
Count
Number of data elements in the rule tree, from the root to the furthest data entry (leaf).
Sub-chain count
PSCBs in primary
Number of pattern search control blocks (PSCBs) stored in primary node memory.
memory
PSCBs in secondary
memory
Leaves in primary
Leaves in secondary
Fragmentation control
Note: The current MSS version filters only the first packet of a fragmented IP packet and
passes the remaining fragments.
UC switchdest
Note: The current MSS version filters only the first packet of a fragmented IP packet and
passes the remaining fragments.
Port number
Note: The current MSS version filters only the first packet of a fragmented IP packet and
passes the remaining fragments.
Number of action types
Number of actions that can be performed by ACLs. This value is always 2, because ACLs can
either permit or deny.
LUdef in use
Number of the lookup definition (LUdef) table currently in use for packet handling.
Memory address used for packet handling, from which default action data is obtained when
necessary.
472
Description
L4 global
No rules
Non-IP rules
Note: The current MSS version supports security ACEs for IP only.
Root in first
No per-user (MAC)
mapping
Per-user application of a security ACL with the Filter-Id attribute, on the MX switch:
TrueNo security ACLs are applied to users.
FalseSecurity ACLs are applied to users.
Out mapping
In mapping
No VLAN or PORT
mapping
No VPORT mapping
473
474
Cryptography Commands
Informational Note: A digital certificate is a form of electronic identification for computers. The MX requires digital certificates to
authenticate communications to RingMaster and Web View, to WebAAA clients, and to Extensible Authentication Protocol (EAP)
clients for which the MX performs all EAP processing. Certificates can be generated on the MX or obtained from a certificate authority
(CA). Keys contained within the certificates allow the MX, the servers, and the wireless clients to exchange information secured by
encryption.
Informational Note: If the MX does not already have certificates, MSS automatically generates the
missing ones the first time the MX boots with MSS Version 4.2 or later. You do not need to install certificates
unless you want to replace the ones automatically generated by MSS. (For more information, see the
Certificates Automatically Generated by MSS section in the Managing Keys and Certificates chapter of the
Juniper Mobility System Software Configuration Guide.)
Informational Note: Before installing a new certificate, verify with the show timedate and show
timezone commands that the MX is set to the correct date, time, and time zone. Otherwise, certificates might
not be installed correctly.
This chapter presents cryptography commands alphabetically. Use the following table to locate commands
in this chapter based on their use.
Encryption Keys
PKCS #7 Certificates
Self-Signed Certificate
475
crypto ca-certificate
Installs a certificate authoritys own PKCS #7 certificate into the MX certificate and key storage
area.
Syntax crypto ca-certificate {admin | eap | web} PEM-formatted-certificate
admin
eap
web
Stores the certificate authoritys certificate that signed the WebAAA certificate
for the MX.
The Web certificate authenticates the MX to clients who use WebAAA.
Command introduced
Version 3.0
Version 4.1
Usage The Privacy-Enhanced Mail protocol (PEM) format is used for representing a PKCS #7
certificate in ASCII text. PEM uses base64 encoding to convert the certificate to ASCII text, then
puts the encoded text between the following delimiters:
-----BEGIN CERTIFICATE---------END CERTIFICATE----To use this command, you must already have obtained a copy of the certificate from the certificate
authority as a PKCS #7 object file. Then do the following:
1. Open the PKCS #7 object file with an ASCII text editor such as Notepad or vi.
2. Enter the crypto ca-certificate command on the CLI command line.
3. When MSS prompts for the PEM-formatted certificate, paste the PKCS #7 object file onto the
command line.
476
Cryptography Commands
Examples The following command adds the certificate from the certificate authority to MX
certificate and key storage:
MX# crypto ca-certificate admin
Enter PEM-encoded certificate
-----BEGIN CERTIFICATE----MIIDwDCCA2qgAwIBAgIQL2jvuu4PO5FAQCyewU3ojANBgkqhkiG9wOBAQUFADCB
mzerMClaweVQQTTooewi\wpoer0QWNFNkj90044mbdrl1277SWQ8G7DiwYUtrqoQplKJvxz
.....
Lm8wmVYxP56M;CUAm908C2foYgOY40=
-----END CERTIFICATE----See Also show crypto ca-certificate on page 485
crypto certificate
Installs one of the MX PKCS #7 certificates into the certificate and key storage area on the MX. The
certificate, which is issued and signed by a certificate authority, authenticates the MX either to
RingMaster or Web View, or to 802.1X supplicants (clients).
Syntax crypto certificate {admin | eap | web} PEM-formatted certificate
admin
eap
web
PEM-formatted
certificate
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Version 4.1
Usage To use this command, you must already have generated a certificate request with the
crypto generate request command, sent the request to the certificate authority, and obtained a
signed copy of the MX certificate as a PKCS #7 object file. Then do the following:
1. Open the PKCS #7 object file with an ASCII text editor such as Notepad or vi.
2. Enter the crypto certificate command on the CLI command line.
Copyright 2011, Juniper Networks, Inc.
477
3. When MSS prompts you for the PEM-formatted certificate, paste the PKCS #7 object file in the
command line.
The MX verifies the validity of the public key associated with this certificate before installing it, to
prevent a mismatch between the MX private key and the public key in the installed certificate.
Examples The following command installs a certificate:
MX# crypto certificate admin
Enter PEM-encoded certificate
-----BEGIN CERTIFICATE----MIIBdTCP3wIBADA2MQswCQYDVQQGEwJVUzELMAkGA1UECBMCQOExGjAYBgNVBAMU
EXR1Y2hwdWJzQHRycHouY29tMIGfMAOGCSqGSIb3DQEBAQAA4GNADCBiQKBgQC4
.....
2L8Q9tk+G2As84QYLm8wmVY>xP56M;CUAm908C2foYgOY40=
-----END CERTIFICATE----See Also
crypto generate request on page 479
crypto generate self-signed on page 481
domain
eap
ssh
web
Defaults None.
Access Enabled.
478
Cryptography Commands
History
Version 1.0
Command introduced
Version 2.0
Version 3.0
Version 4.1
Version 5.0
Usage You can overwrite a key by generating another key of the same type.
SSH requires an SSH authentication key, but you can allow MSS to generate it automatically. The
first time an SSH client attempts to access the SSH server on an MX, the MX automatically
generates a 1024-byte SSH key. If you want to use a 2048-byte key instead, use the crypto
generate key ssh 2048 command to generate one.
Examples To generate an administrative key for use with RingMaster, type the following
command:
MX# crypto generate key admin 1024
key pair generated
See Also show crypto key ssh on page 487
eap
web
After type the command, you are prompted for the following variables:
Country Name
string
State Name string (Optional) Specify the name of the state, in up to 64 alphanumeric
characters. Spaces are allowed.
479
Locality Name
string
Organizational
Name string
Organizational
Unit string
Common Name
string
Email Address
string
Unstructured
Name string
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Version 4.1
Usage To use this command, you must already have generated a public-private encryption key
pair with the crypto generate key command.
Enter crypto generate request admin, crypto generate request eap, or crypto generate
request web and press Enter. When you are prompted, type the identifying values in the fields, or
press Enter if the field is optional. You must enter a common name for the MX.
This command outputs a PKCS #10 text string in Privacy-Enhanced Mail protocol (PEM) format
that you paste to another location for submission to the certificate authority. You then send the
request to the certificate authority to obtain a signed copy of the MX certificate as a PKCS #7
object file.
Examples To request an administrative certificate from a certificate authority, type the following
command:
MX# crypto generate request admin
Country Name: US
State Name: CA
Locality Name: Pleasanton
Organizational Name: Trapeze
480
Cryptography Commands
eap
web
After type the command, you are prompted for the following variables:
Country Name
string
Locality Name
string
481
Organizational
Name string
Note: Organizational
Unit string
Common Name
string
Email Address
string
Command introduced
Version 3.0
Version 4.1
Usage To use this command, you must already have generated a public-private encryption key
pair with the crypto generate key command.
Examples To generate a self-signed administrative certificate, type the following command:
MX# crypto generate self-signed admin
Country Name:
State Name:
Locality Name:
Organizational Name:
Organizational Unit:
Common Name: [email protected]
Email Address:
Unstructured Name:
success: self-signed cert for admin generated
482
Cryptography Commands
See Also
crypto certificate on page 477
crypto generate key on page 478
crypto otp
Usage Sets a one-time password (OTP) for use with the crypto pkcs12 command.
Syntax crypto otp {admin | eap | web} one-time-password
admin
Creates a one-time password for installing a PKCS #12 object file for
an administrative certificate and key pairand optionally the certificate
authoritys own certificateto authenticate the MX switch to
RingMaster or Web View.
eap
Creates a one-time password for installing a PKCS #12 object file for
an EAP certificate and key pairand optionally the certificate
authoritys own certificateto authenticate the MX switch to 802.1X
supplicants (clients).
web
Creates a one-time password for installing a PKCS #12 object file for a
WebAAA certificate and key pairand optionally the certificate
authoritys own certificateto authenticate the MX to WebAAA clients.
one-time-password
Command introduced
Version 3.0
Version 4.1
483
Usage The password allows the public-private key pair and certificate to be installed together from
the same PKCS #12 object file. MSS erases the one-time password after processing the
crypto pkcs12 command or when you reboot the MX.
Juniper Networks recommends that you create a password that is memorable to you but is not
subject to easy guesses or a dictionary attack. For best results, create a password of
alphanumeric uppercase and lowercase characters.
Examples The following command creates the one-time password hap9iN#ss for installing an
EAP certificate and key pair:
MX# crypto generate otp eap hap9iN#ss
OTP set
See Also crypto pkcs12 on page 484
crypto pkcs12
Usage Unpacks a PKCS #12 object file into the certificate and key storage area on the MX. This
object file contains a public-private key pair, an MX certificate signed by a certificate authority, and
the certificate authoritys certificate.
Syntax crypto pkcs12 {admin | eap | web} file-location-url
admin
Unpacks a PKCS #12 object file for an administrative certificate and key
pairand optionally the certificate authoritys own certificatefor
authenticating the MX to RingMaster or Web View.
eap
Unpacks a PKCS #12 object file for an EAP certificate and key
pairand optionally the certificate authoritys own certificatefor
authenticating the MX to 802.1X supplicants (clients).
web
Unpacks a PKCS #12 object file for a WebAAA certificate and key
pairand optionally the certificate authoritys own certificatefor
authenticating the MX switch to WebAAA clients.
file-location-url
Defaults The password you enter with the crypto otp command must be the same as the one
protecting the PKCS #12 file.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Version 4.1
Usage To use this command, you must have already created a one-time password with the
crypto otp command.
484
Cryptography Commands
You must also have the PKCS #12 object file available. You can download a PKCS #12 object file
via TFTP from a remote location to the local nonvolatile storage system on the MX.
Examples The following commands copy a PKCS #12 object file for an EAP certificate and key
pairand optionally the certificate authoritys certificatefrom a TFTP server to nonvolatile
storage on the MX, create the one-time password hap9iN#ss, and unpack the PKCS #12 file:
MX# copy tftp://192.168.253.1/2048full.p12 2048full.p12
success: received 637 bytes in 0.253 seconds [ 2517 bytes/sec]
MX# crypto otp eap hap9iN#ss
OTP set
MX# crypto pkcs12 eap 2048full.p12
Unwrapped from PKCS12 file:
keypair
device certificate
CA certificate
See Also crypto otp on page 483
admin
Displays information about the certificate authoritys certificate that signed the
administrative certificate for the MX.
The administrative certificate authenticates the MX to RingMaster or Web View.
eap
Displays information about the certificate authoritys certificate that signed the
Extensible Authentication Protocol (EAP) certificate for the MX.
The EAP certificate authenticates the MX to 802.1X supplicants (clients).
web
Displays information about the certificate authoritys certificate that signed the
WebAAA certificate for the MX.
The WebAAA certificate authenticates the MX to WebAAA clients.
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Version 4.1
Examples To display information about the certificate of a certificate authority, type the following
command:
Copyright 2011, Juniper Networks, Inc.
485
Description
Version
Serial Number
Subject
Signature Algorithm
Algorithm that created the signature, such as RSA MD5 or RSA SHA.
Issuer
Validity
See Also
crypto ca-certificate on page 476
show crypto certificate on page 486
eap
web
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Version 4.1
Usage You must have generated a self-signed certificate or obtained a certificate from a certificate
authority before displaying information about the certificate.
Examples To display information about a cryptographic certificate, type the following command:
MX# show crypto certificate eap
Table 78 describes the fields of the display.
486
Cryptography Commands
Description
Version
Serial Number
Subject
Signature Algorithm
Algorithm that created the signature, such as RSA MD5 or RSA SHA.
Issuer
Validity
See Also
crypto generate self-signed on page 481
show crypto ca-certificate on page 485
487
488
Command Auditing
LDAP Servers
RADIUS Client
RADIUS Diagnostics
RADIUS Servers
Server Groups
Copyright 2011, Juniper Networks, Inc.
(For information about RADIUS attributes, see the RADIUS appendix in the Juniper Mobility System
Software Configuration Guide.)
490
clear radius
Usage Resets parameters that were globally configured for RADIUS servers to the default values.
Syntax clear radius {deadtime | key | retransmit | timeout}
deadtime
key
retransmit
timeout
491
keyNo key
retransmit3 (the total number of attempts, including the first attempt)
timeout5 seconds
Access Enabled.
History Introduced in MSS 1.0.
Usage To override the globally set values on a particular RADIUS server, use the set radius
server command.
Examples To reset all global RADIUS parameters to their factory defaults, type the following
commands:
MX# clear radius deadtime
success: change accepted.
MX# clear radius key
success: change accepted.
MX# clear radius retransmit
success: change accepted.
MX# clear radius timeout
success: change accepted.
See Also
set radius on page 498
set radius server on page 503
show aaa on page 218
Usage The clear radius client system-ip command causes the MX to use the IP address of the
interface through which the MX sends a RADIUS client request as the source IP address. The MX
selects a source interface address based on information in the routing table as the source address
for RADIUS packets leaving the MX.
Examples To clear the system IP address as the permanent source address for RADIUS client
requests, type the following command:
MX# clear radius client system-ip
success: change accepted.
See Also
set radius client system-ip on page 501
show aaa on page 218
493
Name of a RADIUS server configured to perform remote AAA services for the
MX.
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Examples The following command removes the RADIUS server rs42 from a list of remote AAA
servers:
MX# clear radius server rs42
success: change accepted.
See Also
set radius server on page 503
show aaa on page 218
load-balance
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage Deleting a server group removes the server group from the configuration. However, the
members of the server group remain.
Examples To remove the server group sg-77 type the following command:
MX# clear server group sg-77
success: change accepted.
To disable load balancing in a server group shorebirds, type the following command:
MX# set server group shorebirds load-balance disable
success: change accepted.
See Also set server group on page 505
ldap-ping
Usage Provides a diagnostic tool to enhance troubleshooting capabilities for LDAP servers on the
network.
494
radping
Usage Provides a diagnostic tool to enhance troubleshooting capabilities for RADIUS servers on
the network. The command sends an authentication request to the RADIUS server to determine if
it is offline.
Syntax MX# radping {server |servername | group servergroup}request [acct-off |
acct-on | acct-start | acct-stop | acct-update | authentication] user
username password password auth-type {plain|mschap2}
server
servername
group
servergroup
request
acct-off
acct-on
Send accounting requests to the RADIUS server to collect and start or stop
user statistics.
acct-start
acct-stop
acct-update
authentication
user
username
password
password
auth-type
plain|mschap2
Defaults None
Access Enabled.
History Introduced in MSS Version 6.2.
Examples To verify that a RADIUS server, alpha with the username, smith5, password, swordfish,
is active on the network, type the following command:
MX# radping alpha request authentication user smith5 password swordfish
auth-type mschap2
Sending authentication request to server test-27708 (10.20.30.40:1812)
495
To send an accounting request to the RADIUS server, use the following command:
MX# radping alpha request acct-start
To stop the accounting requests, use the following commands:
MX# radping alpha request acct-stop
set ldap
Usage Configure additional settings for an LDAP configuration.
Syntax set ldap [ auth-port port] [base-dn basedn]
[bind-mode simpleauth | sasl-md5] [deadtime mins] [mac-addr-format
hyphens |colons | one-hyphen | raw] [timeout seconds]
auth-port
port
base-dn
basedn
bind-mode
simple-auth | sasl-md5
deadtime
mins
mac-addr-format
Defaults None
Access Enabled
History Introduced in MSS 7.1
496
497
set radius
Usage Configures global defaults for RADIUS servers that do not explicitly set these values
themselves. By default, the MX automatically sets all these values except the password (key).
Syntax set radius {author-password use-mac-address | deadtime minutes |
das-port port encrypted-key string | key string | [mac-addr-format [colons |
hyphens | one-hypen | raw]] retransmit number | timeout seconds}
author-password
use-mac-address
das-port port
Set the dynamic authorization port for all DACs. The value can be 1,
65535, or 3799.
deadtime minutes
encrypted-key string
key string
mac-addr-format
[colons | hyphens |
one-hyphen | raw]
Sets the MAC address format for all RADIUS servers using the
author-password option. MAC addresses can have the following
formats:
colons12:34:56:78:9a:bc
hyphens123456789abc
one-hyphen 123456789abc
raw123456789abc
498
retransmit number
timeout seconds
Command introduced
Version 4.2
Usage You can specify only one parameter per command line.
Examples The following commands sets the dead time to 5 minutes, the RADIUS key to goody,
the number of retransmissions to 1, and the timeout to 21 seconds on all RADIUS servers
connected to the MX switch:
MX-20# set radius deadtime 5
success: change accepted.
MX-20# set radius key goody
success: change accepted.
MX-20# set radius retransmit 1
success: change accepted.
MX-20# set radius timeout 21
success: change accepted.
See Also
clear radius server on page 493
set radius server on page 503
show aaa on page 218
499
500
port udp-port-number
acct-port
acct-udp-port-number
key string
Defaults The default UDP port number for access-requests is 1812. The default UDP port number
for stop-accounting records is 1813.
Access Enabled.
Copyright 2011, Juniper Networks, Inc.
501
tag tag-value
802.1Q tag value in packets sent by the third-party AP for the SSID.
ssid ssid-name
Defaults None.
Access Enabled.
History Introduced in MSS 4.0.
Usage AAA for third-party AP users has additional configuration requirements. See the
Configuring AAA for Users of Third-Party APs section in the Configuring AAA for Network
Users chapter of the Juniper Mobility System Software Advanced Configuration Guide.
Enter a separate command for each SSID, and the tag value that you want the MX to support.
Examples The following command maps SSID mycorp to packets received on port 3 or 4, using
802.1Q tag value 104:
MX# set radius proxy port 3-4 tag 104 ssid mycorp
success: change accepted.
See Also
clear radius proxy port on page 493
set authentication proxy on page 198
set radius proxy client on page 501
502
address ip-address
auth-port
port-number
retransmit number
deadtime minutes
key string |
Password (shared secret key) the MX uses to authenticate to RADIUS
encrypted-key string servers. You must provide the same password that is defined on the
RADIUS server. The password can be 1 to 64 characters long, with no
spaces or tabs.
Use the key option to enter the string in its unencrypted form. MSS
encrypts the displayed form of the string in show config and
show aaa output.
To enter the string in its encrypted form instead, use the
encrypted-key option. MSS does not encrypt the string you enter,
and instead displays the string exactly as you enter it.
503
mac-addr-format
hyphen|colons|
one-hyphen|raw
author-password
password
Command introduced
Version 4.2
Usage For a given RADIUS server, the first instance of this command must set both the server
name and the IP address and can include any or all of the other optional parameters. Subsequent
instances of this command can be used to set optional parameters for a given RADIUS server.
To configure the server as a remote authenticator for the MX switch, you must add it to a server
group with the set server group command.
Do not use the same name for a RADIUS server and a RADIUS server group.
Examples To set a RADIUS server named RS42 with IP address 198.162.1.1 to use the default
accounting and authorization ports with a timeout interval of 30 seconds, two transmit attempts,
5 minutes of dead time, a key string of keys4u, and the default authorization password of trapeze,
type the following command:
MX-20# set radius server RS42 address 198.162.1.1 timeout 30 retransmit
2 deadtime 5 key keys4U
504
See Also
set authentication admin on page 186
set authentication console on page 188
set authentication dot1x on page 190
set authentication mac on page 194
set authentication web on page 199
set radius on page 498
set server group on page 505
show aaa on page 218
members
server-name1
The names of one or more configured RADIUS servers. You can enter up to
four server names.
server-name2
server-name3
server-name4
Defaults None.
Access Enabled.
History Introduced in MSS 1.0.
Usage You must assign all group members simultaneously, as shown in the example. To enable
load balancing, use set server group load-balance enable.
Do not use the same name for a RADIUS server and a RADIUS server group.
Examples To set server group shorebirds with members heron, egret, and sandpiper, type the
following command:
MX-20# set server group shorebirds members heron egret sandpiper
success: change accepted.
See Also
clear server group on page 494
set server group load-balance on page 505
show aaa on page 218
505
load-balance
enable | disable
show ldap
Usage Displays configuration information about LDAP servers.
Syntax show ldap
Defaults None
Access Enabled
History Introduced in MSS 7.1.
Examples Use the following command to display information about LDAP configurations.
MX# show ldap
LDAP Servers Default Values
auth-port=389, timeout=5(s),
506
deadtime=5(mn)
Copyright 2011, Juniper Networks, Inc.
bind-mode=sasl-md5,
mac-addr-format=hyphens
LDAP Servers
Flags: (state)
U=up, D=down
(bind-mode)
s=simple-auth, m=sasl-md5
Server
IP address
Flags
Port Out
s:bm
Conf:Rem
FQDN
10.8.112.212
389
:0m
U:mh
testldap
10.1.1.1
389
:0m
U:mh
trapeze.com
Server groups
techldap: testldap
Table 79.show LDAP output
Field
Description
Default values
Flags
Server
IP Address
Auth Port
Time Out
Dead Time
Flags
FQDN
The fully qualified domain name associated with the LDAP server.
Server Group
Names of LDAP server groups and member servers configured on the MX.
Server Port
show radius
Usage Displays configuration information about RADIUS servers.
Syntax show radius
Defaults None
Access Enabled
Copyright 2011, Juniper Networks, Inc.
507
IP Address
------- ----------
Auth
Port
Acct
Time
Retry
Port
Out
-------- Time
Dead
-------
------- ------
State
-------
--------
rs1
172.21.14.3 1812
0
1813
UP
rs2
1.1.1.1
1812
1813
UP
dummy
172.21.14.3 1812
1
1813
UP
Server groups
SG1:rs1
SG2:dummy
Radius Dynamic Authorization Configuration
Server port: 3799
Table 80 describes the fields that can appear in the show radius output.
Table 80.show radius Output
Field
Description
Default values
Server
IP Address
Auth Port
Acct Port
Retry
Dead Time
508
Description
State
UP (operating)
DOWN (unavailable)
Server Group
Names of RADIUS server groups and member servers configured on the MX.
Configuration
Server Port
Dynamic Author
Dynamic Author Clients
IP Address
Disconnect
Disconnected clients
Change Author
Replay Protect
Replay Win
509
510
Caution: 802.1X parameter settings are global for all SSIDs configured on the MX.
Wired Authentication
Port Control
Keys
Bonded Authentication
Reauthentication
Retransmission
511
512
Defaults By default, all wired authentication ports are set to auto and they process authentication
requests as determined by the set authentication dot1X command.
Access Enabled.
History Introduced in MSS 1.0.
Usage This command is overridden by the set dot1x authcontrol command. The clear dot1x
port-control command returns port control to the method configured. This command applies only
to wired authentication ports.
Examples Type the following command to reset the wired authentication port control:
MX# clear dot1x port-control
success: change accepted.
See Also
set dot1x port-control on page 518
show dot1x on page 523
513
disable
515
Defaults The default bonded period is 0 seconds, which disables the feature.
Access Enabled.
History Introduced in MSS 2.1.
Usage Normally, the Bonded Auth period needs to be set only if the network has Bonded Auth
clients that use dynamic WEP, or use WEP-40 or WEP-104 encryption with WPA or RSN. These
clients can be affected by the 802.1X reauthentication parameter or the RADIUS Session-Timeout
parameter.
Juniper Networks recommends that you try 60 seconds, and change the period to a longer value
only if clients are unable to authenticate within 60 seconds.
The bonded authentication period applies only to 802.1X authentication rules that contain the
bonded option.
Examples To set the bonded authentication period to 60 seconds, type the following command:
MX# set dot1x bonded-period 60
success: change accepted.
See Also
clear dot1x bonded-period on page 512
show dot1x on page 523
disable
516
517
Defaults None
Access Enabled
History Introduced in MSS 7.1
forceunauth
auto
port-list
One or more wired authentication ports for which to set 802.1X port control.
Permits reauthentication.
disable
Denies reauthentication.
519
seconds
Command introduced.
Usage You also can use the RADIUS session-timeout attribute to set the reauthentication timeout
for a specific client. In this case, MSS uses the timeout that has the lower value. If the
session-timeout is set to fewer seconds than the global reauthentication timeout, MSS uses the
session-timeout for the client. However, if the global reauthentication timeout is shorter than the
session-timeout, MSS uses the global timeout instead.
Examples Type the following command to set the number of seconds to 100 before
reauthentication is attempted:
MX# set dot1x reauth-period 100
success: dot1x auth-server timeout set to 100.
See Also
clear dot1x reauth-period on page 514
show dot1x on page 523
521
Defaults None
Access Enabled
History Introduced in MSS 7.1
Warning: enable
Warning: Causes the broadcast and multicast keys for WEP to be rotated at an interval set by
the set dot1x wep-rekey-period for each radio, associated VLAN, and encryption type. The MX
generates the new broadcast and multicast keys and pushes the keys to the clients via EAPoL
key messages.
Warning: disable Warning: WEP broadcast and multicast keys are never rotated.
522
Command introduced.
Examples Type the following command to set the WEP-rekey period to 300 seconds:
MX# set dot1x wep-rekey-period 300
success: dot1x wep-rekey-period set to 300
See Also
set dot1x wep-rekey on page 522
show dot1x on page 523
show dot1x
Usage Displays 802.1X client information for statistics and configuration settings.
Syntax show dot1x {clients | stats | config}
clients
stats
config
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
523
Version 2.1
Version 3.1
State
-------------
Vlan
-------
------
Identity
----------
00:20:a6:48:01:1f
Connecting
(unknown)
00:05:3c:07:6d:7c
Authenticated
vlan-it
EXAMPLE\jose
00:05:5d:7e:94:83
Authenticated
vlan-eng
EXAMPLE\singh
00:02:2d:86:bd:38
Authenticated
vlan-eng
00:05:5d:7e:97:b4
Authenticated
vlan-eng
EXAMPLE\havel
00:05:5d:7e:98:1a
Authenticated
vlan-eng
EXAMPLE\nash
00:0b:be:a9:dc:4e
Authenticated
vlan-pm
00:05:5d:7e:96:e3
Authenticated
vlan-eng
EXAMPLE\mishan
00:02:2d:6f:44:77
Authenticated
vlan-eng
EXAMPLE\ethan
00:05:5d:7e:94:89
EXAMPLE\fmarshall
Authenticated
vlan-eng
00:06:80:00:5c:02
EXAMPLE\bmccarthy
Authenticated
vlan-eng
00:02:2d:6a:de:f2
[email protected]
Authenticated
vlan-pm
00:02:2d:5e:5b:76
Authenticated
vlan-pm
EXAMPLE\tamara
00:02:2d:80:b6:e1
Authenticated
vlan-cs
00:30:65:16:8d:69
authenticated
Authenticated
vlan-wep
MAC
00:02:2d:64:8e:1b
Authenticated
vlan-eng
EXAMPLE\wong
524
setting
----------------
-------
supplicant timeout
30
auth-server timeout
30
quiet period
transmit period
reauthentication period
3600
maximum requests
key transmission
enabled
reauthentication
enabled
authentication control
enabled
1800
WEP rekey
enabled
Bonded period
60
value
----------------
-----
Enters Connecting:
709
112
Enters Authenticating:
467
52
525
31
85
Description
Enters Connecting
Number of times that the MX state transitions to the CONNECTING state from any
other state.
Enters Authenticating
526
Network Sessions
Mesh AP Sessions
clear sessions
Usage Clears all administrative sessions, or clears administrative console or Telnet sessions.
Syntax clear sessions {admin | console | telnet client
mesh-ap [session-id session-id]}
admin
Clears sessions for all users with administrative access to the MX through a
Telnet or SSH connection or a console plugged into the switch.
console
Clears sessions for all users with administrative access to the MX through a
console plugged into the switch.
telnet
Clears sessions for all users with administrative access to the MX through a
Telnet connection.
telnet client
[session-id]
Clears all Telnet client sessions from the CLI to remote devices, or clears
an individual session identified by session ID.
mesh-ap
[session-id]
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced.
Version 1.1
Version 6.0
527
Clears all network sessions for a specified MP and radio. Specify radio 1
or 2.
mac-addr
mac-addr-glob
Clears all network sessions for a MAC address. Specify a MAC address in
hexadecimal numbers separated by colons (:), or use the wildcard
character (*) to specify a set of MAC addresses. (For details, see MAC
Address Globs on page 27.)
session-id
local-session-id
Clears the specified 802.1X network session. To find local session IDs,
use the show sessions command.
ssid name
user user-glob
528
vlan vlan-glob
wired
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage The clear sessions network command clears network sessions by deauthenticating and,
for wireless clients, disassociating them.
Examples To clear all sessions for MAC address 00:01:02:03:04:05, type the following command:
MX# clear sessions network mac-addr 00:01:02:03:04:05
To clear session 9, type the following command:
MX-20# clear sessions network session-id 9
SM Apr 11 19:53:38 DEBUG SM-STATE: localid 9, mac 00:06:25:09:39:5d,
flags 0000012fh, to change state to KILLING
Localid 9, globalid SESSION-9-893249336 moved from ACTIVE to KILLING
(client=00:06:25:09:39:5d)
To clear the session of user Natasha, type the following command:
MX-20# clear sessions network user Natasha
To clear the sessions of users whose name begins with the characters Jo, type the following
command:
MX-20# clear sessions network user Jo*
To clear the sessions of all users on VLAN red, type the following command:
MX-20# clear sessions network vlan red
See Also
show sessions on page 529
show sessions network on page 532
show sessions
Usage Displays session information and statistics for all users with administrative access to the
MX, or for administrative users with either console or Telnet access.
529
Displays sessions for all users with administrative access to the MX through a
Telnet or SSH connection or a console plugged into the switch.
console
Displays sessions for all users with administrative access to the MX through a
console plugged into the switch.
telnet
Displays sessions for all users with administrative access to the MX through a
Telnet connection.
telnet clien Displays Telnet sessions from the CLI to remote devices.
t
Defaults None.
Access All, except for show sessions telnet client, which has enabled access.
History
Version 1.0
Command introduced.
Version 1.1
Version 2.0
Version 6.2
Examples To display information about all sessions, use the following command:
MX> show sessions
User
Sess
Type
IP or MAC
VLAN
Name
ID
--------------
---------
--------
--------------
------
engineering-05:
0c:78
28*
dot1x
10.7.255.2
yellow
5/1
engineering-79:
86:73
29*
dot1x
10.7.254.3
red
2/1
engineering-1a:
68:78
30*
dot1x
10.7.254.8
red
7/1
Address
AP/
Radio
To view information about sessions of administrative users, type the following command:
MX> show sessions admin
Tty
Username
Time (s)
Type
-------
--------------------
--------
----
3644
Console
tty0
tty2
tech
Telnet
tty3
sshadmin
381
SSH
3 admin sessions
530
To view information about console users sessions, type the following command:
MX> show sessions console
Tty
Username
Time (s)
-------
--------------------
--------
console
8573
1 console session
To view information about Telnet users sessions, type the following command:
MX> show sessions telnet
Tty
Username
Time (s)
-------
--------------------
--------
tty2
sea
7395
To view information about Telnet client sessions, type the following command:
MX# show sessions telnet client
Session
Server Address
Server Port
Client Port
-------
--------------
------------
-----------
192.168.1.81
23
48000
10.10.1.22
23
48001
Table 82 describes the fields of the show sessions admin, show sessions console, and show
sessions telnet displays.
Table 83 describes the fields of the show sessions telnet client display.
Table 82.show sessions admin, show sessions console, and show sessions telnet
Output
Field
Description
Tty
The Telnet terminal number, or console for administrative users connected through the console port.
Username
Time (s)
Type
Description
Session
Server Address
Server Port
Client Port
TCP port number MSS is using for the client side of the session.
531
verbose
Defaults None.
Access All.
History Introduced in MSS Version 6.0.
Examples To view information about Mesh AP sessions, type the following command:
MX> show sessions mesh-ap
User
Sess
Name
Radio
ID
---------------------------- ---00:0b:0e:17:bb:3f
AP 2/2
IP or MAC
VLAN
Address
Name
AP/
----------------- ---------------
2* 1.1.1.3
(none)
Description
User Name
Sess ID
Locally unique number that identifies this session. An asterisk (*) next to a session ID
indicates that the session is fully active.
IP or MAC Address
VLAN Name
Port/Radio
Number of the port and radio through which the Mesh AP is accessing this session.
532
user user-glob
mac-addr
mac-addr-glob
qos-profile
profilename
ssid ssid-name
statistics
vlan vlan-glob
session-id
local-session-id
Displays the specified network session. To find local session IDs, use the
show sessions command. The verbose option is not available with this
form of the show sessions network command.
wired
verbose
Defaults None.
Access All.
History
Version 1.0
Command introduced.
Version 4.1
533
Version 4.2
New values for the source of user attribute values (attributes include
Vlan-Name, Start-Date, and so on.) See Table 86 on page 538.
Usage MSS displays information about network sessions in three types of displays. See the
following tables for field descriptions.
Summary display
Verbose display
Authorization attribute values can be changed during authorization. If the values are changed,
show sessions output shows the values that are actually in effect following any changes.
Examples To display summary information for all network sessions, type show sessions
network. For example:
MX> show sessions network
User Name SessID Type Address VLAN AP/Radio
--------------------- ------ ----- ----------------- ---------------------TRAPEZE\jjonesg 20* dot1x 172.21.50.151 eng-alpha 20/2
TRAPEZE\jdoe 75* dot1x 172.21.50.97 eng-alpha 2/2
TRAPEZE\lsmith 752* dot1x 172.21.50.89 eng-alpha 20/2
TRAPEZE\lforte 409* dot1x 172.21.52.149 cs-alpha 27/2
TRAPEZE\lcheval 24* dot1x 172.21.50.66 eng-alpha 27/2
TRAPEZE\mjaune 477* dot1x 172.21.52.102 cs-alpha 2/2
TRAPEZE\schat 365* dot1x 172.21.50.135 eng-alpha 27/2
534
Sess
Type
13* web
Address
VLAN
-------------10.10.10.40
vlan-eng
The following command displays summary information about all the sessions of users whose
names begin with E:
MX> show sessions network user E*
User Name
AP/Radio/
Sess
Type
13*
web
Address
VLAN
-------------10.10.10.39
vlan-eng
(Table 85 on page 537 describes the summary displays of show sessions network commands.)
The following command displays verbose output about the sessions of all current network users:
MX> show sessions network verbose
User Name
Sess Type
Address
VLAN
AP/Radio
---------------------------- ------------------ --------SHUTTLE2\exmpl
7/1
-------- -----------------
3* web
10.8.255.8
default
(prev AUTHORIZED)
535
Vlan-Name=default (service-profile)
Service-Type=2 (service-profile)
End-Date=52/06/07-08:57 (AAA)
Start-Date=05/04/11-10:00 (AAA)
1 sessions total
(Table 86 on page 538 describes the additional fields of the verbose output of show sessions
network commands.)
The following command displays information about network session 88:
MX# show sessions network session-id 88
Name: Trapeze\jdoeh
Session Id:
88
Global Id:
SESS-88-00040f-876766-623fd6
Rack-39-PM
IP Address:
10.2.39.217
10/1
State:
ACTIVE
Session Tag: 2
Host name: jdoeh-d410
Vlan Name:
default
Up time: 02:54:29
Roaming history:
Switch
AP/Radio
---------
---------
---------------
--------
192.168.254.82
3/2
09/21/07 11:16:47
02:54:03
Session Start:
Last Activity:
( <15s ago)
Session Timeout: 0
Idle Time-To-Live: 175
EAP Method:
Protocol: 802.11
CoS: flow-through
Session CAC: disabled
Radio type: 802.11na
Last packet rate: 300Mb/s (m15 40 MHz)
536
Bytes
-------
-----
Rx Unicast
1814
2522
Rx Multicast
68
7846
Rx Encrypt Err
Tx Unicast
2004
4444900
Rx peak A-MSDU
2048
Rx peak A-MPDU
13
16345
Tx peak A-MSDU
2048
Tx peak A-MPDU
13
16345
Queue
Tx Packets
Tx Dropped
Re-Transmit
Rx Dropped
-------
-----------
-----------
-----------
-----------
Background
Best Effort
30
Queue
Tx Packets
Tx Dropped
Re-Transmit
Rx Dropped
-------
-----------
-----------
-----------
-----------
Video
Voice
11n Capabilities:
Max Rx A-MSDU size: 2K
Max Rx A-MPDU size: 16K
Max Channel Width: 40MHz
For descriptions of the fields of show sessions network session-id output, see Table 87 on
page 539.
Table 85.show sessions network (summary) Output
Field
Description
User Name
Note: For a MAC-authenticated session, this value is the client devices MAC address.
Sess ID
Locally unique number that identifies this session. An asterisk (*) next to a session ID
indicates that the session is fully active.
IP or MAC Address
IP address of the session user, or the users MAC address if the user has not yet received an
IP address.
VLAN Name
Port/Radio
Number of the port and radio through which the user is accessing this session.
537
Description
Client MAC
GID
State
now on
Shows the following information about the MP and radio the session is currently on:
IP address and port number of the MX managing the MP
Serial number and radio number of the MP
Amount of time the session has been on this MP
from
Shows information about the MPs from which the session has roamed. (See the descriptions
above for the now on field.)
Host name
538
Description
Vlan-Name
Authorization attributes for the user and how they were assigned (the sources of the attribute
(and other
values).
attributes if set)
For Vlan-Name, the source of the attribute value can be one of the following:
AAAVLAN is from RADIUS or the local database.
initial-assignmentFor a client that has roamed from one MX to another, VLAN is the one
assigned to the user on the MX where the user first accessed the network. (This is the MX
where the clients global session in the Mobility Domain started.)
This authorization source (initial-assignment) is displayed only if the following conditions are true:
The client roamed from another MX.
The service profile for the SSID the user is on is configured to keep the clients initial VLAN
assignment. (This means the keep-initial-vlan option is enabled on the service profile.)
The VLAN is not configured for the user on the roamed-to switch by the local database.
A Location Policy on the roamed-to MX does not set the VLAN.
location policyAttribute value was assigned by a Location Policy.
service-profileAttribute value is configured on the SSID, and was not overridden by other
attribute sources (such as AAA or location policy).
Web PortalSession is for a Web Portal client.
Description
Local Id
Identifier for the session on this particular MX. (This is the session ID you specify when
entering the show sessions network session-id command.)
Global Id
State
State,
cont.
SSID
AP/Radio
Number of the port and radio that the user is accessing for this session.
539
Description
MAC address
User Name
IP Address
Vlan Name
Tag
Session Start
Last Activity
Session Timeout
Idle Time-To-Live
Number of seconds the session can remain idle before MSS changes the session state to
Login Type
Disassociated.
DOT1X
MAC
LAST-RESORT
WEB-PORTAL
EAP Method
Extensible Authentication Protocol (EAP) type used to authenticate the session user, and
the IP address of the authentication server.
Session statistics as
Time the session statistics were last updated from the MP access point, in seconds since a
updated from AP
Unicast packets in
Total number of unicast packets received from the user by the MX (64-bit counter).
Unicast bytes in
Total number of unicast bytes received from the user by the MX (64-bit counter).
Total number of unicast packets sent by the MX to the user (64-bit counter).
Total number of unicast bytes sent by the MX to the user (64-bit counter).
Multicast packets in
Total number of multicast packets received from the user by the MX (64-bit counter).
Multicast bytes in
Total number of multicast bytes received from the user by the MX (64-bit counter).
encryption errors
Number of bytes with
encryption errors
Last packet data rate
Data transmit rate, in megabits per second (Mbps), of the last packet received by the MP
access point.
Signal strength, in decibels referred to 1 milliwatt (dBm), of the last packet received by the
MP access point.
Protocol
Session CAC
State of session-based Call Admission Control (CAC) on the SSIDs service profile.
540
SessID
--------------------- -----jdoe
12/1
Type
Address
VLAN
eng-alpha
TRAPEZE\jdoe
Session ID:
49568
SSID:
alpha-aes
IP:
172.21.50.103
MAC:
00:19:7d:37:f7:96
AP/Radio:
4/2
Protocol:
802.11
Session CAC:
disabled
Radio type:
802.11a
36 Mb/s
-80 dBm
15
Voice Queue:
IDLE
Name:
TRAPEZE\jsmith
Session ID:
49558
541
SSID:
alpha-aes
IP:
172.21.50.51
MAC:
00:13:e8:95:51:8d
AP/Radio:
12/2
Protocol:
802.11
Session CAC:
disabled
Radio type:
802.11a
54 Mb/s
-67 dBm
28
Voice Queue:
IDLE
Name: jjones
Session ID:
49549
SSID:
alpha-tkip
IP:
172.21.50.114
MAC:
00:1e:e5:a7:24:66
AP/Radio:
4/2
Protocol:
802.11
Session CAC:
disabled
Radio type:
802.11a
48 Mb/s
-65 dBm
30
Voice Queue:
IDLE
542
Field
Description
Name:
Session ID:
SSID:
IP:
MAC:
AP/Radio:
Protocol:
Session CAC:
Radio type:
Description
Voice Queue:
543
544
RF Detection Commands
MSS automatically performs RF detection scans on enabled and disabled radios to detect rogue
access points. A rogue access point is a BSSID (MAC address associated with an SSID) that does not
belong to a Juniper device and is not a member of the ignore list configured on the seed MX of the
Mobility Domain.
MSS can issue countermeasures against rogue devices to prevent clients from being able to use
them.
You can configure RF detection parameters on individual MX switches.
This chapter presents RF detection commands alphabetically. Use the following table to locate the
commands in this chapter based on usage.
New
New
Spectrum Analysis
Rogue Information
Countermeasures
Classification
New
Ignore List
MP Signatures
545
Log Messages
MX-to-Client RF Link
all
Defaults None.
Access Enabled.
History
MSS Version 4.0
Command introduced.
Examples The following command clears MAC address 11:22:33:44:55:66 from the rogue list:
MX# clear rfdetect attack-list 11:22:33:44:55:66
success: 11:22:33:44:55:66 is no longer in roguelist.
See Also
set rfdetect rogue-list on page 551
show rfdetect rogue-list on page 557
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command removes MAC address 11:22:33:44:55:66 from the blacklist:
MX# clear rfdetect black-list 11:22:33:44:55:66
success: 11:22:33:44:55:66 is no longer blacklisted.
See Also
set rfdetect black-list on page 551
show rfdetect black-list on page 557
546
RF Detection Commands
Basic service set identifier (BSSID), which is a MAC address, of the device to remove from the
neighbor list.
oui
A third-party device ID
all
Defaults None.
Access Enabled.
History
MSS Version 3.0
Command introduced.
Examples The following command removes BSSID aa:bb:cc:11:22:33 from the neighbor list for
RF scans:
MX-20# clear rfdetect neighbor-list aa:bb:cc:11:22:33
success: aa:bb:cc:11:22:33 is no longer on the neighbor-list.
See Also
set rfdetect ignore on page 554
show rfdetect neighbor-list on page 565
SSID name you want to remove from the permitted SSID list.
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command clears SSID mycorp from the permitted SSID list:
MX# clear rfdetect ssid-list mycorp
success: mycorp is no longer in ssid-list.
Copyright 2011, Juniper Networks, Inc.
547
See Also
set rfdetect ssid-list on page 555
show rfdetect ssid-list on page 569
rfping
Provides information about the RF link between the MX and the client based on sending test packets
to the client.
Syntax rfping {mac mac-addr | session-id session-id}
mac-addr
Tests the RF link between the MX and the client with the specified MAC address.
session-id
Tests the RF link between the MX and the client with the specified local session ID.
Defaults None.
Access Enabled.
History
Version 4.2
Command introduced.
Version 6.0
Usage Use this command to send test packets to a specified client. The output of the command
indicates the number of test packets received and acknowledged by the client, as well as the client
signal strength and signal-to-noise ratio.
Examples The following command tests the RF link between the MX and the client with MAC
address 00:0e:9b:bf:ad:13:
MX# rfping mac 00:0e:9b:bf:ad:13
RF-Link Test to 00:0e:9b:bf:ad:13 :
Session-Id: 2
Packets Sent Packets Rcvd RSSI SNR RTT (micro-secs)
------------ ------------ ------- ----- ---------------20
20
-68 26
976
Table 94 describes the fields in this display.
Table 89.rfping Output
Field
Description
Packets Sent
Packets Rcvd
RSSI
Received signal strength indication (RSSI)the strength of the RF signal from the client, in decibels referred
SNR
Signal-to-noise ratio (SNR), in decibels (dB), of the data received from the client.
to 1 milliwatt (dBm).
548
RF Detection Commands
Description
RTT (micro-secs)
The round-trip time, in microseconds, for the client response to the test packets.
See Also
show rfdetect data on page 563
show rfdetect visible on page 569
enable
disable
data-first
spectral-first
549
Type
AP
Ch
RSSI
Duty
CIM
Age
---------
----
----
----- ----
----
---
---
fe:00:1f:20:82:80
Unknown
71
-92
100
292
fe:21:6f:46:bd:11
Microwave
43
-85
41
67
fe:21:6f:46:bd:11
Microwave
71
10
-64
50
68
142
fe:21:6f:46:bd:11
Microwave
71
11
-58
44
82
112
fe:32:1f:ed:82:80
Phone
75
-71
22
fe:32:1f:ed:82:80
Phone
75
-71
82
fe:32:6f:46:00:01
Phone
43
-78
67
In the output table, Age refers to the time, in seconds, since the noise was detected on the
network.
MX# show rfdetect data noise verbose
Source ID: fe:21:6f:46:bd:16
Type: Microwave oven
AP Number: 71
AP Name: AP71
Channels: 10 11
RSSI: -64 -58
Duty Cycle: 50 44
Severity(CIM): 68 84
Age: 72 12
To show a summary of the noise interference detected, use the following command:
MX# show rfdetect data noise summary
Channel Interference Measure
550
AP
Name
AP
Chan
ovens
----
------
----
----
----
-----
----
----
----
43
60
AP43
10
24
43
43
AP43
48
51
74
81
AP74
52
21
75
60
AP75
10
15
blue
phone
video
other
WLAN
CQM
-
RF Detection Commands
mac-addr
Command introduced.
Usage The rogue list applies only to the MX with the configured list. MX switches do not share
rogue lists.
When on-demand countermeasures are enabled (with the set radio-profile countermeasures
configured command) only those devices configured in the rogue list are subject to
countermeasures. In this case, devices found to be rogues by other means, such as policy
violations or by determining that the device is providing connectivity to the wired network, are not
attacked.
Examples The following command adds MAC address aa:bb:cc:44:55:66 to the attack list:
MX# set rfdetect rogue-list 11:22:33:44:55:66
success:
See Also
clear rfdetect rogue-list on page 546
show rfdetect rogue-list on page 557
set radio-profile countermeasures on page 311
551
Access Enabled.
History Introduced in MSS Version 4.0.
Usage In addition to manually configured entries, the list can contain entries added by MSS. MSS
can place a client in the blacklist due to an association, reassociation or disassociation flood from
the client.
The client black list applies only to the MX with the configured list. MX switches do not share client
blacklists.
MSS supports up to 1024 clients in the black list.
Examples The following command adds client MAC address 11:22:33:44:55:66 to the black list:
MX# set rfdetect black-list 11:22:33:44:55:66
success:
See Also
set rfdetect black-list on page 551
show rfdetect black-list on page 557
duration seconds
Length of time that an entry should stay on the black list in seconds.
The range is 1 to 2147483647 seconds.
Defaults None
Access Enabled
History Introduced in MSS Version 7.1.
Examples To allow an entry to stay on the black-list for 60 seconds, you must first enable the
feature and then configure the duration:
MX# set rdetect black-list dynamic enable
success: change accepted.
MX# set rfdetect black-list dynamic duration 60
success: change accepted.
552
RF Detection Commands
rogue
skip-test
Defaults None
Access Enabled
History Introduced in MSS 6.2
Examples To configure MSS to detect ad-hoc networks and classify them as rogue devices, use
the following command:
MX>set rfdetect classification ad-hoc rogue
suspect
neighbor
Defaults None
Access Enabled
History Introduced in MSS 6.2
Examples To configure MSS to detect unknown devices and classify them as rogue devices, use
the following command:
MX>set rfdetect classification default rogue
skip-test
Defaults None
Access Enabled
History Introduced in MSS 6.2
Examples To configure MSS to detect devices seen on the network and classify them as rogue
devices, use the following command:
MX>set rfdetect classification seen-in-network rogue
Copyright 2011, Juniper Networks, Inc.
553
skip-test
Defaults None
Access Enabled
History Introduced in MSS 6.2
Examples To configure MSS to detect unknown devices and classify them as rogue devices, use
the following command:
MX>set rfdetect classification ssid-masquerade rogue
disable
554
RF Detection Commands
Enables MP signatures.
disable
Disables MP signatures.
encrypted
555
ssid*
Defaults The permitted SSID list is empty by default and all SSIDs are allowed. However, after
you add an entry to the list, MSS allows traffic only for the listed SSIDs.
Access Enabled.
History
MSS Version 4.0
Command introduced.
Usage The permitted SSID list applies only to the MX with the configured list. MX switches do not
share permitted SSID lists.
If you add a device that MSS has classified as a rogue to the permitted SSID list, but not to the
ignore list, MSS can still classify the device as a rogue. Adding an entry to the permitted SSID list
merely indicates that the device is using an allowed SSID. However, if you want MSS to stop
classifying the device as a rogue, you must add the device MAC address to the ignore list.
Examples The following command adds SSID mycorp to the list of permitted SSIDs:
MX# set rfdetect ssid-list mycorp
success:
See Also
clear rfdetect ssid-list on page 547
show rfdetect ssid-list on page 569
556
User Role
Calssfication
If in Rogue list
Rogue
RF Detection Commands
Calssfication
Member
Neighbor
If SSID Masquerade
Rogue
Rogue
If Ad hoc device
Rogue
Neighbor
Default Classification
Suspect
Command introduced.
Port/Radio/Chan
RSSI
SSID
ap 2/1/11
-53
rogue-ssid
See Also
clear rfdetect rogue-list on page 546
set rfdetect rogue-list on page 551
557
Type
Port
TTL
25
See Also
clear rfdetect black-list on page 546
set rfdetect black-list on page 551
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command shows information about all wireless clients detected by an MX
and MPs:
MX# show rfdetect clients
Total number of entries: 30
Client MAC
Type Last
Client
Vendor
AP MAC
AP
Vendor
Port/Radio
NoL
/Channel
seen
----------------- ------- ----------------- ------- ------------- ------- ----
558
00:03:7f:bf:16:70 Unknown
intfr 207
Unknown
ap 1/1/6
00:04:23:77:e6:e5
intfr 155
Intel
Unknown
ap 1/1/2
00:05:5d:79:ce:0f
intfr 87
D-Link
Unknown
ap 1/1/149
00:05:5d:7e:96:a7
intfr 117
D-Link
Unknown
ap 1/1/149
RF Detection Commands
00:05:5d:7e:96:ce
intfr 162
D-Link
Unknown
ap 1/1/157
00:05:5d:84:d1:c5
intfr 52
D-Link
Unknown
ap 1/1/1
Description
Client MAC
Client Vendor
AP MAC
MAC address of the radio with which the rogue client is associated.
AP Vendor
Company that manufactures or sells the AP with which the rogue client is associated.
Port/Radio/Channel
Port number, radio number, and channel number of the radio that detected the rogue.
NoL
Number of listeners. This is the number of MP radios that detected the rogue client.
Type
Number of seconds since an MP radio last detected 802.11 packets from the device.
Description
RSSI
Rate
Last Seen
Number of seconds since an MP radio last detected 802.11 packets from the device.
559
Description
BSSID
MAC address of the SSID with which the rogue client is associated.
Vendor
Company that manufactures or sells the AP with which the rogue client is associated.
Typ
Dst
MAC addressed to which the last 802.11 packet detected from the client was
addressed.
Number of seconds since the MX looked on the air for the AP that the rogue client is
associated. The MX looks for the client AP by sending a packet from the wired side of
the network addressed to the client, and watching the air for a wireless packet
containing the clients MAC address.
Command introduced.
Version 4.0
Usage This command is valid only on the seed MX of the Mobility Domain.
Examples The following example displays countermeasures status for the Mobility Domain:
MX# show rfdetect countermeasures
Total number of entries: 190
Rogue MAC
Type
Countermeasures
MX-IPaddr
Radio Mac
Port/Radio
/Channel
00:0b:0e:44:55:66 10.1.1.23
ap 4/1/6
00:0b:0e:03:00:80 rogue
00:0b:0e:11:22:33 10.1.1.23
ap 2/1/11
560
Field
Description
Rogue MAC
RF Detection Commands
Description
Type
MAC address of the Juniper radio sending countermeasures against the rogue.
MX-IPaddr
Port/Radio/Channel
Port number, radio number, and channel number of the countermeasures radio.
Current
Total
-------------------------------------------------- -----------------------
139
4
0
20
561
562
626
Broadcast deauthentications
0
RF Detection Commands
Netstumbler clients
0
Wellenreiter clients
0
Active scans
4383
1796
196
Command introduced.
Version 2.0
New option, verbose, added to include Juniper devices and devices in the
ignore list.
563
Version 3.0
Version 4.0
Version 7.0
Version 7.1
Examples The following command shows the devices detected by the MX during the most recent
RF detection scan:
MX# show rfdetect data
Total number of entries: 197
BSSID
Vendor
Class
AP Name
RSSI
Ch
Age
-----
00:07:50:d5:cc:91
r27-cisco1200-2
Cisco intfr
i----w
-61
00:07:50:d5:dc:78
r116-cisco1200-2
Cisco intfr
i----w
-82
00:09:b7:7b:8a:54
Cisco intfr
i-----
-96
00:0a:5e:4b:4a:c0
3Com intfr
i-----
-76
00:0a:5e:4b:4a:c2
-86 tapezewlan
3Com intfr
i-t1--
00:0a:5e:4b:4a:c4
3Com intfr
6
-85 trpz-ccmp
ic----
00:0a:5e:4b:4a:c6
3Com intfr
6
-85 trpz-tkip
i-t---
00:0a:5e:4b:4a:c8
3Com intfr
6
-83 trpz-voip
i----w
00:0a:5e:4b:4a:ca
3Com intfr
6
-85 trpz-webaaa
i-----
SSID
public
564
Field
Description
BSSID
Vendor
RF Detection Commands
Description
Class
AP Name
Channel
RSSI
Received signal strength indication (RSSI)the strength of the RF signal detected by the
MP radio, in decibels referred to 1 milliwatt (dBm).
Age
Number of seconds since an MP radio last detected 802.11 packets from the device.
SSID
+/-
If the device is using 40 MHz wide channels, the primary channel is listed in the Ch column.
If the secondary channel is above the primary, a - appears next to the channel number. If
the secondary channel is below the primary, a + appears next to the channel number.
See Also
show rfdetect mobility-domain on page 566
show rfdetect visible on page 569
Command introduced.
MSS 6.2
565
See Also
clear rfdetect neighbor-list on page 547
set rfdetect ignore on page 554
bssid mac-addr
Defaults None.
Access Enabled.
History
Version 3.0
Command introduced.
Version 4.0
Usage This command is valid only on the seed MX of the Mobility Domain. To display rogue
information for an individual MX, use the show rfdetect data command on that MX.
Examples The following command displays summary information for all SSIDs and BSSIDs
detected in the Mobility Domain:
MX# show rfdetect mobility-domain
Total number of entries: 194
Flags: i = infrastructure, a = ad-hoc, u = unresolved
c = CCMP, t = TKIP, 1 = 104-bit WEP, 4 = 40-bit WEP, w =
WEP(non-WPA)
BSSID
Vendor
Type
Flags
SSID
566
00:07:50:d5:cc:91
00:07:50:d5:dc:78
00:09:b7:7b:8a:54
00:0a:5e:4b:4a:c0
00:0a:5e:4b:4a:c2
00:0a:5e:4b:4a:c4
00:0a:5e:4b:4a:c6
00:0a:5e:4b:4a:c8
RF Detection Commands
00:0a:5e:4b:4a:ca
The lines in this display are compiled from data from multiple listeners (MP radios). If an item has
the value unresolved, not all listeners agree on the value for that item. Generally, an unresolved
state occurs only when an MP or a Mobility Domain is still coming up, and lasts only briefly.
The following command displays detailed information for rogues using SSID trpz-webaaa.
MX# show rfdetect mobility-domain ssid trpz-webaaa
BSSID: 00:0a:5e:4b:4a:ca Vendor: 3Com SSID: trpz-webaaa
Type: intfr Adhoc: no Crypto-types: clear
567
Description
BSSID
Vendor
Type
Flags
SSID
Description
BSSID
Vendor
SSID
Type
Adhoc
Indicates whether the rogue is an infrastructure rogue (is using an AP) or is operating in
ad-hoc mode.
Crypto-Types
Encryption type:
clear (no encryption)
ccmp
tkip
wep104 (WPA 104-bit WEP)
wep40 (WPA 40-bit WEP)
wep (non-WPA WEP)
568
MX-IPaddress
Port/Radio/Channel
Port number, radio number, and channel number of the radio that detected the rogue.
Mac
RF Detection Commands
Description
Device-type
Adhoc
Crypto-Types
RSSI
SSID
See Also
show rfdetect data on page 563
show rfdetect visible on page 569
569
To display rogue information for the entire Mobility Domain, use the show rfdetect
mobility-domain command on the seed switch.
Examples
Syntax show rfdetect visible mac-addr
Syntax show rfdetect visible ap apnum [radio {1 | 2}]
mac-addr
apnum
radio 1
radio 2
Shows neighbor information for radio 2. (This option does not apply to
single-radio models.)
Defaults None.
Access Enabled.
History
Version 3.0
Command introduced.
Version 4.0
Examples To following command displays information about the rogues detected by radio 1 on MP
port 3:
MX# show rfdetect visible ap 3 radio 1
Total number of entries: 104
Flags: i = infrastructure, a = ad-hoc
c = CCMP, t = TKIP, 1 = 104-bit WEP, 4 = 40-bit WEP, w =
WEP(non-WPA)
Transmit MAC
Vendor
Type
Ch
RSSI Flags
SSID
570
00:07:50:d5:cc:91
Cisco intfr
00:07:50:d5:dc:78
Cisco intfr
00:09:b7:7b:8a:54
Cisco intfr
-54 i-----
00:0a:5e:4b:4a:c0
3Com intfr
11
00:0a:5e:4b:4a:c2
3Com intfr
11
00:0a:5e:4b:4a:c4
3Com intfr
11
00:0a:5e:4b:4a:c6
3Com intfr
11
00:0a:5e:4b:4a:c8
3Com intfr
11
RF Detection Commands
00:0a:5e:4b:4a:ca
3Com intfr
11
Transmit MAC
MAC address the rogue device that sent the 802.11 packet detected by the MP
radio.
Transmit MAC
MAC address the rogue device that sent the 802.11 packet detected by the MP
radio.
Type
Ch
RSSI
Flags
SSID
See Also
show rfdetect data on page 563
show rfdetect mobility-domain on page 566
571
572
LLDP Commands
Link Layer Discovery Protocol (LLDP) is a Layer 2 protocol that allows a network device to advertise its
identity and capabilities on the local network. It is ratified as an IEEE standard. LLDP supports a set of
attributes used to discover neighbor devices. These attributes contain type, length, and value descriptions
and are referred to as TLVs. LLDP supported devices use TLVs to receive and send information to
neighboring devices. Details such as configuration information, device capabilities, and device identity can
be advertised using this protocol.
MSS and WLCs support these basic management TLVs. These are mandatory TLVs:
Port Description
System Name
System Description
System Capabilities
Management Address
Use the following table to locate commands in this chapter based on their use.
set ap apnum auto lldp mode on page 574
set ap apnum lldp mode on page 574
set lldp hold time on page 575
set lldp mode on page 575
LLDP Configuration
Commands on page 574
LLDP-MED Commands
on page 578
LLDP Display
Commands on page 579
573
disable
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples To se the AP configuration to transmit mode, use the following command:
WLC# set ap apnum lldp mode tx
See Also
set lldp mode on page 575
set lldp tx interval on page 576
set lldp hold time on page 575
set lldp reinit delay on page 575
set lldp transmit-delay on page 577
set lldp tlv select on page 576
574
LLDP Commands
disable
Specify the transmit interval value in seconds. The range is 0 to 65535 seconds
disable
Defaults The default value is enabled. If it is set to disabled, it is disabled on MXs and APs. All
TLVs are discarded.
Defaults Disable
Access Enabled
History Introduced in MSS Version 7.5
Examples The following command enables the LLDP protocol:
WLC# set lldp mode enable
575
Defaults 2 seconds
Access Enabled
History Introduced in MSS Version 7.5
Examples The following example sets the delay time to 5 seconds:
WLC# set lldp reinit-delay 5
Defaults 30 seconds
Access Enabled
History Introduced in MSS Version 7.5
Examples The following example sets the advertisement interval to 500 seconds:
WLC# set lldp tx-interval 500
system-description
system-name
enable
disable
576
LLDP Commands
Specify the transmit delay time in seconds. The range is 1 to 8192 seconds
Defaults 2 seconds
Access Enabled
History Introduced in MSS Version 7.5
Examples The following example sets the delay time to 5 seconds:
WLC# set lldp transmit-delay 5
rx
txrx
disable
577
LLDP-MED Commands
LLDP-MED is an extension to LLDP that operates between endpoint devices such as IP phones and
network devices such as switches. Specifically, it provides support for voice over IP (VoIP) applications and
provides additional TLVs for capabilities discover, network policy, Power over Ethernet (PoE), and
inventory management.
LLDP-MED supports the following TLVs:
LLDP-MED capabilities TLV Allows LLDP-MED endpoints to determine the capabilities of a
connected device and if those capabilities are enabled.
Network Policy TLV Allows both network connectivity devices and endpoints to advertise VLAN
configurations and associated Layer 2 and Layer 3 attributes for the specific appliance on that port.
For example, an MX can notify a VoIP phone to use a specific VLAN.
Power management TLV Enables advanced power management between LLDP-MED endpoint and
network connectivity devices. Allows MXs and VoIP phones to convey power information, such as the
type of power, power priority, and the amount of power required by the device.
Inventory management TLVs Allows an endpoint to transmit detailed inventory information to an MX,
including hardware revision, firmware version, software version, serial number, manufacturer name,
model name, and asset ID.
LLDP and LLDP-MED cannot operate simultaneously on a network. By default, network devices send only
LLDP packets until LLDP-MED packets are received from an endpoint device. The network device then
sends out LLDP-MED packets until it receives LLDP packets.
The following commands configure LLDP-MED on the MX
LLDP Display Commands on page 579
set port number lldp mode on page 577
set port portnum lldp med-tlv-select on page 579
auto
enable
disable
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples Use the following command to enable LLDP-MED with the the auto configuration
options:
578
LLDP-MED Commands
LLDP Commands
disable
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples Use the following command to enable LLDP-MED on the MX:
WLC# set port portnum lldp med enable
See Also set port portnum lldp med-tlv-select on page 579
inventory
enable
disable
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples Use the following command to enable LLDP-MED with the Inventory TLV:
WLC# set port portnum lldp med-tlv-select power-via-mdi mode enable
See Also set ap llpd med on page 578
579
580
LLDP Commands
show lldp
Usage Displays global information about LLDP such as protocol running status, transmit
frequency, hold-time, and reinit-delay.
Syntax show lldp
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples Following is sample output for this command:
WLC# show lldp
LLDP
: Enabled
: 2 seconds
Reinit Delay
: 2 seconds
Hold Time
: 120 seconds
LLDP
----
----
txrx
disable
tx
txrx
rx
txrx
txrx
txrx
LLDP AP Configuration
AP
LLDP
MED-MODE
MED-TLVs
--
----
--------
--------
tx
enable
power-via-mdi
inventory
581
disable enable
disable disable
Display robust details about LLDP neighbors. If not specified, only limited
TLV information is displayed.
port
portnum
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples Following is sample output for this command without the verbose attribute specified:
WLC# show lldp neighbors
LLDP Remote Devices Information
Port
ChassisID
PortID
SystemName
TTL
----
---------
------
----------
---
00:1e:f7:20:4f87
Fa0/5
SQA_Office
100
192.168.111.21
00:0b:0e:d0:93:c0
1
2
AP4
120
00:b0:c2:02:ae:0d eth1
trpz.com
120
192.168.111.22
AVA4C357E
120
00:0b:0e:d0:93:e0
Following is sample output for this command with the port, portnum, and verbose attributes
specified:
WLC# show lldp neighbors port portnum verbose
Received from Local Port 1, TTL 100 Seconds, 81 seconds remaining
ChassisID Type:
MAC Address
ChassisID:
00:1e:f7:20:4f:87
PortID Type:
Interface Name
PortID:
Fa0/5
System Name:
SQA_OFFICE
(TBD)
FastEthernet0/5
LLDP Commands
IPv4
Address: 192.168.107.1
Interface Subtype: iflndex
Interface Number:
107
0001
Enabled
583
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
Examples To display verbose information about LLDP AP neighbors, use the following command:
show ap lldp apnum neighbors verbose
See Also clear lldp neighbors on page 585
584
LLDP Commands
portnum
Defaults None
Access Enabled
History Introduced in MSS Version 7.5
See Also show lldp neighbors on page 582
585
586
Software Version
Boot Settings
File Management
Configuration File
backup
Usage Creates an archive of MX system files and optionally, user file, in Unix tape archive (tar)
format.
587
Name of the archive file to create. You can store the file locally in
the switchs nonvolatile storage or on a TFTP server.
all
Backs up system files and all the files in the user files area.
The user files area contains the set of files listed in the file
section of dir command output.
critical
copy
Usage Performs the following copy operations:
Copies a file from a FTP or TFTP server to nonvolatile storage.
589
Copies a file from nonvolatile storage or temporary storage to a FTP or TFTP server.
Copies a file securely using SCP (Secure Copy Protocol).
Copies a file from one area in nonvolatile storage to another.
Copies a file to a new filename in nonvolatile storage.
Syntax copy source-url destination-url
source-url
Name and location of the file to copy. The uniform resource locator (URL) can be
one of the following:
[subdirname/]filename
file:[subdirname/]filename
ftp://ip-addr/[subdirname/]filename
scp://ip-addr/[subdirname/]filename
tftp://ip-addr/[subdirname/]filename
tmp:filename
For the filename, specify between 1 and 128 alphanumeric characters, with no
spaces. Enter the IP address in dotted decimal notation.
The subdirname/ option specifies a subdirectory.
destination-url
Name of the copy and the location to place the copy. The URL can be one of the
following:
[subdirname/]filename
file:[subdirname/]filename
ftp://ip-addr/[subdirname/]filename
scp://ip-addr/[subdirname/]filename
tftp://ip-addr/[subdirname/]filename
If you are copying a system image file into nonvolatile storage, the filename must
include the boot partition name. You can specify one of the following:
boot0:/filename
boot1:/filename
Defaults None.
Access Enabled.
History
590
Version 1.0
Command introduced
Version 1.1
Version 3.0
Version 7.1
Usage The filename and file:filename URLs are equivalent. You can use either URL to refer to a
file in an MX nonvolatile memory. The tftp://ip-addr/filename URL refers to a file on a TFTP server.
If DNS is configured on the MX, you can specify a TFTP server hostname as an alternative to
specifying the IP address.
The tmp:filename URL specifies a file in temporary storage. You can copy a file out of temporary
storage but you cannot copy a file into temporary storage. Temporary storage is reserved for use
by MSS.
If you are copying a system image file into nonvolatile storage, the filename must be preceded by
the boot partition name, which can be boot0 or boot1. Enter the filename as boot0:/filename or
boot1:/filename. You must specify the boot partition that was not used to load the currently
running image.
The maximum supported file size for TFTP is 32 MB.
Examples The following command copies a file called floormx from nonvolatile storage to a TFTP
server:
MX# copy floormx tftp://10.1.1.1/floormx
success: sent 365 bytes in 0.401 seconds [ 910 bytes/sec]
The following command copies a file called closetmx from a TFTP server to nonvolatile storage:
MX# copy tftp://10.1.1.1/closetmx closetmx
success: received 637 bytes in 0.253 seconds [ 2517 bytes/sec]
The following command copies system image MX020101.020 from a TFTP server to boot partition
1 in nonvolatile storage:
MX# copy tftp://10.1.1.107/MX020101.020 boot1:MX020101.020
........................................................................
....................................success: received 9163214 bytes in
105.939 seconds [ 86495 bytes/sec]
The following commands rename test-config to new-config by copying it from one name to the
other in the same location, then deleting test-config:
MX# copy test-config new-config
MX# delete test-config
success: file deleted.
The following command copies file corpa-login.html from a TFTP server into subdirectory corpa in
an MX switchs nonvolatile storage:
MX# copy .1.1.1/corpa-login.html corpa/corpa-login.html
success: received 637 bytes itftp://10n 0.253 seconds [ 2517 bytes/sec]
See Also
delete on page 592
dir on page 592
591
delete
Usage Deletes a file.
Warning: MSS does not prompt you to verify if you want to delete a file. When you press Enter after typing a
delete command, MSS immediately deletes the specified file.
Informational Note: MSS does not allow you to delete the currently running software image file or the
running configuration.
url
Command introduced
Version 3.0
Usage You might want to copy the file to a TFTP server as a backup before deleting the file.
Examples The following commands copy file testconfig to a TFTP server and delete the file from
nonvolatile storage:
MX# copy testconfig tftp://10.1.1.1/testconfig
success: sent 365 bytes in 0.401 seconds [ 910 bytes/sec]
MX# delete testconfig
success: file deleted.
Examples The following command deletes file dang_doc from subdirectory dang:
MX# delete dang/dang_doc
success: file deleted.
See Also
copy on page 589
dir on page 592
dir
Usage Displays a list of the files in nonvolatile storage and temporary files.
592
file:
core:
boot0:
boot1:
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 1.1
Enhanced to list the image files in the boot partitions and indicate the partition
that was used to load the currently running image
Version 3.0
Version 4.1
core:, file:, boot0:, and boot1: options added, to limit the output to the
specified category
Examples The following command displays the files in the root directory:
MX# dir
========================================================================
=======
file:
Filename
Size
file:configuration
15:02:32
48 KB
Jul 12 2005,
file:corp2:corp2cnfig
22:20:04
17 KB
Mar 14 2005,
corp_a/
19:15:48
file:dangcfg
22:20:04
old/
17:23:44
512 bytes
14 KB
512 bytes
Created
May 21 2004,
Mar 14 2005,
May 16 2004,
file:pubsconfig-april062005
21:08:30
40 KB
May 09 2005,
file:sysa_bak
19:18:44
12 KB
Mar 15 2005,
593
file:testback
16:37:18
Total:
28 KB
Apr 19 2005,
========================================================================
=======
Boot:
Filename
Size
Created
boot0:mx040100.020
15:54:08
9780 KB
Aug 23 2005,
*boot1:mx040100.020
21:09:56
9796 KB
Aug 28 2005,
Boot0: Total:
Boot1: Total:
========================================================================
=======
temporary files:
Filename
Size
core:command_audit.cur
21:11:41
37 bytes
Total:
Created
Aug 28 2005,
Size
Created
file:configuration.txt
22:55:44
3541 bytes
Sep 22 2003,
file:configuration.xml
22:55:44
24 KB
Sep 22 2003,
Total:
The following command limits the output to the contents of the user files area:
MX# dir file:
========================================================================
=======
file:
594
Filename
Size
file:configuration
15:02:32
48 KB
Created
Jul 12 2005,
file:corp2:corp2cnfig
22:20:04
corp_a/
19:15:48
17 KB
512 bytes
file:dangcfg
22:20:04
14 KB
dangdir/
17:23:44
512 bytes
Mar 14 2005,
May 21 2004,
Mar 14 2005,
May 16 2004,
file:pubsconfig-april062005
21:08:30
40 KB
May 09 2005,
file:sysa_bak
19:18:44
12 KB
Mar 15 2005,
file:testback
16:37:18
28 KB
Apr 19 2005,
Total:
The following command limits the output to the contents of the /tmp/core subdirectory:
MX# dir core:
========================================================================
=======
file:
Filename
Size
core:command_audit.cur
21:11:41
37 bytes
Total:
Created
Aug 28 2005,
The following command limits the output to the contents of the boot0 partition:
MX# dir boot0:
========================================================================
=======
file:
Filename
Size
boot0:mx040100.020
15:54:08
Total:
9780 KB
Created
Aug 23 2005,
595
Description
Filename
Size
Created
System time and date when the file was created or copied onto the MX.
Total
Number of kilobytes in use to store files and the number that are still free.
See Also
copy on page 589
delete on page 592
load config
Caution: This command completely removes the running configuration and replaces it with the
configuration contained in the file. Juniper Networks recommends that you save a copy of the
current running configuration to a backup configuration file before loading a new configuration.
Loads configuration commands from a file and replaces the MX running configuration with the
commands in the loaded file.
Syntax load config [url]
url
If you do not specify a filename, MSS uses the same configuration filename that was used for the
previous configuration load. For example, if the MX used configuration for the most recent
configuration load, MSS uses configuration again unless you specify a different filename. To
display the filename of the configuration file MSS loaded during the last reboot, use the show
boot command.
596
Access Enabled.
History
Version 1.0
Command introduced
Version 3.0
Usage This command completely replaces the running configuration with the configuration in the
file.
Examples The following command reloads the configuration from the most recently loaded
configuration file:
MX# load config
Reloading configuration may result in lost of connectivity, do you wish
to continue? (y/n) [n]y
success: Configuration reloaded
The following command loads configuration file testconfig1:
MX# load config testconfig1
Reloading configuration may result in lost of connectivity, do you wish
to continue? (y/n) [n]y
success: Configuration reloaded
See Also
save config on page 601
show boot on page 604
show config on page 605
md5
Usage Calculates the MD5 checksum for a file in the MX nonvolatile storage.
Syntax md5 [boot0: | boot1:]filename
boot0: | boot1:
filename
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Usage You must include the boot partition name in front of the filename. If you specify only the
filename, the CLI displays a message stating that the file does not exist.
Examples The following command calculates the checksum for image file MX040003.020 in boot
partition 0:
pubs# md5 boot0:MX040003.020
MD5 (boot0:MX040003.020) = b9cf7f527f74608e50c70e8fb896392a
597
See Also
copy on page 589
dir on page 592
mkdir
Usage Creates a new subdirectory in nonvolatile storage.
Syntax mkdir [subdirname]
subdirname
Defaults None.
Access Enabled.
History Introduced in MSS Version 3.0.
Examples The following commands create a subdirectory called corp2 and display the root
directory to verify the result:
MX# mkdir corp2
success: change accepted.
MX# dir
========================================================================
=======
file:
Filename
Size
file:configuration
18:20:53
17 KB
file:configuration.txt
18:55:17
Created
May 21 2004,
379 bytes
May 09 2004,
corp2/
19:22:09
512 bytes
May 21 2004,
corp_a/
19:15:48
512 bytes
May 21 2004,
file:dangcfg
18:30:44
13 KB
May 16 2004,
dangdir/
17:23:44
512 bytes
May 16 2004,
old/
21:58:48
512 bytes
Sep 23 2003,
Total:
========================================================================
=======
Boot:
598
Filename
Size
*boot0:bload
19:02:16
Created
746 KB
May 09 2004,
*boot0:mx030000.020
18:58:16
8182 KB
May 09 2004,
boot1:mx030000.020
18:01:02
8197 KB
May 21 2004,
Boot0: Total:
Boot1: Total:
========================================================================
=======
temporary files:
Filename
Total:
Size
Created
See Also
dir on page 592
rmdir on page 601
reset system
Usage Restarts an MX and reboots the software.
Syntax reset system [force]
force
Immediately restarts the system and reboots, without comparing the running
configuration to the configuration file.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Usage If you do not use the force option, the command first compares the running configuration
to the configuration file. If the running configuration and configuration file do not match, MSS does
not restart the MX but instead displays a message advising you to either save the configuration
changes or use the force option.
Examples The following command restarts an MX that does not have any unsaved configuration
changes:
MX# reset system
This will reset the entire system. Are you sure (y/n)y
The following commands attempt to restart an MX switch with a running configuration with
unsaved changes, and then force the MX to restart:
MX# reset system
error: Cannot reset, due to unsaved configuration changes. Use "reset
system force" to override.
Copyright 2011, Juniper Networks, Inc.
599
restore
Usage Unzips a system archive created by the backup command and copies the files from the
archive onto the switch.
Syntax restore system [tftp:/ip-addr/]filename [all | critical] [force]
[tftp:/ip-addr/]filename
Name of the archive file to load. The archive can be located in the
MX nonvolatile storage or on a TFTP server.
all
Restores system files and the user files from the archive.
critical
force
Replaces files on the MX with those in the archive, even if the MX is not the same
as the one from which the archive was created.
CAUTION! Do not use this option unless advised to do so by Juniper Networks
TAC. If you restore MX system files from one MX onto another MX, you must
generate new key pairs and certificates on the MX.
The backup command stores the MAC address of the switch in the archive. By default, the
restore command works only if the MAC address in the archive matches the MAC address of the
switch where the restore command is entered. The force option overrides this restriction and
allows you to unpack an archive from one MX onto another MX.
Informational Note: Do not use the force option unless you are certain you want to replace the MX
files with files from another MX. If you restore one MX system files onto another MX, you must generate
new key pairs and certificates on the MX.
600
If the configuration running on the MX is different from the one in the archive or you renamed the
configuration file, and you want to retain changes made after the archive was created, see the
Managing System Files chapter of the Juniper Mobility System Software Configuration Guide.
Examples The following command restores system-critical files on a MX from archive sysa_bak:
MX# restore system tftp:/10.10.20.9/sysa_bak
success: received 11908 bytes in 0.150 seconds [ 79386 bytes/sec]
success: restore complete.
See Also backup on page 587
rmdir
Usage Removes a subdirectory from nonvolatile storage.
Syntax rmdir [subdirname]
Subdirectory name. Specify between 1 and 32 alphanumeric characters,
with no spaces.
subdirname
Defaults None.
Access Enabled.
History Introduced in MSS Version 3.0.
Usage MSS does not allow the subdirectory to be removed unless it is empty. Delete all files from
the subdirectory before attempting to remove it.
Examples The following example removes subdirectory corp2:
MX# rmdir corp2
success: change accepted.
See Also
dir on page 592
mkdir on page 598
save config
Usage Saves the running configuration to a configuration file.
Syntax save config [filename]
filename
Defaults By default, MSS saves the running configuration as the configuration filename used
during the last reboot.
Access Enabled.
Copyright 2011, Juniper Networks, Inc.
601
History
Version 1.0
Command introduced
Version 3.0
Usage If you do not specify a filename, MSS replaces the configuration file loaded during the most
recent reboot. To display the filename of the configuration file MSS loaded during the most recent
reboot, use the show boot command.
The command completely replaces the specified configuration file with the running configuration.
Examples The following command saves the running configuration to the configuration file loaded
during the most recent reboot. In this example, the filename used during the most recent reboot is
configuration.
MX# save config
Configuration saved to configuration.
The following command saves the running configuration to a file named testconfig1:
MX# save config testconfig1
Configuration saved to testconfig1.
See Also
load config on page 596
show boot on page 604
show config on page 605
Name of the file to use as a backup configuration file if MSS cannot read the MX configuration file.
602
Command introduced
Version 3.0
Boot partition 0.
boot1
Boot partition 1.
Defaults By default, an MX uses the same boot partition for the next software reload that was
used to boot the currently running image.
Access Enabled.
History Introduced in MSS Version 1.1.
Usage To determine the boot partition used to load the currently running software image, use the
dir command.
Examples The following command sets the boot partition for the next software reload to partition 1:
MX# set boot partition boot1
success: Boot partition set to boot1.
See Also
copy on page 589
603
show boot
Usage Displays the system image and configuration filenames used after the last reboot and
configured for use after the next reboot.
Syntax show boot
Defaults None.
Access Access.
History
Version 1.0
Command introduced
Version 1.1
The following fields were removed because they are not applicable in 1.1:
Last boot status
Unpacking status
Version 2.1
Version 4.1
New fields, Configured boot version and Backup boot configuration, added
Examples The following command shows the boot information for an MX:
MX# show boot
Configured boot version:
4.1.0.65
boot1:mx040100.020
file:configuration
file:backup.cfg
Booted version:
4.1.0.65
Booted image:
boot1:mx040100.020
Booted configuration:
file:configuration
Product model:
MX
Description
Boot partition and image filename MSS uses to boot when the software is rebooted.
The name of the configuration file to be used in the event that MSS cannot read the
configured boot configuration file next time the software is rebooted.
Booted version
604
Description
Booted image
Boot partition and image filename MSS used the last time the software was rebooted.
MSS is running this software image.
Booted configuration
Configuration filename MSS used to load the configuration the last time the software
was rebooted.
See Also
clear boot config on page 589
reset system on page 599
set boot configuration-file on page 603
show version on page 607
show config
Usage Displays the configuration running on the MX.
Syntax show config [all | cluster | local] [area area]
area area
605
snmp
snoop
spantree
system
trace
vlan
vlan-fdb
vlan-profile
If you do not specify a configuration area, nondefault information for all
areas is displayed.
cluster
local
all
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 2.1
New comment added to the comments at top of the file, to list the model number
Version 3.0
Version 4.0
Version 4.1
Version 4.2
Version 7.0
Added the options cluster and local to support Virtual Controller Cluster
configuration.
Usage If you do not use one of the optional parameters, configuration commands that set
nondefault values are displayed for all configuration areas. If you specify an area, commands are
displayed for that area only. If you use the all option, the display also includes commands for
configuration items that are set to the default values.
Examples The following command shows configuration information for VLANs:
MX# show config area vlan
606
show version
Usage Displays software and hardware version information for an MX and, optionally, for any
attached MPs.
Syntax show version [details]
Includes additional software build information and information about the MP
configured on the MX.
details
Defaults None
Access All.
History
Version 1.0
Command introduced
Version 2.1
MX
Hardware
Mainboard:
PoE board:
Serial number
0321300013
Flash:
4.1.0.14
Kernel:
BootLoader:
4.10 / 4.1.0
- md0a
The following command displays additional software build information and MP information:
607
4.1.0.67_072105_MX20
Build Suffix:
-d-O1
Model:
MX
Hardware
Mainboard:
CPU Model:
PoE board:
Serial number
0321300013
Flash:
4.1.0.14
Kernel:
BootLoader:
4.10 / 4.1.0
Port/ AP AP Model
- md0a
Serial #
Versions
/-
MP-352
0424902948
H/W
: A
F/W1 : 5.6
F/W2 : 5.6
S/W
: 4.1.0.67_072105_0432__AP
608
Description
Build Information
Label
Build Suffix
Build suffix.
Model
Build model.
Hardware
Version information for the MX motherboard and Power over Ethernet (PoE) board.
Serial number
Flash
Kernel
Kernel version.
BootLoader
Port/AP
AP Model
MP model number.
Serial #
MP serial number.
Versions
609
610
Trace Commands
Use trace commands to perform diagnostic routines. While MSS allows you to run many types of traces,
this chapter describes commands for those traces you are most likely to use. For a complete listing of the
types of traces MSS allows, type the set trace ? command.
Warning: Using the set trace command can have adverse effects on system performance. Juniper Networks
recommends that you use the lowest levels possible for initial trace commands, and slowly increase the levels
to get the data you need.
This chapter presents trace commands alphabetically. Use the following table to locate commands in this
chapter based on their use.
Trace
clear trace
Usage Deletes running trace commands and ends trace processes.
611
Ends a particular trace process. Specify one of the following keywords to end the
traces documented in this chapter:
authorizationEnds an authorization trace
dot1xEnds an 802.1X trace
authenticationEnds an authentication trace
smEnds a session manager trace
all
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To clear all trace processes, type the following command:
MX# clear trace all
success: clear trace all
To clear the session manager trace, type the following command:
MX# clear trace sm
success: clear trace sm
See Also
set trace authentication on page 613
set trace authorization on page 613
set trace dot1x on page 614
set trace sm on page 615
show trace on page 616
save trace
Usage Saves the accumulated trace data for enabled traces to a file in the MX nonvolatile
storage.
Syntax save trace filename
filename
Name for the trace file. To save the file in a subdirectory, specify the subdirectory
name, then a slash. For example: traces/trace1
Defaults None.
Access Enabled.
History Introduced in MSS Version 3.0.
Examples To save trace data into the file trace1 in the subdirectory traces, type the following
command:
MX# save trace traces/trace1
612
Trace Commands
mac-addr mac-address
port port-num
user username
level level
Command introduced.
mac-addr mac-address
port port-num
613
user username
level level
Command introduced.
Examples The following command starts a trace for information for authorization for MAC address
00:01:02:03:04:05:
MX# set trace authorization mac-addr 00:01:02:03:04:05
success: change accepted.
See Also
clear trace on page 611
show trace on page 616
mac-addr mac-address
port port-num
user username
level level
Trace Commands
History
MSS Version 1.0
Command introduced.
Examples The following command starts a trace for the 802.1X sessions for MAC address
00:01:02:03:04:05:
MX# set trace dot1x mac-addr 00:01:02:03:04:05:
success: change accepted.
See Also
clear trace on page 611
show trace on page 616
set trace sm
Usage Traces session manager activity.
Syntax set trace sm [ip-addr ip address][mac-addr mac-address] [port port-num]
[user username] [level level]
ip-addr ip address
mac-addr mac-address
port port-num
user username
level level
Command introduced.
615
Examples Type the following command to trace session manager activity for MAC address
00:01:02:03:04:05:
MX# set trace sm mac-addr 00:01:02:03:04:05:
success: change accepted.
See Also
clear trace on page 611
show trace on page 616
show trace
Usage Displays information about traces that are currently configured on the MX, or all possible
trace options.
Syntax show trace [all]
all
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To view the traces currently running, type the following command:
MX# show trace
milliseconds spent printing traces: 1885.614
Trace Area
Filter
Level Mac
User
Port
sm
0
See Also
clear trace on page 611
set trace authentication on page 613
set trace authorization on page 613
set trace dot1x on page 614
set trace sm on page 615
616
Snoop Commands
Use snoop commands to monitor wireless traffic, by using an MP as a sniffing device. The MP copies the
sniffed 802.11 packets and sends the copies to an observer, typically a protocol analyzer such as Ethereal
or Tethereal.
(For more information, including setup instructions for the monitoring station, see the Remotely Monitoring
Traffic section in the Troubleshooting an MX Switch chapter of the Trapeze Mobility System Software
Configuration Guide.)
This chapter presents snoop commands alphabetically. Use the following table to locate commands in this
chapter based on their use.
clear snoop on page 617
clear snoop map on page 618
Remote monitoring
(snooping)
new
clear snoop
Usage Deletes a snoop filter.
Syntax clear snoop filter-name
filter-name
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command deletes snoop filter snoop1:
MX# clear snoop snoop1
See Also
set snoop on page 618
show snoop info on page 624
Copyright 2011, Juniper Networks, Inc.
617
ap apnum
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command removes snoop filter snoop2 from radio 2 on Distributed MP 3:
MX# clear snoop map snoop2 ap 3 radio 2
success: change accepted.
The following command removes all snoop filter mappings from all radios:
MX# clear snoop map all
success: change accepted.
See Also
set snoop map on page 621
show snoop on page 623
show snoop map on page 624
set snoop
Usage Configures a snoop filter.
618
Snoop Commands
Name for the filter. The name can be up to 15 alphanumeric characters, with
no spaces.
condition-list
Match criteria for packets. Conditions in the list are ANDed. Therefore, to be
copied and sent to an observer, a packet must match all criteria in the
condition-list. You can specify up to eight of the following conditions in a filter,
in any order or combination:
frame-type {eq | neq} {beacon | control | data | management | probe}
channel {eq | neq} channel
bssid {eq | neq} bssid
src-mac {eq | neq | lt | gt} mac-addr
dest-mac {eq | neq | lt | gt} mac-addr
host-mac {eq | neq | lt | gt} mac-addr
mac-pair mac-addr1 mac-addr2
direction {eq | neq} {transmit | receive}
To match on packets to or from a specific MAC address, use the dest-mac or
src-mac option. To match on both send and receive traffic for a host
address, use the host-mac option. To match on a traffic flow (source and
destination MAC addresses), use the mac-pair option. This option matches
for either direction of a flow, and either MAC address can be the source or
destination address.
If you omit a condition, all packets match that condition. For example, if you
omit frame-type, all frame types match the filter.
For most conditions, you can use eq (equal) to match only on traffic that
matches the condition value. Use neq (not equal) to match only on traffic that
is not equal to the condition value.
The src-mac, dest-mac, and host-mac conditions also support lt (less than)
and gt (greater than).
observer ip-addr Specifies the IP address of the station where the protocol analyzer is located.
If you do not specify an observer, the MP radio still counts the packets that
match the filter.
619
snap-length
num
tx-mode
Command introduced
Version 5.0
New Boolean operators: lt (less than) and gt (greater than). The new
options apply to src-mac, dest-mac, and host-mac.
Version 6.0
Version 7.5
tx-mode added.
Usage Traffic that matches a snoop filter is copied after it is decrypted. The decrypted (clear)
version is sent to the observer.
For best results:
Do not specify an observer that is associated with the MP configured with the snoop filter. This
configuration causes an endless cycle of snoop traffic.
If the snoop filter is running on a Distributed MP, and the MP used a DHCP server in its local
subnet to configure the IP information, and the MP did not receive a default router (gateway)
address as a result, the observer must also be in the same subnet. Without a default router, the
MP cannot find the observer.
The MP with a snoop filter forwards snooped packets directly to the observer. This is a one-way
communication, from the MP to the observer. If the observer is not present, the MP still sends
the snoop packets, which uses bandwidth. If the observer is present but is not listening to TZSP
traffic, the observer continuously sends ICMP error indications back to the MP. These ICMP
messages can affect network and MP performance.
Examples The following command configures a snoop filter named snoop1 that matches on all
traffic, and copies the traffic to the device that has IP address 10.10.30.2:
MX# set snoop snoop1 observer 10.10.30.2 snap-length 100
The following command configures a snoop filter named snoop2 that matches on all data traffic
between the device with MAC address aa:bb:cc:dd:ee:ff and the device with MAC address
11:22:33:44:55:66, and copies the traffic to the device that has IP address 10.10.30.3:
MX# set snoop snoop2 frame-type eq data mac-pair aa:bb:cc:dd:ee:ff
11:22:33:44:55:66 observer 10.10.30.3 snap-length 100
620
Snoop Commands
The following command captured 802.11 packets to small sizes to make wired header information
more significant by compacting multiple frame headers into a single UDP packet which reduces
the overhead of UDP/IP headers and the packet forwarding load within the network.
set snoop filter filter-name {condition-list} {observer ip-addr}
where
{observer ip-addr}
is the snoop observer configured using the next command:
set snoop observer ip-addr { snap-length length}|{interval interval}|
{transmission-mode tx-mode}
clear snoop on page 617
set snoop map on page 621
set snoop mode on page 622
show snoop info on page 624
show snoop stats on page 625
ap ap-num
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
621
Name of the snoop filter. Specify all to enable all snoop filters.
enable
disable
Command introduced
Version 6.0
622
Snoop Commands
transmitter-type
member-ap
Defaults None.
Access Enabled.
History Introduced in MSS Version 7.5
Examples To configure a snoop filter that allows you to filter all packets transmitted by MPs that
are members of a mobility domain, use the following command:
MX# set snoop-filter name transmitter-type [eq | neq] member-ap
show snoop
Usage Displays the MP radio mapping for all snoop filters. To display the mappings for a specific
MP radio, use the show snoop map command.
Syntax show snoop
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Examples The following command shows the MP radio mappings for all snoop filters configured
on an MX switch:
MX# show snoop
AP: 3
Radio: 2
snoop1
snoop2
AP: 2
Radio: 2
snoop2
623
filter-name
Defaults None.
Access Enabled.
filter-name
Defaults None.
Access Enabled.
Radio: 2
See Also
clear snoop map on page 618
set snoop map on page 621
624
Snoop Commands
ap ap-num
radio 1
radio 2
Radio 2 of the MP. (This option does not apply to single-radio models.)
Defaults None.
Access Enabled.
History Introduced in MSS Version 4.0.
Usage The MP retains statistics for a snoop filter until the filter is changed or disabled. The MP
then clears the statistics.
Examples The following command shows statistics for snoop filter snoop1:
MX# show snoop stats snoop1
Filter
AP Radio
Rx Match
Tx Match
Dropped
===================================================================
snoop1
96
Description
Filter
AP
Radio
Rx Match
Tx Match
Dropped
Number of packets that matched the filter but that were not copied to the observer
due to memory or network problems.
625
626
clear log
Usage Clears the log messages stored in the log buffer, or removes the configuration for a syslog
server and stops sending log messages to that server.
Syntax clear log [buffer | server ip-addr
buffer
server ip-addr
Deletes the configuration for and stops sending log messages to the syslog
server at this IP address. Specify an address in dotted decimal notation.
Defaults None.
Access Enabled.
History Introduced in MSS Version 1.0.
Examples To stop sending system logging messages to a server at 192.168.253.11, type the
following command:
MX# clear log server 192.168.253.11
success: change accepted.
Type the following command to clear all messages from the log buffer:
MX# clear log buffer
success: change accepted.
See Also
clear log trace on page 611
set log on page 628
627
set log
Usage Enables or disables logging of MX and MP events to the MX log buffer or other logging
destination and sets the level of the events logged. For logging to a syslog server only, you can
also set the facility logged.
Syntax set log {buffer | console | current | sessions | trace} [severity
severity-level] [enable | disable]
console
current
Sets log parameters for the current Telnet or console session. These
settings are not stored in nonvolatile memory.
server ip-addr
sessions
Sets the default log values for Telnet sessions. You can set defaults for the
following log parameters:
Severity
Logging state (enabled or disabled)
To override the session defaults for an individual session, type the set log
command from within the session and use the current option.
trace
port port-number
Sets the TCP port for sending messages to the syslog server. You can
specify a number from 1 to 65535. The default syslog port is 514.
severity
severity-level
Logs events at a severity level greater than or equal to the level specified.
Specify one of the following:
emergencyThe MX is unusable.
alertAction must be taken immediately.
criticalYou must resolve the critical conditions. If the conditions are
not resolved, the MX can reboot or shut down.
errorThe MX is missing data or is unable to form a connection.
warningA possible problem exists.
noticeEvents that potentially can cause system problems have
occurred. These are logged for diagnostic purposes. No action is
required.
infoInformational messages only. No problem exists.
debugOutput from debugging.
628
local-facility For messages sent to a syslog server, maps all messages of the severity
facility-level
you specify to one of the standard local log facilities defined in RFC 3164.
You can specify one of the following values:
0maps all messages to local0.
1maps all messages to local1.
2maps all messages to local2.
3maps all messages to local3.
4maps all messages to local4.
5maps all messages to local5.
6maps all messages to local6.
7maps all messages to local7.
If you do not specify a local facility, MSS sends the messages with their
default MSS facilities. For example, AAA messages are sent with facility 4
and boot messages are sent with facility 20 by default.
enable
disable
Defaults
Events at the error level and higher are logged to the MX console.
Events at the error level and higher are logged to the MX system buffer.
Trace logging is enabled, and debug-level output is stored in the MX trace buffer.
Access Enabled.
History
Version 1.0
Command introduced
Version 4.2
Usage Using the command with only enable or disable turns logging on or off for the target at all
levels. For example, entering set log buffer enable with no other keywords turns on logging to the
system buffer of all facilities at all levels. Entering set log buffer disable with no other keywords
turns off all logging to the buffer.
Examples To log only emergency, alert, and critical system events to the console, type the
following command:
MX# set log console severity critical enable
success: change accepted.
See Also
show log config on page 632
clear log on page 627
629
disable
severity level
interval interval
Interval at which MSS generates the mark messages. You can specify
from 1 to 2147483647 seconds.
Defaults Mark messages are disabled by default. When messages are enabled, MSS generates
a message at the notice level once every 300 seconds by default.
Access Enabled.
History Introduced in MSS Version 4.1.
Examples The following command enables mark messages:
MX# set log mark enable
success: change accepted.
See Also show log config on page 632
630
+|-number-of-messages
facility facility-name
Area of MSS that is sending the log message. Type a space and a
question mark (?) after show log buffer facility for a list of valid
facilities.
matching string
severity severity-level
Defaults None.
Access Enabled.
History
Version 1.0
Command introduced
Version 5.0
Option COPP removed. The option is not applicable to MSS Version 5.0.
Usage The debug level produces a lot of messages, and many can appear to be cryptic. Debug
messages are used primarily by Juniper Networks for troubleshooting and are not intended for
administrator use.
Examples Type the following command to see the facilities that you can view event messages
archived in the buffer:
MX# show log buffer facility ?
631
<facility name>
Select one of: KERNEL, AAA, SYSLOGD, ACL,
APM, ARP, ASO, BOOT, CLI, CLUSTER, CRYPTO, DOT1X, NET, ETHERNET,
GATEWAY, HTTPD, IGMP, IP, MISC, NOSE, NP, RAND, RESOLV, RIB, ROAM,
ROGUE, SM, SNMPD, SPAN, STORE, SYS, TAGMGR, TBRIDGE, TCPSSL, TELNET,
TFTP, TLS, TUNNEL, VLAN, X509, XML, MP, RAPDA, WEBVIEW, EAP, FP, STAT,
SSHD, SUP, DNSD, CONFIG, BACKUP.
The following command displays logged messages for the AAA facility:
MX# show log buffer facility AAA
AAA Jun. 25 09:11:32.579848 ERROR AAA_NOTIFY_ERR: AAA got SM special
event (98) on locality 3950 which is gone
See Also
clear log on page 627
show log config on page 632
632
Logging console:
disabled
DEBUG
Logging sessions:
disabled
INFO
Logging buffer:
enabled
WARNING
Logging trace:
enabled
DEBUG
10485760 bytes
Log marking:
disabled
NOTICE
300 seconds
Logging server:
Current session:
disabled
INFO
See Also
set log on page 628
clear log on page 627
Area of MSS that is sending the log message. Type a space and a
question mark (?) after show log trace facility for a list of valid facilities.
matching string
severity
severity-level
Defaults None.
Access Enabled.
633
History
Version 1.0
Command introduced
Version 5.0
Option COPP removed. The option is not applicable to MSS Version 5.0.
Examples Type the following command to see the facilities for which you can view event
messages archived in the buffer:
MX# show log trace facility ?
<facility name>
Select one of: KERNEL, AAA, SYSLOGD, ACL,
APM, ARP, ASO, BOOT, CLI, CLUSTER, CRYPTO, DOT1X, ENCAP, ETHERNET,
GATEWAY, HTTPD, IGMP, IP, MISC, NOSE, NP, RAND, RESOLV, RIB, ROAM,
ROGUE, SM, SNMPD, SPAN, STORE, SYS, TAGMGR, TBRIDGE, TCPSSL, TELNET,
TFTP, TLS, TUNNEL, VLAN, X509, XML, MP, RAPDA, WEBVIEW, EAP, PORTCONFIG,
FP.
The following command displays the newest five trace log entries for the ROGUE facility:
MX# show log trace +5 facility ROGUE
ROGUE Oct 28 16:30:19.695141 ERROR ROGUE_AP_ALERT: Xmtr Mac
01:0b:0e:ff:00:3b Po
rt 7 Radio 1 Chan 36 RSSI 18 Tech DOT_11A SSID trapeze
ROGUE Oct 28
16:30:19.7046
37 ERROR ROGUE_AP_ALERT: Xmtr Mac 01:0b:0e:00:09:5f Port 7 Radio 1 Chan
36 RSSI
15 Tech DOT_11A SSID examplewlan
ROGUE Oct 28 16:30:19.711253 ERROR
ROGUE_AP_ALER
T: Xmtr Mac 01:0b:0e:00:06:b7 Port 7 Radio 1 Chan 36 RSSI 36 Tech
DOT_11A SSID wlan-7
ROGUE Oct 28 16:30:19.717954 ERROR ROGUE_AP_ALERT: Xmtr Mac
00:0b:0e:00:0
6:8f Port 7 Radio 1 Chan 36 RSSI 13 Tech DOT_11A SSID trapeze
ROGUE Oct
28 16:30:
19.727069 ERROR ROGUE_AP_ALERT: Xmtr Mac 01:0b:0e:da:da:dd Port 7 Radio
1 Chan 3
6 RSSI 22 Tech DOT_11A SSID trapeze
See Also
clear log on page 627
show log config on page 632
634
This chapter presents boot prompt commands alphabetically. Use the following table to locate commands
in this chapter based on their use.
Command Information
ls on page 643
help on page 643
Booting
File Management
Boot Profile
Management
Diagnostics
autoboot
Usage Displays or changes the state of the autoboot option. The autoboot option controls whether
an MX automatically boots a system image after initializing the hardware, following a system reset
or power cycle.
635
on
OFF
off
boot
Usage Loads and executes a system image file.
Syntax boot [BT=type] [DEV=device] [FN=filename] [HA=ip-addr] [FL=num]
[OPT=option] [OPT+=option]
BT=type
Boot type:
cCompact flash. Boots using nonvolatile storage or a flash card.
nNetwork. Boots using a TFTP server.
DEV=device
636
FN=filename
HA=ip-addr
Host address (IP address) of a TFTP server. This parameter applies only
when the boot type is n (network).
FL=num
Number representing the bit settings of boot flags to pass to the booted
system image. Use this parameter only if advised to do so by Juniper
Networks.
OPT=option
String up to 128 bytes of boot options to pass to the booted system image
instead of the boot option(s) in the currently active boot profile. The options
temporarily replace the options in the boot profile. Use this parameter only if
advised to do so by Juniper Networks.
OPT+=option
String up to 128 bytes of boot options to pass to the booted system image in
addition to the boot option(s) in the currently active boot profile. The options
are appended to the options already in the boot profile. Use this parameter
only if advised to do so by Juniper Networks.
Defaults The boot settings in the currently active boot profile are used by default.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Usage If you use an optional parameter, the parameter setting overrides the setting of the same
parameter in the currently active boot profile. However, the boot profile itself is not changed. To
display the currently active boot profile, use the show command. To change the currently active
boot profile, use the change command.
Examples The following command loads system image file WLC010101.020 from boot partition 1:
boot> boot FN=WLC010101.020 DEV=boot1
Compact Flash load from boot1:testcfg matches WLC010101.020.
unzip: Inflating ramdisk_1.1.1.. OK
unzip file len 36085486 OK
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
The NetBSD Foundation, Inc.
637
change
Usage Changes parameters in the currently active boot profile. (For information about boot
profiles, see show on page 646.)
Syntax change
Defaults The default boot type is c (compact flash). The default filename is default. The default
flags setting is 0x00000000 (all flags disabled) and the default options list is run=nos;boot=0. The
default device setting is the boot partition specified by the most recent set boot partition
command typed at the Enabled level of the CLI, or boot 0 if the command has never been typed.
After you type the change command, the system interactively displays the current setting of each
parameter and prompts you for the new setting. When prompted, type the new setting, press Enter
to accept the current setting, or type . (period) to change the setting to the default value. To back
up to the previous parameter, type - (hyphen).
For information about each of the boot parameters you can set, see show on page 646.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples The following command enters the configuration mode for the currently active boot
profile, changes the device to boot1, and leaves the other parameters with their current settings:
boot> change
Changing the default configuration is not recommended.
Are you sure that you want to proceed? (y/n)y
BOOT TYPE:
[c]
DEVICE:
[boot0:]boot1
FILENAME:
[default]
FLAGS:
[0x00000000]
OPTIONS:
[run=nos;boot=0]
The following command enters the configuration mode for the currently active boot profile and
configures the WLC (in this example, an WLCR-2) to boot using a TFTP server:
boot> change
Changing the default configuration is not recommended.
Are you sure that you want to proceed? (y/n)y
638
BOOT TYPE:
[c]> n
DEVICE:
[boot0:]> emac1
FILENAME:
[default]> bootfile
HOST IP:
[0.0.0.0]> 172.16.0.1
LOCAL IP:
[0.0.0.0]> 172.16.0.21
GATEWAY IP:
[0.0.0.0]> 172.16.0.20
IP MASK:
[0.0.0.0]> 255.255.255.0
FLAGS:
[0x00000000]>
OPTIONS:
[run=nos;boot=0]>
See Also
boot on page 636
create on page 639
delete on page 640
dhcp on page 640
next on page 644
show on page 646
create
Usage Creates a new boot profile. (For information about boot profiles, see show on page 646.)
An MX can have up to four boot profiles. The boot profiles are stored in slots, numbered
0 through 3. When you create a new profile, the system uses the next available slot for the profile.
If all four slots already contain profiles and you try to create a fifth profile, the WLC displays a
message advising you to change one of the existing profiles instead.
To make a new boot profile the currently active boot profile, use the next command. To change
boot parameter settings, use the change command.
Syntax create
Defaults The new boot profile has the same settings as the currently active boot profile by default.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples The following command creates a new boot profile in slot 1 on an MX that currently has
only one boot profile, in slot 0:
boot> create
BOOT Index:
BOOT TYPE:
DEVICE:
boot1:
FILENAME:
default
FLAGS:
00000000
OPTIONS:
run=nos;boot=0
639
See Also
change on page 638
delete on page 640
next on page 644
show on page 646
delete
Usage Removes the currently active boot profile. (For information about boot profiles, see show
on page 646.)
When you type the delete command, the next-lower numbered boot profile becomes the active
profile. For example, if the currently active profile is number 3, profile number 2 becomes active
after you type delete to delete profile 3. You cannot delete boot profile 0.
Examples
Syntax delete
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples To remove the currently active boot profile, type the following command:
boot> delete
BOOT Index:
BOOT TYPE:
DEVICE:
boot1:
FILENAME:
default
FLAGS:
00000000
OPTIONS:
run=nos;boot=0
See Also
change on page 638
create on page 639
next on page 644
show on page 646
dhcp
Usage Displays or changes the state of the DHCP option. The DHCP option controls whether an
MX uses DCHP to obtain its IP address when it is booted using a TFTP server.
640
on
OFF
off
diag
Usage Accesses the diagnostic mode.
Syntax diag
Defaults The diagnostic mode is disabled by default.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Usage Access to the diagnostic mode requires a password, which is not user configurable. Use
this mode only if advised to do so by Juniper Networks.
dir
Usage Displays the boot code and system image files on an MX switch.
Syntax dir [c: | d: | e: | f: | boot0 | boot1]
c:
d:
e:
f:
boot0
Boot partition 0.
boot1
Boot partition 1.
Defaults None.
641
5523634 bytes
BLOAD
696176 bytes
BSTRAP
38056 bytes
5524593 bytes
See Also
fver on page 642
version on page 648
fver
Usage Displays the version of a system image file installed in a specific location on an MX.
Syntax fver {c: | d: | e: | f: | boot0: | boot1:} [filename]
e:
f:
boot0
Boot partition 0.
boot1
Boot partition 1.
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Usage To display the image filenames, use the dir command. This command does not list the
boot code versions. To display the boot code versions, use the version command.
Examples The following command displays the system image version installed in boot partition 1:
boot> fver boot1
File boot1:default version is 1.1.0.98.
See Also
dir on page 641
version on page 648
642
help
Usage Displays a list of all the boot prompt commands or detailed information for an individual
command.
If you specify a command name, detailed information is displayed for that command. If you do not
specify a command name, all the boot prompt commands are listed.
Examples
Syntax help [command-name]
Boot prompt command.
command-name
Defaults None.
USAGE: fver
[c:file|d:file|e:file|f:file|boot0:file|boot1:file|boot2:file|boo
t3:file]
Command to display the version of the compressed image file
associated with the given device:filename.
See Also ls on page 643
ls
Usage Displays a list of the boot prompt commands.
To display help for an individual command, type help followed by the command name (for
example, help boot).
Syntax ls
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples To display a list of the commands available at the boot prompt, type the following
command:
boot> ls
ls
help
autoboot
option.
boot
Load and execute an image using the current boot
configuration profile.
Copyright 2011, Juniper Networks, Inc.
643
change
create
delete
next
show
dir
fver
Display the version of the loadable image specified by
device:filename.
version
information.
reset
test
diag
option.
next
Usage Activates and displays the boot profile in the next boot profile slot. (For information about
boot profiles, see show on page 646.)
An MX contains 4 boot profile slots, numbered 0 through 3. This command activates the boot
profile in the next slot, in ascending numerical order. If the currently active slot is 3, the command
activates the boot profile in slot 0.
Syntax next
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples To activate the boot profile in the next slot and display the profile, type the following
command:
boot> next
644
BOOT Index:
BOOT TYPE:
DEVICE:
boot1:
FILENAME:
testcfg
FLAGS:
00000000
OPTIONS:
run=nos;boot=0
See Also
change on page 638
create on page 639
delete on page 640
show on page 646
reset
Usage Resets an MX hardware.
After resetting the hardware, the reset command attempts to load a system image file only if other
boot settings are configured to do so.
Syntax reset
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples To immediately reset the system, type the following command at the boot prompt:
boot> reset
Juniper Networks WLC Bootstrap 1.17 Release
Testing Low Memory 1 ............
Testing Low Memory 2 ............
CISTPL_VERS_1:
4.1
1.6.5
Release
Bootstrap 0 version:
1.17
Active
Bootloader 0 version:
1.6.5
Active
Bootstrap 1 version:
1.17
Bootloader 1 version:
1.6.3
3.
24.
BOOT Index:
BOOT TYPE:
DEVICE:
boot1:
FILENAME:
default
FLAGS:
00000000
OPTIONS:
run=nos;boot=0
645
show
Usage Displays the currently active boot profile. A boot profile is a set of parameters that an MX
uses to control the boot process. Each boot profile contains the following parameters:
Boot typeEither compact flash (local device on the MX) or network (TFTP)
Boot deviceLocation of the system image file
FilenameSystem image file
FlagsNumber representing the bit settings of boot flags to pass to the booted system image.
OptionsString up to 128 bytes of boot options to pass to the booted system image
An MX can have up to four boot profiles, numbered 0 through 3. Only one boot profile can be
active at a time. You can create, change, and delete boot profiles. You also can activate another
boot profile in place of the currently active one.
Syntax show
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Examples To display the currently active boot profile, type the following command at the boot
prompt:
boot> show
BOOT Index:
BOOT TYPE:
DEVICE:
boot1:
FILENAME:
default
FLAGS:
00000000
OPTIONS:
run=nos;boot=0
The following is an example of a boot profile from an WLCR-2 that is booted with a software image
downloaded from a TFTP server. In the example, when the WLCR-2 boots, it downloads a system
image file called bootfile located on a TFTP server with address 172.16.0.1.
boot> show
646
BOOT Index:
BOOT TYPE:
DEVICE:
emac1
FILENAME:
bootfile
HOST IP:
172.16.0.1
LOCAL IP:
172.16.0.21
GATEWAY IP:
172.16.0.20
IP MASK:
255.255.255.0
FLAGS:
00000000
OPTIONS:
run=nos
Description
BOOT Index
BOOT TYPE
Boot type:
cCompact flash. Boots using nonvolatile storage or a flash card.
nNetwork. Boots using a TFTP server.
DEVICE
HOST IP
For network booting, the IP address of the host with the system image.
LOCAL IP
For network booting, the IP address of the WLC. If the DHCP option is enabled, this
does not need to be specified.
GATEWAY IP
For network booting, the default router (gateway) used by the WLC. If the DHCP option
IP MASK
For network booting, the subnet mask. If the DHCP option is enabled, this does not
FLAGS
Number representing the bit settings of boot flags to pass to the booted system image.
OPTIONS
String up to 128 bytes of boot options to pass to the booted system image.
See Also
change on page 638
create on page 639
delete on page 640
dhcp on page 640
next on page 644
test
Usage Displays or changes the state of the poweron test flag. The poweron test flag controls
whether an MX performs a set of self tests prior to the boot process.
647
on
OFF
off
version
Usage Displays version information for the MX hardware and boot code.
Syntax version
Defaults None.
Access Boot prompt.
History Introduced in MSS Version 1.0.
Usage This command does not list the system image file versions installed in the boot partitions.
To display system image file versions, use the dir or fver command.
648
Examples To display hardware and boot code version information, type the following command at
the boot prompt:
boot> version
Juniper Networks WLC Bootstrap/Bootloader
Version
1.6.5
Release
Bootstrap 0 version:
1.17
Active
Bootloader 0 version:
1.6.5
Active
Bootstrap 1 version:
1.17
Bootloader 1 version:
1.6.3
3.
24.
See Also
dir on page 641
fver on page 642
649
650