336 | | |
337 | | |
338 | | __Before:__ |
339 | | {{{ |
340 | | xx |
341 | | }}} |
342 | | __After:__ |
343 | | {{{ |
344 | | yy |
345 | | }}} |
| 335 | The Amarisfot MME system has several logging levels. By default, it will cap- |
| 336 | ture all connect and disconnect messages, as well as any eNodeB heartbeats. If |
| 337 | desired, one can turn on verbose logging which will capture much more data, |
| 338 | such as any and all GTP packets coming/going, as well as the standard mes- |
| 339 | sages. Be cautious when using verbose logging, as it generates log files that are |
| 340 | quite large in size, and can easily fill up the rotating log files very quickly. Syslog |
| 341 | will be set up to allow users who are not currently logged into the physical EPC |
| 342 | to view/parse log files themselves. Amarisoft places log files into |
| 343 | [[BR]] |
| 344 | `/var/log/mme.log` |
| 345 | [[BR]] |
| 346 | |