IBM Blade HS23 Emulex Adapter Woes

I inherited an IBM Blade chassis with three HS23 blades in it, each sporting an Emulex 10GbE VFA Advanced II module.
I have been tasked with adding three additional blades to the chassis with the same cards. I am having terrible trouble setting these up or finding documentation that may describe the process.
One very interesting thing I have noticed is the new blades have a BIOS option for "Emulex iSCSI EFI Configuration Utility" the original blades do not.
If any of you out there have advice or could point me to documentation it would be greatly appreciated.
I have submitted a ticket with IBM but they have yet to respond.
This topic first appeared in the Spiceworks Community

Hi ciscolive,You do not need to install software FCoE adapter because the LOM has a capability of hardware FCoE initiator. On the screenshot, adapter type is corrrectly shown as "Fibre Channel" and it looks that the host recognizes the LOM correctly. Ref) Configuring FCoE Adaptershttps://pubs.vmware.com/vsphere-50/index.jsp#com.vmware.vsphere.storage.doc_50/GUID-A9503ED6-2622-4278-890E-B869C3971A9F.html Hardware FCoE AdaptersThis category includes completely offloaded specialized Converged Network Adapters (CNAs) that contain network and Fibre Channel functionalities on the same card.When such adapter is installed, your host detects and can use both CNA components. In the vSphere Client, the networking component appears as a standard network adapter (vmnic) and the Fibre Channel component as a FCoE adapter (vmhba). You do not need to configure the hardware FCoE adapter to be able to use it. Thanks,

Similar Messages

My IBM blade server Lost all the Interfaces its running oracle linux 6.3

Hi am moses i installed oracle linux on ibm blade server and installed the ethernet, iscsi and fcoe drivers and it worked fine. but after there was an electrical blackout my oracle Linux server lost all
the eth* interfaces. Please assist on what to do because it contains installed application and we don't need to format it.

The out put for dmesg is this:
io scheduler cfq registered
pcieport 0000:00:01.0: setting latency timer to 64
pcieport 0000:00:01.0: irq 65 for MSI/MSI-X
pcieport 0000:00:02.0: setting latency timer to 64
pcieport 0000:00:02.0: irq 66 for MSI/MSI-X
pcieport 0000:00:02.2: setting latency timer to 64
pcieport 0000:00:02.2: irq 67 for MSI/MSI-X
pcieport 0000:00:03.0: setting latency timer to 64
pcieport 0000:00:03.0: irq 68 for MSI/MSI-X
pcieport 0000:00:11.0: setting latency timer to 64
pcieport 0000:00:11.0: irq 69 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 70 for MSI/MSI-X
pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
pci 0000:16:00.0: Signaling PME through PCIe PME interrupt
pci 0000:16:00.1: Signaling PME through PCIe PME interrupt
pci 0000:16:00.2: Signaling PME through PCIe PME interrupt
pci 0000:16:00.3: Signaling PME through PCIe PME interrupt
pci 0000:16:00.4: Signaling PME through PCIe PME interrupt
pci 0000:16:00.5: Signaling PME through PCIe PME interrupt
pci 0000:16:00.6: Signaling PME through PCIe PME interrupt
pci 0000:16:00.7: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:11.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:11.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
pcieport 0000:01:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:02:01.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
efifb: probing for efifb
efifb: framebuffer at 0x90000000, mapped to 0xffffc90027900000, using 6144k, total 16384k
efifb: mode is 1024x768x32, linelength=4096, pages=1
efifb: scrolling: redraw
efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device 128x48
fb0: EFI VGA frame buffer device
intel_idle: MWAIT substates: 0x21120
intel_idle: v0.4 model 0x2D
intel_idle: lapic_timer_reliable_states 0xffffffff
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: Power Button [PWRF]
ACPI: acpi_idle yielding to intel_idle
[Firmware Bug]: APEI: Invalid bit width in GAR [0x7ed3b038/3/0]
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
brd: module loaded
loop: module loaded
Fixed MDIO Bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:00:1a.0: setting latency timer to 64
ehci_hcd 0000:00:1a.0: EHCI Host Controller
ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.0: debug port 2
ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.0: irq 16, io mem 0x92301000
ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.39-200.24.1.el6uek.x86_64 ehci_hcd
usb usb1: SerialNumber: 0000:00:1a.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.0: setting latency timer to 64
ehci_hcd 0000:00:1d.0: EHCI Host Controller
ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.0: debug port 2
ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.0: irq 23, io mem 0x92300000
ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.39-200.24.1.el6uek.x86_64 ehci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
i8042: PNP: No PS/2 controller found. Probing ports directly.
i8042: No controller found
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
EFI Variables Facility v0.08 2004-May-17
Refined TSC clocksource calibration: 1999.993 MHz.
Switching to clocksource tsc
usb 1-1: new high speed USB device number 2 using ehci_hcd
usb 1-1: New USB device found, idVendor=8087, idProduct=0024
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 6 ports detected
usb 2-1: new high speed USB device number 2 using ehci_hcd
usb 2-1: New USB device found, idVendor=8087, idProduct=0024
usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 8 ports detected
usb 1-1.2: new high speed USB device number 3 using ehci_hcd
usb 1-1.2: New USB device found, idVendor=04b4, idProduct=6560
usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1.2:1.0: USB hub found
hub 1-1.2:1.0: 2 ports detected
usb 2-1.1: new high speed USB device number 3 using ehci_hcd
usb 2-1.1: New USB device found, idVendor=ffff, idProduct=0248
usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.1: Product: Gadget USB HUB
usb 2-1.1: Manufacturer: no manufacturer
usb 2-1.1: SerialNumber: 0123456789
hub 2-1.1:1.0: USB hub found
hub 2-1.1:1.0: 6 ports detected
usb 2-1.3: new full speed USB device number 4 using ehci_hcd
usb 2-1.3: New USB device found, idVendor=04b3, idProduct=4002
usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.3: Product: IBM MM2
usb 2-1.3: Manufacturer: IBM
usb 2-1.3: SerialNumber: 0000003012214
usb 1-1.2.2: new high speed USB device number 4 using ehci_hcd
usb 1-1.2.2: New USB device found, idVendor=04b4, idProduct=6560
usb 1-1.2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1.2.2:1.0: USB hub found
hub 1-1.2.2:1.0: 4 ports detected
usb 2-1.1.5: new high speed USB device number 5 using ehci_hcd
usb 2-1.1.5: New USB device found, idVendor=04b3, idProduct=4010
usb 2-1.1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.1.5: Product: RNDIS/Ethernet Gadget
usb 2-1.1.5: Manufacturer: IBM
usb 1-1.2.2.3: new high speed USB device number 5 using ehci_hcd
usb 1-1.2.2.3: New USB device found, idVendor=0928, idProduct=0007
usb 1-1.2.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2.2.3: Product: Mass Storage Plus
usb 1-1.2.2.3: Manufacturer: OEM
usb 1-1.2.2.3: SerialNumber: R8RQ6GKC900D1Z
usb 2-1.1.5: USB disconnect, device number 5
usb 2-1.1.5: new high speed USB device number 6 using ehci_hcd
input: IBM IBM MM2 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input1
generic-usb 0003:04B3:4002.0001: input,hidraw0: USB HID v1.10 Keyboard [IBM IBM MM2] on usb-0000:00:1d.0-1.3/input0
input: IBM IBM MM2 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.1/input/input2
generic-usb 0003:04B3:4002.0002: input,hidraw1: USB HID v1.10 Mouse [IBM IBM MM2] on usb-0000:00:1d.0-1.3/input1
input: OEM Mass Storage Plus as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2.3/1-1.2.2.3:1.1/input/input3
generic-usb 0003:0928:0007.0003: input,hidraw2: USB HID v1.11 Device [OEM Mass Storage Plus] on usb-0000:00:1a.0-1.2.2.3/input1
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
zram: num_devices not specified. Using default: 1
zram: Creating 1 devices ...
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
Registering the dns_resolver key type
registered taskstats version 1
IMA: No TPM chip found, activating TPM-bypass!
rtc_cmos 00:03: setting system clock to 2013-09-03 14:54:17 UTC (1378220057)
Initializing network drop monitor service
Freeing unused kernel memory: 1508k freed
dracut: dracut-004-283.0.1.el6
dracut: rd_NO_LUKS: removing cryptoluks activation
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
udev: starting version 147
udevd (141): /proc/141/oom_adj is deprecated, please use /proc/141/oom_score_adj instead.
usb 2-1.1.5: New USB device found, idVendor=04b3, idProduct=4010
usb 2-1.1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.1.5: Product: RNDIS/Ethernet Gadget
usb 2-1.1.5: Manufacturer: IBM
dracut: Starting plymouth daemon
dracut: rd_NO_DM: removing DM RAID activation
dracut: rd_NO_MD: removing MD RAID activation
mpt2sas version 13.100.00.00 loaded
scsi0 : Fusion MPT SAS Host
mpt2sas 0000:0c:00.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26
mpt2sas 0000:0c:00.0: setting latency timer to 64
mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (41134540 kB)
mpt2sas 0000:0c:00.0: irq 71 for MSI/MSI-X
mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 71
mpt2sas0: iomem(0x0000000092240000), mapped(0xffffc900100d8000), size(16384)
mpt2sas0: ioport(0x0000000000002000), size(256)
mpt2sas0: Allocated physical memory: size(4219 kB)
mpt2sas0: Current Controller Queue Depth(1865), Max Controller Queue Depth(2040)
mpt2sas0: Scatter Gather Elements per IO(128)
mpt2sas0: LSISAS2004: FWVersion(10.00.08.00), ChipRevision(0x03), BiosVersion(07.18.04.02)
mpt2sas0: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
mpt2sas0: sending port enable !!
Emulex LightPulse Fibre Channel SCSI driver 8.3.5.68.6p
Copyright(c) 2004-2011 Emulex. All rights reserved.
lpfc 0000:16:00.2: enabling device (0040 -> 0042)
lpfc 0000:16:00.2: PCI INT C -> GSI 36 (level, low) -> IRQ 36
lpfc 0000:16:00.2: setting latency timer to 64
lpfc 0000:16:00.2: 0:1408 Port Failed POST - portsmphr=0x80000400, perr=x1, sfi=x0, nip=x0, ipc=x0, scr1=x0, scr2=x0, hscratch=x0, pstatus=x400
lpfc 0000:16:00.2: 0:1412 Failed to set up driver resource.
lpfc 0000:16:00.2: PCI INT C disabled
lpfc 0000:16:00.3: enabling device (0040 -> 0042)
lpfc 0000:16:00.3: PCI INT D -> GSI 38 (level, low) -> IRQ 38
lpfc 0000:16:00.3: setting latency timer to 64
lpfc 0000:16:00.3: 0:1408 Port Failed POST - portsmphr=0x80000400, perr=x1, sfi=x0, nip=x0, ipc=x0, scr1=x0, scr2=x0, hscratch=x0, pstatus=x400
lpfc 0000:16:00.3: 0:1412 Failed to set up driver resource.
lpfc 0000:16:00.3: PCI INT D disabled
Initializing USB Mass Storage driver...
scsi1 : usb-storage 1-1.2.2.3:1.0
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi: waiting for bus probes to complete ...
scsi 1:0:0:0: CD-ROM            IBM SATA DEVICE 81Y3658 IB01 PQ: 0 ANSI: 0
mpt2sas0: host_add: handle(0x0001), sas_addr(0x500507604d0112dc), phys(4)
mpt2sas0: port enable: SUCCESS
scsi 0:1:0:0: Direct-Access     LSI      Logical Volume   3000 PQ: 0 ANSI: 6
scsi 0:1:0:0: RAID1: handle(0x00b5), wwid(0x098d6d2781629507), pd_count(2), type(SSP)
scsi 0:1:0:0: qdepth(128), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
scsi 0:0:0:0: Direct-Access     IBM-ESXS MK1401GRRB       SC27 PQ: 0 ANSI: 6
scsi 0:0:0:0: SSP: handle(0x0005), sas_addr(0x5000039428005452), phy(0), device_name(0x5000039428005451)
scsi 0:0:0:0: SSP: enclosure_logical_id(0x500507604d0112dc), slot(0)
scsi 0:0:0:0: qdepth(254), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
scsi 0:0:1:0: Direct-Access     IBM-ESXS MK1401GRRB       SC27 PQ: 0 ANSI: 6
scsi 0:0:1:0: SSP: handle(0x0006), sas_addr(0x500003942802c216), phy(1), device_name(0x500003942802c215)
scsi 0:0:1:0: SSP: enclosure_logical_id(0x500507604d0112dc), slot(1)
scsi 0:0:1:0: qdepth(254), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
sd 0:1:0:0: [sda] 285155328 512-byte logical blocks: (145 GB/135 GiB)
sd 0:1:0:0: [sda] Write Protect is off
sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
sd 0:1:0:0: [sda] Got wrong page
sd 0:1:0:0: [sda] Assuming drive cache: write through
sd 0:1:0:0: [sda] Got wrong page
sd 0:1:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2 sda3
sd 0:1:0:0: [sda] Got wrong page
sd 0:1:0:0: [sda] Assuming drive cache: write through
sd 0:1:0:0: [sda] Attached SCSI disk
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
dracut: Scanning devices sda3 for LVM logical volumes vg_sspaswl11g3/lv_root vg_sspaswl11g3/lv_swap
dracut: inactive '/dev/vg_sspaswl11g3/lv_root' [50.00 GiB] inherit
dracut: inactive '/dev/vg_sspaswl11g3/lv_home' [15.00 GiB] inherit
dracut: inactive '/dev/vg_sspaswl11g3/lv_swap' [19.68 GiB] inherit
dracut: inactive '/dev/vg_sspaswl11g3/lv_oracle' [50.00 GiB] inherit
EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
dracut: Mounted root filesystem /dev/mapper/vg_sspaswl11g3-lv_root
dracut: Loading SELinux policy
type=1404 audit(1378220065.747:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
SELinux: 2048 avtab hash slots, 250819 rules.
SELinux: 2048 avtab hash slots, 250819 rules.
SELinux: 9 users, 12 roles, 3762 types, 187 bools, 1 sens, 1024 cats
SELinux: 81 classes, 250819 rules
SELinux: Permission audit_access in class file not defined in policy.
SELinux: Permission audit_access in class dir not defined in policy.
SELinux: Permission execmod in class dir not defined in policy.
SELinux: Permission audit_access in class lnk_file not defined in policy.
SELinux: Permission open in class lnk_file not defined in policy.
SELinux: Permission execmod in class lnk_file not defined in policy.
SELinux: Permission audit_access in class chr_file not defined in policy.
SELinux: Permission audit_access in class blk_file not defined in policy.
SELinux: Permission execmod in class blk_file not defined in policy.
SELinux: Permission audit_access in class sock_file not defined in policy.
SELinux: Permission execmod in class sock_file not defined in policy.
SELinux: Permission audit_access in class fifo_file not defined in policy.
SELinux: Permission execmod in class fifo_file not defined in policy.
SELinux: Permission syslog in class capability2 not defined in policy.
SELinux: the above unknown classes and permissions will be allowed
SELinux: Completing initialization.
SELinux: Setting up existing superblocks.
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev dm-0, type ext4), uses xattr
type=1403 audit(1378220066.125:3): policy loaded auid=4294967295 ses=4294967295
dracut:
dracut: Switching root
readahead: starting
udev: starting version 147
WARNING! power/level is deprecated; use power/control instead
be2net 0000:16:00.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34
be2net 0000:16:00.0: setting latency timer to 64
be2net 0000:16:00.0: POST error; stage=0x400
be2net 0000:16:00.0: PCI INT A disabled
be2net 0000:16:00.0: Emulex OneConnect 10Gbps NIC(be3) initialization failed
be2net: probe of 0000:16:00.0 failed with error -1
be2net 0000:16:00.1: PCI INT B -> GSI 37 (level, low) -> IRQ 37
be2net 0000:16:00.1: setting latency timer to 64
be2net 0000:16:00.1: POST error; stage=0x400
be2net 0000:16:00.1: PCI INT B disabled
be2net 0000:16:00.1: Emulex OneConnect 10Gbps NIC(be3) initialization failed
be2net: probe of 0000:16:00.1 failed with error -1
be2net 0000:16:00.4: PCI INT A -> GSI 34 (level, low) -> IRQ 34
be2net 0000:16:00.4: setting latency timer to 64
be2net 0000:16:00.4: POST error; stage=0x400
be2net 0000:16:00.4: PCI INT A disabled
be2net 0000:16:00.4: Emulex OneConnect 10Gbps NIC(be3) initialization failed
be2net: probe of 0000:16:00.4 failed with error -1
be2net 0000:16:00.5: PCI INT B -> GSI 37 (level, low) -> IRQ 37
be2net 0000:16:00.5: setting latency timer to 64
be2net 0000:16:00.5: POST error; stage=0x400
be2net 0000:16:00.5: PCI INT B disabled
be2net 0000:16:00.5: Emulex OneConnect 10Gbps NIC(be3) initialization failed
be2net: probe of 0000:16:00.5 failed with error -1
be2net 0000:16:00.6: PCI INT C -> GSI 36 (level, low) -> IRQ 36
be2net 0000:16:00.6: setting latency timer to 64
be2net 0000:16:00.6: POST error; stage=0x400
be2net 0000:16:00.6: PCI INT C disabled
be2net 0000:16:00.6: Emulex OneConnect 10Gbps NIC(be3) initialization failed
be2net: probe of 0000:16:00.6 failed with error -1
be2net 0000:16:00.7: PCI INT D -> GSI 38 (level, low) -> IRQ 38
be2net 0000:16:00.7: setting latency timer to 64
be2net 0000:16:00.7: POST error; stage=0x400
be2net 0000:16:00.7: PCI INT D disabled
be2net 0000:16:00.7: Emulex OneConnect 10Gbps NIC(be3) initialization failed
be2net: probe of 0000:16:00.7 failed with error -1
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143)
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
cdc_ether 2-1.1.5:1.0: usb0: register 'cdc_ether' at usb-0000:00:1d.0-1.1.5, CDC Ethernet Device, 36:40:b5:d1:00:67
usbcore: registered new interface driver cdc_ether
sd 0:1:0:0: Attached scsi generic sg0 type 0
scsi 0:0:0:0: Attached scsi generic sg1 type 0
scsi 0:0:1:0: Attached scsi generic sg2 type 0
sr 1:0:0:0: Attached scsi generic sg3 type 5
input: PC Speaker as /devices/platform/pcspkr/input/input4
microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU2 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU3 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU4 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU5 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU6 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU7 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU8 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU9 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU10 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU11 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU12 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU13 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU14 sig=0x206d7, pf=0x1, revision=0x70b
microcode: CPU15 sig=0x206d7, pf=0x1, revision=0x70b
microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
EXT4-fs (dm-0): re-mounted. Opts: (null)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
SELinux: initialized (dev sda2, type ext4), uses xattr
SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
SELinux: initialized (dev dm-2, type ext4), uses xattr
EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
SELinux: initialized (dev dm-3, type ext4), uses xattr
Adding 20635644k swap on /dev/mapper/vg_sspaswl11g3-lv_swap. Priority:-1 extents:1 across:20635644k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
NET: Registered protocol family 10
iscsi: registered transport (iser)
libcxgbi:libcxgbi_init_module: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
libcxgbi:ddp_setup_host_page_size: system PAGE 4096, ddp idx 0.
Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010)
iscsi: registered transport (cxgb3i)
Chelsio T4 iSCSI Driver cxgb4i v0.9.1 (Aug. 2010)
iscsi: registered transport (cxgb4i)
cnic: Broadcom NetXtreme II CNIC Driver cnic v2.5.10 (March 21, 2012)
Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.0.3 (Jun 15, 2011)
iscsi: registered transport (bnx2i)
iscsi: registered transport (be2iscsi)
ip6_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
usb0: no IPv6 routers present
802.1Q VLAN Support v1.8
bnx2fc: Broadcom NetXtreme II FCoE Driver bnx2fc v1.0.10 (Jan 22, 2011)
TARGET_CORE[0]: Loading Generic Kernel Storage Engine: v4.0.0-rc7-ml on Linux/x86_64 on 2.6.39-200.24.1.el6uek.x86_64
SELinux: initialized (dev configfs, type configfs), uses genfs_contexts
TARGET_CORE[0]: Initialized ConfigFS Fabric Infrastructure: v4.0.0-rc7-ml on Linux/x86_64 on 2.6.39-200.24.1.el6uek.x86_64
TCM: Registered subsystem plugin: rd_dr struct module:           (null)
TCM: Registered subsystem plugin: rd_mcp struct module:           (null)
CORE_HBA[0] - TCM Ramdisk HBA Driver v4.0 on Generic Target Core Stack v4.0.0-rc7-ml
CORE_HBA[0] - Attached Ramdisk HBA: 0 to Generic Target Core TCQ Depth: 256 MaxSectors: 1024
CORE_HBA[0] - Attached HBA to Generic Target Core
RAMDISK: Referencing Page Count: 8
CORE_RD[0] - Built Ramdisk Device ID: 0 space of 8 pages in 1 tables
rd_dr: Using SPC_PASSTHROUGH, no reservation emulation
rd_dr: Using SPC_ALUA_PASSTHROUGH, no ALUA emulation
Vendor: LIO-ORG   Model: RAMDISK-DR        Revision: 4.0
Type:   Direct-Access                      ANSI SCSI revision: 05
CORE_RD[0] - Added TCM DIRECT Ramdisk Device ID: 0 of 8 pages in 1 tables, 32768 total bytes
TCM: Registered subsystem plugin: pscsi struct module: ffffffffa056ece0
TCM: Registered subsystem plugin: fileio struct module: ffffffffa0575700
TCM: Registered subsystem plugin: iblock struct module: ffffffffa057a740
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
pci 0000:04:00.0: Invalid ROM contents
fuse init (API version 7.16)
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
usb 1-1.2.2.1: new high speed USB device number 6 using ehci_hcd
usb 1-1.2.2.1: New USB device found, idVendor=058f, idProduct=6387
usb 1-1.2.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2.2.1: Product: Mass Storage
usb 1-1.2.2.1: Manufacturer: Generic
usb 1-1.2.2.1: SerialNumber: 68204C70
scsi2 : usb-storage 1-1.2.2.1:1.0
scsi 2:0:0:0: Direct-Access     Generic Flash Disk       8.07 PQ: 0 ANSI: 2
sd 2:0:0:0: Attached scsi generic sg4 type 0
sd 2:0:0:0: [sdb] 2052096 512-byte logical blocks: (1.05 GB/1002 MiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
udev: starting version 147
udev: starting version 147
udev: starting version 147
udev: starting version 147
usb0: no IPv6 routers present
usb 1-1.2.2.1: USB disconnect, device number 6
usb 1-1.2.2.1: new high speed USB device number 7 using ehci_hcd
usb 1-1.2.2.1: New USB device found, idVendor=058f, idProduct=6387
usb 1-1.2.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2.2.1: Product: Mass Storage
usb 1-1.2.2.1: Manufacturer: Generic
usb 1-1.2.2.1: SerialNumber: 68204C70
scsi3 : usb-storage 1-1.2.2.1:1.0
scsi 3:0:0:0: Direct-Access     Generic Flash Disk       8.07 PQ: 0 ANSI: 2
sd 3:0:0:0: Attached scsi generic sg4 type 0
sd 3:0:0:0: [sdb] 2052096 512-byte logical blocks: (1.05 GB/1002 MiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 3:0:0:0: [sdb] No Caching mode page present
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sd 3:0:0:0: [sdb] No Caching mode page present
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 3:0:0:0: [sdb] No Caching mode page present
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sd 3:0:0:0: [sdb] Attached SCSI removable disk
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
usb 1-1.2.2.1: USB disconnect, device number 7
usb 1-1.2.2.1: new high speed USB device number 8 using ehci_hcd
usb 1-1.2.2.1: New USB device found, idVendor=1e3d, idProduct=2093
usb 1-1.2.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2.2.1: Product: Flash Disk
usb 1-1.2.2.1: Manufacturer: USB 2.0
usb 1-1.2.2.1: SerialNumber: 0719440042B25701
scsi4 : usb-storage 1-1.2.2.1:1.0
scsi 4:0:0:0: Direct-Access     USB 2.0 Flash Disk       5.00 PQ: 0 ANSI: 2
sd 4:0:0:0: Attached scsi generic sg4 type 0
sd 4:0:0:0: [sdb] 2052096 512-byte logical blocks: (1.05 GB/1002 MiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 0b 00 00 08
sd 4:0:0:0: [sdb] No Caching mode page present
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] No Caching mode page present
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 4:0:0:0: [sdb] No Caching mode page present
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] Attached SCSI removable disk
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
[root@sspaswl11g3 Desktop]#

Vlan tag issue with Nexus 4001 in IBM Blade Centre

Hi
I have a DC architecture with a pair of Nexus 7010's running 3 VDC's (Core/Aggregation/Enterprise). I have at the edge Nexus 5548's which connect to back to the Aggregation VDC. Also connecting back to the Aggregation VDC is an IBM Blade Chassis which has a Nexus 4001i in slots 7 and slot 9. These blade servers are running ESXi 4.0 and are mapped to the Nexus 4001 blade switch.
I had set up the Native VLAN as VLAN 999 which connects up to the ESXi host and I am trunking up multiple VLANS for the Virtual Machines.
The problem I have is that VM's in all VLANS except the ESXi host VLAN (VLAN 10) cannot see their default gateway, and I suspect that there is an issue with the VLAN tag going up to the ESXi host. I have read enough documentation to suggest that this is where the issue is.
My Nexus 4001 interface configuration is below
interface Ethernet1/1
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 10,30,40-41,60-62,90,96,999
spanning-tree port type edge trunk
speed auto
The Aggregation VDC on the Nexus 7010 is the default gateway for all these VLANS.
I also noted that the Nexus 5000 and Nexus 7000 supports the command vlan dot1q tag native command yet the Nexus 4000 doesn't seem to support this. Any assistance would be useful
Thanks
Greg

Your configuration on the N4K looks correct. You shouldn't use vlan dot1q tag native commands on your N7Ks and N5Ks. Native VLAN tagging is really for QinQ (dot1q tunneling).
My only suggestion is check your configuration of the vSwitch in the ESXi host and the host network profile.
Regards,
jerry

How to pass a filename to MQHRF2 header in IBM MQ using JMS Adapter in SAP PI

Hi Expers,
Can you please help on ...
how to pass a filename to MQHRF2 header in IBM MQ using JMS Adapter in SAP PI
Thanks,
Chandar

Hi Chandar,
Could you check the following post Re: Inserting custom header fields inside MQRFH2 (JMS Receiver adapter)?
I hope you find it useful.
Regards!

Hyper-V fails to start, though NX bit is in proper state. IBM Blade Center.

Hi!
Please help, I'm in dead end.
I'm trying to start hyper-v in Blade. But launch fails. Here is an event log error:
System
Microsoft-Windows-Hyper-V-Hypervisor
2/6/2009 11:59:36 AM
Error code: 52
Error
User: SYSTEM
Computer: WIN-4DG9NOAK4J9
Description:
Hyper-V launch failed; No-execute (NX) or DEP not enabled on processor 0x0 (check BIOS settings).
Xml events:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
   <Provider Name="Microsoft-Windows-Hyper-V-Hypervisor" Guid="{52fc89f8-995e-434c-a91e-199986449890}" />
   <EventID>52</EventID>
   <Version>0</Version>
   <Level>2</Level>
   <Task>0</Task>
   <Opcode>0</Opcode>
   <Keywords>0x8000000000000000</Keywords>
   <TimeCreated SystemTime="2009-02-06T08:59:36.921Z" />
   <EventRecordID>6140</EventRecordID>
   <Correlation />
   <Execution ProcessID="4" ThreadID="8" />
   <Channel>System</Channel>
   <Computer>WIN-4DG9NOAK4J9</Computer>
   <Security UserID="S-1-5-18" />
  </System>
  <EventData>
   <Data Name="CPU">0x0</Data>
  </EventData>
</Event>
I checked bios settings for blade, Dep is enabled. But hyper-v still fails.
Blade configuration (bought a month ago):
IBM Blade Center
Blade HS21:
2x Intel Xeon 5405.
6GB RAM
2x SAS 76GB.
I looked through other disscussions on the subject but nothing helped. Trick with changing Regional setting doesn't help either.
W2k8 std I bought in august 2008.
uch

Just to clarify:
You have enabled virtualization on the chipset.
You have enabled DEP
You then powered off the server.
Then you added the Hyper-V role.
I mention the first steps, becuase the machine must be fully shut down (cold boot) after DEP is enabled for it to properly report. Just rebooting or exiting the BIOS and booting (warm boot) won't take the setting properly.
I have done this a couple times myself with new hardware.. Just getting in a rush.Brian Ehlert
(hopefully you have found this useful)

Anyone tried to deploy IBM's Java resource adapter for IMS on WLS6.1sp2?

          Has anyone had success or attempted to deploy the IMS Connector
          for Java (IBM's resource adapter) on WLS6.1sp2? I would like to
          use this to connect WebLogic to IMS via IMS Connect 1.2?
          Thanks
          Sam


          "Sam Naylor" <[email protected]> wrote:
          >
          >Has anyone had success or attempted to deploy the IMS Connector
          >for Java (IBM's resource adapter) on WLS6.1sp2? I would like to
          >use this to connect WebLogic to IMS via IMS Connect 1.2?
          >
          >Thanks
          >Sam
          Sam,
          I was wondering if you were able to use the IMN Connector RAR file. I was able
          to deploy but that was teh extent of my effort.
          Appreciate you insight!

Anyone used the IBM Message Broker PeopleSoft Adapter

Is anyone out there using the PeopleSoft Adapter for the IBM Message Broker
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.wmbadapters_v6/wmbadapters/6.1/PeopleSoftAdapter.html
I'm interested in sharing best practice in developing PeopleSoft CIs that connect to the IBM event adapter.
Many thanks
Graham

John,
Following could be the reasons:
1. Make sure that the path in the jar file for the class files(PeopleSoft CI java api) exactly matches the following:
\PeopleSoft\Generated\CompIntfc
Upper and lower case differences should be followed exactly.
2. The Java API for the selected component interface is not found in the API JAR file. Please check the Java API for the class file for the CI. If not found, please add the class file for the CI.
3. The component interface name is mentioned incorrectly in the request document.
4. If you are using 10.1.3.x version of SOA Suite, then make sure that the component interface jar is included in the server.xml. Please see the details for this in the 10.1.3.x application adapter installation guide.
5. Following could also be an issue:
LOCATION Component Interface
Explanation
When you attempt to access the LOCATION Component Interface using the Human Resources application, release 8.80.000, a failure occurs during runtime and the following message is displayed:
Component Interface Not Found
This is due to a problem in the way the PeopleSoft application has been delivered and is not related to the PeopleTools release.
Workaround
Perform the following steps:
1. Open the component interface in the PeopleTools Application Designer.
2. Make a small change to the component interface.
3. Undo the change.
4. Save the component interface.
This procedure resets certain internal PeopleSoft data structures, which enables the Adapter for PeopleSoft to find the component interface. This has been observed in the LOCATION Component Interface running on the Human Resource applications release 8.8.000 on several different releases of PeopleTools, but it may
occur in other component interfaces as well.
Edited by: Siva Krishnajee on Jul 6, 2009 1:18 PM
Edited by: Siva Krishnajee on Jul 6, 2009 1:36 PM

Mini Dvi to Video Adapter woes

I've taken an extensive look at this problem, and I am very lost. I am trying to make an extended desktop on my Standard Definition Panasonic TV. When I plug in my Mini DVI to Video Apple adapter, I get a fuzzy outline of the screen, and am not sure how to fix this. Does anyone have any ideas?
Help would be greatly appreciated,
Dylan

Either way. You set if you want mirroring or two monitors in Display in System Preferences.

IMac CD with mini-DVI - Video adapter woes

I bought a mini-DVI to video adapter when I first got my iMac Core Duo. I never used it, and so a few weeks ago I was distressed to find out that it didn't work. So I ordered another, assuming the cable was the problem. Nope -- this one has the same trouble.
The problem is that the display is distorted and "rolls" occasionally like the V-Hold is off. There are also two black "bumps" or places where there are waves in the display, one on each side of the TV's tube. The TV itself is a little 20" Orion -- not too new, but not too old either.
* The TV should be fine, since I've used it with a mini-VGA to Video adapter with my previous Mac, an iBook G4.
* The cables should be fine, because I've switched them all out and tried different ones.
* The adapter should be fine, since I ordered another cable and it displays the same thing.
* The computer should be fine, since I can output to an LCD monitor with my mini-DVI -> VGA just fine and dandy.
So does anyone have an idea of what the problem might be? I'm really perplexed, and I don't think I'm missing anything obvious. Like I said, I've used a couple of similar cables before without problems, my iMac is otherwise flawless, and so on.

I reinstalled the OS to see if that solved the problem. It didn't.
I tried to get an appointment with an Apple Genius, but apparently the Concierge was experiencing a large amount of traffic and could not help me. I don't really understand if I'll be charged for calling tech support (I'm out of the 90-day period, but obviously not out of warranty), so I don't particularly want to drop any money for support on a computer that apparently arrived lacking a significant feature. Unless I'm greatly mistaken, that's also known as DOA...

Enabling AAA on IBM blade server switches

I am having some trouble getting users to be able to log in to the web gui for the cisco switches that are built in to the blade servers we bought. I have a feeling it is due to there being no enable login when you use the webgui but needing enable priveleges...
how am I supposed to set up the user in tacacs so (CSACS) so that they are able to log in to the web gui?
thanks in advance...

any ideas about this situation specifically? I have AAA working on all of our routers and switches (we manage them via CLI) and on these switches in the blade server, but we want users to be able to authenticate and use the GUI for these switches also.
I went into the groups the users in question belong to since the users are set under "Enable Options" to "Use Group Setting"
One user is a network engineer so his is set to "Max Privilege for any AAA Client (15)" but he still isnt able to log in via the web gui. Any ideas? Im not seeing anything in the "Failed Attempts" on the csacs server.

Etherchannel issue between 3750 stack and WS-CBS3012 for IBM blade centre

Hi,
We are trying to configure Etherchannel between four ports of cisco 3750 stack(2ports from one switch of stack and two ports from another switch of same stack). We are facing issues with this setup. The ports in WS-CBS3012 are going to err disable mode.
Is there any limitations associated with such a cross-stack etherchannel configuration. Please suggest if there is any particular sequence of configuration involved.
Switch1 in stack
int gi 3/0/3
switchport mo trunk
switchport trunk allowed vlan 10-30
sw tr en dot1q
channel-group 1 mode on
spanning-tree guard root
switch 2 in stack
int gi 3/0/3
switchport mode trunk
switchport trunk allowed vlan 10-30
sw tr en dot1q
channel-group 1 mode on
spanning-tree guard root
int port-channel 1
switchport mode trunk
switchport trunk allowed vlan 10-30
sw tr en dot1q
channel-group 1 mode on
spanning-tree guard root
in WS-CBS3012 ports are configured with trunk,allowed vlan and etherchannel configuration with mode on.
With Regards,
Madhan kumar G

Hi,
The commnad "no spanning-tree etherchannel guard misconfig" on WS-CBS3012 resolved the issue.
Regards,
Madhan kumar G

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

Pro's - Con's XI JMS adapter /IBM WBI XI adapter

Hi there,
I would like to know what are the pro's /con's of the XI JMS adapter and IBM's WebSphere XI adapter.
When and why to use which one..etc?
Also appreciate if someone can share some thoughts/previous experiences with one of these two adapters?
Tnx,
Roberto.

Hi,
Check Below links,
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
Regards,
Phani

Script to find, list and create Emulex NIC teaming

Hello all!
I need your help on creating a script (could be VBS or PS) to be used on IBM Blades.
I need to:
1. find all enabled Emulex OCl NICs,
2. list them,
3. unmount any teaming,
4. list them again and
5. mount two teaming of 2 NICs
NIC model is Emulex OCl11102-F-X Virtual Fabric Adapter 2-port 10Gb
Please advise if you can help me.
Thank you in advance for any suggestion.
Rafael

Ok, I have already started looking for something like this.
And could find some interesting posts.
I posted this one trying to have someone helping me creating it or just modifying any that already exists.
Or I'd appreciate any tips, i.e. how to handle the Emulex particularity.
Thanks anyway!
Rafael

VN-Tag with Nexus 1000v and Blades

Hi folks,
A while ago there was a discussion on this forum regarding the use of Catalyst 3020/3120 blades switches in conjunction with VN-tag. Specifically, you can't do VN-Tag with that Catalyst blade switch sitting inbetween the Nexus 1000V and the Nexus 5000. I know there's a Blade switch for the IBM blade servers, but will there be a similar version for the HP C-class blades? My guess is NO, since Cisco just kicked HP to the curb. But if that's the case, what are my options? Pass-through switches? (ugh!)
Previous thread:
https://supportforums.cisco.com/message/469303#469303

wondering the same...

IBM Blade HS23 Emulex Adapter Woes

Similar Messages

Maybe you are looking for