04-01-2003 05:59 AM - edited 03-02-2019 06:18 AM
router(config)#radius-server attribute nas-port format ?
a Format is type, channel, port
b Either interface(16) or isdn(16), async(16)
c Data format(bits): shelf(2), slot(4), port(5), channel(5)
d Data format(bits): slot(4), module(1), port(3), vpi(8), vci(16)
e Configurable data format
Are there any examples about option 'e'?
CCO doesn't even refer it.
Solved! Go to Solution.
04-01-2003 11:44 AM
This was a feature request for more scalable and flexible 32 nas-port attribute through CSCdt60424.
AAA Nas Port Format E is being introduced, which allow a
customer to customize the exact output of the 32 bits which represent
Radius attribute 5.
Zero : 0
One : 1
DS0 shelf : f
DS0 slot : s
DS0 adapter : a
DS0 port : p
DS0 subinterface : i
DS0 channel : c
Async shelf : F
Async slot : S
Async port : P
Async Line : L
The configuration requires all 32 bits be explicitly defined. Any value
exceeding the bit range configured will be bitmasked away and can cause
incorrect port information to be provided. As such, care should be taken
to ensure that enough bits are defined to represent a given field of interest
for the platform being used.
A working example used for the AS5400 which would provice both the Async
and DS0 information would be:
radius-server attribute nas-port format e SSSSPPPPPPPPPssssaaaaapppppccccc
Thanks, Mak.
04-01-2003 08:32 AM
04-01-2003 08:38 AM
I have already seen this url. It doesn't refer to option 'e', only a-d
04-01-2003 11:44 AM
This was a feature request for more scalable and flexible 32 nas-port attribute through CSCdt60424.
AAA Nas Port Format E is being introduced, which allow a
customer to customize the exact output of the 32 bits which represent
Radius attribute 5.
Zero : 0
One : 1
DS0 shelf : f
DS0 slot : s
DS0 adapter : a
DS0 port : p
DS0 subinterface : i
DS0 channel : c
Async shelf : F
Async slot : S
Async port : P
Async Line : L
The configuration requires all 32 bits be explicitly defined. Any value
exceeding the bit range configured will be bitmasked away and can cause
incorrect port information to be provided. As such, care should be taken
to ensure that enough bits are defined to represent a given field of interest
for the platform being used.
A working example used for the AS5400 which would provice both the Async
and DS0 information would be:
radius-server attribute nas-port format e SSSSPPPPPPPPPssssaaaaapppppccccc
Thanks, Mak.
04-01-2003 08:17 PM
That was a very fine answer Mak :-) But here comes another one for you....
I have a 5350 with the following interfaces (only isdn clients):
Serial1/0:0 - Serial1/0:30
Serial1/1:0 - Serial1/1:30
Serial1/2:0 - Serial1/2:30
Serial1/3:0 - Serial1/3:30
Serial1/4:0 - Serial1/4:30
Serial1/5:0 - Serial1/5:30
Serial1/6:0 - Serial1/6:30
Serial1/7:0 - Serial1/7:30
----------------------------------
Serial2/0:0 - Serial2/0:30
Serial2/1:0 - Serial2/1:30
Serial2/2:0 - Serial2/2:30
Serial2/3:0 - Serial2/3:30
Serial2/4:0 - Serial2/4:30
Serial2/5:0 - Serial2/5:30
Serial2/6:0 - Serial2/6:30
Serial2/7:0 - Serial2/7:30
What would be the correct 'e' format in order to achieve something like:
Serial1/0:0 - Serial1/0:30 -> Nas-port = xx1000-xx1030
Serial1/1:0 - Serial1/1:30 -> Nas-port = xx1100-xx1130
and so on....
Serial2/0:0 - Serial2/0:30 -> Nas-port = xx2000-xx2030
Serial2/1:0 - Serial2/1:30 -> Nas-port = xx2100-xx2130
and so on...
where x is any digit 0-9 (not necessarily 2 digits, can be more)
04-03-2003 05:46 PM
You are thinking decimal when we are dealing with binaries here.
So, if we define a range such as ccccc we are dealing with a range of chanels from 0 to 2^5 (32). No way to limit that to 30. If you preappend it with a pppppccccc, you are then dealing with a range of 0 to 32 ports, and 0 to 32 channels. This is the only way to maximime the use of the 32 bits allowed under NAS Port (attr 5).
The problems with format a and b is that they were in decimal and
could not represent the information needed within the 32 bits
available, as much was wasted.
Thanks, Mak.
04-08-2003 09:07 AM
Ok, i found a way to solve my problem after doing a lot of combinations.
A last question: Will this bug be integrated into any furure ios releases?
04-08-2003 11:47 AM
This was a feature request that was tracked thru CSCdt60424..it's integrated from IOS 12.2(03.04)T onwards.
Thanks, Mak.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: