reboot and failover - cause ssl vpn - HF 1370

Alberto

Hi,

After about 45 days of stability a 6600 rebooted (see trace below)

Machine firmware: 6.5.4.7-83n - HFGEN6-1249

Open Ticket 43573050.

Support has already released me the HFGEN6-1370 hotfix (6.5.4.7-83n - HFGEN6-1370-9n)

I haven't updated yet

Could I know detail about HF 1370?

Also support tells me after updating to do this:

"Once you have upgraded to the provided Hotifx, you need to go to the SSL VPN-> Server Settings page, you will find this option" Enable Compression Control Protocol (CCP) for SSL VPN connections: "You need to disable it."

Because?

What does this relate to the GEN6-1285 issue ? (Mobile Connect clients running on Android and Chromebook are able to connect to the firewall, but traffic is not forwarded.)

Thanks a lot !

Alberto

- trace on restart ---

log core 13: number of exceptions 1, time 21/10 22: 04: 30.144: event status logged 0, failure 0 - critical events recorded 491, failure 0

************************************************** ****************

DP Stored Side: Core 13: Unhandled exception.

Firmware version: SonicOS Enhanced 6.5.4.7-83n - HFGEN6-1249-1n

Directory: /depot-141227-6/NG/SonicOS/WorkSet/6.5.4/release_6.5.4.7-83n_HFGEN6-1249/m2/target/oct_mips64/sw_octeon6600-cp-base

cause: tlb load / fetch

************************************************** ****************

 r0 ($ 00): 0x0000000000000000 s0 ($ 16): 0x000000006f7ee1d0

 a ($ 01): 0x000000000000003d s1 ($ 17): 0x000000003df6b528

 v0 ($ 02): 0x0000000000000000 s2 ($ 18): 0xffffffffe893df98

 v1 ($ 03): 0x0000000000000000 s3 ($ 19): 0x0000000000000008

 a0 ($ 04): 0xffffffffe893dfa0 s4 ($ 20): 0xffffffffe893df96

 a1 ($ 05): 0x0000000016043fd8 s5 ($ 21): 0x0000000000000008

 a2 ($ 06): 0x0000000000004000 s6 ($ 22): 0x000000006f7ee19c

 a3 ($ 07): 0x000000001603fff8 s7 ($ 23): 0x0000000000000017

 t0 ($ 08): 0xffffffffe893dfc0 t8 ($ 24): 0x0000000000000001

 t1 ($ 09): 0x0000000000000000 t9 ($ 25): 0x00000000102cb6c8

 t2 ($ 10): 0x0000000010644240 k0 ($ 26): 0x000000001032d318

 t3 ($ 11): 0x00000000000003c5 k1 ($ 27): 0xffffffff80001190

 t4 ($ 12): 0x0000000000000001 mo ($ 28): 0x000000001201b940

 t5 ($ 13): 0xffffffff853f0000 sp ($ 29): 0x000000001601f910

 t6 ($ 14): 0x000000000b4c51fc s8 ($ 30): 0x0000000000004000

 t7 ($ 15): 0x000000000b4c51f6 ra ($ 31): 0x000000001035b118

   COP0_CAUSE: 0x0000000040008008

   COP0_STATUS: 0x00000000501004e3

  COP0_BADVADDR: 0x0000000016040000

    COP0_EPC: 0x000000001052d6fc

************************************************** ****************

DP 13 core stack trace:

 0x101ce790

 0x101ce034

 0x101c5804

 0x101c55a0

 0x105004c8

 0x1035b448

 0x1035b118

 0x1052d6fc

Alberto

see my option

Micah

Hello @Alberto, I'm sorry to hear about this inconvenience. Let me reach out internally to get an answer to your question.

Kind Regards,

Micah

Hello @Alberto. I reached out to our support team and they are working internally to provide you with an updated assessment via the case.

Kind Regards,