We are trying to configure a 4 node C800 MCC-IP with Cisco9336 switches... one of the last commands fails "metrocluster configuration-settings connection connect" and complains that the node cannot ping between some of the metrocluster interface IPs... We have gone though almost everything.. (switch config, etc. etc. etc.) but we would like to be able to test the ping before we run the command again... but there doesn't seem to be a wey to do this? The interface is hidden from the interfaces list, and we cannot fint any useful option in the "metrocluster" command stack...
#Troubleshooting MCC-IP "IPVI" interfaces...
polar chasm
..I'm no Cisco expert, but would it be possible to create an IP on the switch and test pinging the NetApp adapter IP? But I am hoping there are another way 🙂
polar chasm
OK... FFS NetApp get your documentation in order... It seems I have ended up in this little "issue" https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/MetroCluster_IP_installation_-_Did_not_receive_a_"ping"_response
It seems you need to specify a VLAN chen you create the interfaces... this VLAN needs to match the VLAN on your clusterswitches (port 9-10)...
In our instance the RCF tool specified VLAN 10 and 11 as default... we didn't know any better...
DKDC1-NAMC0002::*> metrocluster configuration-settings interface create -cluster-name DKDC1-NAMC0002 -home-node DKDC1-NAMN001 -home-port e0b -address 10.1.1.1 -netmask 255.255.255.0 -vlan-id 10
Warning: Verify that the attached switches' RCF has been updated with the VLAN ID value specified using "-vlan-id" parameter before proceeding further.
Do you want to continue? {y|n}: y
Error: command failed: Invalid value for parameter "-vlan-id". Valid range is 101 to 4096 inclusive.
Sadly you have to use VLANs over 101... which is just great... we then need to reconfigure our four switches...
And might I just add that non of this is mentioned in the MCC documentation... 😉 And this is not my first Metrocluster, just my first IP-based... is has been painful to say the least 😉
quartz kindle
sorry but this is clearly stated in the docs: here it says "By default, each of the two ports use a different VLAN: 10 and 20. You can also specify a different (non-default) VLAN higher than 100 (between 101 and 4095) using the ... command"
but yeah, MetroCluster is tricky to set up if you've never done it before because there are so many things to consider. But the documentation is actually pretty good these days (it was waaaaay worse some 1-2 years ago)
polar chasm
Well it ended up not working with the -vlan-id option... not sure if it was the adapter or the asa c800 config, but it stated that it was not possible to use vlans on the system... I also didn't understand it since the ports on the switch was configured as access ports... never the less something must have changed with the new config on the switches because it ended up working... Another annoying thing is that the documentation clearly shows the metrocluster ports as "up" before you configure the ports.. and some of them were online, but not all... so this send me down a deep rabbit hole where we was close to replacing cables etc.. but we ended up upgrading IOS which did noting, and then updating ONTAP (mid configuration) then old fashioned way.. and then all ports were down which I guess makes sense.. then as you configure the ports, they link up, and we could get past this step and start creating and mirroring aggregates... As this is my first MCC-IP this is somewhat new to me, I have setup a lot of MCC-FC which seems simpler than this... and I can see that all disks have been "obfuscated" with virtual HBAs all the way down to the "sysconfig -a" 🙂 Which makes things interesting 😉 Anyway it seems like we are "out of the woods" for now 🙂
quartz kindle
yeah, it depends on the platform whether you have to use access-ports or tagged VLAN ports. This is also somewhere in the documentation but I can't check right now
dense ginkgo
@polar chasm at least with dedicated switches, metrocluster setup has worked very easily through system manager, just peer the clusters and then click metrocluster setup and it does everything automatically. 🙂