07-17-2012
Quote:
Originally Posted by
zaxxon
Is 10.1.40.41 an external network or is it virtual and does only exist in on your managed system?
10.1.40.41 is the IP of the LPAR I'm trying to setup. It only exists in my private network.
10 More Discussions You Might Find Interesting
1. AIX
I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
Discussion started by: LegendMan
1 Replies
2. IP Networking
Dear friends,
Please explain the functionality of the ping command and explain the network details, and IP layers.
I want some more clarification about following things
i) switch
ii) hub
iii) routers
iv) proxy (3 Replies)
Discussion started by: thangappan
3 Replies
3. AIX
I am planning for System P with 2 number of 2-core processor (4 core in total).
Can I make 3 LPARS with this processor configuration without the support of micropartitioning, that means with simple LPAR only. (3 Replies)
Discussion started by: pchangba
3 Replies
4. AIX
can i get a step b syep explanation in creating LPAR... i have searched for tutorials i couldn't find the right one.... (2 Replies)
Discussion started by: udtyuvaraj
2 Replies
5. AIX
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies
6. Shell Programming and Scripting
Hi,
I develop simple animation ping script on Solaris Platform. It is like Cisco ping.
Examples and source code are below.
bash-3.00$ gokcell 152.155.180.8 30
Sending 30 Ping Packets to 152.155.180.8
!!!!!!!!!!!!!.!!!!!!!!!!!!!!!.
% 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies
7. AIX
Hi,
I installed AIX 7.1 on a blade though (hmc with vio). I can ping the IP address, but not the gateway. Is there anything that I should configure?
Is there anything that I have to check with vio setting or Am I missing any configuration?
Please let me know further.
Thank you (5 Replies)
Discussion started by: pjeedu2247
5 Replies
8. Shell Programming and Scripting
Hi
I am using perl to ping a list of nodes - with script below :
$p = Net::Ping->new("icmp");
if ($p->ping($host,1)){
print "$host is alive.\n";
}
else {
print "$host is unreacheable.\n";
}
$p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies
9. AIX
There can be configurations in IBM Server wherein a
standalone partition is created on some supported IBM Server
Or
A VIOS - VIOC LPARs created.
Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..?
On a... (2 Replies)
Discussion started by: Manish00712
2 Replies
10. Programming
help with bash script!
im am working on this script to make sure my server will stay online, so i made this script..
HOSTS="192.168.138.155"
COUNT=4
pingtest(){
for myhost in "$@"
do
ping -c "$COUNT" "$myhost" &&return 1
done
return 0
}
if pingtest $HOSTS
#100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies
LEARN ABOUT X11R4
systemd-networkd
SYSTEMD-NETWORKD.SERVICE(8) systemd-networkd.service SYSTEMD-NETWORKD.SERVICE(8)
NAME
systemd-networkd.service, systemd-networkd - Network manager
SYNOPSIS
systemd-networkd.service
/lib/systemd/systemd-networkd
DESCRIPTION
systemd-networkd is a system service that manages networks. It detects and configures network devices as they appear, as well as creating
virtual network devices.
To configure low-level link settings independently of networks, see systemd.link(5).
systemd-networkd will create network devices based on the configuration in systemd.netdev(5) files, respecting the [Match] sections in
those files.
systemd-networkd will manage network addresses and routes for any link for which it finds a .network file with an appropriate [Match]
section, see systemd.network(5). For those links, it will flush existing network addresses and routes when bringing up the device. Any
links not matched by one of the .network files will be ignored. It is also possible to explicitly tell systemd-networkd to ignore a link by
using Unmanaged=yes option, see systemd.network(5).
When systemd-networkd exits, it generally leaves existing network devices and configuration intact. This makes it possible to transition
from the initrams and to restart the service without breaking connectivity. This also means that when configuration is updated and
systemd-networkd is restarted, netdev interfaces for which configuration was removed will not be dropped, and may need to be cleaned up
manually.
CONFIGURATION FILES
The configuration files are read from the files located in the system network directory /lib/systemd/network, the volatile runtime network
directory /run/systemd/network and the local administration network directory /etc/systemd/network.
Networks are configured in .network files, see systemd.network(5), and virtual network devices are configured in .netdev files, see
systemd.netdev(5).
SEE ALSO
systemd(1), systemd.link(5), systemd.network(5), systemd.netdev(5), systemd-networkd-wait-online.service(8)
systemd 237 SYSTEMD-NETWORKD.SERVICE(8)