| |
|
Alert Type: | Updated * |
Bug Id: | CSCux56322 | Title: | router crash with memory corruption related to vstack feature |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Cisco router may crash with the following:
*Dec 15 20:59:49.759: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
chunk_diagnose, code = 3
chunk name is MallocLite
current chunk header = 0x3FFE45B8
data check, ptr = 0x3FFE45C8
next chunk header = 0x3FFE462C
data check, ptr = 0x3FFE463C
previous chunk header = 0x3FFE4544
data check, ptr = 0x3FFE4554
========= Dump chunk = 0x3FFE45B8 ======================
3FFE44C8: B0D0B0D B0D0B0D 15A3C78B 0 338E6C48 3FFD6FF0 EF4321CD 338E69E0
3FFE44E8: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4508: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4528: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D 15A3C78B
3FFE4548: 0 338E6C48 3FFD6FF0 EF4321CD 338E69E0 B0D0B0D B0D0B0D B0D0B0D
3FFE4568: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4588: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE45A8: B0D0B0D B0D0B0D B0D0B0D B0D0B0D 15A3C78B FFFFFFFF 31C41154 3FFD6FF0
3FFE45C8: EF4321CD 329E3344 B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE45E8: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4608: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4628: B0D0B0D 15A3C78B 0 31C41154 3FFD6FF0 EF4321CD 329E3084 B0D0B0D
3FFE4648: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4668: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4688: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D 15A3C78B 0
3FFE46A8: 376A5578 3FFD6FF0 EF4321CD 376CB9AC B0D0B0D B0D0B0D B0D0B0D B0D0B0D
========= Dump chunk_next = 0x3FFE462C ======================
3FFE452C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D 15A3C78B 0
3FFE454C: 338E6C48 3FFD6FF0 EF4321CD 338E69E0 B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE456C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE458C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE45AC: B0D0B0D B0D0B0D B0D0B0D 15A3C78B FFFFFFFF 31C41154 3FFD6FF0 EF4321CD
3FFE45CC: 329E3344 B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE45EC: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE460C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE462C: 15A3C78B 0 31C41154 3FFD6FF0 EF4321CD 329E3084 B0D0B0D B0D0B0D
3FFE464C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE466C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE468C: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D 15A3C78B 0 376A5578
3FFE46AC: 3FFD6FF0 EF4321CD 376CB9AC B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE46CC: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE46EC: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE470C: B0D0B0D B0D0B0D 15A3C78B 0 376A5578 3FFD6FF0 EF4321CD 376BEAC8
========== Dump chunk_previous = 0x3FFE4544 =====================
3FFE4444: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D 15A3C78B 0
3FFE4464: 329DFA04 3FFD6FF0 EF4321CD 329DEEC4 B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4484: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE44A4: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE44C4: B0D0B0D B0D0B0D B0D0B0D 15A3C78B 0 338E6C48 3FFD6FF0 EF4321CD
3FFE44E4: 338E69E0 B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4504: B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D B0D0B0D
3FFE4524: B0D
|
|
Last Modified: | 20-MAY-2016 |
|
Known Affected Releases: | 15.6(1.11)T |
|
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.5(3)M2.1, 15.6(1)T1.1, 15.6(1.16)T, 15.6(1.22.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum82405 | Title: | Support for GLC-EX-SMD SFP on ISR-G2 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: GLC-EX-SMD SFP unsupported on ISR-G2 platform.
Conditions: This symptom is observed in ISR-G2 platform.
Workaround: There is no workaround.
|
|
Last Modified: | 27-MAY-2016 |
|
Known Affected Releases: | 15.4(0.20)PI24 |
|
Known Fixed Releases: | 15.4(1.24)T0.2, 15.4(1.25)T, 15.4(2)CG, 15.4(2)T, 15.4(2)T1, 15.4(2.20)T, 15.4(3)M |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy01416 | Title: | EHWIC-1GE-SFP-CU on ISR2951: MAC addr is not learned with EVC/BD config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
EHWIC-1GE-SFP-CU on ISR2951: MAC addr is not learned with EVC/BD config
Conditions:
EHWIC-1GE-SFP-CU on ISR2951: MAC addr is not learned with EVC/BD config when traffic is passed
Workaround:
Unknown
Further Problem Description:
NA
|
|
Last Modified: | 24-MAY-2016 |
|
Known Affected Releases: | 15.5(2.25)T, 15.6(1.8)T |
|
Known Fixed Releases: * | 15.6(2.12.1a)T0, 15.6(2.2)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw97075 | Title: | perf-monitor service policy does not with connection initiator commands |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Perf-monitor service policy does not with connection initiator commands on the flow record
Conditions:
When we have "match connection initiator"or "collect connection initiator" command within a performance-monitor service policy and when we try to apply the policy on an interface we face an error as below
LAB(config-subif)#service-policy type performance-monitor input NETFLOW_AVC
% Field connection initiator cannot be collected. Please modify flow record NETFLOW_AVC.
Unable to attach policy,class [NETFLOW_AVC,class-default]: Failure
Workaround:
Further Problem Description:
|
|
Last Modified: | 24-MAY-2016 |
|
Known Affected Releases: | 15.4(3)M3.2 |
|
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.8, 15.4(3)S5, 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.1, 15.5(3)S2, 15.6(0.22)S0.9, 15.6(1)T0.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv01607 | Title: | Invalid spi, Attempt to use contiguous buffer as scattered, Full queue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traceback & buffer error:
%CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=X.X.X.X, prot=50, spi=0x410D57F3(1091393523), srcaddr=Y.Y.Y.Y, input interface=GigabitEthernet0/1
Jun 16 12:31:00.744: %SYS-2-BADBUFFER: Attempt to use contiguous buffer as scattered src, ptr= 3DE47CB4, pool= 3DE47634 -Process= "", ipl= 1
-Traceback= 300BE43Cz 37116CF8z 37108568z 30402C18z 304037E0z 30406CE4z 37108BDCz 300C04ECz 300BFE30z 3002A23Cz 30F4D278z
Interfaces associated with tunnels get wedged shortly - input queue full.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 24-MAY-2016 |
|
Known Affected Releases: | 15.5(1)T |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.6(1.23)T, 15.6(2.1)T, 15.6(2.12.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy16501 | Title: | Static noise introduced on FXO after IOS upgrade |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Static noise is introduced on the FXO lines after IOS upgrade - Observed this issue in the below IOS versions
154-3.M4
155-3.M1
15.5(3)M train is affected
In the PCM captures we will be able to see the static in the SIN output itself.
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 24-MAY-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: * | 15.4(3)S5.3, 15.5(3)M2.1, 15.5(3)S2.2, 15.6(0.22)S0.18, 15.6(1)T1, 15.6(1.22)T0.2, 15.6(1.23)T, 15.6(2)T, 15.6(2.1)T, 15.6(2.12.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv54418 | Title: | SGT packets dropped when CTS enabled on dot1q sub-interface w bridging |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When enabling "cts manual" on a dot1q sub-interface, SGT tagged packets will be dropped as malformed if ANY of the other dot1q sub-interfaces on that physical interface are configured with a bridge group. If is enabled the following messages are logged on the router:
>Jul 23 01:35:56 CDT: cts-l2sgt_rx:cts_ether_cmd_process_receive_packet:
>[in=GigabitEthernet0/0.101:pak=18D39A8:size=88
>Jul 23 01:35:56 CDT: cts-l2sgt_rx:cts_cmd_get_pre_encap_size:[4]
>Jul 23 01:35:56 CDT: cts-l2sgt_rx:l2cts-drop:[in=GigabitEthernet0/0.101
>src:0100.5e00.000a dst:7cad.742b.7fb2] Malformed L2CTS packet dropped.
Conditions:
Enable "cts manual" on a dot1q sub-interface where a bridge-group is also configured on one of the other dot1q sub-interfaces on the physical.
Workaround:
Remove bridge-group
Further Problem Description:
CMD processing logic was incorrectly reading the pre-encap size (as 4-bytes) on a 802.1Q interface, even though the packet had the 802.1Q header removed.
We started digging into 802.1Q processing logic and found that dot1q demux logic actually removes the 802.1Q header (i.e. 4-bytes) in the packet received on sub-interfaces configured with bridge-group.
On the other hand, the CTS CMD packet processing logic accounts the 4-bytes as pre-encap size oblivious to the fact that the 802.1Q header has actually been removed for that packet. This results in incorrect classification of the CMD payload resulting in the drop of the packet.
The fix is to be cognizant of the removal of 802.1Q header for bridged-interfaces and
appropriately discount the 802.1Q header (4-bytes) while determining the pre-encap size
for CTS processing. This will ensure the proper processing of CMD data.
We will work on an providing an Engineering Special image for validation by Tim/Mike/Matt.
It will be based on Version 15.3(3)M5 that the customer is running. Prior to that we will
ensure basic sanity and regression runs.
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via
normal resolution channels.
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another
evaluation.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 24-MAY-2016 |
|
Known Affected Releases: | 15.3(3)M |
|
Known Fixed Releases: * | 15.3(3)M7, 15.6(2.12.1a)T0, 15.6(2.2)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw51653 | Title: | SIP SRST router in eSRST mode reject phone registration due to + DN |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
SIP SRST router in eSRST mode rejects SIP phones registration if the phone DN has a "+"
Conditions:
- SIP Phones DN has "+"
- id mac is configured under the voice register pool
- SRST router in eSRST mode
Workaround:
- Remove the "+" from the DN
Further Problem Description:
Cisco eSRST when it sync up its configuration with the SRST router in eSRST mode it configures the voice register pool using "mac id" not "id ip address " OR "id network".
When a SIP IP phone with a + DN try to fallback and register to the SRST router in eSRST mode, the router will reject the registration request even though the mac address configured matches the phone
|
|
Last Modified: | 20-MAY-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.1, 15.4(3)S5, 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.1, 15.5(3)S2, 15.6(0.22)S0.14, 15.6(0.26)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz56429 | Title: | C2900: MGCP ssrc=0/seq=0 in secure call |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Sporadically CWMS can't decrypt packets from GW
Conditions:
MGCP with secure call
Workaround:
Using older version , such as 15.2(2)T3
Further Problem Description:
|
|
Last Modified: | 31-MAY-2016 |
|
Known Affected Releases: | 15.6(2)T |
|
Known Fixed Releases: * | 15.4(3)S5.12, 15.5(3)S2.14, 15.6(2.13)T, 16.2(1.21), 16.3(0.206), 16.4(0.29) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv87098 | Title: | Connected number not populated in RPID correctly |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Incorrect connected name appears on the calling phone and RPID header of the SIP message.
Example:
Remote-Party-ID: >;party=called;screen=no;privacy=off
Conditions:
Call flow:
IP phone -- CUCM -- sip - GW -- PRI qsig -- PBX
The Connect should arrive with both the Connected number info and facility message like the following:
Mar 30 14:28:16.559: ISDN Se0/0/1:15 Q931: RX <- CONNECT pd = 8 callref = 0x8081
Facility i = 0x91AA068001008201008B0100A11402022EE206042B0C09028008414C432037393833
Connected Number i = '!', 0x81, '7983'
Locking Shift to Codeset 5
Codeset 5 IE 0x32 i = 0x81
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-MAY-2016 |
|
Known Affected Releases: | 15.1(4)M9, 15.3(3)M4.2, 15.4(3)M2.2 |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.5(3)S2.4, 15.6(0.22)S7, 15.6(0.27)T, 15.6(1)T1.1, 15.6(1.3)T, 15.6(1.9)S, 15.6(1.9)T0.1, 15.6(1.9)T0.2, 15.6(2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz74337 | Title: | Convert cause value 86 to 16 when using MGCP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When the call is disconnected from the PSTN side, the IP Phone plays reorder tone instead of hang up the call.
Conditions:
FXO Port is MGCP controlled by CUCM.
TELCO use Tone based disconnect.
Workaround:
Convert to either H323 or SIP and change the Disconnect Value from 86 to 16:
H323:
application
map
q850-cause 86 q850-cause 16
SIP:
voice class sip-profiles 1
request BYE sip-header Reason modify "Reason: Q.850;cause=86" "Reason: Q.850;cause=16"
Further Problem Description:
1. The following behavior is observed when the issue occurs:
--snip--
Feb 1 21:19:41.013 UTC: //1134/4561055B822D/DSPAPI/[0/1:2]/dsp_voice_det_status_change:
Feb 1 21:19:41.013 UTC: //1134/4561055B822D/DSPAPI/[0/1:2]/dsp_voice_det_status_change:
Status=512, Timestamp=0, Tone ID=0, Trigger=TRUE
Feb 1 21:19:41.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/vtsp_dsm_media_event_cb:
Event=E_DSMP_DSP_SUP_TONE
Feb 1 21:19:41.013 UTC: htsp_process_event: [0/1/0, FXOLS_OFFHOOK, E_DSP_SUP_DISCONNECT]fxols_outgoing_sup_disc
Feb 1 21:19:41.013 UTC: htsp_timer - 1000 msec
Feb 1 21:19:41.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/vtsp_process_event:
[state:S_CONNECT, event:E_TSP_PRE_DISC_CAUSE]
Feb 1 21:19:42.013 UTC: htsp_process_event: [0/1/0, FXOLS_OFFHOOK, E_HTSP_EVENT_TIMER]fxols_disc_confirm
Feb 1 21:19:42.013 UTC: htsp_timer_stop
Feb 1 21:19:42.013 UTC: htsp_timer_stop2
Feb 1 21:19:42.013 UTC: htsp_timer_stop3
Feb 1 21:19:42.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/vtsp_process_event:
[state:S_CONNECT, event:E_TSP_DISCONNECT_IND]
Feb 1 21:19:42.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/act_generate_disc:
Cause Value=86
--snip--
--snip--
Feb 1 21:19:42.013 UTC: MGCP Packet sent to 22.34.64.11:2427--->
DLCX 998279287 aaln/S0/SU1/0@SCORTR11001.bfm.com MGCP 0.1
C: A000000009809b17000000F5
I: 22A
P: PS=1293, OS=206880, PR=1294, OR=207040, PL=0, JI=5, LA=0
E: 501
<---
--snip--
2. A new CLI was created for this, the command will be available on the coming fixed releases:
voice-port x/x/x
supervisory cause-code callclear-to-normaldisconn
|
|
Last Modified: | 23-MAY-2016 |
|
Known Affected Releases: | 15.2(4)M6 |
|
Known Fixed Releases: * | 15.6(2.15)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh77363 | Title: * | No direct IPv6 Call between two phones on EHWIC-D-8ESG-P |
|
Status: | Other |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
No direct IPv6 Call between two phones on EHWIC-D-8ESG-P.
Conditions:
CISCO2911/K9 router with an internal switch EHWIC (EHWIC-D-8ESG-P). All phones are connected to this HWIC. CUCM is a VM connected to one of the onboard Gigabit ports. CUCM onboard port and EHWIC ports share a BVI interface and thus are in the same subnet. Signalling and media preference is set to IPv6 in "Enterprise Parameters Configuration".
Workaround:
None.
|
|
Last Modified: | 05-MAY-2016 |
|
Known Affected Releases: | 15.3(0.2)T |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo48908 | Title: | SM-ES2-24 Support for VTP3 |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
VTP3 not supported on SM-E2-24
Conditions:
Support needed for VTP version 3 on SM-ES2-24
Workaround:
Use VTPv2
Further Problem Description:
|
|
Last Modified: | 05-MAY-2016 |
|
Known Affected Releases: | 15.4(1)T1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtq22846 | Title: | Dr.Maxwell Add SDK 8.0 |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: * |
#
#
# cd /source
/source: bad directory
# ls -l bin/slqssdk
-rwxr-xr-x 1 0 0 774522 May 11 2011 bin/slqssdk
#
|
|
Last Modified: | 03-MAY-2016 |
|
Known Affected Releases: | 1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCto23459 | Title: | Request for PFR CLI support for adding new interfaces for CME interfaces |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
PFR doesn't work for logical interfaces of CME
Conditions:
When PFR is enabled in a router configured with CME, it doesn't learn active probes as the logical interfaces it uses for Voice/DSP are internal code based and are not used by PFR components.
Workaround:
None.
|
|
Last Modified: | 03-MAY-2016 |
|
Known Affected Releases: * | 15.1(3.22)M0.5 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtq44556 | Title: | Modem Upgrade Not working by specifying File name through flash. |
|
Status: | Other |
|
Severity: | 6 Enhancement |
Description: * | Can Download now from flash and specify file to download
|
|
Last Modified: | 03-MAY-2016 |
|
Known Affected Releases: | 1 |
|
Known Fixed Releases: | |
|
|
| |
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论