09-20-2005
X6799A PCI cards and Sunfire v880
Hi,
Can X6799A PCI single fiber channel cards be fitted into the top 2 slots of a Sunfire v880. These 2 slots are 66Mhz and X6799A are supposed to be able to connect at this speed.
However , I believe the cards are 5volts , whilst the slots are 3.3volts.
10 More Discussions You Might Find Interesting
1. BSD
Hi!
I just wanted to know what network cards are supported in FreeBSD. I have looked at the list of supported cards but I can't find any of them in the stores. Is the list not updated, I would really preciate info about where (in EU, Sweden) I can buy them.
/Peter (2 Replies)
Discussion started by: Barfly.se
2 Replies
2. AIX
I am trying to find PCI Ethernet cards that are compatible with the IBM RISC 6000 - B50 Power PC. None of the regular NIC's seem to have AIX drivers. Does anyone know of AIX drivers for standard PCI Ethernet NIC's or a non IBM NIC that works with the Model B50 at 10/100 MB ? (0 Replies)
Discussion started by: rahe
0 Replies
3. Solaris
Has anyone ever relocated an HBA card after already having it configured in another PCI slot? I've found that the HBA instance #'s start incrementing past the previous. It results in me having to have my instance numbers in /kernel/drv/qla2300.conf be 4,5,6,7 instead of 0,1,2,3. Cleanup with... (5 Replies)
Discussion started by: kduffin
5 Replies
4. Solaris
We have 3 V880's and we need to purchase a KVM for them. I've never purchased one before. Does anyone have a recommendation for one? (3 Replies)
Discussion started by: dangral
3 Replies
5. Solaris
I have two mechine, one is SUN V880 and another is IBM p570.
I run the same script on V880 and p570 , why the cpu usage always under 50% on V880 but the cpu usage can growth to 100% on p570. (4 Replies)
Discussion started by: golden
4 Replies
6. Solaris
Hi,
I'mtrying to connect a Device via the serial port to my Solaris 10 environment (Sunfire V880).
I have setup ttyb to connect to the Device. I am getting a connected status in my Port Listing (Using a separate Module that I have in the app running in the environment) but the moment I try to... (0 Replies)
Discussion started by: Alchemist
0 Replies
7. Solaris
Hello All,
I am not a sun expert, but in my network administration job I had to deal with SUN servers. We've to replace a faulty motherboard of SF V880. As per my understanding, host id of machines is programmed in PROM. So will host ID be changed with the replacement of V880 motherboard?... (6 Replies)
Discussion started by: Charagh
6 Replies
8. Solaris
Any help on this would be greatly appreciated. I have read other threads on similar subject but still not clear on what this is telling me and what action to take. Do I have a couple of disks that are slowly dying?
While checking disk usage on the V880 I noticed the following:
# format... (3 Replies)
Discussion started by: jamba1
3 Replies
9. Solaris
Hi
I have a 1TB external drive that I want to attach to a SunFire v880 server which runs on Solaris 9. After attaching the external drive what commands should I issue so that the drive will be seen by the server? (7 Replies)
Discussion started by: rahmantanko
7 Replies
10. Hardware
Hi
Does someone have the latest firmware for a sunfire v880
I have a problem with the FC-AL disk i guess i need to upgrade the firmware but i dont have a support with oracle and i can't find it anywhere
thank you (4 Replies)
Discussion started by: simplextibi
4 Replies
AN(4) BSD Kernel Interfaces Manual AN(4)
NAME
an -- Aironet 4500/4800 and Cisco 340/350 series wireless network driver
SYNOPSIS
an* at pcmcia? function ?
an* at pci? dev ? function ?
an* at isapnp?
DESCRIPTION
The an driver provides support for Aironet Communications 4500/4800 and Cisco Aironet 340/350 series wireless network adapters. This
includes the ISA, PCI and PCMCIA varieties. The 4500 series adapters operate at 1 and 2Mbps while the 4800 series and 340/350 series can
operate at 1, 2, 5.5 and 11Mbps. The ISA, PCI and PCMCIA devices are all based on the same core PCMCIA modules and all have the same pro-
gramming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the host as normal ISA and PCI devices and
do not require any PCMCIA support.
The PCMCIA Aironet cards require PCMCIA support. ISA cards can either be configured to use ISA Plug and Play or to use a particular I/O
address and IRQ by properly setting the DIP switches on the board. (The default switch setting is for plug and play.) The an driver has
Plug and Play support and will work in either configuration, however when using a hard-wired I/O address and IRQ, the driver configuration
and the NIC's switch settings must agree. PCI cards require no switch settings of any kind and will be automatically probed and attached.
All host/device interaction with the Aironet cards is via programmed I/O. The Aironet devices support 802.11 and 802.3 frames, power manage-
ment, BSS (infrastructure) and IBSS (ad-hoc) operation modes. The an driver encapsulates all IP and ARP traffic as 802.11 frames, however it
can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps, or ``auto'' (the NIC automat-
ically chooses the best speed).
By default, the an driver configures the Aironet card to join an access point with an SSID of null string. For ad-hoc mode, in which sta-
tions can communicate among each other without the aid of an access point, the driver must be set using ifconfig(8).
For more information on configuring this device, see ifconfig(8) and ifmedia(4).
HARDWARE
Cards supported by the an driver include:
Aironet 4500 Series
Aironet 4800 Series
Cisco Aironet 340 Series
Cisco Aironet 350 Series
DIAGNOSTICS
an%d: init failed The Aironet card failed to come ready after an initialization command was issued.
an%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM.
an%d: device timeout The Aironet card failed to generate an interrupt to acknowledge a transmit command.
SEE ALSO
arp(4), ifmedia(4), netintro(4), ifconfig(8)
HISTORY
The an device driver first appeared in FreeBSD 4.0, and then in NetBSD 1.6.
AUTHORS
The an driver was written by Bill Paul <wpaul@ee.columbia.edu>.
BSD
December 13, 2000 BSD