1. Home
    2. /
  2. Manuals
    3. /
  3. NETGEAR
    4. /
  4. FVX538
    5. /
  5. 42
Page 206 / 240 Scroll up to view Page 201 - 205
ProSafe VPN Firewall 200 FVX538 Reference Manual
B-20
Network Planning for Dual WAN Ports
v1.0, March 2009
VPN Telecommuter: Dual Gateway WAN Ports for Load Balancing
In the case of the dual WAN ports on the gateway VPN firewall, the remote PC client initiates the
VPN tunnel with the appropriate gateway WAN port (i.e., port WAN1 or WAN2 as necessary to
balance the loads of the two gateway WAN ports) because the IP address of the remote NAT router
is not known in advance. The chosen gateway WAN port must act as the responder.
The IP addresses of the gateway WAN ports can be either fixed or dynamic. If an IP address is
dynamic, a fully-qualified domain name must be used. If an IP address is fixed, a fully-qualified
domain name is optional.
Figure B-20
Page 207 / 240
System Logs and Error Messages
C-1
v1.0, March 2009
Appendix C
System Logs and Error Messages
This appendix uses the following log parameter terms.
System Log Messages
This section describes log messages that belong to one of the following categories:
•
Logs generated by traffic that is meant for the device.
•
Logs generated by traffic that is routed or forwarded through the device.
•
Logs generated by system daemons NTP, WAN daemon and others.
System Startup
This section describes log messages generated during system startup.
Table C-1. Log Parameter Terms
Term
Description
[FVX538]
System identifier
[kernel]
Message from the kernel.
CODE
Protocol code (e.g., protocol is ICMP, type 8) and CODE=0 means successful reply.
DEST
Destination IP Address of the machine to which the packet is destined.
DPT
Destination port.
IN
Incoming interface for packet.
OUT
Outgoing interface for packet.
PROTO
Protocol used.
SELF
Packet coming from the system only.
SPT
Source port
SRC
Source IP Address of machine from where the packet is coming.
TYPE
Protocol type
Page 208 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
C-2
System Logs and Error Messages
v1.0, March 2009
Reboot
This section describes log messages generated during system reboot.
NTP
This section describes log messages generated by the NTP daemon during synchronization with
the NTP server.
•
The fixed time and date before NTP synchronizes with any of the servers is:
Thu Jan 01 00:01:52 GMT 1970.
•
The resynchronization interval is governed by the specification defined in:
DOC-00045_Ntp_Spec.pdf.
Table C-2. System Logs: System Startup
Message
Jan 1 15:22:28 [FVX538] [ledTog] [SYSTEM START-UP] System Started
Explanation
Log generated when the system is started.
Recommended Action
None
Table C-3. System Logs: Reboot
Message
Nov 25 19:42:57 [FVX538] [reboot] Rebooting in 3 seconds
Explanation
Log generated when the system is rebooted from the web management.
Recommended Action
None
Table C-4. System Logs: NTP
Message
Nov 28 12:31:13 [FVX538] [ntpdate] Looking Up time-f.netgear.com
Nov 28 12:31:13 [FVX538] [ntpdate] Requesting time from time-f.netgear.com
Nov 28 12:31:14 [FVX538] [ntpdate] adjust time server 69.25.106.19 offset
0.140254 sec
Nov 28 12:31:14 [FVX538] [ntpdate] Synchronized time with time-f.netgear.com
Nov 28 12:31:16 [FVX538] [ntpdate] Date and Time Before Synchronization:
Tue Nov 28 12:31:13 GMT+0530 2006
Nov 28 12:31:16 [FVX538] [ntpdate] Date and Time After Synchronization: Tue
Nov 28 12:31:16 GMT+0530 2006
Nov 28 12:31:16 [FVX538] [ntpdate] Next Synchronization after 2 Hours
Page 209 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
System Logs and Error Messages
C-3
v1.0, March 2009
Login/Logout
This section describes logs generated by the administrative interfaces of the device.
Firewall Restart
This logging is always done.
Explanation
Message1: DNS resolution for the NTP server (time-f.netgear.com)
Message2: request for NTP update from the time server.
Message3: Adjust time by re-setting system time.
Message4: Display date and time before synchronization, that is when
resynchronization started
Message5: Display the new updated date and time.
Message6: Next synchronization will be after the specified time mentioned.
Example: In the above logs the next synchronization will be after two hours.
The synchronization time interval is configurable via the CLI
Recommended Action
None
Table C-5. System Logs: Login/Logout
Message
Nov 28 14:45:42 [FVX538] [login] Login succeeded: user admin from
192.168.10.10
Explanation
Login of user admin from host with IP address 192.168.10.10
Recommended Action
None
Message
Nov 28 14:55:09 [FVX538] [seclogin] Logout succeeded for user admin
Nov 28 14:55:13 [FVX538] [seclogin] Login succeeded: user admin from
192.168.1.214
Explanation
Secure login/logout of user admin from host with IP address 192.168.1.214.
Recommended Action
None
Table C-6. System Logs: Firewall Restart
Message
Jan 23 16:20:44 [FVX538] [wand] [FW] Firewall Restarted
Explanation
Log generated when the firewall is restarted.
This log is logged when firewall restarts after applying any changes in the
configuration.
Recommended Action
None
Table C-4. System Logs: NTP
(continued)
Page 210 / 240
ProSafe VPN Firewall 200 FVX538 Reference Manual
C-4
System Logs and Error Messages
v1.0, March 2009
IPSec Restart
This logging is always done.
WAN Status
This section describes the logs generated by the WAN component. If there are two ISP links for
Internet connectivity, the router can be configured either in Auto Rollover mode or Load
Balancing mode.
Load Balancing
When the WAN mode is configured for Load Balancing, both the WAN ports are active
simultaneously and the traffic is balanced between them. If one WAN link goes down, all the
traffic is diverted to the WAN link that is active.
This section describes the logs generated when the WAN mode is set to Load Balancing.
Table C-7. System Logs: IPSec Restart
Message
Jan 23 16:20:44 [FVX538] [wand] [IPSEC] IPSEC Restarted
Explanation
Log generated when the IPSEC is restarted.
This log is logged when IPSEC restarts after applying any changes in the
configuration.
Recommended Action
None
Table C-8. System Logs: WAN Status, Load Balancing
Message
Dec 1 12:11:27 [FVX538] [wand] [LBFO] Restarting WAN1_
Dec 1 12:11:31 [FVX538] [wand] [LBFO] Restarting WAN2_
Dec 1 12:11:35 [FVX538] [wand] [LBFO] WAN1(UP), WAN2(UP)_
Dec 1 12:24:12 [FVX538] [wand] [LBFO] WAN1(UP), WAN2(DOWN)_
Dec 1 12:29:43 [FVX538] [wand] [LBFO] Restarting WAN2_
Dec 1 12:29:47 [FVX538] [wand] [LBFO] WAN1(UP), WAN2(DOWN)_
Explanation
Message 1 and Message 2 indicate that both the WANs are restarted.
Message 3: This message shows that both the WANs are up and the traffic is
balanced between the two WAN interfaces.
Message 4: This message shows that one of the WAN links is down. At this
point, all the traffic is directed through the WAN which is up
Recommended Action
None

Rate

4 / 5 based on 1 vote.

Popular NETGEAR Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top