Event ID 27 – “The description for Event ID 27 from source e1iexpress cannot be found”

KB ID 0001130 

Problem

I was seeing intermittent network drops on my Server 2012 R2 servers, so when I took a lot in the logs this was what I found;

[box]

Log Name:      System
Source:        e1iexpress
Date:          {time}
Event ID:      27
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      {host-name}
Description:
The description for Event ID 27 from source e1iexpress cannot be found. Either the component
 that raises this event is not installed on your local computer or the installation corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the 
event.
The following information was included with the event:
Intel(R) 82574L Gigabit Network Connection.
the message resource is present but the message is not found in the string/message table.

[/box]

Solution

I found plenty of people complaining about this error with servers running Intel physical network cards, but this was a virtual machine? Not only that, but a Windows 2012 R2 Datacenter Machine running on ESXi 6. Forums indicated that it was a problem with the NIC/Driver and that replacing the card had helped. I took a look at the vNIC on the virtual server and was surprised to see it was an E1000 card. This is the default in hardware version 11 for server 2012.

Looking in Windows it’s simply listed at an Intel 82574L Gigabit Network Card.

So I added another network card (a VNXNET 3).

Disable the original card. WARNING: Make sure you are on the console and not remotely connected when you do this!

Give the new card the IP of the old one, and don’t be surprised if you see this popup, CLICK NO.

Then you can remove the original E1000 card.

Related Articles, References, Credits, or External Links

NA

GNS3 – Can’t Save ASA Config – ‘%Error copying system:/running-config (Not enough space on device)’

KB ID 0000987

Problem

I love GNS3, it is a brilliant piece of software, I use it for bench testing and proof of concept work. Yes is can be a bit clunky sometimes, but it’s FREE! I had a project open with about four ASA’s on it, and it would not save the config on just one of them.

[box]

HostName(config)# copy running-config startup-config

Source filename [running-config]?
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
HostName(config)#

[/box]

[box]

HostName(config)# write mem
Building configuration...
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
Error executing command
[FAILED]
HostName(config)# 

[/box]

[box]

HostName(config)# copy running-config disk0:

Source filename [running-config]?

Destination filename [running-config]?
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
HostName(config)# 

[/box]

Solution

At first I simply deleted the ASA and added a new one, which annoyingly did the same. Then I read a post that said, do the following;

1. Open the configuration for the affected ASA.

2. Change the NIC Model to pcnet > Apply > OK > Stop the firewall > Start the Firewall.

HOWEVER, in my case the problem persisted, I eventually fixed it by formatting the virtual ASA’s flash drive.

3. Execute the following command;

[box]

HostName# format flash 

 

Format operation may take a while. Continue? [confirm]

Format operation will destroy all data in "flash:". Continue? [confirm]{Enter}
Initializing partition - hda: hda1
done!
mkdosfs 2.11 (12 Mar 2005)

System tables written to disk

Format of disk0 complete
HostName# 

[/box]

4. Power off, then power on the firewall, problem fixed.

Related Articles, References, Credits, or External Links

NA

GNS3 Cannot Connect Network Interfaces when running on VMware vSphere

KB ID 0000671 

Problem

I have plenty of real ASA firewalls to play with, but it’s getting round to re-certification time, so for ease I thought I’d run up a Virtual ASA on my vSphere 5 box just for testing and breaking.

However no matter what type of Virtual Network adaptor I used (vmxnet3, e1000, etc) I could not connect to the virtual firewall.

Solution

1. Firstly make sure you actually have an IP address in the correct range set on the ASA, and the interface is up.

Note: To connect a virtual ASA to the outside world you need to have a ‘Cloud’, then assign your machines NIC to the cloud. Finally you join the cloud to the ASA with a switch.

2. From my laptop (out on the network), I could not connect to, or ping the ASA 🙁

3. However if you log into your ESX/vCenter Server and change the settings on the virtual switch that the parent VM is attached to. Configuration > Networking > Switch > Properties > vSwitch > Edit > Security Tab > Change Promiscuous Mode to Accept > OK.

4. Now it works!

Related Articles, References, Credits, or External Links

NA