Kdump

asternos kdump this chapter provides examples on how to use netconf to manage kdump tools configurations on asternos devices note this feature is only supported on cx306p, cx308p, cx532p and cx732 series platforms modify kdump tools configurations note we can configure kdump enablement, reserved memory space, and the threshold for the number of dump files request example to modify kdump tools configurations via edit config \<config> \<top> \<kdump> \<enabled>true\</enabled> \<memory>0m 2g 256m,2g 4g 512m,4g 8g 618m,8g 800m\</memory> \<num dumps>3\</num dumps> \</kdump> \</top> \</config> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid 4c8c8f28 72ba 47c8 9b9e adcd932c19db"> \<ok/> \</rpc reply> get kdump tools configurations request example to retrieve kdump tools configurations via get config with subtree filter \<filter type="subtree"> \<top> \<kdump/> \</top> \</filter> response example \<data> \<top> \<kdump xmlns="http //asterfusion com/ns/yang/asternos kdump"> \<enabled>true\</enabled> \<memory>0m 2g 256m,2g 4g 512m,4g 8g 618m,8g 800m\</memory> \<num dumps>3\</num dumps> \</kdump> \</top> \</data> get dump files of kdump tools show kernel core dump and dmesg files request example to get dump files of kdump tools via rpc show kdump files \<show kdump files/> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid 2c0ad596 f0f7 475c 9dd0 de1f17dcfc0a"> \<data xmlns="http //asterfusion com/ns/yang/asternos kdump"> kernel core dump files kernel dmesg files \ /var/crash/202506261458/kdump 202506261458 /var/crash/202506261458/dmesg 202506261458 \</data> \</rpc reply> get logs of kdump tools note show last n lines of lastest kernel dmesg file or specific dmesg file by default, we will print the last 10 lines of the most lastest kernel dmesg file in addition, we can also specify a particular dmesg file to print and the number of lines to display request example to get logs of kdump tools via rpc show kdump logging \<show kdump logging/> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid\ eaaaaeb0 637b 4b70 ab8a 2f01f68014cf"> \<data xmlns="http //asterfusion com/ns/yang/asternos kdump"> \[ 409 482325] entry syscall 64 after hwframe+0x6e/0xd8 \[ 409 487406] rip 0033 0x7fafbff34340 \[ 409 491004] code 40 00 48 8b 15 c1 aa 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 80 3d a1 32 0e 00 00 74 17 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 48 89 \[ 409 509857] rsp 002b 00007ffe2d74d308 eflags 00000202 orig rax 0000000000000001 \[ 409 517467] rax ffffffffffffffda rbx 0000000000000002 rcx 00007fafbff34340 \[ 409 524637] rdx 0000000000000002 rsi 000055a76e5a59a0 rdi 0000000000000001 \[ 409 531807] rbp 000055a76e5a59a0 r08 0000000000000007 r09 0000000000000073 \[ 409 538986] r10 0000000000000000 r11 0000000000000202 r12 0000000000000002 \[ 409 546163] r13 00007fafc0010760 r14 0000000000000002 r15 00007fafc000b9e0 \[ 409 553339] \</task> \</data> \</rpc reply> get kdump logs of the specified file note show last n lines of lastest kernel dmesg file or specific dmesg file by default, we will print the last 10 lines of the most lastest kernel dmesg file in addition, we can also specify a particular dmesg file to print and the number of lines to display request example to get logs of the specified file via rpc show kdump logging \<show kdump logging> \<filename>dmesg 202506261458\</filename> \<lines>20\</lines> \</show kdump logging> response example \<rpc reply xmlns="urn\ ietf\ params\ xml\ ns\ netconf\ base 1 0" message id="urn\ uuid 613002e1 6ad4 42d3 afc8 704304fa8031"> \<data xmlns="http //asterfusion com/ns/yang/asternos kdump">\[ 409 441175] ? syscall exit to user mode+0x1e/0x40 \[ 409 445995] ? do syscall 64+0x61/0xb0 \[ 409 449768] ? ptep set access flags+0x2e/0x40 \[ 409 454240] ? wp page reuse+0x60/0x70 \[ 409 458013] ? auditd test task+0x39/0x50 \[ 409 462050] ksys write+0x6b/0xf0 \[ 409 465385] do syscall 64+0x55/0xb0 \[ 409 468982] ? handle mm fault+0xdb/0x2d0 \[ 409 473023] ? do user addr fault+0x1b0/0x550 \[ 409 477415] ? exit to user mode prepare+0x44/0x1f0 \[ 409 482325] entry syscall 64 after hwframe+0x6e/0xd8 \[ 409 487406] rip 0033 0x7fafbff34340 \[ 409 491004] code 40 00 48 8b 15 c1 aa 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 80 3d a1 32 0e 00 00 74 17 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 48 89 \[ 409 509857] rsp 002b 00007ffe2d74d308 eflags 00000202 orig rax 0000000000000001 \[ 409 517467] rax ffffffffffffffda rbx 0000000000000002 rcx 00007fafbff34340 \[ 409 524637] rdx 0000000000000002 rsi 000055a76e5a59a0 rdi 0000000000000001 \[ 409 531807] rbp 000055a76e5a59a0 r08 0000000000000007 r09 0000000000000073 \[ 409 538986] r10 0000000000000000 r11 0000000000000202 r12 0000000000000002 \[ 409 546163] r13 00007fafc0010760 r14 0000000000000002 r15 00007fafc000b9e0 \[ 409 553339] \</task> \</data> \</rpc reply>