When configuring a PIX 6.x to use the PPPoE client on the outside interface, if you recieve the following error :
“PPPoE: Unsolicited PADO, Invalid session state”
It probably means you’re as dumb as I am and didn’t specify a vpdn username with the following command :
pix(config)#vpdn username <username from ISP> password <Password>
I was recently configuring an ASA running 8.x software to authenticate and download ACL’s for remote-access users from microsoft IAS. During my testing I changed one of the ACE’s but accidentally used incorrect syntax (tried to match a port number on an “ip” access list):
ip:inacl#100=permit ip 10.1.0.0 255.255.255.0 host 10.2.0.1 eq 3389
Which should have read
ip:inacl#100=permit tcp 10.1.0.0 255.255.255.0 host 10.2.0.1 eq 3389
The end result was that my authentication denied and I received this error on the ASA:
%ASA-3-109032: Unable to install ACL ‘AAA-user-username-ABC12345’, downloaded for user username; Error in ACE: ‘permit ip 10.1.0.0 255.255.255.0 host 10.2.0.1 eq 3389’
No biggie, fixed the syntax and tried to logon again. But then I recieved this interesting error:
%ASA-4-716023: Group <groupName> User <username> IP <x.x.x.x> Session could not be established: session limit of 2 reached.
%ASA-4-716007: Group <groupName> User <username> IP <x.x.x.x> WebVPN Unable to create session
I thought maybe I had some previous sessions still connected:
ASA# sh uauth
Current Most Seen
Authenticated Users 0 1
Authen In Progress 0 0
ASA# sh vpn-sessiondb webvpn
INFO: There are presently no active sessions of the type specified
It appears that if a SSLvpn connection fails due to an incorrectly configured downloadable ACE it locks out that session. I couldn’t find a command that would return the sessions back to the available pool and had to reload the ASA to correct it.
Now I doubt you would see this issue in a production environment but if anyone knows of a way to correct this without reloading I would love to know.
Version 8.0(2) contains a bug that involves an inconsistent interpretation of what the default command is for “crypto isakmp nat-traversal 20”. Whilst running, the device appears to have this command on by default but on boot the command is negated by default. The effect of this is nat-traversal is disabled every time you reboot the ASA.
Use a non-default keep-alive interval. I used “crypto isakmp nat-traversal 30” and the command now persists through a reboot.
Note: This issue appears to be fixed in 8.0(3) bug ID CSCsj5258.
I recieved a lesson in research first, configure second today.
I was trying to configure l2tp over IPSEC on an ASA 5510 running version 8.0(2) software and for life of me couldn’t work out why it wasn’t working. I kept getting this error every time I tried to create the tunnel:
%ASA-4-713903: Group = x.x.x.x, IP = y.y.y.y, Can’t find a valid tunnel group, aborting…!
%ASA-3-713902: Group = x.x.x.x, IP = y.y.y.y, Removing peer from peer table failed, no match!
%ASA-4-713903: Group = x.x.x.x, IP = y.y.y.y, Error: Unable to remove PeerTblEntry
%ASA-4-713903: IP = x.x.x.x, Header invalid, missing SA payload! (next payload = 4)
Google didn’t really turn much information. OK, time to check cisco.com and I found this article.
I made the mistake of jumping straight down to the configuration example, which still left me stumped for as far as I could tell I had configured the ASA correctly.
Then I noticed this line:
“Use only the default tunnel group and default group policy on the Cisco PIX/ASA. User-defined policies and groups do not work.”
Arrrgh! I switched the configuration to “tunnel-group DefaultRAGroup” and everything worked great.
Interestingly though I didn’t switch the group-policy from my user-defined policy and the configuration still worked fine.