Reconfigure Basic Settings
When you deploy a unit on your network, you must configure settings,
such as an IP address, to enable communication with the unit. These settings
are configured during the Guided Setup process, described in the Getting
Started Guide. Periodically, you may need to modify these settings.
|
|
Note: To perform this task from PolicyCenter, you must first select a group and/or unit configuration from the Group:
and Unit: drop-down lists at the top of the page.
|
To view or modify the basic settings:
1. Click the setup tab. The Basic Settings
automatically appear on the Setup screen.  show screen
2. Verify or modify configuration details, as described
in the following table.
3. Click apply changes to update the settings.
| Field |
Description |
| Shaping |
When shaping is on, traffic is classified and measured,
and policies and partitions actively control bandwidth allocation.
When shaping is off, traffic is classified and measured, but it is
not actively managed. |
| Traffic Discovery |
When enabled, traffic discovery lets PacketWise automatically
create classes based on the service types it detects. |
Easy Configure
(not available on all models) |
When Easy Configure is enabled, you assign your applications
and services to categories (such as Mission Critical or Prohibited),
and then PacketWise automatically creates appropriate partitions and
policies. See Assign
Categories to Classes. |
Auto Policy
(not available on all models) |
When Auto Policy is enabled, a suggested policy is
assigned to each discovered traffic class. See Use
Suggested Policies for more details. |
Compression
(not available on all models) |
When compression is enabled, PacketWise will automatically
create and use a tunnel to transport compressed data between Packeteer
units. See Compression
Overview for details. |
| IP Address |
The IP address assigned to the unit |
| Net Mask |
The subnet mask for the network where the unit resides |
| Gateway |
The IP address the unit uses to reach other networks.
The unit uses this gateway to route unit-initiated transactions to
a non-local address — for example, FTP transfers initiated from
the unit to a server on a non-local network. Frequently, the gateway
address is the same as the site router address. |
| Site Router |
The IP address of the access router to the link the
unit is managing
When you set an IP address, the unit only manages packets going to
this router. All other packets are ignored.
When you set the site router to none, the unit manages all
traffic passing through it, regardless of whether the traffic is going
to or from the site router. |
Domain
(optional) |
The default domain name |
| DNS Server(s) |
The IP address(es) of the Domain Name Server(s). Enter a maximum
of eight addresses separated by spaces and/or commas.
If you don't specify a DNS server, Top Talker/Listener reports
will list IP addresses only, instead of more meaningful domain names.
|
Inbound Rate
Outbound Rate |
To manage bandwidth, PacketWise must know the capacity of the access
link it is managing. Data rates may be specified as integer bits
per second, followed by a “k” (thousands) or “M”
(millions), or specified symbolically (“T1”, “E1”,
“T3”).
- For a full-duplex WAN link, enter the total link speed for the
inbound and outbound rates. Because full-duplex has wires that
can simultaneously communicate in both inbound and outbound directions,
you should enter the same rate for Inbound Rate and Outbound Rate.
For example, if you have two T1 lines (3 Mbps), you should enter
3M for Inbound Rate and 3M for Outbound Rate.
- In rare situations in which the Packeteer unit is managing half-duplex
links, split the rate between the inbound and outbound links.
For example, if you are managing a 10 Mbps half-duplex link, you
could configure 5 Mbps for the inbound rate and 5 Mbps for the
outbound rate since data can be transmitted in only one direction
at a time.
Note: If you have any NIC in the Packeteer unit set to
half-duplex, you will not be able to transmit and receive at the
same time, limiting the bandwidth to half. For example, if you
have set 10 Mbps half-duplex on the NIC, the Packeteer unit will
be able to pass only 5 Mbps IN and 5 Mbps OUT at one time. Hence,
you will not be able to manage a WAN link size greater than 5
Mbps.
- If your unit is using two LAN Expansion Modules (LEMs) to manage
two different WAN links, the link speed should be the size of
the smallest LEM. For example, if you have two 100 Mbps
LEMs managing two links, you should specify 100M for the rate.
On the other hand, if your unit is using two LEMs to manage a
single WAN link, you should specify the WAN link speed for the
rate. Although the Info page will give you an error message (such
as "Link speed of 155 Mbps exceeds outside NIC speed of 100
Mbps") in the latter situation, it is still appropriate to
specify the actual size of the link for the rate.
- When using the direct standby feature in a load-sharing topology,
you should set the link speed to the sum of both WAN links. Because
each unit receives copied packets from its partner, the Packeteer
unit must have overall Inbound and Outbound partition sizes that
will support that level of extra traffic. Note: In this
situation, you may want to use the access-link monitoring feature
(advanced mode) to monitor the routers’ WAN interfaces and
avoid oversubscribing the WAN bandwidth.
- Software configuration determines maximum shaping capacity.
See PacketShaper,
PacketSeeker,
or PacketShaper ISP
Configuration Limits.
Note: 10BaseT links rarely reach the 10 Mbps limit. Keep
Ethernet's practical limits in mind when configuring rates.
|
| NIC Modes |
Packeteer 1500, 2500, 4500, 6500 Series
Choose: auto-negotiate, 100BaseT half-duplex, 10BaseT
full-duplex or 100BaseT full-duplex.
When you select auto-negotiate, the Packeteer unit detects
the connected device’s port speed and configures the speed
and duplex settings for a “best match.” While the Packeteer
unit automatically negotiates ports according to the IEEE 802u standard,
other connected devices may not operate in compatible modes, which
can result in connectivity problems.
Packeteer 8500 Series (Gigabit Fiber-Optic)
The choices for gigabit fiber-optic are auto-negotiate,
autoneg-only, and 1000BaseX full-duplex. If auto-negotiate
is specified and auto-negotiation signals are not received from
the other side, the negotiation will time out in one second and
the interface will be set at 1000 fixed. To force auto-negotiation
without timing out, use the autoneg-only option.
Packeteer 8500 Series (Gigabit Ethernet)
For gigabit Ethernet, you can specify auto-negotiate or
1000BaseT full-duplex. (1000BaseT actually does the same
thing as auto-negotiate; manual setting to gigabit Ethernet is not
part of the 802.3 Ethernet standard.)
LAN Expansion Modules
If you have installed one or two LAN Expansion Modules, you will
see additional NIC Mode fields. The additional fields will be named
to reflect the module location. Possible additional fields are:
Lower_inside and Lower_outside
Upper_inside and Upper_outside
Note: Whenever you wish to change Network Interface Card
(NIC) settings, always select auto-negotiate first, then select
a different value if desired. Do not change from one non-auto setting
to another non-auto setting directly; re-negotiation may fail and
In Link Down or Out Link Down appears on the LCD.
|
|
