Troubleshooting Guide - FarSync WAN T-Series - Linux
|
| Problem Symptom | Possible Cause(s) | Action |
| farutil sync0 reports a different configuration from that in the ifcfg-sync0 configuration file. | Backup's of configuration files are causing a problem | Please purge backup files from the configuration directory.
Typically, if you edit ifcfg-sync0 to change the PROTO from ppp to cisco with xemacs, then xemacs creates a backup file called ifcfg-sync0~ (this is a copy of the file before you made the change). You then bring the interface down and up again with ifdown/farifdown and ifup/farifup, and check the configuration with farutil sync0, to verify that the PROTO is now cisco. However, next time you boot, and then use farutil on sync0 to examine the configuration is has reverted back to ppp. This is because the startup scripts look for configuration files using a wildcard, i.e. files starting with ifcfg-sync* and in this case will call ifup/farifup with ifcfg-sync0 and then ifcfg-sync0~, thus reverting the configuration back to the original. |