1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RV082 Network Service Detection - Load balance - Problem

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by kopija, Oct 12, 2007.

  1. kopija

    kopija LI Guru Member

    Hi all,

    I have a big issue with Network Service Detection not bringing WAN1 (ixp1) Down when it suspends that connection (with firmware 1.3.7beta and 1.3.5 - didn't try out 1.3.3.5 cause I need Bandwidth Management supported by these fw's) .

    I have attached pictures of Syslog (rv
    082_syslog.jpg) saying that ixp1 has been suspended, but in Log->System Statistic it says Connected (rv082_PortStatus.jpg)??! IXP1 got private IP from cable modem (192.168.100.10) but cannot ping 87.250.33.1 as designated for Network Service Detection for that interface (rv082_NetDet.jpg) which should mean that IF is Down (not Disconnected).

    When i do traceroute to any other network not bound to WAN2 interface - which is UP - I get lost packets, cannot route to anything, cannot surf... etc.

    When i manually Disconnect IXP1 - I can route, ping and surf through WAN2.
    If i Connect IXP1 again... problem reappears. Syslog doesn't say anything.


    Can someone help me get Network Service Detection working properly?


    Best Regards,
    Kopija





     

    Attached Files:

  2. d__l

    d__l Network Guru Member

    I use 1.3.3.8 and have no problems with Network Service Detection in Load Balance mode. The RV082 has dual DSL lines and when the PPPoE connection is lost on one, the router switches traffic to the second line without problems. Now there may be a delay to the switch as the router finishes stepping through the retry counter (2) and retry timeout (30) delays. I have the router checking the Default Gateway.
     
  3. kopija

    kopija LI Guru Member

    I have reverted firmware to 1.3.3.5 and now everything works fine. Some testing should be performed with new fw version 1.3.5 an 1.3.7 because Network Service Detection seems not to change routes properly.

    Best Regards
    Kopija
     
  4. Toxic

    Toxic Administrator Staff Member

    did you reset the firmware to factory defaults when you upgraded to v1.3.7 firmware?
     
  5. kopija

    kopija LI Guru Member

    No, I didn't, cause it says that You don't have to when upgrading. The router reset itself to factory defaults when downgraded to 1.3.3.5.

    Can it be that you have to reset the router to factory defaults even when upgrading?

    This is a litle bit of a problem cause I don't use 192.168.1.0 as default LAN IP range. I have to connect router to PC and change LAN IP range to the range we are using and then again set WAN interfaces bindings and bandwidth priority etc...


    Kopija
     
  6. kopija

    kopija LI Guru Member

    Seems that it Network Detection doesn't work properly when cable modem assigns 192.168.100.x IP to WAN1 rather then sticking to public IP given by provider when there is cable signal.

    When I release WAN1 from 192.168.100.x and leave it at 0.0.0.0 everything reroutes to WAN2.
     

Share This Page