netapp NIC flapping

DevilWAHDevilWAH Member Posts: 2,997 ■■■■■■■■□□
in Off-Topic
Hi all,

any net-app guys here?

I have a port on my switch bouncing up and down. its part of a two port LACP group and the same switch has another identical filer with identical config (for network) with two more ports that are not showing any issue. So my only conclusion is its a config issue on the netapp, or a hardware issue at one end.

The switch logs don't show any more than below, but the netapp doesn't show any thing at all in the logs. Any one know how to show up network NIC events on the CLI of a netapp filer. I think it might be hardware issue but would really expect the netapp to show up in its logs that the line protocol is bouncing.

Cheers.
Sep 30 2013 17:56:28.504 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to downSep 30 2013 17:56:32.345 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 18:00:33.529 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 18:00:37.262 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 18:11:42.514 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 18:11:46.171 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 18:20:58.523 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 18:21:02.289 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 18:30:12.527 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 18:30:16.436 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 18:39:26.531 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 18:39:30.247 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:06:47.539 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:06:51.196 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:09:04.546 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:09:08.430 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:16:54.541 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:16:58.307 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:22:26.554 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:22:30.572 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:27:27.555 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:27:31.414 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:33:21.554 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:33:25.153 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 19:57:02.559 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 19:57:06.526 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 20:03:32.569 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 20:03:36.428 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 20:06:17.578 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 20:06:21.143 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 20:40:24.584 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 20:40:28.325 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 20:43:41.586 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 20:43:45.419 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 20:47:49.589 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 20:47:53.431 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 20:58:01.590 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 20:58:05.407 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 21:13:25.598 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 21:13:29.281 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 21:17:54.598 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 21:17:58.616 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 21:20:41.602 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 21:20:45.394 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
Sep 30 2013 21:27:07.603 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
Sep 30 2013 21:27:11.512 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
  • If you can't explain it simply, you don't understand it well enough. Albert Einstein
  • An arrow can only be shot by pulling it backward. So when life is dragging you back with difficulties. It means that its going to launch you into something great. So just focus and keep aiming.
Linkin Profile - Blog: http://Devilwah.com
· Share on FacebookShare on Twitter

Comments

  • phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    Do these help?

    netdiag
    stats show aggregate
    stats show fcp
    stats show iscsi
    stats show cifs
    stats show ifnet
    · Share on FacebookShare on Twitter
  • QHaloQHalo Member Posts: 1,488
    ifstat -a

    rdfile /etc/messages

    rdfile /etc/log/lacp_log

    You can also pktt capture using Wireshark to view the logs.
    http://vwilmo.wordpress.com

    · Share on FacebookShare on Twitter
  • AwesomeGarrettAwesomeGarrett Member Posts: 257
    This is a little odd that the line protocol is going up/down not the link itself. Have you replaced the cabling? Reset the NIC in the OS of the netapp device?(Don't know anything about netapp) Added another port to the port-channel on the switch and move the cable to the new port?
    · Share on FacebookShare on Twitter
  • DevilWAHDevilWAH Member Posts: 2,997 ■■■■■■■■□□
    QHalo wrote: »
    ifstat -a

    rdfile /etc/messages

    rdfile /etc/log/lacp_log

    You can also pktt capture using Wireshark to view the logs.

    the LACP_log shows a lot of
    2013-10-03 16:34:32: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE2013-10-03 16:34:49: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:35:02: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:35:14: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:35:30: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:35:41: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:36:00: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:36:10: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:36:28: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:36:40: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:36:54: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:37:09: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:37:22: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:37:36: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:37:50: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:38:05: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:38:18: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:38:32: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:38:47: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE
2013-10-03 16:38:59: DEBUG:  Rx_machine : LAG_PKT: e0b setting partner port sync to TRUE
2013-10-03 16:39:14: DEBUG:  Rx_machine : LAG_PKT: e0a setting partner port sync to TRUE

    this normal?

    Cheers
    • If you can't explain it simply, you don't understand it well enough. Albert Einstein
    • An arrow can only be shot by pulling it backward. So when life is dragging you back with difficulties. It means that its going to launch you into something great. So just focus and keep aiming.
    Linkin Profile - Blog: http://Devilwah.com
    · Share on FacebookShare on Twitter
  • QHaloQHalo Member Posts: 1,488
    All of mine are similar. Is this a new install? Did someone just create that ifgrp on the filer? I've seen where when you do that you need to reboot the filer. You can also try 'source /etc/rc' to reload the rc config but I wouldn't do that if it's serving anything production. It shouldn't cause an issue but you can never be too sure.

    If its possible can you show the running config of the ports and the /etc/rc file output?
    http://vwilmo.wordpress.com

    · Share on FacebookShare on Twitter
Sign In or Register to comment.