Unsolved
1 Rookie
•
7 Posts
0
35
February 27th, 2025 17:32
OME 4.3.1 deploy template to mx750c blade success but all CNA paths offline, modular works fine though.
We have an odd one here, when deploying the same template to the same blade in OME-M, keeping the existing ESXi 7.0 U3 (dell ISO), all paths work fine.
But we're trying to start using OME, however deploying from OME, using the same template as above (unassigned in OME-M first..), keeping the same reserved identities and pools, edited the template to include the FC vlan's and esxi mgmt + vmotion vlan's etc etc, the deploy is successful however all CNA paths are down, both FC and Ethernet.
Maybe a hint i'm not sure but also in OME, we cannot seem to propagate any newly created VLAN's, the job fails instantly, but define in OME-M and edit template, the propagate job runs successfully.
BTW - This same process worked successfully in another site using OME 4.1
moogoose
1 Rookie
•
7 Posts
0
February 27th, 2025 17:34
modular version 2.00
DELL-Young E
Moderator
•
5.3K Posts
0
February 28th, 2025 05:34
Hello,
"BTW - This same process worked successfully in another site using OME 4.1"
#1 can you check if switches get VLANs assigned to the ports or not
#2 does it apply any profile settings at all
#3 if it does not, can you try to fail over/reboot MM in affected chassis
#4 https://dell.to/4h0UCqL
Respectfully,
moogoose
1 Rookie
•
7 Posts
0
March 3rd, 2025 02:31
@DELL-Young E thanks for your reply,
#1 we're using smart fabric mode so our cli is more limited but if you could advise us how to check we'd glady check that for you. currently i've just done a show run | no-more output to a txt file and searched for the vlan number being allowed on a port and i find that only the vlan's assigned to a template deployed from modular are allowed on eth 1/1/1 and eth1/71/1 etc.
2# it does 100% apply other profile settings and also the deployment job says it completed successfully
#3 we can deploy in modular successfully, so that would suggest the MM is ok? we've encountered the scenario previously where dell support have instructed us to reseat the MM's due to becoming unresponsive and all operations on chassis #2 failing but successful on chassis #1 etc.
(edited)
DELL-Joey C
Moderator
•
4.1K Posts
0
March 3rd, 2025 07:55
Hi,
YoungAh is not around today, I'll send her the updates and check what could be the next action.
Meanwhile, in OME-M, can you go to your Identity Pools tab and click on Usage. Can you check if there is any conflicts or mismatch. Alternately, you can give us a screenshot of that.
moogoose
1 Rookie
•
7 Posts
0
March 3rd, 2025 21:17
@DELL-Joey C
thanks for your reply, image above, the modular fabric manager can't see it.. but from OME below, the profile thinks it has some identities assigned:
OME identity pool usage:
esxi:
moogoose
1 Rookie
•
7 Posts
0
March 3rd, 2025 21:33
we have tried re-deploy from OME even though the first deploy was successful but still same issue (as with OME, sometimes running the job again helps)
later today we're going to try failover the MM for chassis 1 and see if that helps.
moogoose
1 Rookie
•
7 Posts
0
March 6th, 2025 23:07
update on this one, looks like its confirmed in Dell LAB that this issue exists for modular 2.00/2.10 and OME 4.3.x, recommendation is to update modular to 2.20 and retry, will report back once we've done that :-)