Obtaining Data-Cpu Logs Using Cli Commands - AudioCodes Mediant MSBR Series Troubleshooting Manual

Configuration Note
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.
[000000.667] isa bounce pool size: 16 pages
[000000.674] physmap flash device: 4000000 at 1bc00000
[000000.683] phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-
bit bank
[000000.694]
[000000.702] phys_mapped_flash: CFI does not contain boot bank
location. Assuming top.
[000000.715] number of CFI chips: 1
[000000.720] cfi_cmdset_0002: Disabling erase-suspend-program due
to code brokenness.
[000000.733] cmdlinepart partition parsing not available
[000000.742] RedBoot partition parsing not available
[000000.750] u32 classifier
[000000.755]
[000000.760] NET: Registered protocol family 2
[000000.784] IP route cache hash table entries: 2048 (order: 2,
16384 bytes)
[000000.795] IP route PBR cache hash table entries: 2048 (order:
2, 16384 bytes)
[000000.808] TCP established hash table entries: 8192 (order: 4,
65536 bytes)
[000000.820] TCP bind hash table entries: 8192 (order: 4, 65536
bytes)
[000000.831] TCP: Hash tables configured (established 8192 bind
8192)
[000000.841] TCP reno registered
[000000.846] IPv4 over IPv4 tunneling driver
Version 7.2
Amd/Fujitsu Extended Query Table at 0x0040
OLD policer on
19
3. Gathering Data-CPU
Troubleshooting the MSBR