Monday, June 28, 2010

Factory Default Reset for IP phones

If there is only one 7941 phone which is not booting properly and other phones are working fine

then we can try factory resetting of that particular phone

To initiate the factory reset:

Start with the phone in a powered off state.
While holding the "#" key down on the keypad, apply power to the phone.
Keep the "#" key depressed until you see the LEDs on the phone begin a 'walking' sequence, where they walk down from top to bottom.
After you see the LED walk sequence begin, you can release the "#" key and enter one of the reset sequences below. You have to enter the sequence as is, any deviation from the given sequence will abort the factory reset and resume a normal boot sequence.

#Soft Reset

The code for the soft factory reset is: 123456789*0#


A soft reset does the following:

deletes key files on the phone including /etc/init.tab
reboots
phone recovers default loads file from TFTP server

#Total Hard Reset

The code for the total hard reset is: 3491672850*#


A total hard reset formats /flash0 blowing away everything except CNU. All settings and personalization of the phone is removed.


#Hard Reset with Network Setting Preservation

The code for the network preservation hard reset is: *7412369#085


And it also does a complete format of /flash0 - yet it preserves the network settings so that after the format, any static IP and other network settings are preserved. The settings are stored in volatile RAM, so it is important to not remove power to the phone during this process


For CSCsi60439 reference please see document EDCS-609633.


#Prerequisites

There are a number of prerequsites that are necessary for a successful factory reset.

You must have a network environment in which DHCP is used to provide the phone with an IP address and a TFTP server (i.e. DHCP option 150).
There must be an appropriate default load for your phone model on that TFTP server:
The default load name is: termxx.default.loads (where xx is part of the model number, 41 for 7941, 62 for 7962, 70 for 7970, etc.)
The version of the default load must be the same signing type (dev or release) as the phone on which you wish to do a factory reset.
This file (termxx.default.loads) is packaged with every phoneload that is installed on the callmanager, but since the name is not unique per phoneload version, the copy of termxx.default.loads is always the one from the most recent load that was installed on the callmanager. It may not be the type (dev or release) that you want.
How to configure conference/transcoder on CME using DSP

1. enable DSP farm service for a voice card
voice-card 0
dsp service dspfarm

2. configure SCCP for CME
sccp local g0/0 (local interface that SCCP register to CME)
sccp ccm 192.168.1.1 identifier 1 version 4.0
sccp

3. configure SDP farm
dspfarm profile 1 conference
maximum session 4
associate application sccp
dspfarm profile 2 transcoder
maximum session 4
associate application sccp

4. associate CME with DSP farm profile
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register Conf
associate profile 1 register Xcode

5. Enable conferencing
telephony-service
sdspfarm units 2
sdspfarm tag 1 Conf
sdspfarm tag 1 Xcode

6. configure Ad-Hoc and Meet-Me number
ephone-dn 99 dual-line
number 888
conference ad-hoc (or meetme)
preference
no huntstop

7. configure conf option for a phoen

8. how to verify
show ephone-dn conference
show telephony-service conference hardware
show dsp all, only see status: associated means good
show voice dsp
show sdspfarm sessions
show sdspfarm units

Sunday, March 28, 2010

Cisco Lifecycle Services

Cisco Lifecycle Services

1. Prepare Phase

1.1 Account qualification and planning

1.2 Business requirements development

1.3 Technology stragety development

1.4 High-level design development

1.5 Business case development

1.6 Proof of concept

2. Plan Phase

2.1 Planning project kickoff

2.2 Site readiness assessment

2.3 Network readiness assessment

2.4 Operations readiness assessment

2.5 Security architecture assessment

3. Design Phase

3.1 Detailed design document

3.2 Operations plan development

3.3 Implementation plan development

3.4 Staging plan development

3.5 Systems acceptance test plan development

3.6 Staff plan development

4. Implement Phase

4.1 Staging and systems migration

4.1.1 Verifying bill of materials (BMO), adding to inventory and completing out-of-box component test

4.1.2 Configuring all devices

4.1.3 Executing test cases

4.1.4 Preparing for migration. Double check BOM, logistics and other 3rd party resources

4.1.5 Tracking and verifying site dependency milestones. Doucle check schedule and support from customer and 3rd party

4.1.6 Executing migration plan. Completing implementation activities and tasks for all sites

4.1.7 Hosting a handoff meeting

4.2 Implementation

4.2.1 Prepare for implementation

4.2.2 Install, configure and integrate system components

4.2.3 Complete implementation plan test cases

4.2.4 Document implemented components, devices and applications

4.2.5 Develop an implementation report

4.2.6 Conduct post implementation hand off meeting

4.3 Staff Training

4.4 Systems acceptance testing

4.5 Operations implementation

4.6 Post implementation support handoff meeting

4.6.1 Preparing for handoff meeting

4.6.2 SMARTnet only support

4.6.3 SMARTnet shared support

4.6.4 SMARTnet shared and partnet value added support

4.6.5 Verifying customer understand

4.7 Project close out

4.7.1 Obtaining customer satisfaction: sends a customer satisfaction survey to customer

4.7.2 Determining engagement profitability. Evaluates the internal sucess of the project

4.7.3 Conducting lessons learned meeting.

4.7.4 Incorporating into leading practices.

5. Operate Phase

5.1 Systems monitoring and problem management

5.2 Incident management

5.3 Change management

5.3.1 Originating change

5.3.2 Evaluating change

5.3.3 Accept and schedule change

5.3.4 Communicate change

5.3.5 Conduct post-change evaluations

5.3.6 Accept and close change

5.4 Configuration management

5.5 Security administration

6. Optimise Phase

Tuesday, March 23, 2010

Campus QoS

Cisco QoS 设计和配置都可以在这个文档中找到。有这个文档,一切搞定。http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html

Wednesday, March 10, 2010

borderless switches

2960-S,3560-X and 3750-X是下一代的access layer switches。增加了一些功能,比如FlexStack for 2960-S, PowerStack for redundant power supply and Macsec 加密。

这里能找到相关的介绍
http://www.cisco.com/web/partners/sell/technology/borderless/accelerate_products.html#sw

http://www.cisco.com/web/partners/sell/technology/borderless/bn_accelerate_launch.html

Tuesday, March 9, 2010

2975 Switch

这个2975就是3750G-48-PoE的简化版本,端口一样,带宽都是32G,转发速度都是38.7 mpps,都可以stack到9台。唯一不同的就是3750是三层的,2950只是2层的。

2975目前只有一个型号,stack cable跟3750是否一样还不太清楚。

WS-C3750G-48PS-S 的标价是18284加元, WS-C2975GS-48PS-L的标价是11800加元,便宜了不少。

我还没有用过2975不过很多客户感兴趣。比3750便宜不少,性能还一样。

Switch QoS

交换机QoS

3750和3560是一样的,两个输入queue,没有priority queue。4个输入队列,队列1是priority。在配置QoS的时候,主要注意mapping,然后把cos5放到queue1中。其他配置参考best practice。

6500需要看不同的板卡。我的经验是打开mls qos后,使用默认配置即可。

access layer信任cos电话,信任dscp from uplink,distribution和core信任dscp。

3750的QoS best practice


! enable QoS on the switch
mls qos
!MAPS
! Re-map CoS (L2) to DSCP
! Cos 2 = AF21 (18) Mission Critical and Delay Sensitive Data
! CoS 3 = AF31 (26) Voice Control
! CoS 4 = AF41 (34) Video
! CoS 5 = EF (46) Voice
! Cos 6 = AF (48) Network Control
! Cos 7 = AF (56) Network Control
mls qos map cos-dscp 0 8 18 26 34 46 48 56

!INPUT QUEUES
! Setup input queue thresholds
mls qos srr-queue input threshold 1 25 80
mls qos srr-queue input threshold 2 25 60
!Set up the ingress queues so that queue 2 is the PQ and dedicated 20% bandwidth
no mls qos srr-queue input priority-queue 1
no mls qos srr-queue input priority-queue 2
mls qos srr-queue input priority-queue 2 bandwidth 20
! Allocate half of the remaining bandwidth to each queue
mls qos srr-queue input bandwidth 50 50
! Assign buffer percentages to each queue
mls qos srr-queue input buffers 70 30
! Ingress Queue Mapping (map CoS values to one of the two queues)
! (Maps CoS 0,1 to Queue 1, CoS 2-7 to queue 2)
no mls qos srr-queue input cos-map
mls qos srr-queue input cos-map queue 1 threshold 3 0
mls qos srr-queue input cos-map queue 1 threshold 2 1
mls qos srr-queue input cos-map queue 2 threshold 1 2 3
mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
mls qos srr-queue input cos-map queue 2 threshold 3 5
! Ingress DSCP Queue Mapping
no mls qos srr-queue input dscp-map
mls qos srr-queue input dscp-map queue 1 threshold 2 8 9 10 11 12 13 14 15
mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue input dscp-map queue 2 threshold 1 24 25 26 27 28 29 30 31
mls qos srr-queue input dscp-map queue 2 threshold 2 32 33 34 35 36 37 38 39
mls qos srr-queue input dscp-map queue 2 threshold 2 48 49 50 51 52 53 54 55
mls qos srr-queue input dscp-map queue 2 threshold 2 56 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
!OUTPUT QUEUES

! Setup Egress Thresholds and Memory Allocation
mls qos queue-set output 1 threshold 1 138 138 92 138
mls qos queue-set output 1 threshold 2 40 70 92 400
mls qos queue-set output 1 threshold 3 36 70 100 318
mls qos queue-set output 1 threshold 4 20 50 67 400
! Egress Queue Mapping (map CoS values to one of the four queues)
no mls qos srr-queue output cos-map
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 6 7
mls qos srr-queue output cos-map queue 2 threshold 2 4
mls qos srr-queue output cos-map queue 3 threshold 3 3
mls qos srr-queue output cos-map queue 3 threshold 2 2
mls qos srr-queue output cos-map queue 4 threshold 2 1
mls qos srr-queue output cos-map queue 4 threshold 3 0
!! Egress DSCP Queue Mapping
no mls qos srr-queue output dscp-map
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 2 threshold 2 32 33 34 35 36 37 38 39
mls qos srr-queue output dscp-map queue 3 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue output dscp-map queue 3 threshold 2 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 4 threshold 2 8 9 10 11 12 13 14 15
mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7

! Set up egress queue buffer sizes
mls qos queue-set output 1 buffers 20 30 10 40
interface range fastEthernet1/0/1 - 24
srr-queue bandwidth shape 10 0 0 0
srr-queue bandwidth share 10 30 20 40
priority-queue out
interface range gigabitEthernet1/0/1 - 2
srr-queue bandwidth shape 10 0 0 0
srr-queue bandwidth share 10 30 20 40
priority-queue out

! Ports that connect to IP Phones:
Interface range fastEthernet1/0/1 - 24
! trust the CoS from the phone
mls qos trust cos
! trust the phone - CDP needs to be enabled for this
mls qos trust device cisco-phone
! re-mark anything from the phone's PC port to 0 - don't do this if using softphone though!
switchport priority extend cos 0
! Trunk Ports that are uplinks:
interface range gig1/0/1 - 2
! trust CoS
mls qos trust cos