简单游戏 快乐生活
您当前的位置：
>> >> >>华为设备无法添加vlan
华为设备无法添加vlan
作者：电玩巴士
来源：互联网
发布时间： 16:39:59
在华为2403里添加vlan1213，提示了下面一个错误：FailedtocreatthisVlanbecauseofcollisionwithvlan701!求高手帮忙解释下，这是什么原因？
小编推荐答案：可能是端口问题，你这是两个VLAN冲突了。
======================================提问人的追问&& 10:151213 和 701怎么冲突的======================================回答人的补充&& 10:18你这个VLAN的端口和那个重复了======================================提问人的追问&& 14:20从头查到为，没发现重复的端口
你有遇到过玩游戏时切换出来查看攻略，不幸导致游戏崩溃的情况吗？下载，边玩游戏边用手机看攻略，轻松愉快，大家都在用。
关注安卓中文网官方微信
扫描左侧二维码即可添加安卓中文网官方微信
您也可以在微信上搜索“安卓中文网”或“anzhuozww”，获取更多数码资讯
24小时热点怎么在交换机上新增加一个Vlan?_百度知道添加，如何请使用SNMP修改，并且去除VLAN在Catalyst
[an error occurred while processing this directive]
新闻与刊物
商业解决方案
网络解决方案
服务与支持
思科网络技术学院
培训、活动与会议
合作伙伴与代理商
中国：简体中文
TAC中文文档
原文件的链接(英语)
此文档是由人工智能自动翻译系统翻译的,请随时参考。
添加，如何请使用SNMP修改，并且去除VLAN在Catalyst
     
     
     
     
     
     
     
使用简单网络管理协议(SNMP)的本文如何在Cisco Catalyst交换机描述创建和删除VLAN。 它如何也描述添加端口到VLAN与SNMP。
在您使用本文的信息之前，请保证您了解：
ifTable和IfIndex如何工作
VLAN如何在Cisco Catalyst交换机工作
如何查看VLAN信息关于Cisco Catalyst交换机
SNMP一般用途获得，设置，并且走命令
本文是为运行正常Catalyst OS或Catalyst IOS支持IF-MIB、CISCO-VTP-MIB和CISCO-VLAN-MEMBERSHIP-MIB的Catalyst交换机。 本文件中的信息以下列软件和硬件版本为依据。
运行Cat IOS 12.0(5)WC5a的Catalyst 3524XL
NET-SNMP版本5.0.6可用在
本文所包含信息基于特定实验室环境下的设备。 本文所引用的所有设备均采用原始 (缺省)配置。 如果在真实网络工作，在您请之前使用所有命令了解任何命令潜在影响。
有关文件规则的更详尽信息请参阅Cisco技术提示规则。
1.3.6.1.4.1.9.9.46.1.3.1.1.2 (CISCO-VTP-MIB)
vtpVlanState
OBJECT-TYPE
INTEGER { operational(1),
suspended(2),
mtuTooBigForDevice(3),
mtuTooBigForTrunk(4) }
MAX-ACCESS read-only
DESCRIPTION
"The state of this VLAN.
The state 'mtuTooBigForDevice' indicates that this device
cannot participate in this VLAN because the VLAN's MTU is
larger than the device can support.
The state 'mtuTooBigForTrunk' indicates that while this
VLAN's MTU is supported by this device, it is too large for
one or more of the device's trunk ports."
::= { vtpVlanEntry 2 }
1.3.6.1.4.1.9.9.46.1.4.1.1.1 (CISCO-VTP-MIB)
vtpVlanEditOperation OBJECT-TYPE
INTEGER { none(1),
release(4),
restartTimer(5)
MAX-ACCESS read-create
DESCRIPTION
"This object always has the value 'none' when read.
written, each value causes the appropriate action:
'copy' - causes the creation of rows in the
vtpVlanEditTable exactly corresponding to the current global
VLAN information for this management domain.
If the Edit
Buffer (for this management domain) is not currently empty,
a copy operation fails.
A successful copy operation starts
the deadman-timer.
'apply' - first performs a consistent check on the the
modified information contained in the Edit Buffer, and if
consistent, then tries to instanciate the modified
information as the new global VLAN information.
an empty Edit Buffer (for the management domain) would
always result in an inconsistency since the default VLANs
are required to be present.
'release' - flushes the Edit Buffer (for this management
domain), clears the Owner information, and aborts the
deadman-timer.
A release is generated automatically if the
deadman-timer ever expires.
'restartTimer' - restarts the deadman-timer.
'none' - no operation is performed."
::= { vtpEditControlEntry 1 }
1.3.6.1.4.1.9.9.46.1.4.1.1.3 (CISCO-VTP-MIB)
vtpVlanEditBufferOwner OBJECT-TYPE
OwnerString
MAX-ACCESS read-create
DESCRIPTION
"The management station which is currently using the Edit
Buffer for this management domain.
When the Edit Buffer for
a management domain is not currently in use, the value of
this object is the zero-length string.
Note that it is also
the zero-length string if a manager fails to set this object
when invoking a copy operation."
::= { vtpEditControlEntry 3 }
1.3.6.1.4.1.9.9.46.1.4.2.1.11 (CISCO-VTP-MIB)
vtpVlanEditRowStatus OBJECT-TYPE
2:notInService
3:notReady
4:createAndGo
5:createAndWait
MAX-ACCESS read-create
DESCRIPTION
"The status of this row.
Any and all columnar objects in an
existing row can be modified irrespective of the status of
A row is not qualified for activation until instances of at
least its vtpVlanEditType, vtpVlanEditName and
vtpVlanEditDot10Said columns have appropriate values.
The management station should endeavor to make all rows
consistent in the table before 'apply'ing the buffer.
inconsistent entry in the table will cause the entire
buffer to be rejected with the vtpVlanApplyStatus object
set to the appropriate error value."
::= { vtpVlanEditEntry 11 }
1.3.6.1.4.1.9.9.46.1.4.2.1.3.1.48 (CISCO-VTP-MIB)
vtpVlanEditType OBJECT-TYPE
MAX-ACCESS read-create
DESCRIPTION
"The type which this VLAN would have.
An implementation may restrict access to this object."
{ ethernet }
::= { vtpVlanEditEntry 3 }
1.3.6.1.4.1.9.9.46.1.4.2.1.4.1.48 (CISCO-VTP-MIB)
vtpVlanEditName OBJECT-TYPE
DisplayString (SIZE (1..32))
MAX-ACCESS read-create
DESCRIPTION
"The name which this VLAN would have.
This name would be
used as the ELAN-name for an ATM LAN-Emulation segment of
this VLAN.
An implementation may restrict access to this object."
::= { vtpVlanEditEntry 4 }
1.3.6.1.4.1.9.9.46.1.4.2.1.6.1.48 (CISCO-VTP-MIB)
vtpVlanEditDot10Said OBJECT-TYPE
OCTET STRING (SIZE (4))
MAX-ACCESS read-create
DESCRIPTION
"The value of the 802.10 SAID field which would be used for
this VLAN.
An implementation may restrict access to this object."
::= { vtpVlanEditEntry 6 }
1.3.6.1.4.1.9.9.46.1.4.1.1.2.1 (CISCO-VTP-MIB)
vtpVlanApplyStatus OBJECT-TYPE
INTEGER { inProgress(1),
succeeded(2),
configNumberError(3),
inconsistentEdit(4),
tooBig(5),
localNVStoreFail(6),
remoteNVStoreFail(7),
editBufferEmpty(8),
someOtherError(9)
MAX-ACCESS read-only
DESCRIPTION
"The current status of an 'apply' operation to instanciate
the Edit Buffer as the new global VLAN information (for this
management domain).
If no apply is currently active, the
status represented is that of the most recently completed
The possible values are:
inProgress - 'apply' o
succeeded - the 'apply' was successful (this value is
also used when no apply has been invoked since the
last time the local system restarted);
configNumberError - the apply failed because the value of
vtpVlanEditConfigRevNumber was less or equal to
the value of current value of
managementDomainConfigRevN
inconsistentEdit - the apply failed because the modified
information was not self-
tooBig - the apply failed because the modified
information was too large to fit in this VTP
Server's non-volat
localNVStoreFail - the apply failed in trying to store
the new information in a local non-volatile
remoteNVStoreFail - the apply failed in trying to store
the new information in a remote non-volatile
editBufferEmpty - the apply failed because the Edit
Buffer was empty (for this management domain).
someOtherError - the apply failed for some other reason
(e.g., insufficient memory)."
::= { vtpEditControlEntry 2 }
1.3.6.1.4.1.9.9.68.1.2.2.1.2 (CISCO-VLAN-MEMBERSHIP-MIB)
OBJECT-TYPE
INTEGER(0..4095)
MAX-ACCESS read-write
DESCRIPTION
"The VLAN id of the VLAN the port is assigned to
when vmVlanType is set to static or dynamic.
This object is not instantiated if not applicable.
The value may be 0 if the port is not assigned
to a VLAN.
If vmVlanType is static, the port is always
assigned to a VLAN and the object may not be
If vmVlanType is dynamic the object's value is
0 if the port is currently not assigned to a VLAN.
In addition, the object may be set to 0 only."
::= { vmMembershipEntry 2 }
在如下所示的示例中， VLAN 11被添加到交换机：
为了检查哪些VLAN在交换机目前被配置，请发出一snmpwalk在vtpVlanState OID ：
注意： ？最后一个号码在OID是VLAN号。
snmpwalk -c public crumpy vtpVlanState
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.48 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1002 : INTEGER: operational
验证版本是否由另一个NMS工作站或设备是在使用中。 如果看到此消息，版本不是在使用中： 没有MIB对象包含在子树之下：
snmpwalk -c public crumpy vtpVlanEditTable
no MIB objects contained under subtree.
版本不是在使用中，因此开始编辑是安全的。 设置vtpVlanEditOperation为复制状态(整数2)。 这允许您创建VLAN。
snmpset -c private crumpy vtpVlanEditOperation.1 integer 2
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpEditControlTable.vtpEditControlEntry.vtpVlanEditOperation.1 : INTEGER: copy
为了使当前责任人编辑权限可视，您能设置责任人，当您发出命令时， vtpVlanEditBufferOwner。
snmpset -c private crumpy vtpVlanEditBufferOwner.1 octetstring "Gerald"
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpEditControlTable.vtpEditControlEntry.vtpVlanEditBufferOwner.1 : OCTET STRING- (ascii):
此示例如何显示验证表存在：
snmpwalk -c public crumpy vtpVlanEditTable
vtpVlanEditState.1.1 : INTEGER: operational
vtpVlanEditState.1.2 : INTEGER: operational
vtpVlanEditState.1.3 : INTEGER: operational
此示例如何是VLAN 11并且显示您创建行和设置类型和名字：
snmpset -c private crumpy vtpVlanEditRowStatus.1.11 integer 4
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpVlanEditTable.vtpVlanEditEntry.vtpVlanEditRowStatus.1.11 : INTEGER: createAndGo
snmpset -c private crumpy vtpVlanEditType.1.11 integer 1
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpVlanEditTable.vtpVlanEditEntry.vtpVlanEditType.1.11 : INTEGER: ethernet
snmpset -c private crumpy vtpVlanEditName.1.11 octetstring "test_11_gerald"
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpVlanEditTable.vtpVlanEditEntry.vtpVlanEditName.1.11 : DISPLAY STRING- (ascii):
test_11_gerald
设置vtpVlanEditDot10Said。 这是VLAN号+ 100000被转换为十六进制。 此示例创建VLAN 11，因此vtpVlanEditDot10Said应该是： 11 + 100000 = 100011 - >十六进制： 000186AB
snmpset -c private crumpy vtpVlanEditDot10Said.1.11 octetstringhex 000186AB
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpVlanEditTable.vtpVlanEdi
ntry.vtpVlanEditDot10Said.1.11 : OCTET STRING-
(hex): length = 4
00 01 86 ab -- -- -- -- -- -- -- -- -- -- -- --
................
当您创建了VLAN 11时，您必须适用修改。 再请使用vtpVlanEditOperation OID。 这次使用适用确认设置：
snmpset -c private crumpy vtpVlanEditOperation.1 integer 3
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpEditControlTable.vtpEditControlEntry.vtpVlanEditOperation.1 : INTEGER: apply
验证VLAN顺利地被创建了。 请使用OID vtpVlanApplyStatus。 请检查进程，直到状态读： 成功：
snmpget –c public crumpy vtpVlanApplyStatus.1
vtpVlanApplyStatus.1 : INTEGER: inProgress
snmpget –c public crumpy vtpVlanApplyStatus.1
vtpVlanApplyStatus.1 : INTEGER: inProgress
snmpget –c public crumpy vtpVlanApplyStatus.1
vtpVlanApplyStatus.1 : INTEGER: succeeded
最后动作是做修改和发布权限，以便其他用户能从他们的NMS添加，修改或者删除VLAN。
-c private crumpy vtpVlanEditOperation.1 integer 4
vtpVlanEditOperation.1 : INTEGER: release
验证缓冲区是空的：
snmpwalk –c public crumpy vtpVlanEditTable
no MIB objects contained under subtree.
验证VLAN 11在交换机被创建了用Cli命令show VLAN或用snmpwalk ：
snmpwalk -c public crumpy vtpVlanState
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.11 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.48 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1002 : INTEGER: operational
一个步骤指令
这一个步骤进程使用OID编号而不是OID名字类似早先逐步进程。 请参阅关于转换。 此示例创建VLAN 6 ：
snmpset -c private crumpy 1.3.6.1.4.1.9.9.46.1.4.1.1.1.1 integer 2 1.3.6.1.4.1.9.9.46.1.4.1.1.3.1 octetstring "gcober"
snmpset -c private gooroo 1.3.6.1.4.1.9.9.46.1.4.2.1.11.1.6 integer 4 1.3.6.1.4.1.9.9.46.1.4.2.1.3.1.6 integer 1 1.3.6.1.4.1.9.9.46.1.4.2.1.4.1.6 octetstring "vlan6" 1.3.6.1.4.1.9.9.46.1.4.2.1.6.1.6 octetstringhex
1.3.6.1.4.1.9.9.46.1.4.1.1.1.1 integer 3
snmpset -c private gooroo 1.3.6.1.4.1.9.9.46.1.4.1.1.1.1 integer 4
snmpwalk -c public crumpy 1.3.6.1.4.1.9.9.46.1.3.1.1.2
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.6 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.11 : INTEGER: operational
注意： ？某些SNMP版本要求您使用a (。) 在OID之前在SNMP Set命令。
在本例中VLAN 48从交换机被删除。 请参见欲知更多信息。 此部分之间的区别，其中您删除VLAN和那个您添加VLAN的地方是您使用毁坏而不是CreateAndGo命令vtpVlanEditRowStatus ：
发出命令删除VLAN 48 ：
snmpset -c private crumpy vtpVlanEditOperation.1 integer 2
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpEditControlTable.vtpEditControlEntry.vtpVlanEditOperation.1 : INTEGER: copy
snmpset -c private crumpy vtpVlanEditRowStatus.1.48 integer 6
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanEdit.vtpVlanEditTable.vtpVlanEditEntry.vtpVlanEditRowStatus.1.48 : INTEGER: destroy
要验证VLAN 48被删除了，请使用vtpVlanState或show VLAN在CLI ：
snmpwalk -c public crumpy vtpVlanState
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1 : INTEGER: operational
cisco.ciscoMgmt.ciscoVtpMIB.vtpMIBObjects.vlanInfo.vtpVlanTable.vtpVlanEntry.vtpVlanState.1.1002 : INTEGER: operational
此示例如何显示添加端口快速以太网0/5到VLAN 48。
要验证哪IfIndex快速的Eth 0/5有，请发出ifDescr snmpwalk ：
snmpwalk -c public crumpy ifDescr
interfaces.ifTable.ifEntry.ifDescr.6 : DISPLAY STRING- (ascii):
FastEthernet0/5
因为您知道端口快速的Eth 0/5有IfIndex 6，请添加端口到VLAN 48 ：
snmpset -c private crumpy vmVlan.6 integer 48
cisco.ciscoMgmt.ciscoVlanMembershipMIB.ciscoVlanMembershipMIBObjects.vmMembership.vmMembershipTable.vmMembershipEntry.vmVlan.6 : INTEGER: 48
验证端口通过再查询同样OID正确地添加。
snmpget -c public crumpy vmVlan.6
cisco.ciscoMgmt.ciscoVlanMembershipMIB.ciscoVlanMembershipMIBObjects.vmMembership.vmMembershipTable.vmMembershipEntry.vmVlan.6 : INTEGER: 48
您在交换机能也验证此：
crumpy#sh vlan
---- -------------------------------- --------- -------------------------------
Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/6, Fa0/7, Fa0/8, Fa0/9,
Fa0/10, Fa0/11, Fa0/12, Fa0/13,
Fa0/14, Fa0/15, Fa0/16, Fa0/17,
Fa0/18, Fa0/19, Fa0/20, Fa0/21,
Fa0/22, Fa0/23, Fa0/24, Gi0/1,
此示例展示端口快速的Eth 0/3如何如何属于VLAN 48和移动它向VLAN 1 (默认VLAN) ：
要验证哪IfIndex快速的Eth 0/3有，请发出ifDescr snmpwalk ：
snmpwalk -c public crumpy ifDescr
interfaces.ifTable.ifEntry.ifDescr.4 : DISPLAY STRING- (ascii):
FastEthernet0/3
因为您知道端口快速的Eth 0/3有IfIndex 4，您能验证对哪个VLAN端口目前属于：
snmpget -c public crumpy vmVlan.4
cisco.ciscoMgmt.ciscoVlanMembershipMIB.ciscoVlanMembershipMIBObjects.vmMembership.vmMembershipTable.vmMembershipEntry.vmVlan.4 : INTEGER: 48
端口属于VLAN 48。
snmpset -c private crumpy vmVlan.4 integer 1
cisco.ciscoMgmt.ciscoVlanMembershipMIB.ciscoVlanMembershipMIBObjects.vmMembership.vmMembershipTable.vmMembershipEntry.vmVlan.4 : INTEGER: 1
从VLAN 48要移动端口向VLAN 1，请发出snmpset vmVlan。
要验证端口是否更改了到另一个VLAN，再请查询vmVlan ：
snmpget -c public crumpy vmVlan.4
cisco.ciscoMgmt.ciscoVlanMembershipMIB.ciscoVlanMembershipMIBObjects.vmMembership.vmMembershipTable.vmMembershipEntry.vmVlan.4 : INTEGER: 1
您在交换机能也验证此：
在更改之前：
crumpy#sh vlan
---- -------------------------------- --------- -------------------------------
Fa0/1, Fa0/2, Fa0/4, Fa0/5,
Fa0/6, Fa0/7, Fa0/8, Fa0/9,
Fa0/10, Fa0/11, Fa0/12, Fa0/13,
Fa0/14, Fa0/15, Fa0/16, Fa0/17,
Fa0/18, Fa0/19, Fa0/20, Fa0/21,
Fa0/22, Fa0/23, Fa0/24, Gi0/1,
在更改以后：
crumpy#sh vlan
---- -------------------------------- --------- -------------------------------
Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8,
Fa0/9, Fa0/10, Fa0/11, Fa0/12,
Fa0/13, Fa0/14, Fa0/15, Fa0/16,
Fa0/17, Fa0/18, Fa0/19, Fa0/20,
Fa0/21, Fa0/22, Fa0/23, Fa0/24,
Gi0/1, Gi0/2
注意： ？您能做其他更改，例如VLAN名字，责任人和更多。 请参见整个MIB关于更详细的细节在OID。
声明：此文档是由为思科 TAC 网页内容翻译所开发的英汉机器自动翻译系统翻译的。在有疑问或作出重要的技术支持决策时,请随时参考英文原文。Updated:
Oct 01, 2003Document ID: 45080
[an error occurred while processing this directive]
[an error occurred while processing this directive]查看: 1147|回复: 5
【求助】tomato固件，如何设置多个VLAN
电信送的 Feixun 302B 路由器（1wan口 + 4lan口），
已刷 MultiWAN 的固件。
请教一下论坛内有经验的指导一下，如何设置才能满足下列需求：
1、 WAN&&接外线
2、 LAN1&&为内网管理专用
3、 LAN2、3、4， 分别设为三个独立VLAN +自动分配IP，且可以直接访问WAN口上网
最近有需求，要路由器是设置： 三个独立VLAN 互不干扰（自动分配IP，且共享WAN口上网） +1WAN +1LAN用来管理路由器
按下图设置，只能实现1个VLAN， 再加VLAN会提示 必须和WAN口绑定。。
QQ截图48.png (17.11 KB, 下载次数: 0)
23:25 上传
QQ截图14.png (23.75 KB, 下载次数: 0)
23:25 上传
我也想知道这个怎么设置研究一晚上了
111.png (108.79 KB, 下载次数: 0)
22:39 上传
从国外教程看这步设置好久应该可以了但是我的还是分配到192.168.1.X段的地址&&重新获取dhcp也不行
按我的图片设置
LAN1 LAN2是可以DHCP分配 BR1的IP
192.168.11.***
但是要上网只能用网线接LAN3（lan1、lan2随意一个口 要不没法上网）&
从国外教程看这步设置好久应该可以了但是我的还是分配到192.168.1.X段的地址&&重新获取dhcp也不行
按我的图片设置& &LAN1 LAN2是可以DHCP分配 BR1的IP&&192.168.11.***
但是要上网只能用网线接LAN3（lan1、lan2随意一个口 要不没法上网）
我感觉是不是这个需要用telnet设置呀 图形的还不能设置？
实际上你这样设置后，除了第一个你认为的vlan可以登录路由器，其它几个你不认为能登录路由器的vlan也能登录路由器，所以如果只是单纯为了只让自己管理的目的，是没必要这样的，（我隐约记得好像这样做的时候，隔壁vlan也能ping通，我已经忘记了，也许不能ping通）
Powered by}