Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 25 subscribers
  • Views 4766 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

red tunnel compression changes

onward

SFOS 17.0.6 MR-6

is it necessary to download a new provisioning file from the server xg and recreate the RED interface on the client xg after enabling or disabling compression on the RED interface on the server xg?



This thread was automatically locked due to age.
  • 0

    answering my own question - a brief RED network connectivity interruption happens and the client XG logs entries below after enabling compression on the server XG RED interface so it looks like it's not necessary to download a new provisioning file after enabling.  A way to query active RED interface connection details would be useful.

     

    XG210_WP03_SFOS 17.0.6 MR-6# /log/syslog.log 

    Apr 26 08:36:24 (none) user.err kernel: [2580549.497118] reds4: RX decryption failed
    Apr 26 08:41:34 (none) user.info kernel: [2580859.828922] reds4: switched to compression algorithm 'lzo'
    Apr 26 08:41:34 (none) user.debug kernel: [2580859.896822] id 4, peerid 0, ifindex 9
    Apr 26 08:41:36 (none) daemon.info red2ctl[2363]: Overflow happened on reds4:0
    Apr 26 08:41:36 (none) daemon.info red2ctl[2363]: Missing keepalive from reds4:0, disabling peer 1.1.1.1
    Apr 26 08:41:39 (none) daemon.info red2ctl[2363]: Received keepalive from reds4:0, enabling peer 1.1.1.1