免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
123下一页
最近访问板块 发新帖
查看: 12065 | 回复: 29
打印 上一主题 下一主题

HBA卡被禁用? 如何启用? [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2008-12-26 17:29 |只看该作者 |倒序浏览
操作系统solaris 9,主机v215,HBA 卡 qlc2462(SG-XPCIE2FC-QF4).
san的驱动包已经安装,相应的补丁也都打上了,在OS上也可以识别该HBA.
但是连上光纤线,从光纤线的另一端口不能看到光,那么当然不管直连还是连交换机都是没有用的了.开始以为是卡有问题,换了一块还是这样.
美国同事说:There is software that needs to be loaded on the server that will activate the card.其他的就没有说了,他去休假了,当然他也不愿意说,原因大家都知道的.
看起来这卡被他禁用了,但是我不知道他是怎么配置的?大家有知道的么?

我也就这个问题在sun开了case,目前sun的工程师也没有找到什么原因?

hostname# /usr/platform/sun4u/sbin/prtdiag -v | more

System Configuration: Sun Microsystems  sun4u Sun Fire V215

System clock frequency: 188 MHZ

Memory size: 8GB        



==================================== CPUs ====================================

               E$          CPU                    CPU     Temperature

CPU  Freq      Size        Implementation         Mask    Die   Amb.  Status      Location

---  --------  ----------  ---------------------  -----   ----  ----  ------      --------

0    1504 MHz  1MB         SUNW,UltraSPARC-IIIi     3.4     -     -    online      MB/P0

1    1504 MHz  1MB         SUNW,UltraSPARC-IIIi     3.4     -     -    online      MB/P1



================================= IO Devices =================================

Bus     Freq  Slot +      Name +

Type    MHz   Status      Path                          Model

------  ----  ----------  ----------------------------  --------------------

pci     188   MB          pci10b9,5237.10b9.5237 (usb)                     

              okay        /pci@1e,600000/pci@0/pci@1/pci@0/usb@1c



pci     188   MB          pci10b9,5237.10b9.5237 (usb)                     

              okay        /pci@1e,600000/pci@0/pci@1/pci@0/usb@1c,1



pci     188   MB          pciclass,0c0320 (usb)                           

              okay        /pci@1e,600000/pci@0/pci@1/pci@0/usb@1c,3



pci     188   MB          pci10b9,5229 (ide)                              

              okay        /pci@1e,600000/pci@0/pci@1/pci@0/ide@1f



pci     188   MB          pci14e4,1668 (network)                           

              okay        /pci@1e,600000/pci@0/pci@9/pci@0/network@4



pci     188   MB          pci14e4,1668 (network)                           

              okay        /pci@1e,600000/pci@0/pci@9/pci@0/network@4,1



pci     188   MB          pci14e4,1668 (network)                           

              okay        /pci@1e,600000/pci@0/pci@a/pci@0/network@4



pci     188   MB          pci14e4,1668 (network)                           

              okay        /pci@1e,600000/pci@0/pci@a/pci@0/network@4,1



pci     188   MB          scsi-pci1000,50 (scsi-2)      LSI,1064           

              okay        /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1



pciex   188   +SER-RIGHT/PCI0  SUNW,qlc (scsi-fcp)           QLE2462            

              okay        /pci@1e,600000/pci@0/pci@8/SUNW,qlc



pciex   188   +SER-RIGHT/PCI0  SUNW,qlc (scsi-fcp)           QLE2462            

              okay        /pci@1e,600000/pci@0/pci@8/SUNW,qlc





============================ Memory Configuration ============================

Segment Table:

-----------------------------------------------------------------------

Base Address       Size       Interleave Factor  Contains

-----------------------------------------------------------------------

0x0                4GB               4           BankIDs 0,1,2,3

0x1000000000       4GB               4           BankIDs 16,17,18,19



hostname# prtpicl -v -c scsi-fcp

  SUNW,qlc (scsi-fcp, 42000002e3)

  :_fru_parent   (4200000abbH)

  eviceID      0

  :UnitAddress   0

  :vendor-id     0x1077

  :device-id     0x2432

  :revision-id   0x3

  :subsystem-vendor-id   0x1077

  :subsystem-id  0x143

  :class-code    0xc0400

  :interrupts    00  00  00  01

  :fcode-rom-offset      0xb000

  :#address-cells        0x2

  :#size-cells   0

  :device_type   scsi-fcp

  :min-grant     0

  :max-latency   0

  :devsel-speed  0

  :short-version         1.24  11/15/06

  :compatible   (42000002f1TBL)

   | pciex1077,143.1077.143.3 |

   | pciex1077,143.1077.143 |

   | pciex1077,143 |

   | pciex1077,2432.3 |

   | pciex1077,2432 |

   | pciclass,c0400 |

  :reg  

00  07  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  01  07  00  10  00  00  00  00  00  00  00

00  00  00  00  00  00  00  01  00  03  07  00  14  00  00  00  00  00  00  00  00  00  00  00  00  00  00  10  00

  :node-wwn      20  00  00  1b  32  0d  5a  ee

  :port-wwn      21  00  00  1b  32  0d  5a  ee

  :model         QLE2462  

  :version       QLE2462 Host Adapter Driver(SPARC): 1.24  11/15/06

  :manufacturer  QLGC

  :assigned-addresses   

81  07  00  10  00  00  00  00  00  00  20  00  00  00  00  00  00  00  01  00  82  07  00  14  00  00  00  00  04  00  00

00  00  00  00  00  00  00  40  00  82  07  00  30  00  00  00  00  04  04  00  00  00  00  00  00  00  04  00  00

  :devfs-path    /pci@1e,600000/pci@0/pci@8/SUNW,qlc

  :binding-name  SUNW,qlc

  :instance      -1

  :_class        scsi-fcp

  :name  SUNW,qlc

  SUNW,qlc (scsi-fcp, 4200000307)

  :_fru_parent   (4200000abbH)

  eviceID      0

  :UnitAddress   0,1

  :vendor-id     0x1077

  :device-id     0x2432

  :revision-id   0x3

  :subsystem-vendor-id   0x1077

  :subsystem-id  0x143

  :class-code    0xc0400

  :interrupts    00  00  00  02

  :fcode-rom-offset      0xb000

  :#address-cells        0x2

  :#size-cells   0

  :device_type   scsi-fcp

  :min-grant     0

  :max-latency   0

  :devsel-speed  0

  :short-version         1.24  11/15/06

  :compatible   (4200000315TBL)

   | pciex1077,143.1077.143.3 |

   | pciex1077,143.1077.143 |

   | pciex1077,143 |

   | pciex1077,2432.3 |

   | pciex1077,2432 |

   | pciclass,c0400 |

  :reg  

00  07  01  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  01  07  01  10  00  00  00  00  00  00  00

00  00  00  00  00  00  00  01  00  03  07  01  14  00  00  00  00  00  00  00  00  00  00  00  00  00  00  10  00

  :node-wwn      20  01  00  1b  32  2d  5a  ee

  :port-wwn      21  01  00  1b  32  2d  5a  ee

  :model         QLE2462  

  :version       QLE2462 Host Adapter Driver(SPARC): 1.24  11/15/06

  :manufacturer  QLGC

  :assigned-addresses   

81  07  01  10  00  00  00  00  00  00  21  00  00  00  00  00  00  00  01  00  82  07  01  14  00  00  00  00  04  00  40

00  00  00  00  00  00  00  40  00  82  07  01  30  00  00  00  00  04  08  00  00  00  00  00  00  00  04  00  00

  :devfs-path    /pci@1e,600000/pci@0/pci@8/SUNW,qlc

  :binding-name  SUNW,qlc

  :instance      -1

  :_class        scsi-fcp

  :name  SUNW,qlc

hostname#

论坛徽章:
0
2 [报告]
发表于 2008-12-26 20:51 |只看该作者
大家有遇到这样的情况么?

论坛徽章:
0
3 [报告]
发表于 2008-12-27 16:03 |只看该作者
run below command:

modinfo|grep -i fc
luxadm -e port
luxadm qlgc
luxadm fcode_download -p

cat /kernel/drv/qlc.conf
cat /kernel/fp.conf
cat /kernel/fcp.conf


PS:有没有换过光纤线?

论坛徽章:
0
4 [报告]
发表于 2008-12-27 21:10 |只看该作者

回复 #3 skyoflzp 的帖子

上面的那些命令我在sun的工程师指导下运行过一次的,没有效果。

需要显示那些配置文件的内容,我周一贴上来。

光纤线肯定是好的,可以用在其他的HBA卡上,当然业换过光纤线的。

谢谢你的回复。

论坛徽章:
0
5 [报告]
发表于 2008-12-27 21:53 |只看该作者
把EIS补丁打到最新,主要是SAN PATCH
再重启一下机器。

论坛徽章:
0
6 [报告]
发表于 2008-12-28 11:31 |只看该作者

回复 #5 skyoflzp 的帖子

谢谢你的回复。

SAN的补丁都打上了,SUN的工程师检查过我的日志了,说没有问题。

论坛徽章:
7
荣誉会员
日期:2011-11-23 16:44:17水瓶座
日期:2013-08-28 21:20:16丑牛
日期:2013-10-02 21:01:462015年迎新春徽章
日期:2015-03-04 09:54:45操作系统版块每日发帖之星
日期:2016-06-05 06:20:0015-16赛季CBA联赛之吉林
日期:2016-06-20 08:24:0515-16赛季CBA联赛之四川
日期:2016-08-18 15:02:02
7 [报告]
发表于 2008-12-28 16:11 |只看该作者
原帖由 sousi 于 2008-12-28 11:31 发表
谢谢你的回复。

SAN的补丁都打上了,SUN的工程师检查过我的日志了,说没有问题。


2楼的兄台说了那么多,你照人家的帖子把输出贴出来看看啊,别浪费了人家的一片苦心!

论坛徽章:
0
8 [报告]
发表于 2008-12-29 10:49 |只看该作者

回复 #7 nimysun 的帖子

谢谢你的回复,我在上面的回复说周一贴,现在已经贴上来了,请大家帮忙分析,谢谢了.

sunshnis01# clear
sunshnis01# modinfo | grep -i fc
19  11ebf7a  2c3fc 208   1  mpt (MPT HBA Driver v1.23)
33  125291a    afc   -   1  todm5823 (tod module for ALI M5823 and co)
40  1237fce   18e1 225   1  mi2cv (MI2CV Nexus Driver 1.1)
50  12e65fc  281d1   2   1  tcp (TCP Streams module)
50  12e65fc  281d1  42   1  tcp (TCP Streams device 1.46)
67  1366ba6   8314   -   1  fctl (SunFC Transport v20070703-1.38)
70 78186000  cd574 153   1  qlc (SunFC Qlogic FCA v20070212-2.19)
129 78156000  126fc 226   1  rpcmod (RPC syscall)
129 78156000  126fc 226   1  rpcmod (32-bit RPC syscall)
129 78156000  126fc  16   1  rpcmod (rpc interface str mod)
152  13fccbd   202d  49   1  msgsys (System V message facility)
152  13fccbd   202d  49   1  msgsys (32-bit System V message facilit)
169 781c11fc    e57  14   1  iwscn (Workstation Redirection driver )
189  13c8501   1049  56   1  fcode (FCode driver 1.4)
190  13a0e34   2a8c   -   1  fcodem (FCode framework 1.13)
217 78278000  20bab 150   1  fcp (SunFC FCP v20070703-1.95)
322  125ffc7    bfb 176   1  inst_sync (instance binding syscall)
322  125ffc7    bfb 176   1  inst_sync (32-bit instance binding syscall)
sunshnis01# luxadm -e port

Found path to 0 HBA ports

sunshnis01# luxadm qlgc

  Found Path to 0 FC100/P, ISP2200, ISP23xx Devices
  Complete
sunshnis01# luxadm fcode_download -p

  Found Path to 0 FC/S Cards
  Complete

  Found Path to 0 FC100/S Cards
  Complete

  Found Path to 0 FC100/P, ISP2200, ISP23xx Devices
  Complete

  Found Path to 0 JNI1560 Devices.
  Complete

  Found Path to 0 Emulex Devices.
  Complete
sunshnis01# bash        
sunshnis01# cat /kernel/drv/qlc.conf
#
# Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# Qlogic Fibre Channel Adapter driver configuration
#
#ident  "@(#)qlc.conf   1.9     06/02/02 SMI"
#

#
# Copyright (C) QLogic Corporation 1998-2005. All rights reserved.
#
#   File is setup as the default parameters for all adapters in the
#   system.
#   If a parameter needs to be changed for a particular adapter,
#   make a copy of the parameter. Then change the hba number
#   (decimal) in the parameter to match the adapter instance number
#   that is displayed during the boot process. Now alter the
#   parameter for the adapter.
#
#   example:
#       Setting hard address of 124 and 125 for adapter
#       instance 3 and 4 respectively.
#
#       Before:
#           hba0-enable-adapter-hard-loop-ID=0;
#
#           hba0-adapter-hard-loop-ID=0;
#
#       After:
#           hba0-enable-adapter-hard-loop-ID=0;
#           hba3-enable-adapter-hard-loop-ID=1;
#           hba4-enable-adapter-hard-loop-ID=1;
#
#           hba0-adapter-hard-loop-ID=0;
#           hba3-adapter-hard-loop-ID=124;
#           hba4-adapter-hard-loop-ID=125;
#

#
# Enable/disable the use adapter hard loop ID address on the fibre
# channel bus.
#    0 = disable, 1 = enabled
hba0-enable-adapter-hard-loop-ID=0;


#
# Adapter hard loop ID address to use on the fibre channel bus.
#    Range: 0 - 125
hba0-adapter-hard-loop-ID=0;

#
# Sun StorEdge Traffic Manager Software (mpxio) may be enabled or disabled
# on a given qlc HBA port. Possible values are mpxio-disable="no" or
# mpxio-disable="yes". By default all ports have mpxio-disable="no".
# The following examples illustrate the syntax for disabling
# Multipath I/O feature through this configuration file.
#
# Example 1: To disable mpxio for a port on a single ported HBA
# with devicename /device/pci@6,2000/SUNW,qlc@2/fp@0,0:devctl
# add the following line to this file
#
# name="qlc" parent="/pci@6,2000" unit-address="2" mpxio-disable="yes";
#
# Example 2: To disable mpxio for a port on a dual ported HBA
# with devicename /devices/pci@13,2000/pci@2/SUNW,qlc@5/fp@0,0:devctl
# add the following line to this file
#
# name="qlc" parent="/pci@13,2000/pci@2" unit-address="5" mpxio-disable="yes";
#
#Name:  Maximum frame length
#Type:  Integer, bytes;  Range: 512, 1024, 2048
#       Default: 2048
#Usage: This field specifies the frame payload length (in bytes) used by
#       the ISP2xxx firmware.
#NOTE:  The minimum value is 512 bytes; if this variable is not equal to
#       512, 1024 or 2048, the ISP2xxx defaults to values specified
#       above.
max-frame-length=2048;

#Name:  Execution throttle
#Type:  Integer, commands; Range: 1 - 65535; Default: 32
#Usage: This field specifies the maximum number of commands sent per LUN
#       by the ISP2xxx firmware.
#NOTE:  Exceeding device capabilities causes unneeded command retries
#       that impact performance.
execution-throttle=32;

#Name:  Login timeout
#Type:  Integer, count; Range: 0 - 255; Default: 3
#Usage: This field specifies the maximum number seconds to
#       wait for the login of a device to complete.
#NOTE:  Large values may cause long delays during initialization
#       and device reconfiguration.
login-timeout=3;

#Name:  Login retry count
#Type:  Integer, count; Range: 0 - 255; Default: 4
#Usage: This field specifies the maximum number of retry attempts
#       for the firmware when the login into a device fails.
#NOTE:  Large values may cause long delays during initialization
#       and device reconfiguration.
login-retry-count=4;

#Name:  Enable adapter hard loop ID
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 0
#Usage: This field allows the setting of adapters hard loop ID on the
#       fibre channel bus.
#NOTE:  May be necessary on some bus configurations where devices fail to
#       appear.
enable-adapter-hard-loop-ID=0;

#Name:  Adapter hard loop ID
#Type:  Integer, ID; Range: 0-125; Default: 0
#Usage: This field specifies the adapters hard loop ID to be used on the
#       Fibre Channel bus.
#NOTE:  This field takes effect only when adapter hard loop ID is enabled.
adapter-hard-loop-ID=0;

#Name:  Enable LIP reset on bus reset
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 0
#Usage: This field enables the adapter to issue a LIP reset during Fibre
#       Channel reset.
enable-LIP-reset-on-bus-reset=0;

#Name:  Enable LIP full login on bus reset
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 1
#Usage: This field enables the adapter to issue a LIP full login reset
#       during Fibre Channel reset.
enable-LIP-full-login-on-bus-reset=1;

#Name:  Enable target reset on bus reset
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 0
#Usage: This field enables the adapter to issue a LIP target reset during
#       Fibre Channel reset.
enable-target-reset-on-bus-reset=0;

#Name:  Reset delay
#Type:  Integer, seconds; Range: 1 - 255; Default: 5
#Usage: This field specifies the delay after a reset before sending
#       commands to the devices on the Fibre Channel bus.
reset-delay=5;

#Name:  Port down retry count
#Type:  Integer, count; Range: 0 - 255; Default: 8
#Usage: This field specifies the amount of command retries to be done
#       when devices are not responding on the Fibre Channel bus.
#NOTE:  Large values may cause long delays for failover software to
#       detect a failing device.
port-down-retry-count=8;

#Name:  Port down retry delay
#Type:  Integer, count; Range 0 - 255 seconds. Default: 2
#Usage: Amount of time to delay between port down retries.
#NOTE:  Large values may cause long delays for failover software to
#       detect a failing device. May also cause upper layer driver
#       or applications to timeout the IO's.
port-down-retry-delay=2;

#Name:  Queue full retry count
#Type:  Integer, count. Range: 0 - 255. Default: 16
#Usage: This field specified the number of times to retry a SCSI
#       queue full error.
queue-full-retry-count=16;

#Name:  Queue full retry delay
#Type:  Integer, seconds. Range: 0 - 255 seconds. Default: 2
#Usage: This field specifies the amount of time to delay after a SCSI
#       queue full error before starting any new I/O commands.
queue-full-retry-delay=2;

#Name:  Connection options
#Type:  Integer, mode; Range: 0 - 2; Default: 2
#       0 = loop only
#       1 = point-to-point only
#       2 = loop preferred, else point-to-point
#Usage: This field specifies the connection mode the driver firmware
#       uses. When connecting the HBA to a switch port with auto-
#       mode sensing capability (a G port), it is recommended that this
#       parameter be set to either 0 or 1, not 2. Setting this
#       parameter to 2 when connected to a G port on a switch may
#       result in device lost or system hang.
connection-options=2;

#Name:  Enable FCP 2 Error Recovery
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 1
#Usage: This field enables/disables the Fibre Channel FCP 2 error
#       recovery support.
enable-FCP-2-error-recovery=1;

#Name:  Fibre Channel Data Rate Option
#Type:  Integer, mode; Range: 0-3; Default: 2
#       0 = 1 gigabit/second
#       1 = 2 gigabit/second
#       2 = Auto-negotiate
#       3 = 4 gigabit/second
#Usage: This field specifies the data rate which the driver uses.
fc-data-rate=2;

#Name:  Link down timeout
#Type:  Integer, seconds; Range: 0 - 240; Default: 0
#Usage: This field specifies the amount of time the driver waits for
#       a Fibre Channel loop to come up before reporting the failure.
#NOTE:  Small values may report transient errors that should be ignored.
link-down-timeout=0;

#Name:  Link down error
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 1
#Usage: This field disables the driver error reporting during link down
#       conditions.
enable-link-down-error=1;

#Name:  Enable extended logging
#Type:  Integer, flag; Range: 0 (disable), 1 (enable); Default: 0
#Usage: This field enables logging of driver detected events occurring
#       either in the driver or fibre channel bus. Events are logged
#       in Solaris /var/adm/messages file.
extended-logging=0;

#Name:  Firmware Dump Flags
#Type:  Integer, flag bits; Range: 0 (disable), 1 (enable); Default: 0
#Usage: These flags are used to force a firmware dump when the flag
#       condition occurs. More than one flag bit can be combined to
#       obtain the desired result.
#       TAKE_FW_DUMP_ON_MAILBOX_TIMEOUT         1
#       TAKE_FW_DUMP_ON_ISP_SYSTEM_ERROR        2
#       TAKE_FW_DUMP_ON_DRIVER_COMMAND_TIMEOUT  4
#       TAKE_FW_DUMP_ON_LOOP_OFFLINE_TIMEOUT    8
firmware-dump-flags=0;

#Name:  PCI max read request override
#Type:  Integer, bytes; Range: 128, 256, 512, 1024, 2048, 4096
#Usage: This field specifies the value to be used for the PCI max read
#       request setting, overriding the default value or the value programmed
#       by the system.
#NOTE:  The minimum value is 128 bytes on PCI Express and 512 on PCI; if
#       this variable does not exist or is not equal to 128, 256, 512,
#       1024, 2048 or 4096, the ISP2xxx uses the default or the value
#       specified by the system.
pci-max-read-request=2048;

#Name:  DDI Force Attach
#Type:  Interger, byte; Range: 0, 1
#Usage: This field specifies to the Solaris kernel during boot to always
#       load all instances of the driver regardless of system events or
#       conditions.
ddi-forceattach=1;

sunshnis01# cat /kernel/drv/fp.conf
#
# Copyright (c) 1999, 2001 by Sun Microsystems, Inc.
# All rights reserved.
#
# Sun Fibre Channel Port driver configuration
#
#ident  "@(#)fp.conf    1.2     01/03/30 SMI"
#

name="fp" class="fibre-channel" port=0;
name="fp" class="fibre-channel" port=1;

#
# List of ULP modules for loading during port driver attach time
#
load-ulp-list="1","fcp";
#
# Force attach driver to support hotplug activity (do not remove the property)
#
ddi-forceattach=1;

scsi-binding-set="fcp";
sunshnis01# cat /kernel/drv/fcp.conf
#
# Copyright (c) 1999 by Sun Microsystems, Inc.
# All rights reserved.
#
#ident  "@(#)fcp.conf   1.1     99/07/22 SMI"
#

name="fcp" parent="pseudo" instance=0;
sunshnis01# exit
exit
sunshnis01# exit

论坛徽章:
7
荣誉会员
日期:2011-11-23 16:44:17水瓶座
日期:2013-08-28 21:20:16丑牛
日期:2013-10-02 21:01:462015年迎新春徽章
日期:2015-03-04 09:54:45操作系统版块每日发帖之星
日期:2016-06-05 06:20:0015-16赛季CBA联赛之吉林
日期:2016-06-20 08:24:0515-16赛季CBA联赛之四川
日期:2016-08-18 15:02:02
9 [报告]
发表于 2008-12-29 11:26 |只看该作者
Step 1, Please verify all LUNs can ben scanned under OK prompt

Step 2, You need to check if your HBA can cowork with your server's PCI slot

Step 3, You should make sure all SAN packages and patches have been applied in your solaris

Step 4, After all steps above, You must ensure "luxadm -e port" can see your HBA ! Or else you can not connect your disk storage system.

论坛徽章:
0
10 [报告]
发表于 2008-12-29 12:06 |只看该作者

回复 #9 nimysun 的帖子

Thanks for your reply.

1, I don't bind the LUN to this HBA card. I just hope that the SAN switch can identify this HBA card.
Now I can't find the ray from the cable port when the cable is connected to HBA port.

2, Yes, I have verified that. It's OK.

3, Yes, I'm sure that. It's OK.

4, the "luxadm -e port" can't find this HBA card, I just want to know what causes that?

Is there have a software or switch or config file can disable the HBA card?
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP