- Overview
- Command Line Interface
- Access the Switch Module from the Host Router
- Assign the Switch Module IP Address and Default Gateway
- Cisco IOS Configuration Engine
- Administer the Switch Module
- Switch Module Authentication
- Interface Configuration
- EtherChannel Configuration Between the Switch Module and the Host Router
- Smartports Macros Configuration
- VLAN Configuration
- Private VLAN Configuration
- IEEE 802.1Q and Layer 2 Protocol Tunneling Configuration
- Quality of Service Configuration
- EtherChannel Configuration and Link State Tracking
- MODBUS TCP Configuration
- SDM Template Configuration
- Troubleshooting
- Initial Configuration with the CLI Setup Program
- Cisco IOS File System, Configuration Files, and Software Images
- MODBUS TCP Registers
- Unsupported Commands in Cisco IOS Release 12.2(58)EZ
- Managing the System Time and Date
- Building the Address Table
- MAC Addresses and VLANs
- Default MAC Address Table Configuration
- Changing the Address Aging Time
- Removing Dynamic Address Entries
- Configuring MAC Address Change Notification Traps
- Configuring MAC Address Move Notification Traps
- Configuring MAC Threshold Notification Traps
- Adding and Removing Static Address Entries
- Configuring Unicast MAC Address Filtering
- Disabling MAC Address Learning on a VLAN
- Displaying MAC Address Table Entries
Administer the Switch Module
This chapter describes how to perform one-time operations to administer the CGR 2010 ESM, as well as how to monitor the switch module’s temperature and configure the temperature yellow threshold. This chapter contains the following topics:
Managing the System Time and Date
You can manage the system time and date on your switch module using automatic configuration, such as the Network Time Protocol (NTP), or manual configuration methods.
Note
For complete syntax and usage information for the commands used in this section, see the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2.
These sections contain the following configuration information:
- Understanding the System Clock
- Understanding the Network Time Protocol
- Configuring the Network Time Protocol
- Configuring Time and Date Manually
Understanding the System Clock
The heart of the time service is the system clock. This clock runs from the moment the system starts up and keeps track of the date and time.
The system clock can then be set from these sources:
The system clock can provide time to these services:
The system clock keeps track of time internally based on Universal Time Coordinated (UTC), also known as Greenwich Mean Time (GMT). You can configure information about the local time zone and summer time (daylight saving time) so that the time appears correctly for the local time zone.
The system clock keeps track of whether the time is authoritative or not (that is, whether it has been set by a time source considered to be authoritative). If it is not authoritative, the time is available only for display purposes and is not redistributed. For configuration information, see the “Configuring Time and Date Manually” section.
Understanding the Network Time Protocol
The Network Time Protocol (NTP) is designed to time-synchronize a network of devices. NTP runs over User Datagram Protocol (UDP), which runs over IP. NTP is documented in RFC 1305.
An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP then distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two devices to within a millisecond of one another.
NTP uses the concept of a stratum to describe how many NTP hops away a device is from an authoritative time source. A stratum 1 time server has a radio or atomic clock directly attached, a stratum 2 time server receives its time through NTP from a stratum 1 time server, and so on. A device running NTP automatically chooses as its time source the device with the lowest stratum number with which it communicates through NTP. This strategy effectively builds a self-organizing tree of NTP speakers.
NTP avoids synchronizing to a device whose time might not be accurate by never synchronizing to a device that is not synchronized. NTP also compares the time reported by several devices and does not synchronize to a device whose time is significantly different than the others, even if its stratum is lower.
The communications between devices running NTP (known as associations) are usually statically configured; each device is given the IP address of all devices with which it should form associations. Accurate timekeeping is possible by exchanging NTP messages between each pair of devices with an association. However, in a LAN environment, NTP can be configured to use IP broadcast messages instead. This alternative reduces configuration complexity because each device can simply be configured to send or receive broadcast messages. However, in that case, information flow is one-way only.
The time kept on a device is a critical resource; you should use the security features of NTP to avoid the accidental or malicious setting of an incorrect time. Two mechanisms are available: an access list-based restriction scheme and an encrypted authentication mechanism.
Cisco’s implementation of NTP does not support stratum 1 service; it is not possible to connect to a radio or atomic clock. We recommend that the time service for your network be derived from the public NTP servers available on the IP Internet.
Figure 6-1 shows a typical network example using NTP. Switch A is the NTP master, with Switches B, C, and D configured in NTP server mode, in server association with Switch A. Switch E is configured as an NTP peer to the upstream and downstream switch module, Switch B and Switch F.
Figure 6-1 Typical NTP Network Configuration
If the network is isolated from the Internet, Cisco’s implementation of NTP allows a device to act as if it is synchronized through NTP, when in fact it has learned the time by using other means. Other devices then synchronize to that device through NTP.
When multiple sources of time are available, NTP is always considered to be more authoritative. NTP time overrides the time set by any other method.
Several manufacturers include NTP software for their host systems, and a publicly available version for systems running UNIX and its various derivatives is also available. This software allows host systems to be time-synchronized as well.
Configuring the Network Time Protocol
The switch module does not have a hardware-supported clock and cannot function as an NTP master clock to which peers synchronize themselves when an external NTP source is not available. The switch module also has no hardware support for a calendar. As a result, the ntp update-calendar and the ntp master global configuration commands are not available.
Default NTP Configuration
Table 6-1 shows the default NTP configuration.
|
|
|
|---|---|
Disabled; no interface sends or receives NTP broadcast packets |
|
NTP is enabled on all interfaces by default. All interfaces receive NTP packets.
Configuring NTP Authentication
This procedure must be coordinated with the administrator of the NTP server; the information you configure in this procedure must be matched by the servers used by the switch module to synchronize its time to the NTP server.
Beginning in privileged EXEC mode, follow these steps to authenticate the associations (communications between devices running NTP that provide for accurate timekeeping) with other devices for security purposes:
To disable NTP authentication, use the no ntp authenticate global configuration command. To remove an authentication key, use the no ntp authentication-key number global configuration command. To disable authentication of the identity of a device, use the no ntp trusted-key key-number global configuration command.
This example shows how to configure the switch module to synchronize only to devices providing authentication key 42 in the device’s NTP packets:
Configuring NTP Associations
An NTP association can be a peer association (this switch module can either synchronize to the other device or allow the other device to synchronize to it), or it can be a server association (meaning that only this switch module synchronizes to the other device, and not the other way around).
Beginning in privileged EXEC mode, follow these steps to form an NTP association with another device:
You need to configure only one end of an association; the other device can automatically establish the association. If you are using the default NTP version (Version 3) and NTP synchronization does not occur, try using NTP Version 2. Many NTP servers on the Internet run Version 2.
To remove a peer or server association, use the no ntp peer ip-address or the no ntp server ip-address global configuration command.
This example shows how to configure the switch module to synchronize its system clock with the clock of the peer at IP address 172.16.22.44 using NTP Version 2:
Configuring NTP Broadcast Service
The communications between devices running NTP (known as associations) are usually statically configured; each device is given the IP addresses of all devices with which it should form associations. Accurate timekeeping is possible by exchanging NTP messages between each pair of devices with an association. However, in a LAN environment, NTP can be configured to use IP broadcast messages instead. This alternative reduces configuration complexity because each device can simply be configured to send or receive broadcast messages. However, the information flow is one-way only.
the switch module can send or receive NTP broadcast packets on an interface-by-interface basis if there is an NTP broadcast server, such as a router, broadcasting time information on the network. the switch module can send NTP broadcast packets to a peer so that the peer can synchronize to it. the switch module can also receive NTP broadcast packets to synchronize its own clock. This section provides procedures for both sending and receiving NTP broadcast packets.
Beginning in privileged EXEC mode, follow these steps to configure the switch module to send NTP broadcast packets to peers so that they can synchronize their clock to the switch module:
To disable the interface from sending NTP broadcast packets, use the no ntp broadcast interface configuration command.
This example shows how to configure a port to send NTP Version 2 packets:
Beginning in privileged EXEC mode, follow these steps to configure the switch module to receive NTP broadcast packets from connected peers:
To disable an interface from receiving NTP broadcast packets, use the no ntp broadcast client interface configuration command. To change the estimated round-trip delay to the default, use the no ntp broadcastdelay global configuration command.
This example shows how to configure a port to receive NTP broadcast packets:
Configuring NTP Access Restrictions
You can control NTP access on two levels as described in these sections:
- Creating an Access Group and Assigning a Basic IP Access List
- Disabling NTP Services on a Specific Interface
Creating an Access Group and Assigning a Basic IP Access List
Beginning in privileged EXEC mode, follow these steps to control access to NTP services by using access lists:
The access group keywords are scanned in this order, from least restrictive to most restrictive:
- peer —Allows time requests and NTP control queries and allows the switch module to synchronize itself to a device whose address passes the access list criteria.
- serve —Allows time requests and NTP control queries, but does not allow the switch module to synchronize itself to a device whose address passes the access list criteria.
- serve-only —Allows only time requests from a device whose address passes the access list criteria.
- query-only —Allows only NTP control queries from a device whose address passes the access list criteria.
If the source IP address matches the access lists for more than one access type, the first type is granted. If no access groups are specified, all access types are granted to all devices. If any access groups are specified, only the specified access types are granted.
To remove access control to the switch module NTP services, use the no ntp access-group { query-only | serve-only | serve | peer } global configuration command.
This example shows how to configure the switch module to allow itself to synchronize to a peer from access list 99. However, the switch module restricts access to allow only time requests from access list 42:
Disabling NTP Services on a Specific Interface
NTP services are enabled on all interfaces by default.
Beginning in privileged EXEC mode, follow these steps to disable NTP packets from being received on an interface:
To re-enable receipt of NTP packets on an interface, use the no ntp disable interface configuration command.
Configuring the Source IP Address for NTP Packets
When the switch module sends an NTP packet, the source IP address is normally set to the address of the interface through which the NTP packet is sent. Use the ntp source global configuration command when you want to use a particular source IP address for all NTP packets. The address is taken from the specified interface. This command is useful if the address on an interface cannot be used as the destination for reply packets.
Beginning in privileged EXEC mode, follow these steps to configure a specific interface from which the IP source address is to be taken:
|
|
|
|
|---|---|---|
Specify the interface type and number from which the IP source address is taken. By default, the source address is set by the outgoing interface. |
||
The specified interface is used for the source address for all packets sent to all destinations. If a source address is to be used for a specific association, use the source keyword in the ntp peer or n tp server global configuration command as described in the “Configuring NTP Associations” section.
Displaying the NTP Configuration
You can use two privileged EXEC commands to display NTP information:
For detailed information about the fields in these displays, see the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2.
Configuring Time and Date Manually
If no other source of time is available, you can manually configure the time and date after the system is restarted. The time remains accurate until the next system restart. We recommend that you use manual configuration only as a last resort. If you have an outside source to which the switch module can synchronize, you do not need to manually set the system clock.
Setting the System Clock
If you have an outside source on the network that provides time services, such as an NTP server, you do not need to manually set the system clock.
Beginning in privileged EXEC mode, follow these steps to set the system clock:
|
|
|
|
|---|---|---|
This example shows how to manually set the system clock to 1:30 p.m. on September 30, 2010:
Displaying the Time and Date Configuration
To display the time and date configuration, use the show clock [ detail ] privileged EXEC command.
The system clock keeps an authoritative flag that shows whether the time is authoritative (believed to be accurate). If the system clock has been set by a timing source such as NTP, the flag is set. If the time is not authoritative, it is used only for display purposes. Until the clock is authoritative and the authoritative flag is set, the flag prevents peers from synchronizing to the clock when the peers’ time is invalid.
The symbol that precedes the show clock display has this meaning:
Configuring the Time Zone
Beginning in privileged EXEC mode, follow these steps to manually configure the time zone:
|
|
|
|
|---|---|---|
| The switch module keeps internal time in universal time coordinated (UTC), so this command is used only for display purposes and when the time is manually set: |
||
The minutes-offset variable in the clock timezone global configuration command is available for those cases where a local time zone is a percentage of an hour different from UTC. For example, the time zone for some sections of Atlantic Canada (AST) is UTC-3.5, where the 3 means 3 hours and.5 means 50 percent. In this case, the necessary command is clock timezone AST -3 30.
To set the time to UTC, use the no clock timezone global configuration command.
Configuring Summer Time (Daylight Saving Time)
Beginning in privileged EXEC mode, follow these steps to configure summer time (daylight saving time) in areas where it starts and ends on a particular day of the week each year:
The first part of the clock summer-time global configuration command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the southern hemisphere.
This example shows how to specify that summer time starts on the first Sunday in June at 02:00 and ends on the last Sunday in September at 02:00:
Beginning in privileged EXEC mode, follow these steps if summer time in your area does not follow a recurring pattern (configure the exact date and time of the next summer time events):
The first part of the clock summer-time global configuration command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the southern hemisphere.
To disable summer time, use the no clock summer-time global configuration command.
This example shows how to set summer time to start on June 20, 2010, at 02:00, and end on September 23, 2010, at 02:00:
Configuring a System Name and Prompt
You configure the system name on the switch module to identify it. By default, the system name and prompt are Switch.
If you have not configured a system prompt, the first 20 characters of the system name are used as the system prompt. A greater-than symbol ( >) is appended. The prompt is updated whenever the system name changes.
For complete syntax and usage information for the commands used in this section, see the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 and the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2.
These sections contain this configuration information:
Default System Name and Prompt Configuration
The default switch module system name and prompt is Switch .
Configuring a System Name
Beginning in privileged EXEC mode, follow these steps to manually configure a system name:
When you set the system name, it is also used as the system prompt. To return to the default hostname, use the no hostname global configuration command.
Understanding DNS
The DNS protocol controls the Domain Name System (DNS), a distributed database with which you can map hostnames to IP addresses. When you configure DNS on your switch module, you can substitute the hostname for the IP address with all IP commands, such as ping, telnet, connect, and related Telnet support operations.
IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain. Domain names are pieced together with periods (.) as the delimiting characters. For example, Cisco Systems is a commercial organization that IP identifies by a com domain name, so its domain name is cisco.com. A specific device in this domain, for example, the File Transfer Protocol (FTP) system is identified as ftp.cisco.com.
To keep track of domain names, IP has defined the concept of a domain name server, which holds a cache (or database) of names mapped to IP addresses. To map domain names to IP addresses, you must first identify the hostnames, specify the name server that is present on your network, and enable the DNS.
Default DNS Configuration
Table 6-2 shows the default DNS configuration.
|
|
|
|---|---|
Setting Up DNS
Beginning in privileged EXEC mode, follow these steps to set up your switch module to use the DNS:
If you use the switch module IP address as its hostname, the IP address is used and no DNS query occurs. If you configure a hostname that contains no periods (.), a period followed by the default domain name is appended to the hostname before the DNS query is made to map the name to an IP address. The default domain name is the value set by the ip domain-name global configuration command. If there is a period (.) in the hostname, the Cisco IOS software looks up the IP address without appending any default domain name to the hostname.
To remove a domain name, use the no ip domain-name name global configuration command. To remove a name server address, use the no ip name-server server-address global configuration command. To disable DNS on the switch module, use the no ip domain-lookup global configuration command.
Displaying the DNS Configuration
To display the DNS configuration information, use the show running-config privileged EXEC command.
Creating a Banner
You can configure a message-of-the-day (MOTD) and a login banner. The MOTD banner displays on all connected terminals at login and is useful for sending messages that affect all network users (such as impending system shutdowns).
The login banner also displays on all connected terminals. It appears after the MOTD banner and before the login prompts.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2.
These sections contain this configuration information:
- Default Banner Configuration
- Configuring a Message-of-the-Day Login Banner
- Configuring a Login Banner
Default Banner Configuration
The message of the day and login banners are not configured by default.
Configuring a Message-of-the-Day Login Banner
You can create a single or multiline message banner that appears on the screen when someone logs in to the switch module.
Beginning in privileged EXEC mode, follow these steps to configure a message of the day login banner:
To delete the message of the day banner, use the no banner motd global configuration command.
This example shows how to configure a message of the day banner for the switch module by using the pound sign (#) symbol as the beginning and ending delimiter:
This example shows the banner that appears from the previous configuration:
Configuring a Login Banner
You can configure a login banner to be displayed on all connected terminals. This banner appears after the message of the day banner banner and before the login prompt.
Beginning in privileged EXEC mode, follow these steps to configure a login banner:
To delete the login banner, use the no banner login global configuration command.
This example shows how to configure a login banner for the switch module by using the dollar sign ($) symbol as the beginning and ending delimiter:
Monitoring Temperature and Configuring the Yellow Threshold
The CGR 2010 ESM includes sensors that measure and monitor the status and internal temperature of critical components. Internal component temperatures are measured for the central processor, internal components, and interface cards.
The measured temperature is compared to predetermined threshold limits and, if the temperature does not fall within the limits, the information is recorded and a warning sent to the system administrator by means of Simple Network Management Protocol (SNMP) traps until the temperature falls back to its normal range.
- Use the show env temperature status privileged EXEC command to display the current temperature value, state, and thresholds of the switch module’s CPU and Ethernet board (see Table 6-3 below). The temperature value is the temperature in the switch module (not the external temperature). If the temperature exceeds the threshold, a warning message is sent.
- You can configure the yellow threshold level (in Celsius) by using the system env temperature threshold yellow value global configuration command to set the difference between the yellow and red thresholds. You cannot configure the green or red thresholds (see “Configuring the Yellow Threshold” below for details).
Temperature Show Commands
The switch module monitors the temperature conditions to determine the health of the power supplies. The temperature value is the temperature in the switch module (not the external temperature).
Table 6-3 describes the Show commands that monitor the switch module’s temperature:
|
|
|
|---|---|
Configuring the Yellow Threshold
You cannot configure the green and red thresholds but you can configure the yellow threshold.
Use the system env temperature threshold yellow value global configuration command to specify the difference between the yellow and red threshold values and to configure the yellow threshold (in Celsius). The range is 20 to 25. The default value is 20.
For example, if the red threshold is 60º C and you want to configure the yellow threshold as 51º C (a 9º difference), set the 9º difference between the red and yellow thresholds by using the system env temperature threshold yellow 9 command.
Use the no form of this command to return to the default value.
The default yellow thresholds differ for the switch module’s Copper and SFP models (see Table 6-4 ).
|
|
|
|
|---|---|---|
Managing the MAC Address Table
The MAC address table contains address information that the switch module uses to forward traffic between ports. All MAC addresses in the address table are associated with one or more ports. The address table includes these types of addresses:
- Dynamic address: a source MAC address that the switch module learns and then ages when it is not in use.
- Static address: a manually entered unicast address that does not age and that is not lost when the switch module resets.
The address table lists the destination MAC address, the associated VLAN ID, and port number associated with the address and the type (static or dynamic).
Note For complete syntax and usage information for the commands used in this section, see the command reference for this release.
These sections contain this configuration information:
- Building the Address Table
- MAC Addresses and VLANs
- Default MAC Address Table Configuration
- Changing the Address Aging Time
- Removing Dynamic Address Entries
- Configuring MAC Address Change Notification Traps
- Configuring MAC Address Move Notification Traps
- Configuring MAC Threshold Notification Traps
- Adding and Removing Static Address Entries
- Configuring Unicast MAC Address Filtering
- Disabling MAC Address Learning on a VLAN
- Displaying MAC Address Table Entries
Building the Address Table
With multiple MAC addresses supported on all ports, you can connect any port on the switch module to individual workstations, repeaters, switches, routers, or other network devices. The switch module provides dynamic addressing by learning the source address of packets it receives on each port and adding the address and its associated port number to the address table. As stations are added or removed from the network, the switch module updates the address table, adding new dynamic addresses and aging out those that are not in use.
The aging interval is globally configured. However, the switch module maintains an address table for each VLAN, and STP can accelerate the aging interval on a per-VLAN basis.
The switch module sends packets between any combination of ports, based on the destination address of the received packet. Using the MAC address table, the switch module forwards the packet only to the port associated with the destination address. If the destination address is on the port that sent the packet, the packet is filtered and not forwarded. the switch module always uses the store-and-forward method: complete packets are stored and checked for errors before transmission.
MAC Addresses and VLANs
All addresses are associated with a VLAN. An address can exist in more than one VLAN and have different destinations in each. Unicast addresses, for example, could be forwarded to port 1 in VLAN 1 and ports 1, 9, and 10 in VLAN 5.
Each VLAN maintains its own logical address table. A known address in one VLAN is unknown in another until it is learned or statically associated with a port in the other VLAN.
When private VLANs are configured, address learning depends on the type of MAC address:
- Dynamic MAC addresses learned in one VLAN of a private VLAN are replicated in the associated VLANs. For example, a MAC address learned in a private-VLAN secondary VLAN is replicated in the primary VLAN.
- Static MAC addresses configured in a primary or secondary VLAN are not replicated in the associated VLANs. When you configure a static MAC address in a private VLAN primary or secondary VLAN, you should also configure the same static MAC address in all associated VLANs.
For more information about private VLANs, see Chapter12, “Private VLAN Configuration”
Customers in a service provider network can tunnel a large number of MAC addresses through the network and fill up the available MAC address table space. You can control MAC address learning on a VLAN and manage the MAC address table space that is available on the switch module by controlling which VLANs, and which ports, can learn MAC addresses.
Before you disable MAC address learning, be sure that you are familiar with the network topology and the switch module system configuration. Disabling MAC address learning on a VLAN could cause flooding in the network. See the “Disabling MAC Address Learning on a VLAN” section for more information.
Default MAC Address Table Configuration
Table 6-5 shows the default MAC address table configuration.
|
|
|
|---|---|
Changing the Address Aging Time
Dynamic addresses are source MAC addresses that the switch module learns and then ages when they are not in use. You can change the aging time setting for all VLANs or for a specified VLAN.
Setting too short an aging time can cause addresses to be prematurely removed from the table. Then when the switch module receives a packet for an unknown destination, it floods the packet to all ports in the same VLAN as the receiving port. This unnecessary flooding can impact performance. Setting too long an aging time can cause the address table to be filled with unused addresses, which prevents new addresses from being learned. Flooding results, which can impact switch module performance.
Beginning in privileged EXEC mode, follow these steps to configure the dynamic address table aging time:
To return to the default value, use the no mac address-table aging-time global configuration command.
Removing Dynamic Address Entries
To remove all dynamic entries, use the clear mac address-table dynamic command in privileged EXEC mode. You can also remove a specific MAC address (clear mac address-table dynamic address mac-address), remove all addresses on the specified physical port or port channel (clear mac address-table dynamic interface interface-id), or remove all addresses on a specified VLAN (clear mac address-table dynamic vlan vlan-id).
To verify that dynamic entries have been removed, use the show mac address-table dynamic privileged EXEC command.
Configuring MAC Address Change Notification Traps
MAC address change notification tracks users on a network by storing the MAC address change activity. When the switch module learns or removes a MAC address, an SNMP notification trap can be sent to the NMS. If you have many users coming and going from the network, you can set a trap-interval time to bundle the notification traps to reduce network traffic. The MAC notification history table stores MAC address activity for each port for which the trap is set. MAC address change notifications are generated for dynamic and secure MAC addresses. Notifications are not generated for self addresses, multicast addresses, or other static addresses.
Beginning in privileged EXEC mode, follow these steps to configure the switch module to send MAC address change notification traps to an NMS host:
To disable MAC address-change notification traps, use the no snmp-server enable traps mac-notification change global configuration command. To disable the MAC address-change notification traps on a specific interface, use the no snmp trap mac-notification change { added | removed } interface configuration command. To disable the MAC address-change notification feature, use the no mac address-table notification change global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the switch module to send MAC address notification traps to the NMS, enable the MAC address-change notification feature, set the interval time to 123 seconds, set the history-size to 100 entries, and enable traps whenever a MAC address is added on the specified port.
You can verify your settings by entering the show mac address-table notification change interface and the show mac address-table notification change privileged EXEC commands.
Configuring MAC Address Move Notification Traps
When you configure MAC-move notification, an SNMP notification is generated and sent to the network management system whenever a MAC address moves from one port to another within the same VLAN.
Beginning in privileged EXEC mode, follow these steps to configure the switch module to send MAC address-move notification traps to an NMS host:
To disable MAC address-move notification traps, use the no snmp-server enable traps mac-notification move global configuration command. To disable the MAC address-move notification feature, use the no mac address-table notification mac-move global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the switch module to send MAC address move notification traps to the NMS, enable the MAC address move notification feature, and enable traps when a MAC address moves from one port to another.
You can verify your settings by entering the show mac address-table notification mac-move privileged EXEC commands.
Configuring MAC Threshold Notification Traps
When you configure MAC threshold notification, an SNMP notification is generated and sent to the network management system when a MAC address table threshold limit is reached or exceeded.
Beginning in privileged EXEC mode, follow these steps to configure the switch module to send MAC address table threshold notification traps to an NMS host:
To disable MAC address-threshold notification traps, use the no snmp-server enable traps mac-notification threshold global configuration command. To disable the MAC address-threshold notification feature, use the no mac address-table notification threshold global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the MAC address threshold notification feature, set the interval time to 123 seconds, and set the limit to 78 per cent.
You can verify your settings by entering the show mac address-table notification threshold privileged EXEC commands.
Adding and Removing Static Address Entries
A static address has these characteristics:
- It is manually entered in the address table and must be manually removed.
- It can be a unicast or multicast address.
- It does not age and is retained when the switch module restarts.
You can add and remove static addresses and define the forwarding behavior for them. The forwarding behavior defines how a port that receives a packet forwards it to another port for transmission. Because all ports are associated with at least one VLAN, the switch module acquires the VLAN ID for the address from the ports that you specify. You can specify a different list of destination ports for each source port.
A packet with a static address that arrives on a VLAN where it has not been statically entered is flooded to all ports and not learned.
You add a static address to the address table by specifying the destination MAC unicast address and the VLAN from which it is received. Packets received with this destination address are forwarded to the interface specified with the interface-id option.
When you configure a static MAC address in a private-VLAN primary or secondary VLAN, you should also configure the same static MAC address in all associated VLANs. Static MAC addresses configured in a private-VLAN primary or secondary VLAN are not replicated in the associated VLAN. For more information about private VLANs, see Chapter12, “Private VLAN Configuration”
Beginning in privileged EXEC mode, follow these steps to add a static address:
To remove static entries from the address table, use the no mac address-table static mac-addr vlan vlan-id [ interface interface-id ] global configuration command.
This example shows how to add the static address c2f3.220a.12f4 to the MAC address table. When a packet is received in VLAN 4 with this MAC address as its destination address, the packet is forwarded to the specified port:
Configuring Unicast MAC Address Filtering
When unicast MAC address filtering is enabled, the switch module drops packets with specific source or destination MAC addresses. This feature is disabled by default and only supports unicast static addresses.
Follow these guidelines when using this feature:
- Multicast MAC addresses, broadcast MAC addresses, and router MAC addresses are not supported. If you specify one of these addresses when entering the mac address-table static mac-addr vlan vlan-id drop global configuration command, one of these messages appears:
- Packets that are forwarded to the CPU are also not supported.
- If you add a unicast MAC address as a static address and configure unicast MAC address filtering, the switch module either adds the MAC address as a static address or drops packets with that MAC address, depending on which command was entered last. The second command that you entered overrides the first command.
For example, if you enter the mac address-table static mac-addr vlan vlan-id interface interface-id global configuration command followed by the mac address-table static mac-addr vlan vlan-id drop command, the switch module drops packets with the specified MAC address as a source or destination.
If you enter the mac address-table static mac-addr vlan vlan-id drop global configuration command followed by the mac address-table static mac-addr vlan vlan-id interface interface-id command, the switch module adds the MAC address as a static address.
You enable unicast MAC address filtering and configure the switch module to drop packets with a specific address by specifying the source or destination unicast MAC address and the VLAN from which it is received.
Beginning in privileged EXEC mode, follow these steps to configure the switch module to drop a source or destination unicast static address:
|
|
|
|
|---|---|---|
Enable unicast MAC address filtering and configure the switch module to drop a packet with the specified source or destination unicast static address. |
||
To disable unicast MAC address filtering, use the no mac address -table static mac-addr vlan vlan-id global configuration command.
This example shows how to enable unicast MAC address filtering and to configure the switch module to drop packets that have a source or destination address of c2f3.220a.12f4. When a packet is received in VLAN 4 with this MAC address as its source or destination, the packet is dropped:
Disabling MAC Address Learning on a VLAN
By default, MAC address learning is enabled on all VLANs on the switch module. You can control MAC address learning on a VLAN to manage the available MAC address table space by controlling which VLANs, and which ports, can learn MAC addresses. Before you disable MAC address learning be sure that you are familiar with the network topology and the switch module system configuration. Disabling MAC address learning on a VLAN could cause flooding in the network.
Follow these guidelines when disabling MAC address learning on a VLAN:
- Use caution before disabling MAC address learning on a VLAN with a configured switch module virtual interface (SVI). The switch module then floods all IP packets in the Layer 2 domain.
- You can disable MAC address learning on a single VLAN ID from 1 to 4094 (for example, no mac address-table learning vlan 223) or a range of VLAN IDs, separated by a hyphen or comma (for example, no mac address-table learning vlan 1-10, 15).
- We recommend that you disable MAC address learning only in VLANs with two ports. If you disable MAC address learning on a VLAN with more than two ports, every packet entering the switch module is flooded in that VLAN domain.
- You cannot disable MAC address learning on a VLAN that is used internally by the switch module. If the VLAN ID that you enter is an internal VLAN, the switch module generates an error message and rejects the command. To view internal VLANs in use, enter the show vlan internal usage privileged EXEC command.
- If you disable MAC address learning on a VLAN configured as a private-VLAN primary VLAN, MAC addresses are still learned on the secondary VLAN that belongs to the private VLAN and are then replicated on the primary VLAN. If you disable MAC address learning on the secondary VLAN, but not the primary VLAN of a private VLAN, MAC address learning occurs on the primary VLAN and is replicated on the secondary VLAN.
- You cannot disable MAC address learning on an RSPAN VLAN. The configuration is not allowed.
- If you disable MAC address learning on a VLAN that includes a secure port, MAC address learning is not disabled on that port. If you disable port security, the configured MAC address learning state is enabled.
Beginning in privileged EXEC mode, follow these steps to disable MAC address learning on a VLAN
To reenable MAC address learning on a VLAN, use the default mac address -table learning vlan vlan-id global configuration command. You can also reenable MAC address learning on a VLAN by entering the mac address -table learning vlan vlan-id global configuration command. The first (default) command returns to a default condition and does not appear in the output from the show running-config command. The second command causes the configuration to appear in the show running-config privileged EXEC command display.
This example shows how to disable MAC address learning on VLAN 200:
You can display the MAC address learning status of all VLANs or a specified VLAN by entering the show mac-address-table learning [ vlan vlan-id ] privileged EXEC command.
Displaying MAC Address Table Entries
You can display the MAC address table by using one or more of the privileged EXEC commands described in Table 6-6 :
Managing the ARP Table
To communicate with a device (over Ethernet, for example), the software first must learn the 48-bit MAC address or the local data link address of that device. The process of learning the local data link address from an IP address is called address resolution.
The Address Resolution Protocol (ARP) associates a host IP address with the corresponding media or MAC addresses and the VLAN ID. Using an IP address, ARP finds the associated MAC address. When a MAC address is found, the IP-MAC address association is stored in an ARP cache for rapid retrieval. Then the IP datagram is encapsulated in a link-layer frame and sent over the network. Encapsulation of IP datagrams and ARP requests and replies on 802 networks other than Ethernet is specified by the Subnetwork Access Protocol (SNAP). By default, standard Ethernet-style ARP encapsulation (represented by the arpa keyword) is enabled on the IP interface.
ARP entries added manually to the table do not age and must be manually removed.
For CLI procedures, see Chapter 2, “Command Line Interface” and the Cisco IOS Release 12.2 documentation on Cisco.com.
Feedback