Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

Options for the service route:     

  • Local break out
  • Autogenerated ( learn from the other side another SSR )
  • Learn route ( use-bgo-over-svr )
  • Next Peer ( the next peer will decide the routing )

service-routehttps://docs.128technology.com/docs/config_reference_guide/#service-route
Conductor  5.4.1

PCLI

Example for local breakout:        next-hop node1 wan1

service-route
Configuration Attributes
------------------------
bridge-name               EOSVR bridge to forward packets to for the service.
enable-failover           Enable failover across next-hops and service-routes that have this flag set.
generated                 Indicates whether or not the Service Route was automatically generated as a result of STEP topology builder, Conductor,
                          BGP/SVR, or DHCP Relay services.
host                      Packets are passed to the host operating system for processing
name                      An arbitrary, unique name for the service route.
nat-target                The address or fqdn of the server that packets are forwarded to for the service. The destination is natted to this address.
next-hop                  An instance of the nexthop for the service route.
next-peer                 Peer router to forward packets to for the service.
peer                      Peer router to forward packets to for the service.
reachability-detection    Configure Reachability Detection
routing-stack             Packets are passed to the internal routing agent for processing
routing-stack-vrf         VRF in which the internal routing agent will receive the packets
service-name              The name of the service that this service route applies to.
service-route-policy      Service Route Policy that applies to the service route.
use-learned-routes        Use learned (from routing protocols), connected, and static routes.
vector                    Vector name to assign a cost to this service-route.

bridge-name
generated
host
nat-target:   The target address for this service-route.  dest-NAT : replace with DHCP server or DNS server IP address (eg: 8.8.8.8 )
next-hop
next-peer:    list of multiple peers ( like DC ssr )
peer:   like DC ssr
reachability-detection
routing-stack:   ??????  look & use the routing table???
routing-stack-vrf:     ??????
service-name
service-route-policy:  Max session, session rate, packet replication,  water mark Low/High
use-learned-routes:  to also use the RiB ( by default, without SR, the ssr will use the RiB )




service-route  > host

This is used to direct packets to the host operating system of a specified node

>>> Local Linux host / Node!







service-route > next-hoplocal breakout

local breakout
config

    authority

        router  branch1
            name           branch1

            service-route  to_internet_ServRoute
                name          to_internet_ServRoute
                service-name  to_internet

                next-hop      node1 mgmt
                    node-name  node1
                    interface  mgmt
                exit
            exit
        exit
    exit
exit


service-route-policyhttps://docs.128technology.com/docs/config_reference_guide/#service-route-policy








  • No labels