Sponsored Content
Operating Systems Solaris setting up DS4300 SAN on Solaris Post 302198299 by itik on Thursday 22nd of May 2008 02:33:47 PM
Old 05-22-2008
I'll be using one port 2 GB fiber or two port 4 GB fiber. The card is from Dlink or sun.
 

9 More Discussions You Might Find Interesting

1. Solaris

SAN Configuration in Solaris

I Have IBM ESS 800, trying to configure SAN storage using Fiber card. I installed the SDD driver & can see the disks however, when I did # datapath query device I have the disks shown in slices # ./datapath query device Total Devices : 8 Dev#: 0 Device Name: vpath1a Type:... (0 Replies)
Discussion started by: Remi
0 Replies

2. Solaris

Solaris and SAN

Hi, How can we differentiate a SAN disk with a Solaris local disk? Please respond. Thanks (4 Replies)
Discussion started by: balu_solaris
4 Replies

3. UNIX for Advanced & Expert Users

SAN Configuration in Solaris

Hi, I have 4 servers that I connected SUN HBAs on. (SAN is IBM - ESS 800 with Brocade switch) I installed the SAN foundation kit, IBMsdd drivers, Solaris Patch 108974-50 & SANsurfer CLI. (I'm running Solaris 8 - HBA is SG-XPC11FC-QL2 On 1 of the 4 servers show the HBAs as CONNECTED, but... (3 Replies)
Discussion started by: Remi
3 Replies

4. Solaris

SAN Storage to solaris 10 server

Hi, I have configured our SAN Storage to be connected to our new SUN T5220. On the SAn it looks all fine on the server I do not see any connection: cfgadm -al Ap_Id Type Receptacle Occupant Condition c1 scsi-bus connected ... (4 Replies)
Discussion started by: manni2
4 Replies

5. Solaris

Solaris in a SAN BOOT

My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440. What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Discussion started by: q8devilish
3 Replies

6. Solaris

SAN boot solaris 10

I have a solaris 10 box which does not have internal disks it has just a single dual port HBA card. Storage team has assigned 2 LUNs to the system and i can see it from the probe-scsi-all /pci@3,700000/SUNW,emlxs@0,1 Device PortID 10100 WWPN 5006016941e0a08d LUN 0 Disk DGC ... (0 Replies)
Discussion started by: fugitive
0 Replies

7. Solaris

Solaris SAN configuration.

HI All, What are IPFC(Internet Protocol over Fibre channel) SAN devices. What all i got from guide is "Configuring IPFC over host system describes host recognition of IPFC devices and implementation of IP over FC in SAN" What does above statement actually mean. I would appreciate detailed... (2 Replies)
Discussion started by: ravijanjanam12
2 Replies

8. Solaris

Moving Solaris 9 Host to new SAN.

Hi All, Hopefully you can answer my question. We are about to move to a new Fibre Channel infrastructure going from Cisco to Brocade switches. Amongst others, we have a number of Solaris 9 hosts which connect to our EVA5000 and EVA8100 array's. What is involved in moving the Solaris hosts to... (3 Replies)
Discussion started by: eptc
3 Replies

9. AIX

IBM AIX - SAN Storage DS4300 issue

Hi, This is follow up to the post https://www.unix.com/aix/233361-san-disk-appearing-double-aix.html When I connected Pseries Machine HBA Card ( Dual Port ) directly to the SAN Storage DS4300 , I was able to see Host Port Adapter WWN numbers , although I was getting this message... (2 Replies)
Discussion started by: filosophizer
2 Replies
SK(4)							   BSD Kernel Interfaces Manual 						     SK(4)

NAME
sk -- SysKonnect SK-984x and SK-982x PCI Gigabit Ethernet adapter driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device sk Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_sk_load="YES" DESCRIPTION
The sk driver provides support for the SysKonnect SK-984x and SK-982x series PCI Gigabit Ethernet adapters. The SysKonnect adapters consist of two main components: the XaQti Corp. XMAC II gigabit MAC and the SysKonnect GEnesis controller ASIC. The XMAC provides the gigabit MAC and PHY support while the GEnesis provides an interface to the PCI bus, DMA support, packet buffering and arbi- tration. The GEnesis can control up to two XMACs simultaneously, allowing dual-port NIC configurations. The SK-982x 1000baseT adapters also include a Broadcom BCM5400 1000baseTX PHY which is used in place of the XMAC's internal PHY. The Broad- com PHY is connected to the XMAC via its GMII port. 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. Also supported is the Marvell Semiconductor 88E100* gigabit PHY. 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. The sk driver supports the following media types: autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the /etc/rc.conf file. 1000baseTX Set 1000baseTX operation over twisted pair. This is only available for SK-982x series adapters with 1000baseT ports. Both full-duplex and half-duplex modes are supported. 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both full-duplex and half-duplex modes are supported. The sk driver supports the following media options: full-duplex Force full duplex operation half-duplex Force half duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
Adapters supported by the sk driver include: o 3Com 3C940 single port, 1000baseT adapter o 3Com 3C2000-T single port, 1000baseT adapter o Belkin F5D5005 single port, 1000baseT adapter o D-Link DGE-530T single port, 1000baseT adapter o Linksys (revision 2) single port, 1000baseT adapter o SK-9521 SK-NET GE-T single port, 1000baseT adapter o SK-9821 SK-NET GE-T single port, 1000baseT adapter o SK-9822 SK-NET GE-T dual port, 1000baseT 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 SMC 9452TX single port, 1000baseT adapter LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.skc.jumbo_disable Disable jumbo frame support. Systems with less memory can set it to a non-zero value to save memory. The default value is 0. SYSCTL VARIABLES
The following variable is available as both sysctl(8) variable and loader(8) tunable: dev.skc.%d.int_mod This variable controls interrupt moderation. The accepted range is 10 to 10000. The default value is 100 microseconds. The inter- face has to be brought down and up again before a change takes effect. 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: no memory for softc struct! The driver failed to allocate memory for per-device instance information during initialization. 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
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), vlan(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. AUTHORS
The sk driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BSD
November 23, 2010 BSD
All times are GMT -4. The time now is 07:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy