214. [syslog] set device over night, found temperature was out of its limit range (abnormal)
when show logging (Dec 24 23:43:43 EM system: Board_1 temperature value 192 is out of
its limit range)
215. [Private VLAN] In show VLAN counter, community VLAN and isolated VLAN also will
count into primary VLAN. (Cross Unit issue)
216. [syslog] after system voltage value was back from error to normal, a recovered log should
be display when show logging (ex: System voltage has recovered to normal state)
217. [MIB-RMON] When setting the historyControlBucketsRequested (OID:
1.3.6.1.2.1.16.2.1.1.3) to 65535, the historyControlBucketsGranted (OID:
1.3.6.1.2.1.16.2.1.1.4) will show ”200”, not ”65535”.
218. [IPv6 Static Route]When remove ipv6 default gateway, the default route in show ipv6
route also should be removed.
219. [MIB-
dot1qTp] The dot1qFdbDynamicCount (OID: 1.3.6.1.2.1.17.7.1.2.1.1.2) can’t be
added.
220. [IPv6] Enable ipv6 and ipv6 autoconfig in interface VLAN without static VLAN setting,
after write memory and reboot, CLI will pop error messages. CLI and Web has the same
symptom.
221. [DHCPv6 Relay] Merge Maximum DHCPv6 Relay setting, Web page will have abnormal
in DHCPv6 relay status.
222. [MIB-
pingMIB] SNMPc (version 8.0) can’t set IPv6 format to pingCtlTargetAddress (OID:
1.3.6.1.2.1.80.1.2.1.4) and pingCtlSourceAddress (OID: 1.3.6.1.2.1.80.1.2.1.19), but
SilverCreek can.
223. [SNMP-
traceRouteMIB] The traceRouteMIB (OID: 1.3.6.1.2.1.81) can’t set IPv6 format
address and IPv4 format address is different to pingMIB.
224. [Syslog] Due to the radius server IP problem (set wrong/inexistence radius server
IP),SNMPc should send trap(s) ”RADIUS server not reachable” for each time user try to
re-logging through Radius server (not only display the trap once)
225. [ICMPv6] Set ICMPv6 Rate Limit Error Interval to 2147483647 (maximum), show ipv6 will
display as 214748364 in CLI, ipv6 interface status will display as 2147483640 in Web
page.
226. [Policy Route] When create policy route, then subnet A ping access IP_B fails.
227. [DHCPv6 Client] In DHCPv6 Client, the information refresh minimum should have
warning message when set over maximum value. CLI and Web has the same symptom.
228. [LLDP-MED] the format for LLDP-med should be correspond to each title when show
LLDP configuration interface port-channel 1
229. [LLDP-med] under Capabilities, device type: Network Vonnectivity should be Network
Connectivity (word spell incorrect) when show LLDP info local interface port-channel 1
230. [LLDP-med] after type in the command for LLDP med (LLDP med location coordinate
latitude north 24.0 longitude east 120.0 altitude meters 13 datum WGS84 ), an unKnown
message pops up ”Invalid coordinate LCI: Unknown option meters”; but it works for the
word
”
meter”
231. [MIB] Using SNMPc to set lldpConfigManAddrPortsTxEnable (OID:
1.0.8802.1.1.2.1.1.7.1.1) to 0x80 will make unexpected ports to be set--
＞
0x80:00:00:80:40:EA:B0:00. (Please check all MIB related settings)
232.
[IPv6]In Interface Setup web page, it could not have correct ”delete” and ”cancel” item.
233.
[IPv6]In IPv6 Global Address Setup web page, it could not have correct ”delete”
and ”cancel” item.
234.
[IPv6]In Ipv6 Prefix Setup web page, some items ”delete” check box will be enable
automatically.
235.
[IPv6]In Ipv6 Neighbor Setup web page, it could not have correct ”delete” and ”cancel”
item.
236. [IPv6 Static Route]In Ipv6 static route web page, i
t could not have correct ”delete”
and ”cancel” item.
237. [IPv6 Static Route]In Ipv6 static route web page, it could not have the related next hop
information.
238. [LLDP-med] Few unkown words
”＜
NULL
＞
@( {CHU
＜
NULL
＞
Fa1/0/4
”
display
under Location when show LLDP info remote interface port-channel
239. [Rmirror] Create Rmirror ruler, it will create the related VLAN automatically. But, remove
Rmirror ruler, it could not remove the related VLAN automatically.
