Policies for Session Scheduling and Extension
Policies for session scheduling and extension vary by user group:
- Cisco Users: Cisco employees and contractors. Roughly equivalent to Cisco.com Level 4 access.
- Partner Users: Cisco Partners and Partner Developers with Cisco.com credentials. Roughly equivalent to Cisco.com Level 3 access.
- Standard Users: Everyone with Cisco.com credentials. Roughly equivalent to Cisco.com Level 1 and Level 2 access.
Table 1. Session Scheduling and Extension Policies by User Group
|Session Scheduling and Extension Policy||Cisco Users||Partner Users||Standard Users|
|Self-schedule/self-extend a single session for up to 5 consecutive days||YES||YES||YES|
|Request the scheduling of 6 or more concurrent sessions for up to 5 consecutive days||YES||YES||NO|
|Request the extension of a single session for up to 30 consecutive days||YES||YES||NO|
|Request the scheduling/extension of multiple concurrent sessions for up to 30 consecutive days||YES||NO||NO|
Requests for Session Extensions
Cisco and Partner users must submit requests for session extensions longer than 5 days to Cisco dCloud Support. Support will respond within 48 hours to a request to extend sessions.
For details about submitting a session extension request, refer to Extend a Session Longer than 5 Days.
Limitations and Restrictions for Long-Running Sessions
- To use a session longer than 30 days with all modifications made during the first 30 days, you must save the session before it stops, start a new session using the saved version, and submit an extension request for the new session if you want it active longer than 5 days.
- Planned dCloud downtime may require you to stop, save, and reschedule sessions. Upgrade and maintenance operations planned for a dCloud data center sometimes require that active sessions be stopped. You will be contacted in advance of planned downtime by Cisco dCloud Support if you own sessions that must be stopped.
- To preserve session modifications during dCloud downtime, you must save your active sessions before the downtime starts and then schedule new sessions using the saved versions after dCloud is back online.
- If you schedule new sessions using your saved sessions after dCloud is back online, you must submit a new dCloud Support request to extend any new sessions that must run longer than 5 days.