hi
I’m in use CCR-1036/2ea, but i have a serious problem.
I would like to receive technical support about CCR-1036 series.
In brief my situation,
One(ccr1036-12g-4s1036, package version; 6.27, RB-v3.19) has trouble sometimes, but just about okey,
But other two CCRs(1036-12g-4s/1ea and ccr-1036-8g-2s+/1ea) are often repeated reboots.
After the CCR is started, cpu usage is increased continuously.
When cpu usage exceeds 60%, ccr device reboots automatically.
Shutdown period is the average 4 hours, sometimes fine more than a day.
Looking at the profile, cpu usage of the firewall has been increased continuously
Traffic is below average 200Mbps.
In summary of the operation in policy,
- interface Ethernet; 10
- interface bonding; bonding1(ether1-ether2), bonding2(ether3-ether4)
- ip address; total 13
- ip r; 69
- ip r rule; 148
- ip firewall nat; netmap52
- etc; nothing
ccr 1036-12g-4s1036; package version; 6.28, RB-v3.22
- ccr-1036-8g-2s+; package version; 6.32.2, RB-v3.27
- topology;
GigaEthernet->ISP1_L2_switch > ccr1036_eth2)> local eth7 or 8
I hope as soon as possible technical assistance.
bye
First thing I’d check is you’re not being subject of a DDOS attack, or have system > Watchdog set to monitor an IP that may be going offline, rebooting your router.
If that’s not the case, first thing to do is:
1.- Upgrade CCRs to latest Bugfix release, 6.30.4 as of today
2.- Upgrade CCRs firmware (system > routerboard) to the latest (firmware is delivered together with the routeros npk). reboot.
3.- Make an export of the CCRs configuration.
4.- Reset configuration, no-defaults, skip backup, keep users.
5.- open a terminal, maximize it and import the .rsc file verbosely:
/import file-name=your_export_file.rsc verbose=yes
Make sure there are no errors.
Check if CPU spikes persist.
If that`s the case, next thing I’d do is a netinstall, repeating the previous procedure from step 4.
If the CPU spikes / reboots persist, have a look at CCR files after a reboot; you may have supout.rif files automatically generated by the watchdog (that’s the default setting); if that’s the case, email support attaching that supout file.
If there is no supout file, check the watchdog settings to enable automatic supout generation (the most useful as they’re generated at the time of the “problem”), or generate one manually from Winbox > Generate supout.rif