-
Catalyst 6500 Series Software Configuration Guide, 7.6
-
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
-
Configuring MLS
-
Configuring NDE
-
Configuring Access Control
-
Configuring GVRP
-
Configuring Dynamic Port VLAN Membership with VMPS
-
Checking Status and Connectivity
-
Administering the Switch
-
Configuring Switch Access Using AAA
-
Configuring 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 NTP
-
Configuring Broadcast Suppression
-
Configuring Layer 3 Protocol Filtering
-
Configuring the IP Permit List
-
Configuring Port Security
-
Configuring 802.1x Authentication
-
Configuring Unicast Flood Blocking
-
Configuring SNMP
-
Configuring RMON
-
Configuring SPAN and RSPAN
-
Using Switch TopN Reports
-
Configuring Multicast Services
-
Configuring QoS
-
Configuring Automatic QoS
-
Configuring ASLB
-
Configuring the Switch Fabric Module
-
Configuring a VoIP Network
-
Acronyms
-
Table Of Contents
Hardware and Software Requirements
Understanding How a VoIP Network Works
Example 1: Single Cisco IP Phone 7960
Example 3: One Cisco IP Phone 7960 and One PC
Example 4: Two Cisco IP Phone 7960s and One PC
Configuring VoIP on the Switch
Configuring Per-Port Power Management
Using show Commands to Display Module Type and Version Information
Setting the Power Mode of a Port or Group of Ports
Setting the Default Power Allocation
Displaying the Power Status for Modules and Individual Ports
Displaying the Power Status for Modules and Individual Ports
Configuring Auxiliary VLANs on Catalyst LAN Switches
Auxiliary VLAN Configuration Guidelines
Verifying Auxiliary VLAN Configuration
Configuring the Access Gateways
Configuring a Port Voice Interface
Displaying a Port Voice Interface Configuration
Displaying the Port Configuration for Individual Ports
Displaying 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
Configuring a Trusted Boundary
Using Automatic Voice Configuration
Understanding Automatic Voice Configuration Macros
Automatic Voice Configuration—Cisco IP Phone
Automatic Voice Configuration—Cisco Softphone
Automatic Voice Configuration Guidelines and Restrictions
CLI Interface for Automatic Voice Configuration
Detailed Automatic Voice Configuration Statements
ciscoipphone Configuration Statement
ciscosoftphone Configuration Statement
How to Use Automatic Voice Configuration in Your Network
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 related to VoIP, the primary focus of the chapter is to provide configuration information for integrating 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 47-1; the individual components of this system are described in these sections:
Figure 47-1 IP PBX System
Cisco IP Phone 7960
The Cisco IP Phone 7960 provides connectivity to the IP PBX system. The IP phone has two RJ-45 jacks for connecting to 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 IP phone is Dynamic Host Configuration Protocol (DHCP) capable. Optionally, the IP phone can be programmed with a static IP address.
The IP phone can be powered by the following sources:
•
•
•
Examples 1 through 4 in Figure 47-2 show how to connect the Cisco IP Phone 7960 and PCs to the Catalyst 6500 series switch.
Figure 47-2 Connecting the Cisco IP Phone 7960 to the Catalyst 6500 Series Switch
Example 1: Single Cisco IP Phone 7960
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 either the 10/100 port or wall powered.
Example 2: Single PC
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: One Cisco IP Phone 7960 and One PC
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: Two Cisco IP Phone 7960s and One PC
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 calls between phones, integrating traditional PBX functionality with the corporate IP network. Cisco CallManager manages the components of the IP PBX system, the phones, 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 calls possible across multiple zones. Cisco CallManager can work with existing PBX systems to route a call over the Public Switched Telephone Network (PSTN).
Note
Access Gateways
Access gateways allow the IP PBX system to talk to existing PSTN or PBX systems. 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 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 the Switch" section. The module features are listed in Table 47-1.
Table 47-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 passthrough
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
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 ring voltage as it is not connected to POTS end devices such as 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 T1/E1 interfaces or the ports support transcoding and conferencing. 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 the Switch" section. The module features are listed in Table 47-2.
Table 47-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 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 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 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 voice packets are sensitive to delays, TCP is not suitable for voice transmission as timeouts and retries increase the delay between 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 in turn routes it to the PSTN.
Understanding How VLANs Work
This section describes native VLANs and auxiliary VLANs. This section uses the following terminology:
•
•
•
•
Note
Figure 47-3 shows how you can connect a Cisco IP Phone 7960 to a Catalyst 6500 series switch.
Figure 47-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.
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. Various configurations of connecting the phone and the PC are possible (see the "Cisco IP Phone 7960" section).
Introducing IP-based phones into 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 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.
Configuring VoIP on the 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 47-3 lists the CLI commands that are described in the configuration procedures.
Table 47-3 Voice-Related CLI Command Module and Platform Support
set port inlinepower
X4
set inlinepower defaultallocation
X
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 4000, 5000, and 6500 series switches (note that all modules listed in Table 47-3 are supported only on Catalyst 6500 series switches).
Configuring Per-Port Power Management
This section describes 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 the voice daugher card installed, the supervisor engine software allocates part of the available system power to power up and run the phone. The power can be applied 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:
•
•
•
•
•
Using show Commands to Display Module Type and Version Information
To determine if an Ethernet switching 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 8 does not have a voice daughter card, while the module in slot 9 does have a voice daughter card.
To display module status and information, perform this task in normal mode:
This example shows that there is a submodule field that provides information about submodules. The EARL daughter card is treated as a submodule while the Multilayer Switch Feature Card (MSFC) internal router is not treated as a submodule. The model number for the voice daughter card, as shown in the display, is WS-F6K-VPWR.
Console> (enable) show moduleMod Slot Ports Module-Type Model Sub Status--- ---- ----- ------------------------- ------------------- -----------1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok15 1 1 Multilayer Switch Feature WS-F6K-MSFC no ok8 8 48 10/100BaseTX Ethernet WS-X6348-RJ-45 no ok9 9 48 10/100BaseTX Ethernet WS-X6348-RJ-45 yes okMod Module-Name Serial-Num--- ------------------- -----------1 SAD0343605515 SAD034325979 SAD03414268Mod MAC-Address(es) Hw Fw Sw--- -------------------------------------- ------ ------------------------1 00-30-80-f7-a5-06 to 00-30-80-f7-a5-07 1.0 5.2(1) 6.2(0.32-Eng)FTL00-30-80-f7-a5-04 to 00-30-80-f7-a5-0500-30-a3-4a-a0-00 to 00-30-a3-4a-a3-ff15 00-d0-bc-ee-d0-dc to 00-d0-bc-ee-d1-1b 1.2 12.0(3)XE1 12.0(3)XE18 00-d0-c0-c8-83-ac to 00-d0-c0-c8-83-db 1.1 4.2(0.24)V6.1(0.37)FTL9 00-50-3e-7c-43-00 to 00-50-3e-7c-43-2f 0.201 5.3(1)Mod Sub-Type Sub-Model Sub-Serial Sub-Hw--- ----------------------- ------------------- ----------- ------1 L3 Switching Engine WS-F6K-PFC SAD03451187 1.09 Inline Power Module WS-F6K-VPWR 1.0Console> (enable)To display the version of modules and submodules, perform this task in normal mode:
This example shows the version of modules and submodules:
Console> (enable) show version 2Mod Port Model Serial # Versions--- ---- ------------------- ----------- --------------------------------------2 2 WS-X6K-SUP2-2GE SAD04450LF1 Hw : 1.1Fw : 6.1(2)Fw1: 6.1(3)Sw : 6.3(0.62)PANSw1: 6.3(0.62)PANWS-F6K-PFC2 SAD04440HVU Hw : 1.0Console>Power Management Modes
Each port is configured through the CLI, SNMP, or a configuration file to be in one of the following modes (configured through the set port inlinepower CLI command):
•
•
Each port also has a status, defined as one of the following:
•
•
•
•
These sections provide information that is related to IP phone power requirements and management:
Unpowered Phone
When an unpowered phone is discovered on a switching module port, the switching module reports to the supervisor engine that an unpowered phone is present and on which module/port. If the port is configured in Auto mode, the supervisor engine determines if there is enough available system power to allow the switching module to power up and run the phone. If there is sufficient power, the supervisor engine removes the default allocated power that is required by a phone from the total available system power and sends a message to the switching module instructing it to provide power to the port. If there is not enough available power for the phone, the supervisor engine sends a message to the switching module indicating that power is denied to the port.
After power is applied to the port, the supervisor engine monitors the port to ensure that the link comes up. If the link does not come up within 4 seconds, the supervisor engine instructs the switching module to turn off power. The entire cycle is repeated, and the switching module performs discovery and reports to the supervisor engine if a device is present on the port.
Power Requirements
IP phones may have different power requirements. The supervisor engine initially allocates the configured default of 7 W (167 mA at 42 V) to the Cisco IP Phone. 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 example, the default allocated power is 7 W. A Cisco IP Phone requiring 6.3 W is plugged into a port. 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.
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 inline power (the supervisor engine determines this through CDP), and the mode is set to Auto 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 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. That power is then 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), and the amount of power that is consumed by the phone. 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 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 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 47-4 shows how the system detects a phone that is connected to a Catalyst 6500 series switch port.
Figure 47-4 Power Detection Summary
Error Detection and Handling
This section describes how the Catalyst 6500 series switch handles fault detection and errors that are related to per-port power management.
These sections discuss fault detection and power-management error scenarios:
•
•
•
•
•
Device is Powered but Link is Not Up
The supervisor engine detects that the device is powered but the link is not up by setting a timeout when the switching module is directed to power up the device. If the timeout occurs and the supervisor engine has not received a "link up" for the port, this syslog message is displayed:
1999 Jul 14 10:05:58 %SYS-5-PORT_DEVICENOLINK: Device on Port 4/7 powered, no link up.The supervisor engine also directs the switching module to power off the port. The switching module then performs discovery again on the port.
Port is Unable to Provide Inline Power to the Device
The switching module detects if there is a problem providing inline power to the device and reports this problem to the supervisor engine. This syslog message is displayed:
1999 Jul 14 10:05:58 %SYS-5-PORT_INLINEPWRFLTY: Port 4/7 reporting inline power as faulty.Not Enough Available Power to Power the Device
The supervisor engine tracks the available power left in the system and does not power up any ports if no available power remains. This syslog message is displayed:
1999 Jul 14 10:05:58 %SYS-5-PORT_NOPOWERAVAIL: Device on Port 4/7 will remain unpowered.The supervisor engine informs the switching module that power to the port is denied.
Power Supply Configured from Nonredundant to Redundant
Depending upon the number and type of modules in the chassis, you might need to power off some modules to prevent overdrawing power from the power supply. The supervisor engine first powers off and reallocates the power that is supplied by the ports and then starts powering off and reallocating the power that is used by the module.
Power Supply Configured from Redundant to Nonredundant
Once a module that was powered down due to lack of power is powered up and comes online, the module begins discovery on the ports to determine the presence of unpowered connected devices (phones). The module reports discovered devices to the supervisor engine, which then directs the switching module to power up the device (if the port is configured to do so).
For modules that are already powered on but have devices connected that are power denied, the supervisor engine attempts to power on the devices starting with the lowest numbered slot to the highest numbered slot, and from the lowest port number to the highest port number, one module at a time.
Setting the Power Mode of a Port or Group of Ports
To set the power mode of a port or group of ports, perform this task in normal mode:
Set the power mode of a port or group of ports.
set port inlinepower mod/port {off | auto}
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 autoInline power for ports 2/3-9 set to auto.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 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)Displaying the Power Status for Modules and Individual Ports
To display the power status for modules and individual ports, perform this task in normal mode:
Display the power status for modules and individual ports.
show port inlinepower [mod[/port]]
This example shows how to display the power status for modules and individual ports:
Console> show port inlinepower 3/2-6Default Inline Power allocation per port: 9.500 Watts (0.22 Amps @42V)Total inline power drawn by module 3: 0 WattPort InlinePowered PowerAllocatedAdmin Oper Detected mWatt mA @42V----- ----- ------ -------- ----- --------3/2 auto on yes 10.00 0.2503/3 auto on yes 9.8 0.1983/4 auto denied yes 0 03/5 off off no 0 03/6 off off yes 0 0Console> (enable)The Operational (Oper) status field descriptions in the display are as follows:
•
•
•
•
Displaying the Power Status for Modules and Individual Ports
To display the power status for modules and individual ports, perform this task in privileged mode:
Display the power status for modules and individual ports.
show environment power [mod]
This example shows how to display the power status for modules and individual ports:
Console> (enable) show environment power 5Feature not supported on module 5.Console> (enable) show environment power 9Module 9:Default Inline Power allocation per port: 9.500 Watts (0.22 Amps @42V)Total inline power drawn by module 9: 0 WattSlot power Requirement/Usage :Slot Card Type PowerRequested PowerAllocated CardStatusWatts A @42V Watts A @42V---- ------------------- ------- ------ ------- ------ ----------9 WS-X6348 123.06 2.93 123.06 2.93 okDefault Inline Power allocation per port: 9.500 Watts (0.22 Amps @42V)Port InlinePowered PowerAllocatedAdmin Oper Detected mWatt mA @42V----- ----- ------ -------- ----- --------9/1 auto off no 0 09/2 auto off no 0 09/3 auto off no 0 09/4 auto off no 0 09/5 auto off no 0 09/6 auto off no 0 09/7 auto off no 0 09/8 auto off no 0 0.(display text omitted).9/48 auto off no 0 0Console> (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: 289.80 Watts (6.90 Amps @ 42V)Remaining Power in the System: 863.52 Watts (20.56 Amps @42V)Default inline power allocation: 10.5 Watts/port (0.25 Amps @ 42V)Slot power Requirement/Usage :Slot Card-Type Power-Requested Power-Allocated Card-StatusWatts A @ 42V Watts A @ 42V---- ------------------- ------- ------- ------- ------- ------------1 0.00 0.00 126.42 3.01 none2 WS-X6K-SUP1-2GE 138.60 3.30 138.60 3.30 ok3 WS-X6348-RJ-45 114.24 2.72 151.20 3.60 ok5 WS-X6348-RJ-45 109.20 2.60 100.88 2.40 partial-deny6 Unknown 112.98 2.69 0 0 unknown7 WS-X6248-RJ-45 84.84 2.02 0 0 power-bad9 WS-X6416-GE-MT 105.00 2.50 0 0 power-denyConsole> (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 Auxiliary VLANs on Catalyst LAN Switches
These sections describe how to configure auxiliary VLANs:
•
•
•
Understanding Auxiliary VLANs
You can configure switch ports to send CDP packets that instruct an attached Cisco IP Phone 7960 to transmit voice traffic to the switch in these frame types:
•
–
–
Note
•
•
Note
Auxiliary VLAN Configuration Guidelines
This section describes the guidelines for configuring auxiliary VLANs:
•
•
–
–
–
–
•
•
•
Configuring Auxiliary VLANs
To configure auxiliary VLANs, perform this task in privileged mode:
Configure auxiliary VLANs.
set port auxiliaryvlan mod[/ports] {vlan | untagged | dot1p | none}
This example shows how to add voice ports to auxiliary VLANs, specify an encapsulation type, or specify that the VLAN will not send or receive CDP messages with voice-related information:
Console> (enable) set port auxiliaryvlan 2/1-3 222Auxiliaryvlan 222 configuration successful.AuxiliaryVlan AuxVlanStatus Mod/Ports------------- ------------- -------------------------222 active 1/2,2/1-3Console> (enable) set port auxiliaryvlan 5/7 untaggedPort 5/7 allows the connected device send and receive untagged packets and without 802.1p priority.Console> (enable) set port auxiliaryvlan 5/9 dot1pPort 5/9 allows the connected device send and receive packets with 802.1p priority.Console> (enable) set port auxiliaryvlan 5/12 nonePort 5/12 will not allow sending CDP packets with Voice VLAN information.Console> (enable)The default setting is none. Table 47-4 lists the set port auxiliaryvlan command keywords and their descriptions.
Verifying Auxiliary VLAN Configuration
To verify auxiliary VLAN configuration status, perform this task in privileged mode:
Verify auxiliary VLAN configuration status.
show port auxiliaryvlan {vlan | untagged | dot1p | none}
This example shows how to verify auxiliary VLAN configuration status:
Console> show port auxiliaryvlan 123AuxiliaryVlan AuxVlanStatus Mod/Ports------------- ------------- -------------------------222 active 1/2,2/1-3Console>Configuring the Access Gateways
This section describes the commands that are used to configure the following Catalyst 6500 series access gateway modules:
•
•
Configuring a Port Voice Interface
If DHCP is enabled for a port, the port obtains all other configuration information from the TFTP server. When disabling DHCP on a port, you must specify some mandatory parameters as follows:
•
•
To configure a port voice interface for DHCP, TFTP, and DNS servers, perform this task in privileged mode:
These examples show how to configure the port voice interface for DHCP, TFTP, and DNS servers:
Console> (enable) set port voice interface 7/1 dhcp enablePort 7/1 DHCP enabled.
