I figured out, that need to create a pool at static nat and assign the pool in a new rule set security nat source pool pl-isp2-27 address xxx.xxx.xxx.27 security nat source rule-set rs1 rule r-MX01 then source-nat pool pl-isp2-27 ------------------------------ ...
Hi, we have configured routing-instances for 2 ISP's One of our Exchange-Server which is configured for static NAT ist not using the IP (xxx.xxx.xxx.27) configured in the static nat configuration. The server is using instead the IP of the SRX (xxx.xxx.xxx.26) ...
What is your experience with this policy that you have applied now? What is actually occurring and showing up in your LSDB? Do you have a term 1 before this term 2? Also you might need an accept-all term after that term 2 if the only terms in this policy ...
Doing it by policy is certainly the way to go, below is the policy to advertise lo0.0 only: # Policy for advertising lo0.0 only: set policy-options policy-statement OSPF-EXPORT term LO0 from interface lo0.0 set policy-options policy-statement OSPF-EXPORT ...
under the interface irb.2 try to turn on the "no-advertise-adjacency-segment" knob and commit it. See if that will take it out of LSDB on the remote end. https://www.juniper.net/documentation/us/en/software/junos/ospf/topics/ref/statement/no-advertise-adjacency-segment-edit-protocols-ospf-interface-level.html ...
Juniper is driving a company-wide initiative to further enhance our customers’ experience. Please tell us how we’re doing via a quick video that will be used for internal Juniper viewing only--none of it will be shared publicly!
Use your phone or laptop. It should take about 5-10 minutes, and you can review and re-record any segment at the click of a button.
Thank you in advance!
New Book. Day One: Migrating to Segment Routing is a highly anticipated migration guide packed with tips and configurations culled from field implementations and production cutovers. Read what you need to think about, your options, and how to do it all with Junos.