We installed a SA540 last Saturday at a clients site and it has been nothing but a nightmare and they are now back using a Draytek until we can resolve the problems with the Cisco.
The SA540 was upgraded to Firmware version 1.1.42 (it shipped from the distributor with 1.0.15) during installation and configuration at the Site on Saturday. Inititally we had problems and had to force the WAN port on the 540 to run at 10Mbps full duplex in order for it to keep the WAN connection up. The 540 is connected to a 10Mbps fibre optic line via the carriers on site equipment. The carrier has repeatedly checked out the link and it is working perfectly (the Draytek also uses it without any issues). The 540 has a fairly simplistic configuration at the moment with 20 firewall rules and 5 IPSec VPN connections. It's plugged into an APC UPS to prevent any power fluctuations causing a problem. The box ran from 4pm on Saturday through till 08:10am on Monday at which point it locked up and the staff on site had to turn switch it off and on again before it would work again (just a point to make here that it is at least 5 minutes before the 540 is connected to the internet - is this typical of this device?). We then ha an issue where the 540 would say that the VPN's were connected, but they weren't, and it would not drop them either, the only way we could get the VPN's to run again was to delete both the IKE & VPN policies for each of the 5 VPN's and as each one was recreated then so that VPN link would run again. The device then started rebooting itself at around 11am on Tuesday, it would reboot and get connected to the internet and then after a minute or two it would just spontanesouly reboot itself again and we were unable to get it to stabilise and so we were forced to pull it out of the network and put the Draytek 2820 back in.
It's really embarrasing to have put the Draytek back in and basically - help!!!!
I remember this is the FW update that has a release not saying a factory reset and reconfiguration is required under certain conditions (the from release). What release did you upgrade from? I think you stated 1.0.15, which means you needed to wipe it......
Recommended Practices Recommended Upgrade Steps NOTE When upgrading from version 1.0.15, 1.0.17, or 1.0.39, the firmware will reset the router to its factory default and you will need to back up the configuration. When upgrading from 1.1.21, these steps are not required.
Robin, The WAN and VPN issues you are experiencing are not typical. Have you called our small business support center to have a case opened? That will allow us to better work with you to understand and resolve these issues. If a case has been opened, please respond back with the case #.
We are going back on site tomorrow to wipe, reload and configure things so that we can get the Cisco usable on the network
with the ability to put some traffic through it to give it some load but without upsetting the staff. :-) So once that is working then we will give the support team a ring and see what we can hammer out. I just thought it would be worth posting in the meantime as there may be things that people can suggest that we do that perhaps have had some experience of similar issues.
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
You have a Cisco Unified Communications Manager (CUCM) system and want
to configure a SPA112 analog telephone adaptor (ATA) to register to the
CUCM so that you can use up to two analog phones or similar FXS devices
with the CUCM.In this application note, ...
Introduction: This document describes how to connect SG300 with Catalyst
switch via STP. Spanning Tree Protocol (STP) is a Layer 2 protocol that
runs on mainly on switches. The specification for STP is IEEE 802.1D.
The main purpose of STP is to ensure tha...