Cannot access server or ping on WS-X6708-10GE

[thornick]

Connected server on a  tenGigabitEthernet interface simple configuration setup

switchport

switchport access vlan 201

end

for server connection.  Connected with Fibre.

The interface is up and up but cannot ping server?

[John Blakley]

Does the vlan have an svi associated to it or do you have another host in the same vlan that you're trying to ping? Are you eying to ping the host from the switch?

Sent from Cisco Technical Support iPhone App

[thornick]

This switch is our core server switch so yes there are other devices on that vlan and we can ping and access them.  This connection is the tengigabitethernet connection, first one that is connected to a server, the other tengigabitethernet connections are connected to our other switches throughout the building.  I cannot ping the server from the switch or any other location.  The interface is showing up and up.  What do you mean does the vlan have an svi associated to it?

[John Blakley]

A L3 SVI has an address associated to it. For example, if you had vlan 50, you could have:

int vlan50

ip address 192.168.50.5

All clients in vlan 50 would have their default gateway set to 192.168.50.5. I'm not sure if that's the case in your scenario though. Otherwise, can you pass any traffic at all? Browse the web?

[Parvesh Paliwal]

can you find any MAC association or arp entries ?

Can you provide us the "show access-llist" output?

Regards,

[thornick]

Yes it is associated to our vlan for servers.  There is no access-list on this switch.   There is not a mac address in the arp table, since I cannot ping the server.  For server connections on 10GE interface is there any special commands that need to be in place globally or on the interface...this is the interface configuration at this time.  There is a vlan 201 configured with an ip and that is what all of our servers use.  The 1gig server connections have no problems.

interface TenGigabitEthernet4/1

switchport

switchport access vlan 201

switchport mode access

[oshincisco]

Nick,

Do "show vlan 201" just to make sure traffic is being forwarded out the giga port. If that is clear.

Check the status of your media converter in use between the switch and the server.

If there is a cut your F link will be down on the media converter but show up/up on the switch.

Lets know the outcome.

The problem is a fibre cut.

Sent from Cisco Technical Support iPhone App

[Leo Laohoo]

Connected server on a  tenGigabitEthernet interface simple configuration setup
switchport
 switchport access vlan 201
end

Can you please post the output to the command "sh interface Ten "?

[goatnetworking]

When this happens to me, it is almost always a misconfiguration on the server side. The switch is setup as an access port and the Server is setup as a Trunk port.

Have your server admin make sure their NIC is setup as an access port to match your port.

If that doesn't fix it, double check your IP's.

Scape

[thornick]

sh int

tenGigabitEthernet4/1 is up, line protocol is up (connected)

  Hardware is C6k 10000Mb 802.3, address is e05f.b97a.de48 (bia e05f.b97a.de48)

  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 10Gb/s, media type is 10Gbase-SR

  input flow-control is on, output flow-control is off

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 1w5d, output 00:00:06, output hang never

  Last clearing of "show interface" counters 1w3d

  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 2000 bits/sec, 3 packets/sec

     795 packets input, 157924 bytes, 0 no buffer

     Received 789 broadcasts (779 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 0 multicast, 0 pause input

     0 input packets with dribble condition detected

     4039151 packets output, 384264134 bytes, 0 underruns

     0 output errors, 0 collisions, 2 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier, 0 PAUSE output

     0 output buffer failures, 0 output buffers swapped out

[goatnetworking]

Thornick, did you ever get this figured out?

I'm interested in what the problem and solution was.