Embedded Ciscoview - Cisco Catalyst 4500 Series Configuration Manual

Release ios xe 3.3.0sg and ios 15.1(1)sg
Hide thumbs Also See for Catalyst 4500 Series:
Table of Contents

Advertisement

Management Features

Embedded CiscoView

A web-based tool to configure the Catalyst 4500 series switch. Embedded CiscoView is a device
management application that can be embedded on the switch flash and provides dynamic status,
monitoring, and configuration information for your switch.
For more information on Embedded CiscoView, see
Embedded Event Manager
Embedded Event Manager (EEM) is a distributed and customized approach to event detection and
recovery offered directly in a Cisco IOS device. EEM offers the ability to monitor events and take
informational, corrective, or any desired EEM action when the monitored events occur or when a
threshold is reached. An EEM policy is an entity that defines an event and the actions to be taken when
that event occurs.
For information on EEM, see the URL:
http://www.cisco.com/en/US/products/ps6815/products_ios_protocol_group_home.html
Ethernet Management Port
The Ethernet management port, also referred to as the Fa1 or fastethernet1 port, is a Layer 3 host port
to which you can connect a PC. You can use the Ethernet management port instead of the switch console
port for network management. When managing a switch stack, connect the PC to the Ethernet
management port on a Catalyst 4500 series switch.
For more information on Ethernet management port, see the "Using the Ethernet Management Port"
section in
File System Management on Supervisor Engine 7-E and Supervisor Engine 7L-E
The format command for IOS XE 3.1.0SG changed slightly compared to the classic IOS format because
the later does not support ext2 format.
For USB flash under IOS XE 3.1.0SG, there are 3 optional formats, i.e. FAT16, FAT32 and EXT2:
Switch# format usb0: ?
FAT16
Software Configuration Guide—Release IOS XE 3.3.0SG and IOS 15.1(1)SG
1-26
To span traffic belonging to specific VRFs on an EVN trunk, configure filter vlan on the SPAN
session with the corresponding VNET tags as vlan_ids and configure VLANs specified in filter
vlan.
To span traffic in specific VRFs on all interfaces, configure vlan as the SPAN source with
VNET tags as vlan_ids and configure VLANs specified as sources.
If cpu is configured as a SPAN source, then transmit packets that will be spanned are tagged by
default. If the encapsulation dot1q option is set on the SPAN session, then the cpu transmitted
packets, which are spanned, are double tagged.
Refer to
Chapter 55, "Configuring SPAN and RSPAN,"
sessions.
Chapter 7, "Configuring Interfaces."
FAT16 filesystem type
Chapter 1
for information on configuring SPAN
Chapter 4, "Administering the Switch."
Product Overview
OL-25340-01

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents