If the cache route stuck on yyy.yyy.yyy.yyy (SENAME002) while it is not assigned for the delivery service, that’s why the client will get 403 rejection when try to download the files.
As workaround, please remove device SENAME001 from the CDSM management, and add it back, this would trigger the cache route to be cleared and updated.
Afterwards we could see the cache route for content http://<OS Domain Name>/<directory>/<filename>.mp4 should be updated to be null, (please note the null is expected in this case because there is only 1 device was assigned to the delivery service)
Now from the clients side the delivery service should start to work fine.
As explained above in troubleshooting steps 3, the 403 was returned to the client’s request was because the clients' request went to device SENAME002 above while it was not assigned to the delivery service
Potential root cause for cache route stuck on SENAME002:
1, The device SENAME002 might be configured as one of the cache engine previously but the device was removed before it was un-offloaded, thus the cache route got stuck
2, There might be some unknown issue for the service router to handle in such situation
Upgrade to a later version of VDS-IS software, 3.3.1 b120 would be recommended
I have successfully registered my SIP endpoints (which we have developed) with Broadsoft sandbox environment. I can make basic calls without problems. When I try to conduct feature tests like Call Waiting (CW), Call Hold (CH), and Call Transfer (CT)...
I am trying to find if there is any Pros or Cons in deploying MPLS with separate customer AS for each site as opposed to one AS. The end goal is to be able to inject default routes from two DCs and be able to make a subset of sites follow one default rout...
So I have attempted the below config: l2vpn
backup disable never
xconnect group Xconns
In one of the discuss, it was initiated to us that there is a specific DB size for example:1 GB and breaching of which will led to crash of Iedge process.I want to replicate the scenario by creating load of user by tool in the lab and track the CDM db uti...
Some 15 years ago we had implemented a PWLAN service by deploying SSG on IOS and Cisco SESM (Subscriber Edge Services Manager) as the web interface (i.e. captive portal). Fast forward, SESM becomes EOL, gets replaced by Broadhop SME. Some years later...