Thinking Workshop”. Cisco Small Business is excited to invite its
Silicon Valley customers to an exclusive interactive one-day session
customers and product Managers. If you are interested in this
workshop, please fill out the Registration
For more information, please check out our FAQ
Get the latest new and information the November issue of the Cisco Small Business Monthly Newsletter
Using CCA 2.0.1 on UC520.
12.4(22)YB/ CME 7.1
After inputting everything through CCA & pressing OK, it said:
CCA detects unsupported firewall configuration on the device UC520
CCA will not create pass-through for unrecognised firewall configuration
I made some changes to F0/4 ACL to allow SSH from Internet...so that could be the changes.
How do I complete the config through CLI?
I will have 5 SR520 connecting...would be nice if I could use GUI on them at least.
I would remove what you have added manually, and then readd it in CCA. If you need in configuring it CCA, let me know. You can enable portforwarding in CCA.
For CLI guide on how to do S2S VPN, refer to:
Please notice this document is UC 500 centric (not SR520).
I think I misread what you were wanting earlier. If you are going to have a UC500 behind a SR520, you should delete the firewall settings on the UC500, the NAT on the UC500, and add routes on the SR520 to go to the UC500. After that, you do the port forwarding through CCA on the SR520 for what you want to pass though.
3rd times the charm... I hope.
That document talks about using remote sites with an 871. You can basically do this with a SR520. If you want this to work via CCA, then my first post is correct. Undo the changes you made via CLI, and redo them via CCA. Also, you should look at the CCA out of band configuration guide. It will let you know how to make changes via CLI that will work with CCA.
In your config, you have...
ip local pool SDM_POOL_1 192.168.1.5 192.168.1.20
You should make this part of your data network, somewhere in the 192.168.0.0/24 range.
I don't have my CCA open right now, but I believe you can set this pool through CCA.
I would use 192.168.0.245 to 192.168.0.254.
Made that change.
Still not able to register IP Communicator nor can I use CCA through the VPN tunnel nor ping anything inside.
I also see this.
ISAKMP:(0):Support for IKE Fragmentation not enabled
If you did the change in CLI, there are changes to access-lists that need to be made. If you did it in CCA, that is good. To get rid of the error message.
crypto isakmp fragmentation