host1(config-tunnel-server)#
max-interfaces 0
•
Issue the
no tunnel-server
command from Global Configuration mode. This command
unprovisions the tunnel-service interfaces on the specified tunnel-server port but does
not
delete the port itself.
host1(config)#
no tunnel-server 2/2/0
NOTE:
When you issue these commands on the ES2 10G ADV LM, the line module
reloads with a warning message and the original forwarding image appears.
max-interfaces
•
Use from Tunnel Server Configuration mode to provision the maximum number of
tunnel-service interfaces to be used on a tunnel-server port.
•
Specify an integer in the range 0–16000 to provision the maximum number of
tunnel-service interfaces.
•
Use the
all-available
keyword to provision the maximum number of tunnel-service
interfaces to match the maximum value that the tunnel-server module supports.
•
Examples
host1(config-tunnel-server)#
max-interfaces 5000
host1(config-tunnel-server)#
max-interfaces all-available
•
Use the
default
version to restore the default configuration. On dedicated tunnel-server
ports, the default configuration is the maximum number of tunnel-service interfaces
that the service module supports (
all-available
). On shared tunnel-server ports, the
default configuration is zero tunnel-server interfaces.
•
Use the
no
version to reduce the number of provisioned tunnel-service interfaces to
zero. Issuing the
no max-interfaces
command has the same effect as issuing the
max-interfaces 0
command.
•
See max-interfaces.
reserve-bandwidth
•
Use from Tunnel Server Configuration mode to reserve a percentage of the total
bandwidth for forwarding on a shared tunnel-server port. The remaining bandwidth is
used for tunnel processing.
•
Specify the value of 80 to reserve 80 percent of the total bandwidth for forwarding.
The remaining 20 percent is used for tunnel processing. Specify the value of 50 to
reserve 50 percent of the total bandwidth for forwarding. The remaining 50 percent
is used for tunnel processing. You may not always obtain the exact percentage of
bandwidth specified because of the overhead involved with identifying and assigning
incoming traffic to the appropriate resources. You may actually obtain a value less
than the configured value.
•
Examples
host1(config-tunnel-server)#
reserve-bandwidth 80
host1(config-tunnel-server)#
reserve-bandwidth 50
Copyright © 2010, Juniper Networks, Inc.
220
JunosE 11.2.x Physical Layer Configuration Guide
Summary of Contents for JUNOSE 11.2.X MULTICAST ROUTING
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x Physical Layer Configuration Guide...
Page 16: ...Copyright 2010 Juniper Networks Inc xvi JunosE 11 2 x Physical Layer Configuration Guide...
Page 24: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x Physical Layer Configuration Guide...
Page 66: ...Copyright 2010 Juniper Networks Inc 44 JunosE 11 2 x Physical Layer Configuration Guide...
Page 228: ...Copyright 2010 Juniper Networks Inc 206 JunosE 11 2 x Physical Layer Configuration Guide...
Page 247: ...PART 2 Index Index on page 227 225 Copyright 2010 Juniper Networks Inc...
Page 248: ...Copyright 2010 Juniper Networks Inc 226 JunosE 11 2 x Physical Layer Configuration Guide...
