Justin S's questions

我们有一个在 Centos 6 服务器上运行的 Qlogic QLE2560 HBA。我需要远程删除附加的 LUN。我没有在设备上安装任何来自 qlogic 的软件。它们是连接到 P200 G3 SAN 的 2 个 LUN，我找不到任何关于如何删除它们的操作系统文档。

[root@server class]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: AMCC     Model: 9650SE-8LP DISK  Rev: 4.10
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: WDC WD1003FBYX-0 Rev: 01.0
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: WDC WD1003FBYX-0 Rev: 01.0
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: Slimtype Model: DVD A  DL8A4SH   Rev: HP54
  Type:   CD-ROM                           ANSI SCSI revision: 05
Host: scsi7 Channel: 00 Id: 00 Lun: 00
  Vendor: HP       Model: P2000 G3 FC      Rev: T230
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi7 Channel: 00 Id: 00 Lun: 01
  Vendor: HP       Model: P2000 G3 FC      Rev: T230
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3000DM001-1CH1 Rev: CC26
  Type:   Direct-Access                    ANSI SCSI revision: 05


[root@server ~]# lsmod | grep ql
qla2xxx_conf          335368  1 
qla2xxx              1023916  0 
intermodule            37892  2 qla2xxx_conf,qla2xxx


[root@server ~]# cat /proc/scsi/qla2xxx/7 
QLogic PCI to Fibre Channel Host Adapter for QLE2560:
        Firmware version 4.06.03 , Driver version 8.02.23-fo
BIOS version 3.13
FCODE version 3.19
EFI version 2.24
Flash FW version 5.07.00 8080
ISP: ISP2532, Serial# BFD1238D93292
Request Queue = 0x63a600000, Response Queue = 0x63bff0000
Request Queue count = 4096, Response Queue count = 512
Total number of active commands = 0
Total number of interrupts = 174363060
    Device queue depth = 0x20
Number of free request entries = 1456
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 0
Number of retries for empty slots = 0
Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
Number of reqs in failover_q= 0
Host adapter:loop state = <READY>, flags = 0x185a43
Dpc flags = 0x0
MBX flags = 0x0
Link down Timeout = 030
Port down retry = 030
Login retry count = 030
Commands retried with dropped frame(s) = 0
Product ID = 0000 0000 0000 0000


SCSI Device Information:
scsi-qla0-adapter-node=20000024ff0caf40;
scsi-qla0-adapter-port=21000024ff0caf40;
scsi-qla0-target-0=217000c0ff144101;

FC Port Information:
scsi-qla0-port-0=208000c0ff144101:217000c0ff144101:010000:81;
scsi-qla0-port-1=208000c0ff144101:257000c0ff144101:010100:82;
scsi-qla0-port-2=5001438012098edf:5001438012098ede:010200:1;
scsi-qla0-port-3=50014380120999bd:50014380120999bc:010300:2;
scsi-qla0-port-4=5001438012098e8b:5001438012098e8a:010400:83;

SCSI LUN Information:
(Id:Lun)  * - indicates lun is not registered with the OS.
( 0: 0): Total reqs 6258578, Pending reqs 0, flags 0x2, Dflags 0x0, 0:0:81 00
( 0: 1): Total reqs 6825301, Pending reqs 0, flags 0x2, Dflags 0x0, 0:0:81 00

我正在运行 Ubuntu 12.04 和 bind9。我的仅缓存 DNS 服务器实际上是一个开放的 dns 解析器，因此我正在尝试更正此问题。

我试图遵循本指南。

命名.conf

// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
#include "/etc/bind/named.conf.default-zones";

named.conf.local 只包含。

    //
    // Do any local configuration here
    //

    // Consider adding the 1918 zones here, if they are not used in your
    // organization
    //include "/etc/bind/zones.rfc1918";

命名的.conf.options

acl "trusted" {
        127.0.0.1/32;
        X.X.192.0/20;

};

options {
        recursion no;
        additional-from-cache no;
        allow-query { none; };
        dnssec-validation auto;
        auth-nxdomain no;    # conform to RFC1035
};

view "trusted" in {
        match-clients { trusted; };
        allow-query { trusted; };
        recursion yes;
        additional-from-cache yes;
        dnssec-validation auto;
        auth-nxdomain no;    # conform to RFC1035
};

我可以毫无问题地重新启动绑定，我可以查询绑定。然而，当我测试时，我仍然是一个开放的解析器，当我查看 DNS top 时，我所有的顶级查询都来自定义范围之外的 IP。所以我知道我有问题。

我目前正在尝试找到一种方法来平衡我们的 4 个邮件网关（运行邮件清理器）。我能够启动 HAProxy 并使用 tcp 模式来毫无问题地进行负载平衡。唯一真正的问题是我的源 IP 始终是 HAProxy 服务器，所以我的一些邮件过滤器检查现在没有用，因为我无法检查邮件是否来自已知的错误中继。

他们是否有任何可用于处理此类情况的 FLOSS 软件？我知道 HAProxy 具有这种能力，如果我让邮件网关将它用作默认网关，并编译一些额外的模块并配置 iptables。如果我只是缺少一个更简单的解决方案，我只是不想开始这条路。