RE: Real world Scnario...Need Help...Lossing $$$

From: Scott Morris (smorris@ipexpert.com)
Date: Fri Dec 07 2007 - 15:33:23 ART


What SUP are you running on the 6500's? how much memory? What does "sh
proc cpu" look like? Are you getting any log messages on your switch (e.g.
are you SURE you aren't getting full routes or trying to?)

Scott

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of ccie
ccie
Sent: Friday, December 07, 2007 12:42 PM
To: Cisco certification
Subject: Real world Scnario...Need Help...Lossing $$$

Hi Tech Lover,

                                              Juniper R1
Juniper J2 <---- Connect to BB
router as well as this router face the internet world.
                                                  | | / / \ \
| | <--- Each EBGP
session with hello 2 Hold 6 running on each physical link. OPSF is also
running on same link.
        Server Iron LB ======= 6500 sw1 ---ibgp---
6500 sw2 ====Server Iron LB
                                                  | | / / \ \
| | <--- Physical
link are L2 port channel
                                             4948 sw1 4948 sw2

  This is an scnario, where i need your help. We cant run EBGP on loopback
due to some architecturial concern. Problem with only EBGP session on core
sw2.

Our EBGP session only on core switch 2 with Juniper 1 & 2 flap with few
irregular hours. IBGP session between core switch 1 & 2 never flap. We are
get hell lot of traffic. This site run multicast ( but sure that could not
be problem) servers, web server, DB server etc. Core sw1 session are always
stable. OSPF neighborship on both switch to Juniper BB router is up snce
more than 1 yrs.

1. BW on link is not high.
2. CPU show 99% spike when BGP falp. CPU cause BGP flap i think so. ( I dont
think BGP flap can cause of CPU spike.)
3 Core switch is not having full BGP route.

( i tried to put ip nabr protocol-discover on EBGP link & session flap due
to me, i revert back in few sec to save my job)

Suggest an troubleshooting step. As usual TAC is already open & CISCO taking
too much time.

Regards,
Mike



This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:29 ARST