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/
