From: Paul Borghese (pborghese@xxxxxxxxxxxxxx)
Date: Sun Jun 17 2001 - 15:10:06 GMT-3
No I need someone from the TAC to send me the header. That way we can see
who the receipient is - if this is actually happening. Remember we have not
had confirmation.
Paul
----- Original Message -----
From: "Theodore TZEVELEKIS" <theodore_tzevelekis@yahoo.com>
To: "Paul Borghese" <pborghese@groupstudy.com>
Sent: Sunday, June 17, 2001 2:04 PM
Subject: RE: OSPF authentication
> Here's what I received Paul.
> And here's the header of the one I received... but I guess you need the
> header of my mail as it was received by cisco, not this one...
>
> X-Apparently-To: theodore_tzevelekis@yahoo.com via web3905.mail.yahoo.com;
> 17 Jun 2001 07:29:24 -0700 (PDT)
> X-Track: -10
> Received: from sj-msg-core-1.cisco.com (171.71.163.11)
> by mta444.mail.yahoo.com with SMTP; 17 Jun 2001 07:29:23 -0700 (PDT)
> Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com
[171.69.11.130])
> by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f5HETNh11890
> for <theodore_tzevelekis@yahoo.com>; Sun, 17 Jun 2001 07:29:23 -0700 (PDT)
> Received: from maildude.cisco.com (localhost [127.0.0.1])
> by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id f5HETQ122971
> for <theodore_tzevelekis@yahoo.com>; Sun, 17 Jun 2001 07:29:26 -0700 (PDT)
> Received: from asteroid.cisco.com (asteroid.cisco.com [171.70.170.217])
> by maildude.cisco.com (8.9.3/8.9.1) with ESMTP id HAA19738
> for <theodore_tzevelekis@yahoo.com>; Sun, 17 Jun 2001 07:24:17 -0700 (PDT)
> Received: (eparser@localhost) by asteroid.cisco.com (8.8.6
> (PHNE_14041)/CISCO.SERVER.1.2) id HAA08852; Sun, 17 Jun 2001
07:29:22 -0700
> (PDT)
> Date: Sun, 17 Jun 2001 07:29:22 -0700 (PDT)
> From: tac@cisco.com
> Message-Id: <200106171429.HAA08852@asteroid.cisco.com>
> X-Authentication-Warning: asteroid.cisco.com: eparser set sender to
> tac@cisco.com using -f
> To: theodore_tzevelekis@yahoo.com
> Reply-to: tac@cisco.com
> Subject: Re: OSPF authentication
>
> If you need more info, I work for the cisco TAC so I can ask the guys in
> charge of tac@cisco.com to look into it.
> Let me know.
>
> Cheers,
> Theo
>
>
> -----Original Message-----
> From: tac@cisco.com [mailto:tac@cisco.com]
> Sent: Sunday, June 17, 2001 4:29 PM
> To: theodore_tzevelekis@yahoo.com
> Subject: Re: OSPF authentication
>
>
> Dear Cisco Customer,
>
> Thank you for your email to tac@cisco.com Unfortunately we did not
> receive enough information to process your technical support request.
> Please make sure that your original email remains attached below by
> using the reply function on your email to respond. Please complete
> and validate all of the required fields highlighted with * on the
> following form. We are unable to open a case without this information.
>
> REQUIRED INFORMATION
> * CONTACT NAME: Theodore TZEVELEKIS
> * CONTACT PHONE NUMBER:
> * CONTACT EMAIL ADDRESS: theodore_tzevelekis@yahoo.com
> * CONTRACT #:
> * SERIAL #: Mismatch
> * PRODUCT TYPE (Model Number):
> * SOFTWARE VERSION:
> * COMPANY NAME:
> * EQUIPMENT LOCATION (Address):
> * BRIEF PROBLEM DESCRIPTION:
>
> ADDITIONAL INFORMATION (if applicable)
> ALTERNATE CONTACT NAME:
> ALTERNATE CONTACT PHONE:
> PICA I.D.:
> ON SITE PHONE:
> PAGER #:
> MOBILE #:
> BUSINESS IMPACT (Low/Medium/High):
>
>
> Once you submit this form and receive a reply with a case number you
> may email attachments containing configurations, show versions, show
> controllers, etc. to attach@cisco.com Use your case number as the
> subject of your email. Please do not send attachments to tac@cisco.com
>
> Customers with valid support contracts may open their own cases via our
> case management tools on www.cisco.com. These tools allow you to
> open cases with increased accuracy. Cases that are opened from the
> web reach our engineers faster than cases opened via other methods.
> Our tools allow you to monitor the case status, upload and attach
> configurations and documentation regarding your case, download software
> updates, and use online troubleshooting and configuration tools. For
> information regarding Cisco.com registration, please see the Registration
> Guide located at http://www.cisco.com/public/regguide.html To access
> the case management tools, please go to http://www.cisco.com , login,
> and then select the "Technical Assistance Center" link under the
> "Service And Support Heading".
>
> Best Regards,
>
> --
> Jeffrey Gomez
> Customer Response Center
> Technical Assistance Center
> Cisco Systems
>
>
> > Hi all,
> >
> > I have the following setup:
> >
> > R1,R2,R4 in area 0 (frame - R4 is hub)
> > R1 - V-L - R6
> >
> > authentication on V-L and area 0
> > R4 and R2 authenticate.
> > V-L authenticates
> > R4 and R1 REFUSE to authenticate.
> > I get on R1:
> >
> > *Mar 1 00:39:03.092: OSPF: Rcv pkt from 137.3.124.4, Serial0/0 :
Mismatch
> > Authe
> > ntication Key - Message Digest Key 1
> >
> > Am I missing something here?
> >
> > Thanks.
> >
> > Theo
> >
> >
> > **************related configs****************
> >
> > R2
> > interface Serial0/0
> > ip address 137.3.124.2 255.255.255.224
> > no ip directed-broadcast
> > encapsulation frame-relay
> > ip ospf message-digest-key 1 md5 cisco
> > ip ospf interface-retry 0
> > ip ospf priority 0
> > no ip mroute-cache
> > no fair-queue
> > frame-relay map ip 137.3.124.1 204
> > frame-relay map ip 137.3.124.4 204
> > no frame-relay inverse-arp
> > !
> > router ospf 100
> > area 0 authentication message-digest
> > redistribute connected metric-type 1 subnets
> > redistribute rip metric-type 1 subnets
> > network 137.3.2.0 0.0.0.255 area 0
> > network 137.3.124.0 0.0.0.31 area 0
> >
> > R4
> > interface Serial0/0
> > ip address 137.3.124.4 255.255.255.224
> > no ip directed-broadcast
> > encapsulation frame-relay
> > ip ospf message-digest-key 1 md5 cisco
> > ip ospf interface-retry 0
> > ip ospf priority 255
> > no ip mroute-cache
> > no fair-queue
> > frame-relay map ip 137.3.124.1 401
> > frame-relay map ip 137.3.124.2 402
> > no frame-relay inverse-arp
> > !
> > router ospf 100
> > area 0 authentication message-digest
> > redistribute connected metric-type 1 subnets
> > network 137.3.4.0 0.0.0.255 area 0
> > network 137.3.40.0 0.0.0.255 area 3
> > network 137.3.124.0 0.0.0.31 area 0
> > neighbor 137.3.124.2
> > neighbor 137.3.124.1
> >
> > R1
> > !
> > interface Serial0/0
> > ip address 137.3.124.1 255.255.255.224
> > no ip directed-broadcast
> > encapsulation frame-relay
> > ip ospf message-digest-key 1 md5 cisco
> > ip ospf priority 0
> > no ip mroute-cache
> > no fair-queue
> > frame-relay map ip 137.3.124.2 104
> > frame-relay map ip 137.3.124.4 104
> > no frame-relay inverse-arp
> > !
> > router ospf 100
> > area 0 authentication message-digest
> > area 4 virtual-link 137.3.6.6 message-digest-key 1 md5 cisco
> > timers spf 10 15
> > redistribute connected metric-type 1 subnets
> > redistribute static metric 1000 metric-type 1 subnets
> > network 137.3.1.0 0.0.0.255 area 0
> > network 137.3.16.0 0.0.0.255 area 4
> > network 137.3.124.0 0.0.0.31 area 0
> > !
> >
> > R6
> > router ospf 100
> > area 0 authentication message-digest
> > area 4 virtual-link 137.3.1.1 message-digest-key 1 md5 cisco
> > area 5 nssa no-summary
> > network 137.3.6.0 0.0.0.255 area 4
> > network 137.3.16.0 0.0.0.255 area 4
> > network 137.3.36.0 0.0.0.255 area 5
> > network 137.3.60.0 0.0.0.255 area 4
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:25 GMT-3