System Logs and Error Messages
435
ProSAFE Gigabit Quad WAN SSL VPN Firewall SRX5308
Multicast/Broadcast Logs
WAN Status
This section describes the logs generated by the WAN component. If there are several ISP
links for Internet connectivity, the VPN firewall can be configured either in auto-rollover or
load balancing mode.
Load Balancing
When the WAN mode is configured for load balancing, all 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 other WAN links that are active.
This section describes the logs generated when the WAN mode is set to load balancing.
Auto-Rollover
When the WAN mode is configured for auto-rollover, the primary link is active, and the
secondary link acts only as a backup. When the primary link goes down, the secondary link
becomes active only until the primary link comes back up. The VPN firewall monitors the
status of the primary link using the configured WAN failure detection method.
Table 115.
System logs: multicast/broadcast
Message
Jan 1 07:24:13 [SRX5308] [kernel] MCAST-BCAST IN=WAN OUT=SELF SRC=
192.168.1.73 DST=192.168.1.255 PROTO=UDP SPT=138 DPT=138
Explanation
•
This multicast or broadcast packet is sent to the device from the WAN network.
•
For other settings, see
Table
106
on page
431.
Recommended action
None
Table 116.
System logs: WAN status, load balancing
Message
Dec 1 12:11:27 [SRX5308] [wand] [LBFO] Restarting WAN1_
Dec 1 12:11:31 [SRX5308] [wand] [LBFO] Restarting WAN2_
Dec 1 12:11:35 [SRX5308] [wand] [LBFO] WAN1(UP), WAN2(UP)_
Dec 1 12:24:12 [SRX5308] [wand] [LBFO] WAN1(UP), WAN2(DOWN)_
Dec 1 12:29:43 [SRX5308] [wand] [LBFO] Restarting WAN2_
Dec 1 12:29:47 [SRX5308] [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.
Messages 4, 5, and 6: These messages show that one of the WAN links is down,
and that restarting the WAN link does not resolve the situation. At this point, all the
traffic is directed through the WAN that is up.
Recommended action
None