Cisco 3845 Message Guide - Page 58

no vlan, no switchport, show interfaces trunk

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 58 highlights

PM Messages Chapter 2 Messages and Recovery Procedures Error Message PM-4-INT_VLAN_NOTAVAIL: Failed to allocate internal VLAN in Port Manager. Explanation The port manager did not find any available internal VLAN. Recommended Action Delete some extended-range VLANs created by users, or remove some features (such as routed ports) that require internal VLAN allocation. To delete extended-range VLANs, use the no vlan vlan-id global configuration command. To delete a routed port, use the no switchport interface configuration command. Error Message PM-4-INVALID_HOST_ACCESS_ENTRY: Invalid Host access entry type ([dec]) is received. Explanation An invalid host access entry type was received. The host access entry should be a configured or a dynamic type. [dec] is the entry type that is received. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 1-5. Error Message PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the recommended limit of [dec]. Explanation The total number of individual VLAN ports on the module or switch has exceeded the recommended limit. VLANs can be counted more than once. If VLAN 1 is carried on ten interfaces, it counts as ten VLAN ports. On some platforms, bundling is also ignored for purposes of this count. If eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it counts as eight VLAN ports. [chars] is the module name (for example, switch or the module number), and [dec] is the recommended limit. Recommended Action Reduce the number of trunks and VLANs configured in the module or switch as recommended in [dec]. Enter the show interfaces trunk privileged EXEC command to see the total number of trunks and VLANs. Error Message PM-4-NO_SUBBLOCK: No PM subblock found for [chars]. Explanation The port manager did not find the subblock for this interface. [chars] is the interface name. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 1-5. 2-44 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-44
Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide
OL-23408-01
Chapter 2
Messages and Recovery Procedures
PM Messages
Error Message
PM-4-INT_VLAN_NOTAVAIL: Failed to allocate internal VLAN in Port
Manager.
Explanation
The port manager did not find any available internal VLAN.
Recommended Action
Delete some extended-range VLANs created by users, or remove some features
(such as routed ports) that require internal VLAN allocation. To delete extended-range VLANs, use
the
no vlan
vlan-id
global configuration command. To delete a routed port, use the
no switchport
interface configuration command.
Error Message
PM-4-INVALID_HOST_ACCESS_ENTRY: Invalid Host access entry type ([dec])
is received.
Explanation
An invalid host access entry type was received. The host access entry should be a
configured or a dynamic type. [dec] is the entry type that is received.
Recommended Action
Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still need assistance, open a case with the TAC, or provide
your Cisco technical support representative with your information. For more information about these
online tools and about contacting Cisco, see the
“Error Message Traceback Reports” section on
page 1-5
.
Error Message
PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the
recommended limit of [dec].
Explanation
The total number of individual VLAN ports on the module or switch has exceeded the
recommended limit. VLANs can be counted more than once. If VLAN 1 is carried on ten interfaces,
it counts as ten VLAN ports. On some platforms, bundling is also ignored for purposes of this count.
If eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1,
it counts as eight VLAN ports. [chars] is the module name (for example, switch or the module
number), and [dec] is the recommended limit.
Recommended Action
Reduce the number of trunks and VLANs configured in the module or switch
as recommended in [dec]. Enter the
show interfaces trunk
privileged EXEC command to see the
total number of trunks and VLANs.
Error Message
PM-4-NO_SUBBLOCK: No PM subblock found for [chars].
Explanation
The port manager did not find the subblock for this interface. [chars] is the interface
name.
Recommended Action
Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still need assistance, open a case with the TAC, or provide
your Cisco technical support representative with your information. For more information about these
online tools and about contacting Cisco, see the
“Error Message Traceback Reports” section on
page 1-5
.