see email below. I wasn't really expecting this, now I don't know whether I should cry or laugh.....
-pavel p.s. yes I know that it is against netiquette to post private emails (apologies to Vijay), but this one really got me On Wed, Mar 3, 2010 at 2:00 PM, vijay gore <[email protected]> wrote: > Dear Sir, > > i have read your mail, > > i am giving you all the details, > > please help out me this, > > > ****Router***#show beep session > Total Active BEEP channels: 0 > Channel limit: 0 (0 = unlimited) > Beep sessions: > ****Router***# > ======================================================================================= > ======================================================================================= > ****Router***#show idb bits > ^ > % Invalid input detected at '^' marker. > ****Router***#show idb ? > all List of all IDBs, including deleted IDBs > | Output modifiers > <cr> > ****Router***#show idb all > Maximum number of Software IDBs 300. In use 22. > HWIDBs SWIDBs > Active 15 15 > Inactive 7 7 > Total IDBs 22 22 > Size each (bytes) 2904 1256 > Total bytes 63888 27632 > Type SIdx Idx St,O,Sh HDel Interface Name (subblocks) > -------------------------------------------------------- > H 1 1 U,U,R . FastEthernet0 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 2 2 U,U,R . FastEthernet1 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 3 3 A,D,R . BRI0 (HW SB CDP(5), HW ISDN(4), Serial(3)) > H 4 4 A,D,R . BRI0:1 (HW SB CDP(5), HW ISDN(4), Serial(3)) > H 5 5 A,D,R . BRI0:2 (HW SB CDP(5), HW ISDN(4), Serial(3)) > H 6 6 U,I,R . FastEthernet2 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 7 7 U,I,R . FastEthernet3 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 8 8 U,I,R . FastEthernet4 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 9 9 U,I,R . FastEthernet5 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 10 10 U,I,R . FastEthernet6 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 11 11 U,I,R . FastEthernet7 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 12 12 U,I,R . FastEthernet8 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 13 13 U,I,R . FastEthernet9 (HW SB CDP(5), MAC ADDR(2), > Ether(1)) > H 14 14 U,D,R . Vlan1 (MAC ADDR(2), Ether(1)) > H 15 15 U,D,R . Tunnel662 > S 1 2 U . FastEthernet0 (SW CDP(6), ARP IDB Subblock(5), > Dynamic DNS Updates(4), NetBIOS(2), KEEPALIVE(1)) > S 2 3 U . FastEthernet1 (SW CDP(6), ARP IDB Subblock(5), > Dynamic DNS Updates(4), NetBIOS(2), KEEPALIVE(1)) > S 3 6 U . BRI0 (SW CDP(6), NetBIOS(2), KEEPALIVE(1)) > S 4 7 U . BRI0:1 (SW CDP(6), NetBIOS(2), SW FIB PENDING > EVENT(10002), KEEPALIVE(1)) > S 5 8 U . BRI0:2 (SW CDP(6), NetBIOS(2), SW FIB PENDING > EVENT(10002), KEEPALIVE(1)) > S 6 10 U . FastEthernet2 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 7 11 U . FastEthernet3 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 8 12 U . FastEthernet4 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 9 13 U . FastEthernet5 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 10 14 U . FastEthernet6 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 11 15 U . FastEthernet7 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 12 16 U . FastEthernet8 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 13 17 U . FastEthernet9 (SW CDP(6), PortMan(3), > NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 14 20 U . Vlan1 (TCP(10003), ARP IDB Subblock(5), Dynamic > DNSUpdates(4), NetBIOS(2), SW FIB PENDING EVENT(10002), KEEPALIVE(1)) > S 15 21 U . Tunnel662 (Dynamic DNS Updates(4), NetBIOS(2), > KEEPALIVE(1)) > Key: SIdx=Sort Index, Idx=hw_if_index or if_number > St=Current State, O=Old State, Sh=Shadow State > HDel=HWIDB Deleted State > A=Admindown, D=Down, G=Going Down, I=Init > R=Reset, T=Testing, U=Up, X=Deleted > ****Router***# > ================================================================================================================== > =================================================================================================================== > > ****Router***#show arap console 0 > ^ > % Invalid input detected at '^' marker. > ****Router***#show ara > > ============================================================================== > ============================================================================== > On Wed, Mar 3, 2010 at 4:08 PM, Pavel Skovajsa <[email protected]> > wrote: >> >> Hello Vijay, >> >> Hope you are doing great! >> >> My name is Pavel and I will be assisting you with your Service Dequest >> 999666999. I am sending this e-mail as an initial point of contact and >> so that you can contact me if you need to. >> >> Problem Description >> >> As I have understood it till now, the issue is that you have issues >> with too much logging into your network system. >> >> I would like to tell you that the command you configured is used for >> tunneling purposes in your routing tables. Here is the actual meaning >> and purpose of the same: >> >> Tunneling tunnels the packets into a tunnel. >> >> Now, for the issue that you are experiencing, there can be >> inconsitency between what you are seeing and what is actually >> happening in reality - hence the tunnel logging issue. >> >> >> To help isolate the issue, send me details of the following: >> >> 1. Please provide me with the output of “show beep session”. >> 2. Please provide me with the output of "show idb bits" >> 3. Please provide me with the output of "show arap console 0" >> 4. Please let me know the purpose for enabling this command. >> >> Action Plan: >> >> 1. *You* will gather various random information and *I* will try to >> understand the issue >> 2. Research and provide information. >> 3. Goto 1 until fixed. >> >> Don't hesitate to contact me anytime for any issue and concern, but >> only if non-relevant to this matter. I have read/accepted your service >> dequest and would like to retain ownership to avoid any delays in >> resolving your issue. If you do not respond within 3 days I will >> simply close your case due to your ignorance. >> >> -pavel skovajsa >> Senior Junior Troubleshooting Architect/Manager >> >> p.s. alternatively you can ignore everything above and take a look at >> >> http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094690.shtml >> >> On Tue, Mar 2, 2010 at 7:53 AM, vijay gore <[email protected]> wrote: >> > Dear Tem, >> > >> > provide the solution, line protocol frequently up & Down, >> > >> > >> > *Mar 1 06:18:16.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet6, changed state to down >> > *Mar 1 06:18:16.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet5, changed state to down >> > *Mar 1 06:18:16.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet4, changed state to down >> > *Mar 1 06:18:16.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet3, changed state to down >> > *Mar 1 06:18:16.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet2, changed state to down >> > *Mar 1 06:18:24.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > Tunnel***, changed state to up >> > *Mar 2 05:17:21.210: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet0, changed state to down >> > *Mar 2 05:17:23.634: %TUN-5-RECURDOWN: Tunnel*** temporarily disabled >> > due >> > to recursive routing >> > *Mar 2 05:17:24.634: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > Tunnel***, changed state to down >> > *Mar 2 05:17:31.210: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > FastEthernet0, changed state to up >> > *Mar 2 05:18:24.634: %LINEPROTO-5-UPDOWN: Line protocol on Interface >> > Tunnel***, changed state to upCMD: >> > _______________________________________________ >> > cisco-nsp mailing list [email protected] >> > https://puck.nether.net/mailman/listinfo/cisco-nsp >> > archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
