Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How do I schedule maintenance for an interface / port in Smarts SAM? (320495)

Last Updated: 3/22/2024Categories: How toTotal Views: 2498Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

How do I schedule maintenance for an interface / port in Smarts SAM?
Can I schedule maintenance for an interface / port in Smarts SAM without putting the device (Router, Switch and so on) into maintenance mode?

Resolution

This is documented in the SAM Operator Guide (has been place since SAM 8.1)

This is only possible via the bulk maintenance feature and cannot be done via the GUI. The following are the steps prescribed in the doc:

The Schedule Maintenance functionality is available only for classes which belong to the following categories: UnitaryComputerSystem ICIMServiceConnection SoftwareService NetworkConnection  Scheduling bulk maintenance for port and interface components You schedule bulk maintenance for port and interface components by specifying the component   s SystemName, the device instance name, in either a text file or an XML file.  Scheduling bulk maintenance for port and interface components using a text file To schedule bulk maintenance for port and interface components using a text file: 1.Open a text editor. 2.Create a file with the format: ClassName InstanceName startdate startTime enddate endTime SystemName where the: Format for the startdate and enddate values is mm-dd-yyyy and the format for startTime and endTime values is HH::MM. SystemName is the name of the system that hosts the given port or interface. You can obtain the SystemName from the Topology Browser console.

Port and interface objects are not imported into SAM. There is no way to validate these object names in SAM. If an invalid port name or interface name is specified in the bulk maintenance input file, a notification for that element is created, even
though the element is invalid (misnamed).

Hour value is from 023
Minute value is from 059
End date must be later then start date
End time should be later than current time Values are delimited with space characters and comments are added with a pound character at the start of the line. For example, # This is the input file for bulk maintenance for ports and interfaces
# Ports to be scheduled for maintence are Port abc 08-05-2009 16:00 08-05-2009 19:00 router1 3.Save and exit the file. 4.Upload the file into the server. Loading the bulk maintenance text tile on page 127 provides detailed information for uploading the text file to the server. Scheduling bulk maintenance for port and interface components using an XML file To schedule bulk maintenance for port and interface components using an XML file: 1.Open an XML editor. 2.Create a file with the format: <?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE ics_config SYSTEM "ics-config.dtd">
<ics_config version="2">
<maintconfig className = "Port" instanceName = "abc" startYear = "2009"
startMonth = "7"
startDay = "26"
startHour= "10"
startMinute= "00"
endYear = "2009"
endMonth = "7"
endDay = "28"
endHour= "16"
endMinute = "00"
systemName = "router1"/> </ics_config> where the: Hour value is from 023
Minute value is from 059
End date must be later then start date
End time should be later than current time
The port abc resides on router1, and router1 must be in the SAM topology. If router1 is not in the SAM topology, it ignores the entry in the XML file. 3.Save and close the file. 4.Upload the XML file to the server. Loading the bulk maintenance XML file on page 128 provides detailed information on uploading the XML file to the server

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant