Reference Guide
Table Of Contents
- OS10 Enterprise Edition User Guide Release 10.3.0E
- Getting Started
- Download OS10 image and license
- Installation
- Log into OS10
- Install OS10 license
- Remote access
- Upgrade OS10
- CLI Basics
- User accounts
- Key CLI features
- CLI command modes
- CLI command hierarchy
- CLI command categories
- CONFIGURATION Mode
- Command help
- Check device status
- Candidate configuration
- Backup or restore configuration
- Reload system image
- Filter show commands
- Alias command
- Batch mode commands
- Linux shell commands
- SSH commands
- OS9 environment commands
- Common OS10 Commands
- alias
- batch
- boot
- commit
- configure
- copy
- delete
- dir
- discard
- do
- feature config-os9-style
- exit
- license
- lock
- management route
- move
- no
- reload
- show alias
- show boot
- show candidate-configuration
- show environment
- show inventory
- show ip management-route
- show ipv6 management-route
- show license status
- show running-configuration
- show startup-configuration
- show system
- show version
- system
- terminal
- traceroute
- unlock
- write
- Interfaces
- Enable Ethernet interfaces
- L2 mode configuration
- L3 mode configuration
- Management interface
- VLAN interfaces
- Loopback interfaces
- Port-channel interfaces
- Create port-channel
- Add port member
- Minimum links
- Assign IP address
- Remove or disable port-channel
- Load balance traffic
- Change hash algorithm
- Configure interface ranges
- Configure FEC
- View interface configuration
- Interface commands
- channel-group
- description (Interface)
- duplex
- fec
- interface breakout
- interface ethernet
- interface loopback
- interface mgmt
- interface null
- interface port-channel
- interface range
- interface vlan
- link-bundle-utilization
- mgmt
- mtu
- show interface
- show link-bundle-utilization
- show port-channel summary
- show vlan
- shutdown
- speed
- switchport access vlan
- switchport mode
- switchport trunk allowed vlan
- Layer 2
- 802.1X
- Link aggregation control protocol
- Link layer discovery protocol
- Protocol data units
- Optional TLVs
- Organizationally-specific TLVs
- Media endpoint discovery
- Network connectivity device
- LLDP-MED capabilities TLV
- Network policies TLVs
- Define network policies
- Packet timer values
- Disable and re-enable LLDP
- Advertise TLVs
- Network policy advertisement
- Fast start repeat count
- View LLDP configuration
- Adjacent agent advertisements
- Time to live
- LLDP commands
- Media Access Control
- Multiple spanning-tree protocol
- Rapid per-VLAN spanning-tree plus
- Rapid spanning-tree protocol
- Virtual LANs
- Port monitoring
- Layer 3
- Border gateway protocol
- Sessions and peers
- Route reflectors
- Multiprotocol BGP
- Attributes
- Selection criteria
- Weight and local preference
- Multiexit discriminators
- Origin
- AS path and next-hop
- Best path selection
- More path support
- Advertise cost
- 4-Byte AS numbers
- AS number migration
- Configure border gateway protocol
- Enable BGP
- Configure Dual Stack
- Peer templates
- Neighbor fall-over
- Fast external fallover
- Passive peering
- Local AS
- AS number limit
- Redistribute routes
- Additional paths
- MED attributes
- Local preference attribute
- Weight attribute
- Enable multipath
- Route-map filters
- Route reflector clusters
- Aggregate routes
- Confederations
- Route dampening
- Timers
- Neighbor soft-reconfiguration
- BGP commands
- Equal cost multi-path
- IPv4 routing
- IPv6 routing
- Open shortest path first
- Autonomous system areas
- Areas, networks, and neighbors
- Router types
- Designated and backup designated routers
- Link-state advertisements
- Router priority
- Enable OSPF
- Assign router identifier
- Stub areas
- Passive interfaces
- Fast convergence
- Interface parameters
- Redistribute routes
- Troubleshoot OSPF
- OSPFv3
- OSPF commands
- OSPFv3 Commands
- Object tracking manager
- Policy-based routing
- Virtual router redundancy protocol
- Border gateway protocol
- System management
- Access Control Lists
- IP ACLs
- MAC ACLs
- IP fragment handling
- L3 ACL rules
- Assign sequence number to filter
- L2 and L3 ACLs
- Assign and apply ACL filters
- Ingress ACL filters
- Egress ACL filters
- Clear access-list counters
- IP prefix-lists
- Route-maps
- Match routes
- Set conditions
- continue Clause
- ACL flow-based monitoring
- Enable flow-based monitoring
- ACL commands
- clear ip access-list counters
- clear ipv6 access-list counters
- clear mac access-list counters
- deny
- deny (IPv6)
- deny (MAC)
- deny icmp
- deny icmp (IPv6)
- deny ip
- deny ipv6
- deny tcp
- deny tcp (IPv6)
- deny udp
- deny udp (IPv6)
- description
- ip access-group
- ip access-list
- ip as-path deny
- ip as-path permit
- ip community-list standard deny
- ip community–list standard permit
- ip extcommunity-list standard deny
- ip extcommunity-list standard permit
- ip prefix-list description
- ip prefix-list deny
- ip prefix-list permit
- ip prefix-list seq deny
- ip prefix-list seq permit
- ipv6 access-group
- ipv6 access-list
- ipv6 prefix-list deny
- ipv6 prefix-list description
- ipv6 prefix-list permit
- ipv6 prefix-list seq deny
- ipv6 prefix-list seq permit
- mac access-group
- mac access-list
- permit
- permit (IPv6)
- permit (MAC)
- permit icmp
- permit icmp (IPv6)
- permit ip
- permit ipv6
- permit tcp
- permit tcp (IPv6)
- permit udp
- permit udp (IPv6)
- remark
- seq deny
- seq deny (IPv6)
- seq deny (MAC)
- seq deny icmp
- seq deny icmp (IPv6)
- seq deny ip
- seq deny ipv6
- seq deny tcp
- seq deny tcp (IPv6)
- seq deny udp
- seq deny udp (IPv6)
- seq permit
- seq permit (IPv6)
- seq permit (MAC)
- seq permit icmp
- seq permit icmp (IPv6)
- seq permit ip
- seq permit ipv6
- seq permit tcp
- seq permit tcp (IPv6)
- seq permit udp
- seq permit udp (IPv6)
- show access-group
- show access-lists
- show ip as-path-access-list
- show ip community-list
- show ip extcommunity-list
- show ip prefix-list
- Route-map commands
- continue
- match as-path
- match community
- match extcommunity
- match interface
- match ip address
- match ip next-hop
- match ipv6 address
- match ipv6 next-hop
- match metric
- match origin
- match route-type
- match tag
- route-map
- set comm-list delete
- set community
- set extcomm-list delete
- set extcommunity
- set local-preference
- set metric
- set metric-type
- set next-hop
- set origin
- set tag
- set weight
- show route-map
- Quality of service
- Configure quality of service
- Class-map configuration
- Policy-map configuration
- Ingress traffic priorities
- Queue selection
- Strict priority queuing
- Class of service or dot1p classification
- Mark traffic
- Traffic metering
- Bandwidth allocation
- Service-policy rate-shaping
- Policy-based rate-policing
- Control-plane policing
- Congestion avoidance
- Verify configuration
- Egress queue statistics
- QoS commands
- bandwidth
- class
- class-map
- clear interface priority-flow-control
- clear qos statistics
- clear qos statistics type
- control-plane
- flowcontrol
- match
- match cos
- match dscp
- match precedence
- match qos-group
- match vlan
- mtu
- pause
- pfc-cos
- pfc-shared-buffer-size
- police
- policy-map
- priority
- priority-flow-control mode
- qos-group dot1p
- qos-group dscp
- queue-limit
- queue qos-group
- random-detect
- service-policy
- set cos
- set dscp
- set qos-group
- shape
- show class-map
- show control-plane info
- show control-plane statistics
- show interface priority-flow-control
- show qos interface
- show policy-map
- show qos control-plane
- show qos egress bufffers interface
- show egress buffer-stats interface
- show qos ingress buffers interface
- show ingress buffer-stats interface
- show queuing statistics
- show qos system
- show qos system buffers
- show qos maps
- system qos
- trust
- trust dot1p-map
- trust dscp-map
- qos-map traffic-class
- trust-map
- Virtual link trunking
- Converged data center services
- sFlow
- Troubleshoot OS10
- Support resources
• ARP, IPv6 neighbors, and MAC tables synchronize between the VLT peer nodes.
• VLT peer devices operate as a separate node with independent control and data planes for devices that attach to non-VLT ports.
• One node in the VLT domain takes a primary role and the other node takes the secondary role. In a VLT domain with two nodes, VLT
assigns the primary node role to the node with the highest MAC address.
• In a VLT domain, the peer network devices must run the same OS10 software version.
• Congure the same VLT domain ID on peer devices. If a VLT domain ID mismatch occurs on VLT peers, the VLT Interconnect (VLTi)
does not activate.
• To verify VLAN and VLT-VLAN LAG mismatch errors, use the show vlt id mismatch command on each VLT peer.
• In a VLT domain, VLT peers support connections to network devices that are connected to only one peer.
• To start conguring a VLT domain, enter the vlt-domain domain-id command in CONFIGURATION mode.
VLT interconnect
A VLT interconnect (VLTi) is the link used to synchronize states between VLT peers. OS10 automatically adds VLTi ports to VLANs spanned
across VLT peers. VLTi ports are not supported as members of VLANs congured on only one peer.
• The system automatically provisions the required VLANs.
• VLAN ID 4094 is reserved as an internal control VLAN for the VLT domain, and it is not user congurable.
• VLT peer switches operate as separate nodes with independent control and data planes for devices attached to non-VLT ports.
• The VLTi synchronizes L2 and L3 control-plane information across the two nodes. The VLTi is used for data trac only when there is a
link failure that requires using VLTi for data packets to reach their nal destination.
• Trac with an unknown destination MAC address, multicast, or broadcast trac can cause ooding across the VLTi.
• MAC, ARP, IPv6 neighbors that are learned over VLANs across VLT peer nodes are synchronized across the nodes.
• In a VLT domain, LLDP, ow control, port monitoring, and jumbo frame features are supported on a VLTi.
• Use the discovery-interface command in VLT-DOMAIN mode to congure member interfaces of the VLTi.
Congure VLT
Verify that both VLT peer devices are running the same software version. For VRRP operation, congure VRRP groups and L3 routing on
each VLT peer. To congure VLT and create a VLT domain where two devices are physically connected and are used to provide single port-
channel connection to access devices, congure settings on each VLT peer device.
1 To prevent loops in VLT domain, enable spanning tree protocol globally (spanning-tree mode rstp command). Only RSTP
mode is supported on VLT ports.
2 Create a VLT domain by conguring the same domain ID on each peer (vlt-domain command).
3 Congure the VLT interconnect interfaces on each peer (discovery-interface command). After you congure both sides of
the VLTi, the primary and secondary roles in the VLT domain are automatically assigned.
4 (Optional) Manually recongure the default VLT MAC address.
5 Congure VLT port-channels between VLT peers and an attached device (vlt-port-channel command). Assign the same VLT
port-channel ID (1 to 1024) to interfaces on dierent peers that you bundle together so that peer interfaces appear as a single VLT
LAG to downstream devices.
6 Connect peer devices in a VLT domain to an attached access device or server.
Virtual link trunking
497