CustomExplorerToolbar v1.05 CustomExplorerToolbar is small utility for Windows 7 only, which allows you to easily customize the toolbar of Windows Explorer, and add. In addition to the introduction to warp inside Pandoras Box, we also included texture mapping to the Preview. In short, texture mapping is the way how the texture (i.
Release Notes for the Catalyst 3. C, 2. 96. 0, 2. 96. S, 2. 96. 0- C, and 2. Plus Switches, Cisco IOS Release 1. SE and Later. Limitations and Restrictions. You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software. Cisco IOS Limitations. Unless otherwise noted, these limitations apply to the Catalyst 3. Cisco Ether. Switch service modules: Configuration A static IP address might be removed when the previously acquired DHCP IP address lease expires. This problem occurs under these conditions: – When the switch is booted up without a configuration (no config. When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).– When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires. The workaround is to reconfigure the static IP address. The workaround is to upgrade to Cisco IOS Release 1. EA1. These are the workarounds: 1. Disable auto- Qo. S on the interface. Change the routed port to a nonrouted port or the reverse. Re- enable auto- Qo. S on the interface. The problem is observed only when the switch is receiving frames. The workaround is to configure the port for 1. Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and the peer work correctly. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is manually removed from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file. The new URL might not take effect after the timeout of the old URL. No workaround is necessary; these are the designed behaviors. This is a hardware limitation. However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. Any log entries that are still in the log buffer (have not been output as a system message) on a switch that fails are lost. When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which you entered the command. There is no workaround. There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. The console on the Cisco Ether. Switch service modules only supports three baud rates (9. The switch rejects a CLI command to change the baud rate. To change the baud rate, reload the Cisco Ether. Switch service module with the bootloader prompt. You can then change the baud rate and change the speed on the TTY line of the router connected to the Cisco Ether. Switch Service module console. There is no workaround. The workaround is to configure aggressive UDLD. This does not affect switch functionality. However, the client does not keep trying to download the configuration. The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout- value command. This status depends on when you respond to the reboot query: Would you like to enter the initial configuration dialog?– After a reboot if you wait until the Line Protocol status of VLAN 1 appears on the console before responding, VLAN 1 line status is always shown as down. This is the correct state.– The problem (VLAN 1 reporting up) occurs if you respond to the query before VLAN 1 line status appears on the console. The workaround is to wait for approximately 1 minute after rebooting and until the VLAN 1 interface line status appears on the console before you respond to the query. The workaround is to use the session stack- member- number privileged EXEC command. The workaround is to disable authorization and accounting or to enter the configuration change for one interface at a time. The loss of connectivity occurs between the NIC and Gigabit Ethernet ports on the Cisco Ether. Switch service modules. These are the workarounds: – Contact the NIC vendor, and get the latest driver for the card.– Configure the interface for 1. Mb/s instead of for 1. Mb/s.– Connect the NIC to an interface that is not listed here. If the internal Gigabit Ethernet interface on a Cisco Ether. Switch service module connected to the router is configured as a switch port in access mode or in trunk mode, the internal link is not operational until it reaches the STP forwarding state. Therefore, the Po. E that comes from the host router is also not available until the internal Gigabit Ethernet link reaches the STP forwarding state. This is due to STP convergence time. This problem does not occur on routed ports. If the Cisco Ether. Switch service module is in access mode, the workaround is to enter the spanning- tree portfast interface configuration command on the internal Gigabit Ethernet interface. If the service module is in trunk mode, there is no workaround. Traffic on Ether. Channel ports is not perfectly load- balanced. Egress traffic on Ether. Channel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC. If this happens, uneven traffic distribution will happen on Ether. Channel ports. Changing the load balance distribution method or changing the number of ports in the Ether. Channel can resolve this problem. Use any of these workarounds to improve Ether. Channel load balancing: – for random source- ip and dest- ip traffic, configure load balance method as src- dst- ip– for incrementing source- ip traffic, configure load balance method as src- ip– for incrementing dest- ip traffic, configure load balance method as dst- ip– Configure the number of ports in the Ether. Channel so that the number is equal to a power of 2 (i. For example, with load balance configured as dst- ip with 1. IP addresses, and the number of ports in the Ether. Channel set to either 2, 4, or 8, load distribution is optimal.(CSCeh. Ether. Switch Modules. A duplex mismatch occurs when two Fast Ethernet interfaces that are directly connected on two Ether. Switch service modules are configured as both 1. Mb/s and full duplex and as automatic speed and duplex settings. This is expected behavior for the PHY on the Cisco Ether. Switch service modules. There is no workaround. The workaround is to remove the VLAN from the bridge group or to remove the static MAC address from the VLAN. Non- IP traffic destined to the secure addresses is flooded within the bridge group. The workaround is to disable fallback bridging or to disable port security on all ports in all VLANs participating in fallback bridging. To remove an interface from a bridge group and to remove the bridge group, use the no bridge- group bridge- group interface configuration command. To disable port security on all ports in all VLANs participating in fallback bridging, use the no switchport port- security interface configuration command. The workaround is to ensure that the ports on the standby cluster members are not in the spanning- tree blocking state. To verify that these ports are not in the blocking state, see the “Configuring STP” chapter in the software configuration guide. The workaround is to not set an ARP timeout value lower than 1. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. Because learning is restricted on IEEE 8. No workaround is necessary. The switch grants power only when the maximum wattage configured on the port is less than or equal to the IEEE class maximum. This ensures that the switch power budget is not oversubscribed. There is no such mechanism in Cisco prestandard powered devices. The workaround for networks with pre- standard powered devices is to leave the maximum wattage set at the default value (1. W). You can also configure the maximum wattage for the port for no less than the value the powered device reports as the power consumption through CDP messages. For networks with IEEE Class 0, 3, or 4 devices, do not configure the maximum wattage for the port at less than the default 1. W (1. 5,4. 00 milliwatts). These access points should be discovered as Cisco pre- standard devices. The show power inline user EXEC command shows the access point as an IEEE Class 1 device. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing. Because unnecessary traffic is sent on the trunk port, it reduces the bandwidth of the port. There is no workaround for this problem because non- RPF traffic is continuous in certain topologies. As long as the trunk port is a member of the group in at least one VLAN, this problem occurs for the non- RPF traffic. The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port. This provides reachability to directly connected clients, if any, in the VLAN. The workaround is to not apply a router ACL set to deny access to a VLAN interface. Apply the security through other means; for example, apply VLAN maps to the VLAN instead of using a router ACL for the group. This occurs because the stack master did not have time to propagate the running configuration to all the stack members before it was powered down. This problem might also affect other configuration commands. There is no workaround.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2017
Categories |