Unprovisioned Tunnel-Service Interfaces
Tunnel-server ports exist whether or not they have been configured. This means that you
cannot delete a tunnel-server port from a module. However, you can unprovision all of
the tunnel-service interfaces on a tunnel-server port by issuing the
no max-interfaces
command or the
no tunnel-server
command.
You can also restore the default configuration by issuing the
default max-interfaces
command. On dedicated tunnel-server ports, the default configuration is the maximum
number of interfaces that the port supports. On shared tunnel-server ports, the default
configuration is zero tunnel-service interfaces.
NOTE:
If the module on which the tunnel-server port resides supports IP reassembly
or NAT services, these services become enabled when you provision tunnel-service
interfaces on the port. However, when you unprovision tunnel-service interfaces to zero,
only IP reassembly is disabled and NAT remains configured in the current release.
Configuring Tunnel-Server Ports and Tunnel-Service Interfaces
This section describes the tasks associated with configuring a tunnel-server port and
tunnel-service interface.
NOTE:
Dedicated and shared tunnel servers do not support QoS profiles on interfaces
stacked on the server-port.
Identifying the Physical Location of the Tunnel-Server Port
To display the physical location of the dedicated and shared tunnel-server ports on your
module, issue the
show tunnel-server config
command.
host1#
show tunnel-server config
Server Ports
------------
Provisioned
Port Type MaximumInterfaces Interfaces HwPresent Bandwidth-Reserved
-------- ------- ----------------- ----------- --------- -----------------
Port 2/2/0 shared 8000 0 yes N/A
Port 8/0/0 dedicated 16000 8000 yes N/A
Port 12/0/0 shared 8000 0 yes 90
Provisioning the Maximum Number of Interfaces on a Tunnel-Server Port
To provision the maximum number of interfaces on a tunnel-server port:
1.
From Global Configuration mode, specify the location of the dedicated tunnel-server
port that you want to configure.
On a dedicated tunnel-server port:
host1(config)#
tunnel-server 8/0/0
217
Copyright © 2010, Juniper Networks, Inc.
Chapter 6: Managing Tunnel-Service and
IPSec-Service Interfaces
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...