-
Catalyst 6500 Series Software Configuration Guide, 8.7
-
Catalyst 6500 Series Switch Software Configuration Guide (Full-book PDF)
-
Index
-
Preface
-
Product Overview
-
Command-Line Interfaces
-
Configuring the Switch IP Address and Default Gateway
-
Configuring Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Switching
-
Configuring Ethernet VLAN Trunks
-
Configuring EtherChannel
-
Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling
-
Configuring Spanning Tree
-
Configuring Spanning Tree PortFast, UplinkFast, BackboneFast, and Loop Guard
-
Configuring VTP
-
Configuring VLANs
-
Configuring InterVLAN Routing
-
Configuring CEF for PFC2/PFC3
-
Configuring MLS
-
Configuring Access Control
-
Configuring NDE
-
Configuring GVRP
-
Configuring MVRP
-
Configuring Dynamic Port VLAN Membership with VMPS
-
Checking Status and Connectivity
-
Configuring Online Diagnostics
-
Administering the Switch
-
Configuring Redundancy
-
Configuring NSF with SSO MSFC Redundancy
-
Modifying the Switch Boot Configuration
-
Working with the Flash File System
-
Working with System Software Images
-
Working with Configuration Files
-
Configuring System Message Logging
-
Configuring DNS
-
Configuring CDP
-
Configuring UDLD
-
Configuring DHCP Snooping and IP Source Guard
-
Configuring NTP
-
Configuring Broadcast Suppression
-
Configuring Layer 3 Protocol Filtering
-
Configuring the IP Permit List
-
Configuring Port Security
-
Configuring Switch Access Using AAA
-
Configuring 802.1x Authentication
-
Configuring MAC Authentication Bypass
-
Configuring Web-Based Proxy Authentication
-
Tracking Host Aging
-
Configuring Network Admission Control
-
Configuring Unicast Flood Blocking
-
Configuring SNMP
-
Configuring RMON
-
Configuring SPAN, RSPAN and the Mini Protocol Analyzer
-
Using Switch TopN Reports
-
Configuring Multicast Services
-
Configuring QoS
-
Configuring Automatic QoS
-
Configuring ASLB
-
Configuring the Switch Fabric Module
-
Configuring a VoIP Network
-
Configuring aCEF
-
Configuring MSFC IOS Features
-
Acronyms
-
Table Of Contents
Hardware and Software Requirements
Understanding How a VoIP Network Works
Understanding How CDP and VoIP Work
Configuring Per-Port Power Management
Using show Commands to Display Module Type and Version Information
Setting the Power Mode of a Port or a Group of Ports
Setting the Default Power Allocation
Setting the Inline Power Notification Threshold for a Module
Displaying the Power Status for Modules and Individual Ports
Displaying the Switch Power Environment for Modules
Configuring the Auxiliary VLANs on Catalyst LAN Switches
Understanding the Auxiliary VLANs
Auxiliary VLAN Configuration Guidelines
Configuring the Auxiliary VLANs
Verifying the Auxiliary VLAN Configuration
Disabling the Auxiliary VLANs Until an IP Phone is Detected
Configuring the Access Gateways
Configuring a Port Voice Interface
Displaying a Port Voice Interface Configuration
Displaying the Port Configuration for the Individual Ports
Displaying the Active Call Information
Configuring QoS in the Cisco IP Phone 7960
Understanding How QoS Works in the Cisco IP Phone 7960
Configuring QoS in the Cisco IP Phone 7960
Configuring a Trusted Boundary to Ensure Port Security
QoS and Cisco IP Phone Configuration
QoS, Cisco IP Phone, and PC Configuration
Trusted Boundary Configuration Guidelines
Configuring a Trusted Boundary
Understanding SmartPorts Macros
SmartPorts Guidelines and Restrictions
Detailed SmartPorts Statements
ciscosoftphone Macro Statement
How to Use SmartPorts in Your Network
SmartPorts Enhancements in Software Release 8.4(1)
Ciscorouter SmartPorts Template
Ciscoswitch SmartPorts Template
Ciscodesktop SmartPorts Template
Ciscoipphone SmartPorts Template
Ciscosoftphone SmartPorts Template
Configuring User-Definable SmartPorts Macros
Using the CLI to Configure User-Definable SmartPorts Macros
Configuring a VoIP Network
This chapter describes how to configure a Voice-over-IP (VoIP) network on the Catalyst 6500 series switches.
Note
While this chapter introduces a number of Cisco networking products that are related to VoIP, the primary focus of the chapter is to provide configuration information for integrating the Catalyst 6500 series products into your VoIP network.
Note
This chapter consists of these sections:
•
•
•
Hardware and Software Requirements
The hardware and software requirements for the Catalyst 6500 series switches and Cisco CallManager are as follows:
•
•
•
Understanding How a VoIP Network Works
A telephony system built on an IP network instead of the traditional circuit-switched private branch exchange (PBX) network is called an IP PBX system. (See Figure 55-1.) The system's components are described in these sections:
Figure 55-1 IP PBX System
Cisco IP Phone 7960
The Cisco IP Phone 7960 provides the connectivity to the IP PBX system. The IP phone has two RJ-45 jacks for connecting to the external devices: a LAN-to-phone jack and a PC-to-phone jack. The jacks use either Category 3 or Category 5 unshielded twisted-pair (UTP) cable. The LAN-to-phone jack is used to connect the phone to the LAN using a crossover cable; a workstation or a PC can be connected to the PC-to-phone jack using a straight-through cable.
The inline power is designed to work in cables from Category 3, Category 4, Category 5, and later up to 100 meters. The inline power works with IBM Token Ring STP cable of 100 meters when used with a Token Ring to Fast Ethernet adapter (LanTel Silver Bullet SB-LN/VIP-DATA adapter).
The IP phone is Dynamic Host Configuration Protocol (DHCP) capable. Optionally, you can program the IP phone with a static IP address.
The IP phone can be powered by the following sources:
•
•
•
•
•
•
•
•
•
•
Figure 55-2 shows how to connect the Cisco IP Phone 7960 and PCs to the Catalyst 6500 series switch.
Figure 55-2 Connecting the Cisco IP Phone 7960 to the Catalyst 6500 Series Switch
The examples shown in Figure 55-2 are described in detail as follows:
•
Example 1 shows one IP phone that is connected to the 10/100 port on the Catalyst 6500 series switch. The PC-to-phone jack on the phone is not used. The phone can be powered through the 10/100 port or wall powered.
•
Example 2 shows one PC that is connected to the 10/100 port on the Catalyst 6500 series switch. The PC is wall powered.
•
Example 3 shows one IP phone that is connected to the 10/100 port on the Catalyst 6500 series switch and one PC that is connected to the PC-to-phone jack on the phone. The PC behaves as if it is connected directly to the 10/100 port on the Catalyst 6500 series switch. The phone can be powered through the 10/100 port or wall powered. The PC must be wall powered.
•
Example 4 shows two IP phones that are connected to the 10/100 port on the Catalyst 6500 series switch and one PC that is connected to the PC-to-phone jack on the phone. The PC behaves as if it is connected directly to the 10/100 port on the Catalyst 6500 series switch. The first phone can be powered through the 10/100 port or wall powered. The second phone and the PC must be wall powered.
Note
Cisco CallManager
Cisco CallManager is an open and industry-standard call processing system; its software runs on a Windows NT server and sets up and tears down the calls between the phones, integrating traditional PBX functionality with the corporate IP network. Cisco CallManager manages the components of the IP PBX system, the phones, the access gateways, and the resources for such features as call conferencing and media mixing. Each Cisco CallManager manages the devices within its zone and exchanges information with the Cisco CallManager in charge of another zone to make the calls possible across multiple zones. Cisco CallManager can work with the existing PBX systems to route a call over the Public Switched Telephone Network (PSTN).
Note
Access Gateways
The access gateways allow the IP PBX system to talk to the existing PSTN or PBX systems. The access gateways consist of analog station gateways, analog trunk gateways, digital trunk gateways, and a converged voice gateway.
These sections describe the gateways:
Analog Station Gateway
The Catalyst 6500 series 24-port Foreign Exchange Station (FXS) analog interface module allows the plain old telephone service (POTS) phones and fax machines to connect to the IP PBX network. The analog station gateway behaves like the PSTN side for the POTS equipment. It requires an IP address, is registered with Cisco CallManager in its domain, and is managed by Cisco CallManager.
To configure the analog station interfaces, see the "Configuring VoIP on a Switch" section. The module features are listed in Table 55-1.
Table 55-1 24-Port FXS Analog Interface Module Features
G.711 and G.729 voice encoding
Silence suppression; voice activity detection
Comfort noise generation
Ringer, software programmable frequency and cadence, based on country
DTMF1 detection
Signaling, loop start
Line echo cancellation (32 ms)
Impedance (600 ohms)
Programmable analog gain, signaling timers
Fax pass-through
SPAN2 or port mirroring support
Address signaling formats: In-band DTMF
Signaling formats: Loop start
Ringing tone: Programmable
Ringing voltage: Programmable, based on country
Ringing frequency: Programmable, based on country
Distance: 500-ohms maximum loop
1 DTMF = dual tone multifrequency
2 SPAN = Switched Port Analyzer
Analog Trunk Gateway
The Cisco access analog trunk gateways allow the IP PBX to connect to the PSTN or PBX. The gateway supports up to eight trunks to the PSTN and appears like a phone to the trunk lines coming from the PSTN. Using this gateway, the IP PBX places an IP call through the PSTN. Similar to the analog station gateway, the analog trunk gateway provides line echo cancellation and dual tone multifrequency (DTMF) tone generation and detection. The analog trunk gateway does not provide the ring voltage as it is not connected to the POTS end devices such as the POTS phones or fax machines. The analog trunk gateway requires an IP address, is registered with Cisco CallManager in its domain, and is managed by Cisco CallManager.
To configure the analog trunk gateways, refer to the documentation that shipped with the gateway.
Digital Trunk Gateway
The Catalyst 6500 series 8-port T1/E1 PSTN interface module can support both digital T1/E1 connectivity to the PSTN or transcoding and conferencing. The module requires an IP address, is registered with Cisco CallManager in its domain, and is managed by Cisco CallManager.
The module software is downloaded from a TFTP server. Depending upon which software you download, the ports can serve as the T1/E1 interfaces or the ports support transcoding and conferencing. The transcoding and conferencing functions are mutually exclusive. For every transcoding port in use, one less conferencing port is available and vice versa.
To configure the 8-port T1/E1 PSTN interfaces, see the "Configuring VoIP on a Switch" section. The module features are listed in Table 55-2.
Table 55-2 8-Port T1/E1 PSTN Interface Module Features
G.711 to G.723 and G.729a transcoding (maximum of 8 x 32 channels of transcoding)
Conference bridging, meet-me, and ad-hoc conference modes (maximum of 8 x 16 channels of conferencing)
Comfort noise generation
Fax pass-through
Silence suppression, voice activity detection
Line echo cancellation
Common channel signaling
For T1: 23 DS0 channels for voice traffic; 24th channel is used for signaling
For E1: 29 DS0 channels for voice traffic; 16th channel is reserved for signaling
Any channel can be configured for common channel signaling
ISDN Primary Rate Interface signaling: Each interface supports 23 channels for T1 and 30 channels for E1. The default mode is for the 24th T1 channel or 16th E1 channel to be reserved for signaling. Both network side and user side operation modes are supported.
T1 binary 8-zero substitution/alternate mark inversion (B8ZS/AMI) line coding, u-law or a-law coding
E1 HDB3 line coding
T1 line bit rate: 1.544 Mbps
E1 line bit rate: 2.048 Mbps
T1 line code: AMI, B8ZS
E1 line code: HDB3
Framing format: D4 superframe and extended superframe
FDL1 is a link management protocol that is used to help diagnose problems and gather statistics on T1 lines
1 FDL = Facilities Data Link
Converged Voice Gateway
The Cisco Voice Gateway 200 (VG200) allows you to connect the standard POTS phones (connected directly to the gateway or anywhere on the PSTN) with Cisco IP or any H.323-compliant telephony devices. When used with Cisco CallManager, the VG200 functions as a Media Gateway Control Protocol (MGCP) gateway. The Cisco VG200 provides a 10/100BASE-T Ethernet port for connection to the data network. The following telephony connections are also available:
•
•
•
–
–
–
These ports can be used to integrate a VoIP network with POTS devices, PBXs, or the PSTN.
To configure the Cisco VG200, refer to the documentation that shipped with the gateway.
How a Call Is Made
An IP phone connects to a LAN either through a hub port or a switch port. The IP phone boots up and uses DHCP to get its IP address and the IP address of its TFTP file server. The IP phone uses its IP address to talk to the TFTP server and gets its configuration file. The configuration file includes the IP address of the phone's Cisco CallManager(s). The phone then talks with Cisco CallManager and registers itself. Each time a phone boots up, it might get a different IP address. Cisco CallManager knows how to associate a consistent user phone number to a particular phone by using the MAC address of the phone. Cisco CallManager always maintains a table mapping the phone MAC address and phone number. Each time a phone registers, the table is updated with the new IP address. During the registration, Cisco CallManager downloads the key pad template and the feature capability for the phone. It tells the phone which run-time image it should use. The phone then goes to the TFTP server to get its run-time image. Each phone has a dedicated TCP connection to Cisco CallManager called the control channel. All control information, such as key pressing, goes from the phone to Cisco CallManager through this channel. Instructions to generate ring tone, busy tone, and so on comes from Cisco CallManager to the phone through this channel.
Cisco CallManager stores the IP-address-to-phone-number mapping (and vice versa) in its tables. When a user wants to call another user, the user keys in the called party's phone number. Cisco CallManager translates the phone number to an IP address and generates an IP packet version of the ring tone to the called IP phone through the TCP connection. When the called IP phone receives the packet, it generates a ring tone. When the user picks up the phone, Cisco CallManager instructs the called IP phone to start talking with the calling party and removes itself from the loop. From this point on, the call goes between the two IP phones through the Real-Time Transport Protocol (RTP) which runs over the User Datagram Protocol (UDP). Because the voice packets are sensitive to delays, TCP is not suitable for voice transmission because the timeouts and retries increase the delay between the packets. When any change occurs during the call due to a feature being pressed on one of the phones, or one of the users hanging up or pressing the flash button, the information goes to Cisco CallManager through the control channel.
If a call is made to a number outside of the IP PBX network, Cisco CallManager routes the call to an analog or digital trunk gateway which routes it to the PSTN.
Understanding How VLANs Work
This section describes the native VLANs and the auxiliary VLANs. This section uses the following terminology:
•
•
•
•
Note
Figure 55-3 shows how to connect a Cisco IP Phone 7960 to a Catalyst 6500 series switch.
Figure 55-3 Switch-to-Phone Connections
When the IP phone connects to a 10/100 port on the Catalyst 6500 series switch, the access port (PC-to-phone jack) of the IP phone can be used to connect a PC.
The packets to and from the PC and to and from the phone share the same physical link to the switch and the same port of the switch. The various configurations are shown in the "Cisco IP Phone 7960" section).
Introducing the IP-based phones into the existing switch-based networks raises the following issues:
•
•
You can resolve these issues by isolating the voice traffic onto a separate VLAN on each of the ports that are connected to a phone. The switch port that is configured for connecting a phone would have separate VLANs that are configured for carrying the following:
•
•
Isolating the phones on a separate, auxiliary VLAN increases the quality of the voice traffic and allows a large number of phones to be added to an existing network where there are not enough IP addresses. A new VLAN means a new subnet and a new set of IP addresses.
Understanding How CDP and VoIP Work
Cisco Discovery Protocol (CDP) was enhanced in software release 8.1(1) to facilitate backward compatibility with the newer, higher-powered Cisco IP phones. With this enhanced CDP, a Cisco IP phone can negotiate its power requirements to the switch within the CDP packet. The switch uses this information to ensure that it does not oversubscribe the available power.
We recommend that you enable CDP on the switch so that the switch can correctly detect and supply power to the IP phones that are connected to it. CDP is enabled on the Catalyst 6500 series switches by default; however, you should confirm that CDP is enabled when setting up your VoIP network. For more information on CDP, see Chapter 31, "Configuring CDP."
Configuring VoIP on a Switch
This section describes the command-line interface (CLI) commands and the procedures that are used to configure the Catalyst 6500 series switch for VoIP operation:
•
•
•
•
•
•
Note
Note
Voice-Related CLI Commands
Table 55-3 lists the CLI commands that are described in the configuration procedures.
Table 55-3 Voice-Related CLI Command Module and Platform Support
set port inlinepower
X4
set inlinepower defaultallocation
This is a switch-level command and does not affect the individual modules.
show port inlinepower
X
show environment power
X
X
X
set port auxiliaryvlan
X/X
show port auxiliaryvlan
X/X
set port voice interface
X
X
show port voice interface
X
X
show port voice
X
X
X
show port voice fdl
X
show port voice active
X
X
X
set port qos mod/port cos-ext
set port qos mod/port trust-ext
X/X
show port qos
X/X
1 Ethernet Module = Ethernet switching module with voice daughter card.
2 WS-X6608-T1 and WS-X6608-E1 = 8-port T1/E1 ISDN PRI modules.
3 WS-X6624-FXS = 24-port FXS analog station interface module.
4 X = Command supported on Catalyst 6500 series switch only; XX = Command supported on Catalyst 4500 series, 5000 family, and 6500 series switches. All modules that are listed in Table 55-3 are supported only on Catalyst 6500 series switches.
Configuring Per-Port Power Management
This section describes the per-port power management and the CLI commands that are used to configure power management for IP phones.
Note
Note
For each IP phone that is connected to an Ethernet switching module with a voice daughter card installed, the module allocates part of the available system power to power up and run the phone. You can apply the power on an individual port basis.
Only one IP phone can be powered per port; the phone must be connected directly to the switch port. If a second phone is daisy chained off the phone that is connected to the switch port, the second phone cannot be powered by the switch.
This section describes the following topics:
•
•
•
•
•
•
Using show Commands to Display Module Type and Version Information
To determine if the module has a voice daughter card installed, enter the show module command and look at the "Sub" field. For example, in the following display, the 10/100BASE-TX module in slot 3 has a voice daughter card.
To display the module status and information, perform this task in normal mode:
This example shows a submodule field that provides information about the submodules. The inline power daughter card that is installed on module 3, as shown in the display, is WS-F6K-SVDB-FE, and the inline power daughter card that is installed on module 6, as shown in the display, is WS-F6K-VPWR-GE-TX.
Console> (enable) show moduleMod Slot Ports Module-Type Model Sub Status--- ---- ----- ------------------------- ------------------- --- --------1 1 2 1000BaseX Supervisor WS-X6K-SUP2-2GE yes ok3 3 48 10/100BaseTX Ethernet WS-X6548-RJ-45 yes ok4 4 48 10/100BaseTX Ethernet WS-X6148-RJ45V no ok6 6 48 10/100/1000BaseT Ethernet WS-X6148-GE-TX yes okMod Module-Name Serial-Num--- -------------------- -----------1 SAD04460M9G3 SAD0447099V4 SAD061901FL6 SAD0706025AMod MAC-Address(es) Hw Fw Sw--- -------------------------------------- ------ ---------- -----------------1 00-d0-c0-d4-04-4e to 00-d0-c0-d4-04-4f 1.1 6.1(2) 7.7(0.82-Eng)00-d0-c0-d4-04-4c to 00-d0-c0-d4-04-4d00-02-4a-30-88-00 to 00-02-4a-30-8b-ff3 00-02-b9-ff-eb-70 to 00-02-b9-ff-eb-9f 0.203 6.3(1) 8.2(1)4 00-00-00-00-00-00 to 00-00-00-00-00-2f 1.3 5.4(2) 7.7(0.81)6 00-40-0b-ff-00-00 to 00-40-0b-ff-00-2f 0.304 7.2(1) 8.2(1)Mod Sub-Type Sub-Model Sub-Serial Sub-Hw Sub-Sw--- ----------------------- ------------------- ----------- ------ ------1 L3 Switching Engine II WS-F6K-PFC2 SAD044302EA 1.03 IEEE InlinePower Module WS-F6K-FE48-AF sasdfasdf 0.1 8.1(0)6 Inline Power Module WS-F6K-VPWR-GE SAD070700GV 0.201 8.1(0)Console> (enable)To display the module and submodule versions, perform this task in normal mode:
This example shows how to display the module and submodule versions:
Console> (enable) show version 6Mod Port Model Serial # Versions--- ---- ------------------- ----------- --------------------------------------6 48 WS-X6148-GE-TX SAD0706025A Hw :0.304Fw :7.2(1)Sw :8.1(0)WS-F6K-VPWR-GE SAD070700GV Hw :0.201Sw :8.1(0)Console>Power Management Modes
Each port is configured through the CLI, SNMP, or a configuration file to be in one of the following modes. The CLI command is set port inlinepower mod/port {{auto | static | limit} [wattage] | off}.
•
•
•
•
•
Each port also has a status that is defined as one of the following:
•
•
•
•
•
These sections provide the information on the IP phone power requirements and management:
Power Requirements
The IP phones may have different power requirements. Table 55-4 lists the power requirements for the different classes of IP phones. The supervisor engine initially calculates the power allocation for each port based on the per-port configuration, classification (IEEE only), and default power. When the correct amount of power is determined from the CDP messaging with the Cisco IP Phone, the supervisor engine reduces or increases the allocated power for any ports that are set to Auto mode. The allocated power is not adjusted for ports that are set to Static mode.
For example, the default allocated power is 7 W for a Cisco IP Phone requiring 6.3 W. The supervisor engine allocates 7 W for the Cisco IP Phone and powers it up. Once the Cisco IP Phone is operational, it sends a CDP message with the actual power requirement to the supervisor engine. The supervisor engine then decreases the allocated power to the required amount if the port is set to Auto mode. If the port is set to Static mode, the supervisor engine allocates the wattage that you specified. If the port is set to off, the supervisor engine does not allot any power to the port.
Available Power
Table 55-5 lists the available power that can be supplied for each port for the voice daughter cards.
For example, if the powered device requires 6.3 W, then the allotted power for that port using a daughter card with 89 percent efficiency must be 6.3/(0.89) = 7 W. If you are using a voice daughter card with 100 percent efficiency, then the allotted power is 6.3 W.
Wall-Powered Phones
When a wall-powered phone is present on a switching module port, the switching module cannot detect its presence. The supervisor engine discovers the phone through CDP messaging with the port. If the phone supports the inline power (the supervisor engine determines this through CDP), and the mode is set to Auto, Static, or Off, the supervisor engine does not attempt to power on the port. If a power outage occurs, and the mode is set to Auto, the phone loses power, but the switching module discovers the phone and informs the supervisor engine, which then applies the inline power to the phone. If a power outage occurs, and the mode is set to Static, the phone loses power, but the switching module discovers the phone and applies the preallocated inline power to the phone.
Powering Off the Phone
The supervisor engine can turn off power to a specific port by sending a message to the switching module. The power for a port in Auto mode is then added back to the available system power. The power for the ports in Static mode is not added back to the available system power. This situation occurs only when you power off the phone through the CLI or SNMP.
Phone Removal
The switching module informs the supervisor engine if a powered phone is removed using a link-down message. The supervisor engine then adds the allocated power for that port back to the available system power.
In addition, the switching module informs the supervisor engine if an unpowered phone is removed.
Caution
High-Availability Support
To support high availability during a failover from the active supervisor engine to the standby supervisor engine, the per-port power management and phone status information is synchronized between the active and standby supervisor engines.
The information to be synchronized (on a per-port basis) is the presence of a phone, the phone power status (on, off, denied, or faulty), allocated power, device class, device type, device maximum power, and device discovery. The active supervisor engine sends this information to the standby supervisor engine, and the standby supervisor engine updates its internal data structures. When a switchover occurs, the standby supervisor engine allocates the power to the modules and ports from the available power, one module at a time. Once the power for each module has been allocated, the supervisor engine allocates the power to the phones, beginning with the lowest slot number, until all inline powered ports have been either powered on, off, or denied.
Phone Detection Summary
Figure 55-4 shows how the system detects a phone that is connected to a Catalyst 6500 series switch port.
Figure 55-4 Power Detection Summary
Setting the Power Mode of a Port or a Group of Ports
To set the power mode of a port or a group of ports, perform this task in normal mode:
Set the power mode of a port or a group of ports.
set port inlinepower mod/port {[auto | static] [max-wattage] | off}
Note
This example shows how to set the power mode of a port or group of ports:
Console> (enable) set port inlinepower 2/5 offInline power for port 2/5 set to off.Console> (enable) set port inlinepower 2/3-9 auto 800Inline power for ports 2/3-9 set to auto and max-wattage to 800.Console> (enable)Setting the Default Power Allocation
The set inlinepower defaultallocation command is global and only affects Cisco IP phones. The inline power threshold notification generates a syslog message when the inline power usage exceeds the specified threshold. To set the default power allocation, perform this task in privileged mode (the default allocation value is 15400 milliwatts):
Caution
Note
This example shows how to set the default power allocation:
Console> (enable) set inlinepower defaultallocation 9500Default inline power allocation set to 9500 mWatt per applicable port.Console> (enable)Setting the Inline Power Notification Threshold for a Module
Use the set inlinepower notify-threshold command to set a threshold for inline power usage. The threshold is a percentage from 1 through 99, with 99 percent being the default. When the threshold is passed, a syslog and trap (if configured) are generated.
To set the inline power notification threshold for a module, perform this task in privileged mode:
Set the inline power notification threshold for a module.
set inlinepower notify-threshold {percentage value} module {mod_num}
This example shows how to set the inline power notification threshold to 50 for module 4:
Console> (enable) set inlinepower notify-threshold 50 mod 4Module 4 inlinepower notify-threshold is set to 50%.Console> (enable)Displaying the Power Status for Modules and Individual Ports
To display the power status for the modules and individual ports, perform this task in normal mode:
Display the power status for the modules and individual ports.
show port inlinepower [mod[/port]] [detail]
This example shows how to display the power status for the modules and individual ports:
Console> show port inlinepower 6/1Configured Default Inline Power allocation per port: 15.400 Watts (0.36Amps @42V)Total inline power drawn by module 4: 33.934 Watts ( 0.807 Amps @42V)Port InlinePowered PowerAllocated Device IEEE classFrom PS To PDAdmin Oper mWatts mWatts----- ------ ------ ------- ------- ---------- ----------6/1 auto on 7079 6300 cisco nonePort MaximumPower ActualConsumptionmWatts mWatts----- ------------ -----------------6/1 15400 6300Console>This example shows how to display the detailed power status for the modules and individual ports:
Console> show port inlinepower 4/1 detailConfigured Default Inline Power allocation per port: 15.400 Watts (0.36Amps @42V)Total inline power drawn by module 4: 33.934 Watts ( 0.807 Amps @42V)Port InlinePowered PowerAllocated Device IEEE class DiscoverModeFrom PS To PDAdmin Oper Detected mWatts mWatts----- ------ ------ -------- ------- ------- ---------- ---------- ------------4/1 auto on yes 7079 6300 cisco none ciscoPort MaximumPower ActualConsumption absentCounter OverCurrentmWatts mWatts----- ------------ ----------------- ------------- -----------4/1 15400 6300 0 0Console>Displaying the Switch Power Environment for Modules
To display the switch power environment for the modules, perform this task in privileged mode:
This example shows how to display the switch power environment for the modules:
Console> (enable) show environment power 2Feature not supported on module 2.Console> (enable)Console> (enable) show environment powerPS1 Capacity:1153.32 Watts (27.46 Amps @42V)PS2 Capacity:nonePS Configuration :PS1 and PS2 in Redundant Configuration.Total Power Available:1153.32 Watts (27.46 Amps @42V)Total Power Available for Line Card Usage:1153.32 Watts (27.46 Amps @42V)Total Power Drawn From the System:683.76 Watts (16.28 Amps @42V)Total Inline Power Drawn From the System: 57.54 Watts ( 1.37 Amps @42V)Remaining Power in the System:469.56 Watts (11.18 Amps @42V)Configured Default Inline Power allocation per port:15.400 Watts (0.36 Amps@42V)Slot power Requirement/Usage :Slot Card Type PowerRequested PowerAllocated CardStatusWatts A @42V Watts A @42V---- ------------------- ------- ------ ------- ------ ----------1 WS-X6K-SUP2-2GE 128.52 3.06 128.52 3.06 ok2 0.00 0.00 128.52 3.06 none3 WS-X6548-RJ-45 123.06 2.93 123.06 2.93 ok4 WS-X6148-RJ45V 100.38 2.39 100.38 2.39 ok6 WS-X6148-GE-TX 145.74 3.47 145.74 3.47 okSlot Inline Power Requirement/Usage :Slot CardType Total Allocated Max H/W Supported Max H/WSupportedTo Module (Watts) Per Module (Watts) Per Port (Watts)---- ------------------- ----------------- ------------------ ----------------3 WS-X6548-RJ-45 31.08 315.84 15.4006 WS-X6148-GE-TX 26.46 315.84 7.000Console> (enable)A partial-deny status indicates that some module ports are inline powered but not all the ports on the module are inline powered.
Configuring the Auxiliary VLANs on Catalyst LAN Switches
These sections describe how to configure auxiliary VLANs:
•
•
•
•
•
Understanding the Auxiliary VLANs
You can config
