×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

CIMC hijacks IP address!

Answered Question
Nov 16th, 2011
User Badges:
  • Gold, 750 points or more

UCS C200M2 CIMC firmware 1.4(1a). CIMC is configured with 192.168.1.48/24 proof


Screen Shot 2011-11-16 at 5.49.22 PM.png


Let me ping it from core:


ARC-3750-Core#ping 192.168.1.48

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.48, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/9 ms

ARC-3750-Core#show ip arp 192.168.1.48

Protocol  Address          Age (min)  Hardware Addr   Type   Interface

Internet  192.168.1.48            0   7081.05ff.2d2c  ARPA   Vlan1


Looks good. Now watch this:


ARC-3750-Core#ping 192.168.1.10


Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/9 ms

ARC-3750-Core#show ip arp 192.168.1.10

Protocol  Address          Age (min)  Hardware Addr   Type   Interface

Internet  192.168.1.10           20   7081.05ff.2d2c  ARPA   Vlan1


192.168.1.10 is also voice gateway, so I've been chasing this for a few days until I finally decided to change voice gateway's IP and then discovered that 192.168.1.10 was still responding.


Probably a bug.









Correct Answer by Robert Burns about 5 years 9 months ago

NP.  As soon as I have the patch version this will be addressed it I will update this post.


Regards,


Robert

Correct Answer by Robert Burns about 5 years 9 months ago

We've logged a new bug spefically to track this issue - CSCtw47679.

(Please allow 24hrs for this bug to be publicly visible)


Symptom:

Default CIMC IP addressing on eth0 mgmt interface is not clearing
after static IP configuration.
When user statically assigns the CIMC with an IP address in the subnet
of 192.168.1.X, IP address 192.168.1.10 is not
cleared from UCS system and user is able to ping both IP's to reach the CIMC. 
This will cause layer 3 addressing confusion if another device is configured
with the 192.168.1.10 address as well.
Conditions:


Bug is experienced on C200 M2 running firmware version 1.4(1a). 
This condition exists when customer is statically
assigning an IP address to the CIMC and affects the network when the
subnet 192.168.1.X is in use. Workaround:
1. Boot into the CIMC Configuration Utility. 2. Reset configurations to factory default settings. 3. Reconfigure configurations through local KVM.



Anyone else having this issue I implore you to open a quick TAC case and request to attach this bug so we can prioritize a fix.


Regards,


Robert

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Robert Burns Wed, 11/16/2011 - 17:00
User Badges:
  • Cisco Employee,

Was the .10 address ever configured on this CIMC?


I dont believe the CIMC would "hijack" a random IP address like that.


Robert

mipetrin Wed, 11/16/2011 - 17:45
User Badges:
  • Cisco Employee,

Hi Roman,


The 192.168.1.10 is a burnt in address that is assigned to the server during manufacturing. A particular script needs to be run in order to remove this address from the interface. Looks like this may have been missed on your device.


To alleviate the issue, break into the CIMC utility and reset the settings to factory default. This will run a script that wipes the address. Then you can reconfigure the CIMC address and should find that 192.168.1.10 is no longer reachable.


Thanks,

Michael

Roman Rodichev Fri, 11/18/2011 - 20:21
User Badges:
  • Gold, 750 points or more

Michael,


this appears to be a common bug. I just got two more servers and they have the same issue. Yes, factory default reset gets rid of 192.168.1.10. This can be a nasty defect for some who use 192.168.1.x and happen to have an existing 192.168.1.10 on their network. I'm asking TAC engineer to file a bug.


As far as my existing production servers go, I now have to go onsite, factory reset CIMC, reboot the server, and set the CIMC IP again.


Roman

Robert Burns Sat, 11/19/2011 - 05:37
User Badges:
  • Cisco Employee,

Thanks Roman - Please update this thread with the Bug ID.


Regards,


Robert

mtimm Sat, 11/19/2011 - 09:50
User Badges:
  • Cisco Employee,

There is this internal bug CSCtl86779 that reports a situation where CIMC will continue to respond to addresses it is no longer configured for if the networking mode is changed when a session is active.   To say that this is left over from the factory seems to be a little off base in my opinion.  This appears to be the default IP address assigned to en0 when the system is in its factory default state, too bad it isn't documented as such though.

Correct Answer
Robert Burns Tue, 11/22/2011 - 13:41
User Badges:
  • Cisco Employee,

We've logged a new bug spefically to track this issue - CSCtw47679.

(Please allow 24hrs for this bug to be publicly visible)


Symptom:

Default CIMC IP addressing on eth0 mgmt interface is not clearing
after static IP configuration.
When user statically assigns the CIMC with an IP address in the subnet
of 192.168.1.X, IP address 192.168.1.10 is not
cleared from UCS system and user is able to ping both IP's to reach the CIMC. 
This will cause layer 3 addressing confusion if another device is configured
with the 192.168.1.10 address as well.
Conditions:


Bug is experienced on C200 M2 running firmware version 1.4(1a). 
This condition exists when customer is statically
assigning an IP address to the CIMC and affects the network when the
subnet 192.168.1.X is in use. Workaround:
1. Boot into the CIMC Configuration Utility. 2. Reset configurations to factory default settings. 3. Reconfigure configurations through local KVM.



Anyone else having this issue I implore you to open a quick TAC case and request to attach this bug so we can prioritize a fix.


Regards,


Robert

Roman Rodichev Wed, 11/23/2011 - 17:43
User Badges:
  • Gold, 750 points or more

Thanks Robert, I'm glad this issue will be addressed in a future CIMC update.

Correct Answer
Robert Burns Wed, 11/23/2011 - 17:44
User Badges:
  • Cisco Employee,

NP.  As soon as I have the patch version this will be addressed it I will update this post.


Regards,


Robert

Robert Burns Thu, 12/15/2011 - 11:36
User Badges:
  • Cisco Employee,

Roman,


Didn't want to leave you hanging.  The fix for the CIMC address bug above is scheduled for 1.4(3) which is currently tracking for a Feb. release.  This is a tenative date as always.  I'll continue to update as things change/confirm/release.


Regards,


Robert

s.winiarz Sun, 07/08/2012 - 03:31
User Badges:

Hello,


We have the same issue with 3 ucs C210M2 servers.

Is there any news about solving this issue ?

I've looked in 1.4.3k firmware release note but it seems that it isn't still resolved...


Regrdas

Robert Burns Mon, 07/09/2012 - 05:10
User Badges:
  • Cisco Employee,

This was was indeed fixed as of 1.4(3).  The latest 1.4(3k) would also be included here.   Not all bugs resolved are documented in the release notes.


Robert

Actions

This Discussion