Aruba 4100i, 6000, 6100 Switch Series User guide

Type
User guide
AOS-CX 10.13 IP Routing
Guide
4100i, 6000, 6100, 6200 Switch Series
November 2023
Edition: 1
|2
Copyright Information
© Copyright 2023 Hewlett Packard Enterprise Development LP.
This product includes code licensed under certain open source licenses which require source
compliance. The corresponding source for these components is available upon request. This offer is
valid to anyone in receipt of this information and shall expire three years following the date of the final
distribution of this product version by Hewlett Packard Enterprise Company. To obtain such source
code, please check if the code is available in the HPE Software Center at
https://myenterpriselicense.hpe.com/cwp-ui/software but, if not, send a written request for specific
software version and product for which you want the open source code. Along with the request, please
send a check or money order in the amount of US $10.00 to:
Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America.
Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett
Packard Enterprise products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or
omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession,
use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer
Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard
Enterprise website.
Acknowledgments
Intel®, Itanium®, Optane™, Pentium®, Xeon®, Intel Inside®, and the Intel Inside logo are trademarks of
Intel Corporation in the U.S. and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
All third-party marks are property of their respective owners.
Contents
Contents
Contents 3
About this document 10
Applicable products 10
Latest version available online 10
Command syntax notation conventions 10
About the examples 11
Identifying switch ports and interfaces 11
Virtual Routing and Forwarding (VRF) 13
VRF support 13
Loopback 14
Loopback commands 14
interface loopback 14
ip address 15
ipv6 address 16
show interface loopback 16
Static routing 18
Default route 19
Recursive static routes 19
Route manager 19
Configuration concepts 20
Configuration example procedure 20
Basic static route configuration example 20
Static routing commands 21
ip route 21
ip route distance 22
ip route tag 23
ipv6 route 24
ipv6 route distance 25
ipv6 route tag 26
show ip rib 27
show ipv6 rib 30
Open Shortest Path First version 2 (OSPFv2) 34
Overview 34
How OSPFv2 protocol works 35
OSPFv2 concepts 35
OSPFv2 Link-state advertisement (LSA) types 35
OSPFv2 router types 35
OSPFv2 area types 36
OSPFv2 configuration task list 37
Tasks at a glance 37
Configuring OSPF on the routing switch 37
AOS-CX 10.13 IP Routing Guide 3
Contents |4
Setting OSPF network for the area 38
Configuring external route redistribution and control 39
Influencing route choice by changing the administrative distance 40
Configuring graceful restart of OSPF routing 40
Configuring OSPF interface settings 41
Configuring OSPF interface authentication 41
Configuring all OSPF interfaces as passive 42
Configuring SPF throttling timers 42
Clearing OSPF statistics on a switch 43
An example of the OSPFv2 information in the show running-config command 43
OSPFv2 commands 44
active-backbone 44
area (ospf) 45
area default-metric 46
area nssa 46
clear ip ospf neighbors 47
clear ip ospf statistics 48
default-information originate 49
default-information originate always 50
default-metric 51
disable 52
distance 53
distribute-list prefix 54
enable 55
graceful-restart 55
ip ospf area 57
ip ospf authentication 58
ip ospf authentication-key 59
ip ospf cost 60
ip ospf dead-interval 61
ip ospf hello-interval 62
ip ospf keychain 63
ip ospf message-digest-key md5 63
ip ospf network 64
ip ospf passive 65
ip ospf priority 66
ip ospf retransmit-interval 67
ip ospf sha-key sha 68
ip ospf shutdown 69
ip ospf transit-delay 70
keychain 70
max-metric router-lsa 71
passive-interface default 72
redistribute 73
reference-bandwidth 74
rfc1583-compatibility 75
router ospf 76
router-id 77
sha-key sha 77
show ip ospf 79
show ip ospf border-routers 80
show ip ospf interface 81
show ip ospf lsdb 83
show ip ospf neighbors 87
show ip ospf routes 89
show ip ospf statistics 90
AOS-CX 10.13 IP Routing Guide | (4100i, 6000, 6100, 6200 Switch Series) 5
show ip ospf statistics interface 91
summary-address 93
timers lsa-arrival 94
timers throttle lsa 95
timers throttle spf 96
trap-enable 97
Open Shortest Path First version 3 (OSPFv3) 99
Overview 99
How OSPFv3 protocol works 100
OSPFv3 protocol 100
OSPFv3 concepts 100
OSPFv3 Link-state advertisement (LSA) types 100
OSPFv3 area types 102
OSPFv3 router types 103
OSPFv3 configuration task list 104
Tasks at a glance 104
Configuring OSPFv3 on the routing switch 104
Creating an OSPFv3 area 105
Setting OSPFv3 network for the area 106
Configuring external route redistribution and control 107
Influencing route choice by changing the administrative distance 108
Configuring graceful restart 108
Configuring OSPFv3 interface settings 108
Configuring all OSPFv3 interfaces as passive 109
Configuring SPF throttling timers 109
Viewing OSPFv3 information 110
Clearing OSPFv3 statistics on a switch 110
OSPFv3 commands 110
active-backbone 110
area 111
area authentication ipsec 112
area encryption ipsec 113
clear ipv6 ospfv3 neighbors 115
clear ipv6 ospfv3 statistics 116
default-metric 117
disable 118
distance 118
distribute-list prefix 120
enable 121
default-information originate 121
default-information originate always 122
graceful-restart 123
ipv6 ospfv3 area 125
ipv6 ospfv3 authentication null 126
ipv6 ospfv3 authentication ipsec 126
ipv6 ospfv3 cost 128
ipv6 ospfv3 dead-interval 128
ipv6 ospfv3 encryption ipsec 129
ipv6 ospfv3 encryption null 131
ipv6 ospfv3 hello-interval 132
ipv6 ospfv3 network 132
ipv6 ospfv3 passive 133
ipv6 ospfv3 priority 134
ipv6 ospfv3 retransmit-interval 135
ipv6 ospfv3 shutdown 135
Contents |6
ipv6 ospfv3 transit-delay 136
maximum-paths 137
max-metric router-lsa 138
passive-interface default 139
redistribute 139
reference-bandwidth 141
retransmit-interval 142
router-id 143
router ospfv3 143
show ipv6 ospfv3 144
show ipv6 ospfv3 border-routers 146
show ipv6 ospfv3 interface 147
show ipv6 ospfv3 neighbors 149
show ipv6 ospfv3 routes 151
show ipv6 ospfv3 statistics 152
show ipv6 ospfv3 statistics interface 153
summary-address 155
timers lsa-arrival 156
timers throttle lsa 157
timers throttle spf 158
transit-delay 159
trap-enable 160
Equal Cost Multipath (ECMP) 162
Overview 162
ECMP commands 162
show ip ecmp 162
Virtual Router Redundancy Protocol (VRRP) 164
Overview 164
Terminology 164
VRRP operation 165
Multiple VRRP groups 166
VRRP priority 167
VRRP preemption 167
Virtual Router MAC address 168
VRRP and ARP 168
VRRP tracking 168
High availability 168
VRRP and Neighbor Discovery for IPv6 168
Duplicate address detection (DAD) 169
Guidelines and limitations 169
VRRP commands 169
address 169
authentication 170
preempt 172
preempt delay minimum 173
priority 174
router vrrp {enable | disable} 175
no router vrrp 175
show track 176
show track brief 177
show vrrp 177
shutdown 185
timers advertise 186
track (VRRP group) 187
AOS-CX 10.13 IP Routing Guide | (4100i, 6000, 6100, 6200 Switch Series) 7
track (VRRP virtual router) 187
track by 188
version 189
vrrp 190
vrrp dual-active-forwarding 191
Policy Based Routing (PBR) 192
PBR actions 192
PBR policy action and action list 192
PBR action list maximum entries 193
IP versions in an action list 193
Specifying valid next-hop and default-nexthop addresses 194
Hardware path PBR versus software path PBR 194
Hardware versus software path for default-nexthop action 194
Software path and system default route 195
PBR, ECMP, and routing protocols 195
PBR, VSX, and VLAN ACLs 195
PBR software path, VSX, and VRRP 196
PBR and next-hop router reachability 196
CLI errors 196
PBR commands 197
apply policy 197
pbr-action-list 198
pbr-action-list copy 201
pbr-action-list resequence 202
pbr-action-list reset 203
policy 204
show pbr 206
show pbr-action-list 207
show running-config current-context 209
IP Directed Broadcast 211
IP Directed Broadcast configuration example 211
IP Directed Broadcast commands 213
copy support-file feature 213
ip directed-broadcast 214
show arp 214
show ip interface 215
show ip directed-broadcast 216
Key chain 218
Key chain commands 218
accept-lifetime 218
cryptographic-algorithm 219
key 220
keychain 221
key-string 222
name 223
recv-id 224
send-id 225
send-lifetime 225
show capacities keychain 227
show keychain 227
show running-config keychain 229
IP Client Tracker 231
Contents |8
IP Client Tracker commands 231
client track ip 231
client track ip { enable | disable | auto } 232
client track ip client-limit 233
client track ip update-interval 234
client track ip update-method probe 234
show capacities 235
show client ip { count | port | vlan } 236
Routing Information Protocol (RIP) 237
Overview 237
RIPv2 (IPv4) commands 237
Configuration commands 237
router rip 237
Interface commands 238
ip rip 238
ip rip all-ip enable 239
ip rip all-ip disable 240
ip rip all-ip send disable 241
ip rip all-ip receive disable 241
Routing commands 242
enable 242
disable 243
distance 244
maximum-paths 244
redistribute 245
timers update 246
RIPv2 clear commands 247
clear ip rip statistics 247
RIPv2 interface commands 248
enable 248
disable 248
send disable 249
receive disable 250
RIPv2 show commands 251
show capacities rip 251
show capacities-status rip 251
show ip rip 252
show ip rip interface 253
show ip rip neighbors 254
show ip rip routes 255
show ip rip statistics 257
show ip rip statistics interface 257
show running-config 258
RIPng (IPv6) commands 260
Configuration commands 260
router ripng 260
Interface commands 261
ipv6 ripng 261
Routing commands 261
enable 261
disable 262
distance 263
maximum-paths 264
redistribute 264
timers update 265
AOS-CX 10.13 IP Routing Guide | (4100i, 6000, 6100, 6200 Switch Series) 9
RIPng clear commands 266
clear ipv6 ripng statistics 266
RIPng interface commands 267
enable 267
disable 268
send disable 268
receive disable 269
RIPng show commands 270
show capacities ripng 270
show capacities-status ripng 270
show ipv6 ripng 271
show ipv6 ripng interface 272
show ipv6 ripng neighbors 273
show ipv6 ripng routes 274
show ipv6 ripng statistics 276
show ipv6 ripng statistics interface 277
show running-config 278
Support and Other Resources 280
Accessing Aruba Support 280
Accessing Updates 281
Aruba Support Portal 281
My Networking 281
Warranty Information 281
Regulatory Information 281
Documentation Feedback 282
Chapter 1
About this document
About this document
This document describes features of the AOS-CX network operating system. It is intended for
administrators responsible for installing, configuring, and managing Aruba switches on a network.
Applicable products
This document applies to the following products:
nAruba 4100i Switch Series (JL817A, JL818A)
nAruba 6000 Switch Series (R8N85A, R8N86A, R8N87A, R8N88A, R8N89A, R9Y03A)
nAruba 6100 Switch Series (JL675A, JL676A, JL677A, JL678A, JL679A)
nAruba 6200 Switch Series (JL724A, JL725A, JL726A, JL727A, JL728A, R8Q67A, R8Q68A, R8Q69A, R8Q70A,
R8Q71A, R8V08A, R8V09A, R8V10A, R8V11A, R8V12A, R8Q72A, JL724B, JL725B, JL726B, JL727B, JL728B,
S0M81A, S0M82A, S0M83A, S0M84A, S0M85A,S0M86A, S0M87A, S0M88A, S0M89A, S0M90A,
S0G13A, S0G14A, S0G15A, S0G16A, S0G17A)
Latest version available online
Updates to this document can occur after initial publication. For the latest versions of product
documentation, see the links provided in Support and Other Resources.
Command syntax notation conventions
Convention Usage
example-text Identifies commands and their options and operands, code examples,
filenames, pathnames, and output displayed in a command window. Items
that appear like the example text in the previous column are to be entered
exactly as shown and are required unless enclosed in brackets ([ ]).
example-text In code and screen examples, indicates text entered by a user.
Any of the following:
n<example-text>
n<example-text>
nexample-text
nexample-text
Identifies a placeholder—such as a parameter or a variable—that you must
substitute with an actual value in a command or in code:
nFor output formats where italic text cannot be displayed, variables
are enclosed in angle brackets (< >). Substitute the text—including
the enclosing angle brackets—with an actual value.
nFor output formats where italic text can be displayed, variables
might or might not be enclosed in angle brackets. Substitute the
text including the enclosing angle brackets, if any, with an actual
value.
AOS-CX 10.13 IP Routing Guide 10
About this document |11
Convention Usage
|Vertical bar. A logical OR that separates multiple items from which you can
choose only one.
Any spaces that are on either side of the vertical bar are included for
readability and are not a required part of the command syntax.
{ } Braces. Indicates that at least one of the enclosed items is required.
[ ] Brackets. Indicates that the enclosed item or items are optional.
or
...
Ellipsis:
nIn code and screen examples, a vertical or horizontal ellipsis indicates an
omission of information.
nIn syntax using brackets and braces, an ellipsis indicates items that can be
repeated. When an item followed by ellipses is enclosed in brackets, zero
or more items can be specified.
About the examples
Examples in this document are representative and might not match your particular switch or
environment.
The slot and port numbers in this document are for illustration only and might be unavailable on your
switch.
Understanding the CLI prompts
When illustrating the prompts in the command line interface (CLI), this document uses the generic term
switch, instead of the host name of the switch. For example:
switch>
The CLI prompt indicates the current command context. For example:
switch>
Indicates the operator command context.
switch#
Indicates the manager command context.
switch(CONTEXT-NAME)#
Indicates the configuration context for a feature. For example:
switch(config-if)#
Identifies the interface context.
Variable information in CLI prompts
In certain configuration contexts, the prompt may include variable information. For example, when in
the VLAN configuration context, a VLAN number appears in the prompt:
switch(config-vlan-100)#
When referring to this context, this document uses the syntax:
switch(config-vlan-<VLAN-ID>)#
Where <VLAN-ID> is a variable representing the VLAN number.
Identifying switch ports and interfaces
AOS-CX 10.13 IP Routing Guide | (4100i, 6000, 6100, 6200 Switch Series) 12
Physical ports on the switch and their corresponding logical software interfaces are identified using the
format:
member/slot/port
On the 4100i Switch Series
nmember: Always 1. VSF is not supported on this switch.
nslot: Always 1. This is not a modular switch, so there are no slots.
nport: Physical number of a port on the switch.
For example, the logical interface 1/1/4 in software is associated with physical port 4 on the switch.
On the 6000 and 6100 Switch Series
nmember: Always 1. VSF is not supported on this switch.
nslot: Always 1. This is not a modular switch, so there are no slots.
nport: Physical number of a port on the switch.
For example, the logical interface 1/1/4 in software is associated with physical port 4 on the switch.
On the 6200 Switch Series
nmember: Member number of the switch in a Virtual Switching Framework (VSF) stack. Range: 1 to 8.
The primary switch is always member 1. If the switch is not a member of a VSF stack, then member is
1.
nslot: Always 1. This is not a modular switch, so there are no slots.
nport: Physical number of a port on the switch.
For example, the logical interface 1/1/4 in software is associated with physical port 4 in slot 1 on
member 1.
Chapter 2
Virtual Routing and Forwarding (VRF)
Virtual Routing and Forwarding (VRF)
VRF is a technology that allows multiple instances of a routing table to co-exist within the same router.
Because the routing instances are independent, the same or overlapping IP addresses can be used
without conflicting with each other. Network functionality is improved because network paths can be
segmented without requiring multiple routers.
VRF support
The 4100i, 6000, 6100, and 6200 Switch Series support predefined VRFs:
nmgmt: Assigned to the management port and is used to isolate management traffic (6200 Switch
Series only).
ndefault: All other interfaces are automatically assigned to the VRF default (6000, 6100 and 6200
Switch Series).
User-defined VRFs are not supported on the 4100i, 6000, 6100, and 6200 Switch Series.
AOS-CX 10.13 IP Routing Guide 13
Chapter 3
Loopback
Loopback
Loopback interfaces are not supported on the Aruba 6000 and 6100 Switch Series.
Loopback interfaces are not supported on the Aruba 4100i Switch Series.
A loopback interface is a virtual interface supporting IPv4/IPv6 address configuration. The loopback
interface can be considered stable because once created, it remains up. The loopback interface can then
be configured with an address to use as a reference or identifier independent of the physical interfaces.
nDevice identification: As long as the router is operational, the state of the loopback interface is
always up. Even if only one link to the router is active, the loopback interface can be reached. This
functionality makes it possible to identify an active device in the network using the IP address
configured on the loopback interface.
nRouting: Since the loopback interface is always active, a routing session (such as a BGP session) can
continue on an alternate path even if the outbound interface fails. In OSPF, a loopback interface
address is advertised as an interface route into the network. This functionality increases reliability by
allowing traffic to take alternate paths if there is a link failure. In OSPF and BGP, the router ID can be
set to the loopback address to avoid reassignment of the router ID when physical interfaces are
added or removed.
nDevice management: Loopback interface is always reachable and can be used for sending and
receiving management information such as logs and SNMP traps without interruption.
Loopback commands
interface loopback
interface loopback <INSTANCE>
no interface loopback <INSTANCE>
Description
Creates a loopback interface and enters loopback configuration mode.
The no form of this command deletes a loopback interface.
Parameter Description
<INSTANCE> Selects the loopback interface ID. Range: 0 to 4
Examples
switch(config)# interface loopback
switch(config-loopback-if)#
AOS-CX 10.13 IP Routing Guide 14
Loopback |15
Command History
Release Modification
10.07 or earlier --
Command Information
Platforms Command context Authority
All platforms config Operators or Administrators or local user group members with
execution rights for this command. Operators can execute this
command from the operator context (>) only.
ip address
ip address <IPV4-ADDR/MASK> [secondary]
no ip address <IPV4-ADDR/MASK> [secondary]
Description
Sets the IPv4 address for a loopback interface.
The no form of this command reverses the set of the IPv4 address for a loopback interface.
Parameter Description
<IPV4-ADDR> Specifies an IP address in IPv4 format (x.x.x.x), where xis a
decimal number from 0 to 255.
<MASK> Specifies the number of bits in the address mask in CIDR format
(x), where xis a decimal number from 0 to 128.
secondary Indicates that the IPv4 address is a secondary address.
Examples
switch(config)# interface loopback 1
switch(config-loopback-if)# ip address 16.93.50.2/24
switch(config-loopback-if)# ip address 20.1.1.1/24 secondary
Command History
Release Modification
10.07 or earlier --
Command Information
Platforms Command context Authority
All platforms config Operators or Administrators or local user group members with
execution rights for this command. Operators can execute this
command from the operator context (>) only.
AOS-CX 10.13 IP Routing Guide | (4100i, 6000, 6100, 6200 Switch Series) 16
ipv6 address
ipv6 address <IPV6-ADDR/MASK>
Description
Sets the IPv6 address for a loopback interface.
Parameter Description
<IPV6-ADDR> Specifies an IP address in IPv6 format
(xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx), where xis a
hexadecimal number from 0 to F.
<MASK> Specifies the number of bits in the address mask in CIDR format
(x), where xis a decimal number from 0 to 128.
Examples
switch(config)# interface loopback 1
switch(config-loopback-if)# ipv6 address fd00:5708::f02d:4df6/64
Command History
Release Modification
10.07 or earlier --
Command Information
Platforms Command context Authority
All platforms config Operators or Administrators or local user group members with
execution rights for this command. Operators can execute this
command from the operator context (>) only.
show interface loopback
show interface loopback [brief | instance <ID>]
Description
This command displays the configuration and status of loopback interfaces.
Parameter Description
brief Displays brief information about all configured loopback
interfaces.
instance <ID> Displays the configuration and status of a loopback interface ID.
Range: 1-255
Examples
Loopback |17
switch# show interface loopback
Interface loopback1 is up
IPv4 address 192.168.1.1/24
Interface loopback2 is up
IPv4 address 182.168.1.1/24
switch# show interface loopback brief
---------------------------------------------------------------------
Loopback IP Address Status
Interface
---------------------------------------------------------------------
loopback1 10.1.1.1/24 up
loopback1 1111:2222:3333:4444::6666/128 up
switch# show interface loopback 1
Interface loopback1 is up
IPv4 address 192.168.1.1/24
Command History
Release Modification
10.07 or earlier --
Command Information
Platforms Command context Authority
All platforms Operator (>) or Manager
(#)
Operators or Administrators or local user group members with
execution rights for this command. Operators can execute this
command from the operator context (>) only.
Chapter 4
Static routing
Static routing
Static routes are manually configured. If the network topology is simple enough, you can use static
routes for the network's routing requirements. The proper configuration and usage of static routes can
improve network performance and ensure bandwidth for important network applications.
The disadvantage of using static routes is that they cannot adapt to network topology changes. If a fault
or topological change occurs in the network, the relevant routes will be unreachable and a network
administrator must modify the static routes manually.
These 'long prefix' IPv6 routes are programmed in a switching ASIC's TCAM table instead of the usual
route table.
The access switch series are comprised of multiple ASICs of different capabilities with a mixture of line
cards with a varying number of capable ASICs. For consistency across platforms, and to support a fair
usage scheme amongst TCAM users, there is an imposed maximum long prefix IPv6 route capacity of
510 for all access switch series. Once this hardware limit is exhausted, long prefix IPv6 routes can still be
configured/learned but will only be programmed in the software (CPU) path.
Once TCAM/long prefix IPv6 resources are freed up there is no automatic migration of a software-only
long prefix IPv6 route to hardware. The route must be removed and recreated, at which point it
consumes the freed hardware resource.
Note that since the TCAM table is shared between multiple applications, the 510 long prefix IPv6 route
capacity is not guaranteed to be available, depending on current switch configuration/conditions. Use
the 'show' resources' command to display current TCAM resource usage & availability.
Each configured/learned long prefix IPv6 route consumes four TCAM entries and these are noted in the
'Long Prefix IPv6 Unicast Route Lookup' row. The maximum 510 TCAM programmed long prefix IPv6
routes would therefore consume 2040 TCAM entries. The remaining Reserved space is necessary for
internal TCAM management.
Below is an example of resource usage:
show resources
Resource Usage:
Mod Description
Resource Used Reserved Free
------------------------------------------------------------------------------
1/3 Long Prefix IPv6 Unicast Route Lookup
Ingress TCAM Entries 16 2048
Total
Ingress TCAM Entries 16 2048 18432
Egress TCAM Entries 0 0 8192
Ingress Lookups 1 8
Ingress Flex Lookups 0 1
Egress Lookups 0 4
Ingress Policers 0 2047
Egress Policers 0 2047
1/4 Long Prefix IPv6 Unicast Route Lookup
Ingress TCAM Entries 16 2048
Total
Ingress TCAM Entries 16 2048 18432
AOS-CX 10.13 IP Routing Guide 18
Static routing |19
Egress TCAM Entries 0 0 8192
Ingress Lookups 1 8
Ingress Flex Lookups 0 1
Egress Lookups 0 4
Ingress Policers 0 2047
Egress Policers 0 2047
1/5 Long Prefix IPv6 Unicast Route Lookup
Ingress TCAM Entries 16 8192
Total
Ingress TCAM Entries 16 8192 57344
Egress TCAM Entries 0 0 8192
Ingress Lookups 1 8
Ingress Flex Lookups 0 1
Egress Lookups 0 4
Ingress Policers 0 8191
Egress Policers 0 4095
Default route
Without a default route, a packet that does not match any routing entries is discarded and an ICMP
destination-unreachable packet is sent to the source. A default route is used to forward packets that do
not match any routing entry.
The network administrator can configure a default route with the destination as 0.0.0.0 and the mask as
0. The router forwards any packet whose destination address fails to match any entry in the routing
table to the next hop of the default static route.
Recursive static routes
A recursive static route is a route for which the next hop is learned from another routing look up (for
example, dynamic protocol or from another another static route). For example, the following
commands create an unsupported recursive static route:
nip route 99.0.0.0/24 30.0.0.2 - Main static route with gateway 30.0.0.2.
nip route 30.0.0.0/24 20.0.0.2 - Static route to reach the nexthop of the previously configured
route.
Route manager
Route Manager (or Routing Table Manager) is the central repository for all routing information. It
maintains the best routes selected by each routing protocol along with various route attributes in the
Routing Information Base (RIB). Route Manager also manages routes from various routing protocols
and determines the best route to each destination network which needs to be programmed into
Forwarding Information Base (FIB).
If the number of routes is larger than 120,000, displaying all routes will require a significant amount of time to
display output. A warning message is displayed to suggest using filters to display routes for prefixes for faster
results. Use Ctrl+C to interrupt and return to prompt.
AOS-CX 10.13 IP Routing Guide | (4100i, 6000, 6100, 6200 Switch Series) 20
Configuration concepts
Before configuring a static route, you must understand the following concepts:
nDestination address and mask: In the ip route command, an IPv4 address is in dotted-decimal
format. A mask can be in the form of mask length - the number of consecutive 1s in the mask.
nOutput interface and next hop address: When configuring a static route, specify the output
interface or next hop address. The next hop address cannot be a local interface IP address or the
route configuration will not take effect.
nOther attributes: You can configure different priorities and administrative distance for different
static routes to make route management policies more flexible. For example, specifying the same
priority for different routes to the same destination enables load sharing, but specifying different
priorities for these routes enables route backup.
Configuration example procedure
Before configuring a static route, complete the following tasks:
nConfigure the physical parameters for related interfaces.
nConfigure the link-layer attributes for related interfaces.
nConfigure the IP addresses for related interfaces.
6000 and 6100 Switch Series: The number of IPv4 and IPv6 static routes that can be configured is limited to 512
combined.
6200 Switch Series: The number of IPv4 and IPv6 static routes that can be configured is limited to 1024
combined. 16K routes are not supported.
6000, 6100 and 6200 Series Switches do not support IPv6 addresses with prefixes greater than 64. Prefixes
between 65 and 127 will be software-forwarded.
Basic static route configuration example
The IP addresses and masks of the switches and hosts are displayed here. Static routes are required for
interconnection between any two hosts.
Procedure
1. Configure IP addresses for interfaces (details not shown).
2. Configure static routes.
a. Configure a default route on Switch A.
6300# config
6300(config)#
<SwitchA> config
[SwitchA] ip route 0.0.0.0/0 1.1.4.2
b. Configure two static routes on Switch B.
<SwitchB> config
[SwitchB] ip route 1.1.2.0/24 1.1.4.1
[SwitchB] ip route 1.1.3.0/24 1.1.5.6
c. Configure a default route on Switch C.
6300# config
6300(config)#
[SwitchC] ip route 0.0.0.0/0 1.1.5.5
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150
  • Page 151 151
  • Page 152 152
  • Page 153 153
  • Page 154 154
  • Page 155 155
  • Page 156 156
  • Page 157 157
  • Page 158 158
  • Page 159 159
  • Page 160 160
  • Page 161 161
  • Page 162 162
  • Page 163 163
  • Page 164 164
  • Page 165 165
  • Page 166 166
  • Page 167 167
  • Page 168 168
  • Page 169 169
  • Page 170 170
  • Page 171 171
  • Page 172 172
  • Page 173 173
  • Page 174 174
  • Page 175 175
  • Page 176 176
  • Page 177 177
  • Page 178 178
  • Page 179 179
  • Page 180 180
  • Page 181 181
  • Page 182 182
  • Page 183 183
  • Page 184 184
  • Page 185 185
  • Page 186 186
  • Page 187 187
  • Page 188 188
  • Page 189 189
  • Page 190 190
  • Page 191 191
  • Page 192 192
  • Page 193 193
  • Page 194 194
  • Page 195 195
  • Page 196 196
  • Page 197 197
  • Page 198 198
  • Page 199 199
  • Page 200 200
  • Page 201 201
  • Page 202 202
  • Page 203 203
  • Page 204 204
  • Page 205 205
  • Page 206 206
  • Page 207 207
  • Page 208 208
  • Page 209 209
  • Page 210 210
  • Page 211 211
  • Page 212 212
  • Page 213 213
  • Page 214 214
  • Page 215 215
  • Page 216 216
  • Page 217 217
  • Page 218 218
  • Page 219 219
  • Page 220 220
  • Page 221 221
  • Page 222 222
  • Page 223 223
  • Page 224 224
  • Page 225 225
  • Page 226 226
  • Page 227 227
  • Page 228 228
  • Page 229 229
  • Page 230 230
  • Page 231 231
  • Page 232 232
  • Page 233 233
  • Page 234 234
  • Page 235 235
  • Page 236 236
  • Page 237 237
  • Page 238 238
  • Page 239 239
  • Page 240 240
  • Page 241 241
  • Page 242 242
  • Page 243 243
  • Page 244 244
  • Page 245 245
  • Page 246 246
  • Page 247 247
  • Page 248 248
  • Page 249 249
  • Page 250 250
  • Page 251 251
  • Page 252 252
  • Page 253 253
  • Page 254 254
  • Page 255 255
  • Page 256 256
  • Page 257 257
  • Page 258 258
  • Page 259 259
  • Page 260 260
  • Page 261 261
  • Page 262 262
  • Page 263 263
  • Page 264 264
  • Page 265 265
  • Page 266 266
  • Page 267 267
  • Page 268 268
  • Page 269 269
  • Page 270 270
  • Page 271 271
  • Page 272 272
  • Page 273 273
  • Page 274 274
  • Page 275 275
  • Page 276 276
  • Page 277 277
  • Page 278 278
  • Page 279 279
  • Page 280 280
  • Page 281 281
  • Page 282 282

Aruba 4100i, 6000, 6100 Switch Series User guide

Type
User guide

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI