Symantec 360R Administration Guide - Page 121

Using Syslog, Configuring and verifying SNMP, Logging/Monitoring

Get Symantec 360R - Security Gateway SGS PDF manuals and user guides
UPC - 037648240185
View all Symantec 360R manuals
Add to My Manuals
Save this manual to your list of manuals

Page 121 highlights

Logging, monitoring and updates 121 Managing logging Using Syslog Sending log messages to a Syslog server lets you store log messages for long term. A Syslog server listens for log entries forwarded by the appliance and stores all log information for future analysis. The Syslog server can be on the LAN or WAN, or behind a VPN tunnel. Note: The date and time on messages in the Syslog server are the time they arrived at the Syslog server, and not the time that the appliance logged the event that triggered the log message. To use Syslog See "Log Settings tab field descriptions" on page 155. 1 In the SGMI, in the left pane, click Logging/Monitoring. 2 In the right pane, on the Log Settings tab, under Syslog, in the Syslog Server text box, type the IP address of a host running a standard Syslog utility to receive the log file. 3 Click Save. Configuring and verifying SNMP The appliance supports Simple Network Management Protocol (SNMP) version 1.0 and generates network event alert messages, copies them into an SNMP TRAP or GET with the associated community name, and then sends them to registered SNMP servers. This capability lets the appliance report status information to network-wide SNMP-based management applications. The appliance generates SNMP messages for the following events: ■ Cold start-up of the appliance ■ SGMI authentication failure ■ Ethernet WAN ports up and down ■ No trap when WAN ports comes alive as part of system startup ■ WAN disconnect ■ WAN coming back after a previous disconnect ■ Serial WAN port (PPPoE or Analog) ■ WAN Link up (connected) ■ WAN Link down (disconnected) A GET is a request from the SNMP server for status information from the Symantec Gateway Security 300 Series appliance. The appliance supports all

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
121
Logging, monitoring and updates
Managing logging
Using Syslog
Sending log messages to a Syslog server lets you store log messages for long
term. A Syslog server listens for log entries forwarded by the appliance and
stores all log information for future analysis. The Syslog server can be on the
LAN or WAN, or behind a VPN tunnel.
Note:
The date and time on messages in the Syslog server are the time they
arrived at the Syslog server, and not the time that the appliance logged the
event that triggered the log message.
To use Syslog
See
“Log Settings tab field descriptions”
on page 155.
1
In the SGMI, in the left pane, click
Logging/Monitoring
.
2
In the right pane, on the Log Settings tab, under Syslog, in the Syslog Server
text box, type the IP address of a host running a standard Syslog utility to
receive the log file.
3
Click
Save
.
Configuring and verifying SNMP
The appliance supports Simple Network Management Protocol (SNMP) version
1.0 and generates network event alert messages, copies them into an SNMP
TRAP or GET with the associated community name, and then sends them to
registered SNMP servers. This capability lets the appliance report status
information to network-wide SNMP-based management applications. The
appliance generates SNMP messages for the following events:
■
Cold start-up of the appliance
■
SGMI authentication failure
■
Ethernet WAN ports up and down
■
No trap when WAN ports comes alive as part of system startup
■
WAN disconnect
■
WAN coming back after a previous disconnect
■
Serial WAN port (PPPoE or Analog)
■
WAN Link up (connected)
■
WAN Link down (disconnected)
A GET is a request from the SNMP server for status information from the
Symantec Gateway Security 300 Series appliance. The appliance supports all