System information

Cisco Cat3K ST 6 June 2012
59
TOE SFRs How the SFR is Met
Command Purpose
show interfaces
status
Displays the status of interfaces, includin
g the
VLANs to which they belongs.
show vlan private-
vlan [type]
Display the private-
VLAN information for the
switch or switch stack.
show interface
switchport
Display private-
VLAN configuration on
interfaces.
show interface
private-vlan
mapping
Display information about the private-
VLAN
mapping for VLAN SVIs.
The following is an example of the output from the show vlan private-vlan
command:
Switch(config)# show vlan private-vlan
Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------
10 501 isolated Gi2/0/1, Gi3/0/1, Gi3/0/2
10 502 community Gi2/0/11, Gi3/0/1, Gi3/0/4
10 503 non-operational
FDP_IFC.1(2) The TOE controls the flow of IP traffic by matching information contained in
the headers of connection-oriented or connection-less IP packets against a set of
rules specified by the authorized administrator in the IP flow control policies.
Within an ACL, the first entry in the ACL that matches the inspected traffic is
the rule that’s applied. ACLs can be applied inbound to an interface and/or
outbound from an interface. All ACLs applicable to a traffic flow through the
TOE applied in the order in which they’re encountered, i.e. any inbound ACL is
applied to the traffic flow when the packet is received (after any Layer 2 VLAN
SFP is applied) and any outbound ACL is applied before the packet is
transmitted. For routed traffic, the outbound interface is determined by the
routing table.
Use of routing protocols specified as permitted in the TOE description (BGPv4,
EIGRP, PIM-SMv2, and OSPFv2) does not interfere with the inspection of
packets and proper enforcement of rules defined in FDP_IFF.1(2). Use of the
routing table is required to determine the proper egress port for IP traffic flows,
and thus which, if any, outbound ACL will be applied to the traffic flow, and
static or dynamic updates to the routing table are expected and consistent with
proper enforcement of traffic flow controls for Layer 3 traffic. Since routing
FDP_IFF.1(2)