Cisco AP775A - Nexus Converged Network Switch 5010 릴리스 노트 - 페이지 10
{카테고리_이름} Cisco AP775A - Nexus Converged Network Switch 5010에 대한 릴리스 노트을 온라인으로 검색하거나 PDF를 다운로드하세요. Cisco AP775A - Nexus Converged Network Switch 5010 26 페이지. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Cisco AP775A - Nexus Converged Network Switch 5010에 대해서도 마찬가지입니다: 릴리스 노트 (48 페이지), 릴리스 노트 (44 페이지), 빠른 참조 매뉴얼 (14 페이지), 릴리스 노트 (26 페이지)
페이지 인쇄
Limitations
S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
interface vfc 1/1
no shutdown
vsan database
vsan 1 interface vfc 1/1
Release 4.0(1a)N1(1a) Converted Configuration
vlan 101
fcoe vsan 1
interface Ethernet 1/1
switchport mode trunk
switchport trunk native vlan 2
switchport trunk allowed vlan 2,101
spanning-tree bpduguard enable
spanning-tree port type edge trunk
interface vfc 1
no shutdown
vsan database
vsan 1 interface vfc 1
Upgrading from Cisco NX-OS 4.0(0)-Based Releases
When you upgrade your Cisco Nexus 5000 Series switch from Cisco NX-OS 4.0(0)-based releases, all
virtual Fibre Channel and virtual Ethernet interface configuration will be lost because the applicable CLI
is incompatible with the previous releases. We recommend that you backup your startup-config file prior
to performing the upgrade. If your switch has an FCoE configuration you will need to reconfigure FCoE
using the new FCoE CLI. Alternatively, you can contact Cisco Customer Support for help with
upgrading and converting your configuration to the new format.
Downgrading to Cisco NX-OS 4.0(0)-Based Releases
Your FCoE configuration will be lost on downgrade. We recommend that you backup your original
configuration prior to upgrading to Cisco NX-OS Release 4.0(1a)N1(1a). The backed up startup-config
can be used to restore your original configuration after a downgrade.
Limitations
This section describes the limitations in Nexus 5000 Series switches, Release 4.0(1a)N1(1a).
•
•
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
10
The untagged cos command is not supported in this release.
Traffic going out the Ethernet SPAN destination is always tagged. The SPAN destination can be in
the access or trunk mode and frames on the SPAN source port can be tagged or untagged. Frames
are always tagged internally as they travel through the system. Information about whether the frame
was originally tagged or untagged, as it appeared in the SPAN source, is not preserved in the SPAN
destination. The spanned traffic exiting the SPAN destination port always has the VLAN tag on it.
OL-16601-01