Home » Netgear Manuals » Bridges & Routers » Netgear FVS338 » Manual Viewer

Netgear FVS338 FVS338 Reference Manual - Page 178

PPP Logs, System Logs: WAN Status, Auto Rollover

UPC - 606449037197

Add to My Manuals
Save this manual to your list of manuals

Page 178 highlights

FVS338 ProSafe VPN Firewall 50 Reference Manual System Logs: WAN Status, Auto Rollover Message Explanation Recommended Action Nov 17 09:59:09 [FVS338] [wand] [LBFO] WAN1 Test Failed 1 of 3 times_ Nov 17 09:59:39 [FVS338] [wand] [LBFO] WAN1 Test Failed 2 of 3 times_ Nov 17 10:00:09 [FVS338] [wand] [LBFO] WAN1 Test Failed 3 of 3 times_ Nov 17 10:01:01 [FVS338] [wand] [LBFO] WAN1 Test Failed 4 of 3 times_ Nov 17 10:01:35 [FVS338] [wand] [LBFO] WAN1 Test Failed 5 of 3 times_ Nov 17 10:01:35 [FVS338] [wand] [LBFO] WAN1(DOWN), WAN2(UP), ACTIVE(WAN2)_ Nov 17 10:02:25 [FVS338] [wand] [LBFO] WAN1 Test Failed 6 of 3 times_ Nov 17 10:02:25 [FVS338] [wand] [LBFO] Restarting WAN1_ Nov 17 10:02:57 [FVS338] [wand] [LBFO] WAN1 Test Failed 7 of 3 times_ Nov 17 10:03:27 [FVS338] [wand] [LBFO] WAN1 Test Failed 8 of 3 times_ Nov 17 10:03:57 [FVS338] [wand] [LBFO] WAN1 Test Failed 9 of 3 times_ Nov 17 10:03:57 [FVS338] [wand] [LBFO] Restarting WAN1_ The Logs suggest that the fail-over was detected after 5 attempts instead of 3. However, the reason the messages appear as above is because of the WAN state transition logic which is part of the failover algorithm. The above logs can be interpreted as below. The primary link failure is properly detected after the 3rd attempt. Thereafter the algorithm attempts to restart WAN and checks once again to see if WAN1 is still down. This results in the 4th failure detection message. If it is then it starts secondary link and once secondary link is up, secondary link is marked as active. Meanwhile secondary link has failed once more and that results 5th failure detection message. Please note that the 5th failure detection and the message suggesting secondary link is active have the same timestamp and so they happen in the same algorithm state-machine cycle. So although it appears that the failover did not happen immediately after 3 failures, internally, the failover process is triggered after the 3rd failure and transition to secondary link is completed by the 5th failure. The primary link is also restarted every 3 failures till it is functional again. In the above log, primary link was restarted after the 6th failure i.e. 3 failures after the failover process was triggered. Check the WAN settings and WAN failure detection method configured for the primary link. PPP Logs This section describes the WAN PPP connection logs. The PPP type can be configured from the web management. B-6 System Logs and Error Messages v1.0, March 2008

Section	Page
FVS338 ProSafe VPN Firewall 50 Reference Manual	1
Contents	7
About This Manual	13
Conventions, Formats and Scope	13
How to Use This Manual	14
How to Print this Manual	14
Revision History	15
Chapter 1 Introduction	17
Key Features	17
Full Routing on Both the Broadband and Serial WAN Ports	18
A Powerful, True Firewall with Content Filtering	18
Security	18
Autosensing Ethernet Connections with Auto Uplink	19
Extensive Protocol Support	19
Easy Installation and Management	20
Maintenance and Support	20
Package Contents	20
Router Hardware Components	21
Router Front Panel	21
Router Rear Panel	22
Rack Mounting Hardware	23
Factory Default Login	23
Chapter 2 Connecting the FVS338 to the Internet	25
Connecting the VPN Firewall to Your Network	25
Logging in to the VPN Firewall	25
Configuring your Internet Connection	26
Setting the Router’s MAC Address (Advanced Options)	31
Manually Configuring Your Internet Connection	33
Programming the Traffic Meter (if Desired)	36
Configuring the WAN Mode	39
Configuring Dynamic DNS (If Needed)	40
Chapter 3 LAN Configuration	43
Configuring Your LAN (Local Area Network)	43
Using the VPN Firewall as a DHCP Server	43
Configuring Multi-Home LAN IPs	46
Managing Groups and Hosts	48
Creating the Network Database	48
Setting Up Address Reservation	52
Configuring Static Routes	52
Static Route Example	53
RIP Configuration	54
Chapter 4 Firewall Protection and Content Filtering	57
About Firewall Security	57
Using Rules to Block or Allow Specific Kinds of Traffic	57
Services-Based Rules	58
Order of Precedence for Firewall Rules	62
Setting LAN WAN Rules	63
LAN WAN Outbound Services Rules	64
LAN WAN Inbound Services Rules	65
Attack Checks	66
Session Limit	68
Inbound Rules Examples	69
Outbound Rules Example - Blocking Instant Messenger	74
Adding Customized Services	74
Specifying Quality of Service (QoS) Priorities	76
Setting a Schedule to Block or Allow Traffic	77
Setting Block Sites (Content Filtering)	78
Enabling Source MAC Filtering	80
IP/MAC Binding	82
Setting Up Port Triggering	84
Bandwidth Limiting	86
E-Mail Notifications of Event Logs and Alerts	88
Administrator Information	92
Chapter 5 Virtual Private Networking	95
Dual WAN Port Systems	95
Setting up a VPN Connection using the VPN Wizard	96
Creating a VPN Tunnel to a Gateway	96
Creating a VPN Tunnel Connection to a VPN Client	97
IKE Policies	98
IKE Policy Operation	98
IKE Policy Table	98
VPN Policies	99
VPN Policy Operation	100
VPN Policy Table	100
VPN Tunnel Connection Status	101
Creating a VPN Gateway Connection: Between FVS338 and FVX538	102
Configuring the FVS338	102
Configuring the FVX538	105
Testing the Connection	106
Creating a VPN Client Connection: VPN Client to FVS338	106
Configuring the FVS338	107
Configuring the VPN Client	108
Testing the Connection	113
Extended Authentication (XAUTH) Configuration	114
Configuring XAUTH for VPN Clients	115
User Database Configuration	116
RADIUS Client Configuration	117
Manually Assigning IP Addresses to Remote Users (ModeConfig)	119
ModeConfig Operation	120
Setting Up ModeConfig	120
Configuring the ProSafe VPN Client for ModeConfig	124
Certificates	127
Trusted Certificates (CA Certificates)	127
Self Certificates	128
Managing your Certificate Revocation List (CRL)	131
Chapter 6 Router and Network Management	133
Performance Management	133
VPN Firewall Features That Reduce Traffic	133
VPN Firewall Features That Increase Traffic	136
Using QoS to Shift the Traffic Mix	139
Tools for Traffic Management	139
Administration	139
Changing Passwords and Settings	139
Enabling Remote Management Access	141
Using a SNMP Manager	144
Settings Backup and Firmware Upgrade	146
Setting the Time Zone	148
Monitoring the Router	149
Enabling the Traffic Meter	150
Setting Login Failures and Attacks Notification	151
Viewing Port Triggering Status	153
Viewing Router Configuration and System Status	154
Monitoring WAN Ports Status	155
Monitoring VPN Tunnel Connection Status	156
VPN Logs	157
DHCP Log	157
Performing Diagnostics	158
Chapter 7 Troubleshooting	161
Basic Functions	161
Power LED Not On	161
LEDs Never Turn Off	162
LAN or Internet Port LEDs Not On	162
Troubleshooting the Web Configuration Interface	162
Troubleshooting the ISP Connection	164
Troubleshooting a TCP/IP Network Using a Ping Utility	165
Testing the LAN Path to Your Firewall	165
Testing the Path from Your PC to a Remote Device	166
Restoring the Default Configuration and Password	167
Problems with Date and Time	167
Appendix A Default Settings and Technical Specifications	169
Appendix B System Logs and Error Messages	173
System Log Messages	173
System Startup	173
Reboot	174
NTP	174
Login/Logout	175
Firewall Restart	175
IPSec Restart	176
WAN Status	176
Web Filtering and Content Filtering Logs	180
Traffic Metering Logs	182
Unicast Logs	182
FTP Logging	183
Invalid Packet Logging	183
Routing Logs	186
LAN to WAN Logs	187
LAN to DMZ Logs	187
DMZ to WAN Logs	187
WAN to LAN Logs	187
DMZ to LAN Logs	188
WAN to DMZ Logs	188
Appendix C Related Documents	189

Match case Limit results 1 per page

FVS338 ProSafe VPN Firewall 50 Reference Manual

B-6

System Logs and Error Messages

v1.0, March 2008

PPP Logs

This section describes the WAN PPP connection logs. The PPP type can be configured from the

web management.

System Logs: WAN Status, Auto Rollover

Message

Nov 17 09:59:09 [FVS338] [wand] [LBFO] WAN1 Test Failed 1 of 3 times_

Nov 17 09:59:39 [FVS338] [wand] [LBFO] WAN1 Test Failed 2 of 3 times_

Nov 17 10:00:09 [FVS338] [wand] [LBFO] WAN1 Test Failed 3 of 3 times_

Nov 17 10:01:01 [FVS338] [wand] [LBFO] WAN1 Test Failed 4 of 3 times_

Nov 17 10:01:35 [FVS338] [wand] [LBFO] WAN1 Test Failed 5 of 3 times_

Nov 17 10:01:35 [FVS338] [wand] [LBFO] WAN1(DOWN), WAN2(UP),

ACTIVE(WAN2)_

Nov 17 10:02:25 [FVS338] [wand] [LBFO] WAN1 Test Failed 6 of 3 times_

Nov 17 10:02:25 [FVS338] [wand] [LBFO] Restarting WAN1_

Nov 17 10:02:57 [FVS338] [wand] [LBFO] WAN1 Test Failed 7 of 3 times_

Nov 17 10:03:27 [FVS338] [wand] [LBFO] WAN1 Test Failed 8 of 3 times_

Nov 17 10:03:57 [FVS338] [wand] [LBFO] WAN1 Test Failed 9 of 3 times_

Nov 17 10:03:57 [FVS338] [wand] [LBFO] Restarting WAN1_

Explanation

The Logs suggest that the fail-over was detected after 5 attempts instead of 3.

However, the reason the messages appear as above is because of the WAN

state transition logic which is part of the failover algorithm. The above logs can

be interpreted as below. The primary link failure is properly detected after the

3rd attempt. Thereafter the algorithm attempts to restart WAN and checks once

again to see if WAN1 is still down. This results in the 4th failure detection

message. If it is then it starts secondary link and once secondary link is up,

secondary link is marked as active. Meanwhile secondary link has failed once

more and that results 5th failure detection message. Please note that the 5th

failure detection and the message suggesting secondary link is active have the

same timestamp and so they happen in the same algorithm state-machine

cycle. So although it appears that the failover did not happen immediately after

3 failures, internally, the failover process is triggered after the 3rd failure and

transition to secondary link is completed by the 5th failure. The primary link is

also restarted every 3 failures till it is functional again. In the above log, primary

link was restarted after the 6th failure i.e. 3 failures after the failover process

was triggered.

Recommended Action

Check the WAN settings and WAN failure detection method configured for the

primary link.