Supported Features On The Ethernet Management Port; Layer 3 Routing Configuration Guidelines - Cisco Catalyst 3120 Software Manual

Using the Internal Ethernet Management Port

Supported Features on the Ethernet Management Port

The Ethernet management port supports these features:
•
•
•
•
•
•
•
•
•
•
•
•
•
Caution Before enabling a feature on the Ethernet management port, make sure that the feature is supported. If
you try to configure an unsupported feature on the Ethernet Management port, the feature might not work
properly, and the switch might fail.

Layer 3 Routing Configuration Guidelines

When Layer 3 routing is enabled, you should be aware of these guidelines:
•
•
•
•
•
Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide
10-14
Express Setup (only in switch stacks)
Network Assistant
Telnet with passwords
TFTP
Secure Shell (SSH)
DHCP-based autoconfiguration
SMNP (only the ENTITY-MIB and the IF-MIB)
IP ping
Interface features
– Speed—100 Mb/s (nonconfigurable)
Duplex mode—Full (nonconfigurable)
–
Loopback detection
–
Cisco Discovery Protocol (CDP)
DHCP relay agent
IPv4 and IPv6 access control lists (ACLs)
Routing protocols
If Routing Information Protocol (RIP) or Open Shortest Path First (OSPF) is enabled, RIP or OSPF
advertises routes with the internal Ethernet management port. By default, RIP and OSPF are
disabled.
For traffic to be routed between VLAN 1 and the Ethernet management port, IP routing must be
enabled.
Virtual private network routing and forwarding (VRF) can be used to separate the routing domains
for the Ethernet management port and for data packets.
The default gateway is not available. It is available when IP routing is disabled.
Control packets (such as for routing, CDP, and STP) that are received on the Ethernet management
port might not return to the port. This can occur because the default route of the router uses a router
in the network instead of the device in the network to which the blade switch belongs. The
control-packet source host might not be on the same subnet as the blade switch. To avoid this
problem, use VRF or configure static route to forward the packets to specific hosts and networks.
Chapter 10 Configuring Interface Characteristics
OL-12247-01