Login or Register to Ask a Question and Join Our Community


AIX

Virtualizing the Fiber card (VFC) on P595

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX Virtualizing the Fiber card (VFC) on P595
# 1  
Old 09-06-2011
[Solved] Virtualizing the Fiber card (VFC) on P595
Hi,

We have a P595 machine with a dual port Fiber card per VIOs.

We have two VIOs in the box.

VIO1: ---> 2 port Fiber Card
VIO2: ---> 2 port Fiber Card

One port on each fiber card is utilized. Connected to SAN switches. We are getting all disks from SAN both for VIOs and LPARs.

Now we have connected our tape library to our SAN switches and from switches to our P595 box Fiber cards. We need to Virtualize the Fiber card in order to take backups.

----> Now if we Virtualize the fiber card then wouldnt it disturb the Fiber card on the machines? The disks comming from SAN would no longer be available. I found this link to do this:

NPIV Setup and Configuration to Virtualize Fibre-channel card on IBM p6 - AIX & System P Community

Regards,

---------- Post updated at 08:33 AM ---------- Previous update was at 03:26 AM ----------

Well folks this is how its going to work.

If one port is free we can utilize it and no need to worry about the other port as the vfc that would be created would be mapped "manually" to the available fcs

Regards,
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. AIX

AIX: DLPAR VFC - HMC v9

Hey All, I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS. In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the... (1 Reply)
Discussion started by: aixkidbee
1 Replies

2. AIX

Virtualizing Physical Machine

Hi Experts - we have power710 (no VIOs) that is already connected to hmc and everything . I already have a Physical LPAR in there and network configured . Now I plan to delete that LPAR and then put Virtualization code (COD) to virtualize that machine by building VIO servers and stuff.Also ordered... (9 Replies)
Discussion started by: JME2015
9 Replies

3. AIX

HMC Hardware Discovery does not work for p595 frames

Hi, I require help with hardware discovery while running a command from an HMC with firmware V7.3.5 SP 3. The two frames I am running the command for are p 5 595's. Command input: lshwres -m swdc-c02-9119-595-SN02780CF -r io --rsubtype slotchildren -F lpar_name Error output: The managed... (1 Reply)
Discussion started by: AIXNEWBIE62
1 Replies

4. AIX

Powerha on P595 and Blade HX5 Type 787

Hello Everyobdy! Is it poosible to implement PowerHa on Different Server like power 595 and Blade HX5 Type 787 Thanks in Advance (8 Replies)
Discussion started by: Vit0_Corleone
8 Replies

5. UNIX for Advanced & Expert Users

Help with old DG/UX machine, virtualizing?

Hey all, We have an old Data General Unix system (DG/UX) on an old AViiON machine. That DG system is Intel-based (PentiumPro) and we are trying to virtualize / emulate it. DG was a clever system, as it cannot be installed on a 'regular' x86 machine, only on an AViiON box. I think I figured out... (2 Replies)
Discussion started by: dgux
2 Replies

6. AIX

p595 LPAR no longer sees SAN boot disk

Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines. Now, on two... (2 Replies)
Discussion started by: rwesterik
2 Replies

7. HP-UX

Setting Fiber Card to Auto Negotiate

I have the Fiber Card assigned to a vPar and I am trying to use it with our HP EVA 4000. Our SAN switch is only a 2GB switch. The card has three LED lights labeled 4GB, 2GB and 1GB and the 4GB light has an amber light. I need to change the link speed, how do you do this on HP-UX? Also here is... (3 Replies)
Discussion started by: scotbuff
3 Replies

8. AIX

How to know the hardware configuration on P595 LAPRs

The p595 have 6 Lpars, not all hardware resource assigned to 6 lpars. which command can list all hardware configuration on p595? Do I need go to each lapr to list? (2 Replies)
Discussion started by: rainbow_bean
2 Replies

9. Solaris

Identify fiber card

All, Is there a way to identify which fiber card (brand) I have in my system? I believe my solaris 8 box has an LP9002LE card, I'm just not 100% sure. Thanks, Kevin (4 Replies)
Discussion started by: kjbaumann
4 Replies
Login or Register to Ask a Question

LEARN ABOUT NETBSD

skc

SK(4)							   BSD Kernel Interfaces Manual 						     SK(4)

NAME

     sk, skc -- SysKonnect XMAC II and Marvell GMAC based gigabit ethernet

SYNOPSIS

     skc* at pci? dev ? function ?
     sk* at skc?
     mskc* at pci? dev ? function ?
     msk* at skc?

DESCRIPTION

     The sk driver provides support for SysKonnect based gigabit ethernet adapters and Marvell based gigabit ethernet adapters, including the fol-
     lowing:

	   o   SK-9821 SK-NET GE-T single port, copper adapter
	   o   SK-9822 SK-NET GE-T dual port, copper adapter
	   o   SK-9841 SK-NET GE-LX single port, single mode fiber adapter
	   o   SK-9842 SK-NET GE-LX dual port, single mode fiber adapter
	   o   SK-9843 SK-NET GE-SX single port, multimode fiber adapter
	   o   SK-9844 SK-NET GE-SX dual port, multimode fiber adapter
	   o   SK-9521 V2.0 single port, copper adapter (32-bit)
	   o   SK-9821 V2.0 single port, copper adapter
	   o   SK-9843 V2.0 single port, copper adapter
	   o   3Com 3c940 single port, copper adapter
	   o   Belkin Gigabit Desktop Network PCI Card, single port, copper (32-bit)
	   o   D-Link DGE-530T single port, copper adapter
	   o   Linksys EG1032v2 single-port, copper adapter
	   o   Linksys EG1064v2 single-port, copper adapter

     The msk driver provides support for the Marvell Yukon-2 based Gigabit Ethernet adapters, including the following:

	   o   Marvell Yukon 88E8035, copper adapter
	   o   Marvell Yukon 88E8036, copper adapter
	   o   Marvell Yukon 88E8038, copper adapter
	   o   Marvell Yukon 88E8050, copper adapter
	   o   Marvell Yukon 88E8052, copper adapter
	   o   Marvell Yukon 88E8053, copper adapter
	   o   Marvell Yukon 88E8055, copper adapter
	   o   SK-9E21 1000Base-T single port, copper adapter
	   o   SK-9E22 1000Base-T dual port, copper adapter
	   o   SK-9E81 1000Base-SX single port, multimode fiber adapter
	   o   SK-9E82 1000Base-SX dual port, multimode fiber adapter
	   o   SK-9E91 1000Base-LX single port, single mode fiber adapter
	   o   SK-9E92 1000Base-LX dual port, single mode fiber adapter
	   o   SK-9S21 1000Base-T single port, copper adapter
	   o   SK-9S22 1000Base-T dual port, copper adapter
	   o   SK-9S81 1000Base-SX single port, multimode fiber adapter
	   o   SK-9S82 1000Base-SX dual port, multimode fiber adapter
	   o   SK-9S91 1000Base-LX single port, single mode fiber adapter
	   o   SK-9S92 1000Base-LX dual port, single mode fiber adapter
	   o   SK-9E21D 1000Base-T single port, copper adapter

     The SysKonnect based adapters consist of two main components: the XaQti Corp. XMAC II Gigabit MAC (sk) and the SysKonnect GEnesis controller
     ASIC (skc).  The XMAC provides the Gigabit MAC and PHY support while the GEnesis provides an interface to the PCI bus, DMA support, packet
     buffering and arbitration.  The GEnesis can control up to two XMACs simultaneously, allowing dual-port NIC configurations.

     The Marvell based adapters are a single integrated circuit, but are still presented as a separate MAC (sk) and controller ASIC (skc).  At
     this time, there are no dual-port Marvell based NICs.

     The sk driver configures dual port SysKonnect adapters such that each XMAC is treated as a separate logical network interface.  Both ports
     can operate independently of each other and can be connected to separate networks.  The SysKonnect driver software currently only uses the
     second port on dual port adapters for failover purposes: if the link on the primary port fails, the SysKonnect driver will automatically
     switch traffic onto the second port.

     The XaQti XMAC II supports full and half duplex operation with autonegotiation.  The XMAC also supports unlimited frame sizes.  Support for
     jumbo frames is provided via the interface MTU setting.  Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the
     adapter to receive and transmit jumbo frames.  Using jumbo frames can greatly improve performance for certain tasks, such as file transfers
     and data streaming.

     Hardware TCP/IP checksum offloading for IPv4 is supported.

     The following media types and options (as given to ifconfig(8)) are supported:

	   media autoselect
		Enable autoselection of the media type and options.  The user can manually override the autoselected mode.

	   media 1000baseSX mediaopt full-duplex
		Set 1000Mbps (Gigabit Ethernet) operation on fiber and force full-duplex mode.

	   media 1000baseSX mediaopt half-duplex
		Set 1000Mbps (Gigabit Ethernet) operation on fiber and force half-duplex mode.

	   media 1000baseT mediaopt full-duplex
		Set 1000Mbps (Gigabit Ethernet) operation and force full-duplex mode.

     For more information on configuring this device, see ifconfig(8).	To view a list of media types and options supported by the card, try
     ifconfig -m <device>.  For example, ifconfig -m sk0.

DIAGNOSTICS

     sk%d: couldn't map memory	A fatal initialization error has occurred.

     sk%d: couldn't map ports  A fatal initialization error has occurred.

     sk%d: couldn't map interrupt  A fatal initialization error has occurred.

     sk%d: failed to enable memory mapping!  The driver failed to initialize PCI shared memory mapping.  This might happen if the card is not in a
     bus-master slot.

     sk%d: no memory for jumbo buffers!  The driver failed to allocate memory for jumbo frames during initialization.

     sk%d: watchdog timeout  The device has stopped responding to the network, or there is a problem with the network connection (cable).

SEE ALSO

     ifmedia(4), intro(4), netintro(4), pci(4), ifconfig(8)

     XaQti XMAC II datasheet, http://www.xaqti.com.

     SysKonnect GEnesis programming manual, http://www.syskonnect.com.

HISTORY

     The sk device driver first appeared in FreeBSD 3.0.  OpenBSD support was added in OpenBSD 2.6.  NetBSD support was added in NetBSD 2.0.

     The msk driver first appeared in OpenBSD 4.0, and was ported to NetBSD 4.0.

AUTHORS

     The sk driver was written by Bill Paul <wpaul@ctr.columbia.edu>.  Support for the Marvell Yukon-2 was added by Mark Kettenis
     <kettenis@openbsd.org>.

BUGS

     This driver is experimental.

     Support for checksum offload is unimplemented.

     Performance with at least some Marvell-based adapters is poor, especially on loaded PCI buses or when the adapters are behind PCI-PCI
     bridges.  It is believed that this is because the Marvell parts have significantly less buffering than the original SysKonnect cards had.

BSD
								 September 9, 2006							       BSD