AudioCodes Mediant MSBR Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Network Router
  5. Mediant MSBR Series
  6. Troubleshooting manual

AudioCodes Mediant MSBR Series Troubleshooting Manual

Multi-service business routers
Hide thumbs Also See for Mediant MSBR Series:
Table of Contents

Advertisement

Quick Links

Download this manual
Configuration Note
Multi-Service Business Routers Product Series
Mediant MSBR
Troubleshooting
Version 7.2

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes Mediant MSBR Series

Summary of Contents for AudioCodes Mediant MSBR Series

  • Page 1 Configuration Note Multi-Service Business Routers Product Series Mediant MSBR Troubleshooting Version 7.2...

  • Page 3: Table Of Contents

    Configuration Note Contents Table of Contents Introduction ......................7 Capturing Packets ....................9 Capturing Data-CPU on Physical Interfaces ............9 2.1.1 Changing the Debug File Destination Target ............10 2.1.2 Viewing Currently Configured Capture ..............10 2.1.3 Debugging Capture Physical using WinSCP Example ..........11 2.1.4 Capturing Data-CPU on Physical Interface Example ..........12 2.1.5...
  • Page 4 Troubleshooting the MSBR This page is intentionally left blank. Configuration Note Document #: LTRT-40386...
  • Page 5 Please contact your local recycling authority for disposal of this product. Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our website at https://www.audiocodes.com/services-support/maintenance-and-support.
  • Page 6 40386 Updates to the document template. Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our website at https://online.audiocodes.com/documentation-feedback. Configuration Note...

  • Page 7: Introduction

    Configuration Note 1. Introduction Introduction This document describes the basic system configuration for AudioCodes Multi-Service Business Routers (MSBR), using the CLI management interface. Version 7.2 Troubleshooting the MSBR...
  • Page 8 Troubleshooting the MSBR This page is intentionally left blank. Configuration Note Document #: LTRT-40386...

  • Page 9: Capturing Packets

    Configuration Note 2. Capturing Packets Capturing Packets The MSBR has built-in packet capturing capabilities used for debugging the MSBR and providing an instant overview of current network traffic. Two types of packet capturing can be performed on the MSBR: Physical – on the wire packet capturing ...

  • Page 10: Changing The Debug File Destination Target

    Troubleshooting the MSBR Source Description eth-lan vlan4001 Defines internal link between Data and Voice-CPUs only. only eth-lan all-int- Defines all internals links between Data and Voice-CPUs, and LAN voip Ethernet interfaces. eth-lan all-int- Defines all internals links between Data and Voice-CPUs only. voip only wifi-lan Defines the Wi-Fi interface.

  • Page 11: Debugging Capture Physical Using Winscp Example

    Configuration Note 2. Capturing Packets 2.1.3 Debugging Capture Physical using WinSCP Example The following example captures data from the Ethernet interface on the LAN and WAN sides and sends it to the PC using SSH-WINSCP (Windows Secure CoPy) software.  To capture physical packets using WinSCP: Activate SSH on MSBR;...

  • Page 12: Capturing Data-Cpu On Physical Interface Example

    Troubleshooting the MSBR 2.1.4 Capturing Data-CPU on Physical Interface Example This example captures data from the Ethernet interface on the LAN side and sends it to a USB device: # debug capture data physical eth-lan Interface eth-lan was added to the debug capture rules Use start command in order to start the debug capture # debug capture data physical eth-wan Interface eth-wan was added to the debug capture rules...

  • Page 13: Capturing Data On Logical Interfaces

    Configuration Note 2. Capturing Packets Capturing Data on Logical Interfaces The “debug capture data interface” command is used to debug traffic on a specific interface, filtering specific protocols (ICMP/IP/UDP/TCP) and a specific host. You may choose to view the packets on the terminal or upload to TFTP. Use the following command to capture traffic on a logical interface: Table 2-5: Capturing Traffic on Logical Interface Command Command...

  • Page 14: Looking Inside The Vpn Ipsec Tunnel Example

    Troubleshooting the MSBR The following example captures data from the Ethernet interface on the WAN side and sends it to a TFTP server: # debug capture data interface gigabitethernet 0/0 proto all host any port any tftp-server 192.168.0.50 ......2.2.2 Looking Inside the VPN IPSec Tunnel Example The "debug capture data interface"...

  • Page 15: Capturing Voice On Physical Interfaces

    Configuration Note 2. Capturing Packets Capturing Voice on Physical Interfaces Voice-CPU has two interfaces: LAN switch  VLAN 4001 connected to the Data-CPU: This interface is monitored using the  “debug capture data physical eth-lan vlan4001” command. Sometimes you may need to debug or analyze traffic coming from the internal LAN switch directly to the Voice-CPU, by-passing the Data-CPU.

  • Page 16: Capturing Voice On Logical Interfaces

    Troubleshooting the MSBR Capturing Voice on Logical Interfaces The “debug capture voip interface” command provides the capability of monitoring specific logical interfaces (e.g. VLANs). The same concept is applied in the “debug capture voip interface” as in the “debug capture data interface”...

  • Page 17: Gathering Data-Cpu

    RMX refers to the Data-CPU. Debugging Data-CPU There are two methods for debugging Data-CPU: Reviewing serial logs of the last five MSBR runs  Enabling direct access to the Data-CPU serial interface without using AudioCodes'  proprietary serial cable 3.1.1 Reviewing Serial Logs A cyclic buffer of 50K runs and logs of the MSBR-Data-CPU serial interface is stored.

  • Page 18: Obtaining The Data-Cpu Log Files Using Winscp

    Troubleshooting the MSBR The Data-CPU log files can be obtained by using either one of the following options: WinSCP  USB Storage  CLI Commands  3.1.1.1 Obtaining the Data-CPU Log Files using WinSCP The following procedure describes how to obtain the Data-CPU log files using WinSCP. ...

  • Page 19: Obtaining Data-Cpu Logs Using Cli Commands

    Configuration Note 3. Gathering Data-CPU 3.1.1.3 Obtaining Data-CPU Logs Using CLI commands The Data-CPU log files can be obtained by running the following CLI commands: debug rmx-serial list-log  debug rmx-serial read-log <log number>  # debug rmx-serial read-log 8 [000000.658] lo: Dropping NETIF_F_SG since no checksum feature.

  • Page 20: Accessing The Data-Cpu Serial Interface

    Accessing the Data-CPU Serial Interface Live debugging of Data-CPU sometimes requires direct access to its serial interface. AudioCodes has a proprietary serial cable for direct connectivity of both serial consoles - the yellow and red cable. The “debug rmx-serial tap” command provides the same capability without using any cable.

  • Page 21: Resetting History

    Configuration Note 4. Resetting History Resetting History This feature provides historical reasons and date/time of the last 20 resets that occurred on the MSBR. This information provides a complete picture of MSBR problems. By looking at the reset history, you can distinguish whether the problem is located in the VoIP-CPU, Data- CPU or there is faulty power cord.
  • Page 22 Troubleshooting the MSBR This page is intentionally left blank. Configuration Note Document #: LTRT-40386...

  • Page 23: Cpu And Memory Utilization History

    Configuration Note 5. CPU and Memory Utilization History CPU and Memory Utilization History The MSBR device has an option to view the CPU history. The MSBR device includes two CPUs: Voice CPU and Data CPU. You can view both CPU utilization and memory utilization history for both of these CPUs.
  • Page 24 Troubleshooting the MSBR 111111111111111111111111111111111111111111111111111111111111 545455455545554545454554545554555545554544555545444554555555 |************************************************************ +------------------------------------------------------------ 123456789111111111122222222223333333333444444444455555555556 012345678901234567890123456789012345678901234567890 Data Cpu Utilization in last 60 seconds 111111111111111111111111111111111111111111111111111111111111 555444555555666555555444555445555555555555555554443335555555 |************************************************************ +------------------------------------------------------------ 123456789111111111122222222223333333333444444444455555555556 012345678901234567890123456789012345678901234567890 Mediant 500 - MSBR# Configuration Note Document #: LTRT-40386...

  • Page 25: Cpu Memory Utilization History

    Configuration Note 5. CPU and Memory Utilization History CPU Memory Utilization History The same method that is used for CPU utilization history is used for memory utilization history. The following commands show memory utilization values: Command Description show system utilization history Show data memory utilization history.
  • Page 26 Troubleshooting the MSBR 123456789111111111122222222223333333333444444444455555555556 012345678901234567890123456789012345678901234567890 Mediant 500 - MSBR# Configuration Note Document #: LTRT-40386...

  • Page 27: Debugging Usb Devices

    Configuration Note 6. Debugging USB Devices Debugging USB Devices AudioCodes provides several USB debug utilities for debugging USB devices. If the 3G/4G USB modem fails to connect to the MSBR, the following information needs to be provided: USB Hardware Information ...

  • Page 28: Providing Software Driver Definitions

    Troubleshooting the MSBR Providing Software Driver Definitions Run the "Debug usb-3g devices" command to provide a deeper look into the software driver definitions. debug usb-3g devices Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1 Alloc= 7/800 us ( 1), #Int= 2, #Iso= Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs=...
  • Page 29 Configuration Note 6. Debugging USB Devices Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 3 Spd=480 MxCh= 0 Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= Vendor=0011 ProdID=7788 Rev= 1.03 Manufacturer=SAMSUNG Product=Flash Disk SerialNumber=12345678 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-...

  • Page 30: Providing At Modem Command Responses

    Providing AT Modem Command Responses AudioCodes provides the capability for recording AT modem commands between the USB device and the AudioCodes router. This capability allow us to analyze the 3G device in case of unsupported devices. debug usb-3g serial-trace cli...

  • Page 31: Debugging Wi-Fi

    The "show data dot11radio other-ap" command provides the ability to look up all Wi-Fi access points around the MSBR. # show data dot11radio other-ap SSID BSSID CHAN RATE Audc-QA 00:0b:86:35:72:74 AudioCodes 00:0b:86:35:72:70 Guest-AudC 00:0b:86:35:72:71 AudcPBX 00:0b:86:35:72:73 AudioCodes 00:0b:86:2d:38:90 54M 24:0...
  • Page 32 Troubleshooting the MSBR 228 tx frames with no ack marked 9061 rx failed 'cuz of bad CRC 50229 PHY errors 45421 phy ofdm timing 4784 phy cck timing 24 phy cck restart 699 periodic calibrations 1 switched default/rx antenna Antenna profile: [0] tx 0 rx [1] tx...
  • Page 33 Configuration Note 7. Debugging Wi-Fi 0 tx aggr old frames requeued 0 filtered aggr packet 0 tx aggr: last sub-frame failed 0 tx aggr: h/w long retries 0 tx aggr: h/w short retries 0 tx aggr: tx timer expired 0 rx pkts 0 rx aggregated packets 0 rx bars 0 rx non qos-data frames...
  • Page 34 Troubleshooting the MSBR This page is intentionally left blank. Configuration Note Document #: LTRT-40386...

  • Page 35: Sending Service Requests

    Configuration Note 8. Sending Service Requests Sending Service Requests When a Service Request is issued, specific information must be provided so that appropriate analysis could be performed on the problem. Please provide the output from the following commands: show system version ...
  • Page 36 Website: https://www.audiocodes.com/ ©2019 AudioCodes Ltd. All rights reserved. AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, User Management Pack, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One Voice and CloudBond are trademarks or registered trademarks of AudioCodes Limited.

Table of Contents