| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw51800 | Title: | unable to delete param-list from config file |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When using auto-config, the param-list of a profile are not removed when a profile is un-applied.
Conditions:
This happens after "copy r s" and reload reload with param-list / applied configs present in startup config.
Workaround:
Use no param-list xyz cross-check command to force remove the param-list if it is not actually being used.
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0.150) |
|
Known Fixed Releases: * | 7.0(3)I3(0.276), 7.0(3)I3(1), 7.0(3)IAB3(0), 7.0(3)IAB3(0.100), 7.1(3)ZN(0.131), 7.1(4)N1(0.696), 7.1(4)N1(1), 7.2(2)N1(0.379), 7.2(2)N1(1), 7.2(2)ZN(0.62) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy08128 | Title: | Cut through Threshold change on Tiburon FEX's on 40gb NIF's |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Under rare conditions a Nexus 2300 series fabric extender might corrupt packets. This is due to an incorrect buffer setting in software on the FEX. Once this issue is hit the FEX will need to be reloaded to recover.
Conditions:
Workaround:
Reload the FEX.
Further Problem Description:
|
|
Last Modified: | 26-FEB-2016 |
|
Known Affected Releases: | 7.1(3)N1(1) |
|
Known Fixed Releases: * | 7.0(7)ZN(0.284), 7.0(7)ZN(0.285), 7.1(3)N1(2.7), 7.1(3)N1(3), 7.1(3)ZD(0.95), 7.1(3)ZN(0.200), 7.1(3)ZN(0.201), 7.1(4)N1(0.743), 7.1(4)N1(0.744), 7.1(4)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy14813 | Title: | After changing fcoe pinning in AA FEX, HIF ports need flap |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Logins are flushed out automatically and port goes into to Error disabled state
Conditions:
fcoe pinning is removed
fex
no fcoe
Workaround:
flap host interfaces (sh/no sh) to achieve correct state of ports and for login clean state.
Further Problem Description:
|
|
Last Modified: | 20-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0.283) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66815 | Title: | Nexus 5k/6k may reload with "fex hap reset" when FEX is not supported. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Device reloads with "fex hap reset" after "show fex" or "show fex # transceiver".
Conditions:
FEX is not supported in used NX-OS version.
Workaround:
Upgrade to NX-OS which supports this FEX.
Further Problem Description:
N/A
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 7.0(7)N1(1) |
|
Known Fixed Releases: * | 7.0(3)I3(0.272), 7.0(3)I3(1), 7.0(3)IAB3(0), 7.0(3)IAB3(0.100), 7.3(0)IZN(0.7), 7.3(0)N1(0.169), 7.3(0)N1(1), 7.3(0)ZN(0.157) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw93085 | Title: | After shutting down an i/f , it takes long time to get to shut state |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:The reason is the port-channel is in adminCfgChange state for that much time.
Conditions:In vPC setup scale setup, It is seen that on shutdown of port-channel interface, there is a traffic drop for around 8-10 seconds. After it is completely down , the routes are removed from the adjacent routers... after which the traffic converges.
Workaround:None
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: * | 7.3(0)N1(0.177), 7.3(0)N1(0.208) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux32809 | Title: | kk218:ISSU to upg fails in 5672 due totimeoutof hitless linecard upgrade |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
The issue is ISSU fails during the fex upgrade . ISSU fails showing the errror description and the error id and also where the issue is seen (here issue is with fex upgrade).
Conditions:
This issue is seen during ISSU in N6k having its host and target in fex and connected to brocade switch (peer switch is brocade) and the topology is FCOE.
Workaround:
Trying issu for multiple times is a workaround to perform a successful issu.
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0.218) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui84039 | Title: | ascii-cfg core and n6k reload observed no feature-set fabricpath |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ascii-cfg process crash when doing "no feature-set fabricpath"
Nexus# sh core
Module Instance Process-name PID Date(Year-Month-Day Time)
------ -------- --------------- -------- -------------------------
1 1 ascii-cfg 3675 2011-03-27 00:00:46
Nexus(config)# no feature-set fabricpath
Feature-set Operation may take up to 30 minutes depending on the size of configuration.
[362482.443853] Shutdown Ports..
[362482.479243] writing reset reason 16, ascii-cfg hap reset
Broadcast message from root (console) (Fri MSending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting filesystems...
Conditions:
Issue command:
Nexus(config)# no feature-set fabricpath
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 11-FEB-2016 |
|
Known Affected Releases: | 6.0(2)N2(2), 6.0(2)N3(0.195) |
|
Known Fixed Releases: * | 5.2(1)N1(10), 5.2(1)N1(9.179), 7.0(0)N1(0.501), 7.0(0)N1(1), 7.0(0)ZN(0.208) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu62888 | Title: | N5K/N6K ISIS Neighbor with network type p2p adjacency not coming up |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On a nexus 5000/6000 series switch, ISIS Neighbor with network type p2p is not coming up with routers running IOS-XR
Conditions:
None
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.163), 7.1(4)N1(0.717), 7.1(4)N1(1), 7.3(0)BZN(0.47), 7.3(0)N1(1), 7.3(0)ZN(0.103) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux49563 | Title: | msg format correction in fwm |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
msg format correction in fwm component.
Conditions:
Some syslog msgs format strings were not properly converted
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0.218) |
|
Known Fixed Releases: * | 7.3(0)N1(0.236), 7.3(0)N1(1), 7.3(0)ZN(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun90417 | Title: | platform/storage/common/scripts/initsys/init-system-satnuova add to z7_0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Sunnyside fex initsys script only get affected
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 13-FEB-2016 |
|
Known Affected Releases: | 7.1(0)ZN(0.99) |
|
Known Fixed Releases: * | 7.0(0)BZ(0.46), 7.0(0)HSK(0.317), 7.0(0)KM(0.97), 7.0(1)ZD(0.158), 7.0(1)ZN(0.234), 7.0(3)N1(0.8), 7.0(3)N1(1), 7.1(0)D1(0.171), 7.1(0)FC(0.2), 7.1(0)NF(0.28) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw74228 | Title: | peer-link inconsistency and peer keep alive fail when instantiating net |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
When instantiating/autoconfiguring networks on a EVPN programmable fabric setup , one sees the following messages on VPC leaf.
This message can also be seen when the networks are removed
%$ VDC-1 %$ %STP-2-VPC_PEER_LINK_INCONSIST_BLOCK: vPC peer-link de
ed Bridge Assurance Inconsistency blocking Po10 VLAN: 875.
2001 Dec 5 12:48:04 IP-FAB1-VPC1 %$ VDC-1 %$ %STP-2-VPC_PEER_LINK_INCONSIST_BLOCK: vPC peer-link deed BPDU receive timeout blocking Po10 VLAN: 46,881.
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0.158) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv35326 | Title: | N6k :: ICMPv6 related to neighbor discovery punted to the CPU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In Nexus5K/6K ICMPv6 packets related to neighbor discovery are punted to the CPU even if there is no SVI configured in vlan where packets are present.
Conditions:
Nx-OS version 7.0(0)N1(1) and newer - still to be confirmed
Workaround:
If this is causing drops in copp-system-class-arp, ARP policer can be increased.
Further Problem Description:
|
|
Last Modified: | 10-FEB-2016 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.659), 7.1(3)N1(1), 7.1(3)ZN(0.67), 7.2(2)N1(0.389), 7.2(2)N1(1), 7.2(2)ZN(0.71) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv99658 | Title: | VPC peer link is not coming up after peer-link flap |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
VPC peer-link down.VPC peer link is not coming up after peer-link flap (reason:vPC peer is not reachable over cfs).
Conditions:
Its a timing issue and happens very very rarely. Mostly after first peer-link flap post reload.
Workaround:
Shut and no shut on the peer-link ie flapping the vpc peer-link will solve the issue.
Further Problem Description:
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0.104) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus37334 | Title: | N56k: global FCF mac as src fcns fames for vfc's with bind mac-address |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
- N56k sends a name server PLOGI_ACC using vsan global FCF mac instead of interface MAC. ethanalyzer can be used to capture the mac address used.
- host's affected will not have access to their storage.
- host's affected will not have fcns "fc4-types", "symbolic-port-name" and "symbolic-node-name" registered with the name server.
------------------------
VSAN:10 FCID:0xd30060
------------------------
port-wwn (vendor) :50:01:99:93:ed:2a:10:0c
[A-D-bc1atrabl09-hba1]
node-wwn :50:01:99:93:ed:2a:10:0d
class :3
node-ip-addr :0.0.0.0
ipa :00 00 00 00 1e 00 01 30
fc4-types:fc4_features : ---->
symbolic-port-name : ---->
symbolic-node-name : ---->
port-type :N
port-ip-addr :0.0.0.0
fabric-port-wwn :21:30:8c:60:4f:25:81:7f
hard-addr :0x000000
permanent-port-wwn (vendor) :50:01:99:93:ed:2a:10:0c
connected interface :vfc305
switch name (IP address) :RF_NEXUS1_SR1 (10.200.99.211)
- the following errors are shown under
"`show platform software fcoe_mgr event-history errors`"
356) Event:E_DEBUG, length:80, at 971774 usecs after Thu Dec 18 18:49:06 2014
[102] fcoe_mgr_fill_get_fcoe_info(2822): vfc301 eth_ifindex is invalid, skipping
Conditions:
all of the following must apply for the issue to be a hit on this bug.
- Nexus 5600 or 6000 only "N55k is not affected".
- software code 7.x.
- vfc's are configured to using "bind mac-address":
interface vfc301
bind mac-address 0019.993E.D302
switchport trunk allowed vsan 10
switchport description FCoE-to-Blade
no shutdown
Workaround:
configure the following:
- remove the vfc interfaces with bind mac-address.
- use one vfc interface that is bind to the physical interface.
- enable NPIV on the switch.
feature npiv
interface vfc 1
bind interface port-channel 1
switchport trunk allowed vsan 10
switchport description FCoE-to-Blade
no shutdown
with this setup, instead of using multiple vfc interfaces each one that is bound to a MAC. we will use on interface, and all the host's will login through that one vfc which is allowed through NPIV.
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 7.0(5)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv91507 | Title: | Migrating Fex from N7K to N6K/N5K may result in the FEX failing to boot |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A FEX which is attached to an N7K running 6.2(12) or 7.2(0)D1(1) may fail to boot when moved to a Nexus 6K or Nexus 5K:
08/21/2015 00:51:59.593386: Module register received
08/21/2015 00:51:59.594388: Image Version Mismatch
08/21/2015 00:51:59.595438: Registration response sent
08/21/2015 00:51:59.595794: Requesting satellite to download image
08/21/2015 00:53:52.981356: Image preload failed.
08/21/2015 00:54:00.132452: Deleting route to FEX
08/21/2015 00:54:00.141675: Module disconnected
08/21/2015 00:54:00.143718: Module Offline
08/21/2015 00:54:00.152157: Deleting route to FEX
08/21/2015 00:54:00.159062: Module disconnected
08/21/2015 00:54:00.161167: Offlining Module
Conditions:
Issue has been observed on 2248TP-E FEX conencted to F3 line card on N7K.
Workaround:
On 5K/6K running 7.2, the issue can be corrected by unplugging and plugging the cable back in at the FEX uplink.
Further Problem Description:
Migrating Fex from N7K to N6K/N5K may result in the FEX failing to boot
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.2(12), 7.2(0)D1(1) |
|
Known Fixed Releases: * | 7.3(0)IZN(0.13), 7.3(0)N1(0.208), 7.3(0)N1(1), 7.3(0)ZN(0.188), 8.3(0)CV(0.337) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy45682 | Title: | Comunity starting with '/!#' is not shown on running config |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
SNMP was not supporting few characters in the older releases
Conditions:
Using a community string that starts with '/!#' , community is not being shown on the running config, however it can be polled.
Workaround:
Use #show snmp community command
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: * | 7.0(2)N1(1), 7.2(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux85363 | Title: | N5600/6K : IGMP GSQ are not sent out in response to IGMP leaves |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Upon receiving IGMP leaves for certain groups, IGMP group specific queries are generated by the CPU but the group specific queries are never sent out on the switch towards the host.
Conditions:
- Nexus 5600/6000
- this is only seen when multiple IGMP snooping entries are present for those groups on that vlan
- Issue is not seen if only one snooping entry is present
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 8.3(0)CV(0.272) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.201), 7.1(4)N1(0.744), 7.1(4)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq96902 | Title: | N6K QSFP-40G-CSR4 shows up as "transceiver is not supported" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
QSFP-40G-CSR4 transceivers do not come up after no shut, and show "transceiver is not supported" in show int eX/Y transceiver details
Conditions:
Workaround:
service unsupported-transceiver - will bring the transceiver up into a working state, but it will still show as an unsupported transceiver.
Reload the LEM with the following commands:
power off module
no power off module
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 6.0(2)N2(2) |
|
Known Fixed Releases: * | 7.0(7)N1(0.66), 7.0(7)N1(1), 7.0(7)ZN(0.142), 7.1(1)N1(1) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy00762 | Title: | SNMP dot3StatsDuplexStatus doesnt populate for mgmt0 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
SNMP OID dot3StatsDuplexStatus is not populating to show the duplex value of the interface mgmt0 on Nexus6000/Nexus5000.
Conditions:
When queried for OID dot3StatsDuplexStatus through SNMP for interface mgmt0.
Workaround:
Query duplex value for the interface mgmt0 through CLI 'show interface mgmt0'.
Further Problem Description:
NA
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 7.1(2)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup74458 | Title: | few seconds of packet loss on vpc secondary link bringup |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Few seconds of packet loss seen on VPC link bringup. Drops would correspond with PIF drop counter on fex uplink port
N6K-2(config-if)# show platform fwm info pif ethernet 1/7/1 | grep drop
Eth1/7/1 pd: tx stats: bytes 204948156412 frames 2328371667 discard 0 drop 0
Eth1/7/1 pd: rx stats: bytes 177822996614 frames 2388580485 discard 0 drop 1173850 <---HERE
Conditions:
VPC is being restored on a Nexus 5K/6K and traffic re-hashes to the newly brought up VPC. The delay is due to VLAN programming on the VPC trunk.
Workaround:
Reduce the number of VLANs on the VPC trunk by manually clearing not needed VLANs.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 6.0(2)N2(3), 7.0(2)N1(1) |
|
Known Fixed Releases: * | 6.0(2)N2(5.95), 6.0(2)N2(6), 7.0(1)ZN(0.710), 7.0(6)N1(0.214), 7.0(6)N1(1), 7.1(0)EVN(0.18), 7.1(0)N1(0.356), 7.1(0)N1(1), 7.1(0)ZN(0.432), 7.1(1)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux35886 | Title: | N5K/6K: No core saved for ipqosmgr process crash |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
In a Nexus 5K/6K, if ipqosmgr process restarts, no core file gets written
Conditions:
IPQOSMGR process undergoes a unexpected restart
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 7.1(3)N1(1) |
|
Known Fixed Releases: * | 7.3(1)N1(0.29), 7.3(1)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul00657 | Title: | HW entry not programmed for remote host prefix due to some steps |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
The problem occurs when we change the VNI. You will see following syslogs when you hit this issue.
FWM-2-VLAN_VNI_MAPPING_INCORRECT: VLAN to VNI mapping is incorrect
Conditions:
The problem occurs when we change the VNI.
Workaround:
First Try shut/no-shut of VRF, if that doesn't works then Reload is the only option.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.0(2)N3(0.288), 7.1(0)N1(0.370), 7.2(0)N1(0.147), 7.2(1)N1(0.313) |
|
Known Fixed Releases: * | 7.3(0)IZN(0.7), 7.3(0)N1(0.189), 7.3(0)N1(1), 7.3(0)ZN(0.172), 8.3(0)CV(0.337) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu66977 | Title: | show tech enhancement |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
relevant info is not generated while running show tech command for l2 multicast on n6k platform.
Conditions:
while running show tech command for l2 multicast on n6k platform.
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0) |
|
Known Fixed Releases: * | 7.1(3)N1(0.622), 7.1(3)N1(1), 7.1(3)ZN(0.29), 7.2(2)N1(0.388), 7.2(2)N1(1), 7.2(2)ZN(0.70), 7.3(0)BZN(0.41), 7.3(0)N1(0.75), 7.3(0)N1(1), 7.3(0)ZN(0.73) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv39838 | Title: | CLI to dump all SGs in a system |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
None. This is an enhancement to introduce new CLI.
Conditions:
while running commands. show-tech.
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 11-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0) |
|
Known Fixed Releases: * | 7.1(3)N1(0.622), 7.1(3)N1(1), 7.1(3)ZN(0.29), 7.2(2)N1(0.390), 7.2(2)N1(1), 7.2(2)ZN(0.72), 7.3(0)N1(0.75), 7.3(0)N1(1), 7.3(0)ZN(0.73) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu67165 | Title: | pss runtime oifl not showing correct info |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
pss runtime oifl not showing correct info vi command "show platform fwm info pss runtime_oifl".
Conditions:
while running show command.
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 7.3(0)N1(0) |
|
Known Fixed Releases: * | 7.1(3)N1(0.622), 7.1(3)N1(1), 7.1(3)ZN(0.29), 7.2(2)N1(0.388), 7.2(2)N1(1), 7.2(2)ZN(0.70), 7.3(0)N1(1), 7.3(0)ZN(0.79) |
|
|
| |
:
没有评论:
发表评论