It's trying both port 22 (ssh) and port 23 (telnet). Usually sys admin's aren't leaving telnet running or open as often these days, so port 22 is most likely the only *real*option. Because ssh is working, you're getting the CI's to update correctly. You can either safely ignore those messages, or configure the discovery for "ssh only" in the method section instead of "both" if you know you aren't going to be needing telnet.
See here <http://documents.bmc.com/supportu/documents/94/93/99493/99493.pdf>on page 271. (may require a bmc login) On Wed, Dec 16, 2009 at 2:20 PM, Kathy Morris <kathymorris...@aol.com>wrote: > ** > Hi All > I thought I understood, but now I am totally confused. > > In my discovery report it says > I am discovering Linux/Solaris thru SSH. The report says Port 23 was > skipped and shows me IP Address XYZ. Then I look at the same IP address > later in the report and it shows that it updated the CI. > > How could this be if the port was skipped? How could the CI update if the > port was skipped? I am thinking these skipped ports are an issue. > > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ -- I know the Lord is always with me. I will not be shaken, for he is right beside me. --Psalm 16:8 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
