##EDIT: to anyone who stumbles on this in the future, the "Profile.xml" is case sensitive. If you attempt to use "profile.xml" for the cisco VPN client, it will not work. @alemabrahao had the solution dead on, this is just a reminder to double check the case of your file.
I just installed the AnyConnect client from my company in order to get the stuff I needed to make OpenConnect work, so I did go through the install and might be able to help you out. This was with 3.1.04063, so keep that in mind as I don't know what's different for 4.0. My company has a Windows cifs share with the anyconnect available clients, but they were in a .pkg format. I extracted them with 7-zip on Windows, then copying that folder to somewhere I could get at from Arch.
I used to sort of be able to use the actual anyconnect client, but only from my 32 bit chroot (I'm on x64). And then something seemed to go awry with /etc/resolv.conf or some other network settings, as the successful VPN connection in the chroot didn't seem to translate into my "actual" 64 bit environment and thus I couldn't do anything with the internet. Web pages just wouldn't load. Same with a 32 chroot installed browser, though, too... so I'm not sure what the issue was. I could ping, with ridiculously slow return times, but never do anything useful.
We connect to 2 different sites with anyconnect, but those 2 locations have a site-site VPN tunnel between them. Regardless, for some reason what worked for me to resolve this problem was to connect to site A using the older version of the anyconnect client. Then disconnect, and connect to site B, which automatically updated the client version upon connect. For whatever reason, that worked.