Hi, On Mon, Feb 23, 2026 at 06:02:47PM +0300, Muhammad Atif Jauhar via cisco-nsp wrote: > Thank you both for your feedback. > > Basically, one subnet is for backup environment and other link is for > normal user traffic toward Data center. > > If we use one link most of the bandwidth captured by backup to avoid any > bandwidth issue and slowness faced by users, we acquired one link for only > backup and replication. > > Now want to segregate traffic on both link to avoid any bandwidth issue.
Quite often this can be done by destination (like, "backup server is
in the remote location, on a well-known IP address, so *this* prefix
goes to the left, and will take most of the traffic"). Sometimes not.
B&R traffic tends to be highly asymmetric by nature ("much higher needs
toward the backup storage than vice versa") so getting this direction
sorted out can help a lot with the scenario "backup left, link can be
saturized, rest goes right, sufficient capacity remains".
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
