I'm not quite sure what you mean exactly.  

Are you not seeing the switch listed when you run a tracert?

Can you provide an example?

No, I have 3 vlans on it all IP'ed and when I run a tracert I don't get a report back when I run a tracert from that switch. it skips and I get a report from the firewall, I like all my switches to report.

So say I have a switch that is 172.16.200.1 IP for VLAN 1 If I traceroute from say a server IP 172.16.100.56

I get

1ms 1ms 1ms 172.16.100.6 (access layer switch)

1ms 1ms 1ms 172.16.252.2 (firewall port)_

So the gateway (distribution layer) 172.16.100.1 switch between the 172.16.100.6 and the 172.16.252.2 does not report back

Are you seeing a response similar to this?

1ms 1ms 1ms 172.16.100.6 (access layer switch)

*       *      *      *      Request timed out.

*       *      *      *      Request timed out.

1ms 1ms 1ms 172.16.252.2 (firewall port)

There is an option to use this command from a windows client

tracert -w 30 xxx.xxx.xxx.xxx

or

tracert -w 60 xxx.xxx.xxx.xxx

This gives each hop a longer period of time to respond.  The ICMP is the lowest priority on the switch and can be disregarded based on the load that the device is carrying at the time of the tracert request.  This may be what you are dealing with.  I'm not sure of a way to make any changes on the switch to get a better response.  

If the switch is busy responding to the needs of the current traffic you may not want to interfere with that process.