UCS 1.4(3M) BIOS Issue ? no network/san boot when diskless

Recreated faithfully on multiple blades and chassis with VIC cards. Have many SAN boot nodes in production and testing and after upgrading firmware this week anytime I apply my store policy of "diskless" to a blade I lose the ability to boot from network. After much effort to work around comes down to no matter what I do with diskless storeage policy, the configured boot order will never become the actual boot order. In the BIOS all network boot options/reference are invisible, cannot enable nor add to options. Upon removing diskless storeage profile and applying "any other that I have" I see in FST that it's powering up internal storage, starting up and updating pre-boot environments, and other things related that connected the dots. Returning to BIOS all reference and options have returned as I expected due to actual boot order screen updating to match configured order and hba's of course login the fabric right away, boot is fine. While I can faithfully replice across many, many blades, they are all the models with same mezz running 1.4.3 so curious if anyone else is seeing, particuaraly now with new version out, as I have done last few weeks without issues leading me towards the firmware.
In a nut shell I see that when going diskless this is actually shutting down the storage/raid controller. i can see that clearly but no bios access to it and not sure what else is or why it's affecting network and hba also since I cannot see, it's shutting more down than low powering drive side raid. I use different profiles due to some blades having disks removed, some retain them. moving a san boot service-profile dynamically around multiple chassis will fail to associate with errors on some due to disk setup and all that. some i have disks pulled and diskless based on documentation and best practices as this customer needed several san boot only blades in that pool. But yes if I use a storage profile allowing "any disk config" for association whether it has disks, no disks, raided drives, replaces the diskless policy in same service profile it faithfully follows my boot order and boots via hba's across multiple blades, up to about 8 or 10 as of today.....b200-m2's with vic's
thx
dave

My UCS manager firmware and Adapter is 1.3.1p,
the boot policy has been set to Boot to SAN,
I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
I can install the "windows 2008 r2 x64" successfuly...
Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
Thanks a lot

Similar Messages

Bios Switches A / B only boot when OC Genie button is on. MSI Z77 Military Grade

MSI Z77 Military Grade
1. Bios Switches A / B only boot when OC Genie button is on.
2. I normally use Bios B and upgraded the Bios from 17.6 to 17.12.
Flash was successful. I don't remember if I had the OC Genie button on or not.
But when I rebooted I couldn't get into the bios stuck at "A2" (thought I totally corrupted the bios
until I turned on the OC Genie from the motherboard.
However here is the quandary:
3. Neither A or B Bios will boot without the OC Genie button on.
4. The system will cycle twice than stop at A2
5. Eventually I would like to have both Bios-es working optimally.
Thanks for taking the time to read my post.

remove power cord from the PSU and do >>Clear CMOS Guide<<

Weird issue starting network at boot [Solved]

So, whenever i bootup, when it comes to starting the network, it hangs for a few seconds, then says 'fail', however, whenever i get gnome up and working, the connection is working just fine, so far, i have tried to increase the timeout though it doesn't really seem to make it wait any longer during boot...here is my rc.conf if it helps anyone, also, i am trying to connect to some NFS shares from my freeNAS box on boot, but since that fails, the network shares normally do to, but after booted, i can just do mount -a and they all connect just fine...its weird
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(sky2 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !usblp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.2.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng dbus hal fam network rpcbind nfs-common netfs crond)
also, i do have 'myhost' added to my hosts file as well, did so during setup...
anyone got any ideas?
Thanks
Last edited by psilo357 (2009-12-21 00:02:46)

alright, if just backgrounded 'network' it woudl cause rpcbind to start after it, but fail, so i backgrounded them all, and while network no longer says FAIL while booting, the network drives still don't mount, i still have to issue a mount -a after boot to get everything mounted...
thanks for the tip though. I don't mind it not running in background and waiting an extra few seconds to get everything setup as i want it to be as soon as i am logged in, just want it to all start correctly.
EDIT: alright, all network drives ARE mounting correctly on boot if nothing is in background, but i still don't like that network says FAIL when it is starting up, though it is apparently working...
all help is appreciated.
Last edited by psilo357 (2009-12-19 20:31:27)

Issue with PC not booting when PCIe 8360 attached to controller PXI 8360

I am using a PCIe 8360 in our Windows 7 PC and connecting it to a PXI 8360 controller in a Pickering chassis. When I connect the mxi card to the controller and try starting the PC, the PC will not boot. Has anyone seen this issue and if so, what is the problem/solution?

It sounds like this may be an issue with BIOS compatibility. I have included some more information below. I would recommend upgrading the BIOS to the latest version and seeing if that resolves the issue.
http://pcsupport.about.com/od/fixtheproblem/ht/accessbios.htm
R. Brill
Applications Engineer
National Instruments

San Boot Win2K8 R2 SP1 x64 on UCS blades B with M81KR installation issue

I am trying to install a storage San Boot Win2K8 R2 SP1 x64 on UCS blades,(There are only 1 path to the OS installation drive during the installation.)
I loaded drivers for the M81K2 following the "UCS Windows Install Guide" , and I can see the LUN I mapped from XIV. I was able to create and format partitions, make it online, but when
I try to install, windows gives the error:"Windows cannot be installed to this disk. The computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu."
any one know this issue?
Thanks

My UCS manager firmware and Adapter is 1.3.1p,
the boot policy has been set to Boot to SAN,
I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
I can install the "windows 2008 r2 x64" successfuly...
Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
Thanks a lot

HT4623 i have issue with my iphone5, the phone is open and good network signal, but when some one calling me they cant reach me, like the phone is off

i have issue with my iphone5, the phone is open and good network signal, but when some one calling me they cant reach me, like the phone is off

You are as far as you can be with the original iPad; only iPad 2 and greater will update to 7+

My itunes account shuts down for no reason. It wont recognize my iphone and there is an issue with network connectivity and itunes. I have already reinstalled itunes and did a syste restore on my computer, firewall checked and virus scan done. Ideas??

My itunes account on windows xp shuts down for no reason. If even try to delete something from my library it shuts down. It wont recognize my iphone and there is an issue with network connectivity and I can't connect to the store. I have already reinstalled itunes and did a system restore on my computer, firewall has been checked, itunes is ok on firewall and virus scan done. Ideas??

Same problem. I can see the itunes store so not a problem with windows firewall. The account is active on my iphone so i know i am not locked out. I can connect the PC to my iphone so i know itunes is working ok. It is just logging into itunes on this pc which doesn't work. Only thing I can think of is that the email address I use for my apple id has been offline for a while and is working again now, I'm wondering whether this has been the case for others who are having this issue?

Having issues mapping network drives

Having issues mapping network drives to my Mac. I trying to use samba, the name of the server is Media_Server and I want it to connect to volume_1. So I put int smb://mediaserver/volume1 and I get an error.
Can anyone tell me what I'm doing wrong?

I'm not sure, but when I want to connect to the desktop my other Mac on my home LAN I use:
smb://192.168.1.105/johna/desktop

MOVED: Power of the Press - Neo4 Bios Issue - Can Anyone Test This?

This topic has been moved to Overclockers & Modding Corner.
Power of the Press - Neo4 Bios Issue - Can Anyone Test This?

This topic has been moved to Overclockers & Modding Corner.
Power of the Press - Neo4 Bios Issue - Can Anyone Test This?

Samsung Galaxy S3 Issues - No Network Connection! Please Help.

I have had my S3 for a few weeks now with no issues.
Suddenly in the last two days, my phone is silent for a while, which is uncommon. I generally have a consistent stream of notifications, emails, texts, etc. So when I picked up the phone, the 4GLTE signal is usually located, I saw a Ø icon. I thought that was weird but thought maybe I was in a bad coverage area. So I walked around outside the office building and got a notification when I clicked the Internet app, "No Network Connection."
Of course, I initially thought the SIM card was maybe messed up. I restarted the phone, and all was well. Then yesterday, the same thing! Now this morning my alarm goes off at 4:30am like always - only I get up to get ready for the gym and I see it's only 3:30. The auto-detect for time zone is wacky.
Upon googling no network connection with the galaxy, I see some S2 users had this same issue. Is this a phone issue? Network issue? SIM issue? It's done it twice in the last two days, so I don't know if I need to contact Verizon or what!
Thanks for any advice you can give.

It's really funny that anyone believes Verizon when they say an OTA is coming "soon" or "next month" or "next week". They only tell you these things to placate you and get you off the phone. They have no idea when an OTA is being rolled out!!!
Verizon is the absolute worst provider when it comes to timely phone updates. How long did it take for Verizon to update the Nexus compared to the GSM version? 6+ months!!
Be prepared to wait that long for an OTA to fix the dropped call issue, the data reception issue, the SIM card issue and the time zone issue.

Critical Issue with Network

Hi Team,
I have been using Lenovo P780 past one year. From Two months am facing a mojor issue with Network. When am connecting the device with WIFI then after few min. my GSM network goes down even after Turn off the WIFI. After a Hard rebot of the Device also am not able to get any GSM network on my Device. Please help me to resolve this issue. Am expecting more from Lenovo Technical Team.
Note : Am unable to Get GSM network in my P780 Device after using the WIFI.

there was no error occured in AE monitoring as per logs it processed successfully, but receiver party which is outside organization network complained saying that they receive this file empty.
Logs for your reference received by third party:-
2011-08-26 08:23:35 XXX.XXX.XX.XXX 21 980 XXX.XXX.XX.XXX 33081 3172 XXXX-X-p@br 0 0 File Name 3 >>FILE INFO: D:\ftp\kunden\File Name was opened. Sharing is 1. File Handle is 0x00000b24.
2011-08-26 08:23:35 XXX.XXX.XX.XXX 21 980 XXX.XXX.XX.XXX 33081 3172 XXXX-X-p@br 0 0 File Name 3 Did not receive any data, Error=1506, SubError=0, WSAError=0
2011-08-26 08:23:35 XXX.XXX.XX.XXX 21 980 XXX.XXX.XX.XXX 33081 3172 XXXX-X-p@br 0 0 File Name 15 >>FILE INFO: D:\ftp\kunden\File Name was closed. File Handle is 0x00000b24.
2011-08-26 08:23:35 XXX.XXX.XX.XXX 21 980 XXX.XXX.XX.XXX 33081 3172 XXXX-X-p@br 0 0 File Name 15 Finishing STOR, Triggering events manager for FX_EVENT_FILE_WRITE_SUCCESS
2011-08-26 08:23:35 XXX.XXX.XX.XXX 21 980 XXX.XXX.XX.XXX 33081 3172 XXXX-X-p@br 0 0 File Name 15 RESPONSE: 226 Closing data connection. Transferred 0 bytes in 1 seconds. 0KB/second.
where in PI we could see message contains data and message has been successfully processed, could it be issue on receiver end?
thanks.

Bootcamp issue with network connexion

Hi,
I just install windows seven on macbook pro. Windows works fine but i have a network connexion issue. Network card (wifi and ethernet) doesn't work. When I instelled windows, bootcamp download drivers for windows 64bits.
My questions :
- How can fix this network connexion ?
- Where can i download broadcomNetworkAdapter32.exe ? (for connect to internet and install correctly all driver)
Thanks

Did you download and then install the Windows support software according to the Boot Camp instructions? You install the Windows support software from within Windows after you install Windows.

Many issues with network of 2 AE and one AEBS

I have a well functioning small WDS network of two airport express (AE) stations, a wireless printer, a G4 iMac and a 12" PB. One of the AE is hooked into the cable modem with an ethernet cable and is set-up as the main base station. The other functions as a remote to extend the network.
I bought an Airport Extreme N base station (AEBS). My intention is to use it as a a file server. I've attached a powered USB hub and two USB hard drives to it. I'd also like it to be available on my existing WDS network, so I needn't change networks everytime I want to access files through the AEBS.
The AEBS has version 7.0. I haven't been able to update the version in Airport Utility, because it kind of hangs up (stays at 0%) and then fails.
Problems:
1) to solve the firmware update issue: Do I need to set-up the AEBS to access the internet first? When I'm on my small WDS network, I can't see the base station, since it is setup as a separate network. When I switch to the AEBS network, obviously I do not have internet access. So how do I update the firmware? What could be the reason for the update error?
2) The AEBS file sharing network was available yesterday, but today I can not access it from my Mac (neither the Mac nor the AEBS was put to sleep or powered down during that time). I was in the process of erasing the whole HD so I could do a fresh wireless backup. The menu bar icon for the airport disc shows my AEBS disk, but I can't connect to it. I enter my password to access the AEBS network and then the connection fails. What could be the cause? Do I need to reset the AEBS everytime? Is there an automatic logoff somehwere I need to disable?
3) I tried manually setting up the AEBS to join my WDS network. I followed all the instructions: i.e. adding the MAC address of the AEBS to my main station setup and indicating the AEBS to participate in a wireless network as a remote relay and adding the main station MAC to the setup. Channels are set-up automatically. DHCP is also automatic. However, I get an eror message when updating it. Basically it will say someting to the effect that the AEBS can no longer be found. What could be the cause of this?
(Airpot Utility worked great when I added my second AE to the WDS network. But when doing exactly the same for the AEBS, I get error messages as above.)

I solved all my problems mentioned above. It took a while to figure out.
First I discovered that connecting the Airport Extreme N Basestation (AEBS) to an existing WDS network gave me continuous errors: I couldn't update the firmware from 7.0 to 7.1.1 etc.
So I reset my Airport Express (Ax) which was previously acting as a remote and I reset the AEBS. I kept the Ax (which was acting as a main station and is attached by ethernet to the cable modem) as is. I set up all 3 near each other.
While keeping the reset Ax and AEBS in default settings, I selected my existing Network in the airport menu icon and then I selected the AEBS in the Airport Utility and was able to update the firmware of the AEBS.
Settings for the Ax acting as a main station: WDS settings: Participate in WDS; allow wireless clients. Internet: I set connection sharing to "share public IP address". DHCP and NAT at default settings. Channel 6. ( I discovered that the main station and the two remotes need to be on the same channel!). Set up as a main station, allow wireless clients and and added Mac addresses of the Ax and AEBS. Updated.
Then I started by adding the AEBS the WDS Network created by the main station: participate in network; allow network to be extended = off. Set up as a WDS remote. Allow wireless clients. Added main station Mac address. Internet connection sharing = off. File sharing enabled. Channel 6. Updated.
Same set-up for the Ax as a remote.
Now I can access my two USB drives wirelessly over the network and each remote has an IP address.
I did a speed test over my wireless connection for internet speed. Results: Download: 9442 kBit/s
Upload: 1006 kBit/s
Answer time: 13ms
So everything is OK!

K8N Bios issues

I running into some strange bios issues.
If you increase your FSB in the bios past 210 or so the Raid array is no longer detected on SATA 1 and 2. You then have a hell of a time getting back into the bios. No matter how many times you hit the delete button during the boot. Once you are able to get into the bios and lower the FSB your boot order has changed and the Raid array is no longer the first in order?????????????
Whats up with that. Come on MSI get us a good bios. This release version is pretty buggy. If you look at all the reviews on this mobo, take a look at the bios they are using. The Cell menu is located on the Left half of the screen not on the Right like this bios. It seems it also clocks much better than this thing, as I have never heard of any problems on the review sites about dissapearing SATA arrays, unlike I have here on this and other forums.

And that my friends is known as a System Crash. When first running a new system, give it a day or so running at stock settings before going in and changing for increased performance. It may sound "Old-fashioned", but I really believe in letting electronics "burn-in". Then, when you do make changes - make them one at a time, and in small increments! I think this board is really a good one. Aside from slightly higher temps than my 64 3000+, I think it was easier to get running, and a lot more stable.

U160 netbook BIOS issue

Hi,
Today when I turned on my U160 the BIOS was stopped at the boot screen with the MSI logo. I tried disconnecting the power cord and the battery as well but unfortunately nothing helped. Every time turned on it stopped at the MSI logo and not reacting on any buttons. Sometimes holding the power button for more than 5 seconds did not turn off the power either, so I had to remove the battery in order to turn off the computer.
No I haven't tried to do BIOS flashing prior that, but after that I was just wondering if now I could do at least a BIOS upgrade would be really good. Unfortunately it was not possible to boot any OS, so I had no chance to do any BIOS operations except for the HW intrusion.
So I decided to try to fix it in the hard way. The warranty period was over, so I brought my U160 to the electronics HW lab at my workplace and disassembled it completely. I managed to find the BIOS flash chip so I removed it using a hot-air soldering station. We have a flash programmer called DediProg here, so I hooked up the chip in a socket and flashed with the latest BIOS image release (N051EMS1.423 1.0D 2011-05-13).
After that I soldered the chip back to its place and voila - the U160 booted correctly again.
Right know everything looks good, but I have some concerns about that...
- it looks like the BIOS can kill itself after several boot-ups (I have no idea how.)
- in order to repair, you have to have soldering skills
- a flash programmer equipment is also needed for this operation
As a conclusion I think this is a very serious problem and I hope it has been fixed in this new BIOS release.
If there are any technical people who are interested in the old image I saved before flashing, I can send it over.
///Alpy

I don't really agree.
1) I haven't tried any BIOS updates, I was satisfied with the old one.
2) During the boot process the BIOS writes to the flash certainly. If you disconnect power at the right time you can corrupt the BIOS image. I spent several years working together BIOS developers and we came across this problem at every new Intel CPU generation. (I'm a hardware designer and we are building server motherboards based on Intel chipsets.)
However the chip can get corrupted for many other reasons, but since the manufacturer of the flash (Winbond) guaranties 10 years data retention, I would not really suspect such issues. Anyway if I will have the same problem again within 1 year I will replace the chip. (Fortunately, we have several new parts here in the lab.)

UCS 1.4(3M) BIOS Issue ? no network/san boot when diskless

Similar Messages

Maybe you are looking for