11-19-2013
The Mapping normaly points to the MAC-adress of your FC-Adapter.
Use the following command to get the MAC-adress:
lscfg -vl fcs3 | grep -i "Network Address"
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies
2. Solaris
Hi All,
The path requires me to go Single User mode. On single user mode, the patch still won't continue:
dhcpagent supports a new keyword in /etc/default/dhcpagent.
Please merge the existing /etc/default/dhcpagent with the
patched version of /etc/default/dhcpagent shipped with this... (2 Replies)
Discussion started by: itik
2 Replies
3. AIX
Hi folks,
does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies
4. AIX
Hello All,
After creating lpp_source/spot from AIX 5.3TL6-07 DVD on the NIM(AIX6.1), I went online and download the fix pack for reaching TL8-04. (it was less than 200Mgegs total)
then I did define a newer lpp_source530TL8-04 via a copy from the older lpp_source530TL6-07 (I diduse a command... (2 Replies)
Discussion started by: sangers
2 Replies
5. AIX
On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem.
The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like
5.3 TL3 = IBM.MPIO 5.3.0.30
5.3... (0 Replies)
Discussion started by: clking
0 Replies
6. AIX
Hi,
we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes.
Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
8 Replies
7. AIX
Hello,
we are planning to deploy some of our databases on AIX/LPAR based servers (we didn't bought it yet ...). IBM's engineers says that if we want to boot them from SAN the hardware array has to be compatible with MPIO but they don't want to deliver any document with list of arrays supported... (5 Replies)
Discussion started by: andy55
5 Replies
8. AIX
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies
9. AIX
Hello,
I have some concerns over the disk management of my AIX system.
For example server1
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c vg_2 active
hdisk2 00c1cc14d6de272b ... (6 Replies)
Discussion started by: Phat
6 Replies
10. AIX
Hello,
I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c None
hdisk2 ... (9 Replies)
Discussion started by: Phat
9 Replies
LEARN ABOUT DEBIAN
mac_none
MAC_NONE(4) BSD Kernel Interfaces Manual MAC_NONE(4)
NAME
mac_none -- null MAC policy module
SYNOPSIS
To compile the null policy into your kernel, place the following lines in your kernel configuration file:
options MAC
options MAC_NONE
Alternately, to load the sample module at boot time, place the following line in your kernel configuration file:
options MAC
and in loader.conf(5):
mac_none_load="YES"
DESCRIPTION
The mac_none policy module implements a sample MAC policy that has no effect on access control in the system. Unlike mac_stub(4), none of
the MAC entry points are defined.
Label Format
No labels are defined for mac_none.
SEE ALSO
mac(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_partition(4), mac_portacl(4), mac_seeotheruids(4),
mac_stub(4), mac_test(4), mac(9)
HISTORY
The mac_none policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project.
AUTHORS
This software was contributed to the FreeBSD Project by Network Associates Labs, the Security Research Division of Network Associates Inc.
under DARPA/SPAWAR contract N66001-01-C-8035 (``CBOSS''), as part of the DARPA CHATS research program.
BUGS
See mac(9) concerning appropriateness for production use. The TrustedBSD MAC Framework is considered experimental in FreeBSD.
While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by
entry point checks. As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user.
BSD
December 1, 2002 BSD