> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/ja/sono/troubleshooting/purecanimeraki-radsecgasuru.md).

# PureCA移行後にMeraki RadSec認証が失敗する

#### 症状

* RadSecを使用しているMerakiアクセスポイントが、突然クライアントの認証に失敗する
* RADIUSaaSの設定は何も変更されていない

#### 原因

MerakiはRadSecデバイス証明書をKeeper Organization CAから新しい [PureCAサービス](https://documentation.meraki.com/Wireless/Design_and_Configure/Architecture_and_Best_Practices/Cisco_Keeper_to_PureCA_Migration_Strategy)。PureCA発行の証明書を持つアクセスポイントは、RADIUSaaSでPureCAチェーンが信頼されるまで拒否される。

MerakiではPureCAの最小ファームウェアとしてMR 33.1.2を挙げていますが、それ以前のファームウェアのアクセスポイントがPureCA証明書を提示しているのも確認しています。

#### 解決策

で説明されているように [RadSec PureCA証明書](https://docs.radiusaas.com/configuration/access-point-setup/radsec-available/meraki#radsec-pureca-certificates)。Keeper CAも引き続き信頼済みにしておいてください。両方を並行して信頼できます。

それでも認証に失敗する場合は、設定を次と照らし合わせて確認してください [Meraki RadSecセットアップガイド](https://docs.radiusaas.com/configuration/access-point-setup/radsec-available/meraki) またはサポートにお問い合わせください。お使いのMerakiデバイスの証明書やファームウェアに関するご質問は、Merakiサポートへお問い合わせください。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.radiusaas.com/ja/sono/troubleshooting/purecanimeraki-radsecgasuru.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.