09-22-2018
Quote:
Originally Posted by
filosophizer
OK, everything is fine, however now cannot connect to ASMI through browser,
using both HMC Ports
Default IP 1 = 192.168.2.147
Default IP 2 = 192.168.3.147
I haven't used an IBM p-Series without a HMC for such a long time that i am not sure i can help you off the top of my head here. However, there might be all sorts of problems putting obstacles into the IP-communication between your browser and the Serviceprocessor.
First off, it might be that the IP addresses have once been changed and i am not sure if a simple SP-reset really changes that back to the defaults. (That i am not sure means just that: i don't know. If you have information in the affirmative, then perhaps it is so.)
Second, there is a sure-fire way to connect to the SP, whatever its IP might be: go to the data centre, connect a crossed-out cable to the SP connector 1 or 2 and connect your system directly to it. I have a small netbook for these purposes with a Wireshark/Ethereal software installed, so i can identify even unknown or fogotten IP-adresses. Once you identified the IP-address you still need the ASMI password, which is, btw., completely separate!
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. HP-UX
Hello HP-UX Gurus,
I am having issues trying to start an x-session via eXceed 7.1.
When I bring up eXceed via XDMCP Braodcast I see the host name and IP Address but when I try to connect the X window does not come up.
I made the modification to the following file “/etc/dt/config/Xaccess”... (2 Replies)
Discussion started by: smokie
2 Replies
2. Solaris
Hi friends
recently i have installed SXDE 1/08 into my machine,and i installed wifi driver also
its working fine,Recently i was unable to connect to Internet,I have not changed any configurations and any installations,thing is that i got my iwk0 interface is UP and IP address also and i can... (6 Replies)
Discussion started by: srinivas2828
6 Replies
3. Emergency UNIX and Linux Support
I shall explain the situation that I am facing to the best extent possible. I require some help, as this situation is an urgent one.
I am trying to automate sending data from one AIX machine to another. A script runs that tries to push data received from an upstream application to another AIX... (7 Replies)
Discussion started by: ggayathri
7 Replies
4. AIX
Hi friends
How to clear the asmi deconfiguration errors.recently on cpu got deconfigured ibm assist to clear the error and to update the firmware please help me
raj (0 Replies)
Discussion started by: senmak
0 Replies
5. AIX
Hi
I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct.
i have rebooted and reconfigured the ip address, but issue is persists.
Kindly suggest how to... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
6. HP-UX
Hi,
I'm trying to connect from an HP-UX with SSH2 client(ssh2 3.1.2 on hppa1.1-hp-hpux11.00) to an SSH2 server on a VxWorks system. The SSH connection is failing with the below connection logs:
> /usr/local/bin/ssh2 -v -l testuser 10.10.10.10
debug: Ssh2/ssh2.c:1391: Using file... (4 Replies)
Discussion started by: ysafi
4 Replies
7. Shell Programming and Scripting
I am trying to connect to SQL plus through unix but i am getting below error
'ksh: sqlplus: not found'
note i am running this from /home/xxx
do i need to set any environmental variable for this. below is my code
echo " hello world"
sqlplus -s apps/CAF78GEN<<EOF
set heading... (4 Replies)
Discussion started by: karnatis
4 Replies
8. Red Hat
I have managed to install Broadcom BCM43228 Wireless adapter on a laptop running CentOS 5.9 using instructions at:
wiki.centos.org/HowTos/Laptops/Wireless/Broadcom
I had the problem "Error for wireless request "Set Encode" (8B2A): SET failed on device... mentioned on the same page and solved... (0 Replies)
Discussion started by: cooltoad
0 Replies
9. Red Hat
Hello,
I just installed CentOS 7 (Server with GUI) and guess what I could install Virtual Box Guest additions without installing any extra package/software which is great news !
Now bad news or not so great news.
My Host OS is Windows 10, Virtual Box is the virtualization software. CentOS7-1... (0 Replies)
Discussion started by: bluemind2005
0 Replies
10. Solaris
hi
I am having issues when trying to connect using ftp, I am having the following error:
User (10.100.48.73:(none)): moz
331 Password required for moza.
Password:
530 Login incorrect.
Login failed.
ftp> by
221 Goodbye.
I have created a user like this:
useradd -g 10 -d /lam/moza -m -s... (11 Replies)
Discussion started by: fretagi
11 Replies
LEARN ABOUT DEBIAN
smokeping_probes_opensshjunosping
Smokeping_probes_OpenSSHJunOSPing(3) SmokePing Smokeping_probes_OpenSSHJunOSPing(3)
NAME
Smokeping::probes::OpenSSHJunOSPing - Juniper SSH JunOS Probe for SmokePing
SYNOPSIS
*** Probes ***
+OpenSSHJunOSPing
forks = 5
offset = 50%
packetsize = 100
step = 300
timeout = 15
# The following variables can be overridden in each target section
junospass = password # mandatory
junosuser = user # mandatory
pings = 5
psource = 192.168.2.129
source = 192.168.2.1 # mandatory
# [...]
*** Targets ***
probe = OpenSSHJunOSPing # if this should be the default probe
# [...]
+ mytarget
# probe = OpenSSHJunOSPing # if the default probe is something else
host = my.host
junospass = password # mandatory
junosuser = user # mandatory
pings = 5
psource = 192.168.2.129
source = 192.168.2.1 # mandatory
DESCRIPTION
Connect to Juniper JunOS via OpenSSH to run ping commands. This probe uses the "extended ping" of the Juniper JunOS. You have the option
to specify which interface the ping is sourced from as well.
VARIABLES
Supported probe-specific variables:
forks
Run this many concurrent processes at maximum
Example value: 5
Default value: 5
offset
If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-
specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or
alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT
influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable
'concurrentprobes' is set in the 'General' section.)
Example value: 50%
packetsize
The (optional) packetsize option lets you configure the packetsize for the pings sent.
Default value: 100
step
Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the
step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to
delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the
'General' section.)
Example value: 300
timeout
How long a single 'ping' takes at maximum
Example value: 15
Default value: 5
Supported target-specific variables:
junospass
The junospass option allows you to specify the password for the username specified with the option junosuser.
Example value: password
This setting is mandatory.
junosuser
The junosuser option allows you to specify a username that has ping capability on the JunOS Device.
Example value: user
This setting is mandatory.
pings
How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the
number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have
to delete the old RRD files or somehow convert them.
Example value: 5
psource
The (optional) psource option specifies an alternate IP address or Interface from which you wish to source your pings from. Routers
can have many many IP addresses, and interfaces. When you ping from a router you have the ability to choose which interface and/or
which IP address the ping is sourced from. Specifying an IP/interface does not necessarily specify the interface from which the ping
will leave, but will specify which address the packet(s) appear to come from. If this option is left out the JunOS Device will source
the packet automatically based on routing and/or metrics. If this doesn't make sense to you then just leave it out.
Example value: 192.168.2.129
source
The source option specifies the JunOS device that is going to run the ping commands. This address will be used for the ssh connection.
Example value: 192.168.2.1
This setting is mandatory.
AUTHORS
Tobias Oetiker lttobi@oetiker.chgt
based on Smokeping::probes::TelnetJunOSPing by S H A N ltshanali@yahoo.comgt.
NOTES
JunOS configuration
The JunOS device should have a username/password configured, as well as the ability to connect to the VTY(s).
Make sure to connect to the remote host once from the commmand line as the user who is running smokeping. On the first connect ssh will ask
to add the new host to its known_hosts file. This will not happen automatically so the script will fail to login until the ssh key of your
juniper box is in the known_hosts file.
Some JunOS devices have a maximum of 5 VTYs available, so be careful not to hit a limit with the 'forks' variable.
Requirements
This module requires the Net::OpenSSH and IO::Pty.
2.6.8 2013-03-17 Smokeping_probes_OpenSSHJunOSPing(3)