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.

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]#

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)

Nexus 1K VEM module shutdown (with DELL BLADE server)

Hello, This is Vince.
I am doing one of PoC with important customer.
Can anyone help me to explain what the problem is?
I have been found couples of strange situation in a Nexus 1000V with DELL BLADE server)
Actually, Network diagram is like below.
I installed each two Vsphere Esxi on the Dell Blade server.
As Diagram shows each server is connected to Cisco N5K via M8024 Dell Blade Switch.
- two N1KV VM are installed on the Esxi. (of course as Primary and Secondary)
- N5K is connected to M8024 in vPC.
- VSM and VEM are checking each other via Layer3 control interface.
- the way of uplink's port-profile port channel LB is mac pinning.
interface control0
ip address 10.10.100.10/24
svs-domain
domain id 1
control vlan 1
packet vlan 1
svs mode L3 interface control0
port-profile type ethernet Up-Link
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1-2,10,16,30,77-78,88,100,110,120-121,130
switchport trunk allowed vlan add 140-141,150,160-161,166,266,366
service-policy type queuing output N1KV_SVC_Uplink
channel-group auto mode on mac-pinning
no shutdown
system vlan 1,10,30,100
state enabled
n1000v# show module
Mod Ports Module-Type                       Model               Status
1    0      Virtual Supervisor Module         Nexus1000V          ha-standby
2    0      Virtual Supervisor Module         Nexus1000V          active *
3    332    Virtual Ethernet Module           NA                  ok
4    332    Virtual Ethernet Module           NA                  ok
Mod Sw                  Hw
1    4.2(1)SV2(2.1a)     0.0
2    4.2(1)SV2(2.1a)     0.0
3    4.2(1)SV2(2.1a)     VMware ESXi 5.5.0 Releasebuild-1331820 (3.2)
4    4.2(1)SV2(2.1a)     VMware ESXi 5.5.0 Releasebuild-1331820 (3.2)
Mod Server-IP        Server-UUID                           Server-Name
1    10.10.10.10      NA                                    NA
2    10.10.10.10      NA                                    NA
3    10.10.10.101     4c4c4544-0038-4210-8053-b5c04f485931 10.10.10.101
4    10.10.10.102     4c4c4544-0043-5710-8053-b4c04f335731 10.10.10.102
Let me explain what the strange things happened from now on.
If I move the Primary N1KV on the module 3 to the another Esxi of the module 4, VEM will be shutdown suddenly.
Here is sys logs.
2013 Dec 20 15:45:22 n1000v %VEM_MGR-2-VEM_MGR_REMOVE_NO_HB: Removing VEM 4 (heartbeats lost)
2013 Dec 20 15:45:22 n1000v %VIM-5-IF_DETACHED_MODULE_REMOVED: Interface Ethernet4/7 is detached (module removed)
2013 Dec 20 15:45:22 n1000v %VIM-5-IF_DETACHED_MODULE_REMOVED: Interface Ethernet4/8 is detached (module removed)
2013 Dec 20 15:45:22 n1000v %VIM-5-IF_DETACHED_MODULE_REMOVED: Interface Vethernet1 is detached (module removed)
2013 Dec 20 15:45:22 n1000v %VIM-5-IF_DETACHED_MODULE_REMOVED: Interface Vethernet17 is detached (module removed)
2013 Dec 20 15:45:22 n1000v %VIM-5-IF_DETACHED_MODULE_REMOVED: Interface Vethernet9 is detached (module removed)
2013 Dec 20 15:45:22 n1000v %VIM-5-IF_DETACHED_MODULE_REMOVED: Interface Vethernet37 is detached (module removed)
2013 Dec 20 15:46:53 n1000v %VEM_MGR-2-MOD_OFFLINE: Module 4 is offline
If I wanna make it works again then I have to do two things.
First of all, It should be selected on the Source MAC Check the way of vSwitch's Load balance.
(Port ID check is the default)
Second of all, the the order of Switch's fail over is very important.
If I change this order then VEM will be off in very soon.
Here you go, the screen capture file of These option. (you may not understand these Korean letters.)
In my opinion, the main problem is the link part between Esxi and M8024.
As you saw, Each Esxi is connected to two M8024 Dell Blade switches separately.
I saw the manual for the way N1K's uplink Load balance.
Even though there are 16 different port-channel LB way,
but It should be used only the way of src-mac If there is no supporting port-channel option in the upstreaming switches.
But I don't know exactly why this situation happened.
Can anyone help me how I make it works better.
Thanks in advance.
Best Regards,
Vince

There's not enough information to determine the reason by those two outputs alone. All those commands tell us is the VSM is removing/attaching the VEM.
The normal cause for the VEM to flap is a problem with the Control VLAN communication. The loss of 6 consecutive heart beats will cause the VEM to detach from the VSM. We need to isolate the reason why.
-Which version of 1000v & ESX?
-Are multiple VEMs affected or just one?
-Are the VSM's interfaces hosted on the DVS or vSwitch?
-What is the network topology between the VEM and VSM (primarily the control VLAN)
-Do you have the Cisco SR # I can take a look into it. TAC is your best course of action for an issue like this. There will likely need to be live troubleshooting into your network environment to determine the cause.
Regards,
Robert

Issue w/ Case Differences Using the IBM Directory Server MA

We have the following issue using the IBM Directory Server MA using FIM 2010 R2 (Version 4.1.3479.0).
We provision a new object, e.g., uid=jdoe,ou=users,o=contoso, into an instance of IBM Directory Server
The object is created in IBM Directory Server as uid=jdoe,ou=users,o=contoso
A Full Import on the IBM Directory Server MA runs and confirms the export
Subsequent imports, sync, and exports run successfully
<Time passes>
A Full Import on the IBM Directory Server MA runs, and this object shows up as a staging-error (uid=jdoe,ou=Users,o=contoso)
Subsequent imports and syncs report errors on this object (staging-error)
Note that we do not manipulate the anchor (DN) of this object once it is created in IBM Directory Server. Other attributes are synchronized, but the object is never renamed/moved. This case change does not happen with all of the objects brought
in during the Full Import, but the number of instances do increase periodically. At this point, it does look like the import is changing from a lowercase "u" to an uppercase "U" but not vice versa.
I found a related
TechNet article containing the following remark:
"IBM Directory Server does not guarantee that the case of a DN component will match in all instances. On a synchronization or import from IBM Directory Server, this can manifest itself as an unexpected update. For example, if you create
O=TEST, and then create the user cn=MikeDan,O=TEST, this might be imported from IBM Directory Server as
cn=MikeDan,O=test. Because of the case difference, FIM treats this as an update on subsequent full imports."
Unfortunately, the article does not propose a resolution.
Has anyone encountered this issue? More importantly has anyone resolved this or found an acceptable workaround?
Note that deleting the connector space is not an acceptable workaround. :)

I remember experiencing this issue when we were on 5.0, and I believe it persists through 5.1 as well.
There is a comment in the 5.2 release notes that something similar was fixed:
Changing case sensitive attribute values failed in MMR. (4624693)
If I had to take a wild guess, I would say that the server does some internal checking to see if the value has changed, possibly based on the attribute syntax, to avoid replicating "changes" that really don't change anything except case. I doubt that all your custom attributes are case-sensitive, though. Enabling replication probably "turns on" this behavior, which doesn't go away even if replication is disabled.
In any case, you're probably out of luck unless/until you upgrade to 5.2.

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

Enabling aaa authorization on pix/asa

I managed to get authentication on easy enough but now am having difficulty getting authorization to work properly. I have auth/author turned on for my IOS stuff so any techs logged in will have rights based on what I give them on secure ACS. However I can't get the same to work on PIX code. I can log in fine with aa authentication but it still prompts me for the enable password. End result is I want to be able to login just once (and enabled). Any white papers that can point me the right way?

Thank you, Prem. here is my concern. When I enable AAA access on the firewalls, from what you said there is no way for me to govern what rights a tech has when accessing the device? I want to establish the same restrictions as the IOS gear I have where normal techs will only have certain commands and others have full command. The way it is now, anyone with an account on Secure ACS can access it via ASDM.
EDIT:
Also I'm a little confused about the various fields on the AAA Access (from Device Access) tab. In Authentication, there is an option to toggle to require auth to be able to use enable mode. I am not sure how this auth against our ACS server (i checked the various settings in ACS and enabled what I think are all PIX commands to permit enable) and it doesn't work. I entere the enable password when I telnet in and I get auth failed when running any commands.
Also there is an Authorization tab which I am assuming allows to you to push down rights from an aaa server? Where on the ACS can I configure that?

Span blade server on Cisco 3020?

I have an HP blade center with a Cisco 3020. From what I know, the baldes use a connection on the backplane for network connectivity. So my question is, can you setup a monitoring session to capture traffic from one individual blade server? I would normally span source interface destination interface. But how do I specify the blade server's interface when it's not on the switch itself? Thanks.

Hi Josh,
I'm not sure I really follow you here. The backplane of the blade server chassis is simply used as a communications channel between the blade server NICs and the server facing interfaces of the switch i.e., Gi0/1-16 and has no real bearing on how SPAN would work.
SPAN in the Catalyst 3020 switch works in exactly the same way as other Catalyst switches, with you specifying the source and destination interfaces etc., as you normally would. So assuming you have a server connected to Gi0/1 that you wanted to capture traffic to/from then you would configure something along the lines of monitor session 1 source interface gi0/1.
The tricky part can be the SPAN session destination and you have a number of options.
Use a server within the same chassis as the capture device.
If you have a server in the same chassis that has packet capture capability then you simply specify its NIC interface as the SPAN destination e.g., monitor session 1 destination interface gi0/2. The problem here is that when the destination interface goes into the monitoring state you'll lose in-band connectivity to the server so you would need to use the console to access the server.
Attach an external capture device to one of the switches external interfaces
The Catalyst 3020 has eight external facing interfaces i.e., Gi0/17-24 which are typically used for upstream network connectivity. If not all of these are in use then attach your capture device to one of those interfaces and configure the SPAN destination appropriately e.g., monitor session 1 destination interface Gi0/24.
Attach your capture device to an upstream switch and, on the Catalyst 3020, use an RSPAN VLAN as the destination to carry the traffic
This requires you define an RSPAN VLAN on the Catalyst 3020 and configure this as the SPAN destination. This VLAN is then configured on the external interfaces between your Catalyst 3020 and the upstream switch, where you would connect your capture device. In this case the upstream switch obviously requires a SPAN session to be configured as well.
There's discussion on the use of SPAN and RSPAN in the Integrating the Cisco Catalyst Blade Switch 3020 for the HP c-Class BladeSystem into the Cisco Data Center Network Architecture design guide that would go into more detail and has examples configurations.
Regards

EtherChannel Bundle for an HP Blade server

I'm running a Catalyst 6513 switch with Native IOS installed. I have created a EtherChannel bundle for an HP Blade server running with two clustered (teamed) NICs. The configurations are as follows:
interface Port-channel100
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2
switchport mode trunk
end
interface GigabitEthernet10/35
description XPQASRV13 (Cable No.35)
no ip address
speed 100
duplex full
switchport
switchport trunk allowed vlan 2
switchport mode trunk
channel-protocol lacp
channel-group 100 mode active
end
interface GigabitEthernet11/42
description XPQASRV13 (Cable No.90)
no ip address
speed 100
duplex full
switchport
switchport trunk allowed vlan 2
switchport mode trunk
channel-protocol lacp
channel-group 100 mode active
end
The problem is that running the interfaces at 1GiG causes the two NICs to insert and de-insert on the network every second but forcing them to 100 Meg makes them perform normally. These are connected using Cat5e cables which are 1GIG certified. What could be the cause for this problem?

As per your mention, I think the problem is with the server on the other side. The speed is not compatible on the other. Why don't you set the speed/duplex to auto and check it out?.

Oracle 10g rac installation on IBM power server

Dear Gurus,
I am installing Oracle 10g RAC on IBM power server but while running CRS getting the following errors. Please help to resolve this issue.
OUTPUT from Installation log:
INFO: Start output from spawned process:
INFO: INFO:
INFO: /oracle/app/oracle/product/crs/bin/genclntsh
INFO: /usr/bin/ld: cannot find -lxl
INFO: collect2: ld returned 1 exit status
INFO: genclntsh: Failed to link libclntsh.so.10.1
INFO: make:
INFO: *** [client_sharedlib] Error 1
INFO: End output from spawned process.
INFO: INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'client_sharedlib' of makefile '/oracle/app/oracle/product/crs/network/lib/ins_net_client.mk'. See '/oracle/app/oracle/oraInventory/logs/installActions2011-12-26_04-40-48PM.log' for details.
Exception Severity: 1
INFO: Exception handling set to prompt user with options to Retry Ignore
SYSTEM:
IBM power server
Linux 5.3
I have already tried changing ORACLE_HOME,CRS_HOME,LD_LIBRARY_PATH but nothing worked.
Regards,
Prajash

Those errors remind me on errors I encountered when I was trying to do installation that was not certified,
so try to check if installation you are doing is actually supported.
In the meantime , visit metalink and read document [ID 460969.1] , */usr/bin/ld: Cannot Find -lxml10, Genclntsh: Failed To Link Libclntsh.so.10.1*

Internal Server Error while using IBM HTTP SERVER

I used Webstudio tool to develop a JSP page and publish it on the IBM HTTP Server. When i was previewing the file, I got a internal server error 500 with the message of misconfiguration. I will be
extremely happy if you can provide an answer for this. All the path and classpath settings are good.
Thanks
Srini_gs

Are you talking AS400? Websphere Application Server? Are you sure the file is in the right place? By default jsp's go in a folder or directory called 'web' which resides in the same directory as the 'servlets' directory. So in one directory you would have two directories, one called servlets for .class files and one called web for jsps. I don't know if this helps or not, but check it out. But I don't know if this were your problem if you wouldn't get a 'NOT FOUND' error instead of the misconfiguration error.

Got error: Location Code is not enabled in the XML Gateway Server

Hi,
When I perform Compliance rule screening on GTM - Globel Trade Management,that I defined GTM as an Trading Partner on EBS R12.1.3,
GTM can send response to EBS,but I see the following error message via Transaction Monitor on EBS workflow:
[The Standard:OAG, Transaction Type:ITM , Transaction SubType:EXPORT_COMPLIANCE and Location Code GTM6.2 is not enabled in the XML Gateway Server. Pls check your Setup.]
On EBS,I defined an ITM Partner for GTM,named 'GTM6.2',according to the document created by you: ITM Setup.doc
and I also finished the following steps:
1. ITM Application Users
2.ITM Partner Service Types
3.ITM Parameter Setup
4.Order Type Creation: ITM Only
5.Customer Creation: create a customer named 'GTM6.2', also enter 'GTM6.2' as EDI Location
6.Define Transactions on XML Gateway as following:
<Header>:
Party Type: Customer
Transaction Type: ITM
Transaction Sub Type: EXPORT_COMPLIANCE
<External Transactions (Lines)>:
Standard Code: OAG
External Transaction Type: ITM
External Transaction Sub Type: EXPORT_COMPLAINCE
Queue: APPLSYS.ECX_IN_OAG_Q
7.Define Trading Partners on XML Gateway as following:
<Header>:
Trading Partner Type: Customer
Trading Partner Name: GTM6.2
<Trading Partner Details>:
Transaction Type: ITM
External Transaction Type: ITM
External Transaction Sub Type: EXPORT_COMPLAINCE
Map: WSHITEIN
Source Trading Partner Location Code: GTM6.2 (same as the value what defined in EDI Location for customer)
I think the combination of External Transaction Type, External Transaction Subtype, Standard Code,Source Trading Partner Location Code
should be existing once done above steps, I have no idea why the error prompted.
Does someone can tell how to trace the error?
Thanks,
Rambler

user12254038 wrote:
Can you send any supporting documents on ITM Setup? My client is implementing ITM for the first time and I wanted to know more details on how it works in R12.1.3 version of EBS?Oracle International Trade Management (ITM) Partner Integration: Specifications [ID 572524.1]
International Trade Management Integration [ID 259691.1]
How Can I Tell if International Trade Management is Installed or Not? [ID 742539.1]
What are the Required Setups for International Trade Management (ITM) Flows in Shipping Execution? [ID 782861.1]
What Patches Provide the Latest Fixes and Enhancements for ITM Adapter? [ID 465122.1]
How to Generate Debug Information From ITM Adapter for XML Processing [ID 738925.1]
How to Generate Debug File for International Trade Management (ITM) [ID 1294853.1]
Thanks,
Hussein

We can't install Solaris 8 - IBM PC SERVER 315

Hello:
We are trying to install Solaris 8 (Intel) (02/02) in an IBM PC Server 315.
Some words about it:
- 128 Mb RAM
- Pentium Pro 200 Mhz
- Adaptec AHA-2940U/2940UW Ultra SCSI in PCI bus1,Slot 4 (Info from Solaris install) (Target 7)
- Hard Disk IBM SCSI (Target 0)
- CD-Rom SCSI IBM CDRM00203 (Target 6 of SCSI) (info from Solaris install)
We have a big problem.
We can't install Solaris from CD.
After Loading kernel , when it begins Searching /dev and /devices...we see this text in the screen repeated a lot of times:
WARNING: /pci@0,0/pci1011,24@2/pci9004,8178@1(adp0):
timeout: abort device, target=6 lun=0
And before this something like it has some problem and begins a resinc ??
Please Could you help us?
Solaris has been purchased from Sun on 12 March 2002
A lot of Thank's!
P.D: Please, excuse my poor English.
A lot of thank's.

two other severs wouldn't run the cd either? Break it down a little it will be more solvable. We will create two separate problems with this. First we will check the cd disk itself. Put in another system and install solaris. If that works, move to the cdrom drive....move it to the same computer you just installed solaris on...if it works then it is another problem.

RFC in IBM Websphere server

Hi all,
I want to run a Java application that calls SAP RFC in an IBM Websphere server. Right now its working fine in Tomcat server.(I have installed JCO for Tomacat).
What all are the steps (intallations and configurations) I need to do in Websphere server.
I came across terms like SAPODA and JCO. Is SAP ODA neccessary??? or JCO installation alone will work?
Thanks in advance
George

u need only sapjco.jar file and dll files ..............
u put sapjco.jar file in ibm/sdp/6.0/portal/eclipse/plugins/eis.webtools.sap.6.0_0
here u copy that file.....
go to dynamic webproject, right click>properties>java build path-->add external
jars>add that sapjco.jar file and click okfinish..
now u write ur program..........
it works fine...........

I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich P

Thank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P

Enabling AAA on IBM blade server switches

Similar Messages

Maybe you are looking for