Sponsored Content
Operating Systems Solaris Solaris 10 installing on Cisco UCS doesn't see HBAs Post 302988834 by jnojr on Tuesday 3rd of January 2017 12:27:00 PM
Old 01-03-2017
Quote:
Originally Posted by achenle
What's the output from running scanpci?
It does show two entries like:

Code:
pci bus 0x000a cardnum 0x00 function 0x00: vendor 0x1137 device 0x0045
 Cisco Systems Inc VIC FCoE HBA

 

6 More Discussions You Might Find Interesting

1. Solaris

Connect Solaris 10 to NetApp filer using Emulex single port HBAs.

Hi, I'm connecting a Solaris 10 server to a Netapp filer with two single port Emulex (Sun StorageTek PCI-X Enterprise 4GB FC HBA) HBAs. After physically installing both these HBAs what do I ned to do within Solaris 10 to enable them and configure them with persistent bindings. Do I need... (6 Replies)
Discussion started by: gwhelan
6 Replies

2. Slackware

latex-ucs

Hi! I am using Slackware 12.1 and I have a question regarding LaTeX. I am trying to use the package ucs, so that I can write in greek, but with no success. In Debian there is a package latex-ucs.deb that does the trick. Is there something similar in Slackware? Thanks in advance (1 Reply)
Discussion started by: kerb41
1 Replies

3. Shell Programming and Scripting

Perl variables inside Net::Telnet::Cisco Module doesn't work

I am writing perl script to configure Cisco device but Variables inside Net::Telnet::Cisco Module doesn't work and passed to device without resolving. Please advise. here is a sample of script: use Net::Telnet::Cisco; $device = "10.14.199.1"; ($o1, $o2, $o3, $o4) = split(/\./,$device);... (5 Replies)
Discussion started by: ahmed_zaher
5 Replies

4. Solaris

Connecting Solaris 10 to Cisco PIX with IPsec tunnel

I having problem connecting to a Cisco PIX Log from IKE # /usr/lib/inet/in.iked -f /etc/inet/ike/config -d Jan 16 00:40:57: 2012 (+0800) *** in.iked started *** Jan 16 00:40:57: Loading configuration... Jan 16 00:40:57: Checking lifetimes in "nullrule" Jan 16 00:40:57: Using default value... (0 Replies)
Discussion started by: conandor
0 Replies

5. Red Hat

UCS installation issues

I am installing RHEL6 on a Cisco UCS blade and the GUI isn't showing up. Curious!!!!! I have installed it on 5 of the other blades and the GUI is there. However, there are many issues that I am having and I am going crazy with this thing. I have issues where the network adapters are not showing... (1 Reply)
Discussion started by: styehimba
1 Replies

6. IP Networking

How to stack Cisco 2960-S and Cisco 2960X?

Is there an easy way to stack Cisco 2960-S and Cisco 2960X switches? If you have no idea, follow this: 1. Stacking is not supported on switches running the LAN Lite image. All switches in the stack must be running the LAN Base image. 2. In a mixed stack of Catalyst 2960-X and Catalyst 2960-S... (0 Replies)
Discussion started by: Ayaerlee
0 Replies
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)
All times are GMT -4. The time now is 05:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy