X2200 M2 ILOM unaccessible via TCPIP

We have three new x2200 M2 servers. After setting the ILOM IP addresses via serial connection, I can only reach two of the three addresses and manage accordingly.
IP addressing is correct (172.16.254.X under subnet of 255.255.255.0 with no gateway (no Internet traffic)). Server seems to work fine otherwise.
Anyone have a similar experience?
It could just be bad hardware but one would think the interface would exhibit anomalies when setting via the serial port. Tried different cables and switches to yield no change.
Thanks in advance for any input.

Even if you could slow the 2200M2 fans down; all you'd accomplish is to cook the server.
Find a 3-4U rack mount box, or a desktop. Fan noise is a function of RPM; a 1U fan must spin MUCH faster to deliver the same air as a bigger diameter one.
Edited by: rtfm-fr on Oct 6, 2009 4:27 PM -- typo

Similar Messages

Communication via TCPIP with an oscilloscope

I try to communicate via TCPIP with a digital oscilloscope (Tektronix TDS3000B series). First of all; Is that possible or do I need a GPIB interface? Where can I find an exact description of the commands? So far I could build a connection, but nothing happens on commands like "clearmenu", ... Is the protocol I am using anyway GPIB? I found a labview file tktds3k.vi - could I use or modify this file.
I'm happy about any kind of suggestions-there must be someone communicating with an oscilloscope!? thanks, Felix

Are you sure that your scope supports VXI-11 for TCP instrument communication? Given IP 192.168.0.1, this VISA resource descriptor will access a VXI-11 instrument (VXI-11 specifies the ports for communication in its specification, so you don't need this in the descriptor) "TCPIP::192.168.0.1::INSTR".
If your instrument does not support VXI-11 and you want access it via VISA using straight TCP to a specific port number (port 5555 in this example), use the descriptor "TCPIP::192.168.0.1::5555:OCKET". Also, make sure you are running a newer version of VISA since VXI-11/ Raw Socket support hasn't been around as long as VISA has. If it's referenced in the helpfile (for viOpen) then it should support these resource descriptor formats.
Hope this helps.
Scott B.
GPIB Software
National InstrumentsMessage Edited by ScottieB on 04-11-2005 09:55 AM

T5-2 ILOM authentication via Active Directory

Hello,
We are trying to leverage AD to authenticate our ILOMs. However I am seeing the following when I set the method to None (server authentication)
(ActDir) ServerUserAuth - Error 0, failed to validate user group access
We have a group defined and I have set it under Admin groups using the DN.
Any ideas on this or has anyone been successful getting this to work with AD and AD Groups?
TIA.
Jeff

Hello Man !
your provided documents and links are very effective. thank you guy for your help. right now i have to problem below listed,
I have Cisco aironet 1142n access point. I have no ACS / WLC
but want to authenticate end users 802.1x with Active directory 2003/2008 using RADIUS (IAS/NPS).
These APs are standalone. Please provide any configuration document
"How to authenticate end users with active directory using cisco 1142n Standalone (Without WLC/ACS)".
Thanks & Regards,
Rizwan Haider Siddiqui.

I can't send anything over 1024 bytes by using visa via TCPIP

I am trying to use NI-VISA talk to instruments visa TCPIP. The problem is I can not send anything over 1024 bytes using viPrintf or viBufWrite call. A time out will be returned. I tried to use MAX to open a VISA session for my TCPIP device. If I put a string less than 1024 bytes in write buffer, it is fine. Anything longer than that will cause time out and some time the whole MAX crash.

Hi Johnma,
I suggest you check the specs on TCP/IP. I seem to remember a limit on the packet size. TCP is just the transport layer. Higher layers should handle the work of breaking packets into smaller sizes and tracking packet sequencing.
I am relying on memory hear so please verify. (maybe the limit was 4096 and I am full of it).
I also believe there was some discusion of a related topic recently on info-labview where Rolf did a good job explaining what was happening.
Search for "Rolf" and "TCP" on Brian Renkins search engine.
http://infolv.brianrenken.com/
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Modbus RTU Command Via TCPIP and Receive The Holding Register Value

I have connected Energy Meter with Modbus to Ethernet Conveter Via RS485. My Slave Id:1. Mode: RTU. I want to read holdig register values from 3911 to 3920. I have formatted the modbus command and write to tcp write and read the value from TCP read. I have getting invalid values while decoding.
Please provide your suggestion.

Hi,
If I am right you are sending serial ModBus data to the TCP link and you don't handle the received data correctly.
You also are using the wrong port. Default port 502 is used for ModBus TCP.
Here is an example how it could be done. Data in is the loopback command.
Data out is the TCP data without the slave address and CRC of the serial data
Kees

X2200 M2 iLom issue on OS X

I can not seem to bring up the console through the web interface on a Mac running OS X.
I can manage the server with the power-on, off, etc... Just not the console.
I have tried both Safari and Firefox (1.5 & 2.0). On the Windows and Solaris (running Mozilla) platforms, it works like a champ.
Bringing up the debug/error window in Firefox on OS X, this is the error I get, any insights?
Error: [Exception... "'Permission denied to get property XULElement.accessKey' when calling method: [nsIDOMXULLabelElement::accessKey]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame :: https://192.168.1.11/timeout_action_forlaunch.cgi :: <TOP_LEVEL> :: line 5" data: no]
Source File: https://192.168.1.11/timeout_action_forlaunch.cgi
Line: 5

You know, it wouldn't irratate me so bad if it was a problem with Safari, but it's a problem with the JVM on the MAC.
It doesn't matter which broweser you use on Windows... Firefox, Opera, IE, they all work no problem. Same goes for any Solaris or Linux.
I think there is an issue with Apple being the ones responsible for maintaining the JVM for the MAC platform. I'm not sure whose fault that is.... ie: Did Sun say we aren't going to develop it for the MAC and Apple picked up the slack, or was it Apple saying... "We'll do this better"....
Regardless, I have downloaded even the latest JVM from the Apple developer site and it has the same problem. This is very irratating as we are an all MAC shop, and PowerPC based, so I have to load up a very SLOW Virtual PC just for an IE session to bring up the console.... Arghh!!!
If there are any updates, lemme know!

X2100 M2 & X2200 M2 ilom and Mac OS X's Java

For some reason OS X's Java will not run the remote KVM. It works fine on Windows, Linux and about any other platform I have tried, but I'm running 10.4.8 on a PPC (have tried several workstations) and when I first log in through the web interface (Safari, have tried Opera and Firefox too), I can see the minature console, but when I click the "Launch", it starts up, with the usual "trust" this and that...
Then the Virtual KVM pops up, but before I see the screen I get a small pop up that says "Connect to Remote Host Fail!", once I click "OK" it closes the whole KVM.
Anyone have any ideas?

You know, it wouldn't irratate me so bad if it was a problem with Safari, but it's a problem with the JVM on the MAC.
It doesn't matter which broweser you use on Windows... Firefox, Opera, IE, they all work no problem. Same goes for any Solaris or Linux.
I think there is an issue with Apple being the ones responsible for maintaining the JVM for the MAC platform. I'm not sure whose fault that is.... ie: Did Sun say we aren't going to develop it for the MAC and Apple picked up the slack, or was it Apple saying... "We'll do this better"....
Regardless, I have downloaded even the latest JVM from the Apple developer site and it has the same problem. This is very irratating as we are an all MAC shop, and PowerPC based, so I have to load up a very SLOW Virtual PC just for an IE session to bring up the console.... Arghh!!!
If there are any updates, lemme know!

X2200 iLom and Watchdog timer...

I have setup our x2200 and have the iLom working great for most things.
I have two specific problems going on with it though....
First, sometimes the iLom just stops responding, I can't SSH, use the WebGUI or anything. I'm using the same mgmt. port for the global zones IP, which I can still log into. Once I log into the domain, I can reboot the server, or power it down and then the iLom starts responding again. Any ideas?
Second issue is that if I turn on the watchdog timer in the BIOS it will reset or power cycle (depending on which setting I setup) once the timer expires, even if booted into the OS. This is very disturbing, because I can't use the watchdog unless I want to reboot every five minutes. :/
Now I am installing the minimal Solaris 10 SUNWreq cluster, but I'm adding a number of packages back into the jumpstart session, including TCPWrappers. Is there a specific package that needs to be installed as part of the Solaris base install in order for the Watchdog to determine if the OS is up and running or should I open a hardware trouble ticket on the new server?
Thanks!
Information
Error in the ILOM Error Log:
OS Load Watchdog timeout cause STR_POWER_CYCLE1
Server x2200 M2
ILOM Version
BMC Version : 1.20
BIOS Version : S39_3A10
Description BMC Board Information
Device ID 5
Device Revision 0
Firmware Revision 1.20
IPMI Revision 2.0

Did you ever figure this out? I have been having the same problem since receiving my x2200 M2 a couple of months ago. I'm running the latest OpenSolaris and the watchdog timer will reboot continuously until it seems to give up and then just stops rebooting. I have a feeling it also disables the watchdog timer at that point.
Another frightening thing this server does is leave the power off, even when bios is configured to power on after a power failure!

Sharing internet while hooked up via ethernet

Hi,
I want to hook two computers (one 10.3 one 10.4) via ethernet to each other. I also want to hook one up to an airport via its airport card then share the internet (the 10.4 one is the one connected to the airport).
How would I go about this? I can't figure out how to allow airport connection via tcpip while I'm using tcpip for the ethernet connection.
I am sure this is posted here somewhere but I can't find anything specific (step by step instructcions).
I have figured out how to network the two computers via ethernet.
Thanks!
Misha

Hi Misha,
The exact thing you want to do is configured via:
System Preferences > Sharing > Internet
(Ref: http://docs.info.apple.com/article.html?path=Mac/10.4/en/mh336.html)
In your case you will set this up on the 10.4 machine, where you will share your Aiport connection and allow other computers to connect via the ethernet connection. (ie. airport is set up in Network preferences, and ethernet is set up in Sharing preferences)
Note the advice about turning on Personal Web sharing also. (This should mean your 10.4 firewall will allow pass-thru connections from the 10.3 machine)
Graham

ASA 5520 with multiple contexts becomes unresponsive

Hi all. We have encountered a perculiar problem with a pair of our ASA 5520 firewalls with 2 contexts(each context being active on different ASA). What we are seeing is that sometimes when we have a sudden increase of inbound traffic(mostly HTTP) towards servers behind the firewalls they seem to go bananas for the lack of a better expression.
They become unaccessible via ssh and the traffic drops significantly. The problem is mitigated by disabling one of the monitored interfaces for failover(on one of the switches the firewall is connected to) so that both contexts become active on one firewall. After that the firewalls seem to come to their senses and we can enable the switch interface again but sometimes one of the pair needs to be rebooted to restore full funcionality.
To us it seems like there is a problem with failover and contexts but we haven't been able to pin it down. The failover link isn't stateful and when we tested the failover it works fine both ways with each ASA taking up the full load when the other ASA of the pair is not available.
Did anyone come across a similar situation with their firewalls?

We are using ASA version 8.2(5).
The configuration of the failover is:
failover
failover lan unit primary
failover lan interface fail_int GigabitEthernet0/3
failover interface ip fail_int x.x.x.x 255.255.255.252 standby x.x.x.x
failover group 1
preempt
failover group 2
secondary
preempt
Output of the "show failover":
This host:    Primary
Group 1       State:          Active
                Active time:    399409 (sec)
Group 2       State:          Standby Ready
                Active time:    111 (sec)
                slot 0: ASA5520 hw/sw rev (2.0/8.2(5)) status (Up Sys)
                  admin Interface out (x.x.x.x): Normal (Waiting)
                  admin Interface inside (x.x.x.x): Normal (Waiting)
                  admin Interface dmz4 (x.x.x.x): Normal
                  admin Interface dmz1(x.x.x.x): Normal (Not-Monitored)
                  C1 Interface out (x.x.x.x): Normal (Waiting)
                  C1 Interface inside (x.x.x.x): Normal (Waiting)
                  C1 Interface dmz5 (x.x.x.x): Normal
                  C1 Interface dmz1 (x.x.x.x): Normal (Not-Monitored)
                slot 1: empty
Other host:   Secondary
Group 1       State:          Standby Ready
                Active time:    0 (sec)
Group 2       State:          Active
                Active time:    398992 (sec)
                slot 0: ASA5520 hw/sw rev (2.0/8.2(5)) status (Up Sys)
                  admin Interface out (x.x.x.x): Normal (Waiting)
                  admin Interface inside (x.x.x.x): Normal (Waiting)
                  admin Interface dmz4 (x.x.x.x): Normal
                  admin Interface dmz1(x.x.x.x): Normal (Not-Monitored)
                  C1 Interface out (x.x.x.x): Normal (Waiting)
                  C1 Interface inside (x.x.x.x): Normal (Waiting)
                  C1 Interface dmz5 (x.x.x.x): Normal
                  C1 Interface dmz1 (x.x.x.x): Normal (Not-Monitored)
                slot 1: empty
Stateful Failover Logical Update Statistics
        Link : Unconfigured.
When I disabled the monitored interface it was always the same interface altough I believe the same effect could be achieved with disabling any of the monitored interfaces.
As for memory and CPU when it happens I cannot access the units to get a reading but I asume it's through the roof.
The thing that troubles me more is that the situation persists when the load drops and I have to perform the solution from the first post. One would assume that with the drop of the load that both firewalls would start to behave normally.
And I see that I haven't mentioned it before but when the load drops both units continue to handle traffic normally but I sometimes see as a side effect that I cannot SSH to one of the units. That unit usually has to be restarted.

RS-232 through TCP/IP with LabView

Hello
I currently have a serial device being read through a hardware RS232 to TCP/IP converter.
On the computer with labview I use a third party virtual serial port that reads the TCP/IP data and converts it pack to COM port data.
I then read the COM port normally with VISA.
I would like to remove the third party TCP/IP to RS232 software and have LabView read the TCP/IP port and convert to serial.
How would I achieve this?
More details on the hardware and 3rd party sofware;
thydzik.com/monitor-cms2000-inverter-via-tcpip-usr-tcp232-e4-rs232ip-convertor/
More details ont he labview code here;
thydzik.com/log-solar-generated-to-pvoutput-with-labview/
Solved!
Go to Solution.

I don't think it's as complicated as you seem to expect. Try the VISA TCP approach. Create a VISA TCP resource, in raw mode, as explained in the white paper. Take your existing code, replace the COM resource with the new TCP one, remove the serial port configuration, and it might just work. Make sure you close the resource when you stop there program.
If you want to go with the TCP functions, take a look at the examples. You open a connection, read and write strings to it exactly as you would with a serial port, and close it when you're done.

The Story of 2 iPads - Side by Side Wifi

Im sitting beside my friend, both with the same iPad (16Gb version) both accessing the same Netspeed.net server using the same wireless router. My download speed is 5 MB and his is 24 MB. I have one bar on the wireless signal he has full strength. We checked our connection set up and as far as we can tell they are the same. He is a Cisco CCIE so he knows his stuff. What gives??
Jim

Check to make sure network settings are the same, and then trade iPads and run the test again. Also swap seating positions and try again. You may be quite shocked by the outcome. This is RF we are talking about, and is influenced by everything from the Water Content of your body, to how much metal is between you and the Transceiver.
The higher the frequency, the more fickle things become. 2.4 ghz is a fairly high frequency, with a very short wavelength, so absorption of the signal is a real problem.
Have your ever wondered why wireless networks needed to be 54 MB/sec+, when the average bandwidth was less than half that, and still is in most cases, even with FiOS? WiFi via TCPIP is like one big party line, with lots of data collisions and retransmissions happening.

Fiery 250 driver and new Intel Mac

I recently installed a new Intel iMac in my office and hooked it up to our Xerox printer via our Fiery 250 RIP. Bad news--the driver does not work with the Intel Mac. I had a Xerox tech come and try to troubleshoot it for a few hours, went under the hood to try and resolve the issue...nothing. Next step is he is going to have to contact Fiery. Anyone else have any experience with an Intel Mac and getting the driver to work on Fiery? Very inconvenient.
Intel iMac Mac OS X (10.4.5) Intel Mac-Fiery RIP

i can give you a tip.
download the ppd from the support page.
install it via tcpip and select the ppd.
it will work to print, but no special features then.
andy
powerbook g4 Mac OS X (10.4.6)

Labview (client) and corba/CDR(server)

Hello all,
I am trying to write some VI's that will send data via tcpip to another PC to a application/server that uses corba/CDR (common data representation).
I haven't been successful. I have looked into endianess issues and I am sure I am using it correctly.
The data sent is packetize in the applications format.
Is this even possible?
thanks,
Joseph
Message Edited by J3K on 04-09-2008 03:01 PM

Hi Joseph,
There isn't a lot of information on Corba with LabVIEW. You might check this discussion forum. Additionally, this KnowledgeBase might also prove helpful as a starting point.
Regards,
Hillary E
National Instruments

NI MAX cannot see / looses network instrument

There appears to be a bug with NI MAX where a network instrument which was previously configured suddently dissappears and when we attempt to re-establish the instrument, MAX claims that it cannot find the instrument.
This was seen on 4 different stations, all sharing the similar behavior. This was also seen at a completely different customer where the configuration was setup by a fourth person. At client # 1 there are 4 stations. They were setup by 3 different people using the same instructions. Everything was fine on all 4 stations. All of a sudden, the information dissappears from the network instrument list and it is not possible to re-configure the network instrument within MAX. A similar behavior was reported by another client which is totally different than the first client. NI MAX was configured by a different person than at client 1, possibly using different steps (although it is quite simple to setup a network device within NI MAX).
NI MAX at client #1 are versions 5.40f0 and 14.0.0a2.
NI MAX at client # 2 is version at least 14.0.0a2.
If we copy an exported settings file from another station, the network devices are restored and it is possible to use the network instrument. However, if you attempt to setup the instrument manually, because MAX cannot find it automatically, it is not possible to validate the instrument and complete the setup. Even if you cheat and complete the setup, the PC will not communicate with the instrument via VISA. However, it is possible to communicate with the instrument outside NI MAX. The instrument is seen by the PC and does respond to ping requests.
See image below.
When trying to validate the instrument, NI MAX responds with the fact that it could not open a VISA session via TCPIP.
My first question is: why does the instrument dissappear in the first place?
Rebooting the PC did not help. Basic troubleshooting did not resolve the issue. This is not the first time I work with NI MAX and with network instruments; however, this is the first time I see them dissappear fromNI MAX.
I did not find anything while searching for posts for similar issues, so I do not know if anyone else has seen this. I did encounter a similar description for a bug that was supposidly fixed in MAX 5.4
Does anyone at NI have a clue at how to make NI MAX more solid with respect to network instruments?
Thanks,
RayR
Attachments:
badMAX.png ‏190 KB

Hello AK2DM,
I was just north of you last week in Sedona. Beautiful place. Our next trip in your area will take us to Phoenix. We'll have to get together.
There are no dependencies on any NI Services that I am aware of. A customer just reported a similar issue at their Penang CM site. They are now in a bit of a panic. I did not work on the code at that site, but 3 sites, 2 customers reporting the same issue??? That's not a coincidence. Something is wrong with MAX. The only way to recover is to import the configuration file within NI MAX. It was impossible to simply scan for the instrument to get MAX to communicate with the instrument, although the PC, that has NI MAX installed, is able to ping the instrument.
I may have seen a similar issue a few years ago with another client where we kept loosing the network communication, but gave up and switched to GPIB. At the time, we thought the network switches were causing issues and blamed it on the network. Today, I may think otherwise... I do not know what to investigate to verify why this is occurring. Strangely enough, these systems ran for a year before we started seeing the symptoms. I thought windoze upgrades was turned off... It may be related to some recent upgrade, because we only started seeing these unusual behaviors since November (?). I can't remember exactly when we first saw it. Late fall / early winter??
It is strange that you started seeing an odd behavior around the same time. Running windoze, right? I never liked windoze... Everyone should move to Linux/Unix/Solaris. LOL!

X2200 M2 ILOM unaccessible via TCPIP

Similar Messages

Maybe you are looking for