06-11-2008 03:06 PM - edited 03-05-2019 11:34 PM
hi all,
i have a problem here.
user is on vlan140 with ip address.
user is unable to ping server from his pc.
i am able toping server from user gateway.but when i do extended ping using source ip as user vlan then ping does not work
any help
06-11-2008 03:11 PM
Mahesh
Could you give us a few more details. Are you talking about a L3 switch.
Please provide a few more details.
Jon
06-11-2008 03:22 PM
Hi jon
other users on different vlan can ping it.
this us user gateway
sh ver
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9-M), Version 12.2(18)SXF6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Mon 18-Sep-06 23:59 by tinhuang
Image text-base: 0x40101040, data-base: 0x42D90000
ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-IPSERVICESK9-M), Version 12.2(18)SXF6, RELEASE SOFTWARE (fc1)
06-11-2008 03:25 PM
Mahesh
Could you check what Jorge has suggested.
In addition this is a 6500 switch. Are both devices attached to this switch.
From the user PC can you ping it's default gateway ie. the vlan 40 L3 interface on the 6500.
Can you confirm that the vlan 40 L3 is up/up ie.
sh ip int brief
Jon
06-11-2008 03:27 PM
hi all,
vlan 140 is up up
Vlan140 is up, line protocol is up
Hardware is EtherSVI, address is 0009.7bdb.7000 (bia 0009.7bdb.7000)
Description: Enterprise App servers Vlan 1
Internet address is 192.168.140.3/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 11/255
Encapsulation ARPA, loopback not set
Keepalive not supported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 33w0d
Input queue: 4/75/267/1 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 44561000 bits/sec, 5230 packets/sec
5 minute output rate 2577000 bits/sec, 1601 packets/sec
L2 Switched: ucast: 14670755639 pkt, 5923725805904 bytes - mcast: 60679425 pkt, 4541744037 bytes
L3 in Switched: ucast: 64138066876 pkt, 53901304943452 bytes - mcast: 445 pkt, 56558 bytes mcast
L3 out Switched: ucast: 30433489078 pkt, 7794757558948 bytes mcast: 0 pkt, 0 bytes
64241720527 packets input, 53908641785717 bytes, 0 no buffer
Received 88392599 broadcasts (471 IP multicasts)
0 runts, 0 giants, 4 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
30456889718 packets output, 7796272959172 bytes, 0 underruns
0 output errors, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
06-11-2008 03:29 PM
Hi all,
Server is on differet network
06-11-2008 03:25 PM
Hi all,
this is info from user gateway
ping
Protocol [ip]:
Target IP address: 172.31.41.82
Repeat count [5]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: vlan140--user vlan
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 172.31.41.82, timeout is 2 seconds:
Packet sent with a source address of 192.168.140.3
..................
Success rate is 0 percent (0/18)
oktulesfr2#x
able toping it without extended command
ping 172.31.41.82
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.31.41.82, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/16 ms
06-11-2008 03:30 PM
Mahesh
If vlan 140 is a user vlan why does it have a description of "Enterprise App servers Vlan 1"
Anyway, where is 172.31.41.82 - is the device connnected to the 6500 switch or is it connected to another device ?
Jon
06-11-2008 03:37 PM
hi jon
server is connected to another device at different location
06-11-2008 03:39 PM
Hi jon,
traceroute from user gateway to server
traceroute 172.31.41.82
Type escape sequence to abort.
Tracing the route to houtsm4300a.williams.com (172.31.41.82)
1 (192.168.253.13) 4 msec
(192.168.253.5) 0 msec
(192.168.253.13) 0 msec
2 (172.16.128.9) 0 msec
(172.16.128.13) 0 msec
(172.16.128.9) 0 msec
3 (172.16.100.2) 12 msec 16 msec 12 msec
4 (172.16.51.9) 12 msec 12 msec 12 msec
5 (172.31.41.82) 16 msec 12 msec 16 msec
06-11-2008 03:41 PM
Mahesh
You need to make sure that all those routers that your traceroute is going through know how to route back to vlan 140 subnet. It looks like some router along the way or the final destination does not know how to route back to the 192.168.40.x subnet.
Jon
06-11-2008 03:45 PM
hi jon,
how can i check that
this is traceroute from user PC to server IP
tracert 172.31.41.82
Tracing route to [172.31.41.82]
over a maximum of 30 hops:
1 [192.168.140.3]
2 [192.168.253.5]
3 [172.16.128.9]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
06-11-2008 03:48 PM
Mahesh
You need to go to the next router in the traceroute and see why it doesn't have a route back to 192.168.140.3. That is what is happening, not all the routers in the path to 172.31.42.82 know about the 192.168.140.x network.
So you have to go router by router until they all know about the 192.168.140.x subnet.
Jon
06-11-2008 04:02 PM
hi jon,
how can i check that should i log onto next hopd router and do extended ping???
06-11-2008 04:05 PM
Mahesh
You need to log onto each router in the path and try to ping 192.168.140.3. If it doesn't work you need to work out why it is not in the routing table.
Jon
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: