• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Upgrade help

Scheduled Pinned Locked Moved Problems Installing or Upgrading TNSR Software
4 Posts 1 Posters 2.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    lastactionhero
    last edited by May 6, 2021, 10:54 PM

    Trying to upgrade (from Netgate TNSR Version: tnsr-v21.03-2) by redeploying home+lab tnsr-v21.03.1-1. It failed when I tried to restore my config. The documentation is a bit sparse, but when I "redeploy", besides just simply installing tnsr, do I actually need to assign dataplane interfaces as well? Then restore the config? Or will restoring the config do everything? Please let me know if you need more then what is posted below. Thank you.

    [admin@tnsr01 ~]$ sudo journalctl -xe
    -- Subject: Unit clixon-backend.service has begun start-up
    -- Defined-By: systemd
    -- Support: https://access.redhat.com/support
    -- 
    -- Unit clixon-backend.service has begun starting up.
    May 06 15:40:52 tnsr01 clixon_backend[5793]: Version: tnsr-v21.03.1-1
    May 06 15:40:52 tnsr01 clixon_backend[5793]: Build timestamp: Mon Apr 26 13:57:07 2021 CDT
    May 06 15:40:52 tnsr01 clixon_backend[5793]: This TNSR instance is not configured for package updates.
    May 06 15:40:52 tnsr01 clixon_backend[5793]: For information see 'show documentation'
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: master: Preserved capabilities
    May 06 15:40:52 tnsr01 clixon_backend[5793]: master: Preserved capabilities
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: Skipping interface 1, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: Skipping interface 2, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: Skipping interface 1, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: Skipping interface 2, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: Skipping interface 3, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: Skipping interface 4, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: ignoring interface tap1
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: ignoring interface tap2
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: ignoring interface tap3
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: vpp_init_linux_cp: ignoring interface tap4
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: Skipping interface 3, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: Skipping interface 4, pair already exists
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: ignoring interface tap1
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: ignoring interface tap2
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: ignoring interface tap3
    May 06 15:40:52 tnsr01 clixon_backend[5793]: vpp_init_linux_cp: ignoring interface tap4
    May 06 15:40:52 tnsr01 clixon_backend[5793]: Ignoring unattached interface Guest
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: Ignoring unattached interface Guest
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: Ignoring unattached interface Spectrum
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: Ignoring unattached interface Starlink
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: Ignoring unattached interface Transit
    May 06 15:40:52 tnsr01 clixon_backend[5793]: Ignoring unattached interface Spectrum
    May 06 15:40:52 tnsr01 clixon_backend[5793]: Ignoring unattached interface Starlink
    May 06 15:40:52 tnsr01 clixon_backend[5793]: Ignoring unattached interface Transit
    May 06 15:40:52 tnsr01 vnet[5569]: nat: plugin enabled
    May 06 15:40:52 tnsr01 clixon_backend[5793]: tnsr_err_report: 292: Config error: delete:vpp/nat_glob_opts/-, OK, NAT44 enabling failed
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: tnsr_err_report: 292: Config error: delete:vpp/nat_glob_opts/-, OK, NAT44 enabling failed
    May 06 15:40:52 tnsr01 clixon_backend[5793]: May  6 15:40:52: clixon_backend: 5793 Terminated retval:-1
    May 06 15:40:52 tnsr01 clixon_backend[5793]: clixon_backend: 5793 Terminated retval:-1
    May 06 15:40:52 tnsr01 systemd[1]: clixon-backend.service: Control process exited, code=exited status=255
    May 06 15:40:52 tnsr01 systemd[1]: clixon-backend.service: Failed with result 'exit-code'.
    -- Subject: Unit failed
    -- Defined-By: systemd
    -- Support: https://access.redhat.com/support
    -- 
    -- The unit clixon-backend.service has entered the 'failed' state with result 'exit-code'.
    May 06 15:40:52 tnsr01 systemd[1]: Failed to start Clixon backend.
    -- Subject: Unit clixon-backend.service has failed
    -- Defined-By: systemd
    -- Support: https://access.redhat.com/support
    -- 
    -- Unit clixon-backend.service has failed.
    
    1 Reply Last reply Reply Quote 0
    • L
      lastactionhero
      last edited by May 7, 2021, 6:24 AM

      So as the error implies, it's a NAT issue. I needed to remove my NAT's before the config would succesffully import.

      Needed to remove the following before my backup.xml would restore successfully.

      nat global-options nat44 endpoint-dependent true
      nat global-options nat44 forwarding true
      nat global-options nat44 enabled true
      
      and
      
      interface WAN
      no ip nat 
      
      interface LAN
      no ip nat
      

      Once imported, I proceeded to add NAT commands back in as above. TNSR can access out to internet and can also access internal LAN resources, but my LAN cannot get to internet. My LAN can reach TNSR fine. I will troubleshoot more on this.

      1 Reply Last reply Reply Quote 0
      • L
        lastactionhero
        last edited by May 7, 2021, 6:33 AM

        Ah I just reviewed my notes...forgot nat pool interface wan. Will add this and im sure itll work.

        1 Reply Last reply Reply Quote 0
        • L
          lastactionhero
          last edited by May 7, 2021, 4:23 PM

          That was it.

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received