F5 Big-IP Cat 6509 connectivity problem

Unanswered Question
Sep 21st, 2007
User Badges:

Hello,


we performed a software upgrade on the Big-IP.

After that the BIG-IP stopped working properly;

obviously the communication to the connected

Cat6509 was not working. tcpdump shows only

outgoing traffic, nothing incoming. The port

on the 6509 is connected and does not show up

any error.


Any idea? Every comment welcome!


Best regards, Snitram

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Edison Ortiz Sat, 09/22/2007 - 09:42
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

Perhaps the port is in err-disabled.


Try disabling/enabling the port from the CLI.


If running CatOS, try, 'set port disable mod/port' - then 'set port enable mod/port'


If running Native IOS, try

interface mod/port

shut

no shut



snitram Sat, 09/22/2007 - 09:46
User Badges:

No, the port is not err-dis. I even tried

to disable and enable. The result is always

that the port is connected, but connectivity

is broken (in tcpdump on the Big-IP I

see only outgoing packets, nothing incoming).

The counters on the 6509 are showing the

same.


Snitram

Edison Ortiz Sat, 09/22/2007 - 10:11
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

If the problem resulted after upgrading the Big-IP, I suggest opening a ticket with them.


The other thing I may suggest is changing the layer1 connectivity to another switchport.

cratejockey Sat, 09/22/2007 - 22:49
User Badges:

I have been out of the BigIP Game for about a year. However from my experiance the BigIP and Cisco do not negotiate 10/100 Duplex settings well. I would verify that both the 6500 and the Big IP are locked at Speed 100 and Full Duplex. If you are using 1Gbps interfaces you should be able to use Auto/Auto for your negotiation but if that is your current setting try using speed 1000 Full duplex.


If changing the duplex then a shut/no shut sequence doesn't work then I would either roll back to your old BigIP Code or Open up a support case or both.


Good Luck.


www.staticnat.com

Actions

This Discussion