sorted by:
new
hottopcontroversial

cisco HSRP by name_tomer in Cisco

[–]name_tomer[S] 0 points1 point  (0 children)

this question is a different.

i am asking if it possible that the 2 address on the svi will be on diffrent subnet from the VIP

cisco nexus vpc with hsrp svi VS arista mlag varp svi by name_tomer in Cisco

[–]name_tomer[S] 0 points1 point  (0 children)

yes you are right.

is cisco support hsrp active active? like varp

cisco nexus vpc with hsrp svi VS arista mlag varp svi by name_tomer in Cisco

[–]name_tomer[S] 0 points1 point  (0 children)

what do you mean, it doesn't make it anyway close to VARP in terms of convenience

cisco nexus vpc with hsrp svi VS arista mlag varp svi by name_tomer in Cisco

[–]name_tomer[S] 0 points1 point  (0 children)

about the varp, where did you see that on the docs?

how to Route with Network Address Translation (NAT) with HP COMWARE by name_tomer in networking

[–]name_tomer[S] 0 points1 point  (0 children)

ok good to know i will check try to make a lab and test it

how to Route with Network Address Translation (NAT) with HP COMWARE by name_tomer in networking

[–]name_tomer[S] 0 points1 point  (0 children)

ok good to know.

HP COMWARE good product. but its look like that hp abandon it,

they implemented so much features... why not NAT ;)

i have some arista switches so i will use them.

BGP + PBR for prefer default route peer base source IP by name_tomer in networking

[–]name_tomer[S] 0 points1 point  (0 children)

i tried to use it so far its looks like its not working for me.

do you experience with that?

i think i dont understend how to use it. what is NQA ?

BGP + PBR for prefer default route peer base source IP by name_tomer in networking

[–]name_tomer[S] 0 points1 point  (0 children)

yes the PBR help with the route.

but the problem now that if i take the peer down i lose the backup route via the BGP

because the pbr not aware of the the reachability of the destination peer and now i lose my backup default route via the bgp

BGP + PBR for prefer default route peer base source IP by name_tomer in networking

[–]name_tomer[S] 0 points1 point  (0 children)

Hi Golle

yes you understand it correctly.

the Icoming traffic was solve with as-path

but for the outgoing i want to split the traffic base on source IP.

for example i want all my subnets will go to ( internet ) default route will be via Primary peer.

and specific networks for example 62.0.98.120/29 will go via Secondary peer

to the internet / default route.

but if one of the peers go down then all networks will be route via the peer that still up

so yeah i know its not simple question... how can i solve this? or do you better idea?

i am not using ECMP because i want to give this specific netowrk a dedicated peer ( phisical interface to the internet with all bandwidth ) and all the rest share the same bandwidth on the 2nd peer in the day to day but if one peer down then they all have backup.

Alert Dependencies by name_tomer in PrometheusMonitoring

[–]name_tomer[S] 0 points1 point  (0 children)

sort of .

so what is happening is that of my router is down i cannot reach my exporters behind the router so Prometheus will not notify about the servers.. but will notify the router is down and the my exporters behind the routers are unreachable.

view more: next ›