If the nat cause the problem (although I doubt it), perhaps you can try by shutting the nat of after clearing all cache entries before hand ? use the clear ip nat trans * command to do that, or you can also specify certain host if you like.
One fenomena that I heard in 6500, is that when you define a vlan and there is nothing on physically at that VLAN (no physical machine connected), the vlan interface is regarded as off. I don't know if this is true or not, but that's what I've heard. Regards Donny >From: "Patrick Ramsey" >Reply-To: "Patrick Ramsey" >To: [EMAIL PROTECTED] >Subject: Re: Multilayer Switching [7:24595] >Date: Mon, 29 Oct 2001 21:56:41 -0500 > >IF you have that vlan off then the ip nat inside statement is useless I >would assume. If infact the ip nat inside statement is doign something, I >would assume the vlan to be on... > >Is this logic incorrect? OR do I not understand you question? > >-Patrick > > >>> "Thomas N." 10/29/01 08:45PM >>> >Anyone have any problem turning on VLAN interfaces that are running on NAT >protocol? I couldn't turn VLAN on my 6509 that has "ip nat inside" >statement. Thanks! > >Thomas N. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=24609&t=24595 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
