A packet that passes through the FB6000 can pass through multiple shapers, for example
- The ingress interface can have a defined shaper
- If the packet is carried via an L2TP tunnel of any sort, there can be an aggregate shaper for the
tunnel (e.g. the broadband carrier). There can also be a class applied to the session
which is an aggregate shaper for an arbitrary group of sessions (often used when reselling broadband).
- When passing through an L2TP tunnel, the session typically has a graph and shaper based on the
circuit ID which is specifc to that session. This is important for bonding multiple sessions as it controls
the levels of traffic sent via each session.
- Obviously traffic could come in via one L2TP tunnel and go back out via another, incurring yet
another set of shapers as above.
- PPPoE links can also have a defined shaper, which is important when bonding multiple
links as it is used to decide how much traffic goes via each link.
- It is possible to create a bonded gateway route where multiple routes exist for the same
target (typically a default gateway) and each route as a speed set, which is itself a shaper.
This is used to control how much traffic goes via each of the bonded routes.
(You simply create more than one
route object with a speed or graph setting).
- The egress interface can have a defined shaper
