
5
PoE Main Status - Stand-alone
-----------------------------------------------------------------------
Available DTE Power: 200 Watts
DTE Power Status: Normal
DTE Power Consumption: 0 Watts
DTE Power Usage Threshold: 80 %
Power Pairs: Spare
Traps Control Status: Enable
PD Detect Type: 802.3af
Power Source Present: AC Only
DC Source Type: BayStack 10
DC Source Configuration: Power Sharing
The “PD Detect Type” is the parameter that must be
changed to support the i2002 and i2004 Phone.
Enter configuration mode in the Command Line
Interface and issue the following command at the CLI
prompt:
poe poe-pd-detect-type 802dot3af_and_legacy
Issuing the 460-24T-PWR>sho poe-main-status
command again will show the following:
460-24T-PWR(config)#sho poe-main-status
PoE Main Status - Stand-alone
--------------------------------------------------
Available DTE Power: 200 Watts
DTE Power Status: Normal
DTE Power Consumption: 2 Watts
DTE Power Usage Threshold: 80 %
Power Pairs: Spare
Traps Control Status: Enable
PD Detect Type: 802.3af and Legacy
Power Source Present: AC Only
DC Source Type: BayStack 10
DC Source Configuration: Power Sharing
Power should now be applied to the phone.
To change the setting for a different unit in a stack,
issue the following command:
poe poe-pd-detect-type unit X 802dot3af_and_legacy
where “X” is the unit number.
NETWORK MANAGEMENT
The Misunderstood Windows Client
The OTM Windows client-server architecture is often
misunderstood. Many make the assumption that the
OTM Windows clients will function as would a
traditional dumb client, assuming that there would be
no impact on the network. But in reality, there are
several databases that reside on the OTM Windows
client and network bandwidth provisioning should be
considered when deploying an OTM server with
Windows clients. The OTM server provides the
database for the common data that is shared with the
clients, so it’s important to ensure adequate
bandwidth between the server and clients. However,
certain functions that are performed on the OTM
Windows client will require a direct connection to the
PBX. Because of this, the OTM Windows clients must
be running at the time of the scheduled event.
As you can see, it is important that OTM is engineered
appropriately prior to deployment.
Some things to remember:
! Station Administration runs primarily on the client
and will only communicate with the server to
obtain common data. When making a station
change on an OTM Windows client, the client
must set up a connection with the PBX to
implement the change. (In a true client-server
architecture, the bulk of the tasks would be
executed by the server connecting directly to the
PBX with minimal processing being done by the
client.)
! Other applications like Maintenance, Inventory, IP
Trunk, IP Line, GCAS/CRS Billing, also operate
primarily on the OTM Windows client with minimal
server involvement, except during the startup of
the application.
! The OTM Telecom Billing System operates
primarily on the client and obtains OTM Directory
information from the server.
! Applications such as Data Buffering and Access
(DBA), LDAP Synchronization, and user group
set-up and configuration will operate entirely on
the server but can also be accessed via a
Windows client.
! In most situations we do not recommend
deployment of OTM Windows clients in a WAN
environment. Specific bandwidth requirements
must be met in order for the OTM Windows clients
to function appropriately. As an alternative for
remote management access, OTM Windows
clients can be positioned throughout the LAN and
accessed remotely using PC Anywhere.
! The Web applications operate on the server and
Kommentare zu diesen Handbüchern