Cisco 3845 Message Guide - Page 48

PLATFORM_PBR Messages

Get Cisco 3845 - Security Bundle Router PDF manuals and user guides
UPC - 746320981420
View all Cisco 3845 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 48 highlights

PLATFORM_PBR Messages Chapter 2 Messages and Recovery Procedures PLATFORM_PBR Messages Error Message PLATFORM_PBR-2-NO_RMAP: Cannot create PBR data structures for route-map [chars]. Explanation The policy based routing (PBR) manager could not allocate the internal data structures for this route-map. A likely cause is lack of available memory. [chars] is the route-map. Recommended Action Simplify the configuration so that it requires less memory. Error Message PLATFORM_PBR-3-INSTALL_FAIL: Policy route-map [chars] not installed in hardware. Explanation The PBR manager could not install the complete route-map in hardware, so the packets are forwarded to the CPU for processing. [chars] is the route-map. Recommended Action Simplify route-map configurations. For example, use the same route-map on multiple interfaces. Error Message PLATFORM_PBR-3-NO_LABEL: Cannot allocate label for route-map [chars]. Explanation The PBR manager could not allocate a label for this route-map. As a result, the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing. [chars] is the route-map. Recommended Action Simplify the configuration with label sharing. Use the same route-maps on multiple interfaces, if possible. Error Message PLATFORM_PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for Policy-Based Routing. Explanation The route-map attached to an interface for policy routing contains an action that is not supported. This is a hardware limitation. [chars] is the route-map. Recommended Action Use the route-map map-tag permit global configuration command and the set ip next-hop ip-address route-map configuration command to reconfigure the route map to use only these supported actions. Error Message PLATFORM_PBR-4-CPU_SUPPORTED_ACTION: Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU. Explanation The route-map attached to an interface for policy-based routing contains an action that is not supported in hardware, so the packets are forwarded to the CPU for processing. The route-map actions that invoke this forwarding are set interface, set ip default next-hop, set default interface, or set ip df. [dec] is the action number, and [chars] is the route-map. Recommended Action Use the set ip next-hop ip-address route-map configuration command to reconfigure the route map action to route the packet to the specified next hop. 2-34 Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide OL-23408-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
2-34
Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide
OL-23408-01
Chapter 2
Messages and Recovery Procedures
PLATFORM_PBR Messages
PLATFORM_PBR Messages
Error Message
PLATFORM_PBR-2-NO_RMAP: Cannot create PBR data structures for
route-map [chars].
Explanation
The policy based routing (PBR) manager could not allocate the internal data structures
for this route-map. A likely cause is lack of available memory. [chars] is the route-map.
Recommended Action
Simplify the configuration so that it requires less memory.
Error Message
PLATFORM_PBR-3-INSTALL_FAIL: Policy route-map [chars] not installed in
hardware.
Explanation
The PBR manager could not install the complete route-map in hardware, so the packets
are forwarded to the CPU for processing. [chars] is the route-map.
Recommended Action
Simplify route-map configurations. For example, use the same route-map on
multiple interfaces.
Error Message
PLATFORM_PBR-3-NO_LABEL: Cannot allocate label for route-map [chars].
Explanation
The PBR manager could not allocate a label for this route-map. As a result, the hardware
cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing.
[chars] is the route-map.
Recommended Action
Simplify the configuration with label sharing. Use the same route-maps on
multiple interfaces, if possible.
Error Message
PLATFORM_PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for
Policy-Based Routing.
Explanation
The route-map attached to an interface for policy routing contains an action that is not
supported. This is a hardware limitation. [chars] is the route-map.
Recommended Action
Use the
route-map
map-tag
permit
global configuration command and the
set
ip next-hop
ip-address
route-map configuration command to reconfigure the route map to use only
these supported actions.
Error Message
PLATFORM_PBR-4-CPU_SUPPORTED_ACTION: Set action in sequence [dec] of
route-map [chars] supported by forwarding to CPU.
Explanation
The route-map attached to an interface for policy-based routing contains an action that
is not supported in hardware, so the packets are forwarded to the CPU for processing. The route-map
actions that invoke this forwarding are
set interface
,
set ip default next-hop
,
set default interface
,
or
set ip df
. [dec] is the action number, and [chars] is the route-map.
Recommended Action
Use the
set ip next-hop
ip-address
route-map configuration command to
reconfigure the route map action to route the packet to the specified next hop.