wrote:
> Dana wrote:
> > <> wrote in message
> > news: oups.com...
> > > Any suggestions on this? I have been trying to figure this out for
> > > days and have not found an answer. Any help is appreciated.
> >
> > What have you already done to try and fix it?
>
> That would seem unusual.
>
> To troubleshoot the coms you need to detail where
> you are pinging from, the IP address/mask of the source,
> the target address. To start.
>
> If all other communications is working I guess
> it could be the box.
>
> Is logging enabled?
>
> post
> sh log ! anything interesting?
> sh mem ! first few lines
Logging is enabled but shows nothing at all other than a couple
interfaces going down and up again but wouldn't be related to this as
they occured a few days ago and the interfaces are up/up now anyway:
#show log
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level debugging, 64331 messages logged
Monitor logging: level debugging, 3 messages logged
Buffer logging: level debugging, 64331 messages logged
File logging: disabled
Trap logging: level debugging, 64335 message lines logged
Logging to 65.220.38.82, 64245 message lines logged
Log Buffer (4096 bytes):
down
..Sep 11 16:56:33.164 est: %LINEPROTO-5-UPDOWN: Line protocol on
Interface FastEthernet0/18, changed state to down
..Sep 11 16:57:40.681 est: %LINK-3-UPDOWN: Interface FastEthernet0/18,
changed state to up
..Sep 11 16:57:41.681 est: %LINEPROTO-5-UPDOWN: Line protocol on
Interface FastEthernet0/18, changed state to up
..Sep 11 16:57:41.961 est: %LINK-3-UPDOWN: Interface FastEthernet0/10,
changed state to up
..Sep 11 16:57:42.081 est: %LINK-3-UPDOWN: Interface FastEthernet0/12,
changed state to up
..Sep 11 16:57:42.961 est: %LINEPROTO-5-UPDOWN: Line protocol on
Interface FastEthernet0/10, changed state to up
..Sep 11 16:57:43.081 est: %LINEPROTO-5-UPDOWN: Line protocol on
Interface FastEthernet0/12, changed state to up
I am trying to ping from a host on Vlan 9, 192.168.34.44. This ping is
initiated on the switch itself. I have also tried pinging the host
from the switch which also does not work. The host has the same subnet
as the switch, 255.255.255.240. I've verified the host is on an
interface that is set up in Vlan 9 with switchport access vlan9 and
switchport mode access. Both host and switch have the correct duplex
and speed (100, full). This host is on interface fa 0/9:
interface FastEthernet0/9
switchport access vlan 9
switchport mode access
no ip address
duplex full
speed 100
There are no access lists on the host that would prevent it from
replying, in fact, I do see replys coming from the host using tcpdump
on the host.
I have tried a similar test on one of the other Vlans. Same
configuration except for the ip addresses and Vlan number. I had the
same problem. I cannot ping anywhere from the switch itself either.
A show mem gives this output:
#show mem
Head Total(b) Used(b) Free(b) Lowest(b)
Largest(b)
Processor 9E4A0C 56724980 4654060 52070920 51102188
51800768
I/O 80000000 8388608 936436 7452172 7202332
7384300
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC
what
009E4A0C 0000001504 00000000 009E5018 001 ------- ------- 0018E6E8
List Elements
009E5018 0000005004 009E4A0C 009E63D0 001 ------- ------- 0018E718
List Headers
009E63D0 0000009000 009E5018 009E8724 001 ------- ------- 001A7FB8
Interrupt Stack
..
..
..
Thanks!
Similar Threads
