TSSN1 - Switching Update AOS 8.8 v3
TSSN1 - Switching Update AOS 8.8 v3
Hardened SMB
Netwks Netwks
OS6860N-P24M
OS6860N-P24Z
OS6900-C32E
OmniSwitch
VxLAN on all
OmniSwitch
6900s* & 6860N
SPB neighbors’
OmniSwitch scalability
Naas ready on
switches OmniSwitch
XGSPON SFP support
OmniSwitch for HPOL (6360/6560)
ERP and SPB
interworking
OS6860N FAMILY
Advanced MultiGig access switch
OS6860N Rationale:
OS6860N-P24M • 25G/100G Uplinks
Gig fiber w/ 25G uplink OS6860N-P48M • More MultiGig
Gig/MultiGig Access options (5G/10G)
Gig/MultiGig Access • MACsec
w/ 25G uplink w/ 25G uplink • 95W HPoE (IEEE
OS6860N-U28
802.3bt)
• Inline routing
• MPLS (future)
OS6860N-P24Z OS6860N-P48Z
10G/25G Aggregation
10G Aggregation w/ MACsec
8.9 R1
OS6900-X48C6
48x 10G fiber ports OS6900-X48C4E OS6900 Rationale:
OS6900-X24C2 25G Aggregation
24x 10G fiber ports 6x 100G uplinks 40x 10G fiber ports • More link options
8x 10/25G (25G/100G)
2x 100G uplinks
4x 100G uplinks
• MACsec
10G Server 100G Core • SPB Inline routing
Connectivity OS6900-V48C8 • Switching capacity
48x 25G ports with • MPLS (future)
8.9 R1 8x 100G uplinks
OS6900-T48C6 OS6900-C32E
OS6900-T24C2 48x 10G-BaseT ports 6x 32x 100G ports
24x 10G-BaseT ports 100G uplinks
2x 100G uplinks
VC Compatibility Matrix
OS6360 OS6560 OS6860E OS6860N OS6900 OS6900 OS6900 OS9900
X40/X20 X48 Chassis w/ CFM
T40/T20 T48 Chassis with CFM2
All models All models All models All models X48C4E
X72 V72/V48
C32/C32E
SPB High
VXLAN High Speed Virtual
L3VPN Capacity
EVPN* 100G Chassis
MPLS* 25T
OmniSwitch 9900
NOTE: Mix of CFM and CFM2 will not be allowed in same chassis SPB Chassis Core/Edge
SOFTWARE FEATURES AOS R8.8
ENTERPRISE SWITCHING MARKET TRENDS
Speeds & Feeds Vertical Mix Shift IoT Adoption Cloud Managed Virtualization Push
Services
• WiFi 6/6E adoption • Industrial, logistics • Carpeted Enterprise • Cloud Managed and • Competitive push from
driving 2.5/5G access growing more rapidly access port use associated software Cisco/HPE etc to
compared to other changing: More IoT services growing at a standardize VxLAN-
• Migration to 25G uplinks verticals devices & infra ports. robust 30% EVPN as Campus
in access Less user connectivity network fabric
• All competitors ports. • Move to cloud posing
• 100G in Campus core, launching hardened demands on high speed • Works well for
400G in DC continue to portfolios • New power configs for core customers already
grow at robust pace light & IoT familiar with it in their
DC
Virtualization
MTU ISSUE IN MULTIPLE OVERLAY NETWORKS
Path MTU discovery doesn’t work well particularly when tunneled traffic is traversing over public/private cloud
Results in packet drop at intermediate routers/PE if MTU is more than what intermediate tunnel can support
ok
VxLAN
TCP VxLAN VxLAN TCP
Service
• Configuration
>> service service_id sap {port chassis/slot/port[-port2] | linkagg agg_id[-agg_id2]} [sap_id] [description desc_info] [tcp-
mss {overlay-profile {spb | ethernet} | num}
Supported Platforms
Usage guidelines
• The SAP (both static & dynamic) and its service mapping should pre-exist before LPS can be configured on it
• The dynamic SAP must be created upfront through persistent profile-configuration on UN access port
• LPS on SAP port must be unconfigured before SAP port / persistent-profile
• Violation shutdown option not supported
o Port cannot be administratively disabled when port security violation is detected
o However, violation restrict option is supported to filter unauthorized traffic when port security
violation detected.
• Global level command “port-security chassis admin-state enable/disable” is not supported on SPB SAP
o Use port level command to control the port security admin-state
Platforms Supported
• All platforms that support a service domain : SPB, VxLAN, L2GRE. Is not supported on OS6360, OS6560 and
OS6465
PORT SECURITY ON SAP
Port Security port Static and Dynamic UNP SAP Static vlan port and dynamic UNP
SPB SCALABILITY
Platforms Supported:
• OS6360, OS6465, OS6560, OS6860/E, OS6860N, OS6865, OS6900, OS9900, OS6900-C32, OS6900-
C32E, OS6900-T48C6, OS6900-X48C4E, OS6900-X48C6, OS6900-V48C8, OS6900-V72, OS6900-X72
• NaaS is not available for OS9900
Security
THIN-CLIENT OMNISWITCH
What is it ?
A way to centrally administer/manage the network in a secure way without leaving any sensitive configuration information on
the site switch.
No configuration written to “vcboot.cfg” except minimal configuration for reachability to OVE
Any local config allowed on switch to be approved centrally. Configuration save via “write memory” is not allowed.
Why?
For security sensitive customers who do not want the switches to store / allow any configuration which may reveal details of
sensitive information .When the switch is in Thin-client mode, no configuration is saved in the vcboot.cfg file. Every time the
switch boots up it will contact OVE to retrieve its mode and the configuration to be operating with .
How ?
Switch does a call home at bootup to OVE over HTTPS.
If no DHCP server, a minimal configuration for network access to OVE must be done & is allowed on the switch
“Thin-Client” mode is configured from OV and Switch is centrally configured from OVE each time the switch boots up.
Works with OVE (OmniVista Enterprise) only. OVC support will come in a future release.
If the device is stolen/decommissioned, powered down or reset, there is no configuration information left on the switch
except minimal configuration for network connectivity to OVE .
Platforms Supported:
All omniswitch platforms
RESTORE
At bootup, if switch bootloader detects a USB with ALE generated signature file and AOS image, it will boot from
USB
Files required for switch operation are unencrypted and copied to the switch
Usage Guidelines
Encrypted backup/restore is supported on OS6465 only
Bootable option is available on OS6465 & OS6865
‘usb backup’ command is mutually exclusive with ‘usb auto-copy’ command
A secure way to restore / deploy switches in the field with minimal expertise
Security
MORE SECURE “ENHANCED MODE”
• A new “secureadmin” user to invoke the enhanced mode at bootup automatically to ensure no tampering post
factory-shipment
• ASA enhanced mode has been augmented further to add P.O.S.T functions, integrity checks, critical process
monitoring etc.
• User has an option to login either as “secureadmin” or “admin” (current) at bootup. Login through any of the
admin accounts disables the other admin account permanently
• In SecureAdmin mode, AOS performs Hardware self test, process self test and critical software integrity
check on every bootup.
• Self tests and integrity checks can be invoked manually also by the user through cli
• All switch access services (FTP, Telnet, SSH etc) are disabled by default and have to be manually enabled
• Switch access services among others : Telnet, SSH, FTP, SFTP, HTTP/HTTPs, Radius, SNMP, NTP are part of
critical software list.
• Process ids of these services are monitored continuously and if found altered, switch is forced to reboot.
Prevents any user from loading any pre-compiled malicious binary (sshd) to the switch.
• AOS image & config integrity is checked at every bootup
• Critical commands such as rm, cp, rmdir, su etc are allowed only through console and not allowed to be run
through remoteAsessions
new security mode for critical infrastructure customers – Defense, Healthcare, Transport, FI
HPOL
GPON/XGSPON SUPPORT ON OMNISWITCH
• HPOL end to end solution with Stellar WLAN is in the scope of 89R1
Virtualization
OTHER ENHANCEMENTS
VxLAN Support
• Support for VxLAN L2 functionality on OS6860N and OS6900-X48/T48/V48/X48C4E/C32E
• Support for LPS, Kerberos, Location Time Policies and User defined role on VxLAN is not supported n AOS 88R2
• OVSDB is not supported for platforms added in this release
• VxLAN implementation on existing OS6900 platforms remains unchanged in AOS 8.8R1
ERP-SPB Interworking
• Allows seamless connectivity between an access ERP ring & an SPBM aggregation network
• Configurations supported: ERP ring connecting to a single BEB or to two different BEBs
• Platforms supported: OS9900, OS6900 (TD3), OS6860/E/N
OTHER ENHANCEMENTS
AOS Microservices Controller
redundancy
• Enables 1:1 redundancy for AMS controller
• Uses VRRP protocol
• Redundant controller configuration through DHCP VSO options or manually
• DHCP Server option 43 config:
>> option 43 140 IP-address=192.168.40.254 141 8883 142 “--primary-broker 192.168.40.2 ---secondary-broker 192.168.40.4 100
ISSU Upgrade
• Transition of ASIC-hardware programming to new methodologies in AOS 8.8R01 would mean that ISSU upgrades will not be
supported on some platforms. The change was necessitated by the discontinuation of support from vendor for pre-existing
methods. Following platforms are impacted :
OS6900-V72/C32
OS6900-X/T48C6
OS6900-X48C4E
OS6900-V48C8
OS6860N (All SKUs)
OTHER ENHANCEMENTS
RMON Support
• RMON support has been added on the OS6860N and OS6900-V72/C32/C32E/X48C6/T48C6/X48C4E/V48C8 models
in 8.8R2.