Yes, Junos has the capability of "Totally Stubby Area" in OSPF
Have a look,
[edit protocols ospf]
root# set area 0.0.0.0 stub ?
Possible completions:
<[Enter]> Execute this command
default-metric Metric for the default route in this stub area
no-summaries Don't flood summary LSAs into this stub area
summaries Flood summary LSAs into this stub area
Pipe through a command
[edit protocols ospf]
root# set area 0.0.0.0 stub no-summaries
Sunday, November 9, 2008
Saturday, November 8, 2008
Disabling LMIs on Cisco Router
Once I was asked to diable LMIs on an interface of a Cisco router connected to FR cloud, I found it so simple,
Interface serial1/0
no keepalive
Wow! Its done, and the very important thing is that, through this I can get rid of "Zero" mappings as well.
Interface serial1/0
no keepalive
Wow! Its done, and the very important thing is that, through this I can get rid of "Zero" mappings as well.
Tip for Interface-based NAT on Juniper's Screen OS
The following are some rules and limitations on interface-based NAT:
1. The egress interface must be bound to the Untrust zone.
2. When a user-defined zone is bound to the ingress interface with NAT
enabled, that user-defined security zone must be defined on a different
virtual router than the Untrust zone.
3. Interface-based NAT will not work between the Trust zone and a userdefined
defined zone.
4. Interface-based NAT does not work on an interface bonded to the
Untrust zone, even though it can be enabled.
1. The egress interface must be bound to the Untrust zone.
2. When a user-defined zone is bound to the ingress interface with NAT
enabled, that user-defined security zone must be defined on a different
virtual router than the Untrust zone.
3. Interface-based NAT will not work between the Trust zone and a userdefined
defined zone.
4. Interface-based NAT does not work on an interface bonded to the
Untrust zone, even though it can be enabled.
Subscribe to:
Posts (Atom)