Leigh Kalbli
asked on
Dell poweredge idrac vlan
I am having an issue with our Idrac connections to teh Dell Open Manage plug in for vCenter. I have a seperate vlan for idrac's for 8 hosts. I am able to ping the idrac's IP on VLAN 300 and its gateway. I can connect from other vlans using the WUI. But, when i try to run the Inventory Scan for the Dell Open Manage tool, they all fail to connect to idrac's. The credentials are all correct as i am able to get to the idracs from a browser. Has anyone experienced issues getting DOM to connect? The DOM virtual appliance is on a different VLAN 100, but when creating connection profiles, it can detect esx hosts that are on a different vlan 200.
Any thoughts are appreciated.
Any thoughts are appreciated.
Is this a vcenter appliance, or a windows server ?
If vcenter is a Windows Server, are you able to login to the iDRAC from the server ?
If vcenter is a Windows Server, are you able to login to the iDRAC from the server ?
ASKER
clarification. the vcenter server is the appliance, not windows server. I am able to connect to the idracs from a web browser from other windows servers that are on other vlans. The issue is that when the Dell Open Manage Integration attempts to run its inventory it cannot connect to the idrac. I have tried to disable the VLAN on the idrac and configured the switch port Trunk on the vlan.
do you have a dedicated idrac port, or it shares the network interface. This deals with whether you should tag the vlan as well as whether the definition of the switch port to which this NIC/DRAC is connected and whether it .......
ASKER
I am using the dedicated port.
OK, and the port on the switch is set to VLAN 300 and has an IP on the vlan30 segment including default gateway? double check IP/netmask/default gateway on the idrac configuration matches the VLAN 300 segment definition, and in your case, the idrac should not be tagging , vlan should not be checked.
The other part is to check the ACLs you have on the switch if this is a Level 3 switch where you have ACLs that define how and which VLANs have access to other vlans....segments...
The other part is to check the ACLs you have on the switch if this is a Level 3 switch where you have ACLs that define how and which VLANs have access to other vlans....segments...
ASKER
Arnold,
I have checked all that. I also checked the switch its a Meraki MS42 and it does have the ACL's
I have checked all that. I also checked the switch its a Meraki MS42 and it does have the ACL's
make sure there is no other host using that same IP.
ping ip
arp -a ip
then look at the online mac IP lookup to confirm it is an idrac MAC and not another system's IP.
Not sure idrac responds to ping.
see if you can add a MAC lockout tying the IP of the idRAC to the Mac address of the idrac. Using open manage node tool on the system's remote access configuration, it shows the idrac's mac address....
ping ip
arp -a ip
then look at the online mac IP lookup to confirm it is an idrac MAC and not another system's IP.
Not sure idrac responds to ping.
see if you can add a MAC lockout tying the IP of the idRAC to the Mac address of the idrac. Using open manage node tool on the system's remote access configuration, it shows the idrac's mac address....
ASKER
no other device is using this IP. I can ping idrac and confirmed the mac address of the idrac. I should clarify that i am using Open Manage virtual appliance 3.1.0 and these are idrac6 controllers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Self resolved.
Often the idrac is set to vlan1 this is on the idrac under configuration.....
the issue, is the attempt via the web browser from the same system/vlan/segment from which the scan is attempted?
check whether the access to VLAN 300 from 100/200 is permitted and then whether the responses from 300 are permitted to reach 100/200 hosts/..