From: SHARMA,MOHIT (HP-Germany,ex1) (mohit.sharma@hp.com)
Date: Wed Jun 18 2003 - 17:34:17 GMT-3
HI All,
A correction here, just tested it also on the lab, and found that only the
virtual link inherits the authectication type and you have to configure
either the NULL authentication or the passwords on both sides to make it
work.
Also even if you enable authentication in the area and dont enable it on the
interfaces it works. But if you use NULL or passwords make sure to configure
it on both sides of the link.
Also the passwords can be different for different links.
Hope this helps.
Smiles,
Mohit.
-----Original Message-----
From: SHARMA,MOHIT (HP-Germany,ex1) [mailto:mohit.sharma@hp.com]
Sent: Wednesday, June 18, 2003 9:34 PM
To: 'Nathan Chessin'; ccielab@groupstudy.com
Subject: RE: ospf area authentication
Hi Nate,
Thats right, if you have authentiation enabled for the whole area all the
interfaces automatically inherit this.''
If U want to disbale the authetication for a particular interface or the
Virtual Link you have to use the commad-
area <transit-area id> virtual-link <router-id> authentication null on both
sides.
-----Original Message-----
From: Nathan Chessin [mailto:nchessin@cisco.com]
Sent: Wednesday, June 18, 2003 9:19 PM
To: ccielab@groupstudy.com
Subject: ospf area authentication
Hi All.
When configuring area authentication in OSPF, it looks to me like interfaces
that are put in that area are inheriting the authentication by default.
For instance, if I have simple authentication in area 245 enabled, and I
have a bri interface in that area, it will inherit the simple authentication
parameters even though I don't explicitly state "ip ospf authentication" or
"ip ospf authentication-key xxxxx"
Is this correct thinking and correct behavior. Oh, and I do have a virtual
link transiting area 245 with simple authentication as well.
Any help?
Thanks,
Nate
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:00 GMT-3