ONTAP Discussions

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

ONTAP Discussions

Ask a Question

Cannot ping gateway from Management lif

COG
‎2018-01-17 01:21 AM
8,001 Views

Hi All,

 

We added 2 nodes (node3 and node4) and configured the management lifs. However I cannot even ping the gateway from the managament lifs for Node3 and node4.  Any help will be appreciated.

 

           Logical   Status     Network           Current       Current Is

Vserver     Interface Admin/Oper Address/Mask       Node         Port   Home

----------- ---------- ---------- ------------------ ------------- ------- ----

Cluster

           Node1_clus1 up/up 169.254.209.114/16 Node1     e1a     true

           Node1_clus2 up/up 169.254.218.15/16 Node1     e2a     true

           Node3_clus1 up/up 169.254.233.0/16 Node3         e0c     true

           Node3_clus2 up/up 169.254.242.42/16 Node3       e0e     true

           Node4_clus1 up/up 169.254.72.231/16 Node4         e0c     true

           Node4_clus2 up/up 169.254.85.227/16 Node4         e0e     true

           Node2_clus1   up/up  169.254.126.40/16 Node2         e1a     true

           Node2_clus2   up/up   169.254.60.62/16   Node2         e2a     true

Vserver2

           test2       up/up   136.171.87.106/24 Node1     a0a-1187 true

vserver1

           Node1_icl1 up/up   136.171.211.105/24 Node1     a0a-211 true

           Node1_mgmt0 up/up 136.171.211.101/24 Node1     a0a-211 true

           Node3_mgmt1 up/up 136.171.211.107/24 Node3       a0a-211 true

           Node4_mgmt1 up/up 136.171.211.109/24 Node4       a0a-211 true

           labnas00_mgmt0 up/up 136.171.211.100/24 Node2         a0a-211 true

           Node2_icl1   up/up   136.171.211.104/24 Node2         a0a-211 true

           Node2_mgmt0   up/up   136.171.211.102/24 Node2        a0a-211 true

Vserver3

           Node1_lif1 up/up   136.171.211.200/24 Node1     a0a-211 true

           Node2_lif1   up/up   136.171.211.201/24 Node2         a0a-211 true

0 Kudos
View By:
1 ACCEPTED SOLUTION

HONIG2012
‎2018-01-18 05:34 AM
7,930 Views

what kind of interface group are you using? i see you're having a0a used - so is it an lacp? can you see the lacp coming online on switch side? what's the output of "net port ifgrp show"?

if lacp is up and running i would check the vlan config on the switchports - i think this also could me misconfigured.

 

let me know.

best AJ

View solution in original post

0 Kudos
4 REPLIES 4

HONIG2012
‎2018-01-18 05:34 AM
7,931 Views

what kind of interface group are you using? i see you're having a0a used - so is it an lacp? can you see the lacp coming online on switch side? what's the output of "net port ifgrp show"?

if lacp is up and running i would check the vlan config on the switchports - i think this also could me misconfigured.

 

let me know.

best AJ

0 Kudos

COG
‎2018-01-18 05:59 AM
In response to HONIG2012
7,923 Views

Thanks for the response. Here are some command outputs:

 

 

Cluster::> net port ifgrp show
  (network port ifgrp show)
         Port       Distribution                   Active
Node     IfGrp      Function     MAC Address       Ports   Ports
-------- ---------- ------------ ----------------- ------- -------------------
Node1
         a0a        ip           02:a0:98:17:c5:24 full    e2b, e5b
Node3
         a0a        ip           02:a0:98:20:14:0b full    e0d, e0f
Node4
         a0a        ip           02:a0:98:20:cc:27 full    e0d, e0f
Node2
         a0a        ip           02:a0:98:17:4b:98 partial e2b, e5b


Cluster::> system node run -node Node3, Node4 -command ifgrp status
2 entries were acted on.

Node: Node3
default: transmit 'IP Load balancing', Ifgrp Type 'multi_mode', fail 'log'
a0a: 2 links, transmit 'IP Load balancing', Ifgrp Type 'lacp' fail 'default', Timer 'long'
         Ifgrp Status   Up      Addr_set
        up:
        e0f: state up, since 04Jan2018 12:59:23 (13+18:43:25)
                mediatype: auto-10g_sr-fd-up
                flags: enabled
                active aggr, aggr port: e0d
                input packets 1510842, input bytes 131511648
                input lacp packets 39690, output lacp packets 1330874
                output packets 1330902, output bytes 165029664
                drops (if) 0, drops (link) 0, drops (no active link) 0
                up indications 4, broken indications 1
                indication: up at 04Jan2018 12:59:23
                        consecutive 0, transitions 6
        e0d: state up, since 04Jan2018 12:59:10 (13+18:43:38)
                mediatype: auto-10g_sr-fd-up
                flags: enabled
                active aggr, aggr port: e0d
                input packets 2543190, input bytes 187959056
                input lacp packets 39689, output lacp packets 1268172
                output packets 1301895, output bytes 158848876
                drops (if) 0, drops (link) 0, drops (no active link) 0
                up indications 3, broken indications 1
                indication: up at 04Jan2018 12:59:10
                        consecutive 0, transitions 4

Node: Node4
default: transmit 'IP Load balancing', Ifgrp Type 'multi_mode', fail 'log'
a0a: 2 links, transmit 'IP Load balancing', Ifgrp Type 'lacp' fail 'default', Timer 'long'
         Ifgrp Status   Up      Addr_set
        up:
        e0f: state up, since 04Jan2018 13:59:05 (13+17:43:43)
                mediatype: auto-10g_sr-fd-up
                flags: enabled
                active aggr, aggr port: e0d
                input packets 114249, input bytes 25163909
                input lacp packets 39577, output lacp packets 39581
                output packets 74194, output bytes 6545120
                drops (if) 0, drops (link) 0, drops (no active link) 0
                up indications 5, broken indications 2
                indication: up at 04Jan2018 13:59:05
                        consecutive 0, transitions 7
        e0d: state up, since 04Jan2018 13:59:05 (13+17:43:43)
                mediatype: auto-10g_sr-fd-up
                flags: enabled
                active aggr, aggr port: e0d
                input packets 1234789, input bytes 88013969
                input lacp packets 39576, output lacp packets 39581
                output packets 39613, output bytes 4909516
                drops (if) 0, drops (link) 0, drops (no active link) 0
                up indications 5, broken indications 2
                indication: up at 04Jan2018 13:59:05
                        consecutive 0, transitions 7

      
Cluster::> net port show -node Node3
  (network port show)

Node: Node3
                                                  Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a       Default      -                up   1500  auto/10000 healthy
a0a-1187  Default      -                up   1500  auto/10000 healthy
a0a-211   Default      136.171.211.0/24 up   1500  auto/10000 healthy
a0a-3170  Default      -                up   1500  auto/10000 healthy
e0M       Default      -                up   1500  auto/100   healthy
e0a       Default      -                down 1500  auto/10    -
e0b       Default      -                down 1500  auto/10    -
e0c       Cluster      Cluster          up   9000  auto/10000 healthy
e0d       Default      -                up   1500  auto/10000 healthy
e0e       Cluster      Cluster          up   9000  auto/10000 healthy
e0f       Default      -                up   1500  auto/10000 healthy
e7a       Default      -                down 1500  auto/10    -
e7b       Default      -                down 1500  auto/10    -
13 entries were displayed.

Cluster::> net port show -node Node4
  (network port show)

Node: Node4
                                                  Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a       Default      -                up   1500  auto/10000 healthy
a0a-1187  Default      -                up   1500  auto/10000 healthy
a0a-211   Default      136.171.211.0/24 up   1500  auto/10000 healthy
a0a-3170  Default      -                up   1500  auto/10000 healthy
e0M       Default      -                down 1500  auto/100   -
e0a       Default      -                down 1500  auto/10    -
e0b       Default      -                down 1500  auto/10    -
e0c       Cluster      Cluster          up   9000  auto/10000 healthy
e0d       Default      -                up   1500  auto/10000 healthy
e0e       Cluster      Cluster          up   9000  auto/10000 healthy
e0f       Default      -                up   1500  auto/10000 healthy
e13a      Default      -                down 1500  auto/10    -
e13b      Default      -                down 1500  auto/10    -
e7a       Default      -                down 1500  auto/10    -
e7b       Default      -                down 1500  auto/10    -

 

 

 

Cluster::> system node run -node * -command cdpd show-neighbors
4 entries were acted on.

Node: Node1
Local  Remote          Remote                 Remote           Hold  Remote
Port   Device          Interface              Platform         Time  Capability
------ --------------- ---------------------- ---------------- ----- ----------
e1a    XXXX8f58a. Ethernet1/1            N5K-C5548UP       179   SI
e2a    XXXX8f58b. Ethernet1/1            N5K-C5548UP       178   SI
e2b    XXXX8K61B. Ethernet1/45           N9K-C9396PX       133   RSI
e5b    XXXX8K61A. Ethernet1/45           N9K-C9396PX       133   RSI
e0M    XXXX8f58a. mgmt0                  N5K-C5548UP       179   SI
e0M    XXXX8f58b. mgmt0                  N5K-C5548UP       178   SI
e0M    XXXX8l75a. mgmt0                  N5K-C5010P-BF     179   SI
e0M    XXXX8l75b. mgmt0                  N5K-C5010P-BF     179   SI
e0M    Node2            e0M                    FAS3270           133   H
e0M    XXXX8K61-. GigabitEthernet1/3     cisco WS-C4948    163   RSI

Node: Node3
Local  Remote          Remote                 Remote           Hold  Remote
Port   Device          Interface              Platform         Time  Capability
------ --------------- ---------------------- ---------------- ----- ----------
e0e    XXXX8f58a. Ethernet1/3            N5K-C5548UP       176   SI
e0c    XXXX8f58b. Ethernet1/3            N5K-C5548UP       179   SI

Node: Node4
Local  Remote          Remote                 Remote           Hold  Remote
Port   Device          Interface              Platform         Time  Capability
------ --------------- ---------------------- ---------------- ----- ----------
e0e    XXXX8f58a. Ethernet1/4            N5K-C5548UP       177   SI
e0c    XXXX8f58b. Ethernet1/4            N5K-C5548UP       177   SI

Node: Node2
Local  Remote          Remote                 Remote           Hold  Remote
Port   Device          Interface              Platform         Time  Capability
------ --------------- ---------------------- ---------------- ----- ----------
e1a    XXXX8f58a. Ethernet1/2            N5K-C5548UP       179   SI
e2a    XXXX8f58b. Ethernet1/2            N5K-C5548UP       176   SI
e2b    XXXX8K61A. Ethernet1/47           N9K-C9396PX       133   RSI
e0M    XXXX8f58a. mgmt0                  N5K-C5548UP       179   SI
e0M    XXXX8f58b. mgmt0                  N5K-C5548UP       177   SI
e0M    XXXX8l75a. mgmt0                  N5K-C5010P-BF     179   SI
e0M    XXXX8l75b. mgmt0                  N5K-C5010P-BF     179   SI
e0M    XXXX8K61-. GigabitEthernet1/3     cisco WS-C4948    163   RSI
e0M    Node1        e0M                    FAS3270           146   H

0 Kudos

COG
‎2018-01-18 06:15 AM
In response to HONIG2012
7,918 Views

Also see the ping results. The other 2 nodes in the cluster can ping the gateway except the 2 new nodes.

 

Cluster::> net ping -node Node4 -destination  136.171.211.1
  (network ping)

Cluster::> net ping -node Node3 -destination  136.171.211.1
  (network ping)

Cluster::> net ping -node Node1 -destination  136.171.211.1
  (network ping)
136.171.211.1 is alive

Cluster::> net ping -node Node2 -destination  136.171.211.1
  (network ping)
136.171.211.1 is alive

0 Kudos

COG
‎2018-01-18 01:55 PM
In response to HONIG2012
7,892 Views

Thanks. The problem was with the vlan configuration for the ports on the switch. One of our network personnel changed the configuration of the ports from access to trunk (tagging).

0 Kudos
Announcements
All Community Forums
Public