Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
Can I get notified when a vService goes down; which channels are available (SNMP, e-mail, SMS)?
Short answer
Yes. In HTTP and L7 TCP vServices, the status changes of the vService are notified with the vService Status switch in the Load Balancer → Profiles → Notifications profile, and the health changes of the Backend Services with the Backend Service Status switch (Notifications profile). The profile is assigned by checking Notification on the vService and selecting it from the Notification Profiles list. The profile has four channels: E-mail, SMS, SNMP Trap and UI Notification; E-mail Settings for e-mail and SNMP Settings for SNMP are configured beforehand. In the preset Default Profile that comes when Notification is checked, no channel is on; for this reason, a profile with at least one channel on must be created and selected.
Problem: Nobody Is Notified When the Service Stops
When all the Backend Services of a vService go down or the vService cannot start, this is noticed only through user complaints. Status changes are to be notified to the team immediately by e-mail, SMS or SNMP.
Solution: Two Methods
The two methods create the same Notifications profile; one is done from the interface, the other from the command line.
| Your situation | Suitable method |
|---|---|
| vService and Backend Service status notifications from the interface | Method 1: Notifications profile |
| From the command line | Method 2: WEB-CLI |
Method 1: Notifications Profile Recommended
- How it works The profile monitors the events of the switches that are on and sends them through the channels that are on; the notifications sent are also written to Notification Logs.
- Where it is openedLoad Balancer → Profiles → Notifications
- Requirement E-mail Settings (SMTP) for e-mail, SNMP Settings for SNMP trap
- vService type HTTP · L7 TCP (there is no Notification option in a Network vService)
Step-by-Step Configuration
1
Adım 1 Open the e-mail settings (if E-mail is to be used)
On the Settings → General Settings → Notification Management screen, the E-mail Settings tab is opened and Edit is clicked (E-mail Settings edit form).
2
Adım 2 Enter the SMTP details
Route Table (the route table through which the SMTP server is reached), Host Device, Port, Authentication (if turned on, Username and Password), Security (default TLS) and Sender Address are entered (E-mail Settings edit form).
3
Adım 3 Send a test e-mail
A recipient is written in the address field at the bottom of the form and Test e-mail Settings is clicked (Test e-mail Settings).
4
Adım 4 Save the e-mail settings
Save e-mail Settings is clicked.
5
Adım 5 Open the SNMP settings (if SNMP trap is to be used)
In the SNMP Settings tab of the same screen, Edit is clicked (SNMP Settings edit form).
6
Adım 6 Enter the SNMP target
Route Table (the route table through which the NMS server is reached) is selected; SNMP Version = v1 or v2c is selected; SNMP Community Name (public if empty) and SNMP IP:Port are entered.
7
Adım 7 Save the SNMP settings
Save SNMP Settings is clicked.
8
Adım 8 Open the profile form
The profile form is opened with Load Balancer → Profiles → Notifications → Add (how to add). The form comes filled with the values of the preset profile: vService Status and Backend Service Status are on; the Bandwith (128 Mbps), Request Rate (2500), Current Session (1000) and Number of New Connections (1000) thresholds and Certificate Expiry Notify Days (30) also come filled; all the channels are off.
9
Adım 9 Select the events and channels
Notification Profile Name is entered. vService Status and Backend Service Status are left on; if only status notification is wanted, the threshold fields that come filled are turned off (Can I get notified when a certificate is about to expire or a performance threshold is exceeded?). The required channels are turned on: E-mail (address with +), SMS (number with +), SNMP Trap and UI Notification. If Mute Night Notifications is turned on, only SMS is muted between 22:00 and 08:00.
10
Adım 10 Save the profile
Add in the form is clicked.
11
Adım 11 Open the vService edit form
On the Load Balancer → Load Balancer vService List screen, the vService is right-clicked and Edit is selected (how to add to a vService).
12
Adım 12 Check Notification and select the profile
In the Details panel, Notification is checked. In the Notification Profiles list, the preset Default Profile comes selected first; this selection is removed and the created profile is selected. More than one profile can be selected; all of them are applied together.
13
Adım 13 Save
Save is clicked. The progress of applying the change is followed from the sync indicator at the bottom right of the screen. In a cluster setup, the change is also sent to the peer device with the default auto-sync; if Manual Sync Mode is on, it is sent manually with Synchronize.
Verification
1TestTR7 side
One of the Backend Services of a test vService is disabled.
Expected
Backend service status notification through the selected channels2Notification LogsTR7 side
The record is checked on the Settings → System Logs → Notification Logs screen (notification types).
Expected
Notification record and channel resultMethod 2: WEB-CLI
- How it works The Notifications profile is created from the command line and assigned to the vService. On the command line, the status switches are off by default;
trueis written explicitly. - Where it is opened TR7 WEB-CLI →
lb notification - Requirement WEB-CLI access; E-mail Settings and SNMP Settings above for E-mail and SNMP trap
- vService type HTTP · L7 TCP
Step-by-Step Configuration
1
Adım 1 Create the profile
--poolStatus is the vService Status switch in the interface, --serviceStatus is the Backend Service Status switch; --email.0 is the first e-mail address, --snmp is the SNMP trap channel and --ui is the UI notification channel (status notifications, delivery channels):
text
lb notification add name servis-uyarilari --poolStatus true --serviceStatus true --email.0 noc@example.com --snmp true --ui true2
Adım 2 Assign the profile to the vService
It is assigned with the profile name; this command changes the main notification profile of the vService (bound profiles):
text
lb service update id <vService> --notification servis-uyarilariVerification
1Profile assignmentTR7 side
Command: lb service show <vService>
Expected
The profile in the notification field2Notification LogsTR7 side
The record is checked on the Settings → System Logs → Notification Logs screen (notification types).
Expected
Notification record and channel resultCommon Mistakes
- Turning on Notification and leaving it on the Default profile. The preset profile has no channel; the notification is not sent to any channel.
- Expecting e-mail without defining SMTP. E-mail is not sent without configuring E-mail Settings; the result is seen in Notification Logs.
- Selecting v3 as the SNMP version. Notification traps are sent with v1 or v2c; v1 or v2c is selected in SNMP Settings.
- Turning on SNMP trap without filling in SNMP Settings. The trap is sent to the SNMP IP:Port target in SNMP Settings; the SNMP trap channel does not work without configuring SNMP Settings.
- Adding people to Contact groups. Load Balancer notifications use the profile's own e-mail and SMS lists; Contact groups are for device-wide notification profiles.
- Assuming Mute night notifications also mutes e-mail. Only SMS is muted; e-mail, SNMP trap and UI notification continue to be sent.
- Looking for Notification in a Network vService. The Notifications profile is assigned only to HTTP and L7 TCP vServices.
- Deleting the profile. In the vServices that use the deleted profile, notification stops completely; it does not fall back to the preset profile. Before deleting, the Used in tab in the profile's preview is checked.
How it is done in the documentation
