苹果DreamBLE_LED下载 , 最新版DreamBLE_LEDiPad|iPhone手机版免费下载-PP助手官网
当前位置：
& 苹果版DreamBLE_LED下载
DreamBLE_LED软件截图DreamBLE_LED下载信息DreamBLE_LED简介
ColorMorpth是一款定制的LED 蓝牙智能灯具控制应用软件,支持汉语、英语。主要功能有开关、调色、调亮度、定时、DIY颜色渐变，跳变，频闪模式、随音乐跳动的模式、根据照相机抓取的颜色变化、单控和组控等功能。操作步骤：1. 手机下载安装该应用。2. 将蓝牙灯具通电。3 .打开本app去连接,操控它。DreamBLE_LED更新日志
增加了一个调色版。DreamBLE_LED同一开发者
DreamBLE_LED相关资讯
DreamBLE_LED使用技巧
下载DreamBLE_LED的人还喜欢
应用下载排行榜1
68 万下载2
48 万下载3
44 万下载4
41 万下载5
41 万下载6
37 万下载7
26 万下载8
PP苹果助手：love25ppcom
扫一扫安装PP助手iOS版您所在位置： &
&nbsp&&nbsp&nbsp&&nbsp
基于ZigBe与蓝牙转换的多汇聚节点数据传输系统研究.pdf 66页
本文档一共被下载：
次 ,您可全文免费在线阅读后下载本文档。
下载提示
1.本站不保证该用户上传的文档完整性，不预览、不比对内容而直接下载产生的反悔问题本站不予受理。
2.该文档所得收入(下载+内容+预览三)归上传者、原创者。
3.登录后可充值，立即自动返金币，充值渠道很便利
基于ZigBe与蓝牙转换的多汇聚节点数据传输系统研究.pdf
你可能关注的文档：
··········
··········
分类号：____________
级：______________公开
ＵＤＣ：____________
单位代码：______________
硕士学位论文
论文题目：基于ZigBee 与蓝牙转换的多汇聚节点数据传输系统研究
号：_________________________
名：_________________________
信号与信息处理
专 业 名 称：_________________________
信息科学与工程学院
院：_________________________
指 导 教 师：_________________________
论文提交日期：2014 年6 月 12 日
A Thesis Submitted to Ningbo University for the Master’s Degree
Research on the multi-sink data transmission system
based on ZigBee and Bluetooth forwarding
Candidate ： Guo Chunhong
Supervisors：Professor Zhou
Faculty of Electrical Engineering
and Computer Science
Ningbo University
315211 ， Zhejiang
独 创 性 声 明
本人郑重声明：所呈交的论文是我个人在导师指导下进行的研究工作及取
得研究成果。尽我所知，除了文中特别加以标注和致谢的地方外，论文中不包
含其他人已经发表或撰写的研究成果，也不包含为获得宁波大学或其他教育机
构的学位或证书所使用过的材料。与我一同工作的同志对本研究所做的任何贡
献均已在论文中做了明确的说明并表示了谢意。
若有不实之处，本人愿意承担相关法律责任。
签名：___________
日期：____________
关于论文使用授权的声明
本人完全了解宁波大学有关保留、使用学位论文的规定，即：学校有权保
留送交论文的复印件，允许论文被查阅和借阅；学校可以公布论文的全部或部
分内容，可以采用影印、缩印或其他复制手段保存论文。
正在加载中，请稍后...&&&&Nabu PressHistory&Reports&On&Trade&At&The&Treaty&Ports&For&The&Year&:...
邀请好友参加吧
版 次：页 数：442字 数：印刷时间：开 本：64开纸 张：包 装：平装是否套装：否国际标准书号ISBN：6所属分类：&&&
下载免费当当读书APP
品味海量优质电子书，尊享优雅的阅读体验，只差手机下载一个当当读书APP
本商品暂无详情。
当当价：为商品的销售价，具体的成交价可能因会员使用优惠券、积分等发生变化，最终以订单结算页价格为准。
划线价：划线价格可能是图书封底定价、商品吊牌价、品牌专柜价或由品牌供应商提供的正品零售价（如厂商指导价、建议零售价等）或该商品曾经展示过的销售价等，由于地区、时间的差异化和市场行情波动，商品吊牌价、品牌专柜价等可能会与您购物时展示的不一致，该价格仅供您参考。
折扣：折扣指在划线价（图书定价、商品吊牌价、品牌专柜价、厂商指导价等）某一价格基础上计算出的优惠比例或优惠金额。如有疑问，您可在购买前联系客服咨询。
异常问题：如您发现活动商品销售价或促销信息有异常，请立即联系我们补正，以便您能顺利购物。
当当购物客户端手机端1元秒
当当读书客户端万本电子书免费读Cisco IOS Security Command Reference: Commands M to R, Cisco IOS XE Release 3SE (Cisco WLC 5700 Series) - radius attribute nas-port-type through rd [Cisco 5700 Series Wireless LAN Controllers] - Cisco
Cisco IOS Security Command Reference: Commands M to R, Cisco IOS XE Release 3SE (Cisco WLC 5700 Series)
Book Contents
Book Contents
Available Languages
Download Options
Book Title
Cisco IOS Security Command Reference: Commands M to R, Cisco IOS XE Release 3SE (Cisco WLC 5700 Series)
Chapter Title
radius attribute nas-port-type through rd
View with Adobe Reader on a variety of devices
Chapter: radius attribute nas-port-type through rd
Chapter Contents
radius attribute nas-port-type through rd
radius-server attribute nas-port format
To set the NAS-Port format used for RADIUS accounting features and restore the default NAS-port format, or to set the global attribute 61 session format e string or configure a specific service port type for attribute 61 support, use the radius-server attribute nas-port format command in global configuration mode. To stop sending attribute 61 to the RADIUS server, use the no form of this command.
NAS-Port for RADIUS Accounting Features and Restoring Default NAS-Port Format
radius-server
radius-server
Extended NAS-Port Support
radius-server
nas-port-type ]
radius-server
nas-port-type ]
Syntax Description
NAS-Port format. Possible values for the format argument are as follows:
a--Standard NAS-Port format
b--Extended NAS-Port format
c--Carrier-based format
d--PPPoX (PPP over Ethernet or PPP over ATM) extended NAS-Port format
e--C onfigurable NAS-Port format
(Optional) Represents all of a specific port typefor format e. It is possible to specify multiple values with this argument.
nas-port-type
(Optional) Allows you to globally specify different format strings to represent specific physical port types.
You may set one of the extended NAS-Port-Type attribute values:
type 30 --PPP over ATM (PPPoA)
type 31 --PPP over Ethernet (PPPoE) over ATM (PPPoEoA)
type 32 --PPPoE over Ethernet (PPPoEoE)
type 33 --PPPoE over VLAN (PPPoEoVLAN)
type 34 --PPPoE over Q-in-Q (PPPoEoQinQ)
Command Default
Standard NAS-Port format for NAS-Port for RADIUS accounting features and restoring default NAS-Port format or extended NAS-Port support.
Command Modes
Global configuration
Command History
Modification
Usage Guidelines
The radius-server attribute nas-port format command configures RADIUS to change the size and format of the NAS-Port attribute field (RADIUS IETF attribute 5).
The following NAS-Port formats are supported:
Standard NAS-Port format--This 16-bit NAS-Port format indicates the type, port, and channel of the controlling interface. This is the default format used by Cisco IOS software.
Extended NAS-Port format--The standard NAS-Port attribute field is expanded to 32 bits. The upper 16 bits of the NAS-Port attribute display the type and number of the c the lower 16 bits indicate the interface that is undergoing authentication.
Shelf-slot NAS-Port format--This 16-bit NAS-Port format supports expanded hardware models requiring shelf and slot entries.
PPP extended NAS-Port format--This NAS-Port format uses 32 bits to indicate the interface, virtual path identifier (VPI), and virtual channel indicator (VCI) for PPPoA and PPPoEoA, and the interface and VLAN ID for PPPoE over Institute of Electrical and Electronic Engineers (IEEE) standard 802.1Q VLANs.
Before Cisco IOS Release 12.2(4)T formats a through c did not work with Cisco platforms such as the AS5400. For this reason, a configurable format e was developed. Format e requires you to explicitly define the usage of the 32 bits of attribute 25 (NAS-Port). The usage is defined with a given parser character for each NAS-Port field of interest for a given bit field. By configuring a single character in a row, such as x, only one bit is assigned to store that given value. Additional characters of the same type, such as x, will provide a larger available range of values to be stored. The table belowshows how the ranges may be expanded:
Table 1&Format e Ranges
It is imperative that you know what the valid range is for a given parameter on a platform that you want to support. The Cisco IOS RADIUS client will bitmask the determined value to the maximum permissible value on the basis of configuration. Therefore, if one has a parameter that turns out to have a value of 8, but only 3 bits (xxx) are configured, 8 and 0x7 will give a result of 0. Therefore, you must always configure a sufficient number of bits to capture the value required correctly. Care must be taken to ensure that format e is configured to properly work for all NAS port types within your network environment.
The table below shows the supported parameters and their characters:
Table 2&Supported Parameters and Characters
Supported Parameters
Characters
All 32 bits that represent the NAS-Port must be set to one of the above characters because this format makes no assumptions for empty fields.
Access Router
The DS0 port on a T1-based card and on a T3-based card will give different results. On T1-based cards, the physical port is equal to the virtual port (because these are the same). So, p and d will give the same information for a T1 card. However, on a T3 system, the port will give you the physical port number (because there can be more than one T3 card for a given platform). As such, d will give you the virtual T1 line (as per configuration on a T3 controller). On a T3 system, p and d will be different, and one should capture both to properly identify the physical device. As a working example for the Cisco AS5400, the following configuration is recommended:
Router (config)# radius-server attribute nas-port format e SSSSPPPPPPPPPsssspppppccccc
This will give one an asynchronous slot (0-16), asynchronous port (0-512), DS0 slot (0-16), DS0 physical port (0-32), DS0 virtual port (0-32), and channel (0-32). The parser has been implemented to explicitly require 32-bit support, or it will fail.
Finally, format e is supported for channel-associated signaling (CAS), PRI, and BRI-based interfaces.
This command replaces the radius-server attribute nas-port extended command.
Extended NAS-Port-Type Attribute Support
This command allows you to configure a specific service port type for extended attribute 61 support which overrides the default global setting.
In the following example, a RADIUS server is identified, and the NAS-Port field is set to the PPP extended format:
radius-server host 192.0.2.96 auth-port 1645 acct-port 1646
radius-server attribute nas-port format d
The following example shows how to configure global support for extended NAS-Port-Type ports and how to specify two separate format e strings globally for two different types of ports:
type 30 (which is PPPoA)
type 33 which is (PPPoEoVLAN)
Router# configure terminal
Router(config)#
Router(config)# radius-server attribute 61 extended
Router(config)# radius-server attribute nas-port format e SSSSAPPPUUUUUUUUUUUUUUUUUUUUUUUU
Router(config)# radius-server attribute nas-port format e SSSSAPPPIIIIIIIICCCCCCCCCCCCCCCC type 30
Router(config)#
Router(config)# radius-server attribute nas-port format e SSSSAPPPVVVVVVVVVVVVVVVVVVVVVVVV type 33
Related Commands
Description
radius-server configure-nas
To have the Cisco router or access server query the vendor-proprietary RADIUS server for the static routes and IP pool definitions used throughout its domain when the device starts up, use the radius-server configure-nas command in global configuration mode. To discontinue the query of the RADIUS server, use the no form of this command.
radius-server
configure-nas
radius-server
configure-nas
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Global configuration
Command History
Modification
Usage Guidelines
Use the radius-server configure-nas command to have the Cisco router query the vendor-proprietary RADIUS server for static routes and IP pool definitions when the router first starts up. Some vendor-proprietary implementations of RADIUS let the user define static routes and IP pool definitions on the RADIUS server instead of on each individual network access server in the network. As each network access server starts up, it queries the RADIUS server for static route and IP pool information. This command enables the Cisco router to obtain static routes and IP pool definition information from the RADIUS server.
Because the radius-server configure-nas command is performed when the Cisco router starts up, it will not take effect until you issue a copy system:running-config nvram:startup-config command.
The following example shows how to tell the Cisco router or access server to query the vendor-proprietary RADIUS server for already-defined static routes and IP pool definitions when the device first starts up:
radius-server configure-nas
Related Commands
Description
radius-server dead-criteria
To force one or both of the criteria--used to mark a RADIUS server as dead--to be the indicated constant, use the radius-server dead-criteria command in global configuration mode. To disable the criteria that were set, use the no form of this command.
radius-server
dead-criteria
number-of-tries ]
radius-server
dead-criteria
seconds | tries
number-of-tries ]
Syntax Description
(Optional) Minimum amount of time, in seconds, that must elapse from the time that the router last received a valid packet from the RADIUS server to the time the server is marked as dead. If a packet has not been received since the router booted, and there is a timeout, the time criterion will be treated as though it has been met. You can configure the time to be from 1 through 120 seconds.
If the secondsargument is not configured, the number of seconds will range from 10 to 60 seconds, depending on the transaction rate of the server.
Both the time criterion and the tries criterion must be met for the server to be marked as dead.
number-of-tries
(Optional) Number of consecutive timeouts that must occur on the router before the RADIUS server is marked as dead. If the server performs both authentication and accounting, both types of packets will be included in the number. Improperly constructed packets will be counted as though they were timeouts. All transmissions, including the initial transmit and all retransmits, will be counted. You can configure the number of timeouts to be from 1 through 100.
If thenumber-of-triesargument is not configured, the number of consecutive timeouts will range from 10 to 100, depending on the transaction rate of the server and the number of configured retransmissions.
Both the time criterion and the tries criterion must be met for the server to be marked as dead.
Command Default
The number of seconds and number of consecutive timeouts that occur before the RADIUS server is marked as dead will vary, depending on the transaction rate of the server and the number of configured retransmissions.
Command Modes
Global configuration (config)
Command History
Modification
Usage Guidelines
Both the time criterion and the tries criterion must be met for the server to be marked as dead.
The no form of this command has the following cases:
If neither the seconds nor the number-of-tries argument is specified with the no radius-server dead-criteriacommand, both time and tries will be reset to their defaults.
If the seconds argument is specified using the originally set value, the time will be reset to the default value range (10 to 60).
If the number-of-tries argument is specified using the originally set value, the number of tries will be reset to the default value range (10 to 100).
The following example shows how to configure the router so that it will be considered dead after 5 seconds and 4 tries:
Router (config)# radius-server dead-criteria time 5 tries 4
The following example shows how to disable the time and number-of-tries criteria that were set for the radius-server dead-criteria command.
Router (config)# no radius-server dead-criteria
The following example shows how to disable the time criterion that was set for the radius-server dead-criteria command.
Router (config)# no radius-server dead-criteria time 5
The following example shows how to disable the number-of-tries criterion that was set for the radius-server dead-criteria command.
Router (config)# no radius-server dead-criteria tries 4
Related Commands
Description
radius-server load-balance
To enable RADIUS server load balancing for the global RADIUS server group referred to as “radius” in the authentication, authorization and accounting (AAA) method lists, use the radius-server load-balance command in global configuration mode. To disable RADIUS server load balancing, use the no form of this command.
radius-server
load-balance
least-outstanding
[ batch-size
[ignore-preferred-server]
radius-server
load-balance
Syntax Description
method least-outstanding
Enables least outstanding mode for load balancing.
batch-size
(Optional) The number of transactions to be assigned per batch.
(Optional) The number of transactions in a batch.
The default is 25.
The range is 1-.
Batch size may impact throughput and CPU load. It is recommended that the default batch size, 25, be used because it is optimal for high throughput, without adversely impacting CPU load.
ignore-preferred-server
(Optional) Indicates if a transaction associated with a single AAA session should attempt to use the same server or not.
If set, preferred server setting will not be used.
Default is to use the preferred server.
Command Default
If this command is not configured, global RADIUS server load balancing will not occur.
Command Modes
Global configuration
Command History
Modification
The following example shows how to enable load balancing for global RADIUS server groups. It is shown in three parts: the current configuration of RADIUS command output, debug output, and AAA server status information. You can use the delimiting characters to display only the relevant parts of the configuration.
Server Configuration and Enabling Load Balancing for Global RADIUS Server Group Example
The following shows the relevant RADIUS configuration:
Router# show running-config | inc radius
aaa authentication ppp default group radius
aaa accounting network default start-stop group radius
radius-server host 192.0.2.238 auth-port 2095 acct-port 2096 key cisco
radius-server host 192.0.2.238 auth-port 2015 acct-port 2016 key cisco
radius-server load-balance method least-outstanding batch-size 5
The lines in the current configuration of RADIUS command output above are defined as follows:
The aaa authentication pppcommand authenticates all PPP users using RADIUS.
The aaa accounting command enables the sending of all accounting requests to the AAA server after the client is authenticated and after the disconnect using the keyword start-stop.
The radius-server host command defines the IP address of the RADIUS server host with the authorization and accounting ports specified and the authentication and encryption key identified.
The radius-server load-balance command enables load balancing for the global RADIUS server groups with the batch size specified.
Debug Output for Global RADIUS Server Group Example
The debug output below shows the selection of preferred server and processing of requests for the configuration above.
Router# show debug
General OS:
AAA server group server selection debugging is on
&sending 10 pppoe requests&
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:No more transactions in batch. Obtaining a new server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining a new least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Server[0] load:0
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Server[1] load:0
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Selected Server[0] with load 0
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[5] transactions remaining in batch.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[4] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[3] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[2] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[1] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:No more transactions in batch. Obtaining a new server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining a new least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Server[1] load:0
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Server[0] load:5
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Selected Server[1] with load 0
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[5] transactions remaining in batch.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT():Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT(0000001A):No preferred server available.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.199:AAA/SG/SERVER_SELECT:[4] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT(0000001A):Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT(0000001B):No preferred server available.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT:[3] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT(0000001B):Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT(0000001C):No preferred server available.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT:[2] transactions remaining in batch. Reusing server.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT(0000001C):Server (192.0.2.238:) now being used as preferred server
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT(0000001D):No preferred server available.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT:Obtaining least loaded server.
*Feb 28 13:40:32.203:AAA/SG/SERVER_SELECT:[1] transactions remaining in batch. Reusing server
Server Status Information for Global RADIUS Server Group Example
The output below shows the AAA server status for the global RADIUS server group configuration example.
Router# show aaa server
RADIUS:id 4, priority 1, host 192.0.2.238, auth-port 2095, acct-port 2096
State:current UP, duration 3175s, previous duration 0s
Dead:total time 0s, count 0
Quarantined:No
Authen:request 6, timeouts 1
Response:unexpected 1, server error 0, incorrect 0, time 1841ms
Transaction:success 5, failure 0
Author:request 0, timeouts 0
Response:unexpected 0, server error 0, incorrect 0, time 0ms
Transaction:success 0, failure 0
Account:request 5, timeouts 0
Response:unexpected 0, server error 0, incorrect 0, time 3303ms
Transaction:success 5, failure 0
Elapsed time since counters last cleared:2m
RADIUS:id 5, priority 2, host 192.0.2.238, auth-port 2015, acct-port 2016
State:current UP, duration 3175s, previous duration 0s
Dead:total time 0s, count 0
Quarantined:No
Authen:request 6, timeouts 1
Response:unexpected 1, server error 0, incorrect 0, time 1955ms
Transaction:success 5, failure 0
Author:request 0, timeouts 0
Response:unexpected 0, server error 0, incorrect 0, time 0ms
Transaction:success 0, failure 0
Account:request 5, timeouts 0
Response:unexpected 0, server error 0, incorrect 0, time 3247ms
Transaction:success 5, failure 0
Elapsed time since counters last cleared:2m
The output shows the status of two RADIUS servers. Both servers are up and, in the last 2 minutes, have processed successfully:
5 out of 6 authentication requests
5 out of 5 accounting requests
Related Commands
Description
radius-server vsa send
To configure the network access server (NAS) to recognize and use vendor-specific attributes (VSAs), use the radius-server vsa send command in global configuration mode. To disable the NAS from using VSAs, use the no form of this command.
radius-server
[ accounting | authentication | cisco-nas-port ]
radius-server
[ accounting | authentication | cisco-nas-port ]
Syntax Description
accounting
(Optional) Limits the set of recognized VSAs to only accounting attributes.
authentication
(Optional) Limits the set of recognized VSAs to only authentication attributes.
cisco-nas-port
(Optional) Returns the Cisco NAS port VSA.
Due to the IETF requirement for including NAS port information in attribute 87 (Attr87), the Cisco NAS port is obsoleted by default.
(Optional) Adds Third Generation Partnership Project 2 (3GPP2) Cisco VSAs to the 3GPP2 packet type.
Command Default
NAS is not configured to recognize and use VSAs.
Command Modes
Global configuration (config)
Command History
Modification
Usage Guidelines
The IETF draft standard specifies a method for communicating vendor-specific information between the NAS and the RADIUS server by using the VSA (attribute 26). VSAs allow vendors to support their own extended attributes not suitable for general use. The radius-server vsa send command enables the NAS to recognize and use both accounting and authentication VSAs. Use the accounting keyword with the radius-server vsa send command to limit the set of recognized VSAs to accounting attributes only. Use the authentication keyword with the radius-server vsa send command to limit the set of recognized VSAs to authentication attributes only. Use the
show running-config all command to see the default radius-server vsa send accounting and radius-server vsa send authentication commands.
The Cisco RADIUS implementation supports one vendor-specific option using the format recommended in the specification. The Cisco vendor ID is 9, and the supported option has vendor-type 1, which is named cisco-avpair. The value is a string with the following format:
&protocol : attribute separator value&
In the preceding example, protocol is a value of the Cisco protocol attribute for a particular t attribute and value are an appropriate attribute-value (AV) pair defined in the Cisco TACACS+ and separator is = for mandatory attributes. This solution allows the full set of features available for TACACS+ authorization to also be used for RADIUS.
For example, the following AV pair causes the Multiple Named IP Address Pools feature to be activated during IP authorization (that is, during the PPP Internet Protocol Control Protocol [IPCP] address assignment):
cisco-avpair= &ip:addr-pool=first&
The following example causes a NAS Prompt user to have immediate access to EXEC commands.
cisco-avpair= &shell:priv-lvl=15&
Other vendors have their own unique vendor IDs, options, and associated VSAs. For more information about vendor IDs and VSAs, see RFC 2138, Remote Authentication Dial-In User Service (RADIUS).
The following example shows how to configure the NAS to recognize and use vendor-specific accounting attributes:
Device(config)# radius-server vsa send accounting
Related Commands
Description
To specify a route distinguisher (RD) for a VPN routing and forwarding (VRF) instance, use the rdcommand in VRF configuration mode. To remove a route distinguisher, use the no form of this command.
route-distinguisher
route-distinguisher
Syntax Description
route-distinguisher
An 8-byte value to be added to an IPv4 prefix to create a VPN IPv4 prefix.
Command Default
No RD is specified.
Command Modes
VRF configuration (config-vrf)
Command History
Modification
Usage Guidelines
An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. The RD is added to the beginning of the customer’s IPv4 prefixes to change them into globally unique VPN-IPv4 prefixes.
An RD is either:
ASN-related--Composed of an autonomous system number and an arbitrary number.
IP-address-related--Composed of an IP address and an arbitrary number.
You can enter an RD in either of these formats:
16-bit autonomous-system-number
your 32-bit number
For example, 101:3.
32-bit IP address
your 16-bit number
For example, 192.168.122.15:1.
The following example shows how to configure a default RD for two VRFs. It illustrates the use of both autonomous-system-number-relative and IP-address-relative RDs:
Router(config)# ip vrf vrf1
Router(config-vrf)# rd 100:3
Router(config-vrf)# exit
Router(config)# ip vrf vrf2
Router(config-vrf)# rd 10.13.0.12:200
The following is an example of a VRF for IPv4 and IPv6 that has common policies defined in the global part of the VRF configuration:
vrf definition vrf2
route-target both 200:2
address-family ipv4
exit-address-family
address-family ipv6
exit-address-family
Related Commands
Description
Was this Document Helpful?
Let Us Help
(Requires a )
Related Support Community Discussions}