Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Why does log, trap and disable-port not work with meters sometimes?

« Go Back

Information

 
TitleWhy does log, trap and disable-port not work with meters sometimes?
Question
What does the message "Software actions (log, trap, disable port) are not supported for global meters" mean when configuring meters?
(or)
Why does log, trap and disable-port not work with meters sometimes?
Environment
Summit All
Blackdiamond All
EXOS 16.1 and later 
Answer
There are two kinds of meters present in EXOS - system predefined meters and user created meters (global meters).
You can use log, trap and disable-port as actions carried out when the meter encounters out-of-profile packets, using the following command. "Testmeter" is the user created meter.
Example # configure meter testmeter committed-rate 1000 Kbps out-actions drop log trap
Software actions (log, trap, disable port) are not supported for global meters

The above command will work only for system predefined meters which are shown here - 
Example # show meter <tab_key>
<metername>     meter name
    "ingmeter0"   "ingmeter1"   "ingmeter10"  "ingmeter11"  "ingmeter12"
    "ingmeter13"  "ingmeter14"  "ingmeter15"  "ingmeter2"   "ingmeter3"
    "ingmeter4"   "ingmeter5"   "ingmeter6"   "ingmeter7"   "ingmeter8"
    "ingmeter9"   
Even so, you will not be able to configure meters globally and must be done on a per-port basis -
Example # configure meter "ingmeter0" committed-rate 1000 Kbps out-actions drop log trap
Error: Per port meter configuration requires either port-list or port group to be specified. ingmeter0 is a per-port meter.
Therefore, you must specify the port number on the meter when configuring log, trap or disable port -
Example # configure meter "ingmeter0" committed-rate 1000 Kbps out-actions drop log trap ports 1



 
Additional notes
Please note that even when global meters are simply created in EXOS and you try to execute per-port meter configuration, you will encounter the following error -
Example # configure meter "ingmeter0" committed-rate 1000 Kbps out-actions drop log trap ports 1
Error: Hardware does not support per-port meter configuration, while global meters are configured. You must first delete existing global meters.

As the above error states, we must first delete the user-created meter before we use the predefined meter for per-port meter configuration.
 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255