Public IP Address Allocation (automatic and assigning)

Asked by robb1e

I'm using Eucalyptus 1.5 and when starting an instance, followed by ec2din, the instance reports that it has one of the public IP addresses associated to it already. If I attempt to do an ec2allocaddr you get an InsufficientAddressCapacity exception.

From the front end, you can ssh into the instance private IP address, though if you ssh into the public IP address you get the front end. Attempting to ssh from a computer outside of the cluster doesn't resolve the IP address.

The eucalyptus.conf file has three public IP addresses.

Am I missing something here, or are other people having this issue?

Thanks

Robbie

Question information

Language:
English Edit question
Status:
Solved
For:
Eucalyptus Edit question
Assignee:
No assignee Edit question
Solved by:
robb1e
Solved:
Last query:
Last reply:
Revision history for this message
robb1e (robert-clutton) said :
#1

It seems I can ssh to that public IP address after changing the security settings to open port 22, so that isn't an issue.

Revision history for this message
Neil Soman (neilsoman) said :
#2

**Please use the discussion forum at open.eucalyptus.com for future questions.**

You are likely using SYSTEM mode. In SYSTEM mode IP assignment is done by an external DHCP server, so it doesn't make sense to allocate an IP because Eucalyptus does not control that. The error message should be more helpful, but the front end does not always know how an individual CC's networking is configured.

**Please use the discussion forum at open.eucalyptus.com for future questions.**

Revision history for this message
robb1e (robert-clutton) said :
#3

We're using managed mode.

The exception I'm seeing for ec2allocaddr is as the IPs are being used automatically and we did run out, so it was a valid exception.