Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

% VRF table-id 0 not activeCompressed configuration

Hi Expert,

I upgraded IOS-XE on 4500E (SUP7L-E) to cat4500e-universalk9.SPA.03.03.00.SG.151-1. I encounter the log when i try to issue write mem commad

% VRF table-id 0 not activeCompressed configuration from 8947 bytes to 2140 bytes[OK]

How about this message? it's serious log? Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: % VRF table-id 0 not activeCompressed configuration

Hi Roger,

This mesage is caused by a new bug (not resolved yet) :

CSCtw93140    On 'wr mem' command noticed "% VRF table-id 0" message

Symptom:

Typing wr mem while using an ipbase or lanbase boot level of IOS-XE causes this message to appear on the console .

Conditions:

No specific condition causes this message to appear other than entering the command.

Workaround:

Currently no workaround exists .

According to the current analysis results on this bug, it is seems to be cosmetic.

Kind Regards,

Ivan

**Please grade this post if you find it useful.

Kind Regards, Ivan Shirshin **Please grade this post if you find it useful.
3 REPLIES
Community Member

% VRF table-id 0 not activeCompressed configuration

Hi Experts,

got the same problem (same HW / SW). Additional there is a temporary high CPU and poor reachability using management port fastEthernet1.

Cisco Employee

Re: % VRF table-id 0 not activeCompressed configuration

Hi Odamis,

This is new bug CSCtw93140, not resolved yet but so far seems to be cosmetic. See above for more details.

Kind Regards,
Ivan

**Please grade this post if you find it useful.

Kind Regards, Ivan Shirshin **Please grade this post if you find it useful.
Cisco Employee

Re: % VRF table-id 0 not activeCompressed configuration

Hi Roger,

This mesage is caused by a new bug (not resolved yet) :

CSCtw93140    On 'wr mem' command noticed "% VRF table-id 0" message

Symptom:

Typing wr mem while using an ipbase or lanbase boot level of IOS-XE causes this message to appear on the console .

Conditions:

No specific condition causes this message to appear other than entering the command.

Workaround:

Currently no workaround exists .

According to the current analysis results on this bug, it is seems to be cosmetic.

Kind Regards,

Ivan

**Please grade this post if you find it useful.

Kind Regards, Ivan Shirshin **Please grade this post if you find it useful.
4730
Views
18
Helpful
3
Replies
CreatePlease to create content