Network interface module (NIM) log
The network interface module log is located in nim_log.
It contains trace information about the activities of the network interface modules (NIMs), which are processes used by the Topology Services daemon to monitor each network interface. These logs need to be collected before they wrap or are removed.
There will be a separate log for each NIM that is running on the system, which equates to one for each adapter being monitored locally by Topology Services. Each NIM will keep four instances of its log – the current and three previous (nim_log.001, nim_log.002, and nim_log.003). When the current log file is full, log file .003 is overwritten by .002, .002 is overwritten by .001, and .001 is overwritten by the current log file to make room for a new one.
- A connection with a given adapter is established.
- A connection with a given adapter is closed.
- A daemon has sent a command to start or stop heartbeating.
- A daemon has sent a command to start or stop monitoring heartbeats.
- A local adapter goes up or down.
- A message is sent or received.
- A heartbeat from the remote adapter has been missed
Data in the NIM log is in English only. The format of each message is:
time-of-day messageAt default logging levels, an instance of the NIM log file will wrap when the file reaches approximately 200 KB. Normally, it takes about 10 minutes to fill an instance of the log file. Since three instances are kept, the NIM log files need to be saved within 30 minutes of when the adapter-related problem occurred. If a higher level of NIM tracing has been enabled under the direction of the IBM® Support Center, the wrapping size of the NIM logs will automatically be increased to accommodate the extra logging and could grow as large as 800 KB, depending on the debugging level.