VMware Cloud Community
peeryog
Contributor
Contributor
Jump to solution

Inaccessible host on VSAN

 

I have a VSAN 2 node cluster with a witness.  I have a recent problem with one host.

1. I cannot start a VM. It reaches 66% then fails with an "Operation timed out" error. The 19% is consistent with any vm.

2. It cannot accept a live migration. It reaches 19% and then receives an "Operation timed out" error.

3. It will accept a cold migration, but cannot start the VM (same problem as above.);

4. Skyline health shows there are no issues with the VSAN. All other tests show OK apart from the Create VM test.

5. I am unable to extract a log as when the log is attempted to be open I receive a " marker terminated before EOF" message and the file appears to be corrupt.

Reply
0 Kudos
1 Solution

Accepted Solutions
paudieo
VMware Employee
VMware Employee
Jump to solution

This discussion should be moved to the vSAN storage discussions


From reading the comment "All other tests show OK apart from the Create VM test."
and the comment "i was able to look at the vmkernel.log and it contains numerous references to being unable to create a swap file"

This suggests an underlying plumbing issue of some kind that vSAN health is unable to detect (even though appears clean)
And its preventing you creating a vSAN object. (Cannot create swap)

I still suspect some sort of partition or comms issue

What kind of vSAN 2-node  deployment configuration have you deployed , 
Witness Connected over L3  or Witness trafic seperation?

 We can try to help over this forum but we need some basics first

from each of the vSAN nodes (including witness) can you paste the output of

#esxcli vsan cluster get
#esxcli vsan network list
#esxcli vsan cluster unicastagent list

make sure you can ping all nodes with the correct MTU
#vmkping -I  vmkx <IPs from the unicastagent list > -s -d

where vmkx is the vSAN interface 
-s  means packet size
set to 1472 if default 1500MTU 

-d means dont fragment

#esxcli vsan storage list  
#esxcli vsan health cluster list

 

View solution in original post

Reply
0 Kudos
12 Replies
Tibmeister
Expert
Expert
Jump to solution

What happens when you use vmkping -I <vsan vmknic> <peer address> from one host to another?  Note, that is a capital i, not a lowercase L.  Check your MTU settings as well, I would enable the health check if you are using vDS.

Reply
0 Kudos
peeryog
Contributor
Contributor
Jump to solution

Thanks for the quick reply!

Ping shows 0 packet loss and an average of .327 ms.  MTU is consistent across all connections at 1500. I have enabled health check and will monitor it.

Reply
0 Kudos
Tibmeister
Expert
Expert
Jump to solution

So that's good, you have good vSAN connectivity, although you may want to look at Jumbo Frames at some point.  Repeat the same test using the vmknic of your vMotion interface.

Reply
0 Kudos
peeryog
Contributor
Contributor
Jump to solution

All vmk's ping no problem.  DS health shows connected and good for VDS Status VLAN Health State and Teaming and Failover

Reply
0 Kudos
peeryog
Contributor
Contributor
Jump to solution

Though the other logs seemed corrupt, i was able to look at the vmkernel.log and it contains numerous references to being unable to create a swap file . I am wondering if I have some sort of lock on this host that is preventing the creation of a swap file.

Reply
0 Kudos
paudieo
VMware Employee
VMware Employee
Jump to solution

This discussion should be moved to the vSAN storage discussions


From reading the comment "All other tests show OK apart from the Create VM test."
and the comment "i was able to look at the vmkernel.log and it contains numerous references to being unable to create a swap file"

This suggests an underlying plumbing issue of some kind that vSAN health is unable to detect (even though appears clean)
And its preventing you creating a vSAN object. (Cannot create swap)

I still suspect some sort of partition or comms issue

What kind of vSAN 2-node  deployment configuration have you deployed , 
Witness Connected over L3  or Witness trafic seperation?

 We can try to help over this forum but we need some basics first

from each of the vSAN nodes (including witness) can you paste the output of

#esxcli vsan cluster get
#esxcli vsan network list
#esxcli vsan cluster unicastagent list

make sure you can ping all nodes with the correct MTU
#vmkping -I  vmkx <IPs from the unicastagent list > -s -d

where vmkx is the vSAN interface 
-s  means packet size
set to 1472 if default 1500MTU 

-d means dont fragment

#esxcli vsan storage list  
#esxcli vsan health cluster list

 

Reply
0 Kudos
peeryog
Contributor
Contributor
Jump to solution

From Node 1
[root@ews-node-2:/dev/vsan] esxcli vsan cluster get
Cluster Information
Enabled: true
Current Local Time: 2022-03-23T12:38:39Z
Local Node UUID: 614a0448-c549-5fba-95ba-f40343c83580
Local Node Type: NORMAL
Local Node State: BACKUP
Local Node Health State: HEALTHY
Sub-Cluster Master UUID: 614a6363-82bb-9aca-e109-f40343c86b20
Sub-Cluster Backup UUID: 614a0448-c549-5fba-95ba-f40343c83580
Sub-Cluster UUID: 529aa43f-02c6-982c-4833-3f9ee52521f9
Sub-Cluster Membership Entry Revision: 9
Sub-Cluster Member Count: 3
Sub-Cluster Member UUIDs: 614a6363-82bb-9aca-e109-f40343c86b20, 614a4611-12bf-c8cb-5c0c-0050569d51ee, 614a0448-c549-5fba-95ba-f40343c83580
Sub-Cluster Member HostNames: ews-node-1.domainname.com, ews-node-2.domainname.com
Sub-Cluster Membership UUID: 96e13762-4420-d724-aadf-f40343c86b20
Unicast Mode Enabled: true
Maintenance Mode State: OFF
Config Generation: 6f08c6ea-3368-4fc5-af37-67ef5b84a478 13 2022-03-22T18:05:53.374
Mode: REGULAR
[root@ews-node-2:/dev/vsan] esxcli vsan network list
Interface
VmkNic Name: vmk2
IP Protocol: IP
Interface UUID: 681e4b61-1469-a3e1-94c3-f40343c83580
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: vsan
[root@ews-node-2:/dev/vsan] esxcli vsan cluster unicastagent list
NodeUuid IsWitness Supports Unicast IP Address Port Iface Name Cert Thumbprint SubClusterUuid
------------------------------------ --------- ---------------- ------------- ----- ---------- ----------------------------------------------------------- --------------
614a4611-12bf-c8cb-5c0c-0050569d51ee 1 true 10.1.0.93 12321 F9:46:13:32:11:38:8F:A7:AE:CB:D8:BF:C4:BF:00:2B:41:71:CB:05 529aa43f-02c6-982c-4833-3f9ee52521f9
614a6363-82bb-9aca-e109-f40343c86b20

 

From Node 2

[root@ews-node-1:/dev/vsan] esxcli vsan cluster get
Cluster Information
Enabled: true
Current Local Time: 2022-03-23T12:38:19Z
Local Node UUID: 614a6363-82bb-9aca-e109-f40343c86b20
Local Node Type: NORMAL
Local Node State: MASTER
Local Node Health State: HEALTHY
Sub-Cluster Master UUID: 614a6363-82bb-9aca-e109-f40343c86b20
Sub-Cluster Backup UUID: 614a0448-c549-5fba-95ba-f40343c83580
Sub-Cluster UUID: 529aa43f-02c6-982c-4833-3f9ee52521f9
Sub-Cluster Membership Entry Revision: 9
Sub-Cluster Member Count: 3
Sub-Cluster Member UUIDs: 614a6363-82bb-9aca-e109-f40343c86b20, 614a4611-12bf-c8cb-5c0c-0050569d51ee, 614a0448-c549-5fba-95ba-f40343c83580
Sub-Cluster Member HostNames: ews-node-1.domainname.com,  ews-node-2.domainname.com
Sub-Cluster Membership UUID: 96e13762-4420-d724-aadf-f40343c86b20
Unicast Mode Enabled: true
Maintenance Mode State: OFF
Config Generation: 6f08c6ea-3368-4fc5-af37-67ef5b84a478 13 2022-03-22T18:05:53.362
Mode: REGULAR
[root@ews-node-1:/dev/vsan] esxcli vsan network list
Interface
VmkNic Name: vmk1
IP Protocol: IP
Interface UUID: d690e561-4409-0e3c-1e74-f40343c86b20
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: vsan

Interface
VmkNic Name: vmk0
IP Protocol: IP
Interface UUID: 30a7e561-5ef4-5546-8417-f40343c86b20
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: witness
[root@ews-node-1:/dev/vsan] esxcli vsan cluster unicastagent list
NodeUuid IsWitness Supports Unicast IP Address Port Iface Name Cert Thumbprint SubClusterUuid
------------------------------------ --------- ---------------- ------------- ----- ---------- ----------------------------------------------------------- --------------
614a4611-12bf-c8cb-5c0c-0050569d51ee 1 true 10.1.0.93 12321 F9:46:13:32:11:38:8F:A7:AE:CB:D8:BF:C4:BF:00:2B:41:71:CB:05 529aa43f-02c6-982c-4833-3f9ee52521f9
614a0448-c549-5fba-95ba-f40343c83580 0 true 192.168.254.2 12321 F9:6C:1F:4B:FD:85:9D:A0:29:C6:2F:FC:97:DE:98:5E:7E:52:44:CF 529aa43f-02c6-982c-4833-3f9ee52521f9

 

 

Can ping all nodes with the correct MTU.

 

Storage List from Host with issue

esxcli vsan storage list
mpx.vmhba0:C0:T67:L0
Device: mpx.vmhba0:C0:T67:L0
Display Name: mpx.vmhba0:C0:T67:L0
Is SSD: true
VSAN UUID: 520f83b6-658a-1e3d-0c43-27b8911336b3
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 1241698060807471252
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

mpx.vmhba0:C0:T66:L0
Device: mpx.vmhba0:C0:T66:L0
Display Name: mpx.vmhba0:C0:T66:L0
Is SSD: true
VSAN UUID: 525121e7-3670-018f-61ae-14e622c4faf0
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 7762680675483702515
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

mpx.vmhba0:C0:T65:L0
Device: mpx.vmhba0:C0:T65:L0
Display Name: mpx.vmhba0:C0:T65:L0
Is SSD: true
VSAN UUID: 526770d3-e5cc-cdb0-a4a9-33344135836d
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 10902291082466638895
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

mpx.vmhba0:C0:T68:L0
Device: mpx.vmhba0:C0:T68:L0
Display Name: mpx.vmhba0:C0:T68:L0
Is SSD: true
VSAN UUID: 52764cd1-cae2-83c8-f655-1097c23c5cc8
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 1460327950567094076
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

mpx.vmhba0:C0:T70:L0
Device: mpx.vmhba0:C0:T70:L0
Display Name: mpx.vmhba0:C0:T70:L0
Is SSD: true
VSAN UUID: 52a0b28c-f9fa-7008-e895-8b0159a8e9ea
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 2506376190339000037
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

mpx.vmhba0:C0:T71:L0
Device: mpx.vmhba0:C0:T71:L0
Display Name: mpx.vmhba0:C0:T71:L0
Is SSD: true
VSAN UUID: 52b7d7f0-07ec-fe77-7b28-290b3d96c674
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 18236279211903102675
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

mpx.vmhba0:C0:T69:L0
Device: mpx.vmhba0:C0:T69:L0
Display Name: mpx.vmhba0:C0:T69:L0
Is SSD: true
VSAN UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group UUID: 52e45924-a006-c912-f453-1631affae368
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 13075709333869641331
Checksum OK: true
Is Capacity Tier: false
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Wed Mar 23 00:03:11 2022

 

 

storage list from good host


Device: mpx.vmhba0:C0:T71:L0
Display Name: mpx.vmhba0:C0:T71:L0
Is SSD: true
VSAN UUID: 527e02ef-cbe7-b6f3-113d-72c462400e6f
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 14693399470851128315
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

mpx.vmhba0:C0:T67:L0
Device: mpx.vmhba0:C0:T67:L0
Display Name: mpx.vmhba0:C0:T67:L0
Is SSD: true
VSAN UUID: 52cb270a-a302-93ca-138f-8b8bcaa0f13d
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 14828935015725182813
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

mpx.vmhba0:C0:T68:L0
Device: mpx.vmhba0:C0:T68:L0
Display Name: mpx.vmhba0:C0:T68:L0
Is SSD: true
VSAN UUID: 52e0a425-2c0f-d7da-ece8-ceabaf06d061
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 4218446686140956058
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

mpx.vmhba0:C0:T69:L0
Device: mpx.vmhba0:C0:T69:L0
Display Name: mpx.vmhba0:C0:T69:L0
Is SSD: true
VSAN UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 699148026446318271
Checksum OK: true
Is Capacity Tier: false
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

mpx.vmhba0:C0:T66:L0
Device: mpx.vmhba0:C0:T66:L0
Display Name: mpx.vmhba0:C0:T66:L0
Is SSD: true
VSAN UUID: 52f10925-00ae-454b-d0dc-16a4a897e7c9
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 16326588040070973879
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

mpx.vmhba0:C0:T70:L0
Device: mpx.vmhba0:C0:T70:L0
Display Name: mpx.vmhba0:C0:T70:L0
Is SSD: true
VSAN UUID: 52f559e1-6601-bd64-d00d-e8a03a687954
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 13865254552861956984
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

mpx.vmhba0:C0:T65:L0
Device: mpx.vmhba0:C0:T65:L0
Display Name: mpx.vmhba0:C0:T65:L0
Is SSD: true
VSAN UUID: 52fa0b67-8614-a290-b617-1308d06ad058
VSAN Disk Group UUID: 52e94d7f-2142-4392-a0f4-96cfc2a99b38
VSAN Disk Group Name: mpx.vmhba0:C0:T69:L0
Used by this host: true
In CMMDS: true
On-disk format version: 14
Deduplication: false
Compression: false
Checksum: 16038155854832226426
Checksum OK: true
Is Capacity Tier: true
Encryption Metadata Checksum OK: true
Encryption: false
DiskKeyLoaded: false
Is Mounted: true
Creation Time: Tue Mar 22 20:37:23 2022

Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee
Jump to solution

Thread reported so moderators should move it to the vSAN area.

 


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

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
peeryog
Contributor
Contributor
Jump to solution

Well that'll teach me. All the results I posted have disappeared. Perhaps in the migration.

Reply
0 Kudos
TheBobkin
Champion
Champion
Jump to solution

@peeryog Can you attach the output of:

esxcli vSAN debug object list --all > /tmp/objout

 

Feel free to obfuscate any info you don't want shared or PM me the output if you don't want it shared here.

Reply
0 Kudos
peeryog
Contributor
Contributor
Jump to solution

Thanks to all who responded so quickly . The issue is resolved. As most of you suspected and suggested, it was a network misconfiguration, specifically how one of the hosts was communicating (or not) with the witness. The vmk it was assigned to did not have the Witness task assigned.  So in the end , simple. 

Reply
0 Kudos
paudieo
VMware Employee
VMware Employee
Jump to solution

looks like the outputs finally made it to the thread
Ahh yes you had witness traffic separation as your 2-node config


so on Node 1 we see vsan witness traffic on vmk0 (which I assume is mgmt)
[root@ews-node-1:/dev/vsan] esxcli vsan network list
VmkNic Name: vmk1
IP Protocol: IP
Interface UUID: d690e561-4409-0e3c-1e74-f40343c86b20
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: vsan

Interface
VmkNic Name: vmk0
IP Protocol: IP
Interface UUID: 30a7e561-5ef4-5546-8417-f40343c86b20
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: witness

but on Node 2

there is NO witness traffic separation defined on vmk0

[root@ews-node-2:/dev/vsan] esxcli vsan network list
Interface
VmkNic Name: vmk2
IP Protocol: IP
Interface UUID: 681e4b61-1469-a3e1-94c3-f40343c83580
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: vsan

 

 

Reply
0 Kudos