How to provide all information to effectively resolve a technical issue with 2N OS device

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.

 

In case you have found some issue with 2N OS device, please report it to Technical Support. If you do not have access information, contact your account manager.
Or you can report your issue by creating a ticket - here. The reported issue should contain the following information:

  1.  Describe us the issue in a close detail, so that we will be able to replicate the behavior at 2N Tech Support.
    1. Send us the description of the LAN topology, NATs, IP addresses, etc.

    2.  If your issue can be clearly visible or heard e.g. LED blinking or bad sound quality, please take a picture or record a video (e.g. on a phone) and send us this behavior.

      You can attach it to the e-mail or upload it to e.g. WeTransfer, Dropbox, Google Drive and send us the download link.

  2. Know the Device Information

    The serial number and the current FW version of your 2N OS device.
    It is highly recommended to use always the newest FW version available on 2N web page - here2N_Clip_technical_issue_serial_number 
  3. Backup the Configuration

    Send us the current configuration of the device - in the pictures below there is shown how to do that.2N_Clip_technacl_issue_configuration_backup  
  4. Capture the Wireshark trace

    Catch the Wireshark trace on 2N OS device. Here first of all activate the capturing by "Start" button, make a call and deactivate the capturing by "Stop" button. Then download hiptrace.pcap file and send it to the support. Because the buffer for trace is limited, it is really necessary to start the trace right before you will make a test call.

    2N_Clip_technical_issue_Packet_capture

  5. Capture an internal Syslog on 2N OS device. 

    If 2N Tech support asks you for a Syslog they usually want the setting that is shown in the picture below. Unlike in Wireshark trace the buffer is not limited by size but time.
    Please set the Required Saving Time + Severity level according to 2N Tech support needs.
    After setting press the "Start" button and the Syslog will automatically stop after the time you defined in Required Saving Time, then save the syslog.txt file and send it to us.2N_Clip_technical_issue_syslog 

    6. Capture an external Syslog on 2N OS device.

        The external syslog is often use to capture syslog messages immediately after rebooting the device which often can't be done by internal Syslog.
        Please fill the Severity Level according to 2N Tech support needs. You will need a syslog server where the messages from the device will be sent.
        Set the Server Address in our example we use 192.168.1.15 - IP Address of a PC where SyslogWatcher is installed

    2N_Clip_technical_issue_send_syslog 

    7. Using SyslogWatcher - download here

          Start the server - it will take a few seconds until you see any messages

    2N_Clip_technical_issue_StartServer 
    Stop server - press after you are done with capturing
    Export - press this button to export messages to file
    Export Settings - Choose the time from/to according to what 2N Tech support demands (1h, 24h)
    Custom files (CSV/XML/TXT/JSON/etc.) - type of file

    2N_Clip_technical_issue_StopServer

    Export folder - choose path to save the file
    Filename - name of the file (in default it is date of Syslog capturing) -> export the file with .txt suffix and send it to us
    2N_Clip_technical_issue_export_folder 

Was this page helpful?