VMware Cloud Community
listener
Contributor
Contributor
Jump to solution

IPv6 can't ping 2nd service console

I configured a new vswitch with a service console and a vmkernel to use IPv6 and IPv4.

I can ping the IPv4 address of both the service console and vmkernel. But, I can only ping the IPv4 address of the service console.

Why would something like that happen? I checked to see if it was a duplicate address and it was not.

Thanks

Reply
0 Kudos
1 Solution

Accepted Solutions
Andy_Banta
Hot Shot
Hot Shot
Jump to solution

Is this using vSphere4? There's no requirement for service console ports to use iSCSI, now.

Can you supply the output of esxcfg-vswitch -l and esxcfg-vmknic -l so I can see what your network config looks like?

Also, are you able to ping the storage from ESX using the vmkping command?

If you're able to ping both directions, getting logs from the storage and ESX host around discovery time would be the next piece of helpful information.

Thanks,

Andy

View solution in original post

Reply
0 Kudos
10 Replies
listener
Contributor
Contributor
Jump to solution

It seems that by deleting the second service console and readding it, I can now ping.

However, I still can't get the iSCSI initiator to login on an IPv6 address. I have all my IPv6 iSCSI server addresses in the "Send Targets" of the 'Dynamic Discovery' tab.

thanks again...

Reply
0 Kudos
Andy_Banta
Hot Shot
Hot Shot
Jump to solution

Is this using vSphere4? There's no requirement for service console ports to use iSCSI, now.

Can you supply the output of esxcfg-vswitch -l and esxcfg-vmknic -l so I can see what your network config looks like?

Also, are you able to ping the storage from ESX using the vmkping command?

If you're able to ping both directions, getting logs from the storage and ESX host around discovery time would be the next piece of helpful information.

Thanks,

Andy

Reply
0 Kudos
gcshekhar
Contributor
Contributor
Jump to solution

Could you also add the COS routing table:'ip -6 route show'.

Thanks.

listener
Contributor
Contributor
Jump to solution

Hi Andy!

Yes this is ESX 4.0GA. I just took the service console port out of the virtual switch, but that hasn't made a difference to the iscsi initiator.

Thanks!

Holly

# esxcfg-vswitch -l

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 32 3 32 1500 vmnic0

PortGroup Name VLAN ID Used Ports Uplinks

VM Network 0 0 vmnic0

Service Console 0 1 vmnic0

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch1 64 4 64 1500 vmnic4,vmnic1

PortGroup Name VLAN ID Used Ports Uplinks

VMkernel 0 1 vmnic1,vmnic4

# esxcfg-vmknic -l

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type

vmk0 VMkernel IPv4 192.168.0.6 255.255.255.0 192.168.0.255 00:50:56:7e:c5:d6 1500 65535 true STATIC

vmk0 VMkernel IPv6 fe80::250:56ff:fe7e:c5d6 64 00:50:56:7e:c5:d6 1500 65535 true STATIC

[[root@vmshe-dell2950-02 ~]# ip -6 route show

unreachable ::/96 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 2002:a00::/24 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 2002:7f00::/24 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 2002:a9fe::/32 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 2002:ac10::/28 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 2002:c0a8::/32 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 2002:e000::/19 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

unreachable 3ffe:ffff::/32 dev lo metric 1024 expires -77358sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295

fe80::/64 dev vmnic0 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

fe80::/64 dev vmnic1 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

fe80::/64 dev vmnic2 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

fe80::/64 dev vmnic3 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

fe80::/64 dev vmnic4 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

fe80::/64 dev vmnic5 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

fe80::/64 dev vswif0 metric 256 expires -77364sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vmnic0 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vmnic1 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vmnic2 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vmnic3 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vmnic4 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vmnic5 metric 256 expires -77365sec mtu 1500 advmss 1440 hoplimit 4294967295

ff00::/8 dev vswif0 metric 256 expires -77364sec mtu 1500 advmss 1440 hoplimit 4294967295

Can't ping host to the filer

# vmkping -6 fe80::2a0:98ff:fe0a:1d59

PING fe80::2a0:98ff:fe0a:1d59 (fe80::2a0:98ff:fe0a:1d59): 56 data bytes

sendto() failed (No route to host)

But I can ping from the filer to the host

NETAPP-fas3070-12> ping6 -i e0c fe80::250:56ff:fe7e:c5d6

PING6(56=4088 bytes) fe80::2a0:98ff:fe0a:1d59 --> fe80::250:56ff:fe7e:c5d6

16 bytes from fe80::250:56ff:fe7e:c5d6, icmp_seq=0 hlim=64 time=0 ms

Reply
0 Kudos
gcshekhar
Contributor
Contributor
Jump to solution

> root@vmshe-dell2950-02 ~# vmkping -6 fe80::2a0:98ff:fe0a:1d59

PING fe80::2a0:98ff:fe0a:1d59 (fe80::2a0:98ff:fe0a:1d59): 56 data bytes

sendto() failed (No route to host)

Please provide the outgoing interface (scope) as well, just as you did with ping6. This is necessary for IPv6 since the destination is a link-local address and it has to be scoped:

$ vmking -6 fe80::2a0:98ff:fe0a:1d59 -I vmk0 ;# assuming vmnic1/vmnic4 are reachable to the filer

Thanks,

--shekhar

Reply
0 Kudos
listener
Contributor
Contributor
Jump to solution

  1. vmkping -I vmk0 -6 fe80::2a0:98ff:fe0a:1d5b

PING fe80::2a0:98ff:fe0a:1d5b (fe80::2a0:98ff:fe0a:1d5b): 56 data bytes

--- fe80::2a0:98ff:fe0a:1d5b ping statistics ---

3 packets transmitted, 0 packets received, 100% packet loss

vmshe-fas3070-12> ping6 -i e0c fe80::250:56ff:fe7e:c5d6

PING6(56=4088 bytes) fe80::2a0:98ff:fe0a:1d59 --> fe80::250:56ff:fe7e:c5d6

16 bytes from fe80::250:56ff:fe7e:c5d6, icmp_seq=0 hlim=64 time=0 ms

Filer -> host works

host-> filer doesn't.

I was looking around in the vmkernel I created and the gateway for IPv6 is "auto." I can't change this because the box is grayed out. Is that normal? Or possiblity the cause of this problem?

thanks gcshekhar

Reply
0 Kudos
gcshekhar
Contributor
Contributor
Jump to solution

> Filer -> host works

> host-> filer doesn't.

Do you have any firewalling on the filer that may prevent incoming pings? Does IPv6 ping (using the same fe80:: address) work from another source?

Couple more things that would be helpful:

- 'esxcfg-route -f V6 -l' output on ESX

- 'ip -6 neigh show' output on filer after pinging the ESX

thanks,

--shekhar

kunhuang
Enthusiast
Enthusiast
Jump to solution

Hi,

I think both ipv6 addresses are local scope at netapp target (fe80::2a0:98ff:fe0a:1d59) and esx inititator (fe80::250:56ff:fe7e:c5d6) side.

This local scope addresses would have problem connecting with tcp/ip without giving a outbound interface, which by default esx sw iscsi would not give.

Netapp side might not be able to route iscsi packets either, if they don't suuport local scope ipv6 initiators, which I'm not sure.

(BTW, this does not explain why you can't vmkping from esx to netapp, but it can be the cause of failure of discovery and login iscsi targets)

So can you try to config. global scope ipv6 address at both ends?

Regards,

- Kun

Reply
0 Kudos
listener
Contributor
Contributor
Jump to solution

I added IP6 addresses on my filers. The config looks like this now:

vmshe-fas3070-12> ifconfig -a

...

e0c: flags=148043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

inet6 2008:cccc:bbbb:aaaa::4 prefixlen 64 tentative

inet6 fe80::2a0:98ff:fe0a:1d59 prefixlen 64 scopeid 0x2 autoconf tentative partner e0c (not in use)

ether 00:a0:98:0a:1d:59 (auto-1000t-fd-enabling) flowcontrol full ..

vmshe-fas3070-11> ifconfig -a

e0c: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500

inet6 fe80::2a0:98ff:fe0c:8a3d prefixlen 64 scopeid 0x2 autoconf

inet 192.168.0.90 netmask 0xffffff00 broadcast 192.168.0.255

inet6 2008:cccc:bbbb:aaaa::7 prefixlen 64

partner e0c (not in use)

ether 00:a0:98:0c:8a:3d (auto-1000t-fd-up) flowcontrol full

They both can ping one another...

vmshe-fas3070-12> ping6 2008:cccc:bbbb:aaaa::7

PING6(56=4088 bytes) 2008:cccc:bbbb:aaaa::4 --> 2008:cccc:bbbb:aaaa::7

16 bytes from 2008:cccc:bbbb:aaaa::7, icmp_seq=0 hlim=64 time=1 ms

vmshe-fas3070-11> ping6 2008:cccc:bbbb:aaaa::4

PING6(56=4088 bytes) 2008:cccc:bbbb:aaaa::7 --> 2008:cccc:bbbb:aaaa::4

16 bytes from 2008:cccc:bbbb:aaaa::4, icmp_seq=0 hlim=64 time=0 ms

But cannot ping on the fe80 addresses.

vmshe-fas3070-11> ping6 fe80::2a0:98ff:fe0a:1d59

PING6(56=4088 bytes) :: --> fe80::2a0:98ff:fe0a:1d59

sendmsgping6: wrote fe80::2a0:98ff:fe0a:1d59 16 chars, ret=-65

sendmsgping6: wrote fe80::2a0:98ff:fe0a:1d59 16 chars, ret=-65

There aren't any firewalls up. My cisco switch has all the ports on the same default vlan.

I added a "2008" IP to the vmkernel but I can't ping it.

# esxcfg-vmknic -l

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type

vmk0 VMkernel IPv4 192.168.0.6 255.255.255.0 192.168.0.255 00:50:56:7e:c5:d6 1500 65535 true STATIC

vmk0 VMkernel IPv6 fe80::250:56ff:fe7e:c5d6 64 00:50:56:7e:c5:d6 1500 65535 true STATIC

vmk0 VMkernel IPv6 2008:cccc:bbbb:abab::3 64 00:50:56:7e:c5:d6 1500 65535 true STATIC

vmshe-fas3070-12> ping6 2008:cccc:bbbb:abab::3

PING6(56=4088 bytes) :: --> 2008:cccc:bbbb:abab::3

sendmsgping6: wrote 2008:cccc:bbbb:abab::3 16 chars, ret=-65

sendmsgping6: wrote 2008:cccc:bbbb:abab::3 16 chars, ret=-65

--- 2008:cccc:bbbb:abab::3 ping6 statistics ---

2 packets transmitted, 0 packets received, 100% packet loss

# esxcfg-route -f V6 -l

VMkernel Routes:

Network Netmask Gateway

2008:cccc:bbbb:abab:: 64 Local Subnet

fe80:: 64 Local Subnet

ff01:: 32 Local Subnet

ff02:: 32 Local Subnet

Unfortunately, I don't have anything else on this private network with IPv6 to ping....hmmm

Reply
0 Kudos
listener
Contributor
Contributor
Jump to solution

Fixed it. I changed all the addresses to use unique local fc00::/7 and now the iSCSI initiator logs in.

Thanks

Reply
0 Kudos