07-18-2012
I rephrased my former post from last night and added some info. Hopefully it is more helpful than before.
This User Gave Thanks to zaxxon For This Post:
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 DEBIAN
fipvlan
FIPVLAN(8) Open-FCoE Tools FIPVLAN(8)
NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery
SYNOPSIS
fipvlan [-c|--create] [-s|--start] interfaces
fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-l|--link-retry <num>]
fipvlan -h|--help
fipvlan -v|--version
DESCRIPTION
The fipvlan command performs Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) VLAN Discovery over Ethernet interfaces.
fipvlan can be used as a diagnostic tool to determine which VLANs have FCoE services available on a network, prior to configuring VLAN
interfaces and the Open-FCoE initiator. fipvlan can also be used to create VLAN interfaces as they are discovered, and to start the
Open-FCoE initiator. The --create and --start options are primarily intended to be used as part of an Open-FCoE boot solution. FCoE
instances started in this way cannot be destroyed or reset by fcoeadm.
fipvlan takes a list of network interface names to run the VLAN discovery protocol over, or the --auto option to use all available Ethernet
interfaces.
fipvlan will enable any interface which is found to be not enabled by the time the program runs. If no response is received on that
interface it will be shutdown again when fipvlan terminates.
OPTIONS
-a, --auto
Use all Ethernet interfaces currently available
-c, --create
Create network interfaces for discovered FCoE VLANs. If a VLAN device already exists for a discovered VLAN, a new VLAN device will not
be created.
-d, --debug
Enable debugging output
-s, --start
Start the Open-FCoE initiator on discovered FCoE VLANs
-f, --suffix <suffix string>
Append the specified string <suffix string> to VLAN interface names.
-l, --link-retry <number of retries>
Retry check for link up up to <number of retries> times. The link state is retried every 500 ms. The default is 20.
-h, --help
Display a help message with basic usage instructions
-v, --version
Display the fipvlan version string
VLAN NAMING CONVENTIONS
The default VLAN device name is dev.vlan; where dev is the name of the Ethernet parent device and vlan is the discovered VLAN ID number. An
optional suffix can be appended to this with -f commandline option.
EXAMPLES
Display all discoverable VLANs with FCoE services
fipvlan --auto
Discover FCoE VLANs on interface eth2, create VLAN devices and start the Open-FCoE initiator
fipvlan --create --start eth2
In this example if FCoE services were available on VLAN 101 of network interface eth2, then a VLAN interface eth2.101-fcoe would be created
and used as the parent device for the initiator.
SEE ALSO
fcoeadm(8) fcoemon(8)
SUPPORT
fipvlan is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found
at the Open-FCoE website http://open-fcoe.org/
Open-FCoE 10/06/2011 FIPVLAN(8)