[c-nsp] Cisco/RADIUS PoD Disconnect Problem

[Alexander Serkin]

There might be differences between your 12.3(11)YF and 12.3(14)YX images 
we were using (it is PDSN, isn't it?). Try some combination of 
User-Name, Framed-IP-Address, Acct-Session-Id, NAS-Identifier, 
NAS-IP-Address and/or Calling-Station-Id in the PoD. This is from 
Release Notes:

"The Disconnect Request contains the NAS-ID and the Username (NAI) 
attributes. It can optionally contain 3GPP2 Correlation ID Calling 
station ID (IMSI) and the Framed IP address—some session identification 
attributes."

And more:

"CSCef18987—POD Debugs Display NACK Error Message For a Valid POD Request

A Cisco PDSN running R2.0 S/W incorrectly displays a NACK message being 
sent even though it correctly sends an ACK message to RADIUS server in 
response to a POD request.

This condition occurs when the POD feature is enabled, and the PDSN 
receives a POD request from RADIUS server with only NAI and NAS-ID and 
no session identification attributes in it. "

I'm not sure that i've tested PoD on YF images.

Mark Tinka wrote:
> On Monday 05 March 2007 13:16, Alexander Serkin wrote:
> 
>> aaa server radius dynamic-author
>>   client a.b.c.d
>>   server-key 0 secret
>>   auth-type any
> 
> We have this configured the same way.
> 
>> and the PoD:
>>
>> User-Name = <name at realm>
>> Calling-Station-Id = <CLID>
> 
> If we include the "Calling-Station-Id" attribute it cannot locate 
> the session. We are supplying the "User-Name" attribute in the PoD 
> request.
> 
> Our command set is:
> 
> # radpwtst -user test -s n.n.n.n -secret xxxx -auth_port \   
>   1645 -acct_port 1646 -nas_ip_address a.a.a.a -noauth -noacct \
>   -trace 4 -code Disconnect-Request User-Name=test
> 
> Mark.
> 
> 


-- 
Sincerely Yours,
Alexander