It looks like the port-security command was configured before you configured them as members of an EtherChannel. Since port-security isn't compatible with EtherChannel the CLI doesn't accept port-security commands when the port is configured as part of an EtherChannel.
You need to remove the EtherChannel configuration first before it will let you remove the port-security commands. The best way to do this is to shut the physical interfaces down, remove the channel-group command, then remove the switcport port-security command, re-add the channel-group command and then do a no shut.
I have just tested this on a 3550 and I get the same behaviour as you.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.