Showing posts with label Network. Show all posts
Showing posts with label Network. Show all posts

Saturday, October 13, 2012

Cisco Catalyst 2960 Configuration To Support Avaya IP Phone


Configuration of Cisco 2960 Switch When Connected to Avaya IP Phone and PC
Data VLAN = 80
Voice VLAN = 2

Uplink port configuration for Etherchannel & Trunking for between Cisco 2960 to Avaya Switch
interface Port-channel1
switchport trunk allowed vlan 2,80
switchport mode trunk
spanning-tree bpdufilter enable

interface GigabitEthernet1/0/23
switchport trunk allowed vlan 2,80
switchport mode trunk
no cdp enable
channel-group 1 mode on
!
interface GigabitEthernet1/0/24
switchport trunk allowed vlan 2,80
switchport mode trunk
no cdp enable
channel-group 1 mode on

Access port configuration for Avaya IP Phone port
interface GigabitEthernet1/0/33
switchport access vlan 80
switchport mode access
switchport voice vlan 2
speed 100
duplex full
mls qos trust cos
no cdp enable
spanning-tree portfast

Wednesday, December 21, 2011

Cisco Catalyst 4500 Supervisor LED Status Orange And In Continuous Boot Loop

Cisco Cat4500 switch is in boot loop and restart itself in random interval (every 3 hrs, 1hrs, 1day). A check on sup displayed LED status is orange

FRNX4500-CORE#show environment status
Power Fan Inline
Supply Model No Type Status Sensor Status
------ ---------------- --------- ----------- ------- -------
PS1 PWR-C45-1000AC AC 1000W good good n.a.
PS2 PWR-C45-1000AC AC 1000W bad/off bad/off n.a.

Power supplies needed by system : 1
Power supplies currently available : 1

Chassis Type : WS-C4506

Power consumed by backplane : 0 Watts

Supervisor Led Color : Orange

Module 1 Status Led Color : Orange
Module 2 Status Led Color : Green
Module 3 Status Led Color : Green
Module 4 Status Led Color : Green
Module 5 Status Led Color : Green

Fantray : good

A show on diagnostic result demonstrate the sup is in normal state

FRNX4500-CORE#show diagnostic result module 1

module 1:

Overall diagnostic result: PASS

Test results: (. = Pass, F = Fail, U = Untested)

1) supervisor-bootup ---------------> .
2) packet-memory-bootup ------------> .
3) packet-memory-ongoing -----------> U

However, a check on module display power failure issue

Chassis Type : WS-C4506

Power consumed by backplane : 0 Watts

Mod Ports Card Type Model Serial No.
---+-----+--------------------------------------+------------------+-----------
1 2 1000BaseX (GBIC) Supervisor(active) WS-X4013+ JAE********
2 6 1000BaseX (GBIC) WS-X4306-GB JAE********
3 32 10/100BaseTX (RJ45) WS-X4232-RJ-XX JAE********
4 32 10/100BaseTX (RJ45) WS-X4232-RJ-XX JAE********
5 32 10/100BaseTX (RJ45) WS-X4232-RJ-XX JAE********

M MAC addresses Hw Fw Sw Status
--+--------------------------------+---+------------+----------------+---------
1 ****.59e5.1a40 to 0017.59e5.1a41 4.1 12.2(20r)EW1 12.2(18)EW5 Ok
2 ****.9dd4.5276 to 0016.9dd4.527b 4.1 Ok
3 ****.9d1a.4220 to 0016.9d1a.424f 1.9 Ok
4 ****.d742.0260 to 000e.d742.028f 1.9 Ok
5 ****.946a.bf90 to 0017.946a.bfbf 1.9 Ok

System Failures:
----------------
Power Supply: bad/off (see 'show power')

Checked on the Cisco database and confirmed that the amber light is because of bad PEM - Power Module

As for the Boot Loop, show bootvar found that the boot flash is missing. This might due to improper reboot on the switch

FRNX4500-CORE#show bootvar
BOOT variable does not exist
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2101

Assign boot image and change the config register from 0x2101 to 0x2102

FRNX4500-CORE#configure terminal
FRNX4500-CORE(config)#boot system flash bootflash:cat4000-i9s-mz.122-18.EW5.bin
FRNX4500-CORE(config)#config-register 0x2102

Monday, February 07, 2011

Paessler PRTG - Monitoring WMI sensors (Error 80070005)

WMI monitoring often fails with the following error “Connection could not be established (80070005: Access Denied …)”

Basic Steps
- First of all, please check if the correct credentials are used, especially if the hostname is entered in the field “Domain or Computer Name” in PRTG. Please do not leave this field empty!
- Also verify if any firewalls in between PRTG and the target machine(s) may be interfering with connections on port 135.
- The next thing you should try is to configure the PRTG Probe service to run under a domain administrator account. Sometimes the access rights of the System Account under which the PRTG Probe runs by default are not sufficient.

Next options have to be differentiated by the Windows version running on the target machine

Windows XP/2003
- Start the registry editor (regedit)
- Navigate to key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\
- Make sure that “ForceGuest” is set to “0”
- Reboot

Windows Vista/2008 (R2)
- Open the control panel, head to the Windows firewall
- Click on “Change Settings” and then please select the “Exceptions” tab
- Select the check box for “Windows Management Instrumentation (WMI)”
- Open a command prompt (as administrator) and enter the following line to set another firewall group rule
- netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
- Reboot

Windows 7
- Open Windows Firewall
- Click on “Advanced Settings” and then, for both Inbound and Outbound Rules
- Select all checkboxes for “Windows Management Instrumentation”
- Open a command prompt (as administrator) and enter the following line to set another firewall group rule
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
- Reboot

Friday, March 19, 2010

IxChariot High Performance Throughput Script

IxChariot is a test tool for simulating applications and assessing network performance. This script emulates sending a file from Endpoint 1 to Endpoint 2, and getting a confirmation back. The default file size is 100,000 bytes.
Endpoint 1 Endpoint 2
---------- ----------
SLEEP
initial_delay=0
CONNECT_INITIATE CONNECT_ACCEPT
source_port=AUTO destination_port=AUTO
0 0
0 0
LOOP LOOP
number_of_timing_records=100 number_of_timing_records=100
START_TIMER
LOOP LOOP
transactions_per_record=1 transactions_per_record=1
SEND RECEIVE
file_size=10000000 file_size=10000000
send_buffer_size=65535 receive_buffer_size=65535
send_datatype=NOCOMPRESS
send_data_rate=UNLIMITED
CONFIRM_REQUEST CONFIRM_ACKNOWLEDGE
INCREMENT_TRANSACTION
END_LOOP END_LOOP
END_TIMER
SLEEP
transaction_delay=0
END_LOOP END_LOOP
DISCONNECT DISCONNECT
close_type=Reset close_type=Reset

Tuesday, September 01, 2009

BIG-IP Link Controller incorrectly generates an error message when creating a link object

Fresh installation of the BIG-IP Link Controller software, the BIG-IP Link Controller system's mcpd process does not receive the gtmd configuration, although a valid wideip.conf file exists. In addition, attempts to configure a link object will fail with an error message that appears similar to the following example:

010701793: Link (link_name) must have an associated data center

Reload gtmd Configuration
Force the mcpd process to reload the gtmd configuration. To do so, perform the following procedure:

- Log in to the BIG-IP GTM command line.
- Type the following command to reload the configuration: gtmparse -l

[root@furynax:Active] config # gtmparse -1
gtmparse: Initializing ...
/usr/bin/monitors/builtins/gtm_base_monitors.conf: SUCCESS
/usr/local/gtm/include/base_region.ISP: SUCCESS
/config/gtm/wideip.conf: SUCCESS
gtmparse: SUCCESS
[root@furynax:Active] config #

You should now be able to configure the link object.

Manual Configuration on wideip.conf
If you still cannot configure the link object, the BIG-IP Link Controller's auto-configuration process may not have correctly created the wideip.conf file, which contains the required default data center definition that references the box definition for the BIG-IP Link Controller. To ensure that the wideip.conf file contains the required entries, perform the following procedure:

- Log in to the BIG-IP GTM command line.
- Edit the /config/gtm/wideip.conf file in a text editor.
- Ensure that the configuration file contains stanzas that define the data center and the BIG-IP Link Controller object.

For example:

// *** Data Center Definitions (1) ***

datacenter { // 1 server(s)
name "Default DC"
server "LC-fqdn.domain.com"
}

// *** Server Definitions (1) ***

server { // datacenter=Default DC, #VS=0
name "LC-fqdn.domain.com"
type bigip
box { //gtm
address 192.168.1.2
unit_id 1
}
}

Note: Replace LC-fqdn.domain.com with the FQDN of the BIG-IP Link Controller system, and replace 192.168.1.2 with the self IP address that was configured on the BIG-IP Link Controller system during the initial configuration.
- Save and close the file.
- Load the modified configuration by typing the following command: gtmload

[root@furynax:Active] gtm # gtmload
gtmload: Initializing ...
/usr/bin/monitors/builtins/gtm_base_monitors.conf: SUCCESS
/usr/local/gtm/include/base_region.ISP: SUCCESS
/config/gtm/wideip.conf: SUCCESS
gtmload: SUCCESS
[root@furynax:Active] gtm #

Thursday, August 20, 2009

Change iSCSI Client Registry Setting

An iSCSI client on a network experiencing temporary performance issues may lose connection to its virtual resources, causing any applications relying on those resources to crash.

The iSCSI timeout registry settings on the iSCSI client can be changed to be more resistant to temporary network issues.

By default, the Microsoft initiator is able to sustain a network disconnect for up to 60 seconds. Should the network issues last for more than a minute, this can cause issues to the iSCSI client.

To prevent possible influence caused by temporary network outages, the Microsoft iSCSI Registry keys can be altered to extend the disk timeout. Keep in mind that you will need to reboot the machine after modifying the registry key, so it is best to make this registry change during a scheduled maintenance window.

Run regedit and locate the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-xxxxxxxxxxxxxxxx}

This is SCSI and RAID controller class and details can be viewed on the right-hand panel. The key tree can be expanded to reveal additional folders such as 0000, 0001, etc., which are separate adapter instances. Find the one with DriverDesc of Microsoft iSCSI Initiator and navigate to the Parameters folder. On the right hand pane will be several DWORD values such as DelayBetweenReconnect and EnableNOPOut

Change the DWORD value named MaxRequestHoldTime from its default value of 60 to 300 (or from 3c to 12c if the value is in hexadecimal). This change will allow the iSCSI client and its hosted applications to withstand a network outage of up to five minutes.

Determine Replication Throughput Parameter

Two parameters most often used to adjust replication throughput:

Window Size
This is the transport window for the IPStor SAN/IP protocol. The window size is in packets (1500 bytes). The default value is 320, for a window of about 480KB. FalconStor suggests a setting of 1024 for a window of about 1.5 MB. The total window size of data will not actually be sent unless it is generated by outstanding replication commands. Therefore, it doesn't hurt to make this a little larger than necessary.

The following formula can be used to figure out the best possible parameters for window size:

Window-size=Line speed (T1, T3, and OC3)*Latency (millisecond)*1.2(Overhead latency)*2(roundtrip)/1.5

Based on the formula above and a series of tests, we recommend using the default setting for T1 line. It is more than enough to handle even 100ms latency.

For a T3 line, the default setting is also recommended for most cases. If the latency is greater than 50ms, the recommended window-size=1024.

For OC3 line, if the latency is greater than 50ms, the recommended setting will be window-size=4096. However if the latency is greater than 10ms and less than 50ms, the use of such setting may not achieve the best performance. The recommended setting in this case is window-size=640.

Replication-cmdsout
This parameter controls how many outstanding commands are sent by the source IPStor server during replication. The default value is 4. Each command is 64KB in size, so the default is 256 KB of outstanding data. Make sure to specify an appropriate value that keeps the channel full of data.

The following formula can be used to figure out the best possible parameters for replication-cmdsout:

Cmdsout= Line speed (T1, T3, and OC3)*Latency (millisecond)*1.2(Overhead latency)*2(roundtrip)/64

Based on the formula above and a series of tests, we recommend using the default setting for T1 line. It is more than enough to handle even 100ms latency.

For a T3 line, the default setting is also recommended for most cases. If the latency is greater than 50ms, the recommended cmdsout=24.

For OC3 line, if the latency is greater than 50ms, the recommended setting will be cmdsout=84. However if the latency is greater than 10ms and less than 50ms, the use of such setting may not achieve the best performance. The recommended setting in this case is cmdsout=12.

Check the actual window size and replication activity: cat /proc/krudp

The line speed used in the above formulas is MB/s not Mb/s. The latency is one way only. If using the round trip latency, drop the *2 in the formula.

The window size is changed at the server level in the IPStor Console. Right click on the IPStor server name and open the properties window. Under the performance tab, set the window size.

To change the cmdsout, pull down the help menu on the top line bar of the IPStor Console and click ABOUT. Hit the TAB key until the OK button is highlighted. Type sysvar , this will open the system variable window where the replication cmdsout parameter can be adjusted.

Tuesday, August 18, 2009

SmokePing Installation (Ubuntu 9.04)

Install SmokePing
- Open Terminal
- Type sudo su to ensure you have Root priviledges
- Install Smokeping along with some other recommended packages

aptitude install smokeping curl libauthen-radius-perl libnet-ldap-perl libnet-dns-perl libio-socket-ssl-perl libnet-telnet-perl libsocket6-perl libio-socket-inet6-perl apache2

Configure SmokePing
- Smokeping configuration is in the file /etc/smokeping/config
- Modify some files from /etc/smokeping/config.d directory

vi /etc/smokeping/config.d/General
*** General ***

@include /etc/smokeping/config.d/pathnames

# Please edit this to suit your installation
owner = Falko Timme
contact =" me@example.com"
cgiurl =" http://www.example.com/cgi-bin/smokeping.cgi"
mailhost =" smtp.example.com"
syslogfacility =" local0"
concurrentprobes =" no

Make sure that mailhost contains the primary MX for your email domain

vi /etc/smokeping/config.d/Alerts
*** Alerts ***
to = me@example.com
from = smokealert@example.com
[...]

vi /etc/smokeping/config.d/Targets
[...]
remark = Welcome to the SmokePing website of 'Example Company'
[...]

vi /etc/smokeping/config.d/Targets and edit the configuration accordingly
[...]
+ Local

menu = Local
title = Local Network

++ LocalMachine

menu = Local Machine
title = This host
host = localhost

Save your changes and restart Smokeping
/etc/init.d/smokeping restart

Open a web browser and go to http://www.example.com/cgi-bin/smokeping.cgi

Monday, August 17, 2009

Essential Task in Deployment of BIG-IP Link Controller

Create Default Gateway Pool
- Expand Local Traffic and then click Pools
- Click the Create button
- Name box, type the name of the pool (example : site_gateway_pool)
- In New Members section, add IP addresses associated with each router (example: 10.251.25.1 & 10.251.40.1)
- Configure additional options for the pool as needed.
- Click Finished

Implement Default Gateway Pool
- Expand Network and then click Routes
- Click the Add button
- From the Type list, select Default Gateway
- From the Resource section, select Use Pool
- Select the pool name that represents the group of links you want to use as the default gateway pool (site_gateway_pool)
- Click Finished

Configure Links
- Expand Link Controller and click Links
- Click the Create button
- In the Name box, type a name for the link (example: WAN_Link_1)
- In the Router Address box, type the IP address to associate with the link (Example: 10.251.25.1 - IP address assigned to the router that belongs to the LAN interface)
- In the Uplink Address box, type the IP address to associate with the ISP to which outgoing traffic is sent (Example: 202.12.23.60 - Link Controller uses this address to obtain SNMP statistics from the routers WAN interface)
- In the Service Provider box, type the name of the ISP (Example: GITN)
- Select the health monitors
- Click Finished

Configure Listeners (Node Mode or Bridge Mode)
- Expand Link Controller,and then click Listeners
- Click Create
- In the Destination box, type the IP address on which the LC will listen for network traffic (Example : Wide-IP's IP, DNS IP, Asterix)
- From the VLAN Traffic list, select a VLAN setting appropriate for this listener
- Click Finished

Adding Pools
- Expand Local Traffic and then click Pools
- Click Create
- From the Configuration list, select Advanced
- For the Name setting, type a name for the pool
- Click Finished

Adding Virtual Server
- Expand Local Traffic and then click Virtual Servers
- Click Create
- In the Name box, type the name of the virtual server
- Define the destination of the virtual server (Host/Network)
- In the Address box, type the IP address of the virtual server
- In the Service Port option, type the port number that the virtual server uses
- Click Finished

Configure Wide IPs (FQDN mapping to a set of VS that host the domain content)
- Expand Link Controller
- Click Inbound Wide IPs and then Create button
- In the Name box, type a name that identifies the wide IP
- In the TTL box, type the time-to-live value you want to associate with this wide IP
- Select the appropriate load balancing modes (Preferred, Alternate, and Fallback)
- In the Fallback IP box, type the IP address that the LC uses when it cannot load balance inbound traffic
- For the Virtual Server setting, add the virtual servers that belong to this wide IP
- Click Finished

Configure Address Translation
- Expand Local Traffic, and then click SNATs
- Click Create
- In the Name box, type a unique name for the SNAT
- In the Translation box, select IP Address
- Type an IP address in the adjacent box
- Click Finished

Friday, July 10, 2009

Connect Tunnel Fails To Connect

Overview
Connect Tunnel fails to establish a connection to an appliance and displays the following error:

VPN Connection Failed. A connection with the server could not be established.

Resolution
This issue can occur if SSL Version 2.0 alone is enabled in Internet Explorer. Enable both SSL 3.0 and TLS 1.0 support by following these steps:

- Open Internet Explorer
- Click Tools > Internet Options
- Click Advanced > Security
- Under Security select the following checkboxes: Use SSL 3.0 &Use TLS 1.0
- Click OK to save and apply these settings.

Recovering an EX-750 Root Password

This technical note explains how to recover, reset, or restore, the root account password on an SonicWALL / Aventail EX-750 v8.x appliance. It does not apply to the Aventail Management Console (AMC) GUI administrator account passwords.

- Boot the appliance while connected to the serial port.
- Press the "ESC" key. You should see the following displayed:

GRUB loading stage2...

- Press the "ESC" key to enter the menu. NOTE: You must do this quickly.
- You should see a menu similar to the following (varies appliance by appliance):

GRUB version 0.93 (621K lower / 104748K upper memory)
+-------------------------------------------------------------------+
| fsl-purr 2.4.20 (Xda1)
| app 2.4.20_22 (Xda6)
|
|
+-------------------------------------------------------------------+

- One of the above will be highlighted; the highlighted one is your working/production partition. Make a note of it (such as Xda6, Xda7, or Xda8; it should not be Xda1). This will eventually be the root partition you'll edit.
- Using the up/down arrow keys on your keyboard, select:

fsl-purr 2.4.20 (Xda1)

- Press "ENTER" to boot to it.
- You'll see all of the kernel boot information scrolling by and then it may result in a command prompt caused by a failed fsck.
- Press CONTROL-D to continue and you will get to the fsl-purr login prompt.
- Login as root (no password required).
- Previously at the GRUB menu you noted which partition was initially highlighted (it should be Xda6, Xda7, or Xda8). Mount this partition replacing the 'X' with a 'h' (for example Xda6 would be hda6):

mount -t ext3 /dev/hda6 /mnt

- Edit the root password of that partition:
- vi /mnt/etc/shadow
- NOTE: you may also need to set your term type to "VT100" using this command:

export TERM=vt100

- Now replace the following line:

root:x:11753:0:99999:7:::

- With this...
root::11753:0:99999:7:::

- Save the file and then exit by typing this:

:wq

- Unmount the partition (for example for hda6):

umount /dev/hda6

- Reboot:

reboot or shutdown -r now

- Do *not* do anything with GRUB when it reboots. Let it boot automatically. It should boot up on the default partition.
- When the login screen appears, log in as root; no password will be required.
- Immediately change the password using the Linux password change utility. Type and enter:

passwd

- Type the new password. You will be prompted to confirm it. SonicWALL recommends using the password you use for the AMC admin account. If you change the AMC admin account password, the root password will be changed to match.

Thursday, July 09, 2009

Windows Command Tools To Troubleshoot Network Connectivity

arp –a Shows gateway MAC address.
gpresult Starts the Operating System Group Policy Result tool
ipconfig /all Displays the full TCP/IP configuration for all adapters
ipconfig /flushdns Flushes the DNS resolver cache. Helpful when troubleshooting DNS name resolution problems
nbtstat –a [MachineName] Obtains info from WINS or LMHOST (discovers who is logged on)
nbtstst –A [IP] Gets info from WINS or LMHOST (discovers who is logged on)
nbtstat -R Purges and reloads the remote cache name table
nbtstat –n Lists local NetBIOS names.
nbtstat -r Useful for detecting errors when browsing WINS or NetBIOS
netstat -ab The b switch links each used port with its application
netstat -an Shows open ports
netstat -an 1 | find "15868" Locates only lines with the number 15868 and redisplays every one second
netstat -an | find "LISTENING" Shows open ports with LISTENING status
net use Retrieves a list of network connections
net use file://1.2.3.4/ Sees if the machine can poll IP 1.2.3.4
net user Shows user account for the computer
net user /domain Displays user accounts for the domain
net user /domain [UserName] Shows account details for specific user
net group /domain Shows group accounts for the domain
net view Displays domains in the network
net view /domain Specifies computers available in a specific domain
net view /domain:
[DomainName] | more
Shows user accounts from specific domain
net view /cache Shows workstation names
nslookup Looks up IP/hostnames and displays information helpful in diagnosing DNS issues
ping -a [IP] Resolves IP to Hostname
ping -t [IP] Pings host until stopped
set U Shows which user is logged on
set L Shows the logon server
telnet [IP] [port] Confirms whether the port is open

Configure Port Mirroring on H3C S5600

Port mirroring is about copy the packets passing through a port (called a mirroring port) to another port (monitoring port) connected with a monitoring device for packet analysis.

Serial Options

Baud rate : 9600
Data bits : 8
Parity : None
Stop bits :
Flow control : only XON/XOFF is enabled

Create a local mirroring group

[switch] sys
[switch] mirroring-group 1 local

Configure ports GigabitEthernet 1/0/1 and 1/0/2 as mirroring ports and port GigabitEthernet 1/0/3 as monitor port in the mirroring group

[switch] mirroring-group 1 mirroring-port GigabitEthernet 1/0/1 GigabitEthernet 1/0/2 both
[switch] miroring-group 1 monitor-port GigabitEthernet 1/0/3

Display the config of all mirroring groups

[switch] display mirroring-group all
mirroring-group 1:
type : local
status : active
mirroring port :
GigabitEthernet1/0/1 both
GigabitEthernet1/0/2 both
monitor port : GigabitEthernet1/0/3

Tuesday, June 16, 2009

3Com Switch 4200G Quick Start Guide

Accessing the switch via serial
Set Serial Options as listed below :

Port : COM?? ( Run Device Manager and view active COM Port)
Baud rate : 19200
Data bits : 8
Parity : None
Stop bits :
Flow control : DTR/DSR, RTS/CTS and XONXOFF are all disabled

Setting up the Management
Default username : admin
Password : none

Go to config mode
[JB-AccessSwitch]dis cur
#
sysname JB-AccessSwitch
#
igmp-snooping enable
#
queue-scheduler wrr group1 0 1 1 2 2 3 3 4 4 5 5 9 6 13 7 15
#
radius scheme system
#
domain system
#
local-user admin
password simple XXXXX
service-type ssh telnet terminal
level 3
local-user manager
password simple XXXXX
service-type ssh telnet terminal
level 2
local-user monitor
password simple monitor
service-type ssh telnet terminal
level 1
#
vlan 1
igmp-snooping enable
#
interface Vlan-interface1
ip address 10.247.25.9 255.255.255.0
#
ip route-static 0.0.0.0 0.0.0.0 10.247.25.1 preference 60
#
snmp-agent
snmp-agent local-engineid 8000002B0022577BBD806877
snmp-agent community read public
snmp-agent community write private
snmp-agent sys-info contact furynax
snmp-agent sys-info location JohorBharu
snmp-agent sys-info version all

Saving the configuration
[JB-AccessSwitch] save
The configuration will be written to the device.
Are you sure?[Y/N]y
Please input the file name(*.cfg)(To leave the existing filename
unchanged press the enter key):
Now saving current configuration to the device.
Saving configuration. Please wait...
............
Unit1 save configuration flash:/3comoscfg.cfg successfully

[JB-AccessSwitch]
%Apr 2 00:14:12:769 2000 JB-AccessSwitch CFM/3/CFM_LOG:- 1 -Unit1 saved configuration successfully.