Wired Intelligent Edge

Hello,

I need to check the specs of the 8320 switch to comply with client requirements.

some of the requirements is to have 64k ipv4 routes, RIP v1 and v2 but i cant verify it thru the datasheet.

does the 8320 support these requirements?

Thank you for the response!

Partially you can find some answer reading this recent thread about setting Aruba 8320 forwarding-table in Mode 3 or 4.

Directly from Aruba 8320 VSX (ArubaOS-CX 10.01.0011 set in Mode 3 on both nodes):

Aruba-8320-1# show platform
  forwarding-table-mode  Show the current forwarding table mode

Aruba-8320-1# show platform forwarding-table-mode

Mode    L2 Entries    Host Entries   Route Entries
   3         98304          120000           16384

Aruba-8320-1# show platform forwarding-table-mode vsx-peer

Mode    L2 Entries    Host Entries   Route Entries
   3         98304          120000           16384

Aruba-8320-1# show capacities

System Capacities:
Capacities Name:                                                            Value
----------------------------------------------------------------------------------
Maximum number of active gateway vmacs configurable                         16
Maximum number of BFD sessions configurable in a system                     256
Maximum number of AS numbers in as-path attribute                           32
Maximum number of as-path entries in a single aspath-list                   16
Maximum number of aspath-lists                                              64
Maximum number of community entries in a single community-list              16
Maximum number of community-lists                                           64
Maximum number of equal cost paths                                          8
Maximum number of neighbors allowed across all VRFs                         50
Maximum number of peer groups allowed across all VRFs                       25
Maximum number of routes accepted from a BGP peer                           15000
Maximum number of prefix entries in a single prefix-list                    16
Maximum number of prefix-lists                                              64
Maximum number of route map entries in a single route-map                   16
Maximum number of route-maps                                                64
Maximum number of routes in BGP RIB                                         30000
Maximum number of route reflector clients allowed across all VRFs           16
Maximum number of access control entries configurable in a system           14336
Maximum number of Access Control Lists configurable in a system             1024
Maximum number of class entries configurable in a system                    1024
Maximum number of classes configurable in a system                          512
Maximum number of entries in an Access Control List                         1024
Maximum number of entries in a class                                        1024
Maximum number of entries in a policy                                       1024
Maximum number of classifier policies configurable in a system              512
Maximum number of policy entries configurable in a system                   1024
Maximum number of GRE IPv4 tunnels in a system                              127
Maximum number of IP ECMP groups of nexthops in a system                    2000
Maximum number of nexthops per IP ECMP group                                8
Maximum number of Mirror Sessions configurable in a system                  4
Maximum number of enabled Mirror Sessions in a system                       4
Maximum number of mstp instances configurable in a system                   64
Maximum number of OSPFv2 areas configurable in the system                   128
Maximum number of OSPFv2 interfaces configurable in the system              128
Maximum number of OSPFv2 interfaces per area in the system                  128
Maximum number of OSPFv3 areas configurable in the system                   128
Maximum number of OSPFv3 interfaces configurable in the system              128
Maximum number of OSPFv3 interfaces per area in the system                  128
Maximum number of unique tunnel local IPs in a system                       16
Maximum number of unique tunnel TTLs in a system                            4
Maximum number of VLANs supported in the system                             4094
Maximum number of unique IPv4 VRRP VRIDs configurable between 1 to 255      8
Maximum number of unique IPv6 VRRP VRIDs configurable between 1 to 255      8
Maximum number of VRRP IPv4 addresses supported                             1024
Maximum number of VRRP IPv4 addresses supported per virtual router          16
Maximum number of VRRP IPv4 virtual routers supported per port              8
Maximum number of VRRP IPv6 addresses supported                             512
Maximum number of VRRP IPv6 addresses supported per virtual router          8
Maximum number of VRRP IPv6 virtual routers supported per port              8
Maximum number of VRRP virtual routers supported                            256

Aruba-8320-1# show capacities-status

System Capacities Status:
Capacities Status Name                                                      Value Maximum
-------------------------------------------------------------------------------
Number of active gateway mac addresses in a system                          0     16
Number of aspath-lists configured                                           0     64
Number of community-lists configured                                        0     64
Number of neighbors configured across all VRFs                              0     50
Number of peer groups configured across all VRFs                            0     25
Number of prefix-lists configured                                           0     64
Number of route-maps configured                                             0     64
Number of routes in BGP RIB                                                 0     30000
Number of route reflector clients configured across all VRFs                0     16
Number of access control entries currently configured                       0     14336
Number of Access Control Lists currently configured                         0     1024
Number of class entries currently configured                                0     1024
Number of classes currently configured                                      0     512
Number of policies currently configured                                     0     512
Number of policy entries currently configured                               0     1024
Number of GRE IPv4 Tunnels currently configured                             0     127
Number of Mirror Sessions currently configured                              0     4
Number of Mirror Sessions currently enabled                                 0     4
Number of mstp instances currently configured                               0     64
Number of OSPFv2 areas configured in the system                             0     128
Number of OSPFv2 interfaces configured in the system                        0     128
Number of OSPFv3 areas configured in the system                             0     128
Number of OSPFv3 interfaces configured in the system                        0     128
Number of unique tunnel local IPs currently configured                      0     16
Number of unique tunnel TTLs currently configured                           0     4

Aruba-8320-1#

Also:

With regard to ArubaOS-CX (Aruba 8320 and Aruba 8400) support of RIPv1 (RFC 1058), RIPv2 (RFC 2453) and - eventually - RIPng (RFC 2080 along with RFC 2081 and RFC 2082) no references can be found on latest QuickSpecs, Datasheet or related Release Notes. That's pretty strange (Could it be that RIPv1/v2 should be considered outdated protocols - if not totally dead already - since more modern/advanced/performing routing protocols are instead implemented on ArubaOS-CX just because those one are exactly reflecting the actual routing "state of the art" approach adopted by Aruba Campus Core/ToR deployments?).

I recall to have seen RIP generically cited on some ArubaOS-CX related presentations but I'm not totally sure it was listed within protocols/standards supported specifically on Aruba 8320 platform, Aruba 8400 platform, both of them or just on ArubaOS-CX operating system.