English Community

Ideation - Idea ExchangeXClarity Ideation
All Forum Topics
Options

15 Posts

08-23-2016

SK

28 Signins

240 Page Views

  • Posts: 15
  • Registered: ‎08-23-2016
  • Location: SK
  • Views: 240
  • Message 1 of 8

Manage Flex system components IPs (IMM) from LXCA

2018-08-06, 9:14 AM

Currently you can manage IPs of the compoments only if you have network access to the specific IMM. However If you have a new server in the chassis with factory IPs, LXCA usually has no access to it, therefore you still have to login to the CMM console and set the IP manually.

 

IPs settings should be pushed by LXCA via CMM not directly to IMM.

 

Reply
Options

40 Posts

03-03-2015

US

352 Signins

2957 Page Views

  • Posts: 40
  • Registered: ‎03-03-2015
  • Location: US
  • Views: 2957
  • Message 2 of 8

Re: Manage Flex system components IPs (IMM) from LXCA - Status changed to: Tell Us More

2018-08-06, 15:14 PM

This feature was made available in 2.0.  Are you using a 1.x release?  Or can you describe what is missing from existing features?

 

Hope to hear from you soon.

Reply
Options

15 Posts

08-23-2016

SK

28 Signins

240 Page Views

  • Posts: 15
  • Registered: ‎08-23-2016
  • Location: SK
  • Views: 240
  • Message 3 of 8

Re: Manage Flex system components IPs (IMM) from LXCA

2018-08-06, 16:02 PM

Using 2.1.

It failed when server had factory IP (192.168.70.112). I'm assuming it was trying to communicate directly with IMM which obviosly failed as there is no network routing. Therefore feature is uselless for the new nodes in the chassis. You still have to set IPs via CMM first or use DHCP server to manage them via LXCA.

 

Reply
Options

40 Posts

03-03-2015

US

352 Signins

2957 Page Views

  • Posts: 40
  • Registered: ‎03-03-2015
  • Location: US
  • Views: 2957
  • Message 4 of 8

Re: Manage Flex system components IPs (IMM) from LXCA - Status changed to: New

2018-08-06, 16:14 PM

I am resetting the status back to new as the team is looking at the additional information provided.

Reply
Options

40 Posts

03-03-2015

US

352 Signins

2957 Page Views

  • Posts: 40
  • Registered: ‎03-03-2015
  • Location: US
  • Views: 2957
  • Message 5 of 8

Re: Manage Flex system components IPs (IMM) from LXCA - Status changed to: Tell Us More

2018-08-06, 20:32 PM

The development team did another attempt with 2.1 to see if they could reproduce the issue you stated.  The feature worked just fine so they believe debug would be required with service since this function should already work.

 

Can you please call into service to open a ticket so we can help more directly figure out why it is not working as expected?

Reply
Options

15 Posts

08-23-2016

SK

28 Signins

240 Page Views

  • Posts: 15
  • Registered: ‎08-23-2016
  • Location: SK
  • Views: 240
  • Message 6 of 8

Re: Manage Flex system components IPs (IMM) from LXCA

2018-08-07, 15:10 PM

Looks like you're right. Tried to change IP to non existent one and back and it worked this time.

I have found out error message which I got first time and it failed because of "Inventory properties HOSTNAME modification job for target IPV6_STATIC_ENABLED has failed." We are not using IPv6 so everything there is default. No time to play with it anymore, I may open a ticket if I have issues with a new server.

Reply
Options

40 Posts

03-03-2015

US

352 Signins

2957 Page Views

  • Posts: 40
  • Registered: ‎03-03-2015
  • Location: US
  • Views: 2957
  • Message 7 of 8

Re: Manage Flex system components IPs (IMM) from LXCA - Status changed to: Implemented

2018-08-07, 16:29 PM

Great news! 

 

For others that may have been interested in this feature, I am moving this idea to implemented so they can also be aware the feature is avialable in 2.1.0. 

 

Thanks again for submitting the idea!

Reply
Options

15 Posts

08-23-2016

SK

28 Signins

240 Page Views

  • Posts: 15
  • Registered: ‎08-23-2016
  • Location: SK
  • Views: 240
  • Message 8 of 8

Re: Manage Flex system components IPs (IMM) from LXCA

2018-11-20, 10:31 AM

So definitelly not working as it should, got motheboard replaced, for one node in the chassis, when I tried to change Device Name, host name and IPv4 job failed. Its 9532 server type. LXCA 2.2

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete