wesleyw Posted March 10, 2009 Posted March 10, 2009 (edited) I think one of the NIC modules has never worked however today I swapped them round and neither worked swapping them back made no difference so I am without any network connectivity at all. The lights on the NICs at back of the machine light up and flash when connected (while the blade center is powering up) but after the blade center has booted up and the blades start to boot the lights stop flashing and the OK light is illuminated (Meaning that it has power, has passed the POST and is operational ?) on both modules but there is no conenctivity. (I've tried different switches just to make sure). The config for the broadcomm Ctrl + S allows me in but nothing there says there is an issue or even gives me the option to see one. When running BIOS based diagnostics I get the following (not sure if it'll help any) Following error(s) were detected when the system was started. 1762 configuration error has occurred 162 configuration error has occurred I've also run the IBM diagnostics from windows I'll attach the file(s) if I can. Windows however will still detect the network cards and install them then give me the limtied or no connectivity warning. Wesibm.zip Edited March 10, 2009 by wesleyw Slight mod to the opening line.
wesleyw Posted March 10, 2009 Author Posted March 10, 2009 Right 1762 just means (Configuration change has occurred) Run Configuration/Setup However 162 means (Device configuration error) NOTE: Be sure to load the default settings and any additional desired settings; then, save the configuration. 1. Run Configuration/Setup 2. Battery 3. Failing device 4. System board Looks like somethings cooked. Wes
saundersmatt Posted March 10, 2009 Posted March 10, 2009 Right, wesley, you're talking absolute jibberish! Let's clarify a few point first. There is no such thing a a Blade Centre HS20. A Blade Centre with HS20 blades is what you mean, yes? How many blades? Are the all experienceing this problem? "The lights on the NICs at back of the machine light up and flash when connected" I assume you mean the network modules? What slots are they in? What make/model are the (Intel, Cisco and Nortel are common). If you configure 2 blade servers with local IP addresses can they ping eachother? I think I have an idea what your problem is, but you need to slow down and make me clear about what you're trying to do. Hope I can help Matt 1
wesleyw Posted March 10, 2009 Author Posted March 10, 2009 (edited) Little rattled at present It's an 8677 blade center running 14 HS20 blades. All are experiencing this problem. Both Blade Center Gigabit Ethernet Switch Modules (I did refer to them as modules as well in the original post) have the same issue all four ports flash whilst initialising and the ones connected to the network flash after this however once the POST has finished both modules display OK light but no longer Tx/Rx. They aren't the nortel ones but there isn't any identifying markings other than a serial number. They are in the network module slots 1 and 2. If you configure 2 blade servers with local IP addresses can they ping each other? I'll get back to you one this ASAP. Wes Edited March 10, 2009 by wesleyw
wesleyw Posted March 10, 2009 Author Posted March 10, 2009 Okay I've assigned IP addresses to them but no they can't ping each other? Wes
saundersmatt Posted March 10, 2009 Posted March 10, 2009 Okay, thanks so far. Have you plugged the blade centre management module into the network? Connect to that and go to: Monitors -> Hardware VPD, under I/O modules it will tell you the Manufacturer and Product Code of the modules (I'm betting they're Intel IXM5414E) Then I/O Module Tasks -> Configuration, give the network modules LAN ip addresses and see if they are pingable, and can connect to their web interfaces. For each module click go to the advanced configuration (from the chassis management module) and ensure that under advanced configuration ensure that "External management over all ports" is enabled Then I/O Module Tasks -> Admin/Power/Restart ensure that "external ports" are enabled for each module. Also connect to each Network Module, and ensure that each port is enabled (Admin Mode = Enable) Good Luck Matt 1
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 What software are you using to connect to the management console? Wes
saundersmatt Posted March 11, 2009 Posted March 11, 2009 (edited) It's got a built in web server. Should get an IP from DHCP but if you can't find it then you can connect to it from a machine as follows. The following topics describe how to connect a remote console to the management module to perform initial configuration of the BladeCenter unit. The management module has the following default network settings: IP address: 192.168.70.125 (primary management module) Subnet: 255.255.255.0 User ID: USERID (all capital letters) Password: PASSW0RD (note the number zero, not the letter O, in PASSW0RD) Matt Edited March 11, 2009 by saundersmatt 1
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 (edited) Got it asking me the the username and password but it's not USERID and PASSW0RD. Any way of resetting it? Wes Edited March 11, 2009 by wesleyw
saundersmatt Posted March 11, 2009 Posted March 11, 2009 From here. Insert a paper clip into the pin hole on the back of the advanced management module. Push the paper clip in all the way and hold it for approximately 10 seconds. The advanced management module will reset and the fans will run at full speed, which is clearly audible. Remove the paper clip from the pin hole. Matt 1
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 1 Ethernet SM DLNK n/a n/a 2 3104 ---- ---- J1WDJ47Y008 9308 CCFE DBAB 11D8 8C1D 000D 88E5 1B48 2 Ethernet SM DLNK n/a n/a 2 2604 26K6483 26K6482 J1W1F46S530 9AD6 91FA C053 11D8 8811 000D 88FB 3C68 Wes
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Ping Progress for Switch Module 1 Pinging 192.168.3.7: request timed out. Pinging 192.168.3.7: request timed out. Pinging 192.168.3.7: request timed out. Pinging 192.168.3.7: request timed out.
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Okay the NIC ports on the modules are now lighting up but they still can't find the network for some reason? Seeing as the management console is plugged into the same switch I know it's not the DHCP server or the switch itself? Wes
saundersmatt Posted March 11, 2009 Posted March 11, 2009 Have you ensured that the "External ports" is set to enabled? It will have disabled them when you reset the management module. Matt 1
saundersmatt Posted March 11, 2009 Posted March 11, 2009 That looks about right (Your interface is slightly different to mine). I'm at a loss now pretty much. Are you able to connect to the network module web interfaces? Matt
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Mines older lol. Nope no ping returns from internally or externally? Wes
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Strangely I've imaged some of the blades and haven't renamed them but when booting up complain of duplicate network names? Wes
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Right a further update on this. Ping Progress for Switch Module 1 Reply from 192.168.3.7: bytes=32 time<33ms Reply from 192.168.3.7: bytes=32 time<16ms Reply from 192.168.3.7: bytes=32 time<16ms Reply from 192.168.3.7: bytes=32 time<16ms (I put in our normal gateway address instead of the MM unit Duh!) This is via the web console. Wes
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Externally I can now ping the actual NIC modules and I'm currently looking at the web console for the first module. Why is this working and the HS20 Blade doesn't? Wes
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Ping Progress for Switch Module 1 Reply from 192.168.3.7: bytes=32 time<25ms Reply from 192.168.3.7: bytes=32 time<16ms Reply from 192.168.3.7: bytes=32 time<16ms Reply from 192.168.3.7: bytes=32 time<16ms Ping Progress for Switch Module 2 Reply from 192.168.3.8: bytes=32 time<24ms Reply from 192.168.3.8: bytes=32 time<15ms Reply from 192.168.3.8: bytes=32 time<16ms Reply from 192.168.3.8: bytes=32 time<16ms Bay 1 Display Ports Port State Speed/Duplex Connection Port Type Flow Control Ext 1 Enabled Auto 1000M/Full/802.3x 10/100/1000-T Enabled Ext 2 Enabled Auto Link Down 10/100/1000-T Enabled Ext 3 Enabled Auto Link Down 10/100/1000-T Enabled Ext 4 Enabled Auto Link Down 10/100/1000-T Enabled Bay 2 Display Ports Port State Speed/Duplex Connection Port Type Flow Control Ext 1 Enabled Auto Link Down 10/100/1000-T Enabled Ext 2 Enabled Auto Link Down 10/100/1000-T Enabled Ext 3 Enabled Auto Link Down 10/100/1000-T Enabled Ext 4 Enabled Auto Link Down 10/100/1000-T Enabled interesting that Bay1 looks okay but Bay2 even though I'm connecting to it looks down? Wes
saundersmatt Posted March 11, 2009 Posted March 11, 2009 I think that access the the management interfaces of the modules is through the bladecentre backplane, via the management module, not through the external ports. Odd i know but would explain your quandry. Keep trying Matt
wesleyw Posted March 11, 2009 Author Posted March 11, 2009 Erm unplugged the cable from the MM and I can still ping the NIC Modules? Arrrgghhh Wes
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now